Datapatch fails with "Can't use string ("Could not open logfile ..."...) as a HASH ref while "strict refs" in use at $ORACLE_HOME/sqlpatch/sqlpatch.pm line 7231."
(Doc ID 2700005.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 18.10.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Datapatch is failing with below error:
cd $ORACLE_HOME/OPatch
./datapatch -verbose
SQL Patching tool version 18.0.0.0.0 Production on Sun Jul 19 17:17:55 2020
Copyright (c) 2012, 2020, Oracle. All rights reserved.
Log file for this invocation: /app/oracle/cfgtoollogs/sqlpatch/sqlpatch_9279_2020_07_19_17_17_55/sqlpatch_invocation.log
Connecting to database...OK
Gathering database info...done
Bootstrapping registry and package to current versions...done
Can't use string ("Could not open logfile /app/orac"...) as a HASH ref while "strict refs" in use at /app/oracle/product/18.3/sqlpatch/sqlpatch.pm line 7231.
Please refer to MOS Note 1609718.1 and/or the invocation log
/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_9279_2020_07_19_17_17_55/sqlpatch_invocation.log
for information on how to resolve the above errors.
SQL Patching tool complete on Sun Jul 19 17:18:57 2020
Changes
Applied new patch to the Oracle Home and executing 'datapatch -verbose' to perform post-install patching actions
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 |
Changes |
Cause |
Solution |