My Oracle Support Banner

EM 13c : Fleet UPDATE_GI Procedure Is Not Honoring "dispatchLoc" Parameter Passed Instead It Picks Default /tmp Directory (Doc ID 2659415.1)

Last updated on SEPTEMBER 01, 2021

Applies to:

Enterprise Manager for Oracle Database - Version 13.3.1.0.0 and later
Information in this document applies to any platform.

Symptoms

 In Enterprise Manager (EM) Cloud Control, Fleet Update GI procedure is not honoring "dispatchLoc" parameter passed instead it picks default /tmp directory

$ emcli db_software_maintenance -performOperation -name="Update GI" -purpose=UPDATE_GI -target_type=oracle_database -target_list="<cluster_name>" -normal_credential="ORACLE:SYSMAN" -privilege_credential="ROOT:SYSMAN" -input_file="data:/tmp/update.txt"

Job Name: SHIP_GENERIC_PERL_MODULE_9BA7790B3045469AE0533453F10ACEB5
Step Name: SS_RemoteOp
Step Status: Failed
Start Time: 08/01/2020 20:28:39
End Time: 08/01/2020 20:28:39
Job OutPut:
Commmnd name is
/tmp//GIUPGRADE-1578515296465/rootScripts/dbprov/dispatcher.pl
Second argument is transferCommonModule
second last args is transferCommonModule "NA"
"/emagent/gcagent/agent_13.4.0.0.0"[4-1]
Command Name is:
/tmp//GIUPGRADE-1578515296465/rootScripts/dbprov/dispatcher.pl
Directory is /tmp
Command Name:
/tmp//GIUPGRADE-1578515296465/rootScripts/dbprov/dispatcher.pl
OS Name: Linux
MD5 Present

Changes

 

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
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.