about error -8: Execution failed, parse again

[Former Member]

Hi,

today a transaction in my system failed with this message:

org.exolab.castor.jdo.QueryException: com.sap.dbtech.jdbc.exceptions.DatabaseException: [-8]: Execution failed, parse again

checking docs about -8 message the Explanation is:

The parse identification (parsid) became invalid by modifications made to the database catalog during parsing and executing a statement.

what modifications? as no one changed database catalog in production with users using the system, its something made by maxdb itself? maybe because Automatic Statistics Update is ON? or maybe a parameter i must increase to avoid some type of loss in catalog cache?

executing the transaction again, works, but i must avoid that to occurs again, as this is the first time i see this message.

thanks for any information

Clóvis

[former_member229109 · Accepted solution]

Hello Clóvis,

What is the version of your database?

May be you hit the known problem reported in PTS 1144497.

< www.sapdb.org/webpts >

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hello Natalia,

its version MaxDB 7.6.03.07 running on Linux CentOS x86_64.

i treid to search in PTS but cant returns any result, you can paste here the full link?

best regards

Clóvis

[former_member229109 · Accepted solution]

Hello Clóvis,

-> www.sapdb.org/webpts -> Advanced Search -> Number 1144497

then seach

-> The reported in PTS case should be fixed as 7.6.03.03.

And you are using 7.6.03.07.

Please check if more details could be found in knldiag.err and knldiag file.

Do have the scenario to reproduce this error.

Thank you and best regards, Natalia Khlopina