Gayatri_R
asked on
block corruption in sysaux tablespace
I've a 10.2.0.3 ebusiness instance running on rac. Each time I reboot the database I'm getting block corruption error
ORA-00600: internal error code, arguments: [2032], [41963585], [41963585], [8192], [2], [255], [0], [767]
.When I analyzed the trace file I found the corruption occurs on sysaux tablespace. Is there a way I can fix this issue.
Regards,
Gayatri
ORA-00600: internal error code, arguments: [2032], [41963585], [41963585], [8192], [2], [255], [0], [767]
.When I analyzed the trace file I found the corruption occurs on sysaux tablespace. Is there a way I can fix this issue.
Regards,
Gayatri
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
one more thing sysaux TS is the most dynamic accident prone TS in the whole ;and your chances to have corruption in yet is yet higher than the others ;
if you check metalink you will find that so many things will cause corruption in this TS like
with some versions and backing up with check logical;and then taking these backups to restore to a new host ;
also sometimes when you have compresion on .
try to recover the blocks meanwhile open a TAR worst case scenario you can survive a remake of your sysaux!!!
if you check metalink you will find that so many things will cause corruption in this TS like
with some versions and backing up with check logical;and then taking these backups to restore to a new host ;
also sometimes when you have compresion on .
try to recover the blocks meanwhile open a TAR worst case scenario you can survive a remake of your sysaux!!!
Remember, in the end, SYSAUX can be rebuilt, if it cannot be recovered. There is a procedure to drop and recreate the SYSMAN schema.
You probably need to get patched to 10.2.0.4 but all that AFTER you call Oracle and open an SR pronto!