DB 7.8 Restart fails with SQL error -9407, unexpected error 3

[ulrich_lickert]

Hello,

MaxDB Instance (7.8.01.18) fails to restart with the error

"SQL error -9407 System error: unexpected error 3

Internal errorcode 6433 "system_error" 20017, Restart Filesystem failed with

'System error unexpected error'

9, File directory restart failed; error '3'

31, Error linking entry to parent; file no '000000004066',

parent file no '000000000000000000033D',

file type 'IndexFile', error '11'

We had the problem "[-8]: Execution failed, parse again" with one table,

then we tried to restart the database. Now it doesn't come up any more.

Is there another possibility instead of a recovery?

Greetings

Ulrich

[thorsten_zielke · Accepted solution]

Your problem description sounds very similar to the following error:

PTS1237652:

"Appearance:

Restart fails with file directory corruption:

31,Error linking entry to parent; file no 'xxx', parent file no 'yyy', file type 'IndexFile', error '11'

Preconditions and circumstances:

During a recreate index operation the index was dropped and recreated manually.

Workaround:

None. The system must be recovered to the time just before the index was recreated."

Please note that this is one of those issues that has only been fixed with 7.8.02. 7.8.02 is currently in customer testing, if anyone wants to join, just open a CSS message and test this version before we make it generally available for download.

Best regards,

Thorsten

[ulrich_lickert]

Hello,

thank you, I think your description matches.

I activated "automatic recreation of Bad Indexes", and I think that the problem occured

during automatic fixing this index.

Recovery of the database was successful, after this I deactivated the "automatic fixing"-feature.

This also is related to my post about Bad Indexes with DATE-fields (since this is the main cause,

why we activated this feature and did the migration to 7.8)

Regards

Ulrich