My Oracle Support Banner

DB creation errors out with 'ERROR : clone operation timed out, exceeded the time limit of 45 minutes' (Doc ID 2637182.1)

Last updated on FEBRUARY 15, 2020

Applies to:

Oracle Database Exadata Cloud Machine - Version N/A to N/A
Information in this document applies to any platform.

Symptoms

DB creation fails.

ocde log file generated for the creations shows the failure during prep phase.

INFO : Running clone.pl
ERROR : clone.pl failed : 25
2020-02-07 09:17:33.181050 - cmd took 2776.91561102867 seconds
2020-02-07 09:17:33.182045 - WARN : non-zero status returned
 Command: /var/opt/oracle/ocde/assistants/prep/prep -out /var/opt/oracle/ocde/res/prep.out -bp="default" -bp_update="no" -nid="yes" -dbname="ocdb999x" -grid
_version="18000" -dbtype="rac" -timeout="60" -grid_dbname="+ASM" -psu="default" -acfs_vol_dir="/var/opt/oracle/dbaas_acfs" -lsnr_port="1521" -grid_sid="+ASM1
" -version="12201" -asm="false" -grid_home="/u01/app/18.1.0.0/grid" -action="config" -action=config
 Exit: 255
 Excerpt:
 Starting PREP
 Logfile is /var/opt/oracle/log/ocdb999x/prep/prep_2020-02-07_08:31:16.735526244439.log
 Config file is /var/opt/oracle/ocde/assistants/prep/prep.cfg
 (...)
 Use of uninitialized value $oh in concatenation (.) or string at /var/opt/oracle/ocde/assistants/prep/../../../perl_lib/DBAAS/dbcore.pm line 577.
 INFO : Running clone.pl
 ERROR : clone.pl failed : 25
2020-02-07 09:17:33.182842 - ERROR : Assistant prep has failed, please check logs under /var/opt/oracle/log/ocdb999x

 

Prep logs show timeout waiting for success message from node 2 during clone operation.

INFO : checking log for cc02202vm02, /var/opt/oracle/log/ocdb999x/clone/clone-cmdbg_2020-02-07_08:31:22.533060244589_244589_2020-02-07_08:31:28.254397.log for success message
ERROR : clone there was an error running clone.pl across nodes, please contact support
ERROR : clone operation timed out, exceeded the time limit of 45 minutes
ERROR : clone there was an error running clone.pl across nodes, please contact support

 

Clone logs under /u01/app/oraInventory/logs on node 2 shows failure during inventory read.

INFO: 2/7/20 8:33:30 AM MST: Unable to read inventory information for the home: null.

 

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


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