This is third time when i have face ORA-00600 . As i have mention last two scenario in my previous post . My production database was working fine .I have created it few days ago .There are about 100 users connected to database . I have scheduled the backup through OEM . On very next day while monitering I find that the backup scheduled through OEM get failed . On diagnosis , i find that the backup failed due to RMAN fatal error . Then i check my alert file and find the ORA-600 . Even having the ORA-00600 error the production database is going fine.
RMAN> run {
backup database plus archivelog ;
delete noprompt obsolete;
}
Starting backup at 11-MAY-11
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=34 device type=DISK
RMAN-00571: =======================================================
RMAN-00569: ========== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: =======================================================
RMAN-00601 : fatal error in recovery manager
RMAN-03004 : fatal error during execution of command
Since i don't have any physical or logical backup of database,so i decided to take logical backup and again got the following error .
C:\>expdp system/xxxx@rosen schemas=CCI_HOAL directory=dpump dumpfile=hoal_11052011.dmp logfile=exp_hoal_11052011log.log
Export: Release 11.2.0.1.0 - Production on Fri May 11 11:27:34 2011Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_07": system/********@rosen schemas=CCI_HOAL directory=dpump dumpfile=hoal_11052011.dmp logfile=exp_hoal_11052011log.log
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 4.48 GB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
ORA-39097: Data Pump job encountered unexpected error -600
ORA-39065: unexpected master process exception in MAIN
ORA-00600: internal error code, arguments: [ksuloget2], [0xFEBDD104], [0xFEBCEE54], [496], [0xFEBDD128], [], [], [], [], [], [], []
and it get's hang here.So i kill the job
Export> kill_job
UDE-31623: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_DATAPUMP", line 1137
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4583
ORA-06512: at line 1
So, we have decided to do some workround to get rid of these error. After some troubleshooting and diagnosis we have decided to reduce the size of the sga target . This error occurs when we set the size of sga target more than 1GB. Hence to solve this, I have decided to decrease the size of sga target. Here, in this scenario's i have not exactly solved the issue because it strongly recommended to get support from Oracle whenever we face ORA-00600 .Hope this may help you if the above error occurs.
To know more about ORA-00600. click here .
Enjoy J J J
No comments:
Post a Comment