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/dbaonlin/DBAONLIN1/trace/DBAONLIN1_ora_20026.trc:  
 ORA-30013: undo tablespace 'UNDO2' is currently in use  
 PRODONL(6):JIT: pid 20026 requesting stop  
 PRODONL(6):detach called for domid 6 (domuid: 0xf8d86493, options: 0x10, pid: 20026)  
 PRODONL(6):queued detach broadcast request 43f144a00  
 2020-05-18T04:28:56.600493+05:30  
 ORA-30013 signalled during: alter pluggable database PRODONL open...
PDBs ware configured use to Local Undo mode (Undo Modes in 12.2 Multitenant Databases) and the strange part was, PDB on node 1 is looking for 'UNDO2', which is the local undo tablespace defined for node 2 of the RAC.

We have decided to operate on the opened RAC node and raised a SR with Oracle, which pointed to unpublished bug, Bug - 24808699 - PDB Created On Local Undo CDB RAC Db Fails To Open As UNDOTBS1 Already In Use.

The solutions was to explicitly set the correct undo Tablesapce name, in our case below.
 SQL> show pdbs;  
 CON_ID CON_NAME OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
 6 PRODONL MOUNTED  
 SQL> startup;  
 ORA-30013: undo tablespace 'UNDO2' is currently in use  
 SQL> show pdbs;  
 CON_ID CON_NAME OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
 6 PRODONL MOUNTED  
 SQL> alter system set undo_tablespace=UNDO1 container=current scope=spfile;  
 System altered.  
 SQL> startup;

Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> Create
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more