Posts

Showing posts from May, 2020

ORA-30013 undo Tablespace currently in use during PDB open

DB - Oracle 12.2.0.1 2 node RAC with multitenant OS - Soalris SPARC 11.3 When a 2 node RAC cluster instances were restarted the CDB instance was opened successfully but the PDB was not opening with below errors on the alert log. PDB was on mounted state and not went to 'Restricted' mode. 2020-05-18T04:28:53.167538+05:30 alter pluggable database PRODONL open PRODONL(6):Autotune of undo retention is turned on. 2020-05-18T04:28:54.452346+05:30 PRODONL(6):attach called for domid 6 (domuid: 0xf8d86493, options: 0x4, pid: 20026) PRODONL(6):queued attach broadcast request 43f144a50 PRODONL(6):Endian type of dictionary set to big 2020-05-18T04:28:55.523090+05:30 PRODONL(6):Undo initialization errored: err:30013 serial:0 start:4085472674 end:4085472823 diff:149 ms (0.1 seconds) Pdb PRODONL hit error 30013 during open read write (1) and will be closed. 2020-05-18T04:28:55.524179+05:30 Errors in file /u01/app/oracle/product/12.2.0/diag/rdbms/dbaon...

Oracle Scheduler Jobs not starting the execution until 15-45 mins after scheduled time

DB - Oracle 12.2.0.1 2 node RAC with multitenant OS - Soalris SPARC 11.3 We have come across this strange issue where DBMS_SCHEDULER jobs were submitted, it just waited randomly for 15-45 mins without doing anything. Then suddenly it started and executed in the expected time. This happened with random scheduler jobs on different times. When going through the session details, they were waiting on 'PL/SQL lock timer' event. Also when we have come across a hardware maintenance and running on single node of the RAC the scheduler job delay was not occuring. After opening a SR with Oracle and going through multiple SRDCs ( Doc ID 2077171.1 , Doc ID 2077182.1 ,  Doc ID 2077187.1 ), and looking through different bugs ( Bug - 21047218 - Scheduler Jobs Hang For 23 Minutes Randomly Then Resume ) finally we come across the actual culprit, Bug 28402823 : 12.2.0.1 In Rac Dbms_Scheduler Set Schedule_Type To Null After Job Ran Manually This one was kind of odd and was bit difficult ...