Database Inconsistency: Start Transaction SICK.

[Former Member]

Database inconsistency: Start Transaction SICK.

Hello All,

Every-time I logged to my SAP system I came to ERROR dump.

" Database inconsistency: Start Transaction SICK."

Our every user has the same problem.

At start it gives this message bu after that I can use other transactions without any problem.

When I used transaction SICK it gives me following error message.

"SAP System Check

enqueue name is empty

Severe problems were detected during initial system check.

Please, do not use that system before fixing these problems. "

I am giving error message of ST22 dump analysis

" Runtime Errors START_CALL_SICK

Date and Time 07.03.2014 14:20:38

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

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

|Short text |

| Database inconsistency: Start Transaction SICK. |

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

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

|What happened? |

| The current program had to be terminated because of an |

| error when installing the R/3 System. |

| The error occurred when initializing the R/3 System. |

| - |

| |

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

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

|What can you do? |

| Please call the Transaction SICK. The list generated here |

| contains an installation error. |

| Note which actions and input led to the error. |

| |

| For further help in handling the problem, contact your SAP administrator |

| . |

| |

| You can use the ABAP dump analysis transaction ST22 to view and manage |

| termination messages, in particular for long term reference. |

| |

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

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

|Error analysis |

| |

| The error probably occurred when installing the |

| R/3 system. |

| Error text of the first reported error: |

| "enqueue name is empty". |

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

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

|How to correct the error |

| |

| Report the error to the group responsible for installing your |

| R/3 System. |

| |

| If the error occures in a non-modified SAP program, you may be able to |

| find an interim solution in an SAP Note. |

| If you have access to SAP Notes, carry out a search with the following |

| keywords: |

| |

| "START_CALL_SICK" " " |

| "SAPMSYST" or "SAPMSYST" |

| "D020_SNC_CHECK_EXTID" |

| |

| If you cannot solve the problem yourself and want to send an error |

| notification to SAP, include the following information: |

| |

| 1. The description of the current problem (short dump) |

| |

| To save the description, choose "System->List->Save->Local File |

| (Unconverted)". |

| |

| 2. Corresponding system log |

| |

| Display the system log by calling transaction SM21. |

| Restrict the time interval to 10 minutes before and five minutes |

| after the short dump. Then choose "System->List->Save->Local File |

| (Unconverted)". |

| |

| 3. If the problem occurs in a problem of your own or a modified SAP |

| program: The source code of the program |

| In the editor, choose "Utilities->More |

| Utilities->Upload/Download->Download". |

| |

| 4. Details about the conditions under which the error occurred or which |

| actions and input led to the error. |

| |

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

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

|System environment |

| SAP-Release 700 |

| |

| Application server... "XXXXX" |

| Network address...... "0.0.0.0" |

| Operating system..... "Windows NT" |

| Release.............. "5.2" |

| Hardware type........ "4x AMD64 Level" |

| Character length.... 16 Bits |

| Pointer length....... 64 Bits |

| Work process number.. 3 |

| Shortdump setting.... "full" |

| |

| Database server... "XXXX" |

| Database type..... "MSSQL" |

| Database name..... "XXX" |

| Database user ID.. "XXX" |

| |

| Terminal................. "XX" |

| |

| Char.set.... "C" |

| |

| SAP kernel....... 700 |

| created (date)... "Dec 14 2009 17:59:36" |

| create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00" |

| Database version. "SQL_Server_8.00 " |

| |

| Patch level. 236 |

| Patch text.. " " |

| |

| Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194" |

| SAP database version. 700 |

| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |

| NT 6.0, Windows NT 6.1" |

| |

| Memory consumption |

| Roll.... 16192 |

| EM...... 4189840 |

| Heap.... 0 |

| Page.... 0 |

| MM Used. 851136 |

| MM Free. 3336080 |

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

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

|User and Transaction |

| |

| Client.............. 800 |

| User................ "XXXXX" |

| Language key........ "E" |

| Transaction......... "SESSION_MANAGER " |

| Transactions ID..... "8AD5A5E3620EF1A8B940E41F133A240E" |

| |

| Program............. "SAPMSYST" |

| Screen.............. "SAPMSYST 0020" |

| Screen line......... 74 |

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

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

|Information on where terminated |

| Termination occurred in the ABAP program "SAPMSYST" - in |

| "D020_SNC_CHECK_EXTID". |

| The main program was "SAPMSYST ". |

| |

| In the source code you have the termination point in line 1770 |

| of the (Include) program "SAPMSYST". |

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

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

|Contents of system fields |

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

|Name |Val. |

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

|SY-SUBRC|0 |

|SY-INDEX|0 |

|SY-TABIX|8 |

|SY-DBCNT|0 |

|SY-FDPOS|0 |

|SY-LSIND|0 |

|SY-PAGNO|0 |

|SY-LINNO|1 |

|SY-COLNO|1 |

|SY-PFKEY|0020 |

|SY-UCOMM| |

|SY-TITLE|System Program |

|SY-MSGTY| |

|SY-MSGID| |

|SY-MSGNO|000 |

|SY-MSGV1| |

|SY-MSGV2| |

|SY-MSGV3| |

|SY-MSGV4| |

|SY-MODNO|0 |

|SY-DATUM|20140307 |

|SY-UZEIT|142038 |

|SY-XPROG|SAPCNVE |

|SY-XFORM|CONVERSION_EXIT |

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

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

|Active Calls/Events |

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

|No. Ty. Program Include Line |

| Name |

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

| 1 MODULE (PAI) SAPMSYST SAPMSYST 1770 |

| D020_SNC_CHECK_EXTID |

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

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

|Chosen variables |

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

|Name |

| Val. |

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

|No. 1 Ty. MODULE (PAI) |

|Name D020_SNC_CHECK_EXTID |

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

|RC |

| 0 |

| 0000 |

| 0000 |

|SY-REPID |

| SAPMSYST |

| 5454555522222222222222222222222222222222 |

| 310D393400000000000000000000000000000000 |

| 0000000000000000000000000000000000000000 |

| 0000000000000000000000000000000000000000 |

|RSYST-FCODE |

| |

| 22222222222222222222 |

| 00000000000000000000 |

| 00000000000000000000 |

| 00000000000000000000 |

|C_MAXUSR |

| 312 |

| 3000 |

| 8100 |

|MULTI_LOGON_TAB-LOGON_TIME |

| 000000 |

| 333333 |

| 000000 |

| 000000 |

| 000000 |

|RSYST-MANDT |

| 800 |

| 333 |

| 800 |

| 000 |

| 000 |

|SYST-REPID |

| SAPMSYST |

| 5454555522222222222222222222222222222222 |

| 310D393400000000000000000000000000000000 |

| 0000000000000000000000000000000000000000 |

| 0000000000000000000000000000000000000000 |

|RSYST-BNAME |

| RBKHANDARE |

| 544444445422 |

| 22B81E412500 |

| 000000000000 |

| 000000000000 |

|RSYST-BCODE |

| |

| 2222222222222222222222222222222222222222 |

| 0000000000000000000000000000000000000000 |

| 0000000000000000000000000000000000000000 |

| 0000000000000000000000000000000000000000 |

|SCREEN |

| IUSRACL-BNAME |

| 4555444244444222222222222222222222222222222222222222222222222222222222222222222222222222222222|

| 953213CD2E1D5000000000000000000000000000000000000000000000000000000000000000000000000000000000|

| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|

| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|

|SY-MSGID |

| |

| 22222222222222222222 |

| 00000000000000000000 |

| 00000000000000000000 |

| 00000000000000000000 |

|NEWCODE |

| |

| 22222222 |

| 00000000 |

| 00000000 |

| 00000000 |

|PWD_RC |

| 0 |

| 0000 |

| 0000 |

|SPACE |

| |

| 2 |

| 0 |

| 0 |

| 0 |

|SY-MSGNO |

| 000 |

| 333 |

| 000 |

| 000 |

| 000 |

|C_LOW_DATE |

| 19000101 |

| 33333333 |

| 19000101 |

| 00000000 |

| 00000000 |

|SY-MSGV1 |

| |

| 22222222222222222222222222222222222222222222222222 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

|SY-MSGV2 |

| |

| 22222222222222222222222222222222222222222222222222 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

|SY-MSGV3 |

| |

| 22222222222222222222222222222222222222222222222222 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

|SY-MSGV4 |

| |

| 22222222222222222222222222222222222222222222222222 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

| 00000000000000000000000000000000000000000000000000 |

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

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

|Internal notes |

| The termination was triggered in function "ab_check_sick" |

| of the SAP kernel, in line 2816 of the module |

| "//bas/700_REL/src/krn/runt/abinit.c#22". |

| The internal operation just processed is "----". |

| Internal mode was started at 20140307142032. |

| |

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

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

|Active Calls in SAP Kernel |

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

|Lines of C Stack in Kernel (Structure Differs on Each Platform) |

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

|SAP (R) - R/3(TM) Callstack, Version 1.0 |

|Copyright (C) SAP AG. All rights reserved. |

|Callstack without Exception: |

|App : disp+work.EXE (pid=4420) |

|When : 3/7/2014 14:20:38.796 |

|Threads : 2 |

|Computer Name : XXXXXX |

|User Name : XXXX |

|Number of Processors: 4 |

|Processor Type: EM64T Family 6 Model 26 Stepping 5 |

|Windows Version : 5.2 Current Build: 3790 |

|State Dump for Thread Id ce0 |

|FramePtr ReturnAd Param#1 Function Name |

|00000000082e7f90 0000000077d704ff 000000005f9e38f0 ntdll!ZwWaitForSingleObject |

|00000000082e8030 000000000177faa1 0000000000000250 kernel32!WaitForSingleObjectEx |

|00000000082e8280 00000000006211b5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)] |

|00000000082e82b0 0000000000b22d8c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)] |

|00000000082e8300 0000000000b28221 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7257)] |

|00000000082e8ce0 0000000000b536ff 0000000001dde700 disp+work!ab_rabax [abrabax.c (1271)] |

|00000000082e8d20 0000000000701294 00000000082e0000 disp+work!ab_check_errors [abinit.c (2829)] |

|00000000082e8e30 0000000000704c94 0000000000000308 disp+work!DyISigni [sign.c (1492)] |

|00000000082e8f30 0000000000684456 000000000000000a disp+work!syssigni [sign.c (748)] |

|00000000082e90c0 00000000006890fa 000007fe5720d45e disp+work!dynpmcal [dymainstp.c (2381)] |

|00000000082e9160 000000000068838a 0000000000000000 disp+work!dynppai0 [dymainstp.c (1117)] |

|00000000082e9210 00000000006424c3 0000000000000000 disp+work!dynprctl [dymainstp.c (361)] |

|00000000082efc30 00000000004e0a70 0000000000000002 disp+work!dynpen00 [dymain.c (1920)] |

|00000000082efeb0 000000000043052b 000000000ab6f080 disp+work!TskhLoop [thxxhead.c (4651)] |

|00000000082efee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1166)] |

|00000000082eff10 0000000001a35ff1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)] |

|00000000082eff70 0000000077d596ac 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)] |

|00000000082effa0 0000000000000000 0000000001a35e80 kernel32!BaseProcessStart |

|State Dump for Thread Id 1320 |

|FramePtr ReturnAd Param#1 Function Name |

|000000000f3cfe40 0000000077d5f6f1 0000000000000000 ntdll!NtFsControlFile |

|000000000f3cfeb0 000000000191b87f fffffffffffffffe kernel32!ConnectNamedPipe |

|000000000f3cff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)] |

|000000000f3cff70 0000000077d6b71a 0000000077d6b6e0 msvcrt!endthreadex |

|000000000f3cffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart |

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

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

|List of ABAP programs affected |

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

|Index |Typ|Program |Group |Date |Time |Size |Lang. |

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

| 0|Prg|SAPMSYST | 0|31.01.2010|16:12:06| 111616|E |

| 1|Typ|RSYST | 0|19.07.2004|10:44:06| 11264| |

| 2|Prg|SAPMSSYD | 0|12.09.2006|11:33:31| 21504|E |

| 3|Prg|SAPFSYSCALLS | 0|09.09.2004|14:18:32| 7168|E |

| 4|Typ|DOKIL | 0|12.05.1997|16:46:17| 3072| |

| 5|Typ|TLINE | 0|08.03.1992|00:19:59| 2048| |

| 6|Prg|%_CCXTAB | 0|18.02.2005|14:15:08| 7168|E |

| 7|Typ|SCXTAB_CONTROL | 0|18.05.2004|14:07:29| 6144| |

| 8|Prg|SAPLSNCA | 8|11.09.2007|13:17:45| 37888|E |

| 9|Prg|SAPCNVE | 9|09.09.2004|14:36:10| 8192|E |

| 10|Prg|SAPLLANG | 10|10.09.2007|14:53:12| 10240|E |

| 11|Prg|SAPFSPOR | 0|09.09.2004|14:18:32| 14336|E |

| 12|Prg|SAPLSCNT | 12|18.02.2005|14:16:06| 30720|E |

| 13|Typ|DYCBOX | 0|20.08.1998|11:16:53| 3072| |

| 14|Prg|SAPLSVSM | 14|31.01.2010|16:11:30| 28672|E |

| 15|Prg|SAPLSGUI | 15|17.12.2007|15:41:05| 84992|E |

| 16|Prg|SAPLSTTM | 16|05.07.2005|13:10:18| 69632|E |

| 17|Prg|SAPLSBDC | 17|17.12.2007|15:30:54| 44032|E |

| 18|Prg|CL_DATAPROVIDER===============CP | 18|28.02.2005|21:00:46| 49152|E |

| 19|Prg|%_CCNTL | 18|18.02.2005|14:15:08| 15360|E |

| 20|Typ|OBJ_RECORD | 0|14.02.1998|08:30:43| 2048| |

| 21|Prg|SAPLSTUP | 21|31.01.2010|19:19:23| 74752|E |

| 22|Prg|SAPLCNDP | 22|31.01.2010|20:41:58| 197632|E |

| 23|Prg|SAPSHDTV | 12|05.01.2005|16:26:16| 33792|E |

| 24|Prg|SAPFGUICNTL | 0|18.02.2005|14:15:08| 24576|E |

| 25|Prg|SAPLOLEA | 25|31.01.2010|20:44:43| 96256|E |

| 26|Prg|SAPLSFES | 26|31.01.2010|20:50:59| 264192|E |

| 27|Prg|SAPLTHFB | 27|31.01.2010|20:47:20| 394240|E |

| 28|Typ|WPINFO | 0|26.02.1999|14:49:01| 6144| |

| 29|Prg|SAPLURFC | 29|17.12.2007|15:37:35| 22528|E |

| 30|Prg|SAPLSPLUGIN | 30|09.09.2004|14:18:36| 8192|E |

| 31|Typ|SWCBCONT | 0|15.11.2000|17:55:11| 3072| |

| 32|Typ|OLE_VERBS | 0|04.04.1995|16:02:20| 2048| |

| 33|Typ|OLE_PA | 0|04.04.1995|16:02:19| 2048| |

| 34|Prg|CL_GUI_PROPS_CONSUMER=========CP | 34|31.01.2010|11:43:32| 29696|E |

| 35|Typ|EUDB | 0|06.11.2003|20:28:08| 8192| |

| 36|Prg|CL_DYNAMIC_GUI_EXTENSIONS=====CP | 36|18.02.2005|14:15:28| 37888|E |

| 37|Prg|CL_GUI_DATAMANAGER============CP | 37|05.07.2005|13:10:15| 75776|E |

| 38|Prg|CL_ABAP_CHAR_UTILITIES========CP | 38|05.07.2005|13:10:15| 13312|E |

| 39|Typ|SYST | 0|09.09.2004|14:18:12| 31744| |

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

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

|Directory of Application Tables |

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

|Name Date Time Lngth |

| Val. |

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

|Program SAPMSYST |

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

|SYST . . : : 00004612 |

| \0\0\0\0\x0008\0\x0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 |

|RSYST 19.07.2004 10:44:06 00001574 |

| 800RBXXXXX |

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

|Program CL_GUI_PROPS_CONSUMER=========CP |

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

|EUDB . . : : 00004068 |

| %L8AD5A5E3620EF1A5B940E41F133A240E \0\0\0 |

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

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

|ABAP Control Blocks (CONT) |

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

|Index|Name|Fl|PAR0|PAR1|PAR2|PAR3|PAR4|PAR5|PAR6|Source Code |Line |

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

| 2432|BRAT|02|0003| | | | | | |SAPMSYST | 1763|

| 2433|CMPS|20|0242|01CC|01CC| | | | |SAPMSYST | 1763|

| 2435|BRAF|02|000C| | | | | | |SAPMSYST | 1763|

| 2436|MOVL|00|0002|00A5|004B| | | | |SAPMSYST | 1766|

| 2438|mlq1|02|0005|0F50|0045| | | | |SAPMSYST | 1766|

| 2440|MOVL|00|0008|00A6|00E7| | | | |SAPMSYST | 1766|

| 2442|CLEA|00|00A7| | | | | | |SAPMSYST | 1766|

| 2443|CLEA|00|00A8| | | | | | |SAPMSYST | 1766|

| 2444|CLEA|00|00A9| | | | | | |SAPMSYST | 1766|

| 2445|CLEA|00|00AA| | | | | | |SAPMSYST | 1766|

| 2446|MESS|00|00E7| | | | | | |SAPMSYST | 1766|

| 2447|ENDM|00|0000| | | | | | |SAPMSYST | 1770|

|>>>>>|----|00|0000| | | | | | |SAPMSYST | 1770|

| 2449|PERP|00|0003| | | | | | |SAPMSYST | 1785|

| 2450|PERP|10|0000| | | | | | |SAPMSYST | 1785|

| 2451|PERP|10|0000| | | | | | |SAPMSYST | 1785|

| 2452|PERP|11|0000| | | | | | |SAPMSYST | 1785|

| 2453|mvqs|04|0083|0000|0000| | | | |SAPMSYST | 1790|

| 2455|BREL|04|0000| | | | | | |SAPMSYST | 1792|

| 2456|cmpr|00|00CA|8001|0001| | | | |SAPMSYST | 1793|

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

"

Regards,

Mahendra

[former_member182034]

hi Mahendra,

START_CALL_SICK  SAP System Check   enqueue name is empty

Please check the following Points.

1. Start the SICK / SM28 and analyze the error.
2. Go to RZ10 and check this parameter (rdisp/wp_no_enq) is atleast 1.
3. Restart the System
4. If Error Still occurred, Please update the kernel and restart the system.

hopefully, After performed above steps, You will not get the issue again.

Regards,

[Former Member]

Hi Abdul,

The parameter is set to 1.

While I run sick transaction it gave me following error.

"

SAP System Check

enqueue name is empty

Severe problems were detected during initial system check.

Please, do not use that system before fixing these problems."

I have restarted the system also but it didn't work.

Regards,

Mahendra

[former_member182034]

HI Mahendra,

Please share the log if SICK/SM28. Did you perform all steps(3,4) which i mentioned in my last reply.

For Meanwhile,

would you also confirm me about SM12. Is there any entry locked or not?

please increase the value of rdisp/wp_no_btc and restart the system.

Regards,

[Former Member]

Hello Jamil,

I have performed 3rd step.

But I can't perform 4th step, as it is 24X7 industry so did not get downtime.

SICK output:-

I have also checked SM12, there are no lock entries.

rdisp/wp_no_btc this parameter has value 6, how much it should be increased?

Regards,

Mahendra

[former_member182034]

hi Mahendra,

If following parameters are ok

rdisp/wp_no_enq= 1

rdisp/wp_no_btc= 6

FYI... If you changed the value of any parameter then restart was required.

You need to upgrade the kernel because all steps you have been checked instead kernel upgrade.

Regards,

[Former Member]

Hello Abdul,

The parameters are as it is given by you.

I didn't changed any parameter.

Is kernel upgrade is final solution?

Regards,

Mahendra

[former_member188883]

Hi Mahendra,

Please check whether dbsl and SAP kernel patches are same across landscape.

If not Please try with kernel upgrade including dbsl patches and post the results.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

Both kernel patch & dbsl patch no's are same.

Regards,

Mahendra

[Former Member]

enqueue name is empty:

well it depends a little on the system configuration.

If it is an old style configuration (CI-integrated enqueue server) then

we need following parameter settings:

instance profile (<sid>_dvebmgs<no>_<cihostname>

rdisp/wp_no_enq = 1

and

DEFAULT.PFL

rdisp/enqname = <cihostname>_<sapsid>_<ciinstancesnumber>

if it is a new style configuration (using standalone enqueue server):

DEFAULT.PFL:

enque/process_location = REMOTESA

enque/serverhost = <hostname of the ASCS-Instance>

enque/serverinst = <number of the ASCS-Instance>

Whether you are using a new or an old style configuration can be determined:

old style configuration has

DVEBMGSxx and optional Dxx instances and profiles.

new style has

ASCSxx, DVEBMGS and optional Dxx instances and profiles.

regards

Peter

[Former Member]

Open a SAP GUI,

and just call Transaction SICK

Listen to the output

[Former Member]

Hi Mahendra,

Do you have CI and App server?

If so check the kernel versions on both, they have to be the same.

Run report RSMSSDELSQLJOBS

Check the Snote 562388.

Regards

Flávio

[andreas_herzog]

hi...please check the value of the instance parameter 'rdisp/wp_no_enq'? what about the developer trace for the file associated with the enqueue work process?

GreetZ, AH

[Former Member]

Hello Andreas,

The parameter rdisp/wp_no_enq is set to 1.

But in developer trace for enqueue work process I have found some errors as below,

M *** ERROR => enqueue name is empty [thxxsick.c 735]

M *** ERROR => ThSick: Enque Check failed [thxxsick.c 420]

A Error Code START_CALL_SICK.

Regards,

Mahendra

[former_member188883]

Hi Mahendra,

Have you performed any activity like kernel update or patch update.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

I didn't perform any activity.

Regards,

Mahendra