cancel
Showing results for 
Search instead for 
Did you mean: 

Running but dialog Queue standstill

Former Member
0 Kudos

Hello Everyone.

i encountered following problem - when i start SAP instance via SAP MMC the dispatcher has status "Running but dialog Queue standstill". Connection via SAP GUI not available.

dev_w1 have no errors and at the:

<b>

M Wed Jun 11 15:34:01 2008

M calling db_connect ...

C Prepending C:\usr\sap\SLM\DVEBMGS11\exe to Path.

C Oracle Client Version: '10.2.0.1.0'

C Client NLS settings: AMERICAN_AMERICA.UTF8

C Logon as OPS$-user to get SAPSR3's password

C Connecting as /@SLM on connection 0 (nls_hdl 0) ... (dbsl 700 250407)

C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch

C 0 UTF8 1 05D89B48 05D8F0E4 05D8E96C

C Attaching to DB Server SLM (con_hdl=0,svchp=05D8E8B8,srvhp=05DA04A4)

</b>

So the SAP work process trying to connect to the Oracle as /@SLM.

I try to connect to the Oracle via sqlplus and it's hangs:

<b>

C:\Documents and Settings\slmadm>sqlplus /nolog

SQL*Plus: Release 10.2.0.2.0 - Production on Wed Jun 11 16:22:51 2008

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

SQL> conn /@slm

</b>

Is there any ideas what happening?

regards,

Denis

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Check if there is a problem with Oracle;

Archiver stuck perhaps?

Any error messages in the alert log file?

Former Member
0 Kudos

Hello Joe.

Not archiver stuck.

I think problems with listener.

I can connect as sysdba and as / but not as /@<sid>.

regards,

Denis

Former Member
0 Kudos

Hi

Check these commands:

tnsping <SID> if unsuccessful, then please check tnsnames.ora file.

lsnrctl status: if not started give lsnrctl start then give tnsping <SID> it must be successful.

Then please try to connect to SID.

then give simple sqlplus command, you must be able to go to sql prompt. else check the database state.

Former Member
0 Kudos

Hello Deepak Sharma.

tnsping successful. As i mentioned early conn / as sysdba is successful.

so problem is solved. the port was wrong.

regards,

Denis

Former Member
0 Kudos

So what is the correct port? I ´m with the same error