(B)0[mimport-options = qwqwqqqqqqqqqqqqq>qqqqqqqqqqqwqwqq> x tqwqq> [4mACL[m qqqqqqqqqqqqwqqu x x x mqq> [4mNOACL[m qqqqqqqqqqj x x x tqwqq> [4mBATCH_UPDATE[m qqqwqqu x x x mqq> [4mNOBATCH_UPDATE[m qj x x x tqwqq> [4mCDD_LINKS[m qqqqqqwqqu x x x mqq> [4mNOCDD_LINKS[m qqqqj x x x tqwqq> [4mDATA[m qqqqqqqqqqqwqqu x x x mqq> [4mNODATA[m qqqqqqqqqj x x x mqwqq> [4mTRACE[m qqqqqqqqqqwqqj x x mqq> [4mNOTRACE[m qqqqqqqqj x mqqqqqqqqqqqqqqq<qqqqqqqqqqqqqj
1 – ACL_NOACL
Determines whether the previously defined ACLs are used in the
imported version of the database (ACL) or whether the ACLs from
the interchange file are not used (NOACL). The default is ACL.
The NOACL option overrides the access control lists specified in
the original database and uses the system default access control
lists.
2 – BATCH_UPDATE
Causes the IMPORT operation to run in batch-update mode. This is
the default. No recovery-unit journaling is performed in batch-
update mode.
3 – NOBATCH_UPDATE
Overrides the default and causes the IMPORT operation to run
in exclusive share mode, rather than batch-update mode. This
provides recovery-unit journaling so that you can recover your
database in the event of a failure during the IMPORT operation.
4 – CDD_LINKS
Causes the dictionary relationships to be preserved in the
imported database. If you specify CDD_LINKS, the IMPORT operation
attempts to reconnect the fields and records to the dictionary
pathname entities they reference. If the dictionary entity no
longer exists, you will receive a warning message. The default is
CDD_LINKS.
You cannot specify CDD_LINKS and DICTIONARY IS NOT USED.
5 – NOCDD_LINKS
Causes the IMPORT operation to run without preserving dictionary
relationships in the imported database. Fields and records
are not reconnected to the dictionary pathname entities they
reference.
6 – DATA_NODATA
Specifies whether the RDB file created by the IMPORT statement
includes the data and metadata contained in the database, or the
metadata only. DATA is the default.
When you specify the NODATA option, you import the metadata that
defines a database from an RBR file and exclude the data.
The NODATA option is not compatible with data dictionary
databases (CDD$DATABASE.RDB). An RBR file, created by an EXPORT
statement with the DATA option (the default) and generated
from a CDD$DATABASE.RDB file, cannot be used with the NODATA
option to the IMPORT statement. RDO will issue an error message
stating that the NODATA option is not valid for data dictionary
databases.
7 – TRACE_NOTRACE
Specifies whether usage statistics are logged by IMPORT. NOTRACE
is the default.
Some actions taken by the IMPORT statement can consume
significant amounts of I/O, and CPU time. These actions include
the following operations:
o Loading data
o Defining indices
o Defining constraints
When you specify the TRACE option with the IMPORT statement, RDO
writes a message to your terminal screen when each operation
begins, and writes a summary of DIO, CPU, and PAGE FAULT
statistics when the operation completes. When the IMPORT
statement finishes execution, a summary of all DIO, CPU, and
PAGE FAULT statistics is displayed. The display also includes
information on access to the RBR file, database creation and
loading of data.