Question
What can I do if I get a Raima Database Manager Error with ES-K1?
Raima Database Manager Error
Answer
First of all, make sure that the ES-K1 installation path is not longer than 20 characters.
If you find that your path is too long, then you can try to move the folder <ES-K1 installation path>\DATA\ to another path that is shorter, e.g.
c:\ES-K1\DATA\
If you do this, then you also have to enter the new path in ES-K1:
Open the file <ES-K1 installation path>\EXECUTE\ES-K1.INI with the notepad editor and change the line Appl. Data Path=C:\ES-K1.171\Data accordingly.
A power failure might have occurred while the PC had ES-K1 save data
(in the subdirectory <ES-K1 installation path>\DATA\ ).
Since ES-K1 uses a database system (RAIMA Data Manager), a number of files on the hard drive are changed whenever data is saved.
Due to a power failure or an abrupt hang-up/ending of the application, for example, an inconsistency may have occurred in the database and now cause these error messages.
We suggest that you try the following:
1) Recreate the database key files.
a) Copy the file "KEYBUILD.EXE" into the subdirectory <ES-K1 installation path>\DATA\
b) Close ES-K1, open a DOS box ("Command Prompt"), and go to the subdirectory <ES-K1 installation path>\DATA\
The easiest way to do so is via opening the Windows file explorer, clicking this folder and selecting 'Command Prompt - current folder' in the context menu (click the right mouse button).
c) Enter the command keybuild emi_db
Any error messages? => Please make notes.
d) Restart ES-K1 again.
If this does not help, then you have to proceed as follows:
2) Drag the data into a new database.
a) Start ES-K1 and export all (!) local files to a new external database (e.g. a path c:\esk1_tmp\).
b) Close ES-K1 and rename the directory \DATA\ to e.g. \DATA_BAK\.
c) Create a new folder \DATA\.
d) Copy all files from the folder \DATANULL\ (available with V1.71 only) into this folder \DATA\.
e) Start ES-K1: Now your ES-K1 database looks "empty" (it contains only the basic key files needed to describe an empty database).
f) Import all your data from the external database.
g) Run your test. - Do you still get these error messages?
These steps will hopefully help you. iIf not, then we still have means to "repair" a broken database, but this is not free of charge.
In addition, you should perhaps follow the recommendation from the ES-K1 ReadMe file:
"It is strongly recommended that you regularly move measurement results and other (test) result files into backup databases. This helps a lot to keep the size of the database easily manageable.
Besides, it makes sense to have regular (e.g. weekly) backups of the entire hard drive so that any accidental damage to the data will not harm the system too much (e.g. use a tape streamer, a server, or a second hard drive)."