Export Table Sets - Intergraph Smart Materials - Version 2020 (10.0) - Administration & Configuration - Hexagon PPM

Intergraph Smart Materials Classic Administration (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
2020 (10.0)

Define an export table set on the A.60.02.05 Export Table Sets screen. An export table set is a collection of one or multiple physical table sets with assigned physical database tables. You must assign the pre-defined physical table sets to the export table set. Furthermore, you can specify the details (like schema, tablespace, and so forth) of the storage objects where the archived data will be stored in the database.

The scope of the export operation is limited to a project only, which means only data from the current logged-on project plus data from its underlying product group will be exported. However, tables that do not have the PROJ_ID column always get exported completely.

To define an export table set, enter the set name in the Export Table Set field and a description in the Remarks field in the first (Export Table Sets) block. The Project field shows the login project, which will be archived and exported.

The Schema Name field specifies the name of the database schema into which the specified data will be archived and exported. Per definition, a schema name may consist of the characters (a-z, A-Z, 0-9) and the underscore (_), starting with a letter.

The following reserved schema names must not be used to archive data: SYS, M_SYS, DISCO, DBSNMP, OUTLN, QS_CBADM, PM, ANONYMOUS, SYSTEM, WMSYS, QS_OS, OE, WKSYS, ORDSYS, QS_ES, RMAN, WKPROXY, SCOTT, ORDPLUGINS, QS_WS, QS_CS, ODM, SH, MDSYS, QS, QS_CB, ODM_MTR, HR, CTXSYS, QS_ADM, XDB, OLAPSYS, OC, BI, DIP, DMSYS, DSSYS, DUMP4, EXFSYS, FLOW_010500, FLOW_FILES, HTMLDB_PUBLIC_USER, IX, LBACSYS, MDDATA, MGMT_VIEW, OWB, PERFSTAT, SI_INFORMTN_SCHEMA, SYSMAN, TRACESVR, TSMSYS, WK_TEST, project schemas, and product group schemas. Also, the user cannot use a schema for archiving data if it contains table(s) whose names do not start with M_.

If a new (non-existing) schema was entered in the Schema Name field, you must also enter a schema password in the Password field (maximum 30 characters allowed).

The Tablespace and Index Tablespace fields refer to tablespaces for table data and index data, respectively. In both fields, select an existing tablespace name from the LOV, or enter a new (non-existing) tablespace name. A tablespace name may consist of the characters (a-z, A-Z, 0-9) and the underscore (_), starting with a letter.

The following reserved tablespace names must not be used to archive data: SYSAUX, UNDOTBS1, IPM_INDEX, USERS, SYSTEM, EXAMPLE, MARIAN, MTI_INDEX, M_INDEX, M_MIG, TEMP, and M_TEMP.

The TS Datafile and the Index TS Datafile fields refer to physical data files corresponding to the entered tablespaces. When you have selected existing tablespaces, these fields are filled automatically. For new tablespaces, you must define the datafiles with the extension .ora or .dbf and with the entire path.

The TS Size (Bytes) and the Index TS Size (Bytes) fields refer to the size of datafiles for the specified tablespaces. When you have selected existing tablespaces, these fields are filled automatically. For new tablespaces, you must define the tablespace sizes in bytes.

The Last Modified field shows the date and time when the export table set details have been inserted or modified last. The Export Date field shows the date and time when the data has been exported last for the specified export table set. The Last Created List field shows the date and time when the unique list of tables has been created last (by clicking the Table List button).

In the second (Export Table Set Details) block, you can assign pre-defined physical table sets or individual physical database tables.

To add a table set, select Table Set from the drop-down list in the Table/Table Set Indicator field. Then select a pre-defined table set from the LOV in the Physical Table Set field. To add an individual table, select Table from the drop-down list in the Table/Table Set Indicator field. Then select a database table from the LOV in the Table Name field.

You can double-click a physical table set in the Physical Table Set field to open A.60.02.04 displaying the selected set with the details. To go back, close the screen.

When you have finished table selection, click the Table List button to generate the table list and to open Window 2, which displays the table list with all the tables to be archived. To go back, close Window 2.

Finally, click the Export button to export and archive the data as specified.

If an existing schema was selected for the export, the procedure will drop all the existing tables of the schema and re-create them for archiving. If the schema does not exist, the procedure will create a new schema as specified.

Similarly, the procedure will create new tablespaces, if the specified tablespaces for table data or for index data do not exist.

The procedure also creates the needed unique keys, primary keys, and indexes for the exported tables. Foreign keys are not created.

Many data definition statements (for example, CREATE TABLE, DROP TABLE, and so forth), data manipulation statements (for example, INSERT, DELETE, and so forth), and transaction control statements (for example, COMMIT, ROLLBACK) are executed during the archiving and exporting process. Hence, in many cases, outcomes cannot be rolled back even if the archiving and exporting operation is not successful (although a failure message will appear).

The export procedure will create a log file in the folder specified by the DBA setting LOG_FILE_DEST. All the data definition, data manipulation, transaction control statements, and errors (if any) are written to the log file. When the export is finished, a message will appear notifying you whether the job was successful and where the log file can be found.

The export procedure also updates the ARCHIVED_AT column of the M_PROJECTS table to reflect the date and time of the last export of data from the project.