1 – ACL
Syntax options:
ACL | NO ACL
Specifies that the IMPORT statement uses the access control lists
from the original database when it creates the new database. The
ACL option is the default. If you are using the IMPORT statement
to restructure a database, you typically want to use the ACL
option and preserve the access control lists.
The NO ACL option overrides the ACLs from the original database
and uses the database system default ACLs. Specify NO ACL if
you are using the IMPORT statement to rebuild a database on a
different system. The NO ACL option makes you the owner of the
new database and creates default access control lists.
2 – BANNER
Syntax options:
BANNER | NO BANNER
This clause requests that IMPORT display informational messages
during the import of the database header, such as product
identification, and values for some database parameters. The
default is NO BANNER which will mean most IMPORT statements
generate no output.
3 – BATCH_UPDATE
Syntax options:
BATCH UPDATE | NO BATCH UPDATE
Specifies whether the IMPORT statement stores user data and
indexes using batch-update transactions (BATCH UPDATE) or
read/write transactions for each table (NO BATCH UPDATE). The
NO BATCH UPDATE option is the default.
A batch-update transaction is faster but does not perform
recovery-unit journaling, which means you cannot recover the
database in the event of a failure during the IMPORT operation.
With the NO BATCH UPDATE option, you can recover the database.
For more information about batch-update transactions, see the
SET_TRANSACTION statement.
4 – CDD_LINKS
Syntax options:
CDD LINKS | NO CDD LINKS
Determines whether the IMPORT statement tries to reestablish
links between database definitions originally based on repository
definitions (domains and tables created with the FROM path name
clause) and their sources in the repository.
The default depends on whether or not the IMPORT statement
specifies the PATHNAME option. If the IMPORT statement does
specify PATHNAME, the default is CDD LINKS; if it does not
specify PATHNAME, the default is NO CDD LINKS.
The CDD LINKS option specifies that the IMPORT statement tries
to reestablish repository links even if you do not specify
the PATHNAME option. If you specify CDD LINKS and the database
repository definition on which a database definition was based
does not exist, the IMPORT statement generates a warning message.
The NO CDD LINKS option specifies that the IMPORT statement
does not establish data repository links even if you specify
the PATHNAME option. Specify NO CDD LINKS if you are using the
IMPORT statement to rebuild a database on a different system.
5 – COMMIT_EVERY
Syntax options:
COMMIT EVERY TABLE | COMMIT EVERY n ROWS
Specifies whether the IMPORT statement commits entire tables, or
commits a certain number of rows at regular intervals. If you use
the COMMIT EVERY n ROWS clause, you can supply a value from 1 to
2147483647 for n.
The default is COMMIT EVERY TABLE. If you use the COMMIT EVERY n
ROWS clause, the table will be left with a partial set of rows if
the IMPORT process fails.
NOTE
If the table being imported includes a storage map with the
PLACEMENT VIA INDEX clause, then the COMMIT EVERY clause
is ignored for that table. A message is displayed to inform
the database administrator of the tables that did not have
COMMIT EVERY applied. This condition is shown in Example 6.
6 – create-cache-clause
See the CREATE CACHE clause for a complete description.
7 – create-index-statement
See the CREATE INDEX statement for a complete description.
8 – create-storage-area-clause
See the CREATE STORAGE_AREA statement for a complete description.
9 – create-storage-map-statement
See the CREATE STORAGE_MAP statement for a complete description.
10 – DATA
Syntax options:
DATA | NO DATA
Specifies whether the database created by the IMPORT statement
includes the data and metadata contained in the source database,
or the metadata only. DATA is the default.
When you specify the NO DATA option, you import the metadata
that defines a database from an .rbr file and exclude the data.
Duplicating the metadata of a database while excluding the data
offers the following benefits:
o You can use established, tested metadata to create a database
to store new data. Standardized metadata can be created once
but used in multiple databases.
o You can use the duplicated metadata to test the database
structure. You can experiment with storage areas and storage
maps, and by entering sample data, you can test other aspects
of database structure.
o If a database needs testing by someone outside of your group,
you can submit the database metadata without exposing any
sensitive data. Also, if the database is very large, you need
not submit multiple reels of tape to the tester.
NOTE
The NO DATA option is not compatible with repository
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 NO DATA option for the IMPORT statement. SQL issues an
error message stating that the NO DATA option is not valid
for repository databases.
11 – DROP_CACHE
Syntax options:
DROP CACHE row-cache-name
Prevents the specified row area from being imported.
12 – DROP INDEX index-name
Prevents the specified index from being imported.
13 – DROP_STORAGE_AREA
Prevents the specified storage area from being imported.
14 – DROP STORAGE MAP map-name
Prevents the specified storage map from being imported.
15 – FILENAME file spec
Specifies the file associated with the database.
If you omit the FILENAME argument, the file specification takes
the following defaults:
o Device: the current device for the process
o Directory: the current directory for the process
o File name: the alias (if you omit the FILENAME argument, you
must specify the WITH ALIAS clause)
Use either a full file specification or a partial file
specification. You can use a logical name for all or part of a
file specification.
If you use a simple file name, SQL creates the database in the
current default directory. Because the IMPORT statement may
create more than one file with different file extensions, do
not specify a file extension with the file specification.
16 – FORWARD_REFERENCES
Syntax options:
FORWARD_REFERENCES | NOFORWARD_REFERENCES
The EXPORT interchange file contains declarations of all routines
that will be referenced by other definitions. The default is
to declare the interfaces to those routines prior to creating
domains, tables, views, triggers, functions, procedures and
modules that may need them. The default is FORWARD_REFERENCES.
Use NO FORWARD_REFERENCES to disable these declarations. However,
this may result in definition failures during the IMPORT.
If you include the FORWARD_REFERENCES option on the IMPORT
command line then informational messages will be generated for
each declared routine.
17 – FROM file spec
Names the interchange .rbr file that the IMPORT statement uses as
a source to create a new database.
18 – import-root-file-params
Parameters that control the characteristics of the database root
file associated with the database, or characteristics stored in
the database root file that apply to the entire database.
For more information on other "import-root-file-params-1",
"import-root-file-params-2", "import-root-file-params-3", and
"import-root-file-params-4", see the descriptions of "root-
file-params-1", "root-file-params-2", "root-file-params-3", and
"root-file-params-4" in the CREATE DATABASE.
19 – limit-to-clause
See Select_Expressions in the Oracle Rdb SQL Reference Manual for
information about the LIMIT TO clause.
20 – literal-user-auth
Specifies the user name and password for access to databases,
particularly remote databases.
This literal lets you explicitly provide user name and password
information in the IMPORT statement.
21 – order-by-clause
See Select_Expressions in the Oracle Rdb SQL Reference Manual for
information about the ORDER BY clause.
22 – PROTECTION_IS
Syntax options:
PROTECTION IS ANSI | PROTECTION IS ACLS
By default, the IMPORT statement retains the protection style
of the database that was exported. However, if you specify
PROTECTION IS ANSI or PROTECTION IS ACLS, then the IMPORT
statement creates a database with that protection type. If
the protection of the database created is different from the
protection of the database that was exported, then no protection
records are imported and you will receive default protections.
23 – select-clause
See Select_Expressions in the Oracle Rdb SQL Reference Manual for
information about the SELECT clause.
24 – storage-area-params
Specifies parameters that control the characteristics of database
storage area files. You can specify most storage area parameters
for either single-file or multifile databases, but the effect of
the clauses differs.
o For single-file databases, the storage area parameters
specify the characteristics for the single storage area in
the database.
o For multifile databases, the storage area parameters specify
a set of default values for any storage areas created by the
IMPORT statement that do not specify their own values for
the same parameters. The attributes of a storage area are
supplied by the interchange file unless redefined by the
IMPORT statement. The default values apply to the storage
area named in CREATE STORAGE AREA database elements.
For details about storage area parameters, see the CREATE
STORAGE_AREA clause.
NOTE
The CREATE STORAGE AREA clauses can override these
default values. The default values do not apply to any
storage areas created later with the ALTER DATABASE
statement.
25 – TRACE
Syntax options:
TRACE | NO TRACE
Specifies whether usage statistics are logged by the IMPORT
statement. The NO TRACE option is the default.
Some actions taken by the IMPORT statement can consume
significant amounts of I/O resources and CPU time. These actions
include the following operations:
o Loading data
o Defining indexes
o Defining constraints
When you specify the TRACE option with the IMPORT statement,
SQL writes a message when each operation begins, and writes a
summary of DIO (direct input/output operations), 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. For more information about these statistics, see
the Oracle Rdb7 Guide to Database Performance and Tuning.
26 – USER username
Syntax option:
USER 'username'
Defines a character string literal that specifies the operating
system user name that the database system uses for privilege
checking.
27 – USING password
Syntax option:
USING 'password'
Defines a character string literal that specifies the user's
password for the user name specified in the USER clause.
28 – WITH ALIAS alias
Specifies the alias for the implicit database attach executed
by the IMPORT statement. An alias is a name for a particular
attachment to a database.
You must specify an alias or a file name. If you omit the WITH
ALIAS clause, the default alias for the database created by
the IMPORT statement is RDB$DBHANDLE. If you omit the FILENAME
argument, the IMPORT statement also uses the alias as the file
name for the database root file and creates the root file in
the current default directory. If you omit WITH ALIAS, you must
specify the FILENAME argument.