Convert / Recover Tables (ttaad4228m000)

Field Information

Name of the Error File

Specifies the name of the file that stores the error messages and statistics information. You must specify the ${BSE}/appdata folder when working in the Cloud.

Dump options

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.

Include Reference Counters

If this check box is selected, all reference counters are preserved in the export dump.

The import process will automatically adopt this setting. The Ignore Referential Integrity Constraints check box will be disabled.

Timestamp options

Based on Timestamp

If this check box is selected, you can specify a timestamp. For tables that have a timestamp column, only records that are modified after or before the specified timestamp are converted or recovered.

To define timestamp columns for tables, use the Table Timestamp and Soft Delete Definitions (ttadv4136m000) session.

Based on Timestamp

Select one of these values:

• Records modified before : all records that were modified before the specified timestamp are converted or recovered.
• Records modified after : all records that were modified after the specified timestamp are converted or recovered.

Based on Timestamp

The timestamp value.

Include tables without timestamp

If this check box is cleared, only records from tables that have a timestamp column are converted or recovered.

If this check box is selected, all records of tables that do not have a timestamp column are also converted or recovered.

Workflow options

Include object type (DBCM) info

If this check box is selected, bdbpre6.2 includes workflow information of the exported tables in the exported files.

If this check box is selected, bdbpre6.2 can perform these additional checks during the export of a table:

• If the Allow incomplete object types (not recommended) check box is cleared, bdbpre6.2 checks whether the table is member of an object type. If so, bdbpre6.2 checks whether the other tables belonging to that same object type are also exported. If not all tables of the object type are within the given table range, bdbpre6.2 skips the table.
• If the Allow incomplete table sharing sets (not recommended) check box is cleared, bdbpre6.2 checks whether the table is member of a table sharing set. If so, bdbpre6.2 checks whether the other tables belonging to that set are also exported. If not all tables of the table sharing set are within the given table range or object type range, bdbpre6.2 also skips the table.

By default, this check box must be selected.

Note: This check box is only displayed if bdbpre6.2 supports workflow.

Also checked out data

If this check box is selected, bdbpre6.2 also exports the checked-out data of tables. If this check box is cleared, only the checked-in data is exported.

By default, this check box must be selected.

Note: This check box is only displayed if bdbpre6.2 supports workflow.

Allow incomplete object types (not recommended)

If this check box is selected, you can export a subset of the tables of an object type. If the table range you specified contains a subset of the tables of an object type, only the tables in the range are exported. Any other tables of that object type, which fall outside the range, are skipped.

If this check box is cleared, tables that belong to an object type are only exported if all tables of that object type are included in the table range. If the table range contains a subset of the tables of an object type, all tables of that object type are skipped.

By default, this check box is not selected.

Note: 

We recommend that you clear this check box. Only select this check box if you are completely aware of all the consequences!

This check box is only displayed if bdbpre6.2 supports workflow.

Allow incomplete table sharing sets (not recommended)

If this check box is selected, you can export a subset of the tables of a table sharing set. If the table range or object type range you specified contains a subset of the tables of a table sharing set, only the tables in the range are exported. Any other tables of that table sharing set, which fall outside the range, are skipped.

If this check box is cleared, tables that belong to a table sharing set are only exported if all tables of that table sharing set are included in the table range or object type range. If the table range or object type range contains a subset of the tables of a table sharing set, all tables of that table sharing set are skipped.

By default, this check box is not selected.

Note: 

We recommend that you clear this check box. Only select this check box if you are completely aware of all the consequences!

This check box is only displayed if bdbpre6.2 supports workflow.

Also log trace info

If this check box is selected, information about the workflow verification process of bdbpre6.2 is logged in a file. You can specify the full path name of this file in the next field.

By default, the check box is selected.

Note: This check box is only displayed if bdbpre6.2 supports workflow.

Also log trace info

The full path name of the file in which the trace information is logged. You must specify the ${BSE}/appdata folder when working in the Cloud.

Note: This field is only displayed if bdbpre6.2 supports workflow.

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. You must specify the ${BSE}/appdata folder when working in the Cloud.

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.

Suppress Information Logs (bdbpost)

If this check box is selected, information-related entries are not logged in the log.bdbpost6.2-<seqn>.log file. The report output remains unchanged.