| # Copy parameters and master data For the archive company to function, some mandatory basic data such as master data and parameter data, must be present in the archive company. General data represents static data, required to ensure the references of the archived data. Usually, general data will be copied with the relevant archiving session. The process of copying general data is usually performed each time an archiving session is started and, depending on the amount of general data to be copied, can take a long time. The following sections provide various hints to reduce the time it takes to archive this general data. Most archiving sessions have an Archive General Data check box, which allows you to specify if general data must be archived. For example, when you have put multiple archiving sessions in a single job, it is sufficient to archive general data only once for a specific functional domain, such as Warehousing. You then only select the check box for the first session of a functional domain and leave the check box cleared for subsequent sessions within the job. This will prevent a repeated archiving of the same master data and reduce the time it takes to archive general data. Alternatively, you can make use of more direct database utilities to archive general data. When you do so, you create flat files from the general data of your operational company and import these flat files in the archive company. Two methods are available for doing this: Method 1: Copy general data using regular sessions Export data from the operational company using the Create Sequential Dump of Table (ttaad4226m000) session, and then import this data in the archive company using the Create Table from Sequential Dump (ttaad4227m000) session. One disadvantage of this method is you must repeat this process many times because the involved tables are not within a continuous range. Method 2: Copy general data using bdbpre and bdbpost tools If you are familiar with the use of bdbpre and bdbpost commands, this saves time. Note The following tables must not be copied from the operational company to the archive company: Financial Companies by Group Company (tfgld001) Group Company Parameters (tfgld003) Financial Companies (tfgld004) For more information, refer to the Company Parameters (tfgld0503m000) session and the Group Company Parameters (tfgld0501m000) session in this chapter. Method 1: Copy general data using regular sessions Path: // Tools / Database Management / Database Utilities Instruction (in operational or 000 company) Step 1. Export data from the operational company to a dump file using the Create Sequential Dump of Table (ttaad4226m000) session: Specify the (operational) company and enter one table or a range of the tables for which you want to create a dump file. On the second tab of the session, specify the file name for the dump, and a file name for an error log. These two files will be written to your home directory or the directory entered in the Directory for Table Files field. An extension will be automatically added to the file name of the dump; a dot followed by the company number. Step 2. Import the data which you exported in the previous step into the archive company: Path: // Tools / Database Management / Database Utilities Instruction (in operational or 000 company) The Create Table from Sequential Dump (ttaad4227m000) session allows you to load the previously created dump into the archive company, as shown below. Step 1. Select the Create Tables for Different Company check box and enter the company number of the new archive company. You must select the Ignore Referential Integrity Constraints check box; if not the result could be a 606 error when you create the table from the sequential dump. Therefore, the system may return the bdpost6.2 error message. Step 2. Repeat this action for all dumps for the mandatory tables you created in the previous section. You must also specify a file name for the error log file that will be created when reading in the dump. You must select the Ignore Referential Integrity Constraints check box; if not, the result could be a 606 error when you create the table from the sequential dump. Therefore, the system may return the bdpost6.2 error message. In case of error “Error in running bdbpost6.2”, the errors file in the home directory shows the exact error message, which could look like the following: Default separator ('\0') taken Table M Idx RowCount Messages ----------- - --- -------- ---------------------- tcmcs010999 R 1 1 write error 606 Step 3. Run the Reorganize Tables (ttaad4225m000) session with the Reference Integrity and Repair Reference Counter check boxes selected, as shown below. The company number must be the company number of the archive company. Method 2: Copy general data using bdbpre and bdbpost tools To copy the parameters mentioned previously and the general data from your operational company into the archive company, you can compose an ASCII file such as copy.erpln.data, in which all required tables (enumerated in chapters 5 and 6) are listed. With this file and the bdbpre command, you can dump the tables in a dump file. With the bdbpost command, you can create tables from the dump file as shown: Instruction (UNIX or Windows system level) Step 1. List the names of the tables specified in appendices A and B in one or more ASCII files, such as copy.erpln.data. Step 2. Using the syntax described below, export the data from the operational company (bdbpre) and then import the data into the archive company (bdbpost). UNIX At the command prompt, enter the following: export BSE= path export BSE_TMP=$BSE/tmp set USER= user name of operational company bdbpre6.2 –Icopy.erpln.data –Oerplndata001.dmp –C001 bdbpost6.2 –R –f –n –c901 –Ierplndata001.dmp This will copy the data of the provided tables from company 001 to company 901. Windows On the server, at the command prompt, enter the following: In the $BSE\bin directory: fillenv set user= user name of operational company bdbpre –Icopy.erpln.data –Oerplndata001.dmp –C001 bdbpost –R –f –n –c901 –Ierplndata001.dmp This will copy the data of the provided tables from company 001 to company 901
copy.erpln.data | The ASCII file that contains the list of table names to be exported. Part of the contents might look like this: tcccp000 tccom999 tcibd000 tcmcs000
001 | The company number of the operational company.
erplndata001.dmp | The name of the dump file.
901 | The company number of the archive company.
Step 3. After you post the dump to the archive company, reorganize the tables using the Reorganize Tables (ttaad4225m000) session. In this session, select the following check boxes: Reference Integrity Repair Reference Counter This is required because the bdbpost option –n (Ignore referential integrity constraints) is used. Options for the bdbpre and bdbpost commands are in the Infor Enterprise Server 8 - Technical Manual. |