"Could not open logfile" occurred when run "datapatch -verbose"
(Doc ID 2243580.1)
Last updated on JANUARY 11, 2022
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
"datapatch -verbose" throws the following error:
For example:
[terminal log]
Validating logfiles...
Patch 24732088 apply (pdb CDB$ROOT): WITH ERRORS
logfile:
$GRID_HOME/cfgtoollogs/sqlpatch/24732088/20933516/24732088_apply__MGMTDB_CDBROOT_20171<Month in Japanese> 25_17_27_32.log (errors)
Error at line 0: Could not open logfile
$GRID_HOME/cfgtoollogs/sqlpatch/24732088/20933516/24732088_apply__MGMTDB_CDBROOT_20171<Month in Japanese> 25_17_27_32.log
Patch 24732088 apply (pdb PDB$SEED): WITH ERRORS
logfile:
$GRID_HOME/cfgtoollogs/sqlpatch/24732088/20933516/24732088_apply__MGMTDB_PDBSEED_20171<Month in Japanese> 25_17_29_38.log (errors)
Error at line 0: Could not open logfile
$GRID_HOME/cfgtoollogs/sqlpatch/24732088/20933516/24732088_apply__MGMTDB_PDBSEED_20171<Month in Japanese> 25_17_29_38.log
[sqlpatch_catcon_0.log]
SQL><OLD> 1: SELECT '&logfiledir' || '24732088_apply_' ||
<NEW> 1: SELECT '$GRID_HOME/cfgtoollogs/sqlpatch/24732088/20933516/' ||'24732088_apply_' ||
SQLPATCH_LOGFILE
--------------------------------------------------------------------------------
$GRID_HOME/cfgtoollogs/sqlpatch/24732088/20933516/24732088_apply__MGMTDB_CDBROOT_20171<Month in Japanese> 25_17_27_32.log
SP2-0768: <Illegal SPOOL command>
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 |
| Cause |
| Solution |
| References |