Not able to stop datastage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 136
- Joined: Wed May 07, 2008 11:26 am
- Location: Sydney, Australia
- Contact:
Not able to stop datastage
hi friends,
i urgently need to stop the datastage application using command bin/uv -admin -stop. but i an getting the following error. kindly guide me to resolve this
Error:
Unable to remove the following shared memory segment(s) during shutdown:
m 1048577 0xadec7521 --rw-rw-rw- root system 111088 127264
m 3 0xadee7521 --rw-rw-rw- root system 106932 127264
Stopping JobMonApp
JobMonApp has not been started from: /dsetlsoft/Ascential/DataStage/PXEngine
2 error(s) encountered during shutdown procedure.
DataStage Engine 7.5.2.1 instance "ade" may be in an inconsistent state.
i urgently need to stop the datastage application using command bin/uv -admin -stop. but i an getting the following error. kindly guide me to resolve this
Error:
Unable to remove the following shared memory segment(s) during shutdown:
m 1048577 0xadec7521 --rw-rw-rw- root system 111088 127264
m 3 0xadee7521 --rw-rw-rw- root system 106932 127264
Stopping JobMonApp
JobMonApp has not been started from: /dsetlsoft/Ascential/DataStage/PXEngine
2 error(s) encountered during shutdown procedure.
DataStage Engine 7.5.2.1 instance "ade" may be in an inconsistent state.
Vinay
-
- Premium Member
- Posts: 20
- Joined: Tue Dec 16, 2008 10:09 am
- Location: Lisboa
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The UNIX sync command forces any pages in memory that have not yet been written to disk to be written to disk. This is important for DataStage engine, which makes extensive use of shared memory. The second sync command picks up any pages that might have been modified while the first sync command was running.
While the original error was about inability to remove shared memory segments cleanly - probably permissions as noted - the sync commands guarantee that even if "crowbar" techniques like ipcrm are used, the engine will at least be in a consistent state.
While the original error was about inability to remove shared memory segments cleanly - probably permissions as noted - the sync commands guarantee that even if "crowbar" techniques like ipcrm are used, the engine will at least be in a consistent state.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 136
- Joined: Wed May 07, 2008 11:26 am
- Location: Sydney, Australia
- Contact:
hi,
by killed the process i mean that i executed the command ipcrm -m <shmid>.
the steps that i took are as follows:
-------------------
Shared memory segments:
ipcs -mop
That will list all active shared memory segments. Not all of those are related to DataStage. But if some are (like if they are tagged with "ade") and the NATTCH column shows zero, you need to kill those:
ipcrm -m <shmid>
<shmid> is the 2nd column from the ipcs -mop command
--------------------------
i found these steps on net.
by killed the process i mean that i executed the command ipcrm -m <shmid>.
the steps that i took are as follows:
-------------------
Shared memory segments:
ipcs -mop
That will list all active shared memory segments. Not all of those are related to DataStage. But if some are (like if they are tagged with "ade") and the NATTCH column shows zero, you need to kill those:
ipcrm -m <shmid>
<shmid> is the 2nd column from the ipcs -mop command
--------------------------
i found these steps on net.
Vinay
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 136
- Joined: Wed May 07, 2008 11:26 am
- Location: Sydney, Australia
- Contact:
Hi Ray,
you are right. we need to be very careful.thanks for the caution friend. i found these tips very useful as they solved my problem, but please inform me if there is any damage in using these commands.
actually i have no idea of the commands like ipcs -mop and ipcrm -m <shmid>. yet to explore these commands.
you are right. we need to be very careful.thanks for the caution friend. i found these tips very useful as they solved my problem, but please inform me if there is any damage in using these commands.
actually i have no idea of the commands like ipcs -mop and ipcrm -m <shmid>. yet to explore these commands.
Vinay
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There are other things happening than shared memory segments, and this only gets more complicated when you move to version 8. The main hazard with removing the shared memory segments (other than needing the root login ID) is making sure you get them all - but then what about the semaphores and other structures? If you have the root login then executing the uv -admin -stop command will work and - as a bonus - do all that is necessary. If you want to know all the things that happen during a shutdown of DataStage, take a look at the ds.rc script in the sample directory.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.