DSXchange

Hi all,

I am getting this bellow problem.Please Educate me regarding this issue.


$ uv -admin -stop
Unable to remove the following shared memory segment(s) during shutdown:
m 38797314 0xadec7521 --rw-rw-rw- root system 512014 643084
m 277872651 0xadee7521 --rw-rw-rw- root system 430192 643084
Stopping JobMonApp
JobMonApp has not been started from: /home/dsadm/Ascential/DataStage/PXEngine
2 error(s) encountered during shutdown procedure.
DataStage Engine 7.5.2.1 instance "ade" may be in an inconsistent state.


Thanx in advance.

Got to do with the ID you used. Pls. do an exact search on 'shared memory segment'.

JoshGeorge wrote:Got to do with the ID you used. Pls. do an exact search on 'shared memory segment'.

Hi all,


1)Actually i tried to reslove locks,How to find which processid is having lock.
2)For that i had used clear statatics,cleanup resources.in that i logout all.
releseALL
After that i am not able to see my jobs in repositary both oldjobs,Newly created jobs

After that i had stoped my dsengine.

uv -admin -stop

Right now i am getting this problem.

Please educate me regarding this issue.

Thanx in advance.

This is not about locks; it is about shared memory.

An ipcs -m command will show the shared memory segments in use; any with a key beginning 0xade are DataStage shared memory segments. It will also show that the permissions on them are tight (rw-------) so that you must shut down DataStage using the same login ID that was used to start DataStage (and is therefore the owner of those shared memory segments).