I keep getting the following error when compiling.
"Cannot get exclusive access to executable file for job
premdetail - job may be being monitored"
We are positive this job isn't being monitored, in fact it's not running at all. We killed all connections and stopped then restarted the DS application server, but we still get the error.
You can search the forum for what phantom is. There's 3 different explanations: it's a directory, it's a background process, it's a stub program for running background processes.
As for your troubles with compilation, the first check it a physical lock. If you don't see the job locked via the lock table listing (search the forum), then recycling services is the absolute (but worst) method to release physical locks in the DS database. Unfortunately, DS also uses software locks, which are just entries in a table that have to be removed.
Try using the Clear Job Status capability in the DS Director client. Your problem should go away.
The normal cascading progression for getting a job to compile is:
1. Cancel all monitors.
2. Clear job lock (if any)
3. Clear job internal file locks (RT_CONFIGxxx, RT_LOGxxx, RT_BPxxx, RT_STATUSxxx, etc for this job number)
4. Clear the status file (physically it is the RT_STATUSxxx file)
5. Recycle services
6. Bounce the server
7. Call tech support.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
There are so many posts related to this in this forum. Check them if the following didn't release the job.
Log into "DataStage Administrator" and execute following commands.
Get the jobno for the job. (SELECT JOBNO FROM DS_JOBS WHERE NAME = 'JobName' ;
Then,
Administrator -> execute DS.TOOLS command ->
DataStage Tools Menu
1. Report on project licenses
2. Rebuild Repository indices
3. Set up server-side tracing >>
4. Check integrity of job files
5. Administer processes/locks >>
6. Adjust job tunable properties
Which would you like? ( 1 - 6 ) ? 5
DataStage Process and Lock Administration
1. List all processes
2. List state of a process
3. List state of all processes in a job
----------------------------------------------
4. List all locks
5. List locks held by a process
6. List locks held by all processes in a job
----------------------------------------------
7. Clear locks held by a process
8. Clear locks held by all processes in a job
------------------------------------------
9. Logout a process
10. Logout all processes in a job
11. Clear status file for a job
Which would you like? ( 1 - 11 ) ? 7
Enter pid#=11727 (You get this pid from "List All Locks" and grabing the pid for all the process having jobno of the locked job in its name )
OK to clear locks held by process 11727? (N):y
Clear the status file from Director and/or check for space in the DataStage file tree. You need lots of space.
RStone wrote:Hello everyone, need help with a strange error.
I keep getting the following error when compiling.
"Cannot get exclusive access to executable file for job
premdetail - job may be being monitored"
We are positive this job isn't being monitored, in fact it's not running at all. We killed all connections and stopped then restarted the DS application server, but we still get the error.
