Restore error

artping

While restoring a 3.70 database I received an error module 19 internal error 1355. Does anybody know the meaning of this error?

Thanks
Art

Marije_Brummel

Search the forum for 1355. You'll find lots of posts.

garak

Module 19 is Database, internal error 1355 means "#Err_DB_DBMNotReentrant DB_Err(1355)".

So, this connoted, that when the user performs some read operation that the server determines will take a long time, it sends a message to the client telling it to put up a dialog box asking whether the user wants to cancel the request, and then waits for user input. This results in the client asking the server for some information needed to display the dialog box. This read request falls into the same read routine that the user is already in. However, this routine is not reentrant.

the error can occure, when you have network problems or the server has hardware problems or is bussy). First, try to update to a new version / HF or SP.

regards

garak

Here a description from Timo:

The way this error is provoked is the following:
1) Client issues a db request (which sits in queue on the server)
2) Client doesn't get a response in a timely manner (because the server is either busy with this queue or with something else)
3) Client re-issues the same db request
4) Server says "why do you want the same?" = "non-reentrant code"
The reasons are usualy:
a) the delay between client and server. I have seen it at a big installation when doing a restore (or changing/redesigning table objects) as client server.
When doing the same as client only (on the server) everything was OK. Additionally you must not re-design table on running system
(while old table objects might be in object cache of some other clients) - you may corrupt the database.
b) the server is busy responding this or other requests.
This may be a performance issue and you need to let us know if that is standard code or added functionality.
In both cases, wrongly selected key or poorly structured SIFT fields and keys are most likely to be the problem.

You'll get the error message when a particular piece of code in the database manager is called twice (probably from two different processes).
This errror is generated deep down in the database manager and can be caused by programming.
But it is a temparamental error that may not appear next time you try to run the same process.


I could fix it using two "solutions":
a) Deactivate the secondary keys (table item posts and BIG tables).
Run the Backup using the Navision client.
Restore the objects only.
Restore the Data
Activate the keys.
b) Set the DBMS Cache value (Tools --> Options) to a high value (e.g. 550000).
Commit Cache =NO
TempFilePath = e:/temp

Make sure that you will have enough disk space in a different partition than the S.O.
(if you Nav DB is 10 GB, the E: partition should be greater than 10 GB).