Background documentationIMPORT SCHEMA Locate this document in the navigation structure

 

You can import schema data exported from a database using the EXPORT SCHEMA command into a database. Use the IMPORT SCHEMA command to do so. Only the owner of the schema may execute the IMPORT SCHEMA command.

Prerequisites

You can use the demo databases DEMODB and TESTDB. You have exported the required data from demo database DEMODB. In demo database TESTDB, create the data administrator MONA if you have not already done so. Start the Loader and log onto database TESTDB as database administrator MONA with the password RED. Use the session mode: loadercli -d testdb -u mona,red..

As database administrator MONA create the HOTEL schema if this does not already exist.

Activities

The data from the HOTEL schema is to be imported into the TESTDB database. You can make entries after the keyword CATALOG and/or DATA to select what is to be imported, the database catalog and/or the data belonging to the application.

Caution Caution

If you import a table, the Loader also creates all the objects and links (views, foreign key dependencies with other tables…) that are defined for the table. If the necessary objects are not present and the import therefore cannot be executed, the Loader notifies you of this fact. Typical error messages include -25451 and -25392. If these errors occur, the import is terminated at this point.

End of the caution.
Importing the Database Catalog of a Schema

You can import the database catalog information belonging to the application of the schema.

IMPORT SCHEMA hotel

  CATALOG INSTREAM 'hotel_ddl.catalog'

The database catalog (CATALOG) is imported in the DDL (default value) format.

See also: Loader, Data Stream

Importing the Application Data of a Schema

You can import the application data of the schema.

IMPORT SCHEMA hotel

  DATA INSTREAM 'hotel_pages.data'

The application data (DATA) is imported in the PAGES format (default value).

IMPORT SCHEMA hotel

  DATA INSTREAM 'hotel_records.data' RECORDS

The application data (DATA) is imported in the RECORDS format. A PAGES import uses a database format (based on a page) and does not write Log entries, so it is faster than an import that uses the RECORDS format of the Loader. However, the tables imported in the PAGES format are write-protected until you back up the data.

See also: Loader, PAGES, RECORDS

Importing the Database Catalog and the Application Data of a Schema

You can import the data belonging to the application of a schema.

IMPORT SCHEMA hotel

  CATALOG INSTREAM 'hotel_ddl.catalog'

  DATA INSTREAM 'hotel_pages.data'

Note the sequence of the syntax elements. Always enter the syntax element for the import of the database catalog first, and then the syntax element for the import of the application data.

Excluding Tables from the Import

By specifying a data stream after the keyword CONFIGURATION, you can exclude the application data of selected tables that are specified in this data stream. The tables must be identified in the data stream by specifying the schema and table name.

Test the Loader behavior for different tables. When you exclude tables, you must be careful not to violate any dependencies, such as by excluding the tables CITY or HOTEL. You want to exclude the EMPLOYEE table from the import. Create the employee.configuration file with the following contents:

HOTEL,EMPLOYEE

Specify the following import command in the Loader session mode. Note the sequence of the syntax elements. First, enter the syntax element that excludes the table from the import.

IMPORT SCHEMA hotel

  CONFIGURATION INSTREAM 'employee.configuration'

  CATALOG INSTREAM 'hotel_ddl.catalog'

  DATA INSTREAM 'hotel_pages.data'

The database catalog entries of all tables are always imported, regardless of the restrictions made in employee.configuration.

Additional Log Functions

If you specify a data stream after the keyword PACKAGE, the command entries from the SYSLOADER.TRANSFORMATIONMODEL are exported to this data stream. This is an additional logging option. Always enter the PACKAGE syntax element as the last syntax element.

IMPORT SCHEMA hotel

  CATALOG INSTREAM 'hotel_ddl.catalog'

  PACKAGE OUTSTREAM 'hotel_csv.package'

See also: Loader, Additional Log Functions (package_spec)

Complete Syntax of the IMPORT SCHEMA Command

Combining the syntax options can result in correspondingly complex commands. Note the sequence of the syntax elements.

IMPORT SCHEMA hotel

  CONFIGURATION INSTREAM FILE 'employee.configuration' CSV ASCII

  CATALOG INSTREAM FILE 'hotel_ddl.catalog' DDL

  DATA INSTREAM FILE 'hotel_pages.data' PAGES

  PACKAGE OUTSTREAM FILE 'hotel_csv.package' CSV

For a complete syntax description, see IMPORT SCHEMA command in the Loader documentation.

More Information

Other commands for Importing

Session Mode