- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2008 12:12 PM
тАО01-24-2008 12:12 PM
Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
db to be recycled.
A table becomes locked causing a major backup.
The db says the session causing the lock has gone away. Indeed the lsnr job is gone.
Our assigned dba says under VMS, a lock whose
session is gone cannot be cleared - hence db restart.
Does this ring true?
Is there a way to clear a table lock under this
condition?
Thank you in advance....Doug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2008 12:30 PM
тАО01-24-2008 12:30 PM
Re: Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
sql> select sid, serial#, username, status from v$session;
.
.
.
.
.
.
sql> alter system kill session '
The
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2008 12:40 PM
тАО01-24-2008 12:40 PM
Re: Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2008 08:46 PM
тАО01-24-2008 08:46 PM
Re: Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
It sounds like you are experiencing what is usually called a "blocking lock". One process is holding a lock on a database object which one or more other processes wish to obtain. Identifying the process holding the lock is the trick.
It is not always possible to identify which process is of interest from information in v$session, alone. It depends on the application.
I use a third party product which has made me lazy and out of practise in using SQL to find the problem. But Oracle provide a script in Ora_Rdbms_Admin called UTLLOCKT.SQL which may help. If you have access to an Oracle Enterprise Manager console, it may have tools to show which process is locking which object. Mine does, but it is version 9.2
Usually, if you can identify the Oracle process holding the lock, and kill it, the lock is freed immediately and processing continues. However, if the rogue process has done a massive update, then it may take some time for Oracle to roll back the update. This means the lock can sometimes be held for long after the process has been killed. This is true for all operating systems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-25-2008 02:37 AM
тАО01-25-2008 02:37 AM
Re: Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-25-2008 02:59 AM
тАО01-25-2008 02:59 AM
Re: Oracle 8.1.7.4 on VMS 7.3-2 Lock Problem
You can specify a timeout interval by placing the sqlnet_expire_time parameter in your sqlnet.ora file. For example, setting sqlnet_expire_time=2 will poll the SQL*Net client every two minutes and disconnect the session if there is no activity.
Wim