HP (Hewlett-Packard) B6960-96008 Garage Door Opener User Manual


 
Integrating SAP DB/MaxDB and Data Protector
Troubleshooting
Chapter 3314
Problem An SAP DB/MaxDB instance cannot be started after restore.
Action Using the SAP DB/MaxDB db_restartinfo command, check if the
instance can be restarted.
If the instance cannot be restarted, most probably the existing log
volumes do not contain enough data to restart the instance from data
volumes. The required differential or transactional backups might not
have been restored.
If the instance can be restarted, check the SAP DB/MaxDB instance
kernel error file for errors.
If there was insufficient space for SAP DB/MaxDB logs at some point
of time, logs might have been corrupted: delete the logs (using the
dbmcli util_execute clear log command) or contact
SAP DB/MaxDB or Data Protector support.
Problem A restore from an object copy hangs.
Action Before restarting the restore:
Increase the number of Disk Agent buffers for the device used for the
restore.
If all objects of the backup are recorded in the IDB, perform the
following steps:
1. In the Internal Database context of the Data Protector GUI,
search for all objects belonging to the same backup. The objects
are identified by the same backup ID.
2. Copy each object in a separate object copy session to a separate
device, for example a file library. For each object, use a separate
medium with the non-appendable media policy.
3. Set the highest media location priority for the newly created
copies.
Problem Data Protector reports the following error:
Error: SAPDB responded with:
Error! Connection failed to node (local) for database
CLUSTER:
connection refused: x_server not running.