Database errors reported by MUPIP INTEG differ in impact and severity. Some require an immediate action to prevent extending the damage, action on other less severe errors may be delayed.

The following table outlines the MUPIP INTEG error messages with their severity using the codes as listed below:

A

Access: Prevents database access

B

Benign: Presents no risk of additional damage and has little or no effect on database performance

D

Dangerous: Presents a high risk that continuing updates may cause significant additional damage

I

Index: If the block is an index block, continuing updates will be quite dangerous: treat as a D; if the block is a datablock, continuing updates can only cause limited additional damage

T

Transient: Usually cleared by an update to the database

MUPIP INTEG Error Messages

Error Name

Message

Severity

Section*

Section*: Refers to the specified section in Managing Database Integrity chapter of Administration and Operations Guide. The section details a description along with the action item to be taken on encountering the error message.

DBBADKYNM

Bad Key Name

I

K1

DBBADNSUB

Bad numeric subscript

I

K1

DBBADPNTR

Bad pointer value in directory

D

K4

DBBDBALLOC

Block doubly allocated

D

K3

DBBFSTAT

Block busy/free status unknown (local bitmap corrupted)

D

M1

DBBNPNTR

Bit map block number as pointer

D

K4

DBBPLMGT2K

Blocks per local map is greater than 2K

D

I3

DBBPLMLT512

Blocks per local map is less than 512

D

I3

DBBPLNOT512

Blocks per local map is not 512

D

I3

DBBSIZZRO

Block size equals zero

A

I3

DBCOMPTOOLRG

Record has too large compression count

I

O2

DBDATAMX

Record too large

B

O5

DBFGTBC

File size larger than block count would indicate

B

I4

DBFSTBC

File size smaller than block count would indicate

D

I4

DBFSTHEAD

File smaller than database header

A

I3

DBGTDBMAX

Key larger than database maximum

I

K7

DBHEADINV

Header size not valid for database

A

I3

DBINCLVL

Block at incorrect level

D

O1

DBINCRVER

Incorrect version of GT.M database

A

I2

DBINVGBL

Invalid mixing of global names

D

K3

DBKEYGTIND

Key greater than index key

I or B

K2 or O5

DBKGTALLW

Key larger than maximum allowed length

I

K1

DBLOCMBINC

Local bit map incorrect

B

M1

DBLRCINVSZ

Last record of block has invalid size

I

K5

DBLTSIBL

Key less than siblinga??s index key

I

K2

DBLVLINC

Local map block level incorrect

B

M2

DBMAXKEYEXC

Maximum key size for database exceeds design maximum

D

I3

DBMAXRSEXBL

Maximum record size for database exceeds what the block size can support

D

I3

DBMBMINCFREZ

Master bit map incorrectly asserts this local map has free space

B

M1

DBMBPFLDIS

Master bit map shows this map full, in disagreement with both disk and INTEG results

B

M1

DBMBPFLDLBM

Master bit map shows this map full, agreeing with disk local map

B

M1

DBMBPFLINT

Master bit map shows this map full, agreeing with MUPIP INTEG

B

M1

DBMBPFRDLBM

Master bit map shows this map has space, agreeing with disk local map

B

M1

DBMBPFRINT

Master bit map shows this map has space, agreeing with MUPIP INTEG

B

M1

DBMBPINCFL

Master bit map incorrectly marks this local map full

B

M1

DBMBSIZMN

Map block too small

B

M2

DBMBSIZMX

Map block too large

B

M2

DBMBTNSIZMX

Map block transaction number too large

T

I6

DBMRKBUSY

Block incorrectly marked busy

B

M1

DBMRKFREE

Block incorrectly marked free

D

M1

DBMXRSEXCMIN

Maximum record size for database is less than the design minimum

D

I3

DBNOTDB

File does not have a valid GDS file header

A

I3

DBNOTMLTP

Block size not a multiple of 512 bytes

A

I3

DBRBNLBMN

Root block number is a local bit map number

D

K4

DBRBNNEG

Root block number negative

D

K4

DBRBNTOOLRG

Root block number greater than last block number in file

D

K4

DBREADBM

Read error on bitmap

D

H7

DBRLEVLTONE

Root level less than one

D

O1

DBRLEVTOOHI

Root level higher than maximum

D

O1

DBSPANCHUNKORD

Chunk of blocks is out of order

B

O5

DBSPANGLOINCMP

Spanning node is missing

B

O5

DBSVBNMIN

Start VBN smaller than possible

A

I3

DBSZGT64K

Block size is greater than 64K

A

I3

DBTNNEQ

Current tn and early tn are not equal

T

I6

DBTNTOOLG

Block transaction number too large

T

I6

DBTTLBLK0

Total blocks equal zero

A

I4

DBUNDACCMT

Cannot determine access method; trying with BG

T

I6

loading table of contents...