Provisioning a vPDB fails with ORA-30013: undo tablespace 'UNDO_NAME' is currently in use OPEN_PDB_ERROR (KBA8367)
KBA
KBA# 8367
Issue
Provisioning a vPDB to an Oracle RAC instance fails with: ORA-30013: undo tablespace 'UNDO_NAME' is currently in use OPEN_PDB_ERROR
Prerequisites
Delphix engine
Oracle database with PDB support
Oracle RAC instance (CDB) in target environment
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
-
Major Release All Sub Releases 6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0, 6.0.10.0, 6.0.10.1 5.3
5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0 5.2
5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1
5.1
5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0
5.0
5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4
Resolution
The issue has been confirmed to be an Oracle bug and, therefore, external from Delphix.
If the PDB (or vPDB) uses an undo tablespace of the type bigfile and runs on a single instace, the error is received when trying to provision from a snapshot of that PDB to an Oracle RAC instance.
Oracle does create the undo tablespace for each instance in the node if the undo tablespace is a regular file but fails to do so when it is of the type bigfile.
It is recommended to raise the issue with Oracle Support in order to check if a patch is available.
Alternatively, you may consider switching from bigfile to a regular file on the source database (dSource/VDB), take a new snapshot, and then provision from that snapshot to workaround the issue.
Troubleshooting
Confirm the name and status of the PDB/vPDB on the single instance:
COLUMN NAME FORMAT A15 COLUMN RESTRICTED FORMAT A10 COLUMN OPEN_TIME FORMAT A30 SELECT NAME, OPEN_MODE, RESTRICTED, OPEN_TIME FROM V$PDBS;
Output:
NAME OPEN_MODE RESTRICTED OPEN_TIME --------------- ---------- ---------- --------------------------------- PDBNAME1 READ WRITE NO 03-NOV-21 03.39.49.013 AM -04:00
Alter the session to work with the PDB:
ALTER SESSION SET CONTAINER='PDBNAME';
Check the name(s) of the undo_tablepsace(s):
SELECT VALUE FROM V$PARAMETER WHERE NAME = 'undo_tablespace';
Output:
VALUE -------------------------------------------------------------------------------- UNDOTBS1
Check if the undo_tablespace is of type bigfile:
SELECT TABLESPACE_NAME,BIGFILE FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = 'UNDOTBS1';
Output:
TABLESPACE_NAME BIG ------------------------------ --- UNDOTBS1 YES
If the columns BIG reports YES as seen above, you will encounter the Oracle bug while provisioning from the PDB to an Oracle RAC CDB.
Related Articles
The following articles may provide more information or related information to this article:
- Oracle support reference MOS: Troubleshooting ORA-30013 Error (Doc ID 1578717.1)