- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: RDB problem
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
02-06-2008 05:02 AM
02-06-2008 05:02 AM
Re: RDB problem
84 is the logical area id
67 the page number
1 the line number in the page
can you issue under your sql sessions the command
"show transaction"
to be sure that the first is a read only and the second a shared read write
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-06-2008 05:58 AM
02-06-2008 05:58 AM
Re: RDB problem
Blocker: 202054F5 _TNA281:....... 550021A6 00010001 PR
My assumption is:
PID 202054F6 = 'session B' (delete) and PID 202054F5 = 'session A' (Select); Exclusive access to delete this record (EX) seems rather obvious to me: you'd better be sure the record is'"owned" by the deleter.
Perhaps it would help to remove "reserving table avail_table for shared read" in session A's SQL set transaction command. If that would set a NL (Null) lock, you're ploblem is solved (but as stated before, it depends on what the data is used for later on)
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-06-2008 06:18 AM
02-06-2008 06:18 AM
Re: RDB problem
Also if you try to select a table other that the one reserved you will have a error.
A read only don't lock any record of the tables used in the select statement except if you have disabled the snapshot mechanism which is use by Rdb to maintain the correct isolation level (serializable). If you disabled the snap you will have a read committed isolation level for you read only transaction using transient lock on selected record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-07-2008 05:48 AM
02-07-2008 05:48 AM
Re: RDB problem
Make sure the table you are accessing has a snapshot file associated with it.
Dan Herron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-08-2008 12:15 AM
02-08-2008 12:15 AM
Re: RDB problem
%RDB-F-SYS_REQUEST, error from system services request
-RDMS-F-FILACCERR, error opening storage area file xxxxxx
and a corrupt one generate a bugcheck.
JFP
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP