My Oracle Support Banner

PDB startup hang on the 2nd node after exafusion is enabled (Doc ID 2421027.1)

Last updated on SEPTEMBER 29, 2021

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

PDB startup hang on the 2nd node after exafusion is enabled by the following steps.

Steps
===========================
1. Set the exafusion_enabled parameter to 1
alter system set exafusion_enabled=1 scope=spfile sid='*';

2. Stop DB
srvctl stop database -db <db_name>;

3. Startup DB on node1, PDB startup successfully.
srvctl start instance -db <db_name> -i <sid_name1>;

SQL> show pdbs

   CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
        2 PDB$SEED                       READ ONLY  NO
        3 PDB1                           READ WRITE NO

4. Startup DB on node2, PDB startup hang.
srvctl start instance -db <db_name> -i <sid_name2>;

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       MOUNTED
         3 PDB1                           MOUNTED

The following error occurred while attempting to start up PDB manually.

SQL> alter pluggable database all open ;
alter pluggable database all open
*
ERROR at line 1:
ORA-01219: database or pluggable database not open: queries allowed on fixed tables or views only


- From systemstate dump we can see oraagent process hangs for "gc cr request"

    client details:
      O/S info: user: oracle, term: , ospid: 27853
      machine: dbadm01vm03.us.oracle.com program: oraagent.bin@dbadm01vm03.us.oracle.com (TNS V
      application name: oraagent.bin@dbadm01vm03.us.oracle.com (TNS V, hash value=3849289634
    Current Wait Stack:
     0: waiting for 'gc cr request'
        file#=0x1, block#=0x208, class#=0x4
        wait_id=763 seq_num=769 snap_id=1
        wait times: snap=17 min 51 sec, exc=17 min 51 sec, total=17 min 51 sec
        wait times: max=infinite, heur=17 min 51 sec
        wait counts: calls=859 os=859
        in_wait=1 iflags=0x5a0

Changes

Set exafusion_enabled=1 on 12.1.0.2 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.