Download Database - ABB Solution Bank

Database
Section 4
Server Configuration
Whenever the user selects Server Configuration from the pull down ‘listbox’
beneath the Server Icon, the Tag Configuration program is launched with a set of
command line arguments.
%InstallPath%\Bin\TagConfiguration.exe /EB_DOMAIN %ServerDomain%
This opens the Tagdata.mdb file that resides in the Database$ share folder
specified in the registry. It is important to keep in mind that this is not necessarily
on the computer that you are opening it from.
Messages:
When opening the Server Configuration or performing database manipulation,
there is a potential for a message box to appear. Some messages indicate an
abnormal (but expected) condition based on the given circumstance, and others
will indicate a program terminating error.
Can’t Find Replicated Database :
This message indicates that at least
one of the replicated databases is unavailable. Typically this is due to the
redundant server in the pair being shutdown. If all servers are running and
this message appears, the EbDataSyncService may have “stalled” and
stopping/restarting this service or a reboot shut alleviate the problem.
Cannot get database name from server :
Typically this message will
appear when the server from which you are requesting to see the
configuration is not in the Server Broker host list. All servers in the
networked group should be in the Server Broker host list. This message
could also occur if the server is having network difficulties (Recall that the
path to the database is \\ServerName\Database$\tagdata.mdb).
The Microsoft Jet Database Engine can not open the file…
It is
already opened exclusive by another user or you need permission to view its
data:
Generally this indicates that the username and password that were
used to log into Windows NT is not a valid combination on the computer
storing the database.
Database
Page 1 of 5
Wrong database version or format: This is a fatal message when opening
the server configuration and will be followed by the message “Application
will terminate”.
Things to check:
 Has an upgrade been done and if so was the Transfer Tag Data
procedure followed?
 Does the tagdata.ldb file exist in the Database$ share of the server
possessing the configuration database and a temprep.mdb file in the
Cache$ share? If there is, this procedure may clear the situation:
1. Stop the Server Service (via Control Panel > Services)
2. Delete the .ldb file
3. Delete the temprep.mdb file (in the cache directory)
4. Place EbDataSyncService and EbServerBroker services in manual
(via Control Panel > Services)
5. Reboot the console
6. Start the above two services manually
7. Set the two services back to automatic
If the .ldb file returns soon after starting the services, or after deleting
it then the database is most likely corrupted and needs to be repaired.
Bad File Name or Number :
This is Win32 run-time error that indicates
that the file specified in the executable could not be found. This can occur if
the file does not exist or the network link has been broken between the
computers. It is also possible that this error can occur on a standalone server
if there is a problem with the Server Service on that machine. Sometimes
reloading the applicable Windows NT Service Pack resolves this problem.
Importing Tag Databases:
From the Tag Configuration Utility, the user can open the Import utility. From
this executable the following database components can be imported:
 Alarm Comments
 Engineering Unit Descriptors
 Logic State Descriptors
 Remote Motor Control Block text
 Text Selector text
 Tag Definitions
The tag definitions should always be the last item to imported so that the tables in
the database include the indexes and text associated with the descriptors, etc.
In order to import tags the revision of the tag list must be specified. If the revision
selected doesn’t match the *.ttg file format, a message box will appear during the
“Pre-processing text file” stage of the import. If this occurs simply select a
different revision and try that. If all revisions give the same message, it is
Database
Page 2 of 5
possible that either the *.ttg file is corrupted (as could happen during modification
in a text editor.) or of a revision not compatible with Conductor NT.
Following the text file processing, you have the option to pause the server or not
pause the server. The effects of each are defined as:
1. Pause the Server – Take the ICI offline, import the database, download
the updated point list to the ICI and place the ICI online. This operation
is faster and more memory efficient for the ICI but removes your ability
to view the process from the server (and its redundant if applicable).
2. Don’t Pause the Server – Adds each tag to the ICI’s database individually
with the ICI online. This operation takes longer to complete, can
fragment the ICI’s memory and causes large swings in processor/memory
usage on the server but allows you to view the process. This should only
be used when doing small updates to the database and not when
importing the entire database.
During the import if noticeable performance issues develop you should use the
Windows NT Performance Monitor to diagnose the problem. Microsoft has
defined several counters to indicate the bottleneck on the system. The main
counters are listed below:
Object
Memory
Processor
System
Counter
Pages/sec
%Processor Time
Processor Queue Length
Limit
Sustained > 5
Sustained > 90%
Sustained > 2
Typically, the limiting component on an import is the amount of physical memory
in the system. For this reason it is important to periodically compact the database
with Database Utilities. A message indicating that fact will appear following the
import process.
Enhanced Analog/Digital Tags:
When importing a database that includes the Enhanced Exception Reporting
Tag Types (Harmony Channel Definitions : FC222-225), the database must
be either a CNT2.1 (or later) or X.1 format (if using Wintools). The X.1
format must have the TagTypeSrc field viewed in the browser in order for
the Enhanced attributes to be translated into the *.ttg file. It is also important
to be using an ICI03A for the enhanced tag types to be established.
Tag Fields:
There are several fields for each tag type that are “grayed out” which prevents the
user from specifying the value. This is due to the fact that the values are read
Database
Page 3 of 5
dynamically from the source function code in the module. Therefore, the “grayed
out” fields should be considered normal
Offline Database Manipulation
It is possible to open the Tag Configuration Utility in an offline mode. This will
permit manipulation of things like the Server tag fields that may be necessary to
get proper operation. Depending on the history of the server, just setting the host
name may not be enough. To open the database in this mode, run the following
file with the applicable command line arguments.
%installpath%\Bin\TagConfiguration.exe /DBPATH “%databasepath%”
Note: Typical installations will have C:\Program Files\Conductor NT as the
%installpath% and C:\Program Files\Conductor NT\Database\Tagdata.mdb as the
%databasepath%.
Opening the tag configuration utility in this way opens a window that displays the
names of all servers in the database. Select the server you wish to configure and
press OK.
Licensing
Each server is licensed for a specific number of tags. The Primary and Redundant
must always be licensed for the same number. The features that include this are
the I90SRVR and I90SRVR-R. The Users field is a factor of 100 below the
number of tags that the machine is licensed for. For example:
If the Users field is 5 then the server is licensed for 500 tags.
Database
Page 4 of 5
This can become very critical when it appears that some tags aren’t present. If
Server Configuration is opened and the proper number of tags is shown, open
Server Diagnostics and select the “Tags” tab. The number of tags in the server
will be shown. Numbers such as 500, 1500, 5000 etc are usually dead giveaways
that the number of licensed tags has been exceeded. This can easily be verified by
looking at the licenses. If the license is for too small a number of tags to meet the
customer needs, the Conductor NT Server Expansion must be purchased to
upgrade the license to a higher number of tags.
Database
Page 5 of 5