on 02-05-2009 7:40 AM
Good morning!
I´m not sure if this is the right subforum for backup questions, but in the end it has something todo with the database.
We have this problem for some time now. After a complete SAP and server reboot all planned backups (DB13) are running fine. Then after a week the jobs suddenly stop and are marked red in DB13.
The job protocol says:
04.02.2009 22:00:27 Error! Connection failed to node sapproddb for database PRD:
04.02.2009 22:00:27 tp error:
04.02.2009 22:00:27 External program terminated with exit code 2
04.02.2009 22:00:27 DBMCLI returned error status E
04.02.2009 22:00:27 Job ended
Normally the job copies the logs into a file on a server node (it´s a two-node cluster with the database on node2) into a folder on E: ackupPRD_LOG (I see a PRD_COM right now). Somehow this isn´t working after a time.
Strange thing is: We can start the job manually, so there´s no problem with the server or the diskspace. What else can we look into?
Thanks for any help!
kind regards, Peter
Edited by: Jan-Peter Selter on Feb 5, 2009 8:42 AM
Hello Peter
-> It's looking that the connection to the database using the dbmrfc
failed due the 'tp error'.
Test two TCP/IP links SAPDB_DBM and SAPDB_DBM_DAEMON in /nsm59.
Please run the 'connection test' in /ndb59.
What errors did you see?
-> What version of the MAXDB client software installed on the application server?
What version of tp /SAP kernel you currently have on the system?
-> "Then after a week the jobs suddenly stop and are marked red in DB13."
Did you see any errors in the logs on application server, transaction /nst11?
-> Did you already create the OSS ticket on this issue?
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 |
---|---|
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.