Email: service@parnassusdata.com 7 x 24 online support!
Oracle Error ORA-376 encountered while recovering transaction (A, B) on object YYYY.
oerr ora 376
00376, 00000, "file %s cannot be read at this time"
// *Cause: attempting to read from a file that is not readable. Most likely
// the file is offline.
// *Action: Check the state of the file. Bring it online
ORA-1546: tablespace contains active rollback segment '<rbsname>'
The named tablespace contains an active rollback segment as named in the error. Actions: 1. Offline the named rollback segment: eg: ALTER ROLLBACK SEGMENTOFFLINE; 2. Re-attempt to offline the tablespace
ORA-1545 during DROP ROLLBACK SEGMENT <rbsname>
ORA-1545 may be signalled during a "DROP ROLLBACK SEGMENT" if the
rollback segment is currently online.
eg: SVRMGR> drop rollback segment rprbs;
drop rollback segment rprbs
*
DBA_ROLLBACK_SEGS entry of status "NEEDS RECOVERY" or "PARTLY AVAILABLE"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DBA_ROLLBACK_SEGS entry of status "NEEDS RECOVERY"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The DBA_ROLLBACK_SEGS view shows a rollback segment as "NEEDS RECOVERY"
ORA-1545 during Oracle Startup
[oracle@ocp2 ~]$ oerr ora 1545 01545, 00000, "rollback segment '%s' specified not available" // *Cause: Either: // 1) An attempt was made to bring a rollback segment online that is // unavailable during startup; for example, the rollback segment
Oracle ASM COMMUNICATION ERROR CAUSING THE INSTANCE TO CRASH
ASM communication error has been reported by RDBMS which is leading to
Oracle ASM DISKGROUP WILL NOT MOUNT AFTER ADDING DISKS
This environment is using secure file. There is no backup due to customer
Oracle ORA-600 [3020] , ORA-353 DURING DATABASE RECOVERY
this happened 3 times on 3 different archivedlogs in a recent recovery.