Return-Path: X-Original-To: oracle-l@orafaq.com Delivered-To: oracle-l@orafaq.com Received: from turing.freelists.org (turing.freelists.org [206.53.239.180]) by malta2546.startdedicated.com (Postfix) with ESMTPS id 38D4210032974B for ; Mon, 21 Oct 2019 17:57:26 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2867127D29; Mon, 21 Oct 2019 11:57:25 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freelists.org; s=turing; t=1571673445; bh=HAnvZXRxjdHszwCLawxCFW7VVCk/SjTlNOB6RpctDvw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:Reply-To:List-Help: List-Unsubscribe:List-Id:List-Subscribe:List-Owner:List-post: List-Archive; b=KDGj1AI5VOZo9y0YuDN+12b+2er7kDXTAzyUS701jvNcJjMrSSRFKGxR7BTk3cBeQ TdJ23lGcEyTX0ogjJG+4dhhmBgGVIkFESgUkpQbnIR067Egyqr5OhNBrlog8dXGK/K gj/P1xmMmt0KkxGsSJtuQhPqx+XCAqO8yras1cHc= X-Virus-Scanned: Debian amavisd-new at turing.freelists.org Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RscV9w4TVyE2; Mon, 21 Oct 2019 11:57:24 -0400 (EDT) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 52F5C21542; Mon, 21 Oct 2019 11:56:34 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freelists.org; s=turing; t=1571673436; bh=HAnvZXRxjdHszwCLawxCFW7VVCk/SjTlNOB6RpctDvw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:Reply-To:List-Help: List-Unsubscribe:List-Id:List-Subscribe:List-Owner:List-post: List-Archive; b=s2930mI0UA0LzOEZvaOwqVBC6/xQ5B0UWcoqtJKjzCmFeBUsr3HaVkEXTdXXCu0Xg YarzJ5u6KOd7eEOmighy8tA/u9GVbRRXpbcfr1BCPjECy9Mt8X92n5+pFLKq29513y DuwcP9aaoSouFrT+ggQx68mOVomrp89kQlkaS6Bg= Received: with ECARTIS (v1.0.0; list oracle-l); Mon, 21 Oct 2019 11:55:53 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2979627C9B for ; Mon, 21 Oct 2019 11:55:53 -0400 (EDT) Authentication-Results: turing.freelists.org; dkim=pass reason="2048-bit key; unprotected key" header.d=gmail.com header.i=@gmail.com header.b=CrMEspN1; dkim-adsp=pass; dkim-atps=neutral Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EccUsKsIOc7n for ; Mon, 21 Oct 2019 11:55:53 -0400 (EDT) Received: from mail-io1-f67.google.com (mail-io1-f67.google.com [209.85.166.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id EC04927C9A for ; Mon, 21 Oct 2019 11:55:52 -0400 (EDT) Received: by mail-io1-f67.google.com with SMTP id a1so16510984ioc.6 for ; Mon, 21 Oct 2019 08:55:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SLOLj9++ge+IUv56hVsu/dyl58A937Pi81Ly5HeCn3c=; b=W8PTSwzJuY5XtpVUIdPC93vNIMnvXG8kxo3K+twZd+uqS9q5Hs8l52Na9rbO8aYCMU 62W7Y8P6khBu7VjyV4RYj1Ng6jKxooICxPS1aARm2we52hD+czXTipbJRhq26yspM2Do F/1RYKxVSm/KjwxGWhh3b6JqfdMf3L1CGLssNcdZCbvSUr7rHGQQJxtBgyK/U0z8RlWs gdfDn0scc4FEUVt47Sl0mCDqVq/4TrOTRgbATnOJhzkIx5LccDtvx6PmvcguYghcu+2i V5CTj+uuDs+zb9eXVXWcyHy6wGZMhFUeKmjA8bXVM+ynsM3ZadVX8b1EKd6Eq4cqzZrP gKTQ== X-Gm-Message-State: APjAAAVsKmFbtrT7r0jR46i80A+KFDw7K0fOfioOHFFPhwLnGv+huPlc BKPaegLl7yZ8/0X3FFuvgcK4CyfluR0nl7xwkL0= X-Google-Smtp-Source: APXvYqxwB59Si6o5PHwl8LyKCc+HU8DM9mQE4Evl5piemOzmxLi3fa+I396MEQjwHMGP71l50zq08I6terN9Oo95IV4= X-Received: by 2002:a6b:ee18:: with SMTP id i24mr22628599ioh.163.1571673352270; Mon, 21 Oct 2019 08:55:52 -0700 (PDT) MIME-Version: 1.0 References: <29857_1571666789_5DADBB65_29857_8177_1_ed38ba3bbe454726bb6d9ff6a314e6a2@vontobel.com> <020801d58823$9413b4d0$bc3b1e70$@comcast.net> In-Reply-To: <020801d58823$9413b4d0$bc3b1e70$@comcast.net> From: niall.litchfield@gmail.com Date: Mon, 21 Oct 2019 16:55:40 +0100 Message-ID: Subject: Re: Oracle 12.2 is junk! To: dimensional.dba@comcast.net Cc: Noveljic Nenad , Mladen Gogala , oracle-l Content-Type: multipart/alternative; boundary="000000000000dd78dc05956db727" X-archive-position: 75141 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: niall.litchfield@gmail.com Precedence: normal Reply-To: niall.litchfield@gmail.com List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-Subscribe: List-Owner: List-post: List-Archive: X-list: oracle-l --000000000000dd78dc05956db727 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It's also worth mentioning that Note 1609718.1 mentioned in your output has at least a couple of possible causes in addition to the one you settled on. If you do have corruption in SYSAUX it's quite hard to blame datapatch for that. On Mon, Oct 21, 2019 at 4:25 PM wrote: > There are many of us who patch all the time for different clients and hav= e > no problems at all with datapatch, quarterly or one-offs. > > You definitely need to look at your log files as to what the specific > error is. > > > > > > > > *From:* oracle-l-bounce@freelists.org *On > Behalf Of *Noveljic Nenad > *Sent:* Monday, October 21, 2019 7:06 AM > *To:* gogala.mladen@gmail.com; oracle-l > *Subject:* RE: Oracle 12.2 is junk! > > > > Hi Mladen, > > > > The patching indeed became awkward since the good old sql upgrade scripts > were replaced by datapatch. But I=E2=80=99m afraid, there is no way back,= and > leaving the databases unpatched isn=E2=80=99t a sustainable option. > > > > datapatch invokes =E2=80=9Copatch lsinventory=E2=80=9D which basically ge= nerates some > shell scripts for loading the inventory.xml into the database to check wh= at > needs to be done. In the past, there have been concurrency problems, > because the generated files weren=E2=80=99t unique ( > https://nenadnoveljic.com/blog/simultaneous-patching-not-possible-datapat= ch/ > ) . The files in /u00/oracle/orabase/product/12.2.0.x.x/cfgtoollogs/opatc= h/lsinv/ > should provide you more information about the error. > > > > What worked for me is to start the datapatch with -apply and =E2=80=93for= ce > options to bypass the opatch invocations. You can specify the patch numbe= rs > after =E2=80=93apply. I tested this on many releases for non-cdb and > 18.7.0.0.190716 multi-tenant. > > > > Alternatively, if your database is multi-tenant, you could try patching > the containers one by one =E2=80=93 to avoid concurrency. (I haven=E2=80= =99t tried this > yet.) > > > > Best regards, > > > > Nenad > > > > *From:* oracle-l-bounce@freelists.org *On > Behalf Of *Mladen Gogala > *Sent:* Montag, 21. Oktober 2019 01:36 > *To:* oracle-l > *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@ora122 30133625]$ $ORACLE_HOME/OPatch/datapatch -verbose > SQL Patching tool version 12.2.0.1.0 Production on Sun Oct 20 19:19:07 20= 19 > 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_i= nvocation.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_i= nvocation.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_i= nvocation.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@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: > > a) Fix the corrupted blocks and validate SYSAUX datafile. > Note: You need to restore from valid rman backups or datapump exp/imp. > > b) 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 su= re > fire way to fix the "datapatch" problems and repopulate the tables from > "lsinventory". > > -- > > Mladen Gogala > > Database Consultant > > Tel: (347) 321-1217 > > ____________________________________________________ > > Please consider the environment before printing this e-mail. > > Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken. > > > Important Notice > This message is intended only for the individual named. It may contain > confidential or privileged information. If you are not the named addresse= e > you should in particular not disseminate, distribute, modify or copy this > e-mail. Please notify the sender immediately by e-mail, if you have > received this message by mistake and delete it from your system. > Without prejudice to any contractual agreements between you and us which > shall prevail in any case, we take it as your authorization to correspond > with you by e-mail if you send us messages by e-mail. However, we reserve > the right not to execute orders and instructions transmitted by e-mail at > any time and without further explanation. > E-mail transmission may not be secure or error-free as information could > be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Al= so > processing of incoming e-mails cannot be guaranteed. All liability of > Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively > referred to as "Vontobel Group") for any damages resulting from e-mail us= e > is excluded. You are advised that urgent and time sensitive messages shou= ld > not be sent by e-mail and if verification is required please request a > printed version. Please note that all e-mail communications to and from t= he > Vontobel Group are subject to electronic storage and review by Vontobel > Group. Unless stated to the contrary and without prejudice to any > contractual agreements between you and Vontobel Group which shall prevail > in any case, e-mail-communication is for informational purposes only and = is > not intended as an offer or solicitation for the purchase or sale of any > financial instrument or as an official confirmation of any transaction. > The legal basis for the processing of your personal data is the legitimat= e > interest to develop a commercial relationship with you, as well as your > consent to forward you commercial communications. You can exercise, at an= y > time and under the terms established under current regulation, your right= s. > If you prefer not to receive any further communications, please contact > your client relationship manager if you are a client of Vontobel Group or > notify the sender. Please note for an exact reference to the affected gro= up > entity the corporate e-mail signature. For further information about data > privacy at Vontobel Group please consult www.vontobel.com. > --=20 Niall Litchfield Oracle DBA http://www.orawin.info --000000000000dd78dc05956db727 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It's also worth mentioning that Note=C2=A01609718.1 mentioned in your ou= tput has at least a couple of possible causes in addition to the one you se= ttled on. If you do have corruption in SYSAUX it's quite hard to blame = datapatch for that.=C2=A0



On Mon, Oct 21= , 2019 at 4:25 PM <dimens= ional.dba@comcast.net> wrote:

There a= re many of us who patch all the time for different clients and have no prob= lems at all with datapatch, quarterly or one-offs.

=

You definitely need to look at your log files as= to what the specific error is.

=C2=A0

= =C2=A0

=C2=A0

From: oracle-l-bounce@freelists.org <oracle-l-boun= ce@freelists.org> On Behalf Of Noveljic Nenad
Sent:= Monday, October 21, 2019 7:06 AM
To: gogala.mladen@gmail.com; oracle-l <= ;oracle-l@freel= ists.org>
Subject: RE: Oracle 12.2 is junk!<= /span>

=C2=A0

Hi Mladen,

=C2=A0

The patching indeed became awkward since the goo= d old sql upgrade scripts were replaced by datapatch. But I=E2=80=99m afrai= d, there is no way back, and leaving the databases unpatched isn=E2=80=99t = a sustainable option.

=C2=A0

datapatch invo= kes =E2=80=9Copatch lsinventory=E2=80=9D which basically generates some she= ll scripts for loading the inventory.xml into the database to check what ne= eds to be done. In the past, there have been concurrency problems, because = the generated files weren=E2=80=99t unique ( https://nenadnoveljic.com/blog/simultaneous-patching-not-possible-datapat= ch/ ) . The files in /u00/oracle/orabase/product/12.2.0.x.x/cfgtoo= llogs/opatch/lsinv/ should provide you more information about = the error.

=C2= =A0

What worked for me is to = start the datapatch with -apply and =E2=80=93force options to bypass the op= atch invocations. You can specify the patch numbers after =E2=80=93apply. I= tested this on many releases for non-cdb and 18.7.0.0.190716 multi-tenant.=

=C2=A0<= /span>

Alternatively, if your database is m= ulti-tenant, you could try patching the containers one by one =E2=80=93 to = avoid concurrency. (I haven=E2=80=99t tried this yet.)=

=C2=A0

Best regards,

=C2=A0

Nenad=

=C2=A0<= /span>

From: oracle-l-bounce@freelists.org <oracle-l-b= ounce@freelists.org> On Behalf Of Mladen Gogala
Sent: Montag, 21. Oktober 2019 01:36
To: oracle-l <oracle-l@freelists.org>= ;
Subject: Oracle 12.2 is junk!

=C2=A0<= /p>

I tried patching plain vanilla Oracle 12.2 on OL= 7.7 and patch installation went fine. However "datapatch" part d= id not work:

[oracle@ora122 30133625]$ $ORACLE_HOME/= OPatch/datapatch -verbose
SQ= L Patching tool version 12.2.0.1.0 Production on Sun Oct 20 19:19:07 2019
Copyright (c) 2012, 2019, Oracle.=C2=A0 All rights reserved.

Log file for this invocation: /oracle/cfgtoollogs/sqlpatch/sql= patch_4981_2019_10_20_19_19_07/sqlpatch_invocation.log

Conn= ecting to database...OK
Note:=C2=A0 Datapatch will only apply o= r rollback SQL fixes for PDBs
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 that are in an open state, no patches will be applied to closed PDBs.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Please refer to Note: Datap= atch: Database 12c Post Patch SQL Automation
=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 (Doc ID 1585822.1)
Bootstrapping registry an= d package to current versions...done

Queryable inventory co= uld not determine the current opatch status.
Execute 'selec= t dbms_sqlpatch.verify_queryable_inventory from dual'
and/o= r check the invocation log
/oracle/cfgtoollogs/sqlpatch/sqlpatc= h_4981_2019_10_20_19_19_07/sqlpatch_invocation.log
for the comp= lete error.
Prereq check failed, exiting without installing any= patches.

Please refer to MOS Note 1609718.1 and/or the inv= ocation log
/oracle/cfgtoollogs/sqlpatch/sqlpatch_4981_2019_10_= 20_19_19_07/sqlpatch_invocation.log
for information on how to r= esolve the above errors.

SQL Patching tool complete on Sun = Oct 20 19:19:20 2019<= /p>

So, I did what the message suggests:

[oracle@ora122 30133625]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production o= n Sun Oct 20 19:19:40 2019

Copyright (c) 1982, 2016, Oracle= .=C2=A0 All rights reserved.


Connected to:
= Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Productio= n

SQL> select dbms_sqlpatch.verify_queryable_inventory f= rom dual;

VERIFY_QUERYABLE_INVENTORY
----------= ----------------------------------------------------------------------=
ORA-20001: Latest xml inventory is not loaded into table

So, I went to Oracle Support and looked for t= he message above. No problems, I am not the first one to encounter this:=

datapatch Fails with "ORA-20001: Latest xml inven= tory is not loaded into table" due to Block Corruption "ORA-01578= " (Doc ID 2364930.1)

Here is the solution:<= /p>

a) Fix the corrupted blocks and validate SYSAUX datafile.
Note: You need to restore from valid r= man backups or datapump exp/imp.=

b) Re-run datapatch

cd $ORACLE_HOME/OPatch

./datapatch -verbose=

So, I've had a full= y functional Oracle DB, I install October patches and now I have to do reco= very? What idiot got rid of catbundle PSU apply? I have been patching Oracl= e 11g for years and now I have all sorts of problems with Oracle 12.2 and O= racle 18.8? Do we really need a patching utility that causes unnecessary pr= oblems? 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&= quot; problems and repopulate the tables from "lsinventory".

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
____________________________________________________<=
/span>
Please consider the environment before prin=
ting this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.=


Importan=
t Notice 
This message is intended only for the individual named. It may=
 contain confidential or privileged information. If you are not the named a=
ddressee you should in particular not disseminate, distribute, modify or co=
py this e-mail. Please notify the sender immediately by e-mail, if you have=
 received this message by mistake and delete it from your system.
Withou=
t prejudice to any contractual agreements between you and us which shall pr=
evail in any case, we take it as your authorization to correspond with you =
by e-mail if you send us messages by e-mail. However, we reserve the right =
not to execute orders and instructions transmitted by e-mail at any time an=
d without further explanation.
E-mail transmission may not be secure or =
error-free as information could be intercepted, corrupted, lost, destroyed,=
 arrive late or incomplete. Also processing of incoming e-mails cannot be g=
uaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates=
 (hereinafter collectively referred to as "Vontobel Group") for a=
ny damages resulting from e-mail use is excluded. You are advised that urge=
nt and time sensitive messages should not be sent by e-mail and if verifica=
tion is required please request a printed version. Please note that all e-m=
ail communications to and from the Vontobel Group are subject to electronic=
 storage and review by Vontobel Group. Unless stated to the contrary and wi=
thout prejudice to any contractual agreements between you and Vontobel Grou=
p which shall prevail in any case, e-mail-communication is for informationa=
l purposes only and is not intended as an offer or solicitation for the pur=
chase or sale of any financial instrument or as an official confirmation of=
 any transaction.
The legal basis for the processing of your personal da=
ta is the legitimate interest to develop a commercial relationship with you=
, as well as your consent to forward you commercial communications. You can=
 exercise, at any time and under the terms established under current regula=
tion, your rights. If you prefer not to receive any further communications,=
 please contact your client relationship manager if you are a client of Von=
tobel Group or notify the sender. Please note for an exact reference to the=
 affected group entity the corporate e-mail signature. For further informat=
ion about data privacy at Vontobel Group please consult www.vontobel.com.


-- <= br>
Niall Litchfield
Oracle DB= A
http://www.orawin= .info
--000000000000dd78dc05956db727-- -- http://www.freelists.org/webpage/oracle-l