## IMPORT SCHEMA Command

You can user the Loader’s IMPORT SCHEMA command to import the data belonging to the specified schema’s application.

### Prerequisites

Only the owner of the schema may execute the IMPORT SCHEMA command.

You have exported the required data using the corresponding EXPORT command.

### Syntax

<import_schema_command> ::= IMPORT SCHEMA <schema_name>
[<duplicates_clause>]
[<map_schema_spec>]
[<configuration_spec>]
<catalog_data_instream_part_spec>
[<package_spec>] [<restart_spec>]

<catalog_data_instream_part_spec> ::= <catalog_instream_spec>
| <data_instream_part_spec>
| <catalog_instream_spec> <data_instream_part_spec>

IMPORT SCHEMA <schema_name> [<duplicates_clause>] [<map_schema_spec>] [<configuration_spec>] <catalog_instream_spec> <data_instream_part_spec> [<package_spec>] [<restart_spec>] | Imports the data belonging to the application of the specified schema (database catalog and application data)
IMPORT SCHEMA <schema_name> [<map_schema_spec>] <catalog_instream_spec> [<package_spec>] [<restart_spec>] | Imports the database catalog information belonging to the application of the specified schema
IMPORT SCHEMA <schema_name> [<duplicates_clause>] [<map_schema_spec>] [<configuration_spec>] <data_instream_part_spec> [<package_spec>] [<restart_spec>] | Imports the application data of the specified schema
<schema_name> | Schema name If the name of the schema is identical to a keyword or if the upper- and lowercase notation is relevant, the name must be placed in double quotation marks. <schema_name> ::= <identifier> See the SQL Reference Manual, Schema Name (schema_name)
<duplicates_clause> | REJECT DUPLICATES | IGNORE DUPLICATES | UPDATE DUPLICATES Default value: REJECT DUPLICATES
<map_schema_spec> | MAP SCHEMA [<schema_map_name> | <schema_to_schema>,...] <schema_map_name> ::= <identifier> <schema_to_schema> ::= <schema_name> TO <schema_name> See also: USE SCHEMAMAP Command
<configuration_spec> | CONFIGURATION <instream_csv_spec>
<catalog_instream_spec> | CATALOG <instream_ddl_spec>
<data_instream_part_spec> | DATA <instream_tableformat_spec>
<package_spec> | PACKAGE <outstream_csv_spec>
<instream_csv_spec> <instream_ddl_spec> <instream_tableformat_spec> <outstream_spec> | Data stream
<restart_spec> | RESTART <package_guid> <package_guid> ::= <unsigned_integer> unsigned_integer: ID that is created by Loader for every command at runtime This integer is always 24 bytes long. See the SQL Reference Manual, Unsigned Integer (unsigned_integer)

Examples

Loader Tutorial, IMPORT SCHEMA

### Explanation

#### <duplicates_clause>

You use the DUPLICATES rule to specify how to proceed when importing data from a data stream if a row with the same key as the new row already exists in the table. This rule is not evaluated if the data is imported into the database in the PAGES format.

REJECT DUPLICATES | The new line is rejected with an error message.
IGNORE DUPLICATES | The new line is not inserted.
UPDATE DUPLICATES | The new line overwrites the existing line.

#### <catalog_instream_spec>, <data_instream_part_spec>

Depending on whether database catalog and/or application data is imported, the following data streams are required for the import:

● Data stream with database catalog information: CATALOG <instream_ddl_spec>

● Data stream with application data: DATA <instream_tableformat_spec>

Only one of the two PAGES or RECORDS formats is possible for the data stream of the instream_tableformat_spec application data.

See also:

Data Stream

#### <configuration_spec>

You can exclude tables from the import.

● If you do not specify a data stream by means of CONFIGURATION <instream_csv_spec>, all the application data is imported.

● By specifying a data stream using CONFIGURATION <instream_spec>, you can exclude the application data of selected tables from the import of the instream_tableformat_spec application data. The tables must be identified in the data stream by specifying their schema and the table name.
The information about which tables are not imported is stored in the system tables. One way of displaying this information is to display the system table SYSLOADER.TRANSFORMATIONMODEL. The tables excluded from the import of the application data have the value TRUE in the EXCLUDE column.

The database catalog entries CATALOG <instream_ddl_spec> of all tables are always imported, regardless of the restrictions set using CONFIGURATION <instream_csv_spec>.

#### <map_schema_spec>

If data was exported in one schema, you can import it to another. To do this, you can use the USE SCHEMAMAP command to determine a schema map for a Loader session. However, you can also use the map_schema_spec syntax element in the IMPORT SCHEMA command, either to specify an existing schema map (schema_map_name) that contains the schema mapping you require or to directly determine the schema mapping by means of <schema_name> TO <schema_name>.

See also:

CREATE/DROP SCHEMAMAP Statement

#### <package_spec>

You can export system table SYSLOADER.TRANSFORMATIONMODEL.

● If you specify a data stream by means of PACKAGE <outstream_csv_spec>, all entries of the SYSLOADER.TRANSFORMATIONMODEL table are exported to this data stream. We recommend you use this option to log the import process well.

● If you do not specify a data stream by means of PACKAGE <outstream_csv_spec>, the system table SYSLOADER.TRANSFORMATIONMODEL is not exported.

See also:

Additional Log Functions (package_spec)

#### <restart_spec>

You can restart the import.

The user can determine the package_guid of the corresponding import commands from the SYSLOADER.TRANSFORMATIONMODEL table or the log file. You can restart the command with the corresponding package_guid by using the restart_spec syntax element.

See also:

Restarting

### Result

The application data and/or the database catalog are imported into the data_instream_part_spec and catalog_instream_spec data streams.

If necessary, all entries in the table SYSLOADER.TRANSFORMATIONMODEL are exported to the package_spec data stream.

#### Errors

The import cannot be completed successfully. In this case, the Loader logs the cause of the error in the log file.

The values PACKAGEGUID and CLIENTNODE are also written to the log file. The PACKAGEGUID is required if you want to restart the import.

See also:

Importing: Commands

EXPORT SCHEMA Command

Log File

System Tables