Dispatcher not starting during dialog instance installation

[Former Member]

Hi Experts,

    We are performing an additional instance installation and are facing issue in the start dialog instance phase.

We found that the dispatcher is grey/ not starting up.

I have attached the dev_disp, dev_rd and  dev_w0 logs.

Kindly help us in getting the issue resolved.

Thanks in advance,

Anitha

dev_disp.txt.zip

dev_rd.txt.zip

dev_w0.txt.zip

[Former Member · Accepted solution]

Hi all,

     Thanks for the help and suggestions.

The issue is resolved.

I downloaded the latest SWPM and  kernel and restarted the installation.

And, the installation completed successfully.

Thanks again,

Anitha

[Former Member]

Hi Anitha,

There could be some proble with Oracle Client.

Check for any Warnings/Errors from R3trans.log from App Server.

Also, use DPmon utility to further troubleshoot the error.

Paste the Errors/Warning you find here to help you Solve this issue.

- Santosh Chaitanya

[Former Member]

Hello Anitha,

Is your connection to DB working fine?

regards,

Bala

[Former Member]

Hi Anitha,

While doing Dialog instance installation have you selected correct kernel and oracle client version ?

Cheers

Sharma

[Former Member]

Hi Sharma,

     We have given the correct kernel and client.

Thanks

[sivakumar_kilari3]

Hi Anitha,

Database not connecting, find below error.

Is it non unicode system ?

hu Jun 25 02:14:11 2015

M  calling db_connect ...

B  Loading DB library 'K:\usr\sap\BWD\D00\exe\dboraslib.dll' ...

B  Library 'K:\usr\sap\BWD\D00\exe\dboraslib.dll' loaded

B  Version of 'K:\usr\sap\BWD\D00\exe\dboraslib.dll' is "721.02", patchlevel (0.419)

B  con_info_ext_support(): DBSL supports extended connect protocol

B    ==> connect info for default DB will be read from ssfs

C  dbs/ora/stmt_cache_size = 250

C  Prepending K:\usr\sap\BWD\D00\exe to Path.

C  Register application info.

C  Oracle client version: 0.0.0.0.0, (dbsl 721 030315, non-unicode)

C  Detailed Oracle client (patch) info not available.

C   # CharacterSet                   NCharSet   envhp            errhp            er2hp            bathp          

B  ***LOG BY2=> sql error -1     performing CON [dbsh         1246]

B  ***LOG BY0=> OCI returned error code -1. [dbsh         1246]

B  ***LOG BY2=> sql error -1     performing CON [dblink       544]

B  ***LOG BY0=> OCI returned error code -1. [dblink       544]

M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1525]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11560]

Thanks

Siva

[sivakumar_kilari3]

Try to execute r3trans from your appliaction server?

paste r3trans logs here.

Thanks

Siva

[Former Member]

Hi shiva,

     Yes, it is a non-unicode system.

Thanks

[Former Member]

This is R3trans version 6.24 (release 721 - 14.10.14 - 20:14:08).

non-unicode version

R3trans=>sapparam(1c): No Profile used.

R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

R3trans finished (0000).

trans.log.zip

[sivakumar_kilari3]

check your oralce client version and apply latest dbsl libray files.

Oracle client version: 0.0.0.0.0, (dbsl 721 030315, non-unicode)

[Former Member]

Hello Anitha,

What is the Kernel version. Is it 721 or 721_EXT?

regards,

pavan

Message was edited by: Pavan Kumar Samineni

[Former Member]

It is 721 unicode

[Former Member]

Hi Shiva,

     I have applied the libdbsl patches, still no luck.

got the same error again after retry.

Thanks

[Former Member]

You should use a NUC kernel as it is a NUC system.

At least SAP Kernel version 7.21_EXT is required for Oracle 12c

Have a look at the below note for more info:

2133079 - Oracle Database 12c: Integration in SAP environment

regards,

pavan

[Former Member]

The ABAP work processes are not starting up, and hence the dispatcher is going down.

Kindly help us fix the issue.

[Former Member]

Hi Anitha,

I have asked for oracle client details ? have you selected the correct one ?

Cheers

Sharma