Alter New Primary Open Hang After Switchover
(Doc ID 2663273.1)
Last updated on AUGUST 29, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 19.6.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
1. All was working well until the switchover. After Data Guard switchover, unable to open PDB.
SQL> alter pluggable database <pdb_name> open;
alter pluggable database <pdb_name> open
* ERROR at line 1:
ORA-65054: Cannot open a pluggable database in the desired mode.
alter pluggable database <pdb_name> open
* ERROR at line 1:
ORA-65054: Cannot open a pluggable database in the desired mode.
There's no service that's created for the PDB at this point
$ srvctl status service -db <DATABASE_NAME>
$ srvctl config database -db <DATABASE_NAME>
Database unique name: <DATABASE_NAME>
Database name:
Oracle home: /u01/app/oracle/product/19.0.0.0/db_1
Oracle user: oracle
Spfile: +<DG_NAME>/<DATABASE_NAME>/PARAMETERFILE/spfile.276.1037776417
Password file: +<DG_NAME>/<DATABASE_NAME>/orapwcaprd
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups: <DG_NAME>,<DG_NAME1>,<DG_NAME2>
Mount point paths:
Services:
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: oper
Database instances: <instane_name1>,<instane_name2>
Configured nodes: <node_name1>,<node_name2>
$ srvctl config database -db <DATABASE_NAME>
Database unique name: <DATABASE_NAME>
Database name:
Oracle home: /u01/app/oracle/product/19.0.0.0/db_1
Oracle user: oracle
Spfile: +<DG_NAME>/<DATABASE_NAME>/PARAMETERFILE/spfile.276.1037776417
Password file: +<DG_NAME>/<DATABASE_NAME>/orapwcaprd
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups: <DG_NAME>,<DG_NAME1>,<DG_NAME2>
Mount point paths:
Services:
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: oper
Database instances: <instane_name1>,<instane_name2>
Configured nodes: <node_name1>,<node_name2>
2. Turns out the CDB was not open and the alter database open (for cdb) was hung on follow SQL:
current sql_id: 2381986511 current sql: update /*+ rule */ undo$ set name=:2,file#=:3,block#=:4,status$=:5,user#=:6,undosqn=:7,xactsqn=:8,scnbas=:9,scnwrp=:10,inst#=:11,ts#=:12,spare1=:13 where us#=:1
3. wait information:
- 'row cache lock'
- 'cursor: pin S wait on X'
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |