Dialog instance not apprearing in SM51

[Former Member]

Please help promptly. Our central instance & dialog instances run on different host. There was a problem which caused both to shutdown...i.e. network card change by Unix team. After that we restarted the central instance then the dialog instance. Upon login on to SAP and then transaction SM51, we only found one instance running. Tried checking all parameters. please advise on what should be done next.

[Former Member]

Hi,

Actually the same issue we faced , better we have to check the log at the work directory.

Please check the dev_disp log .

Regards,

Abhishek SIngh

[Former Member]

check dev_disp on that application server for any errors/warnings, check if instance has successfully started or not, network connectivity etc

[Former Member]

All isnatnces running when checking with dpmon command. The only problem is that dialog instances & its workprocesses are not visible in SM51.

Dialog Instance Dev_disp reads as follows:

more dev_disp

-

---

trc file: "dev_disp", trc level: 1, release: "45B"

-

---

Wed Jul 29 17:35:54 2009

relno 4520

patchlevel 0

patchno 921

intno 0

pid 7426178

***LOG Q00=> DpSapEnvInit, DPStart (01 7426178) [dpxxdisp 0868]

• ERROR => DpSysACreate: ShmCreate (CREATE) [dpxxtool 2192]

• ERROR => dispatcher already running ???? [dpxxtool 2193]

• ERROR => I better EXIT before I do any (more) damage [dpxxtool 2195]

dev_disp: END

Central Instance dev_disp:

[martin_juen2]

Can you logon directly on the dialog instance via sap gui?

What about the ip-address and/or alias? Did they change after the change of the network card? nslookup ok?

What tells you the system log of the dialog instance?

What's about the other log files in the work directory?

There's to less info to give a clear advice.

regards,

Martin

[Former Member]

It seems the dialogue instance was not completely stopped before restarting. Try to stop it cleanly, stop all its Unix processes, if in doubt shutdown Unix as well. Then try again.

hope this helps

[Former Member]

Greetings,

We later realized that some DI workprocesses were not cleaned/killed during a restart. They were forever running when executing dpmon. Kill & kill -9 commands could not kill these processes.

The issue has been resolved as follows:

- stopped DI

- execute: cleanipc <sys #> remove

- started DI

The DI work-processes was then visible in SM51

Thanks