Simplicty and flexibility!


Table name already exist - Method to avoid this problem recursively


Started by Marco Marchesi
Search
You will need to Sign In to be able to add or comment on the forum!

Table name already exist - Method to avoid this problem recursively

I return to a topic already covered both on the Forum and on your Blog.

http://www.dataease.com/DG3_ForumList/?ParentID=0000002812&field1=0000002812

http://www.dataease.com/DG3_BlogList/?ParentID=0000000494&field1=0000000494

Sometimes a wrong items is generated in the catalog file RDRRxAAA.DBM which causes the following error when the database is opened:

It has been repeatedly indicated how to correct the error but nothing on how to avoid generating it.

This error recurs periodically in the database for no apparent reason for the $DeStat_DQLInfo$ item which is a system table repeated many times in this file.

Obviously, by correcting the last item from 0C to 0F, everything is resolved.

So the problem lies in the product, how can I prevent this from happening all the time?

Thanks.

[DataEase 8.5]


Written by Marco Marchesi 02/03/21 at 17:01:50 Dataease [{8}]FIVE

Re:Table name already exist - Method to avoid this problem recursively

The problem is related to an automated update routine that look after the Status tables in DFW. 

When it identify that the current version is "outdated" it will replace it and if this replacing goes wrong you get your problem.


As it is highly annoying and these tables are not critical we have in future versions removed this old fashioned updating approach.

However they are still there in 8.5 so what you can do to stop this from happing is to syncronize the files "manually".

I.e. set the 0e to 0f on all occurences of DQL info in the rdrrr and delete all files that correspond to the entries in the app.
Then start over and DE85 will create the latest version and after that it will be in sync.


Written by DataEase 05/03/21 at 12:03:24 Dataease [{8}]FIVE
DG3_ForumList