I’ve run into this as well. The way I got around it was to restore the
database and do the following before re-trying dbua:
exec DBMS_AQADM.DROP_QUEUE_TABLE(queue_table => ‘sys.alert_qt’, FORCE => TRUE);
@?/rdbms/admin/catnoalr
This will result in invalid objects in the sys/system schemas. That’s fine.
The upgrade will recreate what was dropped and all will be good when it’s
finished.
This has worked every time I’ve had this problem.
Scott Canaan ‘88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Jay Hostetter
Sent: Friday, February 21, 2020 7:33 AM
To: Ls Cheng <exriscer@xxxxxxxxx>
Cc: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: Re: January RU Combo Patch
This was the exact problem that I ran into when running datapatch. The
workaround for me was to NOT use the combo patch. I downloaded the Grid RU and
OJVM RU patches separately:
p30501910_190000_Linux-x86-64.zip
p30484981_190000_Linux-x86-64.zip
Jay
On Fri, Feb 21, 2020 at 6:36 AM Ls Cheng
<exriscer@xxxxxxxxx<mailto:exriscer@xxxxxxxxx>> wrote:
Hi
Did you get this error when patching the management database? I got error for
two clusters and for other 2 cluster the patch went through
Installing patches...
Patch installation complete. Total patches installed: 3
Validating logfiles...done
Patch 30557433 apply (pdb CDB$ROOT): SUCCESS
logfile:
/u01/app/grid/cfgtoollogs/sqlpatch/30557433/23305305/30557433_apply__MGMTDB_CDBROOT_2020Feb21_10_18_25.log
(no errors)
Patch 30557433 apply (pdb PDB$SEED): SUCCESS
logfile:
/u01/app/grid/cfgtoollogs/sqlpatch/30557433/23305305/30557433_apply__MGMTDB_PDBSEED_2020Feb21_10_19_56.log
(no errors)
Patch 30557433 apply (pdb GIMR_DSCREP_10): WITH ERRORS
logfile:
/u01/app/grid/cfgtoollogs/sqlpatch/30557433/23305305/30557433_apply__MGMTDB_GIMR_DSCREP_10_2020Feb21_10_19_56.log
(errors)
-> Error at line 42: script rdbms/admin/bug_29784106_prepatch.sql
- ORA-00600: internal error code, arguments: [pfri.c#103: bad lu type],
[22], [],
- [], [], [], [], [], [], [], [], []
- ORA-06512: at "SYS.DBMS_AQADM_SYS", line 15446
- ORA-06512: at "SYS.DBMS_AQADM_SYSCALLS", line 778
- ORA-06512: at "SYS.DBMS_AQADM", line 769
- ORA-06512: at line 5
- ORA-06512: at line 5
Thanks
On Fri, Feb 7, 2020 at 9:37 PM Jay Hostetter
<hostetter.jay@xxxxxxxxx<mailto:hostetter.jay@xxxxxxxxx>> wrote:
My support tech didn't say if it will be republished. Since I have a
workaround, the SR is now closed.
Jay
On Fri, Feb 7, 2020 at 2:09 AM Ls Cheng
<exriscer@xxxxxxxxx<mailto:exriscer@xxxxxxxxx>> wrote:
Good to know, are they going to re-publish the patch?
TIA
On Thu, Feb 6, 2020 at 8:13 PM Jay Hostetter
<hostetter.jay@xxxxxxxxx<mailto:hostetter.jay@xxxxxxxxx>> wrote:
I ran into an ORA-0600 when running datapatch for the January 2020 RU for 19c.
After going back and forth with Support and doing some testing, it seems as
though the combo patch for Linux x86-64 (30463609) may have an issue. My
specific error was related to Streams.
I downloaded the GI and OJVM patches separately and was able to successfully
apply the the RU.
Hopefully this info may save some aggravation if you are preparing to install
this Release Update.
Jay
