Assert failed: Archive detects that page 0x....... is corrupt
<FONT face=3D"Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size= =3D2><DIV>Hello,</DIV><DIV> </DIV><DIV>I have assert fails during an o= nbar level 0. 13 pgs are reported in the online log as corrupt as one of ou= r dbspaces are archived. </DIV><DIV> </DIV><DIV>onchecks cd, cD, cIw, = and cr are all successful ... no errors. The table (SAP r3 system) is heavi= ly used during nightly processing, and there are no job failures reported a= gainst it. It seems that the data is accessible.... at least it's gets read= ok. This is an assumption on my part that the pgs in question hold records= required last night, and not historical in nature.</DIV><DIV> </DIV><= DIV>As this is an SAP system and is not down, the OSS mgs we opened is on h= igh status. It will be awhile before it is addressed.</DIV><DIV> </DIV= ><DIV>I thought I would ask you all if you have experienced this assert fai= l before and have any insight.</DIV><DIV> </DIV><DIV>Correlating the b= ar=5Fact.log with both assert fail events is not conclusive. The first asse= rt fail was within 4 minutes of a bar=5Fact error msg 130. However the seco= nd assert fail (reproducing the errors) does not correspond with any errors= in bar=5Fact.</DIV><DIV> </DIV><DIV> </DIV><DIV>Specs:</DIV><DIV= >SAP R3</DIV><DIV>HPUX 11.11</DIV><DIV>IDS 7.31FD2X7</DIV><DIV> </DIV>= <DIV>Onbar with HP's Data Protector 5.0 (Omniback)</DIV><DIV> </DIV><D= IV> </DIV><DIV> </DIV><DIV>Regards,<BR>Chris St. Aubin<BR><BR>Dat= abase Administrator, & <BR>Disaster Recovery Coordinator<BR>Reebok Inte= rnational, Ltd<BR>Canton, Massachusetts<BR><BR>PH: 781.401.4273<BR>E-m= ail: <A href=3D"mailto:chris.staubin@reebok.com" target=3Dblank >chris.stau= bin@reebok.com</a><BR></DIV></FONT>= sending to informix-list
Chris, It appears that somthing must be wrong with how you've submitted your posting. Either that or Microsoft is suddenly not able to understand HTML... ;-) chris.staubin@reebok.com wrote in message news:<c4mk6p$a4o$1@terabinaries.xmission.com>... > <FONT face=3D"Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size= > =3D2><DIV>Hello,</DIV><DIV> </DIV><DIV>I have assert fails during an o= > nbar level 0. 13 pgs are reported in the online log as corrupt as one of ou= > r dbspaces are archived. </DIV><DIV> </DIV><DIV>onchecks cd, cD, cIw, = > and cr are all successful ... no errors. The table (SAP r3 system) is heavi= > ly used during nightly processing, and there are no job failures reported a= > gainst it. It seems that the data is accessible.... at least it's gets read= > ok. This is an assumption on my part that the pgs in question hold records= > required last night, and not historical in nature.</DIV><DIV> </DIV><= > DIV>As this is an SAP system and is not down, the OSS mgs we opened is on h= > igh status. It will be awhile before it is addressed.</DIV><DIV> </DIV= > ><DIV>I thought I would ask you all if you have experienced this assert fai= > l before and have any insight.</DIV><DIV> </DIV><DIV>Correlating the b= > ar=5Fact.log with both assert fail events is not conclusive. The first asse= > rt fail was within 4 minutes of a bar=5Fact error msg 130. However the seco= > nd assert fail (reproducing the errors) does not correspond with any errors= > in bar=5Fact.</DIV><DIV> </DIV><DIV> </DIV><DIV>Specs:</DIV><DIV= > >SAP R3</DIV><DIV>HPUX 11.11</DIV><DIV>IDS 7.31FD2X7</DIV><DIV> </DIV>= > <DIV>Onbar with HP's Data Protector 5.0 (Omniback)</DIV><DIV> </DIV><D= > IV> </DIV><DIV> </DIV><DIV>Regards,<BR>Chris St. Aubin<BR><BR>Dat= > abase Administrator, & <BR>Disaster Recovery Coordinator<BR>Reebok Inte= > rnational, Ltd<BR>Canton, Massachusetts<BR><BR>PH: 781.401.4273<BR>E-m= > ail: <A href=3D"mailto:chris.staubin@reebok.com" target=3Dblank >chris.stau= > bin@reebok.com</a><BR></DIV></FONT>= > sending to informix-list