OEM13C : Fleet: Windows UPDATE_DB Fails Job Step "In Shutdown Database Instance from source Oracle home" With Error "Could not open file to write SQL command output"
(Doc ID 3010491.1)
Last updated on MAY 06, 2024
Applies to:
Enterprise Manager for Oracle Database - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Enterprise Manger (EM) Cloud Control, when UDPATE_DB command fails with below error.
$ emcli db_software_maintenance -performOperation -name="update -purpose=UPDATE_DB -target_type=oracle_database -target_list="<target_name>" -normal_credential="ORACLESHOST:SYSMAN"
-windows_sec_credential="SEC:SYSMAN"
Job Step Log:
Final command line to execute is %PERL_HOME%\perl "C:\Users\JOB_1053C6BAC9FE1F39E063702016AC2419\stopDBInstance.pl" -debug false -oh C:\app\oracle\product\19.0.0.0\DB -os DBNAME -shutdowndbsids -shutdowndbcontrol -shutdownisqlplus -tns_admin C:\App\Oracle\product\19.21.0.0\DB\network\admin,C:\app\oracle\product\19.0.0.0\DB\network\admin ${from_rac} -parallel false ${from_asm} -home_version 19.0.0.0.0 -primaryDBSids -physicalStdySids -normal true -agent_db_plugin_home C:\App\Oracle\product\OEM\agent_13.5.0.0.0/plugins/oracle.sysman.db.agent.plugin_13.5.1.0.0 -cloneOraHome C:\App\Oracle\product\19.21.0.0\DB -switchbackMode -db_tns_admin C:\app\oracle\product\19.0.0.0\DB\network\admin -stopManagedRecovery -IS_CDB false -workDir C:\Users\AppData\Local\Temp\4864848623487998\1706797568809
Running: C:\Users\AppData\Local\Temp\JOB_1053C6BAC9FE1F39E063702016AC2419\stopDBInstance.pl
Argument count: 33
Perl version: 5.032000
Hostname: ORATEST18
Operating system: MSWin32
Time: Thu Feb 1 08:26:43 2024
Thu Feb 1 08:26:43 2024 - Cloned Oracle Home:C:\App\Oracle\product\19.21.0.0\DB
Thu Feb 1 08:26:43 2024 - IS_CDB is :false
Thu Feb 1 08:26:43 2024 - Working Dir is :C:\Users\AppData\Local\Temp\4864848623487998\1706797568809
Thu Feb 1 08:26:43 2024 - DB Version is 11.2 or above.
Thu Feb 1 08:26:43 2024 - Getting Local Listener Name on Windows....
---------- Error Message ----------
Error: 007
Could not open file to write SQL command output
----------- End Message -----------
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 |