Error in DSDeadLock.log (LK_cleanup_pshm)

[dhwankim]

Hi Gurus,

Today, I inspected DSDeadLock.Log with DataStage 4.x,
and Found some odd. Regurally Failure in LK_cleanup_pshm errors are written in the file.

Is it affect the stabiliy of DS Job Process?
I capture some log for sample ( please see below log capture.)
SO I inspected some another site datastage log.
but there is few error written.

Can you explain the exact thing, what's happen?

Thanks in Advance.

For Sample
===============================================
Tue Jan 6 08:30:06 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (91286)
Tue Jan 6 08:30:06 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 08:30:06 2004 - ** Removed shared memory segment for User (-24537), SegNo (aceba027)
Tue Jan 6 09:00:01 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (128544)
Tue Jan 6 09:00:01 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (19894)
Tue Jan 6 09:00:01 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (183768)
Tue Jan 6 09:00:01 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (208444)
Tue Jan 6 09:00:01 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:01 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:01 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:01 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:01 2004 - ** Removed shared memory segment for User (-24537), SegNo (aceba027)
Tue Jan 6 09:00:01 2004 - Failure in LK_cleanup_pshm
Tue Jan 6 09:00:01 2004 - Failure in LK_cleanup_pshm
Tue Jan 6 09:00:01 2004 - Failure in LK_cleanup_pshm
Tue Jan 6 09:00:03 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (128548)
Tue Jan 6 09:00:03 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:03 2004 - ** Removed shared memory segment for User (-24537), SegNo (aceba027)
Tue Jan 6 09:00:03 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (19896)
Tue Jan 6 09:00:03 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:03 2004 - Failure in LK_cleanup_pshm
Tue Jan 6 09:00:03 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (208446)
Tue Jan 6 09:00:03 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:03 2004 - Failure in LK_cleanup_pshm
Tue Jan 6 09:00:05 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (20878)
Tue Jan 6 09:00:05 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:05 2004 - ** Removed shared memory segment for User (-24537), SegNo (aceba027)
Tue Jan 6 09:00:05 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (69690)
Tue Jan 6 09:00:05 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:05 2004 - Failure in LK_cleanup_pshm
Tue Jan 6 09:00:07 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (206656)
Tue Jan 6 09:00:07 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:00:07 2004 - ** Removed shared memory segment for User (-24537), SegNo (aceba027)
Tue Jan 6 09:10:00 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (208468)
Tue Jan 6 09:10:00 2004 - ** Cleanup being performed for UserSig(-24537)
Tue Jan 6 09:10:00 2004 - ** Removed shared memory segment for User (-24537), SegNo (aceba027)
Tue Jan 6 09:10:00 2004 - DeadLock Daemon started in Dead Process Cleanup Mode by pid (19910)
Tue Jan 6 09:10:00 2004 - ** Cleanup being performed for UserSig(-24537)Tue Jan 6 08:30:06 2004 - DeadLock Daemon started
in Dead Process Cleanup Mode by pid (91286)

[ray.wurlod]

LK_cleanup_pshm is the module called by uvdlockd (dsdlockd in later releases) that cleans up locks held by the defunct process that owns the printer shared memory segment, as part of reclaiming that process's resources.
It can "fail" if it can't clean up the locks because they're shared locks also held by other processes. It can "fail" if locks recorded as held have already been released by other means. There are probably other ways it can "fail" too.
None of these are likely to impact your day to day execution of DataStage jobs.