Re: Snapcreator problem after Changing target path of system

Hello Sahana,

thanks for your reply.

I already know this error list. I also know that the error scf-00103 means that it does not find the command or runs on the wrong host.
But what does the return code 512 mean? And why are there no errors in the agent log files?

XXX.debug.20180104024656.agent.log
[Thu Jan  4 02:46:57 2018] INFO: Starting watchdog with [26445], forced unquiesce timeout [300] second(s)
[Thu Jan  4 02:46:57 2018] INFO: Removing log /opt/NetApp/scAgent3.6.0/logs/P-Landschaft/XXX.out.20171219024557.agent.log
[Thu Jan  4 02:46:57 2018] INFO: Removing log /opt/NetApp/scAgent3.6.0/logs/P-Landschaft/XXX.debug.20171219024557.agent.log
[Thu Jan  4 02:46:57 2018] INFO: Removing log /opt/NetApp/scAgent3.6.0/logs/P-Landschaft/XXX.stderr.20171219024557.agent.log
[Thu Jan  4 02:46:57 2018] INFO: Quiescing databases
[Thu Jan  4 02:46:57 2018] INFO: Quiescing database XXX
[Thu Jan  4 02:46:57 2018] DEBUG: Executing SQL sequence:
connect to XXX;
set write suspend for database;
connect reset;
[Thu Jan  4 02:48:49 2018] DEBUG: Command [su - db2XXX -c "/db2/db2XXX/db2_software_v105/bin/db2 -tvf /tmp/cOJLSon24O.sc"] finished with
exit code: [0]
stdout: [connect to XXX

  Database Connection Information

Database server        = DB2/LINUXX8664 10.5.7
SQL authorization ID   = DB2XXX
Local database alias   = XXX


set write suspend for database
DB20000I  The SET WRITE command completed successfully.

connect reset
DB20000I  The SQL command completed successfully.]
stderr: []
[Thu Jan  4 02:48:49 2018] INFO: Quiescing database XXX finished successfully
[Thu Jan  4 02:48:49 2018] INFO: Quiescing databases finished successfully
[Thu Jan  4 02:48:49 2018] INFO: Unquiescing databases
[Thu Jan  4 02:48:49 2018] INFO: Unquiescing database XXX
[Thu Jan  4 02:48:49 2018] DEBUG: Executing SQL sequence:
connect to XXX;
set write resume for database;
connect reset;
[Thu Jan  4 02:50:41 2018] DEBUG: Command [su - db2XXX -c "/db2/db2XXX/db2_software_v105/bin/db2 -tvf /tmp/p8MNb4yOww.sc"] finished with
exit code: [0]
stdout: [connect to XXX

  Database Connection Information

Database server        = DB2/LINUXX8664 10.5.7
SQL authorization ID   = DB2XXX
Local database alias   = XXX


set write resume for database
DB20000I  The SET WRITE command completed successfully.

connect reset
DB20000I  The SQL command completed successfully.]
stderr: []
[Thu Jan  4 02:50:41 2018] INFO: Unquiescing database XXX finished successfully
[Thu Jan  4 02:50:41 2018] INFO: Unquiescing databases finished successfully

Increasing the timeout value didn't deliver the desired success. Last night the backup was aborted again.