November 11, 1999
-Randy Keup
Below is an article from the knowledge database on Intellution's web site.
It discusses the linked alarm area database (aka AAD) and the process database (aka PDB, the usual tag database). They are apparently inseparable. There is a work around however, that seems to work. I tried it just a few minutes ago, well a bit longer than that. Anyway, here are the instructions for converting from one AAD to another (i.e. local to server).
In local configuration mode, in the database manager under the database menu, do Export... This will export all the tags to a CSV file. BE WARNED, this takes a long time. I have 1700 tags and this entire process took about an hour (see below for speed up tips).
Now shutdown FIX.
Switch to the server configuration (pointing to alarm area database on the server), and start FIX.
In the database manager after opening the database, do Reload under the database menu, and select the "empty" database.
Now also under the database menu, do Import... and select the above exported file.
Now just save as... to whatever database you use. You will of course overwrite the existing one.
It should all work now.
********** Speed up tip ***********
-----------------------------------
If like the CAEN and COT setups, you generate some number of database blocks automatically from some program, then don't export those. I would suggest deleting all automatically generated blocks before exporting.
This should eliminate a lot of them for most people. Then after the conversion, just run your program and generate those blocks again.
************ Safety tips ***********
-----------------------------------
Make sure you copy your database file to some backup beforehand in case things go wrong.
Make sure that the alarm areas you have assigned to tags exist in the server area, otherwise this won't work.
Also copy the server AAD file to the corresponding local directory once this is all working to ensure you have a local copy as well. (S. Segler)
P.S.
Here is the article. Note that the instructions aren't quite the same.
I discovered that if you open the database in server mode to start with, that you lose the alarm area information. So you have to export in local mode and import in server mode.
Article I012729 Back to List New Search
Problem 2 DYN - Alarm Area Database file ID does not match that in the Process Database file Did This Help?
Please help make KB Search better by letting us know how this article helped you with your issue.
Yes it helped
No, it didn't help
Didn't Apply
Comment
Description The following error may occur upon startup of Dynamics as a result of a mismatch of the Process Database (PDB) file and the Alarm Area Database (AAD) file
"Alarm Area Database (AAD) file ID does not match the one stored in the Process Database (PDB) file. Alarm area assignments may not be valid. This database cannot be saved."
This error will occur while LDBA.DLL is loading (as shown in the Dynamics startup window). It is normally the result of moving a PDB or AAD file from one system to another, without the other matching AAD or PDB file.
The reason that these files must match is that the Alarm Area Database defines the valid alarm area names, which are used in the process database blocks.
Workaround
In order to correct this problem, the first step is to ensure that the process database blocks are using the same alarm area names as defined in the currently loaded Alarm Area Database. This can be determined by looking at the configuration of one or more blocks in the Database Manager and checking the names of the defined Alarm Areas on the 'Alarms' tab of the block(s). The names shown in the Alarm Areas list box should then be checked against those found in the System Configuration program.
To check the currently configured alarm areas, run the system Configuration program, select 'Alarms...' from the 'Configure' menu, and then press the 'Advanced...' button. Pressing the 'Alarm Area Database' button will then show the names of the currently configured alarm areas.
If the alarm area names defined in the database blocks appear in this Alarm Area list, then this is probably the correct alarm area file, although it may have a different internal file ID which would lead to this problem.
If the alarm area names do not match those in the database, then it will be necessary to either re-define the alarm areas as defined in the database blocks, or to copy the correct AlarmAreas.AAD file to the Dynamics\LOCAL subdirectory.
Once the Alarm Area Database matches the alarm areas defined in the process database blocks the error may stop occurring, but it may continue due to an incorrect internal file ID. If the problem continues at this point then it can be resolved by the following steps
1) Export the process database by choosing Export... from the Database menu.
2) Load the Empty database supplied with Dynamics by choosing Reload...
from the Database menu and selecting the database names 'Empty'.
3) Import the exported version of the database by choosing Import... from the Database menu and selecting the previously exported database file.
This will synchronize the process database with the alarm area database, thus resolving this problem.
SH 8/20/98