HI all,

we encountered this sybase error Error: 1131, Severity: 22,State: 3 and Error: 1142, Severity: 22,State: 3 while running reorg today.thought of sharing with you all.Happy reading.
we ran checkstorage job on this object and reported no errors.Below is the expanation from the sybase solved case.

--------------------------------------------------------------------------------------------------------------------------------------

Error: 1142 and Error: 1131 This happened while running REORG REBUILD on this table.

Adaptive Server Enterprise/12.5.0.3/EBF 11442 ESD#4/P/Sun_svr4/OS5.8/rel12503/1939/64-bit/FBO/Sun Sep 21 05:21:37 2003

02:00000:00603:2005/10/29 11:55:39.34 server Error: 1142, Severity: 22,State: 3
02:00000:00603:2005/10/29 11:55:39.34 server Invalid OAM Page 2448.
Found pstat=0x8008, object=509453089, database=4, indid=0
02:00000:00603:2005/10/29 11:55:39.35 server Error: 1131, Severity: 22,State: 3
02:00000:00603:2005/10/29 11:55:39.35 server The OAM for object 509453089, index 0, oam page 2448, database=4, is currently allocated to another object.
02:00000:00603:2005/10/29 11:55:39.35 server Error: 1131, Severity: 22,State: 3
02:00000:00603:2005/10/29 11:55:39.35 server The OAM for object 509453089, index 0, oam page 2448, database=4, is currently allocated to another object.
02:00000:00603:2005/10/29 11:55:39.35 server Error: 1131, Severity: 22,State: 3
02:00000:00603:2005/10/29 11:55:39.35 server The OAM for object 509453089, index 0, oam page 2448, database=4, is currently allocated to another object.
02:00000:00603:2005/10/29 11:55:39.35 server Error: 1131, Severity: 22,State: 3
02:00000:00603:2005/10/29 11:55:39.35 server The OAM for object 509453089, index 0, oam page 2448, database=4, is currently allocated to another object.
----------------------------------
Key Words: 1142 1131 reorg
Tip or Workaround
From Troubleshooting and Error Messages Guide --

Error 1142 can be either

(A) a serious error due to actual corruption in the database, or

(B) a result of misusing a system function (data_pgs, reserved_pgs, rowcnt, or used_pgs).

The error can occur from incorrect use of any of the following system functions that retrieve information about allocation pages:

data_pgs

reserved_pgs

rowcnt

used_pgs

For example, if you incorrectly type:

1> select reserved_pgs (id, root) from

2> master..sysindexes

3> where id = object_ID("table_name")

4> go

you will get Error 1142, because the reserved_pgs system function attempted to retrieve an invalid OAM page. (Replacing root in the above example with a correct OAM page, for example doampg, would give expected results.)


So for our error 1131 and 1142 on STATE 3, you can consider it as a informational message and not a fatal error.

CR 382855.

*****************************************************************

Title -- BUILTINS: errors 1131 and 1142 get written in the errorlog often



When the errors 1131 and 1142 are raised by the OAM builtins such as data_pgs() or used_pgs(), they are unexpectedly also written in the ASE's error log.



Words from engineering --

In pg__isoampg_valid() we may raise error 1131 (OAMINVALID).

"The OAM for object %ld, index %d, oam page %ld, database=%d, is currently alloc

ated to another object."

Function pg__isoampg_valid() is called by pg__oambuiltin() only.

The latter implements the OAM builtins like data_pgs(), used_pgs(), etc.

The status value of error msg 1131 is 3 in this case. Its severity value is EX_TABCORRUPT resulting in the error msg being written in the error log.

Similarly do the same for error msg 1142 (OAMINVALID_1) being potentially raised by pg__isoampg_valid() with a state value of 3.

"Invalid OAM Page %ld. Found pstat=0x%x, object=%ld, database=%d, indid=%d."

Workaround -- May want to use trace flag 1116.

It is fixed in ASE 12.5.3 ESD#3.

*****************************************************************

You may want to use workaround to add trace flag 1116 in your RUN_server file and recycle the server.
Resolution
Applying the 12.5.3 ESD #3 EBF will be the eventual resolution, but for now, try traceflag 1116 in the RUN_server file.

Resolutions: Bug is fixed traceflag workaround