Friday, 8 July 2016

ORA-8102 due to data inconsistent between job$ and index I_JOB_NEXT

›
These errors flooded the database alert log. Thankfully, Oracle was kind enough to specify the object number (obj# or object id) which permi...
2 comments:

ORA-00600: internal error code, arguments: [4194]

›
These errors constantly appeared in the database alert log at the point of opening a database. After reviewing the alert log and correspon...
Thursday, 23 July 2015

ORA-00392: log 1 of thread 1 is being cleared, operation not allowed, ORA-00312: online log 1 thread 1: '+DATA'

›
The above error occured during test restore of a RAC database (ASM based) to a single instance filesystem based database. This was encount...
Tuesday, 21 July 2015

'WARNING: Subscription for node down event still pending' in Listener Log

›
This is a single instance database 11.2.0.3 running on RHEL box. This is related to the Oracle TNS Listener's default subscription to t...

ORA-00060: deadlock detected while waiting for resource. Global Enqueue Services Deadlock detected. More info in file

›
Environment: 2-node RAC 11.2.0.3. The following messages are constantly showing up in the alert log. ORA-00060: deadlock detected whil...
1 comment:
Thursday, 16 July 2015

RMAN-03002: failure of restore command at 07/16/2015 20:08:00 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20005: target database name is ambiguous

›
RMAN-03002: failure of restore command at 07/16/2015 20:08:00 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20005: target da...
Wednesday, 15 July 2015

upgrading RMAN catalog schema to support 12c databases

›
Existing infrastructure: Recovery catalog database is 11.2.0.3. We have just deployed a 12.1.0.1.0 database and it needs to be included in t...