I have an issue with Snap Creator Framework and Sybase agent and would like to share with you all in my workaround.
My environment has detail below.
Snapcreator Server:
- Microsoft Windows Server 2016 Standard Evaluation
- java version "1.8.0_161"
- Snap Creator Framework Version 4.3.1P3
Protection Server:
- SUSE Linux Enterprise Server for SAP Applications 12 SP2
- java version "1.6.0_24"
My Sybase's agent can start normally but failed in the quiescing database step.
# ./scAgent status
Checking Status of scAgent:
Watchdog: Running
Agent: Running
I got an error from Snapcreator GUI below.
########## Application Quiesce ########## INFO: Application Quiesce for plugin : sybase INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Starting INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: Entered INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: No database discovery (+ALL) specified, finishing INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Quiescing database model ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/nNjcrBXLoc.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/QfePbHD3wm.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/RQVQXmQSRM.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/mvkCLr4dk1.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/fXkjfT9s9D.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/KIk6ywsoH9.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/rAThV_WTCe.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/dz_B9HoFe2.sc"] failed with return code 255 and message INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Quiescing database master ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/iwYKenXc1S.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/btFYCDCo8q.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/sQznOdT5Hk.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/WQ3CACm2Hq.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/wVVqbFECAS.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/FO2tYMHwJh.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/18AbTyWmPm.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/sG2WE58JoF.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] failed with return code 255 and message ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00004] SYBASE:QUIESCE: Quiescing databases failed ERROR: [x.x.x.x:9090(4.3.0.0)] SCF-00038: Application quiesce for plug-in [sybase] failed with exit code [255], continuing with backup. INFO: Application quiesce result is empty from plugin sybase. skipping config update operation INFO: Application Quiesce for plugin : sybase finished successfully
Looking more detail in debug logs:
########## Application Quiesce ########## INFO: Application Quiesce for plugin : sybase INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Starting INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: Entered INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: No database discovery (+ALL) specified, finishing INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Quiescing database model DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Checking Database model state DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Executing SQL sequence: DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SELECT CASE WHEN (status3 & 128) = 0 THEN 'Fq' ELSE 'Tq' END AS [(qui)] DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) from master.dbo.sysdatabases where name="model DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) go DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Executing command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] finished with DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) exit code: [255]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stdout: [CT-LIBRARY error: DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stderr: []ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] failed with return code 255 and message DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Database model sql unable to execute : SELECT CASE WHEN (status3 & 128) = 0 THEN 'Fq' ELSE 'Tq' END AS [(qui)] DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) from master.dbo.sysdatabases where name="model - -- - - DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Executing SQL sequence: DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SELECT CASE WHEN status = 1 THEN 'T1' ELSE 'F1' END AS [(mix1)] DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) from master.dbo.sysdatabases where name="master DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) go DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Executing command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] finished with DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) exit code: [255]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stdout: [CT-LIBRARY error: DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stderr: []ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] failed with return code 255 and message DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Database master sql unable to execute : SELECT CASE WHEN status = 1 THEN 'T1' ELSE 'F1' END AS [(mix1)] DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) from master.dbo.sysdatabases where name="master ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00004] SYBASE:QUIESCE: Quiescing databases failed ERROR: [x.x.x.x:9090(4.3.0.0)] SCF-00038: Application quiesce for plug-in [sybase] failed with exit code [255], continuing with backup. INFO: Application quiesce result is empty from plugin sybase. skipping config update operation INFO: Application Quiesce for plugin : sybase finished successfully ########## Application Quiesce finished successfully ##########
I have checked with Sybase DBA, they confirmed database system is working well, no failure on Sybase.
My Workaround
1. Try the same command line on Linux.
Test execute the isql command line directly on Linux with simple SQL statement is working properly.
# cat /tmp/list.db.txt use master go sp_helpdb go # /bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/list.db.txt" name db_size owner dbid created durability lobcomplvl inrowlen status --------------------------------------------------------
This is can be confirmed that no failure on Sybase.
2. I got a lucky mistake.
I found the same error when I mistake with an incomplete command line in Linux.
# su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass"CT-LIBRARY error:
ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.
3. found out a password issue.
Snapcreator:
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] finished with DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) exit code: [255]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stdout: [CT-LIBRARY error: DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.]
compared to execute isql on Linux manual (my lucky mistake):
# su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass"CT-LIBRARY error:
ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.
I supposed that it seems The SnapCreator cannot handle this situation when "sapsa" password is content with "#".
because of it same as me execute with an incomplete command line.
This is just my assumption need to prove it.
4. Solution:
> Changing "sapsa" password to a simple password must without "#".
5. Woo!! it's proved!!
Any suggestion welcome if you have an experience like this.
Hope this post is helpful for everyone 