RID in DB2 UDB

Eugenia Huang

RID in DB2 UDB
Greetings! UDB experts and colleagues:

Is there any easier way to track down the exact data of the "bad" row of an
UDB table that we know its RID? Problem is that we've encountered
"duplicate key" errors in an UDB application, so that we know the rids (from
the error messages) but do not know which are the rows that are "bad". Has
anyone encountered this similar problems and are willing to share with us?

Any suggestions/advice would be greatly appreciated.

Thanks in advance!

Eugenia

James Campbell

Re: RID in DB2 UDB
(in response to Eugenia Huang)
Eugenia

Is the UDB for OS/390, or UDB for NT or ...? If it's UDB for OS/390
then:

- The RID is a four byte field, the first 3 bytes are a page number, the
last byte is an ID number within the page. (Large tablespaces use 5
byte RIDs with a 4 byte page number)

- Use DSN1PRNT to give a formatted print out of the pages reported. Use
the ID to locate the rows.

/* standard disclaimer */
James Campbell
DBA
Hansen Corporation, Tooronga
+61 3 9261 1802
[login to unmask email]
-----Original Message-----
From: Huang, Eugenia [mailto:[login to unmask email]
Sent: Thursday, October 07, 1999 6:27 AM
To: [login to unmask email]
Subject: RID in DB2 UDB


Greetings! UDB experts and colleagues:

Is there any easier way to track down the exact data of the "bad" row of
an
UDB table that we know its RID? Problem is that we've encountered
"duplicate key" errors in an UDB application, so that we know the rids
(from
the error messages) but do not know which are the rows that are "bad".
Has
anyone encountered this similar problems and are willing to share with
us?

Any suggestions/advice would be greatly appreciated.

Thanks in advance!

Eugenia

Eugenia Huang

Re: RID in DB2 UDB
(in response to James Campbell)
Jim:

Sorry for not being clear enough. Unfortunately, the UDB that I
referred to is UDB on distributed environment, such as: UDB on Windows, NT,
AIX UNIX, that what we're currently trying to figure out any easier way to
help out the applications that struggling with their online inserts and
deletes...
-----Original Message-----
From: Campbell James [mailto:[login to unmask email]
Sent: Wednesday, October 06, 1999 9:14 PM
To: [login to unmask email]
Subject: Re: RID in DB2 UDB


Eugenia

Is the UDB for OS/390, or UDB for NT or ...? If it's UDB for OS/390
then:

- The RID is a four byte field, the first 3 bytes are a page number, the
last byte is an ID number within the page. (Large tablespaces use 5
byte RIDs with a 4 byte page number)

- Use DSN1PRNT to give a formatted print out of the pages reported. Use
the ID to locate the rows.

/* standard disclaimer */
James Campbell
DBA
Hansen Corporation, Tooronga
+61 3 9261 1802
[login to unmask email]
-----Original Message-----
From: Huang, Eugenia [mailto:[login to unmask email]
Sent: Thursday, October 07, 1999 6:27 AM
To: [login to unmask email]
Subject: RID in DB2 UDB


Greetings! UDB experts and colleagues:

Is there any easier way to track down the exact data of the "bad" row of
an
UDB table that we know its RID? Problem is that we've encountered
"duplicate key" errors in an UDB application, so that we know the rids
(from
the error messages) but do not know which are the rows that are "bad".
Has
anyone encountered this similar problems and are willing to share with
us?

Any suggestions/advice would be greatly appreciated.

Thanks in advance!

Eugenia