Clearing DSEngine/dsdlockd.log
Moderators: chulett, rschirm, roy
Clearing DSEngine/dsdlockd.log
Professor Ray or anyone,
Can I zero out this log file?
-rw-rw-rw- 1 dsadm dstage 2147483653 Mar 5 12:46 ./DSEngine/dsdlockd.log
Thanks
Can I zero out this log file?
-rw-rw-rw- 1 dsadm dstage 2147483653 Mar 5 12:46 ./DSEngine/dsdlockd.log
Thanks
Mamu Kim
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 82
- Joined: Wed Jul 14, 2004 7:21 am
- Location: India
Vinodlakshmanan,
a deadlock process is one which looks for orphaned locks and or processes associated with a program system. Usually this type of program can be found with Databases, since they use a lot of locks and do suffer from orphaned processes, but other types of applications require the same type of external process to do "housekeeping".
In DataStage the deadlock daemon will check the lock tables for locks that are still present in the system but no longer associated with a running process. Typically this type of problem will happen if a designer process is crashed or disconnected.
a deadlock process is one which looks for orphaned locks and or processes associated with a program system. Usually this type of program can be found with Databases, since they use a lot of locks and do suffer from orphaned processes, but other types of applications require the same type of external process to do "housekeeping".
In DataStage the deadlock daemon will check the lock tables for locks that are still present in the system but no longer associated with a running process. Typically this type of problem will happen if a designer process is crashed or disconnected.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The dsdlockd.log file records the activity of the deadlock daemon. Every time it wakes, every time it checks for deadlocks, every time it cleans up after defunct processes - they're all recorded, and there's no auto-purge. Hence Mr Kim's problem.
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.
Hi Kim,
if this file dsdlockd.log goes beyongd 2GB I hope it does not allow writing into this file.
This is the case with some of Unix machines. On some machines max file size is 2GB.
I never came across such a situation but, can you tell if this file is really 2GB size and what are the consequences.
regards
dsxdev
if this file dsdlockd.log goes beyongd 2GB I hope it does not allow writing into this file.
This is the case with some of Unix machines. On some machines max file size is 2GB.
I never came across such a situation but, can you tell if this file is really 2GB size and what are the consequences.
regards
dsxdev
Happy DataStaging
This is just a log file. he 2GB limit is on hash files. Most UNIX machines can go beyond this limit on sequential files like this type of log file. The job log files by the way are hash files and do need to be converted to 64bit to go beyond 2GB. If you have a job log file or really any log file then this is too big. That much history is not needed. These usually slow things down too when they are large.
The ls command will tell you how big this file is. It is a normal UNIX text file.
The ls command will tell you how big this file is. It is a normal UNIX text file.
Mamu Kim