on 02-28-2011 9:19 PM
Hello, please I need your help to solve this problem. I've upgraded
MAXDB from 7.7.04.28 to 7.7.7.28. Then we tried by mistake to recover a DB
backup with Max db database studio and it finished with error. Then we
can't start the database instance, here is the /home/erladm/startdb.log:Checking ADA db Database
-
Database is not available via R3trans
Running /usr/sap/ERL/SYS/exe/run/startdb
Trying to start database ...
Log file: /home/erladm/startdb.log
Database start failed
DB startup failed
ADP-ERL:erladm 41> tail -100 /home/erladm/startdb.log
-
Mon Feb 28 17:32:13 ARST 2011
LOGFILE FOR STARTING DATABASE
Trying to start database ...
-
Mon Feb 28 17:32:13 ARST 2011
Checking required environment variables
SAPSYSTEMNAME is >ERL<
Start database with xuserkey >c<
-
Mon Feb 28 17:32:13 ARST 2011
Connect to the database to check the database state
dbmcli: connect check finished with return code: 0
Database not available
-
Mon Feb 28 17:32:14 ARST 2011
Starting XServer
12798 NISERVER NI support started.
WNG 12453 NISSLSRV NISSL Init: SSL: Could not locate ticket file
12902 XSERVER started, 'U64/LIX86 7.7.07 Build 028-123-241-377'
-
Mon Feb 28 17:32:15 ARST 2011
Starting database
Starting Database Instance...
OK
Opening Database...
ERR
-24988,ERR_SQL: SQL error
-9407,System error: unexpected error
3,Database state: OFFLINE
Internal errorcode, Error code 6433 "system_error"
20025,ACTIVATE is missing
-
Mon Feb 28 17:32:23 ARST 2011
Connect to the database to verify the database is now open
dbmcli check finished with return code: 0
Database start failed
I'll appreciate your quickly response.
Thank you.
Hello Dario,
you should try to understand why the restore terminated unsuccessfully, and probably another restore is mandatory to start the database - what is the error reported in the logs during the restore?
When you try to start database, what is written in the MaxDB error log?
Regards,
Valerio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Valerio, thank you for your answer. This is the error that MAXDB Database Studio gave during the backup restore:
-903 Host file I/O error 6,Data recovery failed 113,Open medium on /mnt/BKPS/BackUP-ADV/BackUP-ADV.bkp for READ failed Servertask Info: because Error in backup task occured Job 1 (Backup / Restore Medium Task) [executing] WaitingT140 Result=3700 Error in backup task occured, Error code 3700 "hostfile_error" 127,RTE header size 524288 instead of 65536 bytes on medium /mnt/BKPS/BackUP-ADV/BackUP-ADV.bkp
You have completed the steps required to perform a recovery. Make the specified medium available and choose 'Start'.
Medium: COM Device/File: /mnt/BKPS/BackUP-ADV/BackUP-ADV.bkp
I'll apreciate your answer.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
1.
you update the MAXDB from 7.7.04.28 to 7.7.7.28
=>
Do you have the database version 7.7.7.28 ?
Please post output of the command:
sdbregview -l
2.
What version database you had when the databackup was created?
Medium: COM Device/File: /mnt/BKPS/BackUP-ADV/BackUP-ADV.bkp
3.
What is the version of DB Studio?
Please update with output of the dbm commands:
medium_labeloffline "COM"
medium_getall
Regards, Natalia Khlopina
Hello,
During a restore on a different system as the backup file has been created, we got the same message:
"Error in backup task occured, Error code 3700 "hostfile_error" 127,RTE header size 524288 instead of 65536 bytes on medium"
Noticing that the multiplier between 524288 and 68836 is 8, we came to the conclusion that we told the system the wrong blocksize (we choosed 8), instead of the correct block size of 64 which was used during the backup.
After redefining the block size to 64 in the definition of the restore file, we could succesfully start the restore.
The content of the message seems to us quite confusing
Regards,
Herbert Stöckl
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.