| # Create Sequential Dump of Table (ttaad4226m000) Use this session to export data from LN database tables to one or more sequential files. This session reads tables for the selected company numbers, converts them into sequential data and writes out the results into specified files on the Operating System. Session usage To extract data for bdbpre6.2 without workflow support: Select the range of company number(s) and tables from which you want to extract data. Use the remaining fields and check boxes to specify the settings for the extraction process. For details, see the online field help. Click Create. To extract data for bdbpre6.2 with workflow support: Select the range of company number(s). Select either the range of tables or the range of object types. Use the remaining fields and check boxes to specify the settings for the extraction process. For details, see the online field help. Click Create. Sequential file types During the extraction, the data is converted to one of the following: sequential files with a field separator. A separate sequential file is generated for each table in the selection range. Use this option if you want to copy data to another company number. You can also easily load the content of the sequential files into any database using SQL, or into applications such as MS Excel. To use this option, select the Specify Field Separators check box and specify the separator in the Specify Field Separators field. sequential files with a fixed record length. A separate sequential file is generated for each table in the selection range. This option is useful for downloading data to databases such as dBASE, which require fixed length records without separators. To use this option, select the Create Fixed Length Records check box. one or more sequential dump files, containing the records and the data dictionary information of all tables in the selection range. A separate dump file is generated for each selected company. To use this option, enter the basic name of the dump file in the Basic Name for Dump File(s) field. The session automatically adds a company number extension to the basic file name. Copy data to another company If you want to copy the extracted data to another company, you must always use sequential files with a field separator: the extracted data in the sequential files contains references to the source company number. Before loading the data into the target company, you must run the Copy Company Data (tccom0214m000) session to correct these references, so that they refer to the target company. This session can only handle files with a field separator. To load the content of the sequential files into another company, use the Create Table from Sequential Dump (ttaad4227m000) session. Refer to To copy a multicompany structure - Procedure details for more information. Technical information Internally the session uses the bdbpre6.2 executable. For more information on this executable, refer to the Infor Enterprise Server Technical Manual (U8172 US). Options Suppress Error Messages 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. Drop Table after Dump If this check box is selected, the physical tables are deleted after the dump is created. Exclude Logical Tables From Dump 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. 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. Note This field is only displayed if bdbpre6.2 supports workflow. Format Export All Data Languages 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. ISO 639 Language 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. Create Fixed Length Records 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 if you want to copy the extracted data to another company number. Refer to Copy data to another company for details. Specify Field Separators 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. Specify Field Separators 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. Default value \0 Directory for Table Files The directory where the files with a fixed record length, or the files with a field separator, will be created. Files Basic Name for Dump File(s) 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. Max. File Size 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 Max. File Size 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. Name of the Error File Specifies the name, including the path, of the file to which all error messages and statistics information is written. |