Skip to main content
Delphix

Oracle VDB provision/refresh fails with "change-archivelog-mode.sh "NOARCHIVELOG"" timed out after 300000 ms" (KBA7914)

 

KBA

KBA# 7914

 

Issue

When provisioning or refreshing an Oracle VDB with the Enable Archivelog Mode deselected, another script executes at then end of the provision called change-archivelog-mode.sh this can fail with a timeout as seen in this failure:

message_command_output | command: umask 027; . $DB_SCRIPT_DIR/setup-oraenv.sh; $DLPX_SHELL -x $DB_SCRIPT_DIR/change-archivelog-mode.sh "NOARCHIVELOG"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | error:"umask 027; . $DB_SCRIPT_DIR/setup-oraenv.sh; $DLPX_SHELL -x $DB_SCRIPT_DIR/change-archivelog-mode.sh "NOARCHIVELOG"" timed out after 300000 ms. Output: END_OF_SETUP

Prerequisites

The option Enable Archivelog Mode must be deselected in order for this extra script to be run.

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases
6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0

5.3

5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0

5.2

5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1

5.1

5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0

5.0

5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

Resolution

This script change-archivelog-mode.sh attempts to do the following operations within the default timeout of 5 minutes (300 seconds).

change_archivelog_mode_output=`sqlplus -S "$LOGON_STR" 2>&1 <<-EOF
 $SQLPLUS_DDL_MODIFIERS
 shutdown abort;
 startup open restrict;
 shutdown immediate;
 startup mount;
 alter database $1;
 exit;
EOF`


open_database_output=`sqlplus -S "$LOGON_STR" 2>&1 <<-EOF
 $SQLPLUS_DDL_MODIFIERS
 alter database open;
 exit;
EOF`

If these steps take longer than the 5 minutes then the error is reported:

| error:"umask 027; . $DB_SCRIPT_DIR/setup-oraenv.sh; $DLPX_SHELL -x $DB_SCRIPT_DIR/change-archivelog-mode.sh "NOARCHIVELOG"" timed out after 300000 ms. Output: END_OF_SETUP

To check on the progress of the steps review the Oracle Alert log to see how far along the process was when the 5 minutes window closed. This information can be used as a guide when choosing an appropriate value to increase the timeout to, avoiding the failure in the future. 

To set the new timeout value and also update the delphix_config_override.properties file with the changed timeout value.

On the Delphix engine run the command:

/opt/delphix/server/bin/jmxtool tunable set oracle.vdb.script_default_timeout <seconds> true

Troubleshooting

When checking the Oracle alert log for the steps run by the script, review this example of the key operations on a failing run:

Tue Jun 29 14:35:18 2021
Shutting down instance (abort)

Tue Jun 29 14:35:20 2021
Instance shutdown complete

Tue Jun 29 14:35:20 2021
Starting ORACLE instance (restrict)

Tue Jun 29 14:37:01 2021
Completed: ALTER DATABASE OPEN

Shutting down instance (immediate)
Tue Jun 29 14:37:01 2021

Tue Jun 29 14:37:54 2021
Starting ORACLE instance (normal)

Tue Jun 29 14:38:09 2021
ALTER DATABASE   MOUNT

Completed: ALTER DATABASE   MOUNT
Tue Jun 29 14:38:14 2021

Tue Jun 29 14:38:14 2021
alter database NOARCHIVELOG

Tue Jun 29 14:38:14 2021
alter database NOARCHIVELOG

Tue Jun 29 14:39:10 2021
alter database open

Completed: alter database open
Tue Jun 29 14:40:20 2021

In this example, it took 5 minutes 2 seconds to complete the steps, so the timeout was exceeded.

 

 


Related Articles

The following articles may provide more information or related information to this article:

  • link
  • link
  • link