Specifications

15
Agilent ChemStore C/S — Installation and Upgrading
• ChemStation Plus CD-ROM, and
• ChemStore C/S client software
(on ChemStation Plus CD-ROM).
Agilent ChemStore C/S data-
base migration
The Agilent ChemStore C/S sys-
tem includes a migration utility
which enables you to migrate your
Agilent ChemStore C/S data in the
following ways:
• Migrate Agilent ChemStore
A.01.03 or B.0x.0x data (stand-
alone) to Agilent ChemStore
C/S B.02.02 (standalone).
The standalone version of Agilent
ChemStore C/S is user-installable
from the ChemStore C/S CD-ROM
and can be added to an existing
ChemStation installation (Agilent
ChemStation software family CD-
ROM version A.09.03 or higher).
The Agilent ChemStore C/S Oracle
client/server version includes :
• ChemStore C/S server
software (included on the
ChemStation Plus CD-ROM),
• Oracle 8i standard edition
version 8.1.7 (included in
ChemStore C/S server software
on a separate CD-ROM),
• Migrate Agilent ChemStore C/S
B.02.02 data to Agilent
ChemStore C/S server data.
If you are currently running
Agilent ChemStore A.01.03 on
your system, and you wish to
migrate your data to the Agilent
ChemStore C/S server Oracle
database, you will need to
migrate in two steps. First
migrate to the B.02.02 Agilent
ChemStore C/S standalone data-
base, then migrate from there to
the Oracle database.
automated archival is restricted to
10. Each archive query is stored
under a unique user-defined name
and can be executed based on a
configurable time interval (per
query), for example, daily, weekly,
monthly or in conjunction with a
counter such as every x days. A
test functions allows the user to
obtain information on the number
of runs that the query returns at
the moment with the given query
condition. For each archive query
the name and path for the archive
unit have to be specified. The file-
name for the automatic archive
file is appended with the archival
date, resulting in a file name for-
mat “<filename>-yyyy-mm-dd”.
Each archive query can be dis-
abled when not required perma-
nently. After successful comple-
tion of the archive the data can be
automatically deleted to create
free space in the database.
Both manual and automatic
archival require re-identification
with user-ID and password.
A checksum-protected archive
catalog file in XML format is gen-
erated with each archive unit,
which contains detailed informa-
tion about the content of the
binary archive file. A generic
archive interface provides a clos-
er linkage to other applications
for enhanced archive manage-
ment (for example, archive man-
agement or hierarchical storage
management systems).
Figure 9a
Setup of automatic archive queries