Re: Cannot Add Index (-212) & (-105)
A user on IDS 10.00.FC5 hit -212/-105 errors when adding an index, with the online log showing "Assert Failed: Page Check Error in next_scan: bad data page" against a table, plus advice to run oncheck -cD. Respondents said this looked like on-disk page corruption rather than a temp-space shortage, and suggested examining the af.* assert file for the bad page contents, using oncheck (with no users connected) to see how widespread the damage was, and contacting IBM support to find the root cause. The poster found the af file referenced the temp dbspace device holding a temporary table and asked whether switching DBSPACETEMP to a newly created temp dbspace would help isolate the problem; no answer or resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
> 17:13:49 Assert Failed: Page Check Error in next_scan:bad data page
> 17:13:49 IBM Informix Dynamic Server Version 10.00.FC5
> 17:13:49 Who: Session(669, ymulla@prime2_endofday.cbq.com.qa, 1256,
> 29f571a68)
> Thread(921, xchg_3.0, 29f53d7c0, 1)
> File: rsdebug.c Line: 1056
> 17:13:49 Results: Possible inconsistencies in> 'prime20:"ymulla".tpaymentalloc'
> 17:13:49 Action: Run 'oncheck -cD 159383595'
> 17:13:49 stack trace for pid 2856 written to /export/home/informix/
> tmp/af.781131c
> 17:13:49 See Also: /export/home/informix/tmp/af.781131c
> 17:13:54 Page Check Error in next_scan:bad data page
> 17:19:07 Fuzzy Checkpoint Completed: duration was 22 seconds, 12112> buffers not flushed.
Dahya,
As Norma already suggested - this does not seem to be a temp space
issue. Rather looks like corruption on disk.
It might be interesting to have a look at the file af.781131c , the
contents of the bad page should be in there.
If the page is indeed corrupted you would have to find out whether
corruption is limited to the one page or more widespread. (Use oncheck
as suggested , if possible while no users are on the system). Then -
most important - try find out what's wrong and remove the cause. You
might want to ask IBM Informix Tech Support for help.
Rgds
Tilman
Hi Tilman,
I have part of the af.781131c file..
In the first line of the file I can see the following :-
17:13:49 bfcheck: bad page: pg_addr 0:-1056899072 != bp->bf_pagenum
152:476
Further down I see
chunk info
chunk info
00000002a033fb88: fffffff2 00980000 0016e360
00000000 ........ ...`....
00000002a033fb98: 0016e0ba 00000000 00000000
00000019 ........ ........
00000002a033fba8: 00010040 08000098 001b2f64 65762f69 ...@.... ../
dev/i
00000002a033fbb8: 6e666f72 6d69782f 74656d70 64627330 nformix/
tempdbs0
00000002a033fbc8: 312e6430 31000000 00000000 00000000
1.d01... ........
00000002a033fbd8: 00000000 00000000 00000000
00000000 ........ ........
00000002a033fbe8: 00000000 00000000 00000000
00000000 ........ ........
00000002a033fbf8: 00000000 00000000 00000000
00000000 ........ ........
00000002a033fc08: 00000000 00000000 00000000
00000000 ........ ........
The error in the table it failed 'prime20:"ymulla".tpaymentalloc' is a
temporary table which gets created while running our EOM process.
The "/dev/informix/tempdbs01.d01" is our temporary DBSpace in the
database. Can we create a new temporary DBSpace and remove the
"tempdbs01" in the DBSPACETEMP variable and use the new DBSPACE.. Say
"tempdbs04"..... Will this help to narrow down the issue.
DBSPACETEMP tempdbs01,tempdbs02,tempdbs03 # Default temp dbspaces
On Mar 2, 8:02 pm, tilleu...@web.de wrote:
> > 17:13:49 Assert Failed: Page Check Error in next_scan:bad data page
> > 17:13:49 IBM Informix Dynamic Server Version 10.00.FC5
> > 17:13:49 Who: Session(669, ymulla@prime2_endofday.cbq.com.qa, 1256,
> > 29f571a68)
> > Thread(921, xchg_3.0, 29f53d7c0, 1)
> > File: rsdebug.c Line: 1056
> > 17:13:49 Results: Possible inconsistencies in> > 'prime20:"ymulla".tpaymentalloc'
> > 17:13:49 Action: Run 'oncheck -cD 159383595'
> > 17:13:49 stack trace for pid 2856 written to /export/home/informix/
> > tmp/af.781131c
> > 17:13:49 See Also: /export/home/informix/tmp/af.781131c
> > 17:13:54 Page Check Error in next_scan:bad data page
> > 17:19:07 Fuzzy Checkpoint Completed: duration was 22 seconds, 12112> > buffers not flushed.
>
> Dahya,
> As Norma already suggested - this does not seem to be a temp space
> issue. Rather looks like corruption on disk.
> It might be interesting to have a look at the file af.781131c , the
> contents of the bad page should be in there.
> If the page is indeed corrupted you would have to find out whether
> corruption is limited to the one page or more widespread. (Use oncheck
> as suggested , if possible while no users are on the system). Then -
> most important - try find out what's wrong and remove the cause. You
> might want to ask IBM Informix Tech Support for help.
> Rgds
> Tilman