| Convert / Recover Tables (ttaad4228m000) |  |
| use.session.to convert tables to another database type, or to recover tables. This session is a combination of the Create Sequential Dump of Table (ttaad4226m000) and Create Table from Sequential Dump (ttaad4227m000) sessions. By converting the tables to another database type you can transfer data from one database to another. By recovering tables you can rebuilt tables by converting data of tables to the same table. For additional refer to the Reorganize Tables (ttaad4225m000) session. Note If the tables are converted or recovered with the Ignore Referential Integrity Constraints check box selected, you run the Reorganize Tables (ttaad4225m000) session afterwards, with the Repair Reference Counter check box selected.
Fields | Description
Company | Specifies the company in which you want to convert or recover the specified tables.
Company | Specifies the company in which you want to convert or recover the specified tables.
Package | Specifies the package in which you want to convert or recover the specified tables.
Package | Specifies the package in which you want to convert or recover the specified tables.
Table | Specifies the table which you want to convert or recover.
Table | Specifies the table which you want to convert or recover.
Name of the Error File | Specifies the name of the file that stores the error messages and statistics information.
Suppress Error Messages | If this check box is selected, no messages or information will be displayed. Any error messages are stored in the log file, log.bdbpre6.2.
Drop Table after Dump | If this check box is selected, the physical tables are deleted after the dump is created.
Convert Tables | If this check box is selected, the tables are converted from one database organization to another.
Target Database | Specifies the database organization to which the tables are to be converted. Enter the full database name like in tabledef. Specifications are optional. Example Oracle(ORACLE_HOME=/usr/oracle)
Create Tables for Different Company | If this check box is selected, the tables are recreated for a different company than the one for which they already exist in the sequential dump file.
Create Tables for Different Company | Specifies the company number for which the tables will be created. The name of the dump file contains an extension which specifies the company of the tables in the dump. Example Dump.001 means that this dump contains tables of company 001.
Create Tables for Different Company | Specifies the package combination which belongs to the company for which you want to convert or recover tables.
Append if Table Exists | If this check box is selected, the data from the sequential dump file is appended to the table.
Overwrite Duplicate Records from Dump | If this check box is selected, the record of the sequential dump overwrites the existing duplicate record in the table.
Delete Existing Tables | If this check box is selected, the tables which are already present are deleted before the new tables are created. Note This option cannot be used if the Append if Table Exists check box is selected.
Create Rows before Index | If this check box is selected, the index will be build after all records of a table are created. This option speeds up the process.
File to Store Table Names not Created | you can specify the file in which unsuccessfully created tables are stored.
File to Store Table Names not Created | Specifies the name of the database driver as specified in the ${BSE}/lib/ipc_info file, or the driver with full path name, or the host name where the driver is located. Example Oracle(ORACLE_HOME=/usr/oracle)
Disable Domain Constraints | If this check box is selected, the domain constraints are disabled. There is no check to make sure that the data of a table field meets the requirements of the domain in the table definition. Example It is possible that a string of 30 characters is placed in a field with a string domain of only 15 characters. In that case you loose information.
Ignore Referential Integrity Constraints | If this check box is selected, the referential integrity constraints are ignored. It is possible that the tables created from the dump have a reference to tables that will be created later from the same dump. Because these tables do not exist yet, this can create a problem. In that case you can ignore the referential integrity constraints by selecting this check box. If all tables from the dump are created, you must run the Reorganize Tables (ttaad4225m000) session. You can also overwrite data of existing tables, or create tables from the dump which have a reference with existing tables in the environment where the tables are created. In that case, this check box must be cleared, because the reference tables are there.