Dispatcher running but Dialog queue standstill

[former_member214784]

Hi

I installed minisap in my laptop, after finishing the installation

i ran the sgen, during the middle of sgen the system got struck.

I tried to restart the SAP system but the SAP not starting,

I am getting that disp+work.exe is running, but dailog queue standstill..

please help me for to overcome this problem

by

vinodh

[former_member4224]

Hi,

the dialog queue standstill is the dispathcer queue.

Probably all work process are in use or stuck.

you can check the work process status using dpmon

dpmon pf=<instance profile> l

If no work process available to use the dispatcher queue will lead to such situation.

Maybe you need to restart the system but try to pinpoint what is happening with the work process.

Clebio

[Reagan]

Hello

You must be having issue with the Log ares being full.

Install MaxDB Database Studio and connect to the database and check that.

You can take a backup using this tool.

Regards

RB

[karthikeyan_natarajan4]

Hi Vinod,

Please refer this http://wiki.scn.sap.com/wiki/display/MaxDB/Log+Area+Full

regards

kartik

[Former Member]

Hi,

Try this,

1.  Logon with sqdsid       #Maxdb server db owner

2.  dbmcli -d SID -u control,password of control

3.  db_admin                 # gets db into admin mode

4.  util_execute clear log   # truncate logs immediately

5.  db_online                # sets db from admin into online mode

Thanks

Rishi Abrol

[Former Member]

Hi Vinodh,

Either you switch off archive log or empty the redo log file from the disk.

As Juan said post dev_w0 log that may say everything.

All the best,

Zaki

[JPReyes]

This sounds like simply your DB logs are full, take a log backup and the system will respond again.

Regards, Juan

[former_member214784]

Hi Mr.Juan,

     I took backup and started the system, I am getting the same problem...

Regards, Vinodh

[JPReyes]

Can you post the dev_w0 log?... what DB are you using?...

Regards, Juan

[former_member214784]

Dear Juan,

I am pasting the dev_w0 log, and I am using MAXDB

---------------------------------------------------

trc file: "dev_w0", trc level: 1, release: "720"

---------------------------------------------------

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      all, MJ

*

M sysno      00

M sid        NSP

M systemid   562 (PC with Windows NT)

M relno      7200

M patchlevel 0

M patchno    201

M intno      20020600

M make       multithreaded, Unicode, 64 bit, optimized

M profile    \\nagavinodh\sapmnt\NSP\SYS\profile\NSP_DVEBMGS00_nagavinodh

M pid        4432

M

M  kernel runs with dp version 133000(ext=118000) (@(#) DPLIB-INT-VERSION-133000-UC)

M  length of sys_adm_ext is 588 bytes

M  ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 4432) [dpxxdisp.c   1377]

I  MtxInit: 30000 0 0

M  DpSysAdmExtCreate: ABAP is active

M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M  DpIPCInit2: read dp-profile-values from sys_adm_ext

M  DpShMCreate: sizeof(wp_adm)                    31696          (2264)

M  DpShMCreate: sizeof(tm_adm)                    5517056          (27448)

M  DpShMCreate: sizeof(wp_ca_adm)                    64000          (64)

M  DpShMCreate: sizeof(appc_ca_adm)          64000          (64)

M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080

M  DpShMCreate: sizeof(comm_adm)                    584080          (1144)

M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M  DpShMCreate: sizeof(slock_adm)                    0          (296)

M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M  DpShMCreate: sizeof(file_adm)                    0          (80)

M  DpShMCreate: sizeof(vmc_adm)                    0          (2152)

M  DpShMCreate: sizeof(wall_adm)                    (41664/42896/64/192)

M  DpShMCreate: sizeof(gw_adm)          48

M  DpShMCreate: sizeof(j2ee_adm)          3952

M  DpShMCreate: SHM_DP_ADM_KEY                    (addr: 000000000FCC0050, size: 6363600)

M  DpShMCreate: allocated sys_adm at 000000000FCC0060

M  DpShMCreate: allocated wp_adm_list at 000000000FCC3070

M  DpShMCreate: allocated wp_adm at 000000000FCC3260

M  DpShMCreate: allocated tm_adm_list at 000000000FCCAE40

M  DpShMCreate: allocated tm_adm at 000000000FCCAE90

M  DpShMCreate: allocated wp_ca_adm at 000000001020DDA0

M  DpShMCreate: allocated appc_ca_adm at 000000001021D7B0

M  DpShMCreate: allocated comm_adm at 000000001022D1C0

M  DpShMCreate: system runs without slock table

M  DpShMCreate: system runs without file table

M  DpShMCreate: allocated vmc_adm_list at 00000000102BBB60

M  DpShMCreate: system runs without vmc_adm

M  DpShMCreate: allocated gw_adm at 00000000102BBC10

M  DpShMCreate: allocated j2ee_adm at 00000000102BBC50

M  DpShMCreate: allocated ca_info at 00000000102BCBD0

M  DpShMCreate: allocated wall_adm at 00000000102BCC60

M  DpCommAttachTable: attached comm table (header=000000001022D1C0/ft=000000001022D1D0)

M  DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm

M  rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80

X  EmInit: MmSetImplementation( 2 ).

X  MM global diagnostic options set: 0

X  <ES> client 0 initializing ....

X  <ES> EsILock: use spinlock for locking

X  Using implementation view

X  <EsNT> Using memory model view.

M  <EsNT> Memory Reset disabled as NT default

X  ES initialized.

X  mm.dump: set maximum dump mem to 96 MB

M  DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

M  ThStart: taskhandler started

M  ThInit: initializing DIA work process W0

M 

M Wed Sep 25 20:28:41 2013

M  ThInit: running on host nagavinodh

M  calling db_connect ...

B  Loading DB library 'D:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...

B  Library 'D:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded

B  Version of 'D:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "720.00", patchlevel (0.201)

C 

C  DBSDBSLIB : version 720.00, patch 0.201 (Make PL 0.201)

C  MAXDB shared library (dbsdbslib) patchlevels (last 10)

C    (0.201) Take care of warnings during database connect (note 1600066)

C    (0.117) Define a primary key on the temp tables for R3szchk (note 1606260)

C    (0.114) Support of MaxDB 7.8 and 7.9 (note 1653058)

C    (0.103) Close all lob locators at end of the transaction (note 1626591)

C    (0.101) Fix for unknown table __TABLE_SIZES_ (R3szchk) (note 1619504)

C    (0.098) Use filesystem counter for R3szchk (note 1606260)

C    (0.092) Secondary connection to HANA (note 1481256)

C    (0.089) UPDSTAT with SAPSYSTEMNAME longer as 3 characters (note 1584921)

C    (0.081) No UPSERT on WBCROSSGT (note 1521468)

C    (0.080) New feature batch streaming (note 1340617)

C 

C 

C  Loading SQLDBC client runtime ...

C  SQLDBC Module  : D:\sapdb\clients\NSP\pgm\libSQLDBC77.dll

C  SQLDBC SDK     : SQLDBC.H  7.9.7    BUILD 010-123-243-190

C  SQLDBC Runtime : libSQLDBC 7.9.7    BUILD 010-123-243-190

C  SQLDBC client runtime is MaxDB 7.9.7.010 CL 243190

C  SQLDBC supports new DECIMAL interface : 1

C  SQLDBC supports VARIABLE INPUT data   : 1

C  SQLDBC supports VARIABLE OUTPUT data  : 1

C  SQLDBC supports Multiple Streams      : 1

C  SQLDBC supports LOB LOCATOR KEEPALIVE : 1

C  SQLDBC supports LOB LOCATOR COPY      : 1

C  SQLDBC supports BULK SELECT with LOBS : 1

C  SQLDBC supports BATCH STREAM          : 1

C  WARNING : TCP/IP service (sql6) in etc/services missing!

C  INFO : SQLOPT= -I 0 -t 0 -S SAPR3

C  Try to connect (DEFAULT) on connection 0 ...

C  Attach to SAP DB : Kernel    7.9.07   Build 010-123-243-190

C  Database release is SAP DB 7.9.07.010

C  INFO : Database 'NSP' instance is running on 'nagavinodh'

C  DB supports UPSERT SQL syntax : 1

C  DB supports new EXPAND syntax : 1

C  DB supports LOB locators      : 1

C  DB uses MVCC support          : 0

C  DB max. input host variables  : 2000

C  DB max. statement length      : 65535

C  UPSERT is disabled for : WBCROSSGT

C 

C Wed Sep 25 20:28:42 2013

C  INFO : SAP DB Packet_Size = 131072

C  INFO : SAP DB Min_Reply_Size = 4096

C  INFO : SAP DB Comm_Size = 126976

C  INFO : DBSL buffer size = 126976

C  INFO : SAP DB MaxLocks = 300000

C  INFO : Connect to DB as 'SAPNSP'

C  Command info enabled

C  Now I'm connected to MaxDB

C  00: nagavinodh-NSP, since=20130925202841, ABAP= <unknown> (0)

B  Connection 0 opened (DBSL handle 0)

C  INFO : SAP RELEASE (DB) = 731

M  ThInit: db_connect o.k.

M  ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png,*.swc,*.swf

by

vinodh

[JPReyes]

Nothing there.

A backup is not what you need, you need a LOG backup.

Regards, Juan