PrerequisiteBefore proceeding, connect to the database, and perform an export operation.
Note the following:
- To import C and C++ XSP/UDF code files that reside on the Client, the code files (source, header, or object) must be available in the Import path. Object files must have been generated to be compatible with the compiler/linker of the Database Server.
- The client-side XSP/UDFs cannot be imported with ODBC connectivity.
- To import C and C++ XSP/UDF code files that reside on the Sever, files must be copied to the appropriate path, as specified in the CREATE/REPLACE PROCEDURE/FUNCTION DDL, on the Server. If a path is unspecified, the files must be copied to the default path. See Teradata Vantage™ - Database Administration, B035-1093 for default paths.
- To import Java XSP/UDF code files, the JAR file, supplied by the user during the export operation, must be registered using the external stored procedure SQLJ.INSTALL_JAR(). Registering the JAR file with the JARID and ClassName specified in the CREATE FUNCTION DDL can be done outside Teradata SET using a BTEQ session.
- Missing files are displayed before the Import operation.
-
Click
.
-
From the Open dialog box, select the .mcf file to use when importing information.
The preview pane (right pane) displays information about the file such as source system information. To close the preview pane, clear the Show Preview check box.A confirmation message displays the name of any missing file along with a statement that the corresponding option cannot be imported. Close the message box to open the Import window.
-
Click Open.
The Import window opens and displays the file name in the title bar.
- In the left pane, select objects to import, such as a table.
- [Optional] Perform any of the following procedures before completing the import:
-
Click .
-
Click Yes to start the import operation.
If a database being imported does not exist on the test system, it is created before the database objects are imported into the database. The main window displays the status of the import operation. The message Import completed appears after the operation is completed. If error messages appear while importing object definitions, see Retrying Failed Import Operations.
- [Optional] View a summary report of the import operation results.
- [Optional] Perform query plan analysis on the test system.