My Oracle Support Banner

DATAPATCH STUCK ON CLONED PDB WITH AQ ERRORS ON EXACC GEN2 (Doc ID 2960626.1)

Last updated on JULY 31, 2024

Applies to:

Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 to 19.23.0.0.0 [Release 19]
Information in this document applies to any platform.

Symptoms

On : DBRU 19.14 with dbaastool 23.1.2.0.0_230411 version, One Console SRs

ACTUAL BEHAVIOR
---------------
datapatch stuck while trying to upgrade DB from 19.14 to 19.17DBRU


STEPS
-----------------------
The issue can be reproduced as following steps at will.

e.g.


1. Created 12.2 DB 'SourceCDB' with 5 pdbs (pdb1 - pdb5), then upgrade 12.2 to 19.14DBRU


2. Created 19.14 DB 'CloneCDB' with default one pdb (pdb1).


3. Cloned 1 pdb (pdb5) from SourceCDB to CloneCDB and the cloned pdb named clonedPDB


4. Upgrade to 19.17DBRU on both 19.14 DBRU. The datapatch stuck issue will only be occurred on clonedPDB.

 
Here is an example of datapatch stuck:

sqlpatch_invocation.log
=========
[2023-06-27 22:49:02] Patch 34419443 apply (pdb clonedPDB): WITH ERRORS
<<<<<<< Here, Patch 34419443 is DBRU19.17
[2023-06-27 22:49:02] logfile:
/u02/app/oracle/cfgtoollogs/sqlpatch/34419443/24972075/34419443_apply_CloneCDB_
clonedPDB_2023Jun27_18_01_05.log[2023-06-27 22:49:02] (errors)
[2023-06-27 22:49:02] -> Error at line 100152: script
rdbms/admin/prvtaqds.plb
[2023-06-27 22:49:02] - Warning: Package Body altered with compilation
errors.
[2023-06-27 22:49:02] -> Error at line 144080: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - Warning: Procedure created with compilation
errors.
[2023-06-27 22:49:02] -> Error at line 144122: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - Warning: Procedure created with compilation
errors.
[2023-06-27 22:49:02] -> Error at line 144129: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - 0/0 PL/SQL: Compilation unit analysis
terminated
[2023-06-27 22:49:02] -> Error at line 144130: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - 5/26 PLS-00905: object SYS.AQ$_DESCRIPTOR
is invalid
[2023-06-27 22:49:02] -> Error at line 144159: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - Warning: Procedure created with compilation
errors.
[2023-06-27 22:49:02] -> Error at line 144166: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - 0/0 PL/SQL: Compilation unit analysis
terminated
[2023-06-27 22:49:02] -> Error at line 144167: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - 2/16 PLS-00905: object SYS.AQ$_DESCRIPTOR
is invalid
[2023-06-27 22:49:02] -> Error at line 144199: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - Warning: Procedure created with compilation
errors.
[2023-06-27 22:49:02] -> Error at line 144206: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - 0/0 PL/SQL: Compilation unit analysis
terminated
[2023-06-27 22:49:02] -> Error at line 144207: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - 4/32 PLS-00905: object SYS.AQ$_DESCRIPTOR
is invalid
[2023-06-27 22:49:02] -> Error at line 144223: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - ORA-04063: package body "SYS.DBMS_AQADM_SYS"
has errors
[2023-06-27 22:49:02] - ORA-06512: at line 6
[2023-06-27 22:49:02] - ORA-06508: PL/SQL: could not find program unit
being called:
[2023-06-27 22:49:02] - "SYS.DBMS_AQADM_SYS"
[2023-06-27 22:49:02] - ORA-06512: at "SYS.DBMS_AQADM", line 1862
[2023-06-27 22:49:02] - ORA-06512: at line 2
[2023-06-27 22:49:02] -> Error at line 144238: script
rdbms/admin/execschlb.plb
[2023-06-27 22:49:02] - ORA-04063: package body "SYS.DBMS_AQADM_SYS"
has errors
[2023-06-27 22:49:02] - ORA-06508: PL/SQL: could not find program unit
being called:
[2023-06-27 22:49:02] - "SYS.DBMS_AQADM_SYS"

...


Here is an example of AQ objects signature is not matching for cdb$root and cloned pdb's since SourceCDB has force bit and CloneCDB does not have force bit.

 

CloneCDB, cdb$root
=========
col name for a30
set linesize 1000
select obj#, owner#, name, type#, flags, signature, status from obj$
where name in ('AQ$_POST_INFO')
order by 1, 2;

OBJ# OWNER# NAME TYPE# FLAGS SIGNATURE STATUS
---------- -------- -------- - ---------- ---------- -------------------------------- ----------
8983 0 AQ$_POST_INFO 13 5308416 08B1552ACFAF53EF773299B8D8B9A1F8 1
13770 0 AQ$_POST_INFO 13 5308416 4D98E90FE0F5D11A3BA7CFCCFD82D11C 1

 

clonedPDB
=======
col name for a30
set linesize 1000
select obj#, owner#, name, type#, flags, signature, status from obj$
where name in ('AQ$_POST_INFO')
order by 1, 2;

OBJ# OWNER# NAME TYPE# FLAGS SIGNATURE STATUS
---------- -------- -------- - ---------- ---------- -------------------------------- ----------
8636 0 AQ$_POST_INFO 13 5308416 0F4D3635C8B946F99F62030853762E33 1

12368 0 AQ$_POST_INFO 13 5308416 4ECA3A7AD4112916AC1FE611DDB3173E 1

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
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.