Product

Platform

Operating system

Error

Symptoms

Dialog box "Waiting for command file D:\Orant\Creo\Util\SuccessfulBackup.cmd to complete" appears every hour and the system backups to tape are not starting, or if they have started, are not completing.

Cause

Typically the backups will complete within a half hour or 45 minutes. The warning timeout can be set to a longer value if the backups regularly take more than an hour.

If the message appears after several hours, this is cause for alarm. This could mean the backup script is hung. If this is the case, subsequent database backups will not proceed until the system is rebooted or the previous backup process is killed.

There are a couple of reasons why the SuccessfulBackup.cmd script can hang:

1) If using Basic Backup, the SHUTDOWN_TO_BACKUP parameter should be set to YES. If it is set to NO, the SuccessfulBackup.cmd script will attempt to stop the Oracle services. The Araxi service is dependent upon the Oracle services, which means that Oracle will not be allowed to shut down until the Araxi service is stopped first. The SuccessfulBackup.cmd script then hangs at a prompt asking if you want to shut down the Araxi service. But since the script is run in the background, there is no way to respond to the prompt. Thus the script will stay in this state until the system is rebooted or the process is killed.

2) If using Basic, Offline, or Online Backup, the SuccessfulBackup.cmd script can hang if a tape with sufficient space is not mounted in the tape drive. If the tape fills up part way through the backup, it will wait for another tape to be mounted. If using Legato Backup, the customer can view the status of the backup using Networker Administrator. If using NT Backup, there is no interface available to check the status.

Solution

Set the Backup_Success_Command_Warning setting in OracleBackupManager to a time longer than the maximum time needed for the backups to complete. If the warning appears more than once, investigate further.

If patch 19 was recently installed, check the parameters in OracleBackupManager. If the customer is using Basic Backup, the SHUTDOWN_TO_BACKUP should be set to YES. Also check the BACKUP_DESTINATION parameter; it will also be reset after applying patch 19. It should be set to the server name if the customer is using Online backup. If using Offline Backup or Basic Backup, check which folder is being backed up, then set the BACKUP_DESTINATION to be the same folder. The folder is typically E:\ORACLEBACKUP, but it should be confirmed by checking the D:\Orant\Creo\Util\SuccessfulBackup.cmd script. If the customer is using Basic Backup, or Legato, check the SaveSet settings for the primary server client. Do this by starting Networker Administrator and editing the client settings for the primary server under “Manage Clients�.

Permanent fix:

See also

Keywords

backup, oracle

Technical contact(s)

Stan Yoshida

Submitted by

Date submitted