Troubleshooting
Problem
Database Locking problem : used_urec: v$transaction : Oracle 8.0.5 on DEC Alpha
Symptom
PART: Interface 6.0 SP1 DCS
OS: DEC Alpha - None
DATABASE: Oracle -
8.0.5
Database Locking problem on Oracle 8.0.5 on DEC Alpha
Cause
Resolving The Problem
Make sure that there are no long-standing locks on the database
(find_db_lock/findallloc scripts can be used). A lock on any table more than a
few hours old can indicate a problem; possibly a user has mistakenly left some
process improperly.
The following query can also be useful:
select
used_urec from v$transaction;
(or use select * for more details, such as
TimeStamp)
This is a dynamic Oracle server table which gives the status of
ongoing transactions being worked on by PMON. If a transaction is logged for a
long time, its Serial # on locks output will increase continually. If the
output of the above query is steady and used_urec count(s) are NOT moving with
old locks from the lock script, you can safely assume a database locking
problem.
Some more explanation from earlier cases :
* Run findallloc
utility, which shows locks held-up from yesterday and the day before on various
tables. (infc_dnld_tab_1, ord_rel_hdr, pick_ticket)
* A similar problem has
been linked to an identified bug with Oracle 8.0.5 on UNIX for Dec-Alpha
*
Check "select used_urec from v$transaction;". If the value for this column
keeps going down, then work is being done. When used_urec reaches zero, then
the rollback will be done, and the session will die.
Oracle Metalink Doc :
1020545.102
For now, stop and restart the database with "shutdown
abort". Once the database is brought down forcefully, the parent Unix
process(es)--if still running--will be cleaned up as well.
Historical Number
PRI48436
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21541274