Fleet : Support For Parallel Shutdown Of Database Instances During UPDATE_GI
(Doc ID 3006872.1)
Last updated on APRIL 23, 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 Manager Cloud Control using Fleet Maintenance, During UPDATE_GI we patch node by node and when we first start patching node, first bring down the databases instance running on the node one by one serially which takes an hour in case of more databases instances.
$ emcli db_software_maintenance -performOperation -name="Update DB" -purpose=UPDATE_DB -target_type=oracle_database -target_list="<target_name>" -normal_credential="ORACLE:SYSMAN" -privilege_credential="ROOT:SYSMAN"
Old Job Step Log :
Invoking "/tmp/191184172449925/191184394882385/stop_database_home_script" as user "oracle"
Executing cmd: /bin/su oracle -c "/tmp/191184172449925/191184394882385/stop_database_home_script"
Stopped database instance $db_inst[1] using user [oracle].
|____________________ FUNCTION CALL END gridupdate::stop_database_home_new |___________________|
Oracle home [/haclu/64bit/app/oracle/product/12.1.0] stopped successfully
cat stop_database_home_script
ORACLE_HOME=/haclu/64bit/app/oracle/product/12.2.0
export ORACLE_HOME
/haclu/64bit/app/oracle/product/12.2.0/bin/srvctl stop instance -d $db_inst -i $db_inst[1] -failover -force
New Job Step Log :
Invoking "/tmp/191184172449925/191184394882385/stop_database_home_script" as user "oracle"
Executing cmd: /bin/su oracle -c "/tmp/191184172449925/191184394882385/stop_database_on_node_script"
Stopped all the database instances on this node.
Action [STOP] completed on this node
|____________________ FUNCTION CALL END gridupdate::stop_database_home_new |___________________|
Oracle home [/haclu/64bit/app/oracle/product/12.1.0] stopped successfully
cat stop_database_on_node_script
ORACLE_HOME=/haclu/64bit/app/oracle/product/12.2.0
export ORACLE_HOME
/haclu/64bit/app/oracle/product/12.2.0/bin/srvctl stop instance -n $NODE -drain_timeout 0 -force
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 |