Enable debugging via util file and you will get more information. Also, if they did refresh, they might have used sap/utl files from prod so please check if these files are back to reflect settings for this instance.
daemon.raw doesn't indicate anything that I can see.
What is a "utl" file? Is that a Networker thing, an Oracle thing, or an SAP thing?
Anyway, one of my colleagues seems to have gotten it working again. He quotes some "article #000119532" that says to set the job inactivity timeout to zero. Now the backups are running to completion, successfully.
utl file is SAP thing found in $ORACLE_HOME/dbs and reflecting backup application configuration. You can call it directly from CFG file in BR_EXEC line. Related is sap file where you specify util file to be used. In SAP world these are called profile and parameter files.
bingo.1
2.4K Posts
0
February 20th, 2014 12:00
I am pretty sure that this does not mean anything else but that the job has been initiated but does not respond (immediately or after a while).
If this happens immediately, i would expect connection/login problems.
If this happens later during the save, the communication was interrupted or the NW client daemon hangs.
The logs/applog files on the client should provide more info.
bingo.1
2.4K Posts
0
February 20th, 2014 12:00
And what does the daemon.raw on th server indicate? - It should monitor the process.
ble1
4 Operator
•
14.4K Posts
0
February 20th, 2014 12:00
Enable debugging via util file and you will get more information. Also, if they did refresh, they might have used sap/utl files from prod so please check if these files are back to reflect settings for this instance.
M_Kirsch
1 Rookie
•
11 Posts
0
February 20th, 2014 12:00
That's the problem. The applog files don't provide any more information.
They simply say "interrupted."
M_Kirsch
1 Rookie
•
11 Posts
0
February 21st, 2014 06:00
daemon.raw doesn't indicate anything that I can see.
What is a "utl" file? Is that a Networker thing, an Oracle thing, or an SAP thing?
Anyway, one of my colleagues seems to have gotten it working again. He quotes some "article #000119532" that says to set the job inactivity timeout to zero. Now the backups are running to completion, successfully.
ble1
4 Operator
•
14.4K Posts
0
February 21st, 2014 07:00
utl file is SAP thing found in $ORACLE_HOME/dbs and reflecting backup application configuration. You can call it directly from CFG file in BR_EXEC line. Related is sap file where you specify util file to be used. In SAP world these are called profile and parameter files.