Re: Oracle 12.2 is junk!
Date: Mon, 21 Oct 2019 15:55:37 +0000
Message-ID: <SN1PR07MB4109633E88CF8B3781144EF5E2690_at_SN1PR07MB4109.namprd07.prod.outlook.com>
Mladen,
My sympathies. I have had no problems patching 12.2 non-RAC systems. but fora couple of, but not all our 12.2 RAC databases, patching has been an adventure.
Haver you verified that you actually have a corrupt blocks? If so, I am wondering if the corruption occurred during the last patching cycle. I'm not sure if Oracle is going to make any changes to any database objects before the pre-checks are done.
Ian A. MacGregor
SLAC National Accelerator Laboratory
From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of Mladen Gogala <gogala.mladen_at_gmail.com> Sent: Sunday, October 20, 2019 4:36 PM
To: oracle-l <oracle-l_at_freelists.org> Subject: Oracle 12.2 is junk!
I tried patching plain vanilla Oracle 12.2 on OL 7.7 and patch installation went fine. However "datapatch" part did not work:
[oracle_at_ora122 30133625]$ $ORACLE_HOME/OPatch/datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Sun Oct 20 19:19:07 2019
Copyright (c) 2012, 2019, Oracle. All rights reserved.
Log file for this invocation: /oracle/cfgtoollogs/sqlpatch/sqlpatch_4981_2019_10_20_19_19_07/sqlpatch_invocation.log
Connecting to database...OK
Note: Datapatch will only apply or rollback SQL fixes for PDBs
that are in an open state, no patches will be applied to closed PDBs.
Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
(Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Queryable inventory could not determine the current opatch status.
Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual'
and/or check the invocation log
/oracle/cfgtoollogs/sqlpatch/sqlpatch_4981_2019_10_20_19_19_07/sqlpatch_invocation.log
for the complete error.
Prereq check failed, exiting without installing any patches.
Please refer to MOS Note 1609718.1 and/or the invocation log /oracle/cfgtoollogs/sqlpatch/sqlpatch_4981_2019_10_20_19_19_07/sqlpatch_invocation.log for information on how to resolve the above errors.
SQL Patching tool complete on Sun Oct 20 19:19:20 2019
So, I did what the message suggests:
[oracle_at_ora122 30133625]$ sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Sun Oct 20 19:19:40 2019
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
SQL> select dbms_sqlpatch.verify_queryable_inventory from dual;
VERIFY_QUERYABLE_INVENTORY
ORA-20001: Latest xml inventory is not loaded into table
So, I went to Oracle Support and looked for the message above. No problems, I am not the first one to encounter this:
datapatch Fails with "ORA-20001: Latest xml inventory is not loaded into table" due to Block Corruption "ORA-01578" (Doc ID 2364930.1)
Here is the solution:
- Fix the corrupted blocks and validate SYSAUX datafile. Note: You need to restore from valid rman backups or datapump exp/imp.
- Re-run datapatch
cd $ORACLE_HOME/OPatch
./datapatch -verbose
So, I've had a fully functional Oracle DB, I install October patches and now I have to do recovery? What idiot got rid of catbundle PSU apply? I have been patching Oracle 11g for years and now I have all sorts of problems with Oracle 12.2 and Oracle 18.8? Do we really need a patching utility that causes unnecessary problems? I rolled back the patches and will not apply any more patches to 12.2 until Oracle comes up with the sure fire way to fix the "datapatch" problems and repopulate the tables from "lsinventory".
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 -- http://www.freelists.org/webpage/oracle-lReceived on Mon Oct 21 2019 - 17:55:37 CEST