Select the Object Definitions check box to export the data model and the DDL text of selected objects or the objects referenced by a given query. Use this option to export the details of the structure and instances of the objects used by a given query.
Exported object definitions are used to create the tables, views, macros, triggers, indexes, stored procedures, User Defined Functions (UDFs), and UDTs on a test system. Object definitions are selected for export based on the type of export operation.
When exporting by query, selecting the Object Definitions check box exports the UDFs and UDTs returned by the SHOW QUALIFIED statement on the query.
When exporting by database, selecting the Object Definitions check box exports the UDTs referenced by objects added for export and the UDTs added manually for export.
When exporting by workload, selecting the Object Definitions check box exports the UDFs and UDTs returned by the SHOW QUALIFIED statement on the queries.
Note: While exporting UDFs, TSET retrieves only the CREATE/REPLACE FUNCTION DDL, as TSET cannot retrieve UDF code files (source, header, or object). The user must supply the UDF code files. TSET displays the File Open Dialog screen for browsing the UDF code files during export. The screen title includes the UDF filename for C and C++ UDFs. For JAVA UDFs, the JAR_ID and Java ClassName are included in the screen title. The supplied UDF code filenames are copied to the Export path.
If C and C++ UDF code files are not copied to the export path, the pack operation fails.
If Java UDF code files are not copied to the export path, the pack operation does not fail, but the Java UDF code files must be moved manually from the production system to the test system.
Missing code files are displayed at the end of the export operation, and before an import operation.