Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

post-installation step (datapatch -verbose) fails for PSU 25115951

Dear DBA FrankMar 7 2017 — edited Aug 3 2017

Hello

I've got to install PSU 25115951 on several 12.1.0.2 ORACLE_HOMES. That PSU must be installed in 2 steps (step 1: the usual opatch apply,  step 2: datapatch -verbose, which runs some SQL code on all open PDBs).  For my first ORACLE_HOME, both steps went fine.  For my 2nd ORACLE_HOME, which is in an identical environment, step 1 went fine but step 2 fails with:

SQL Patching tool version 12.1.0.2.0 Production on Tue Mar  7 11:15:14 2017

Copyright (c) 2012, 2017, Oracle.  All rights reserved.

Log file for this invocation: C:\app\oracle\cfgtoollogs\sqlpatch\sqlpatch_948_2017_03_07_11_15_14\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

Determining current state...done

Current state of SQL patches:

Bundle series PSU:

  ID 170117 in the binary registry and ID 170117 with errors in PDB CDB$ROOT, ID 170117 with errors in PDB PDB$SEED, ID 170117 with errors in PDB MYPDB

Adding patches to installation queue and performing prereq checks...

Installation queue:

For the following PDBs: CDB$ROOT PDB$SEED MYPDB

    Nothing to roll back

    The following patches will be applied:

      25115951 (WINDOWS DB BUNDLE PATCH 12.1.0.2.170117(64bit):25115951)

Installing patches...

Patch installation complete.  Total patches installed: 3

Validating logfiles...

Patch 25115951 apply (pdb CDB$ROOT): WITH ERRORS

  logfile: C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006/25115951_apply_CDBHOOVE_CDBROOT_2017Mars 07_11_15_57.log (errors)

    Error at line 0: Could not open logfile C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006/25115951_apply_CDBHOOVE_CDBROOT_2017Mars 07_11_15_57.log

Patch 25115951 apply (pdb PDB$SEED): WITH ERRORS

  logfile: C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006/25115951_apply_CDBHOOVE_PDBSEED_2017Mars 07_11_16_18.log (errors)

    Error at line 0: Could not open logfile C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006/25115951_apply_CDBHOOVE_PDBSEED_2017Mars 07_11_16_18.log

Patch 25115951 apply (pdb MYPDB): WITH ERRORS

  logfile: C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006/25115951_apply_CDBHOOVE_MYPDB_2017Mars 07_11_16_18.log (errors)

    Error at line 0: Could not open logfile C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006/25115951_apply_CDBHOOVE_MYPDB_2017Mars 07_11_16_18.log

Please refer to MOS Note 1609718.1 and/or the invocation log

C:\app\oracle\cfgtoollogs\sqlpatch\sqlpatch_948_2017_03_07_11_15_14\sqlpatch_invocation.log

for information on how to resolve the above errors.

So I ran this SELECT:

07-03 11:48  SYS AS SYSDBA> select patch_id,  status, bundle_id from dba_registry_sqlpatch;

  PATCH_ID STATUS           BUNDLE_ID

---------- --------------- ----------

  25115951 WITH ERRORS         170117

  25115951 WITH ERRORS         170117

  25115951 WITH ERRORS         170117

  25115951 WITH ERRORS         170117

And that SELECT:

07-03 11:52  SYS AS SYSDBA>  select cause,status,message from PDB_PLUG_IN_VIOLATIONS where status !='RESOLVED' order by name,cause;

CAUSE              STATUS

------------------ ---------

MESSAGE

----------------------------------------------------------------------------------------------------------------------------------

SQL patch error    PENDING

PSU bundle patch 170117 (WINDOWS DB BUNDLE PATCH 12.1.0.2.170117(64bit):25115951): APPLY with status WITH ERRORS in the CDB.

SQL patch error    PENDING

PSU bundle patch 170117 (WINDOWS DB BUNDLE PATCH 12.1.0.2.170117(64bit):25115951): APPLY with status WITH ERRORS in the PDB.

SQL patch error    PENDING

PSU bundle patch 170117 (WINDOWS DB BUNDLE PATCH 12.1.0.2.170117(64bit):25115951): APPLY with status WITH ERRORS in the CDB.

SQL patch error    PENDING

PSU bundle patch 170117 (WINDOWS DB BUNDLE PATCH 12.1.0.2.170117(64bit):25115951): APPLY with status WITH ERRORS in the PDB.

opatch lsinventory does list the 25115951 patch.  I did go to MOS note 1609718.1 but it's a generic list of potential problems that can be encountered while runnning datapatch.  My problem is not in the list.

The symptoms I found are:

  1. the "WITH ERRORS" results of the above 2 SELECTs
  2. the " C:\app\oracle\cfgtoollogs\sqlpatch\25115951\20996006" folder is empty (while in my 1st ORACLE_HOME, it contains the above-mentioned 3 logs)

These are the results of my 3rd attempt: after first facing that issue, I rolled back the PSU, re-applied it but no soap.  Then I re-booted the machine, rolled back the PSU, re-applied it but to no avail.

I scoured over all the logs generated by the application of PSU 25115951 but did not see anything suspicious.  Did anyone run into the same issue?  Can anyone help please?

This post has been answered by Jerry_61 on Apr 26 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 31 2017
Added on Mar 7 2017
6 comments
5,993 views