on 08-16-2013 11:39 PM
Hi Jorge,
Which user are you connected with ?
Also share the details from
- sdbregview -l
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jorge,
Looks like the problem is the BackupTemplates.xml is corrupt.
I would like to look at this xml file first, before suggesting any corrections.
Can you please attach the BackupTemplates.xml file to the thread.
Regards, Yashwanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jorge,
/sapdb/programs/bin/xinstinfo DEV
dbmcli on DEV> param_directget RUNDIRECTORYPATH
RECOMMENDATION:
Since you are using MaxDB 7.8 and the "Database Manager GUI" is an old software, some of the new features of 7.8 may not be known to the GUI, so I recommend you to download the Database Studio software from the service marketplace.
Regards, Yashwanth
Hi Jorge,
The reason for two (//) in the path /var/sapdb/DEV/data//BackupTemplates.xml is,
The parameter RUNDIRECTORYPATH has a (/) at the end
Here's what you need to do:
1) Switch the database to offline mode (db_offline)
2)
Connect to the database as DBM/Control user
Run the commands -
param_startsession
param_directput RUNDIRECTORYPATH /var/sapdb/DEV/data
param_commitsession
param_checkall
OR you can change the parameter using the DBStudio or DBMGUI
3)
Check and make sure the parameter RUNDIRECTORYPATH is set correctly before starting the database to online mode.
Regarding the corrupted BackupTemplates.xml, here's what you can try:
1)
Install the MaxDB Database Studio
2)
Make a copy and rename the DEV_BackupTemplates.xml to BackupTemplates.xml
3)
Put the BackupTemplates.xml inside the rundirectory - which in your case is "/var/sapdb/DEV/data"
Try running the backup wizard and let me know if you are still getting any errors or warnings.
Regards, Yashwanth
OK, now this is a different issue.
I would like to take a look at the database logs - to be able to identify the reason for backup failure.
Run the dbm command 'diag_pack'
A diag_pack.tgz with all required database logs will be generated in RUNDIRECTORY of the database.
Attach it to the thread.
If you are a SAP customer, It would be better if you open a CSS ticket and attach the logs to the ticket.
Regards, Yashwanth
User | Count |
---|---|
76 | |
10 | |
10 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.