Makes a copy of a database in an intermediate, compressed form.
Use the RDO IMPORT statement on this export file to rebuild the
Oracle Rdb database.
Example:
RDO> EXPORT 'DEPT3:PERS' INTO 'DISK2:PERSONNEL.RBR'
1 – More
Use EXPORT and IMPORT to:
You must have the Oracle Rdb READ privilege to the database
relations to use the EXPORT statement.
o Restructure an Oracle Rdb single-file database into a multifile
database
o Restructure a multifile database
o Migrate a database from one DSRI-compliant database management
system to another
o Create a version-independent copy of the database for
archiving purposes
o Create an empty target database that uses the same data
definitions as a source database by copying the metadata,
but not the data, to the target database
o Change database and storage area characteristics that you
cannot change with the CHANGE DATABASE statement
The IMPORT and EXPORT statements are not intended for regular
backups of the database. For regular backups and restorations of
Oracle Rdb databases, use the RMU/BACKUP and RMU/RESTORE commands.
2 – Format
(B)0[m[4mEXPORT[m q> database-file-spec q>INTO q> interchange-file-spec qk
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mqqwqqqqqqqqqqqqqqqqqq>qqqqqqqqqqqqqqqqqqqwqqqqqqq>
mq> [4mWITH[m qqqqqwqqq> [4mEXTENSIONS[m qqqqqqqu
tqqq> [4mNOEXTENSIONS[m qqqqqu
tqqq> [4mDATA[m qqqqqqqqqqqqqu
mqqq> [4mNODATA[m qqqqqqqqqqqj
2.1 – database-file-spec
The file specification for the database you want to export. Use
either a full or partial file specification or a logical name.
If you use a simple file name, Oracle Rdb looks for the database in
the current default directory. If you do not specify a file type,
Oracle Rdb uses RDB.
2.2 – interchange-file-spec
The file specification for a file in which EXPORT places an
intermediate version of the database. Use either a full or
partial file specification or a logical name. If you use a simple
file name, Oracle Rdb places the interchange file in the current
default directory. The default file type is RBR.
2.3 – WITH_EXTENSIONS
Specifies whether the exported format of the database is
compatible with a pre-Version 3.0 Oracle Rdb database (WITH
NOEXTENSIONS), or with an Oracle Rdb database created with Version
3.0 Oracle Rdb software or higher (WITH EXTENSIONS). The default is
WITH EXTENSIONS. The WITH EXTENSIONS option also directs Oracle Rdb
to preserve other parameters about the physical structure of
the exported database. Use WITH NOEXTENSIONS when you export
a database that you plan to import on pre-Version 3.0 Oracle Rdb
software.
When you specify the WITH NOEXTENSIONS option, null flags for
missing value fields are not exported, therefore numeric missing
values are replaced by zeros and character missing values are
replaced by blanks.
Note also that when you specify the WITH NOEXTENSIONS option,
features of Version 3.0 and higher Oracle Rdb databases are not
exported. Storage maps, triggers, and collating sequences, for
example, are not backed up when you specify the WITH NOEXTENSIONS
option.
The WITH NOEXTENSIONS option is not compatible with data
dictionary databases (CDD$DATABASE.RDB). If you attempt to export
a CDD$DATABASE.RDB database, RDO issues an error message stating
that the NOEXTENSIONS option is not valid for data dictionary
databases.
2.4 – WITH_DATA
Specifies whether the RBR file includes the data and metadata
contained in the database (WITH DATA), or the metadata only (WITH
NODATA). The default is WITH DATA.
When you specify the WITH NODATA option, the EXPORT statement
copies metadata from the source database to an RBR file. Use the
IMPORT statement to generate an empty database whose metadata is
identical to that of the source database.
The WITH NODATA option is not compatible with data dictionary
databases (CDD$DATABASE.RDB). If you attempt to export a
CDD$DATABASE.RDB database, RDO issues an error message stating
that the NODATA option is not valid for data dictionary
databases.
3 – Example
Example 1
The following example shows how to export a database to a disk
file:
RDO> EXPORT
cont> 'DEPT3:PERSONNEL.RDB' INTO
cont> 'EXPORT$DISK:[EXPORT]PERSONNEL.RBR'
This statement creates an interchange file for the
PERSONNEL database from the database file identified by
DEPT3:PERSONNEL.RDB. DEPT3 in this case is a logical name for
the device and directory where the database is located. The copy
is stored on EXPORT$DISK in the directory [EXPORT]. By default,
the database is exported WITH EXTENSIONS and WITH DATA.
Example 2
The following example shows how to export a database to a
magnetic tape volume:
$ INITIALIZE MUA0:
_Label: PERS
$
$ MOUNT MUA0:
_Label: PERS
_Log name:
$ RDO
RDO> EXPORT 'DEPT3:PERSONNEL.RDB' INTO 'MUA0:PERSONNEL.RBR'
This statement creates an intermediate copy of the database on
the magnetic tape volume labeled PERS, mounted on device MUA0:.
Example 3
The following example shows how to export the metadata in a
database without its data:
RDO> EXPORT
cont> 'DEPT3:PERSONNEL.RDB' INTO
cont> 'EXPORT$DISK:[EXPORT]PERSONNEL.RBR'
cont> WITH NODATA
This statement creates an interchange file for the
PERSONNEL database from the database file identified by
DEPT3:PERSONNEL.RDB. The WITH NODATA option specifies that the
interchange file, PERSONNEL.RBR, contains only the metadata that
defines the structure of PERSONNEL.RDB.