| Backup | Restore |
Scheduled log backup operation fails with the following error message:
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The database was unable to fulfill a request (-123, No more log to save)
When a log backup is scheduled using a script and if the log size is very small (or negligible), then the log backup operation fails.
Use the following command to check the log size on each log backup in script. If the log size is too small, then skip the log backup.
dbmcli -d <SID> -u '<LOGIN>,<PWD>' -c info log
| Improper group association is specified during installation | The SAP for MAXDB user (sdb) should belong to the same group as
entered during the installation. Otherwise, SAP for MAXDB will not be able to
record the transactions in backint_maxdb.log and will not be able to access the
registry. For example; /etc/<>Registry. As a result, the backups will fail.
Sometimes, the backup fails due to incorrect group permissions. The following message would be logged in the <instanceName>/wrk/dbm.ebl file: Instance [<instanceName>] Machine [<machName>] does not exist. Select 'sys' group (sdb) do not belong to this group and as a result the backup fails during the Backup. Please follow the proper installation instructions to create < >group and reinstall all the < >packages on the client.Use group dba during the installation. Also, make sure to add sdb/sdba to group dba in the file /etc/group. If you need to change the < > Group as part of security administrations. Then follow the procedure given below:
|
| Failure of Backups and Restores performed from a remote desktop on windows | Currently, backups and restores cannot be performed
from a remote desktop on Windows. Use any one of the following solutions that suits your setup:
mstsc /v:winclient /console
|
| External backup tool not found error: The file '/opt/< >/SapMaxDbAgent/in' already exists. |
Execute the following commands: <instance># ./dbmcli -d TEST2 -u dbm,dbm -uUTL -c backup_start BackLog ERR -24927,ERR_TOOLCHK: external backup tool not found The file '/opt/galaxy/SapMaxDbAgent/in' already exists. <instance># rm /opt/galaxy/SapMaxDbAgent/in <instance># ./dbmcli -d TEST2 -u dbm,dbm -uUTL -c backup_start BackLog ERR -24927,ERR_TOOLCHK: external backup tool not found The file '/opt/galaxy/SapMaxDbAgent/out' already exists. <instance># rm /opt/galaxy/SapMaxDbAgent/out <instance># ./dbmcli -d TEST2 -u dbm,dbm -uUTL -c backup_start BackLog ERR -24927,ERR_TOOLCHK: external backup tool not found The file '/opt/galaxy/SapMaxDbAgent/err' already exists. <instance># rm /opt/galaxy/SapMaxDbAgent/err <instance># ./dbmcli -d TEST2 -u dbm,dbm -uUTL -c backup_start BackLog |
| External backup tool not found error: The file /Base/backint.exe is not executable. |
In this situation, the configuration of BACKINT interface is incorrect.
Configure the following parameter files to the exact location of the
backint.exe. D:\program files\sdb\programs\pgm>cat D:\MaxDB\sdb\config\backint.conf BACKINT "D:\< >\< >\Base\backint.exe" INPUT "D:\MaxDB\sdb\config\in" OUTPUT "D:\MaxDB\sdb\config\out" ERROROUTPUT "D:\MaxDB\sdb\config\err" PARAMETERFILE "D:\MaxDB\sdb\config\param" TIMEOUT_SUCCESS 300 TIMEOUT_FAILURE 300 D:\program files\sdb\programs\pgm> |
| External backup tool not found error: The file /SapMaxDbAgent/backint.conf is missing or unreadable. |
Execute the following commands: magnum-as-root> ./dbmcli -d TEST1 -u dbm,dbm -uUTL ./dbmcli on TEST1>dbm_configset -raw BSI_ENV /oracle/galaxy/SapMaxDbAgent/backint.conf OK --- ./dbmcli on TEST1>dbm_configset -raw set_variable_0 LD_LIBRARY_PATH=/oracle/galaxy/Base OK --- ./dbmcli on TEST1>dbm_configset -raw set_variable_1 SHLIB_PATH=/oracle/galaxy/Base OK --- magnum-as-root> pwd /oracle/sdb/programs/bin magnum-as-root> |