index checking help

[beach2112]

Is it possible to change the time in which networker checks the index. Looks like every night between 9 and 10pm, networker checks the index on 5 or sometimes 6 clients about the same time each night. This is causing my RMAN jobs to fail to write the index header because I guess it is locked. The RMAN error is:
RMAN error is:
RMAN-03009: failure of backup command on t2 channel at 04/26/2009 21:23:58
ORA-00447: fatal error in background process

Alert log of the database shows:
ORA-07445: exception encountered: core dump [index_start()+100] [SIGSEGV] [Address not mapped to object] [0x4] [] []

Any suggestions are helpful,

thank you
David

 

[denisfr]

Hello,

the only thing that locks resource is the bootstrap, according to me.

Index checking can be concurrent with a save (tested by me )

Denis

 

[605]

This usually takes place at the end of the group where the NW server is a member. In such case, create a new group for this client.

 

[denisfr]

But, it may be not a real index check but the nsrim -X launched periodically.