on 06-04-2009 5:59 PM
Hallo,<br>
<br>
I try to recover a Database with the HP Data Protector Plug-in. I had made a Full-Backup and a Trans-Backup. These sessions were terminated successfully. <br><br><br>
<br>
After that i had deleted the Data volume and the Log volume of the database and rebooted the Server. Now I want recover the Database.<br><br><br>
<br>
Following actions are done by Data Protector:<br><br>
Executing the dbmcli command: `user_logon'.<br>
Executing the dbmcli command: `dbm_configset -raw BSI_ENV /var/opt/omni/tmp/DEMODB.bsi_env'.<br>
Executing the dbmcli command: `db_admin'.<br>
Executing the dbmcli command: `dbm_configset -raw set_variable_10 OB2BACKUPAPPNAME=DEMODB'.<br>
Executing the dbmcli command: `dbm_configset -raw set_variable_11 OB2BACKUPHOSTNAME=n4shost.sapdb.local'.<br>
Executing the dbmcli command: `util_connect'.<br>
Restoring backup 2009/06/04 0020.<br>
Executing the dbmcli command: `medium_put BACKDP-Data[1]/1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1 PIPE DATA 0 8 NO NO \"\" BACK'.<br>
Executing the dbmcli command: `recover_start BACKDP-Data[1] DATA ExternalBackupID "DEMODB 09060420:1 Stream"'.<br>
<br>
STARTING Media Agent "LTO_drive2"<br>
<br>
Starting OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Completed OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Restoring backup 2009/06/04 0021.<br>
<br>
Executing the dbmcli command: `medium_put BACKDP-Archive/1 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1 PIPE LOG 0 8 NO NO \"\" BACK'.<br>
<br>
Executing the dbmcli command: `db_state'.<br>
<br>
Executing the dbmcli command: `recover_start BACKDP-Archive LOG ExternalBackupID "DEMODB 09060421:1 Stream"'.<br>
<br>
Starting OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Completed OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Executing the dbmcli command: `db_state'.<br>
<br>
Executing the dbmcli command: `recover_start BACKDP-Archive LOG ExternalBackupID "DEMODB 09060421:2 Stream"'.<br>
<br>
Error: SAPDB responded with: -24920,ERR_BACKUPOP: backup operation was unsuccessful<br>
The database was unable to fulfill a request (-1, ).<br>
.<br>
<br>
Executing the dbmcli command: `exit'.
<br>
<br>
<br>
The recovery of the last Full-Backup is successful. But the logfiles not.<br>
<br>
First time I get this error in the Kernel log:<br>
2009-06-04 17:25:57 35 ERR 11000 d0_vatta Cannot open volume, No such file or directory <br>
2009-06-04 17:25:57 35 ERR 11000 d0_vatta Volume name 'DISKL0001'
<br>
(DISKL001 is my Database Log file)<br>
I had generated a new Log-File with db_activate.<br>
<br>
Now I get:<br>
2009-06-04 17:50:09 24 ERR 51080 SYSERROR -9407 unexpected error<br>
2009-06-04 17:50:09 24 ERR 3 Admin Kernel_Administration.cpp:606<br>
2009-06-04 17:50:09 24 ERR 3 Admin 2009-06-04 17:50:09 Admin Error 3<br>
2009-06-04 17:50:09 24 ERR 3 Admin Database state: OFFLINE<br>
2009-06-04 17:50:09 24 ERR 3 Admin + Log_Volume.cpp:342<br>
2009-06-04 17:50:09 24 ERR 3 Admin + 2009-06-04 17:50:09 Log Error 20040<br>
2009-06-04 17:50:09 24 ERR 3 Admin - Logrecovery is not allowed, because state of log volume is 'HistoryLost' (log must be cleared)<br>
2009-06-04 17:50:09 24 ERR 3 Admin + Log_Volume.cpp:343<br>
2009-06-04 17:50:09 24 ERR 3 Admin + 2009-06-04 17:50:09 Log Info 8<br>
2009-06-04 17:50:09 24 ERR 3 Admin - Log- and Data are not compatible because 'Restore Log with Log State 'HistoryLost' is not allowed'.<br>
2009-06-04 17:50:09 24 ERR 3 Admin + Kernel_Administration.cpp:762<br>
2009-06-04 17:50:09 24 ERR 3 Admin + 2009-06-04 17:50:09 Admin Warning 20025<br>
2009-06-04 17:50:09 24 ERR 3 Admin - Initialization of log for 'restore log' failed with 'LogAndDataIncompatible'<br>
2009-06-04 17:50:11 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)<br>
2009-06-04 17:50:11 ___ Stopping GMT 2009-06-04 15:50:11 7.6.00 Build 018-123-119-055
<br>
<br>
How can I clear the History Log. I had try rename the dbm.knl file. Now the Backup history in the dbmcli is empty. But the error is still there.<br>
<br>
Can anyone help me to fix this issue?<br>
<br>
Thanks to everyone!<br>
Edited by: Timm Letzel on Jun 4, 2009 6:59 PM
Hello Timm,
we have the same Problem On a Windows 2003 64bit system. We can recover the last full backup but not the logs. How did you solved the Problem?
Regads,
Jahan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello All,
2 weeks ago i was able to recover a full and 2 trans (log) making log and data area compatibles, the problem is i got time to capture a screen and the log of the restore session but by the time i wanted to take a screenshot of the config and data, etc settings i used (since i did a LOT of trial and error tests) power went out and when i restarted the cell manager server and entered DP i couldn't see the content of the session, and since then i was not able to duplicate any succesful restore.
Cell Manager is running on Red Hat x64, DP is 6.1, SAP ECC 6.0 SPS 15 & MaxDB 6.06.06 running on RHEL Enterprise Server 5.4 IA64 HP Rx2660 servers.
How can i paste the DP log here without looking like a big letters mess?
Obviously i changed the computer name for security reasons.
Best Regards,
Martim Mendes
Edited by: Martim Mendes on Oct 14, 2009 3:54 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow:
This is a official Statement of HP from their MaxDB Whitepaper (Zero Downtime Backup of MaxDB database with HP Data Protector 😞
Supported systems
The MaxDB ZDB solution presented in this document has been tested on a combination of MaxDB 7.6 and Data Protector 6.1 on Windows 2003 32 bit OS in conjunction with EVA snapshot functionality. This combination is supported.
The MaxDB ZDB solution may also work on other operating systems, like HP-UX and Linux variants. However, these combinations have not been tested, and therefore, not supported.
I will try the recovery using a Windows operating System!
Regards
Timm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I have tested it with Windows OS and MaxDB 7.6 and it works!!!!!.
On Linux I used the last version of MaxDB (7.7).
With the Linux-Environment DP execute this sequence of commands (wrong):
recover_start ...
recover_start ...
recover_start ...
With Windows DP execute this (right):
recover_start ...
recover_replace ...
recover_replace ...
- Is there a Bug in the backint or in other components of DP or MaxDB?
- Does anyone know if I am able to customize the sequence that is run by DP 6.1?
- Any other idea how to fix this?
Please help me!
Thanks
Timm
Edited by: Timm Letzel on Oct 2, 2009 9:52 AM
> I have tested it with Windows OS and MaxDB 7.6 and it works!!!!!.
> On Linux I used the last version of MaxDB (7.7).
>
> With the Linux-Environment DP execute this sequence of commands (wrong):
>
recover_start ...
> recover_start ...
> recover_start ...
>
> With Windows DP execute this (right):
>
recover_start ...
> recover_replace ...
> recover_replace ...
>
> - Is there a Bug in the backint or in other components of DP or MaxDB?
Well, BACKINT is just a interface definition and it is called after a recover_* command.
MaxDB does not issue the recover_* commands - instead it just tries to execute the commands given by the tool you're using to trigger the recovery.
This tool seems to be data protector - so I'd say: this is a bug of DP.
> - Does anyone know if I am able to customize the sequence that is run by DP 6.1?
How about asking the DP support about this?
> - Any other idea how to fix this?
Apart from not using DP to issue the recover statements?
Nope.
Why don't you just use DBMGUI/DB Studio to run your recoveries?
regards,
Lars
Hello,
after a long time I remembered my Problem and began to trying solve the Problem again. I think that I have located the error while I configured Logfileshipping between two MaxDB Instances.
The DataProtector runs following sequence of commands:
user_logon
dbm_configset -raw BSI_ENV /var/opt/omni/tmp/DEMODB.bsi_env
db_admin
util_execute clear log
dbm_configset -raw set_variable_10 OB2BACKUPAPPNAME=DEMODB
dbm_configset -raw set_variable_11 OB2BACKUPHOSTNAME=n4shost.sapdb.local
util_connect
medium_put BACKDP-Data[1]/1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1 PIPE DATA 0 8 NO NO \"\" BACK
recover_start BACKDP-Data[1] DATA ExternalBackupID "DEMODB 09091516:1 Stream"
medium_put BACKDP-Archive/1 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1 PIPE LOG 0 8 NO NO \"\" BACK
db_state
recover_start BACKDP-Archive LOG ExternalBackupID "DEMODB 09091518:1 Stream"
db_state
recover_start BACKDP-Archive LOG ExternalBackupID "DEMODB 09091518:2 Stream"
Error: SAPDB responded with: -24924,ERR_DBREQ: cannot start database kernel request
-24994,ERR_RTE: Runtime environment error
1,wrong connection state:requested
exit
In the log I see the error:
The LogIOSequencenumber of the savepoint (338408) is not in the range from the backup \[338409,357627\]
The same error occurred while I manually recovered the instance. The Sequence:
recover_start ...
recover_start ...
recover_start ...
doesnu2019t work. The right one is:
recover_start ...
recover_replace...
recover_replace ...
but how do I say that the DataProtector?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,<br>
<br>
it seems, that the MaxDB dbm does not communicate with the DP Cell Manager. Because all db_activate restore sessions, that I had started doesn't abear in the Dataprotector.<br>
<br>
In the knldiag are following messages after the failed recovery:<br>
2009-06-09 15:52:00 10 11561 COMMUNIC Connecting T167 local 2742<br>
2009-06-09 15:52:00 24 11561 COMMUNIC Connected T167 local 2742<br>
2009-06-09 15:52:00 24 11509 COMMUNIC Connection broken by appl state 10 T167<br>
2009-06-09 15:52:00 24 WNG 11824 COMMUNIC Releasing T167 connection aborted<br>
2009-06-09 15:52:00 24 12929 TASKING Task T167 started<br>
2009-06-09 15:52:00 24 11007 COMMUNIC wait for connection T167<br>
2009-06-09 15:52:04 10 11561 COMMUNIC Connecting T159 local 2742<br>
2009-06-09 15:52:04 24 11561 COMMUNIC Connected T159 local 2742<br>
2009-06-09 15:52:04 24 11509 COMMUNIC Connection broken by appl state 10 T159<br>
2009-06-09 15:52:04 24 WNG 11824 COMMUNIC Releasing T159 connection aborted<br>
2009-06-09 15:52:04 24 12929 TASKING Task T159 started<br>
2009-06-09 15:52:04 24 11007 COMMUNIC wait for connection T159<br>
2009-06-09 15:52:08 10 11561 COMMUNIC Connecting T160 local 2742<br>
2009-06-09 15:52:08 24 11561 COMMUNIC Connected T160 local 2742<br>
2009-06-09 15:52:08 24 11509 COMMUNIC Connection broken by appl state 10 T160<br>
2009-06-09 15:52:08 24 WNG 11824 COMMUNIC Releasing T160 connection aborted<br>
2009-06-09 15:52:09 24 12929 TASKING Task T160 started<br>
2009-06-09 15:52:09 24 11007 COMMUNIC wait for connection T160<br>
2009-06-09 15:52:13 10 11561 COMMUNIC Connecting T161 local 2742<br>
2009-06-09 15:52:13 24 11561 COMMUNIC Connected T161 local 2742<br>
2009-06-09 15:52:13 24 11509 COMMUNIC Connection broken by appl state 10 T161<br>
2009-06-09 15:52:13 24 WNG 11824 COMMUNIC Releasing T161 connection aborted<br>
2009-06-09 15:52:13 24 12929 TASKING Task T161 started<br>
2009-06-09 15:52:13 24 11007 COMMUNIC wait for connection T161<br>
2009-06-09 15:52:18 10 11561 COMMUNIC Connecting T162 local 2742<br>
2009-06-09 15:52:18 24 11561 COMMUNIC Connected T162 local 2742<br>
2009-06-09 15:52:18 24 11509 COMMUNIC Connection broken by appl state 10 T162<br>
2009-06-09 15:52:18 24 WNG 11824 COMMUNIC Releasing T162 connection aborted<br>
2009-06-09 15:52:18 24 12929 TASKING Task T162 started<br>
2009-06-09 15:52:18 24 11007 COMMUNIC wait for connection T162<br>
2009-06-09 15:52:22 10 11577 COMMUNIC Cancel request for T165<br>
2009-06-09 15:52:22 76 ERR 11000 d0_aopen Cannot open device, task canceled <br>
2009-06-09 15:52:22 21 11000 vasynope '/var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1' T72 failed<br>
2009-06-09 15:52:22 21 WNG 52108 SAVE cancelled by user<br>
2009-06-09 15:52:22 24 11000 vasynclo 'DISKD0001' devno 68 T165<br>
2009-06-09 15:52:22 11 12822 TASKING Thread 75 joining<br>
2009-06-09 15:52:22 24 11000 vdetach 'DISKD0001' devno 1 T165<br>
2009-06-09 15:52:22 75 11566 stop DEVi stopped<br>
2009-06-09 15:52:22 11 12822 TASKING Thread 73 joining<br>
2009-06-09 15:52:22 73 11566 stop DEVi stopped<br>
2009-06-09 15:52:22 11 12822 TASKING Thread 74 joining<br>
2009-06-09 15:52:22 24 ERR 52012 RESTORE error occured, basis_err 3700<br>
2009-06-09 15:52:22 24 17 SrvTasks Servertask Info: because Error in backup task occured<br>
2009-06-09 15:52:22 24 17 SrvTasks + 2009-06-09 15:52:22 SrvTasks Info 10<br>
2009-06-09 15:52:22 24 17 SrvTasks - Job 1 (Backup / Restore Medium Task) [executing] WaitingT165 Result=3700<br>
2009-06-09 15:52:22 24 17 SrvTasks + 2009-06-09 15:52:22 KernelCommon Info 6<br>
2009-06-09 15:52:22 24 17 SrvTasks - Error in backup task occured, Errorcode 3700 "hostfile_error"<br>
2009-06-09 15:52:22 74 11566 stop DEVi stopped<br>
2009-06-09 15:52:22 76 11566 stop DEVi stopped<br>
2009-06-09 15:52:45 24 11509 COMMUNIC Connection broken by appl state 10 T165<br>
2009-06-09 15:52:45 24 WNG 11824 COMMUNIC Releasing T165 connection aborted<br>
2009-06-09 15:52:47 24 12929 TASKING Task T165 started<br>
2009-06-09 15:52:47 24 11007 COMMUNIC wait for connection T165
<br>
<br>
I try to start the Recovery using the dbmcli and the dbmgui. But the error is always the same.<br>
<br>
<br>
<br>
Here is the Log from the External Backup Session:<br>
------------------ Start of a new external backup tool action ------------------<br>
<br>
2009-06-09 15:58:09<br>
Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.<br>
Using environment variable 'TMP' with value '' as directory for temporary files and pipes.<br>
Using connection to Backint for MaxDB Interface.<br>
<br>
2009-06-09 15:58:09<br>
Checking existence and configuration of Backint for MaxDB.<br>
Using configuration variable 'BSI_ENV' = '/var/opt/omni/tmp/DEMODB.bsi_env' as path of the configuration file of Backint for MaxDB.<br>
Reading the Backint for MaxDB configuration file '/var/opt/omni/tmp/DEMODB.bsi_env'.<br>
Found keyword 'BACKINT' with value '/opt/omni/lbin/sapdb_backint'.<br>
Found keyword 'INPUT' with value '/var/opt/omni/tmp/DEMODB.bsi_in'.<br>
Found keyword 'OUTPUT' with value '/var/opt/omni/tmp/DEMODB.bsi_out'.<br>
Found keyword 'ERROROUTPUT' with value '/var/opt/omni/tmp/DEMODB.bsi_err'.<br>
Found keyword 'PARAMETERFILE' with value 'SAPDB.589.1244551441.par'.<br>
Found keyword 'TIMEOUT_SUCCESS' with value '900'.<br>
Found keyword 'TIMEOUT_FAILURE' with value '30'.<br>
Finished reading of the Backint for MaxDB configuration file.<br>
<br>
Using '/opt/omni/lbin/sapdb_backint' as Backint for MaxDB program.<br>
Using '/var/opt/omni/tmp/DEMODB.bsi_in' as input file for Backint for MaxDB.<br>
Using '/var/opt/omni/tmp/DEMODB.bsi_out' as output file for Backint for MaxDB.<br>
Using '/var/opt/omni/tmp/DEMODB.bsi_err' as error output file for Backint for MaxDB.<br>
Using 'SAPDB.589.1244551441.par' as parameter file for Backint for MaxDB.<br>
Using '900' seconds as timeout for Backint for MaxDB in the case of success.<br>
Using '30' seconds as timeout for Backint for MaxDB in the case of failure.<br>
Using '/sapdb/data/wrk/DEMODB/dbm.knl' as backup history of a database to migrate.<br>
Using '/sapdb/data/wrk/DEMODB/dbm.ebf' as external backup history of a database to migrate.<br>
Check passed successful.<br>
<br>
2009-06-09 15:58:09<br>
Checking medium.<br>
Check passed successfully.<br>
<br>
2009-06-09 15:58:09<br>
Preparing restore.<br>
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.<br>
Setting environment variable 'BI_REQUEST' to value 'NEW'.<br>
Setting environment variable 'BI_BACKUP' to value 'FULL'.<br>
Got the following list of external backup ID's:<br>
"DEMODB 09060937:1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1"<br>
<br>
Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u DEMODB -f restore -t file -p SAPDB.589.1244551441.par -i /var/opt/omni/tmp/DEMODB.bsi_in -c'.<br>
Created temporary file '/var/opt/omni/tmp/DEMODB.bsi_out' as output for Backint for MaxDB.<br>
Created temporary file '/var/opt/omni/tmp/DEMODB.bsi_err' as error output for Backint for MaxDB.<br>
Writing '09060937:1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1' to the input file.<br>
Prepare passed successfully.<br>
<br>
2009-06-09 15:58:09<br>
Creating pipes for data transfer.<br>
Creating pipe '/var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1' ... Done.<br>
All data transfer pipes have been created.<br>
<br>
2009-06-09 15:58:09<br>
Starting database action for the restore.<br>
Requesting 'CREATE INSTANCE WITH RESTORE DATA FROM '/var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1' PIPE BLOCKSIZE 8 MEDIANAME 'BACKDP-Data[1]'' from db-kernel.<br>
The database is working on the request.<br>
<br>
2009-06-09 15:58:09<br>
Waiting until database has prepared the restore.<br>
Asking for state of database.<br>
2009-06-09 15:58:10 Database is still preparing the restore.<br>
Waiting 1 second ... Done.<br>
Asking for state of database.<br>
2009-06-09 15:58:11 Database is still preparing the restore.<br>
2009-06-09 15:58:11 The database has finished work on the request.<br>
Receiving a reply from the database kernel.<br>
Got the following reply from db-kernel:<br>
SQL-Code :-903<br>
Database has already finished the request.<br>
<br>
2009-06-09 15:58:11<br>
Waiting for end of the restore operation.<br>
2009-06-09 15:58:11 The backup tool is not running.<br>
The restore operation has ended.<br>
<br>
2009-06-09 15:58:11<br>
Filling reply buffer.<br>
Have encountered error -24920:<br>
The database was unable to fulfill a request (-903, Host file I/O error,No more devices).<br>
<br>
Constructed the following reply:<br>
ERR<br>
-24920,ERR_BACKUPOP: backup operation was unsuccessful<br>
The database was unable to fulfill a request (-903, Host file I/O error,No more devices).<br>
Reply buffer filled.<br>
<br>
2009-06-09 15:58:11<br>
Cleaning up.<br>
Removing data transfer pipes.<br>
Removing data transfer pipe /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1 ... Done.<br>
Removed data transfer pipes successfully.<br>
<br>
Copying output of Backint for MaxDB to this file.<br>
---------- Begin of output of Backint for MaxDB (/var/opt/omni/tmp/DEMODB.bsi_out)----------<br>
<br>
---------- End of output of Backint for MaxDB (/var/opt/omni/tmp/DEMODB.bsi_out)----------<br>
Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/DEMODB.bsi_out'.<br>
Copying error output of Backint for MaxDB to this file.<br>
---------- Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/DEMODB.bsi_err)----------<br>
<br>
---------- End of error output of Backint for MaxDB (/var/opt/omni/tmp/DEMODB.bsi_err)----------<br>
Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/DEMODB.bsi_err'.<br>
Removed the Backint for MaxDB input file '/var/opt/omni/tmp/DEMODB.bsi_in'.<br>
Have finished clean up successfully.
<br>
<br>
Because of the Message "The backup tool is not running." something with the Backint is broken? Can anyone locate the error? <br>
<br>
Please help me.<br>
<br>
Thanks<br>
<br>
Timm
Edited by: Timm Letzel on Jun 9, 2009 5:00 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Timm,
I could not see the entries in knldiag file at 2009-06-09 15:58:11, when
the error occurred:
"2009-06-09 15:58:11 Database is still preparing the restore.
2009-06-09 15:58:11 The database has finished work on the request.
Receiving a reply from the database kernel.
Got the following reply from db-kernel:
SQL-Code :-903
Database has already finished the request."
1.
What is the value of the database parameter MAXBACKUPDEVS ?
You have the old database version 7.6.00 Build 018. Correct?
I recommend you to upgrade to the latest released patch/build of 7.6 version.
What is the version of HP DataProtector
2.
Are you SAP customer?
3.
Please update the thread with output of the command:
ls -l /var/opt/omni
Please update with output of the dbm commands::
medium_getall
backup_ext_ids_get "BACKDP-Data[1]''
backup_ext_ids_list
4.
Run after that - activate the database and recover the complete data backup.
< a comma to separate each ID specified >.
dbmcli -d DEMODB -u control,control
db_admin
db_connect control,control
db_activate RECOVER "BACKDP-Data[1]'' DATA ExternalBackupID "< IDs >"
u2026
Exit
Please update the thread after that with the knldiag & dbm.ebp files.
5.
Are you planning to run the restore from the incremental or log backups after
the recover the complete data backup will be finished ?
Thank you and best regards, Natalia Khlopina
Hallo
Sorry. I will use more replys. Because the Text is not parsed if I everything paste in one reply...
>
> 1.
> What is the value of the database parameter MAXBACKUPDEVS ?
dbmcli on MAXDB1>param_getvalue MAXBACKUPDEVS
OK
2
>
> You have the old database version 7.6.00 Build 018. Correct?
> I recommend you to upgrade to the latest released patch/build of 7.6 version.
I have installed the newest version:
dbmcli on MAXDB1>inst_info
OK
KERNEL = Rel 7.7.06 Build 009-123-202-944
LIBOMS = Rel 7.7.06 Build 009-123-202-944
LIBDBPINSTALL = Rel 7.7.06 Build 009-123-202-944
LIBOBJECTACCESSPROVIDER = Rel 7.7.06 Build 009-123-202-944
LIBLVCBENCH = Rel 7.7.06 Build 009-123-202-944
>
> What is the version of HP DataProtector
We using the Version 6.1
>
> 2.
> Are you SAP customer?
Yes
>
> 3.
> Please update the thread with output of the command:
> ls -l /var/opt/omni
[root@n4shost ~]# ls -l /var/opt/omni
total 20
drwxrwxrwx 2 root sys 4096 Jun 12 09:39 enhincrdb
drwxrwxrwx 2 root sys 4096 Jun 12 09:53 log
drwxr-xr-x 3 root sys 4096 Jun 12 09:39 server
drwxrwxrwx 2 root sys 4096 Jun 12 15:24 tmp
drwxrwxrwx 2 root sys 4096 Jun 12 09:39 windu
>
> Please update with output of the dbm commands::
> medium_getall
> backup_ext_ids_get "BACKDP-Data[1]''
> backup_ext_ids_list
Here is the Output:
[root@n4shost ~]# dbmcli -u DBADMIN,SECRET -d MAXDB1
dbmcli on MAXDB1>medium_getall
OK
log_medium /opt/sdb/backup/archive/MAXDB1_LOG FILE AUTO 0 8NO NO 20090611175143 20090611175143 NONE 0
data_medium /opt/sdb/backup/data/MAXDB1_COM FILE DATA 0 8 YES NO 20090611175238 20090611175238 NONE 0
BACKDP-Data[1]\1 /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 PIPE DATA 0 8 NO NO "" 20090612101458 20090615101717 BACK 0
BACKDP-Archive\1 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1 PIPE LOG 0 8 NO NO "" 20090612152211 20090615115910 BACK 0
---
dbmcli on MAXDB1>backup_ext_ids_get "BACKDP-Data[1]"
OK
---
dbmcli on MAXDB1>backup_ext_ids_list
OK
END
AVAILABLE|MAXDB1 09061213:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1|DATA MIGRATION|2009-06-12 10:14:59|
AVAILABLE|MAXDB1 09061217:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 11:55:20|
AVAILABLE|MAXDB1 09061217:2 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 15:13:14|
AVAILABLE|MAXDB1 09061217:3 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 11:35:35|
AVAILABLE|MAXDB1 09061217:4 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 10:55:37|
AVAILABLE|MAXDB1 0906153:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 11:55:20|
AVAILABLE|MAXDB1 0906153:2 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 15:13:14|
AVAILABLE|MAXDB1 0906153:3 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 11:35:35|
AVAILABLE|MAXDB1 0906153:4 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 10:55:37|
AVAILABLE|MAXDB1 0906154:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1|DATA MIGRATION|2009-06-15 10:17:18|
AVAILABLE|MAXDB1 09061512:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 11:55:20|
AVAILABLE|MAXDB1 09061512:2 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-15 11:58:34|
AVAILABLE|MAXDB1 09061512:3 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-15 11:47:22|
AVAILABLE|MAXDB1 09061512:4 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-15 11:25:32|
AVAILABLE|MAXDB1 09061512:5 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 15:13:14|
AVAILABLE|MAXDB1 09061512:6 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 11:35:35|
AVAILABLE|MAXDB1 09061512:7 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-15 11:02:01|
AVAILABLE|MAXDB1 09061512:8 /var/opt/omni/tmp/MAXDB1.BACKDP-Archive.1|LOG RECOVERY |2009-06-12 10:55:37|
---
dbmcli on MAXDB1>exit
OK
---
> 4.
> Run after that - activate the database and recover the complete data backup.
> < a comma to separate each ID specified >.
> dbmcli -d DEMODB -u control,control
> db_admin
> db_connect control,control
> db_activate RECOVER "BACKDP-Data[1]'' DATA ExternalBackupID "< IDs >"
> u2026
> Exit
>
> Please update the thread after that with the knldiag & dbm.ebp files.
dbmcli on MAXDB1>db_state
OK
State
OFFLINE
---
dbmcli on MAXDB1>db_admin
OK
---
dbmcli on MAXDB1>util_connect
OK
---
dbmcli on MAXDB1>db_activate RECOVER "BACKDP-Data[1]" DATA ExternalBackupID "MAXDB1 0906154:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1"
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
---
dbmcli on MAXDB1>
This is the knldiag-file:<br>
<br>
<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 SrvTasks 31: Permanently reserved 66 servertasks for 'Backup / Restore'.<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 SrvTasks 31: Permanently reserved 2 servertasks for 'Backup / Restore'.<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 SrvTasks 31: Permanently reserved 1 servertasks for 'Savepoint'.<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 RTETask 18: Kernel initialization done<br>
DESCRIPTION:<br>
The initialization of the Kernel components has finished. All special tasks are started now.<br>
Thread 0x45B Task 232 2009-06-15 12:51:48 CONNECT 12633: Connect req. (MAXDB1, T232, connection obj. 0x2afdf1840070, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:51 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1840348, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 112: Open of medium /var/opt/sdb/data/MAXDB1/log/DISKL0001 as number 3 for WRITE successfull<br>
DESCRIPTION:<br>
Opening medium /var/opt/sdb/data/MAXDB1/log/DISKL0001 as number 3 for WRITE was successfull. A medium is opened for data backup and data restoration. A database volume can also be opened as a medium. The medium received the internal number 3.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 71: start of formatting of volume LOG_VOLUME_001 ( from file position 8192 to 52428800 ),PAGESIZE=6400,PAGE_OFFSET=1<br>
DESCRIPTION:<br>
Start of formatting volume LOG_VOLUME_001. Beginning to write from the 8192. byte to the size of 52428800. This matches the database page from 1 to the size of 6400 pages. The RTE header page is included here.<br>
Thread 0x45B Task 231 2009-06-15 12:51:51 CONNECT 12677: Client has released connection, T231<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 74: Number of pages left to format /var/opt/sdb/data/MAXDB1/log/DISKL0001:6399<br>
DESCRIPTION:<br>
Since formatting the volume /var/opt/sdb/data/MAXDB1/log/DISKL0001 takes some time, every 5 seconds the amount of remaining pages is put out. Currently 6399 pages are left.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 76: formatting of volume /var/opt/sdb/data/MAXDB1/log/DISKL0001 completed<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 114: medium /var/opt/sdb/data/MAXDB1/log/DISKL0001 with number 3 was closed<br>
Thread 0x45B Task 231 2009-06-15 12:51:51 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1840348)<br>
Thread 0x45B Task 232 2009-06-15 12:51:51 RTEIO 10: volume LOG_VOLUME_001 has identification 2,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 with the logical volume number 1 is identified by 2.<br>
2009-06-15 12:51:51 RTEIO 8: attach volume LOG_VOLUME_001 on /var/opt/sdb/data/MAXDB1/log/DISKL0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type LOG_VOLUME_001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/log/DISKL0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:51 RTEIO 11: detach of volume LOG_VOLUME_001 path /var/opt/sdb/data/MAXDB1/log/DISKL0001<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/log/DISKL0001.<br>
Thread 0x45B Task 232 2009-06-15 12:51:51 RTEIO 10: volume LOG_VOLUME_001 has identification 2,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 with the logical volume number 1 is identified by 2.<br>
2009-06-15 12:51:51 RTEIO 8: attach volume LOG_VOLUME_001 on /var/opt/sdb/data/MAXDB1/log/DISKL0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type LOG_VOLUME_001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/log/DISKL0001 is being attached.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 112: Open of medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE successfull<br>
DESCRIPTION:<br>
Opening medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE was successfull. A medium is opened for data backup and data restoration. A database volume can also be opened as a medium. The medium received the internal number 2.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 71: start of formatting of volume DATA_VOLUME_0001 ( from file position 8192 to 1073741824 ),PAGESIZE=131072,PAGE_OFFSET=1<br>
DESCRIPTION:<br>
Start of formatting volume DATA_VOLUME_0001. Beginning to write from the 8192. byte to the size of 1073741824. This matches the database page from 1 to the size of 131072 pages. The RTE header page is included here.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 74: Number of pages left to format /var/opt/sdb/data/MAXDB1/data/DISKD0001:131071<br>
DESCRIPTION:<br>
Since formatting the volume /var/opt/sdb/data/MAXDB1/data/DISKD0001 takes some time, every 5 seconds the amount of remaining pages is put out. Currently 131071 pages are left.<br>
Thread 0x45B Task 231 2009-06-15 12:51:52 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1841678, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:52 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:51:52 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1841678)<br>
Thread 0x45B Task 231 2009-06-15 12:51:54 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1841678, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:54 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:51:54 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1841678)<br>
Thread 0x442 Task - 2009-06-15 12:51:56 RTEIO 76: formatting of volume /var/opt/sdb/data/MAXDB1/data/DISKD0001 completed<br>
Thread 0x442 Task - 2009-06-15 12:51:56 RTEIO 114: medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 with number 2 was closed<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 RTEIO 10: volume DATA_VOLUME_0001 has identification 3,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 with the logical volume number 1 is identified by 3.<br>
2009-06-15 12:51:56 RTEIO 8: attach volume DATA_VOLUME_0001 on /var/opt/sdb/data/MAXDB1/data/DISKD0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type DATA_VOLUME_0001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/data/DISKD0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 RTEIO 11: detach of volume DATA_VOLUME_0001 path /var/opt/sdb/data/MAXDB1/data/DISKD0001<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/data/DISKD0001.<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 RTEIO 10: volume DATA_VOLUME_0001 has identification 3,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 with the logical volume number 1 is identified by 3.<br>
2009-06-15 12:51:57 RTEIO 8: attach volume DATA_VOLUME_0001 on /var/opt/sdb/data/MAXDB1/data/DISKD0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type DATA_VOLUME_0001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/data/DISKD0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 DATACACH 53000: Begin data cache restart<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE STRIPES : 16<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE HASH LIST :2553088<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE head item siz: 16<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE CONTROLBLOCKS:4954112<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE cblock size : 128<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 20 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 30 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 40 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 50 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 60 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 70 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 80 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 90 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 95 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 99 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DYNP_B20_DATACACHE :7816832<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynDATA 54003: DYND_B20_DATACACHE : 38704<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 DATACACH 53000: Finish data cache restart<br>
Thread 0x45B Task 231 2009-06-15 12:51:58 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf18435f8, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:58 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:51:58 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf18435f8)<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 DATACACH 53000: Begin data cache shutdown<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 95 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 90 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 80 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 70 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 60 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 50 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 40 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 30 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 20 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 DATACACH 54003: Released cache frames: 38704<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 DATACACH 53000: Finish data cache shutdown<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 RTEIO 11: detach of volume DATA_VOLUME_0001 path /var/opt/sdb/data/MAXDB1/data/DISKD0001<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/data/DISKD0001.<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 RTEIO 11: detach of volume LOG_VOLUME_001 path /var/opt/sdb/data/MAXDB1/log/DISKL0001<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/log/DISKL0001.<br>
Thread 0x4AB Task - 2009-06-15 12:51:58 RTEIO 112: Open of medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE successfull<br>
DESCRIPTION:<br>
Opening medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE was successfull. A medium is opened for data backup and data restoration. A database volume can also be opened as a medium. The medium received the internal number 2.<br>
Thread 0x4AB Task - 2009-06-15 12:51:58 RTEIO 72: formatting of volume DATA_VOLUME_0001 not needed, since size 1073741824 bytes,PAGESIZE=131072<br>
DESCRIPTION:<br>
Formatting of volume DATA_VOLUME_0001 is not needed, since hte volume already has the size of 1073741824 bytes. This matches 131072 database pages (with runtime header page).<br>
Thread 0x4AB Task - 2009-06-15 12:51:58 RTEIO 114: medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 with number 2 was closed<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 RTEIO 10: volume DATA_VOLUME_0001 has identification 2,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 with the logical volume number 1 is identified by 2.<br>
2009-06-15 12:51:58 RTEIO 8: attach volume DATA_VOLUME_0001 on /var/opt/sdb/data/MAXDB1/data/DISKD0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type DATA_VOLUME_0001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/data/DISKD0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 RTEIO 11: detach of volume DATA_VOLUME_0001 path /var/opt/sdb/data/MAXDB1/data/DISKD0001<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/data/DISKD0001.<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 RTEIO 10: volume DATA_VOLUME_0001 has identification 2,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 with the logical volume number 1 is identified by 2.<br>
2009-06-15 12:51:58 RTEIO 8: attach volume DATA_VOLUME_0001 on /var/opt/sdb/data/MAXDB1/data/DISKD0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type DATA_VOLUME_0001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/data/DISKD0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 RTEIO 112: Open of medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE successfull<br>
DESCRIPTION:<br>
Opening medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE was successfull. A medium is opened for data backup and data restoration. A database volume can also be opened as a medium. The medium received the internal number 2.<br>
Thread 0x45B Task 231 2009-06-15 12:52:02 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1845e70, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:52:02 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:52:02 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1845e70)<br>
Thread 0x457 Task 127 2009-06-15 12:53:04 ERR RTEIO 113: medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 cannot be opened for READ access,_FILE=RTEIO_StreamMedium+noPIC.cpp,_LINE=1428<br>
DESCRIPTION:<br>
Medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 cannot be opened for READ access.<br>
ACTION:<br>
Contact your system administrator. Show him the error message which points to an operating system configuration error and then contact the database support if your system administrator can not fix the error.<br>
2009-06-15 12:53:04 ERR RTEIO 65: open of medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 was canceled,_FILE=RTEIO_StreamMedium+noPIC.cpp,_LINE=5056<br>
DESCRIPTION:<br>
Opening of medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 was cancelled by an explicit user task termination.<br>
Thread 0x457 Task 153 2009-06-15 12:53:04 WNG SAVE 52108: canceled by user<br>
Thread 0x45B Task 232 2009-06-15 12:53:04 RTEIO 114: medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 with number 2 was closed<br>
Thread 0x45B Task 232 2009-06-15 12:53:04 RTEIO 11: detach of volume DATA_VOLUME_0001 path /var/opt/sdb/data/MAXDB1/data/DISKD0001<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/data/DISKD0001.<br>
Thread 0x45B Task 232 2009-06-15 12:53:04 ERR RESTORE 52012: error occured, basis_err 3700<br>
Thread 0x45B Task 232 2009-06-15 12:53:04 ERR Recovery 6: Data recovery failed,_FILE=Kernel_Administration+noPIC.cpp,_LINE=1780<br>
2009-06-15 12:53:04 SrvTasks 17: Servertask Info: because Error in backup task occured<br>
2009-06-15 12:53:04 SrvTasks 10: Job 1 (Backup / Restore Medium Task) [executing] WaitingT232 Result=3700<br>
2009-06-15 12:53:04 KernelComm 6: Error in backup task occured, Error code 3700 "hostfile_error"<br>
2009-06-15 12:53:04 Backup 1: Backupmedium #1 (/var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1) Could not open stream<br>
2009-06-15 12:53:04 KernelComm 6: Backup error occured, Error code 3700 "hostfile_error"<br>
Thread 0x45B Task 232 2009-06-15 12:53:04 ERR Recovery 6: Data recovery failed,_FILE=Kernel_Administration+noPIC.cpp,_LINE=1780<br>
2009-06-15 12:53:04 SrvTasks 17: Servertask Info: because Error in backup task occured<br>
2009-06-15 12:53:04 SrvTasks 10: Job 1 (Backup / Restore Medium Task) [executing] WaitingT232 Result=3700<br>
2009-06-15 12:53:04 KernelComm 6: Error in backup task occured, Error code 3700 "hostfile_error"<br>
2009-06-15 12:53:04 Backup 1: Backupmedium #1 (/var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1) Could not open stream<br>
2009-06-15 12:53:04 KernelComm 6: Backup error occured, Error code 3700 "hostfile_error"<br>
Thread 0x45B Task 232 2009-06-15 12:53:29 CONNECT 12677: Client has released connection, T232<br>
Thread 0x45B Task 232 2009-06-15 12:53:29 CONNECT 12651: Connection released (MAXDB1, T232, connection obj. 2afdf1840070)<br>
<br>
<br>
This is the dbm.ebp-File<br>
<br>
2009-06-15 12:51:50<br>
Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.<br>
Using environment variable 'TMP' with value '/var/tmp' as directory for temporary files and pipes.<br>
Using connection to Backint for MaxDB Interface.<br>
<br>
2009-06-15 12:51:51<br>
Checking existence and configuration of Backint for MaxDB.<br>
Using configuration variable 'BSI_ENV' = '/var/opt/omni/tmp/MAXDB1.bsi_env' as path of the configuration file of Backint for MaxDB.<br>
Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value '/var/opt/omni/tmp/MAXDB1.bsi_env'.<br>
Reading the Backint for MaxDB configuration file '/var/opt/omni/tmp/MAXDB1.bsi_env'.<br>
Found keyword 'BACKINT' with value '/opt/omni/lbin/sapdb_backint'.<br>
Found keyword 'INPUT' with value '/var/opt/omni/tmp/MAXDB1.bsi_in'.<br>
Found keyword 'OUTPUT' with value '/var/opt/omni/tmp/MAXDB1.bsi_out'.<br>
Found keyword 'ERROROUTPUT' with value '/var/opt/omni/tmp/MAXDB1.bsi_err'.<br>
Found keyword 'PARAMETERFILE' with value 'SAPDB.31776.1245059950.par'.<br>
Found keyword 'TIMEOUT_SUCCESS' with value '900'.<br>
Found keyword 'TIMEOUT_FAILURE' with value '30'.<br>
Finished reading of the Backint for MaxDB configuration file.<br>
<br>
Using '/opt/omni/lbin/sapdb_backint' as Backint for MaxDB program.<br>
Using '/var/opt/omni/tmp/MAXDB1.bsi_in' as input file for Backint for MaxDB.<br>
Using '/var/opt/omni/tmp/MAXDB1.bsi_out' as output file for Backint for MaxDB.<br>
Using '/var/opt/omni/tmp/MAXDB1.bsi_err' as error output file for Backint for MaxDB.<br>
Using 'SAPDB.31776.1245059950.par' as parameter file for Backint for MaxDB.<br>
Using '900' seconds as timeout for Backint for MaxDB in the case of success.<br>
Using '30' seconds as timeout for Backint for MaxDB in the case of failure.<br>
Using '/var/opt/sdb/data/wrk/MAXDB1/dbm.knl' as backup history of a database to migrate.<br>
Using '/var/opt/sdb/data/wrk/MAXDB1/dbm.ebf' as external backup history of a database to migrate.<br>
Checking availability of backups using backint's inquire function.<br>
Check passed successful.<br>
<br>
2009-06-15 12:51:51<br>
Checking medium.<br>
Check passed successfully.<br>
<br>
2009-06-15 12:51:51<br>
Preparing restore.<br>
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.<br>
Setting environment variable 'BI_REQUEST' to value 'NEW'.<br>
Setting environment variable 'BI_BACKUP' to value 'FULL'.<br>
Got the following list of external backup ID's:<br>
"MAXDB1 0906154:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1"<br>
<br>
Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAXDB1 -f restore -t file -p SAPDB.31776.1245059950.par -i /var/opt/omni/tmp/MAXDB1.bsi_in -c'.<br>
Created temporary file '/var/opt/omni/tmp/MAXDB1.bsi_out' as output for Backint for MaxDB.<br>
Created temporary file '/var/opt/omni/tmp/MAXDB1.bsi_err' as error output for Backint for MaxDB.<br>
Writing '0906154:1 /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1' to the input file.<br>
Prepare passed successfully.<br>
<br>
2009-06-15 12:51:51<br>
Creating pipes for data transfer.<br>
Creating pipe '/var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1' ... Done.<br>
All data transfer pipes have been created.<br>
<br>
2009-06-15 12:51:51<br>
Starting database action for the restore.<br>
Requesting 'CREATE INSTANCE WITH RESTORE DATA FROM '/var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1' PIPE BLOCKSIZE 8 MEDIANAME 'BACKDP-Data[1]'' from db-kernel.<br>
The database is working on the request.<br>
<br>
2009-06-15 12:51:51<br>
Waiting until database has prepared the restore.<br>
Asking for state of database.<br>
2009-06-15 12:51:51 Database is still preparing the restore.<br>
Waiting 1 second ... Done.<br>
Asking for state of database.<br>
2009-06-15 12:51:52 Database is still preparing the restore.<br>
Waiting 2 seconds ... Done.<br>
Asking for state of database.<br>
2009-06-15 12:51:54 Database is still preparing the restore.<br>
Waiting 3 seconds ... Done.<br>
Asking for state of database.<br>
2009-06-15 12:51:58 Database is still preparing the restore.<br>
Waiting 4 seconds ... Done.<br>
Asking for state of database.<br>
2009-06-15 12:52:02 Database has finished preparation of the restore.<br>
The database has prepared the restore successfully.<br>
<br>
2009-06-15 12:52:02<br>
Starting Backint for MaxDB.<br>
Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAXDB1 -f restore -t file -p SAPDB.31776.1245059950.par -i /var/opt/omni/tmp/MAXDB1.bsi_in -c >>/var/opt/omni/tmp/MAXDB1.bsi_out 2>>/var/opt/omni/tmp/MAXDB1.bsi_err'.<br>
Process was started successfully.<br>
Backint for MaxDB has been started successfully.<br>
<br>
2009-06-15 12:52:02<br>
Waiting for end of the restore operation.<br>
2009-06-15 12:52:02 The backup tool is running.<br>
2009-06-15 12:52:02 The database is working on the request.<br>
<br>
2009-06-15 12:52:03 The backup tool process has finished work with return code 2.<br>
<br>
2009-06-15 12:52:07 The database is working on the request.<br>
<br>
2009-06-15 12:52:17 The database is working on the request.<br>
<br>
2009-06-15 12:52:32 The database is working on the request.<br>
<br>
2009-06-15 12:52:52 The database is working on the request.<br>
<br>
2009-06-15 12:53:04 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.<br>
<br>
2009-06-15 12:53:05 The database has finished work on the request.<br>
Receiving a reply from the database kernel.<br>
Got the following reply from db-kernel:<br>
SQL-Code :-903<br>
The restore operation has ended.<br>
<br>
2009-06-15 12:53:05<br>
Filling reply buffer.<br>
Have encountered error -24920:<br>
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.<br>
<br>
Constructed the following reply:<br>
ERR<br>
-24920,ERR_BACKUPOP: backup operation was unsuccessful<br>
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.<br>
Reply buffer filled.<br>
<br>
2009-06-15 12:53:05<br>
Cleaning up.<br>
Removing data transfer pipes.<br>
Removing data transfer pipe /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 ... Done.<br>
Removed data transfer pipes successfully.<br>
<br>
Copying output of Backint for MaxDB to this file.<br>
---------- Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAXDB1.bsi_out)----------<br>
#ERROR /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1<br>
<br>
---------- End of output of Backint for MaxDB (/var/opt/omni/tmp/MAXDB1.bsi_out)----------<br>
Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAXDB1.bsi_out'.<br>
Copying error output of Backint for MaxDB to this file.<br>
---------- Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAXDB1.bsi_err)----------<br>
<br>
---------- End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAXDB1.bsi_err)----------<br>
Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAXDB1.bsi_err'.<br>
Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAXDB1.bsi_in'.<br>
Have finished clean up successfully.<br>
<br>
<br>
<br>
<br>
> <br>
> 5.<br>
> Are you planning to run the restore from the incremental or log backups after<br>
> the recover the complete data backup will be finished ?<br>
<br>
<br>
Yes, after the restore of the Full Backup i want to recover the log-Files. With the DATA Protector Plugin it is possible zu recover the full-backup. The error apears while recovering the log-backup using the DP GUI.<br>
> Thank you and best regards, Natalia Khlopina
Thank you too. I hope I have provided all Information you need....
And sorry again for so many replys. But i'am not allowed to post such a big message... I hope it is readable.
Best regards
Timm
Hello Timm,
1. As you are SAP customer, I recommend you to create the OSS ticket.
So we could login to your system and check the needed log files or
variable settings.
Currently, I'm partially lost in the information given in this thread. So may be I missed something.
2. I went to the last reported errors.
The error on 2009-06-15 at 12:53:04 :
"Medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 cannot be opened for READ access."
reported in the knldiag file.
The dbmserver starts the sapdb_backint tool with the following parameters:
/opt/omni/lbin/sapdb_backint -u MAXDB1 -f restore -t file -p SAPDB.31776.1245059950.par -i /var/opt/omni/tmp/MAXDB1.bsi_in -c >>/var/opt/omni/tmp/MAXDB1.bsi_out 2>>/var/opt/omni/tmp/MAXDB1.bsi_err
after the creating pipe '/var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1' was Done successfully according dbm.ebp file.
But the recovery is not working may be, because the sapdb_backint, provided from HP,
does not write any data to the pipe where the MaxDB should recover from.
The problem now could be, that the sapdb_backint tool didn't write the data into the pipe. And it has to be checked < see 3. >.
The recovery has been already initiated on database site. The database tries to read from the pipes, but failed.
3. The sapdb_backint tool has been implemented by HP. Please contact your HP support for help concerning this issue. The case should be reproduced using the mentioned in < 2.> sapdb_backint call.
< && you could use the "dd" command to read from the pipes >
Also the configuration variables has to be set. Please check it.
Please let us know if you got the HP support and you checked that the data were recovered to the pipes.
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on Jun 16, 2009 11:08 AM
Hello,
I have posted this problem in the HP IRC. The DP Admin would install Patches before we open a call with HP.
When I run netstat during the recovery I can see some short established connections. But they will be immediately in the Time_Wait - Status. In the DP-Logs I cannot see any debug messages or something.
I hope the HP IRC can help me. Here is the link to the Post:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1348045
Many Thanks for your help!
Hello Timm,
1. You wrote : "But if I use DP Gui I am able to recover the full Backup. "
Is it correct?
Do you have problems to recover the log backups now?
2. According this thread you have problems to recover the full database Data Backup. And this problem has to be solved before to do the recovery of the database log backups.
From the posted logs you run the recovery of the full database Data Backup & failed, because "Medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 cannot be opened for READ access."
I asked you to check if the configuration variables were set as recommended in DP 6.1 document.
Also check, if that the data were recovered to the pipes using the command posted in my above reply.
3. Did you create the SAP ticket to the component BC-DB-SDB on this issue?
Thank you and best regards, Natalia Khlopina
Hello,
>
> Hello Timm,
> 1. You wrote : "But if I use DP Gui I am able to recover the full Backup. "
> Is it correct?
> Do you have problems to recover the log backups now?
Yes... the Full Backup is recoverable using DP. But if I want to recover a log it throws errors. Please see my first post. If I use the DBMCLI I can't recover the full backup.
>
> 2. According this thread you have problems to recover the full database Data Backup. And this problem has to be solved before to do the recovery of the database log backups.
> From the posted logs you run the recovery of the full database Data Backup & failed, because "Medium /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1 cannot be opened for READ access."
> I asked you to check if the configuration variables were set as recommended in DP 6.1 document.
> Also check, if that the data were recovered to the pipes using the command posted in my above reply.
These are the values from the DP Manual:
>
>Other UNIX systems:
>BACKINT /usr/omni/bin/sapdb_backint
>INPUT /var/opt/omni/tmp/inst_name.bsi_in
>OUTPUT /var/opt/omni/tmp/inst_name.bsi_out
>ERROROUTPUT /var/opt/omni/tmp/inst_name.bsi_err
>PARAMETERFILE name_of_backup_spec
>TIMEOUT_SUCCESS 60
>TIMEOUT_FAILURE 30
And these are my values. I cannot see an error:
>
> [root@n4shost ~]# cat /var/opt/omni/tmp/MAXDB1.bsi_env
> BACKINT "/opt/omni/lbin/sapdb_backint"
> INPUT /var/opt/omni/tmp/MAXDB1.bsi_in
> OUTPUT /var/opt/omni/tmp/MAXDB1.bsi_out
> ERROROUTPUT /var/opt/omni/tmp/MAXDB1.bsi_err
> PARAMETERFILE SAPDB.31776.1245059950.par
> TIMEOUT_SUCCESS 900
> TIMEOUT_FAILURE 30
Edited by: Timm Letzel on Jun 17, 2009 9:51 AM
No Data are written to the pipe. We have a HP MSL, which performs no actions if I start the Backup. I also see no started sessions in the DP Monitor or messeges in the debug.log on DP side. I think the connection from MaxDB to DP Cell Manager is failing. If i run netstat on the MaxDB host i can see some connections. But all connections have only a very short time (probably < 1s) the status ESTABLISHD. After that all the connections are TIME_WAIT. On the Hosts we have no firewalls installed and the Servers are located in the same network.
I have no Idea why DP simply ignore the request.
>
> 3. Did you create the SAP ticket to the component BC-DB-SDB on this issue?
> Thank you and best regards, Natalia Khlopina
No, because I have installed the SAP TestDrive. We have no registered Hardware or somewhat to open the call. We just evaluate if MaxDB is "compatible" with our environment....
Thank you for further Help
Timm Letzel
OT: If I write a certain amount of Text in the Forum all the formatting text will be ignore and even line breaks does not apear if I click on "Preview" or "Post Messages". So the Post will be not human readable after posting. Thats why I have to split my Posts every time. Is this a Bug?
Hello Timm,
You could give short answers on the following steps without a copy of my text + the links
to the files and documents with more details, then this thread will not grow so fast
1.
At the beginning you got error to recover the log backup due Initialization of log for 'restore log' failed with 'LogAndDataIncompatible', Log- and Data are not compatible because 'Restore Log with Log State 'HistoryLost' is not allowed'.
You wrote, that you had generated a new Log-File < log volumes > with db_activate.
<help db_activate
OK
db_activate <sysdba>,<pwd> | RECOVER <recoveroptions> >
After you run the db_activate command the database was initialized & brought online after
that. Backup history is broken down and flagged with the abbreviation HISTLOST.
Before to be able to run recovery of the log backups, you need to do the recovery
of the databackup. Please see more details in the SAP notes & documentation:
869267 FAQ: MaxDB LOG area
129352 Homogeneous system copy with MaxDB (SAP DB)
1014782 FAQ: MaxDB system copy
I also gave you references to the MAXDB documentation in my first reply.
Did you try to run to recover a Database with the HP Data Protector Plug-in using the complete databackup first?
"I had try rename the dbm.knl file." => please restore this file.
I assummed, that the dbm.knl and dbm.ebf files were not renamed or deleted.
You wrote
Run ::
dbmcli -d <SID> -u control,control
db_admin
db_connect control,control
db_execute clear log
exit
After that run to recover a Database with the HP Data Protector Plug-in using the complete databackup first,
then continue with restore of the log backups. Post the results.
2.
When you used the dbmcli tool, did you set the variables ::
OB2OPTS=
OB2APPNAME=DEMODB
< OB2BARHOSTNAME >
OB2BACKUPAPPNAME=DEMODB
OB2BACKUPHOSTNAME=n4shost.sapdb.local
using the dbm command:
dbm_configset -raw BSI_ENV /var/opt/omni/tmp/DEMODB.bsi_env
dbm_configset -raw set_variable_10 OB2BACKUPAPPNAME=DEMODB
dbm_configset -raw set_variable_11 OB2BACKUPHOSTNAME=n4shost.sapdb.local
dbm_configset -raw set_variable_12 OB2OPTS="(null)"
Please update with output of the dbm command 'dbm_configget all'.
Thank you and best regards, Natalia Khlopina
Hello,
I try to describe the whole situation and all actions I have done again.
The first Point is that I installed the DB in a virtual Machine. After each test I revert to snapshot so that the Database is in a well known state. The Diagnostic files are all there and faultless for that reason. After I revert to the snapshot I delete the DB Data File and the Log -File and restart the Database. At this point I want to recover the whole Database including all written log files from Tape through the Data protector.
The Recovery of the Full Backup returns a successful status. After the recovery session the Data file is restored in the file system, but I can't open the Database because the Log file is missing. If I try to recover the Logs, Data protector runs the command "Executing the dbmcli command: `db_warm -f '". During the command I can see in the knldiag.err:
An attempt to open the path '/var/opt/sdb/data/MAXDB1/log/DISKL0001' failed. The operating system returned the error code 2 and the error text 'No such file or directory'
To fix this I used the command "db_activate" without any options. After that a new (empty) Log File existed und the Log Backups was marked with History Lost. In the knldiag.err I saw "log must be cleared" during the next DP-recovery session. Thatu2019s why I have renamed my dbm.knl. This I had done before I did my first post.
I hope the situation becomes increasingly clear.
Now to your questions/suggestions:
I have tested to clear the log before the recovery of the last Full backup. I get the error: "Error code 9050 "disk_not_accessible".
The Full Backup runs without errors. After recovering the Full Backup I am able to clear the log File. Now I start the restore of the Archives and I get some new errors. I did an upload to rapid share with the actual knldiag and my Backup History. Please download it: <a href="http://rapidshare.com/files/247337004/error_recover_logs.zip">http://rapidshare.com/files/247337004/error_recover_logs.zip</a>
It wants to restore a version before the last Full Backup (line 141 in knldiag.txt) and chance the state from "admin" to "abort"(line 163). After this event the DP session ends with an error. (The Full Backup contains all data till Page 227519 and it want to recover the range from 126354 to 173997). (see Backup History)
2.
I had not set the Variables during the previous runs. But even if I did, the error is still the same:
Backupmedium #1 (/var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1) Could not open stream
Here is the requested Output
dbmcli on MAXDB1>dbm_configget all
OK
BSI_ENV = /var/opt/omni/tmp/MAXDB1.bsi_env
set_variable_10 = OB2BACKUPAPPNAME=MAXDB1
set_variable_11 = OB2BACKUPHOSTNAME=n4shost.sapdb.local
set_variable_12 = OB2OPTS=(null)
(My Instance is now called "MaxDB1". Because I had installed the new version of MaxDB Software and load the Tutorial using the DBMGUI Wizard, that suggests the name MAXDB1. )
I hope I have provided all Informationu2019s.
Thanks
Timm Letzel
Hello Timm,
I'm not sure if this will help much, but some background information about the recovery procedure:
When the log volumes are not available anymore, you need to initialize the log volume during the recovery procedure. This is done with the "db_activate recover" command. So when you want to restore the system with data protector after you deleted the log volume, you need to get this tool to issue the db_activate command. I don't know the options of this tool, so I can't explain how to do this. But maybe you can figure this out.
If you don't delete the log volume, the recovery should work with the normal 'recover_start' command.
With DBMGUI/DatabaseStudio/DBMCLI the restore procedure should work as well. In DBMCLI you need to use the command "db_activate recover" as Natalia already explained. In DBMGUI or Database Studio this would be the option 'Recover with Initialization'.
Regarding the error you get during that procedure:
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
This means that the backup tool got an error - and because of that the database request was cancelled. So the backup tool (one of the used backints) failed. Unfortunately the error message is not very helpful:
#ERROR /var/opt/omni/tmp/MAXDB1.BACKDP-Data[1].1
One question from my side: it looks like you configured backint, that only one backint program is used - the sapdb_backint in directory /opt/omni/lbin/. I'm not sure if that is the correct configuration for data protector. Normally when backint is used, you are using two different backint programs - backint for MaxDB delivered with the MaxDB software and the other backint delivered with the backup tool. Maybe this is causing the problems? But then I wouldn't expect the backup to work at all...
And another information: if the database has the state HISTLOST, it does not help to rename/delete file dbm.knl. This state is stored in the database itself as well. When you execute db_activate without any options, an empty database is created and during the first restart the first log entries are written. You'll have to use the "db_activate recover" command then again to restore the system with your backups.
Regards, Melanie
Hallo,<br>
<br>
Thanks for your Post but i am not able to following your how-to.<br>
<br>
To identify the external Backup ID, which is obligatory with db_activate RECOVER I typed following:<br>
<br>
backup_ext_ids_get BACKDP-Data[1]
<br>
After that I can look for the External Backup IDs:<br>
<br>
dbmcli on DEMODB>backup_ext_ids_list<br>
OK<br>
END<br>
AVAILABLE|DEMODB 09060220:1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1|DATA MIGRATION|2009-06-02 14:51:09|<br>
AVAILABLE|DEMODB 09060222:1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1|DATA MIGRATION|2009-06-02 15:26:19|<br>
AVAILABLE|DEMODB 09060224:1 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1|LOG RECOVERY |2009-06-02 16:00:20|<br>
AVAILABLE|DEMODB 09060526:1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1|DATA MIGRATION|2009-06-05 12:49:09|<br>
AVAILABLE|DEMODB 09060527:1 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1|LOG RECOVERY |2009-06-05 12:44:46|<br>
AVAILABLE|DEMODB 09060527:2 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1|LOG RECOVERY |2009-06-03 11:50:10|<br>
AVAILABLE|DEMODB 09060527:3 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1|LOG RECOVERY |2009-06-03 12:01:40|<br>
AVAILABLE|DEMODB 09060527:4 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1|LOG RECOVERY |2009-06-03 12:13:25|<br>
AVAILABLE|DEMODB 09060527:5 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1|LOG RECOVERY |2009-06-03 11:39:24|<br>
<br>
---
<br>
<br>
To Recover the last full Backup I used this command.<br>
dbmcli on DEMODB>db_activate RECOVER BACKDP-Data[1] ExternalBackupID "DEMODB 09060526:1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1"<br>
ERR<br>
-24920,ERR_BACKUPOP: backup operation was unsuccessful<br>
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
<br>
<br>
But this error appears. In the Kernel Error File I see following lines:<br>
33 ERR 11000 d0_aopen Cannot open device, No such file or directory <br>
2009-06-03 11:13:03 33 ERR 11000 d0_aopen Device name '/sapdb/demodb/full/data' <br>
2009-06-03 11:13:03 24 ERR 52012 SAVE error occured, basis_err 3700<br>
2009-06-03 11:13:03 24 ERR 3 Backup Kernel_Administration.cpp:1114<br>
2009-06-03 11:13:03 24 ERR 3 Backup 2009-06-03 11:13:03 Backup Error 3<br>
2009-06-03 11:13:03 24 ERR 3 Backup Data backup failed<br>
2009-06-03 11:13:03 24 ERR 3 Backup + SrvTasks_Job.cpp:123<br>
2009-06-03 11:13:03 24 ERR 3 Backup + 2009-06-03 11:13:03 SrvTasks Info 17<br>
2009-06-03 11:13:03 24 ERR 3 Backup - Servertask Info: because Error in backup task occured<br>
2009-06-03 11:13:03 24 ERR 3 Backup + SrvTasks_Job.cpp:124<br>
2009-06-03 11:13:03 24 ERR 3 Backup + 2009-06-03 11:13:03 SrvTasks Info 10<br>
2009-06-03 11:13:03 24 ERR 3 Backup - Job 1 (Backup / Restore Medium Task) [executing] WaitingT162 Result=3700<br>
2009-06-03 11:13:03 24 ERR 3 Backup + Kernel_Trace.cpp:223<br>
2009-06-03 11:13:03 24 ERR 3 Backup + 2009-06-03 11:13:03 KernelCommon Info 6<br>
2009-06-03 11:13:03 24 ERR 3 Backup - Error in backup task occured, Errorcode 3700 "hostfile_error"
<br>
<br>
The File "sapdb/demodb/full/data" is used by another Backup template:<br>
medium_getall<br>
OK<br>
BACKDP-Data[1]\1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1 PIPE DATA 0 8 NO NO \"\" 20090602145107 20090605144017 BACK<br>
log_medium /sapdb/demodb/archive/log FILE AUTO 0 8 NO NO 20090602152339 20090602152339 NONE<br>
FILE_BACKUP_FULL /sapdb/demodb/full/data FILE DATA 0 8 NO NO 20090603110145 20090603110145 NONE<br>
BACKDP-Archive\1 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1 PIPE LOG 0 8 NO NO \"\" 20090602153028 20090605125331 BACK
<br>
<br>
Why does the dbmcli try to use the "FILE_BACKUP_FULL"-Template?<br>
<br>
After this error I start the Restore of the Full Backup from DP Plug In and execute the command again. But the error is the same.<br>
<br>
I am wondering that the last Archive Backup which was successfully by DP is not in the External Backup History of MaxDB. Is there something wrong?<br>
<br>
Thanks for help.<br>
<br>
Timm <br>
<br>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Timm,
1)
Review the documents at SAP MaxDB 7.6 Library
http://maxdb.sap.com/doc/7_6/default.htm ->Tutorials
-> Database Administration Tutorial
"Creating a Database Copy (Importing a Data Backup into Another D"
After the data and log volumes will be deleted use the dbm commands:
A) Open a database session:
dbmcli on <SID>>db_connect
B) Run recovery with initialization:
dbmcli on <SID>>db_activate RECOVER <recoveroptions>
u2026.
2)
If the database was restarted online after you run 'db_activate' command,
Run ::
dbmcli -d <SID> -u control,control
>db_admin
>db_connect control,control
>db_execute clear log
>exit
After that try to recover a Database with the HP Data Protector Plug-in.
3)
Use recovery with initialization in DBMGUI.
http://maxdb.sap.com/doc/7_6/default.htm ->Tools
-> Database Manager GUI -> Recoveries
"Restoring After Initializing a Database Instance"
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.