Skip to Content
avatar image
Former Member

start instance failed with error

Hello Dears,

we are installing SAP NW 7.5 on SLES 11 SP4 on ASE 16.0.2.5 with kernel 7.45 UC

and in phase start instance we faced the error:

State of instance JGQ/D00 changed from ABAP: STARTING to ABAP: UNKNOWN.

ERROR 2017-03-13 22:46:44.762 (root/sapinst) id=nw.progress.startupFailed errno=CJS-30105
Instance JGQ/D00 reached state UNKNOWN after having state STARTING. Giving up.

ERROR 2017-03-13 22:46:44.913 (root/sapinst) id=controller.stepExecuted errno=FCO-00011
The step start with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_CI_Instance_Start|ind|ind|ind|ind|40|0|start was executed with status ERROR ( Last error reported by the step: Instance JGQ/D00 reached state UNKNOWN after having state STARTING. Giving up.).

INFO 2017-03-13 22:46:47.836 (root/sapinst)
Creating file /tmp/sapinst_instdir/NW750/SYB/INSTALL/STD/ABAP/INSTANA.XML.

INFO 2017-03-13 22:46:48.114 (root/sapinst)
Creating file /tmp/sapinst_instdir/NW750/SYB/INSTALL/STD/ABAP/instslana.xml.

and I attached all logs and hosts files for our QAS system except one files from PRD because all three systems has the same error, please review and advise us


we ensured that the SWAP memory is configured correctly and we reviewed the hosts file and we find all things are OK.

we also restarted the installation on different hosts with the same configurations and we faced the same error.

defaultpfl.txt (1.0 kB)
dev-dispdat.txt (65.3 kB)
dev-disp.txt (65.3 kB)
dev-rddat.txt (4.4 kB)
dev-rd.txt (4.4 kB)
dev-w0.txt (4.3 kB)
hosts.txt (802 B)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Mar 27, 2017 at 02:10 PM

    Hi Karem,

    Work process 0 trace file shows issues when connecting to Database on March 8th:
    B ***LOG BV3=> severe db error 30012; work process is stopped [dbsh 1257]
    B ***LOG BY2=> sql error 30012 performing CON [dblink 647]
    B ***LOG BY0=> [ASE Error SQL30294:HY000][SAP][ASE ODBC Driver]There is no server listening at qasgwsap:4901.[ASE Error SQL30012:08001][SAP][ASE ODBC Driver]Client unable to establish a connection [dblink 647]
    M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 86]

    But it seems that server was started again afterwards, Dispatcher trace file shows the following, when starting on March 12th:

    ***LOG Q0K=> DpMsAttach, mscon ( qasgwsap) [dpMessageSer 1685]
    *** DP_FATAL_ERROR => DpMsAttach: local hostname 'qasgwsap' is resolved to loopback address (cf. SAP note 1054467 for details)

    *** DISPATCHER EMERGENCY SHUTDOWN ***

    and then, server is shut down. You should review mentioned Note:
    1054467 - Local host name refers to loopback address
    Ensure that host name of the instance is not be resolved for a loopback address

    Regards,
    Raquel

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Karem,

      You have attached the "hosts" file to this question and I can see that the hostname is indeed associated to the loopback interface (IP address 127.0.0.2).

      Raquel nailed it :-). You need to fix the hostname resolution.

      Regards,

      IsaĆ­as

  • Mar 15, 2017 at 12:22 PM
    ***LOG BV3=> severe db error 30012; work process is stopped [dbsh         1257]
    B  ***LOG BY2=> sql error 30012  performing CON [dblink       647]
    B  ***LOG BY0=> [ASE Error SQL30294:HY000][SAP][ASE ODBC Driver]There is no server listening at qasgwsap:4901.[ASE Error SQL30012:08001][SAP][ASE ODBC Driver]Client unable to establish a connection [dblink       647]
    M  ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 86]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c   2542]

    Seems like your database is not running...

    Regards, JP

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 11, 2017 at 06:35 AM
    -1

    dears thank you for your help the problem had solved by giving permission to DB LOG FILE

    Regards

    Karem

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 15, 2017 at 02:24 PM

    dear Juan,

    we ran command R3trans -d and we got no error, and we stopped and start the data base using command startsap DB jgq and also started successfully and appeared in top command result

    regards

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 15, 2017 at 03:19 PM

    Hi,

    Re-check the below values in default.pfl. especially port, possibly DB was not installed with standard port.

    dbs/syb/schema = SAPSR3
    dbs/syb/server = qasgwsap
    dbs/syb/dbname = JGQ
    dbs/syb/port = 4901
    
    Refer Note 2166229 as well.
    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      dear Imtiaz,

      thx for your reply, we already had the same profile parameter in our default.profile as we attached in my original message above. :( we still don't know why the SWPM can't start the instance

      regards