Unlocking the datastage jobs

mikva2012 · Post by **mikva2012** » Tue Mar 19, 2013 12:31 am

Hi All,

Am facing strange issue , whenever am trying to open the job in designer window it is giving me error message job is locked by the user.
However when I tried to see the resource lock through the director client there is no resource lock.
After that I tried with the Administrator client , by executing the command LIST.READU EVERY, the output doesn't have any info about resource lock by any user.
Then I checked with the server console in session management there is no such active session.
Please help me to unlock the job.

prasson_ibm · Post by **prasson_ibm** » Tue Mar 19, 2013 1:38 am

Hi,
You have to check in XMETA database if there is any lock exists.

Code: Select all

SELECT * FROM XMETA.XMETALOCKINFO

If there is the entry in this table,you need to delete it.

mikva2012 · Post by **mikva2012** » Tue Mar 19, 2013 1:55 am

Hi Prasson,

I am not aware of the metadata repository username and password.
Apart then that is there any way to do that.

ray.wurlod · Post by **ray.wurlod** » Tue Mar 19, 2013 2:40 am

Log out the Designer session and wait. The lock will be cleaned up after a short while (maybe as long as 15 minutes).

ray.wurlod · Post by **ray.wurlod** » Tue Mar 19, 2013 2:42 am

If you have IS Administrator role, log in to the Web Console for Information Server, open the list of active sessions and disconnect the session that owns the log (the session ID is in the "locked" message). The lock will be cleared immediately.

prasannakumarkk · Post by **prasannakumarkk** » Tue Mar 19, 2013 3:00 am

Ray, 15 Minutes is it configured somewhere or its common? What is happening actually. Are there any process that cleanups the lock record in Xmeta

mikva2012 · Post by **mikva2012** » Tue Mar 19, 2013 3:26 am

Prasson,

As previous mentioned it is not showing any active session related to the user.
And user is not able right now.

Ray,

I came to know about the cleanabondedlocks.sh, if I will run this script what will be the impact.
Please reply with your valuable suggestion.

mikva2012 · Post by **mikva2012** » Tue Mar 19, 2013 8:03 am

Hi Guys,

Please reply what will be the impact if will run the cleanupabondedlock.sh script from Unix command line.

prasson_ibm · Post by **prasson_ibm** » Tue Mar 19, 2013 9:28 am

Hi,
I am not able to fine this script on my ETL server

Code: Select all

find / -name "cleanupabondedlock.sh" -print 2>/dev/null/

I didnt get any output,can you please post the location of the script.

mikva2012 · Post by **mikva2012** » Tue Mar 19, 2013 9:55 am

Yeah Buddy,

It is in ASBServer/bin dir

prasson_ibm · Post by **prasson_ibm** » Tue Mar 19, 2013 10:12 am

Ok, I think it will also delete entry from xmetalockinfo but I am not sure.let's someone focus on this.

mikva2012 · Post by **mikva2012** » Tue Mar 19, 2013 10:27 am

Hi Buddy,

I tried the same script in mine production environment and it work fine for me.
But I didn't remembered how I executed that script.
I didn't remember from which user-id I executed the script and in what way , the only thing I know I have to supply the suite admin id and password.

ray.wurlod · Post by **ray.wurlod** » Tue Mar 19, 2013 1:18 pm

mikva2012 wrote:what will be the impact if will run the cleanup_abandoned_locks.sh script from Unix command line.

Abandoned locks will be cleaned up. However, a lock held by another DataStage client is not an abandoned lock.

rameshrr3 · Post by **rameshrr3** » Tue Mar 19, 2013 3:11 pm

I could find a script named

cleanup_abandonded_locks.sh in my $ASBSERVER/bin directory.

Code: Select all

(/opt/IBM/InformationServer/ASBServer/bin/cleanup_abandonded_locks.sh)

chulett · Post by **chulett** » Tue Mar 19, 2013 4:25 pm

prasson_ibm wrote:I am not able to fine this script on my ETL server
Code: Select all
find / -name "cleanup_abandonded_locks.sh" -print 2>/dev/null/
I didnt get any output,can you please post the location of the script.

You misspelled it as "abandonded" which is one reason why you couldn't find it. The other are the underscores. Probably best to search with wildcards if you're unsure of the exact name:

Code: Select all

find / -name "cleanup*.sh" -print 2>/dev/null/