IDS Forum

Re: HDR - Alarmprogram when down

Posted By: Art Kagel
Date: Tuesday, 3 April 2012, at 8:52 a.m.

In Response To: Re: HDR - Alarmprogram when down (DERRICK MULLER)

OK, so the log message on the secondary is indicating that a bad rowid in a
log record could not be rolled forward. That's bad.

Yes, try dropping all of the violations tables, but first you have to STOP
VIOLATIONS FOR <tablename>; then you can DROP TABLE <tablename>_vio; DROP
TABLE <tablename>_dia;

However, the messages from oncheck are just warnings that because those
tables have page level locking enabled oncheck has to lock the pages of the
indexes as it is checking them which it tries to avoid doing unless you
tell it to.

So, the oncheck -cDI came up clean? I only see the index checks (-cI) did
you also do the data checks (-cD)?

If, after dropping the violations tables and rebuilding the secondary again
from an archive, you still can't keep replication up, I see two choices:
1 - open a support case with IBM
2 - unload all of your databases with dbexport or myexport, reinitialize
the instance, and reload the databases then reestablish replication again
with a clean engine.

I'm also going to suggest that you upgrade to 11.70.FC4GE. I don't know of
any specific problems in .FC3 that are related, but it certainly can't hurt
and .FC4 fixes some performance problems with the new readahead algorithm.

You say you used HPL to load the CISAM data into IDS. Just curious, did
you use DELUXE mode or EXPRESS mode?

Art

Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/

Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.

On Tue, Apr 3, 2012 at 8:23 AM, DERRICK MULLER <derrick@xact.co.za> wrote:

> Thanks Art
>
> This informix stuff looks too smart. If I understand this all correctly the
> seconadary will NOT accept corrupt or damaged looking data thereby
> protecting
> the integrity of the last good data accepted.
>
> Running oncheck give following:
>
> ON ALL DB INDEXES WE GET:
> Validating indexes for arb_db:wwwrun.sa22_qt_so_hd...
> Index 224_345
> Index fragment partition arb_dat_dbs in DBspace arb_dat_dbs
> Index sa22_stk_enq
> Index fragment partition arb_idx_dbs in DBspace arb_idx_dbs
> Index sa22_dl_code_name
> Index fragment partition arb_idx_dbs in DBspace arb_idx_dbs
> Index sa22_loc_type_doc_no
> Index fragment partition arb_idx_dbs in DBspace arb_idx_dbs
>
> Is there any significance with "Index fragment............." message or is
> this normal?
>
> ON INDEXES LEFT OVER FROM HPL (_vio & _dia from unique constraints):
>
> WARNING: index check requires a s-lock on tables whose lock level is page.
> Validating indexes for arb_db:wwwrun.bo30_tran_dia...
> WARNING: index check requires a s-lock on tables whose lock level is page.
> Validating indexes for arb_db:wwwrun.bo30_tran_vio...
>
> Should we be manually be dropping these _vio & _dia tables after HPL run?
> HPL is a once of to convert from current DBISAM db to Informix DB.
>
> ON TABLE SPACES (same _vio & _dia):
>
> TBLspace data check for arb_db:wwwrun.bo30_tran_dia
> WARNING: index check requires a s-lock on tables whose lock level is page.
> TBLspace data check for arb_db:wwwrun.bo30_tran_vio
> WARNING: index check requires a s-lock on tables whose lock level is page.
>
> HERE IS THE SECONDARY LOG AT POINT OF FAILURE:
> (same error as on primary at same time: 12:37:46 Rollforward of log record
> failed. iserrno = 126)
>
> 12:34:27 Maximum server connections 0
> 12:34:27 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
> 0,
> Plog used 220, Llog used 0
>
> 12:37:46 Rollforward of log record failed. iserrno = 126
> 12:37:46 Log Record: log = 262, pos = 0x3160a8, type = OLDRSAM:HUPAFT(43),
> trans = 3547280096119226461
> 12:37:46 Assert Failed: Logical log replay error.
> 12:37:46 IBM Informix Dynamic Server Version 11.70.FC3GE
> 12:37:46 Who: Session(24, informix@arb-vdc-backix, 0, 0x5d64f270)
>
> Thread(51, xchg_1.3, 5d615fc0, 1)
>
> File: rsprecvr.c Line: 7269
> 12:37:46 Results: The secondary server cannot continue.
>
> If you agree I think we will drop the _vio & _dia to test.
>
> Thanks again
>
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>

--14dae93408159a870104bcc5c870

Messages In This Thread

• HDR - Alarmprogram when down
  DERRICK MULLER -- Tuesday, 3 April 2012, at 5:07 a.m.
  • Re: HDR - Alarmprogram when down
    Art Kagel -- Tuesday, 3 April 2012, at 6:49 a.m.
    • Re: HDR - Alarmprogram when down
      DERRICK MULLER -- Tuesday, 3 April 2012, at 8:23 a.m.
      • Re: HDR - Alarmprogram when down
        Art Kagel -- Tuesday, 3 April 2012, at 8:52 a.m.
        • Re: HDR - Alarmprogram when down
          DERRICK MULLER -- Wednesday, 4 April 2012, at 4:16 a.m.
          • Re: HDR - Alarmprogram when down
            Art Kagel -- Wednesday, 4 April 2012, at 6:09 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.