Disp+work in yellow status

[Former Member]

Hi experts.

I have a problem with disp+work proces. After restart instances it´s running but it´s in yellow status. everythink works fine. Have you some solution to repair this status on green?

System release is:

OS: Linux GNU SLES-9 x86_64 cc3.3.3

SAP release: ECC 6 SP3

Kernel Patch number : 179

Database: Oracle 10.2.0.4

Thanks you for help.

Jakub Vaněk

[JPReyes · Accepted solution]

Any changes?.. kernel upgrades?... sometimes it doesn't represent a problem at all... its just a comunication issue between the MMC and the system and a quick reboot fix it.

Regards

Juan

[Former Member]

Hi Vanik,

How can you see that the disp+work process is in yelow status in an Unix/Linux enviroment ?!!

Thanks,

[Former Member]

Hi jakub

Please check SAP note 544533 - FAQs: The R/3 system no longer starts

373326 - NT: R/3 system does not start with 4.6D R/3 kernel

Do you see any "*** ERROR => <EsNT> Block 178/28769608 VirtualAlloc error=487" messages in any of your dev_w* files in \usr\sap\<SID>\DVEBMGS00\work?

Please run R3trans -d and attach the trans.log file

Regards

Chen

[Former Member]

Hi,

This note (544533 ) is for release 4.6D, but I have ECC6 It´s NW release 7.00.

I´m not using sapmmc console.

I check this yellow status of dispwork in SAP Web Application Server from web browser in Administration -> System information. You can check here j2ee processes and SAP processes a.s.o. The monitor shows that all processes are running, SAP is running OK, but I see dispwork in yellow status.

Every work process are correctly running.

I checked log of dev_disp and it´s two warning occured, but I don´t really know if this may affect on status of disp+work.:

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1)

***LOG Q0K=> DpMsAttach, mscon ( sapeao3-M01)

DpStartStopMsg: send start message (myname is >sapeao3-M01_M01_00 <)

DpStartStopMsg: start msg sent

Warning: Swap space is configured quite small with 5436 MB.

It should be configured with at least 20 GB on 64 bit systems.

See note 153641 for more information.

Warning: tmpfs at /dev/shm is configured quite small with 1248 MB!

Minimum value is 8192 MB.

Recommended size is 75 % of RAM + swap.

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

Tue Mar 24 13:08:42 2009

CCMS: Checking Downtime Configuration of Monitoring Segment.

CCMS: start to initalize 3.X shared alert area (first segment).

DpJ2eeLogin: j2ee state = CONNECTED

DpMsgAdmin: Set release to 7000, patchlevel 0

Regards

JV

[Former Member]

Hai,

Have you tried restarting the system?

You can give a try in increasing the parameters as per 153641.

Are you having any other SAP system on the same host in which you have problems.

Regards,

Yoganand.V

[Former Member]

Hi,

It could be communication issue, better check dev_disp file in work directory. Also, Its worth check whether 'sapstart' process is running or not ( I guess u r using sapmmc)

Cheers