errors in Livecache when running a "check database structure"

[Former Member]

Helleo, i have the following error messages when i do a check database structure of our QA Livecache environment :

• DBA Action starts:

Timestamp: 20090406141745 Function: cdb Object: DATABASE

• VERIFY command:

check data

• VERIFY result:

ERR

-24988,ERR_SQL: SQL error

-9053,〰〰〰〰〰〰〰〰〰〳

17,Servertask Info: because b01pverify_participant() failed

10,Job 0 (Check Data) [executing] WaitingT147 Result=OK

6,b01pverify_participant() failed, Error code 9161 "data_page_corrupted"

17,Servertask Info: because b01pverify_participant() failed

10,Job 0 (Check Data) [executing] WaitingT147 Result=OK

6,b01pverify_participant() failed, Error code 9161 "data_page_corrupted"

17,Servertask Info: because b01pverify_participant() failed

10,Job 0 (Check Data) [executing] WaitingT147 Result=OK

6,b01pverify_participant() failed, Error code 9161 "data_page_corrupted"

• DBA Action ends:

Timestamp: 20090406141753 State: Failure

ANd i have the same result whether i run it from DB13 or from the database managerIs there a way to run the check database with a repair option ? How can i fix this ?

Thanks for your help.

Y.

Edited by: Youssef ANEGAY on Apr 6, 2009 3:59 PM

[markus_doehr2 · Accepted solution]

"Bad pages" can't be repaired.

See Note 839333 - FAQ: MaxDB error diagnosis -> corrupt data pages

I would immediately create an OSS call and let the support have a look on the system. They may be able to correct the problem but most likely they will recommend to restore from a backup not containing the error.

Markus

[Former Member · Accepted solution]

Thanks Markus for your answer ... I'll open the OSS call. I guess i'll have no choice but to restore the database ...

[markus_doehr2 · Accepted solution]

> I guess i'll have no choice but to restore the database ...

Yes - most like that will be the case

But before you do that, I'd check the hardware also (drivers, firmware, OS patches etc.). If the system is connected to a SAN I would also check the logs of that.

Markus

[Former Member]

We had to restore the LC