Create Sequential Dump of Table (ttaad4226m000)

If this check box is selected, no messages or information will be displayed. Error messages can be found in the log.bdbpre6.2 log file.

If this check box is selected, the physical tables are deleted after the dump is created.

If this check box is selected, logical tables are skipped during the export. LN exports only tables that are physically stored in the selected companies. Shared tables are exported only once, when you export a logical company together with its physical company. For each logical table that is skipped, LN writes a message to the "dump.err" output file.

If this check box is cleared, both, physical and logical tables, are exported. Shared tables are exported twice, when you export a logical company together with its physical company.

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

Do not combine with the options Create Fixed Length Records or Specify Field Separators. These options create individual export files for each specified table. The check box is automatically cleared in case of such a combination.

If this check box is selected, referential integrity constraints are ignored. Tables are created and the import of data, despite of the nonexisting corresponding reference tables, will succeed. When all tables are created from the sequential files, run the Create Sequential Dump of Table (ttaad4226m000) session. Select the Repair Reference Counter check box in case the option Include Reference Counters is selected. Otherwise no reference counter repair is required.

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 exported.

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

Select one of these values:

• Records modified before: all records that were modified before the specified timestamp are exported.
• Records modified after: all records that were modified after the specified timestamp are exported.

The timestamp value.

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

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

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.

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.

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.

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.

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.

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.

If this check box is selected, data will be exported for all data languages.

If this check box is cleared, you must specify one or more languages in the ISO 639 Language field.

The data language(s) for which you want to export data.

The languages must be separated by commas, for example: nl,en_US,de

You can zoom to the Data Languages (ttaad1111m000) session, and select multiple languages in one go.

If this check box is selected, an ASCII dump with a fixed record length and without any separators is created. A file with a .F extension is created for each of the specified tables. For example: the sequential file ttccom001550.F contains the data that is extracted from the tccom001 (Employees - General) table in company 550.

This option is useful for downloading data to databases such as dBASE, which require fixed length records without separators.

You must specify the directory where the sequential files will be generated in the Directory for Table Files field.

Important: do not use this option to copy the extracted data to another company number. See Copy data to another company for details.

If this check box is selected, you can specify a field separator for the sequential files. A file with a .S extension is created for each of the specified tables. For example: the sequential file ttccom001550.S contains the data that is extracted from the tccom001 (Employees - General) table in company 550.

You can easily load the content of the sequential files into LN tables, into any database using SQL, or into applications such as MS Excel.

You must specify the directory where the sequential files will be generated in the Directory for Table Files field.

Important: you must use this option if you want to copy the extracted data to another company number.

The field separator to be used in the sequential (.S extension) file. For example: a pipe (|), or a caret followed by a single uppercase alphabetical character: ^A, ^B, and so on.

The directory where the files with a fixed record length, or the files with a field separator, are created. You must specify the ${BSE}/appdata folder when working in the Cloud.

The basic name, including the path, of the sequential dump files. You can only generate sequential dump files if the Create Fixed Length Records and Specify Field Separators check boxes are cleared.

The sequential dump files contain the records and the data dictionary information of all tables in the selection range. A separate dump file is generated for each selected company. The session automatically adds a company number extension to the basic file name.

Example

You run this session with the following settings:

• Company: 400-402
• Package: <empty> - zz
• Table: <empty> - zzz999
• Basic Name for Dump File(s): /tmp/dump

3 dump files are generated: /tmp/dump.400, /tmp/dump.401 and /tmp/dump.402. Each dump file contains the records and the data dictionary information of all tables of the corresponding company.

Important: do not use this option if you want to copy the extracted data to another company number. Refer to Copy data to another company for details.

Use this field to specify the maximum size for output files with a fixed record length, or for output files with a field separator. If the maximum file size is reached, LN opens and fills a new file with a sequence number.

To specify the size, enter a number in this field and a unit of storage, such as bytes, Kbytes, Mbytes, or Gbites, in the following field. The maximum size is 2 GB.

You can only specify a maximum file size if one of the following check boxes is selected:

• Create Fixed Length Records
• Specify Field Separators

Use this field to specify the unit of storage for the maximum size for output files with a fixed record length, or for output files with a field separator.

You can select bytes, Kbytes, Mbytes, or Gbites.

Specifies the name, including the path, of the file to which all error messages and statistics information is written. By default $BSE/tmp is used, but you must specify the ${BSE}/appdata folder when working in the Cloud.