One of our replication jobs won't complete because of a job queue lock. Have tried dbms_job.broken, but seems to wait until job completes. Killing the sessions did not release the job queue lock nor completed the job.
How do we force to release a "JQ" lock?
Is there a way to kill SNP processes at the OS level (Windows NT)?
Any advice or suggestion highly appreciated.
11-07-2000, 06:35 AM
This is really a problem.I encountered the same.Try purging all the requests.You can try suspend and resume options.
11-07-2000, 11:39 AM
what u already tried should have worked.
if u r using replication manager then
make job as broken(should be same as job shown in v$lock).then run the job again.
that should release the lock.
in windows NT u can use orakill sid thread to kill a job.
go to command prompt and type orakill.that will guide u thru.
Here for sid u have to use the sid for the instance(like orcl) and not the sid from v$session.
let us know.
11-07-2000, 09:40 PM
Thank you for the help.
I was able to release the lock by killing the thread using orakill in OS mode.
This is my first multimaster-replication assignment and I'm still trying to figure out what these JQ locks, errors during transaction push etc.
Any pointers, suggestions from anybody highly appreciated.
11-09-2000, 10:29 AM
It also depends on the version.we were on 18.104.22.168.0. and the frequecy of deferred trnsactions piling up were high.We applied the patch 22.214.171.124.1 and it got resolved.also shoot up the value of job_queue _processes in init ora file( to 10) and that will also help u to get rid of the defeered tran queue problem.