Hi,
We are not able to release jobs from director using "Clean up resources" as the window showing all process with "Show all" being on shows one PID# with 0 .
While our development server doesnt have any problem.
Jobs not releasing
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
try this :
1. Telnet to the DS server machine and cd to $DSHOME directory as root or dsadm account; (where $DSHOME is the DSEngine directory)
2. Run ". ./dsenv";
3. Run "bin/uvsh" to enter DS Command Prompt;
4. Enter "LOGTO UV" to log into UV account. (*may not need to be done on DS 7) If the LOGTO command is disabled, use this command "CHDIR <path_to_the_DSEngine_folder>" (with <path_to_the_DSEngine_folder>=cat /.dshome under a telnet session on the DataStage server). The UNLOCK command lives in UV account.
5. Type ">LIST.READU EVERY" and press "Enter". Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number.
6. Write down the inode number and user number for the lock that is not a valid lock.
7. Type ">UNLOCK INODE inode# USER user# ALL" and press "Enter";
This will unlock the lock hold on this file (inode#) and hold by this user (user#) for file locks, group locks and record locks.
9. If you need to see all the locks again, type ">LIST.READU EVERY" and press "Enter".
10. Enter ">LOGTO projectname" and press "Enter" to logto the project repository; (where projectname is case sensitive)
11. Enter "CLEAR.FILE RT_STATUSxx" and press "Enter" to clear the status for the job; (where xx is the job_number for that job);
12. Enter "LO" to exit the DS Command Prompt;
1. Telnet to the DS server machine and cd to $DSHOME directory as root or dsadm account; (where $DSHOME is the DSEngine directory)
2. Run ". ./dsenv";
3. Run "bin/uvsh" to enter DS Command Prompt;
4. Enter "LOGTO UV" to log into UV account. (*may not need to be done on DS 7) If the LOGTO command is disabled, use this command "CHDIR <path_to_the_DSEngine_folder>" (with <path_to_the_DSEngine_folder>=cat /.dshome under a telnet session on the DataStage server). The UNLOCK command lives in UV account.
5. Type ">LIST.READU EVERY" and press "Enter". Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number.
6. Write down the inode number and user number for the lock that is not a valid lock.
7. Type ">UNLOCK INODE inode# USER user# ALL" and press "Enter";
This will unlock the lock hold on this file (inode#) and hold by this user (user#) for file locks, group locks and record locks.
9. If you need to see all the locks again, type ">LIST.READU EVERY" and press "Enter".
10. Enter ">LOGTO projectname" and press "Enter" to logto the project repository; (where projectname is case sensitive)
11. Enter "CLEAR.FILE RT_STATUSxx" and press "Enter" to clear the status for the job; (where xx is the job_number for that job);
12. Enter "LO" to exit the DS Command Prompt;
-
- 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:
When you say "restarting the server" do you mean restarting DataStage or re-booting the operating system? The latter is pretty much guaranteed to work (since locks are held in memory) unless your Repository database(s) have been corrupted.
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.
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio