Error: 697, Severity: 21, State: 1

[former_member207908]

Dear Experts,

I received the following error

Error: 697, Severity: 21, State: 1

An attempt was made to fetch logical page '2382' for database 'saptools' (5), object 'DBH_SNAP_TABLES' (2005579152), index 'DBH_SNAP_TABLES' (0), partition 'DBH_SNAP_TABLES_2005579152' (2005579152) from cache 'default data cache'. Wrong logical page '2398' was found in cache

Acc to Sybase troubleshooting guide, we can restart to clear the memory error.

I want to know if there is any alternative for fixing this error

What could be the root cause/reason for this error to occur?

Why I'm seeing "Wrong logical page '2398' was found in cache" ?

Any insight will be much appreciated

Attachment: errorlog

Regards,

Rajesh

error 697_errorlog.txt.zip

[former_member187136]

Rajesh,

Since the problem occurs in cache, it is a soft error.

Shut down and restart Adaptive Server to clear the memory corruption.

This error occurs when Adaptive Server tries to access an object in cache but arrives at an invalid page. The page number is correct on disk, but it does not match the page number of the page in memory.

Regards

Kiran

[former_member207908]

Thanks for your response Kiran. Restart didn't stop the error occurring again.

[former_member207908]

Dear Experts.

The error still persists and I want to fix it before raising it to SAP (is possible).

Let me know the remedy for this issue.

[former_member187136]

Rajesh,

Unfortunately the sybase documentation says the same thing for your problem:

Error 697

Severity 

  20

Error Message

  An attempt was made to fetch logical page '%ld' for

  object '%ld' in database '%d' from cache '%.*s'.

  Wrong logical page '%ld' was found in cache.

Explanation

     This error occurs when Adaptive Server tries to access an object

  in cache but arrives at an invalid page. The page number is correct

  on disk, but it does not match the page number of the page in memory.

  Error 697 results in a stack trace and breaks your connection to

  Adaptive Server.

Action

  Since the problem occurs in cache, it is a soft error. Shut down

  and restart Adaptive Server to clear the memory corruption.

If you still need us to dig further we should take the memory dump and analyse through raising the incident

Regards

Kiran K Adharapuram

[former_member187136]

Rajesh,

Could you able to collect a mini dump so that we can analyse it accordingly?

Regards

Kiran K Adharapuram

[former_member207908]

Thank you Kiran.

Please find the attched errorlog.

Restart date is March 06, 2015

Regards,

Rajesh

error697_errorlog_stacktrace.txt.zip

[former_member207908]

Hi Kiran,

Received the error again. Attached is the error mini dump for your analysis.

Regards,

Rajesh

dump.txt.zip

[former_member207908]

Dear Kiran,

Attached is dbcc output for the following comands

dbcc checkcatalog (database_name)

dbcc checktable (table_name)

dbcc checkalloc (database_name)

Regards,

Rajesh

dbcc output.txt.zip

[former_member187136]

Hello Rajesh,

Its Error:697 again

The Checktable output says:

Checking partition 'DBH_SNAP_TABLES_2005579152' (partition ID 2005579152) of table 'DBH_SNAP_TABLES'. The logical page size of this table is 16384 bytes.

Msg 697, Level 16, State 1:

Server 'E20', Line 1:

An attempt was made to fetch logical page '2382' for database 'saptools' (5), object 'DBH_SNAP_TABLES' (2005579152), index 'DBH_SNAP_TABLES' (-1), partition 'DBH_SNAP_TABLES_2005579152' (2005579152) from cache 'default data cache'. Wrong logical page '2398' was found in cache.

DBCC execution completed.

If DBCC printed error messages, contact a user with System Administrator (SA) role.

Explanation:  

  This error occurs when Adaptive Server tries to access an object   in cache but arrives at an invalid page. The page number is correct on disk, but it does not match the page number of the page in memory.

  Error 697 results in a stack trace and breaks your connection to   Adaptive Server.

Action

  Since the problem occurs in cache, it is a soft error. Shut down and restart Adaptive Server to clear the memory corruption.

PS: If this is not working out then you should try with the "saptools" restore from a good backup

Regards

Kiran K Adharapuram