Applies to:
Oracle Server – Enterprise Edition – Version: 10.2.0.3 and later [Release: 10.2 and later ]
Information in this document applies to any platform.
Symptoms
o There is no loss of functionality with this issue, only that since upgrade you are seeing
errors in the alert.log and it is unclear what the errors mean
o Upgrade database to 10.2.0.3.0, then start up and observe errors in the alert.log and trace files
being produced
o ORA-4063 encountered when generating server alert SMG-4121
ERROR: exception at dbms_ha_alerts_prvt.post_instance_up308: SQLCODE -13917,ORA-13917:
Posting system
alert with reason_id 135 failed with code [5] [post_error]
o Database appears to be working.
o We need to identify the source of the entries and how to stop them from occurring in the future.
Changes
Upgraded database to 10.2.0.3.0
Cause
The problem was the result of some type of corruption in the alert schema.
Issue was resolved by removing the alert schema and then recreating it.
Solution
– To implement the solution, please execute the following steps:
1. $ORACLE_HOME/rdbms/admin/catnoalr.sql
- Ran this to drop schema and objects related to server alerts
2. Run the following scripts to recreate the server alert objects:
$ORACLE_HOME/rdbms/admin/dbmsslrt.sql
$ORACLE_HOME/rdbms/admin/catalrt.sql
3. Recompiled the objects (by running the utlrp.sql script).
© 2009, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.
相关文章 | Related posts:
- dc_table_scns causes WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK in the alert log file
- Possible Cause of ORA-00354 and ORA-00353 -OR- ARC0: Error 19510 closing archivelog file
- Troubleshooting Streams Apply Error ORA-1403, ORA-26787 or ORA-26786
- How to trigger ORA-00600,ORA-7445 by manual
- REDO LOG CORRUPTION – DROPPING REDO LOGS NOT POSSIBLE – CLEAR LOGFILE
- ORA-600 [6006] ORA-600 [6856] During Startup Instance, Followed by Termination by SMON
- ORA-00600 [kddummy_blkchk]错误一例
- Oracle内部错误:ORA-00600[25012]一例
- Diagnosing ORA-12004 Refresh Fast Cannot be Used
- Troubleshooting ORA-1031 Insufficient Privilege
Hdr: 6522925 10.2.0.3.0 RDBMS 10.2.0.3.0 DICTIONARY PRODID-5 PORTID-268 ORA-4063
Abstract: AFTER MIGRATION FROM 32BIT TO 64BIT ORA-4063 ERRORS APPEARD IN ALERT LOG
PROBLEM:
——–
We recently migrated our test environment from 32-bit to 64-bit environment
running Windows 2003 Advanced Server Edition. We have 16 gig of physical
memory on the box and 4 CPUs.
Oracle 64 bit version is 10.2.0.3. It has been patched to the latest security
patch. We have also applied p5337014 and p6116139 patches on the 64-bit
platform.
Sat Oct 13 12:58:21 2007
Completed: ALTER DATABASE OPEN
Sat Oct 13 12:58:23 2007
ORA-4063 encountered when generating server alert SMG-4120
ORA-4063 encountered when generating server alert SMG-4121
ORA-4063 encountered when generating server alert SMG-4121
Sat Oct 13 13:03:17 2007
ORA-4063 encountered when generating server alert SMG-4121
ORA-4063 encountered when generating server alert SMG-4121
Sat Oct 13 13:08:17 2007
ORA-4063 encountered when generating server alert SMG-4120
ORA-4063 encountered when generating server alert SMG-4121
ORA-4063 encountered when generating server alert SMG-4121
Sat Oct 13 13:13:17 2007
ORA-4063 encountered when generating server alert SMG-4121
ORA-4063 encountered when generating server alert SMG-4121
DIAGNOSTIC ANALYSIS:
——————–
Search of WebIV and the bug database. Found no relevant hits
WORKAROUND:
———–
None at present.
RELATED BUGS:
————-
REPRODUCIBILITY:
—————-
Consistently at customer site.
TEST CASE:
———-
STACK TRACE:
————
SUPPORTING INFORMATION:
———————–
24 HOUR CONTACT INFORMATION FOR P1 BUGS:
—————————————-
DIAL-IN INFORMATION:
——————–
IMPACT DATE:
————
As soon as possible
Please get:
a. select owner, object_type from dba_objects where status!=’VALID’;
b. Set
event=”4063 trace name errorstack forever, level 3″
in the init.ora / spfile and restart the instance so that we
get a full errorstack and call stack when the ORA-4063 occurs.
c. Spooled output from catupgrd when it was run to perform
the upgrade (looks like it was on Oct 13th)