Model Upload Using Erwin

You can upload the warehouse data from the operational systems to database schema using ERwin xml file. An ERwin xml file is a standard tagged xml file based on the Object Property Model which can create the required data models. You can upload the xml file by hosting it on the server and customize the update process while uploading a Business Model.

To do model upload using the Erwin option:

1.      From the Business Model Upload window, select Upload Options as Erwin.

2.     Select the Upload Mode from the drop-down list. You can select only New if it is the first upload. For subsequent uploads, you can select Incremental, Rebuild, or Sliced upload mode. For more information, see the Upload Modes section. For Sliced model upload, you can use SQL Data Modeler. For more information, see OFSAA Datamodel Extensions through SQL Data Modeler section.

3.     Select the Object Registration Mode from the drop-down list as Full Object Registration or Incremental Object Registration. You can select Incremental Object Registration for the Upload Mode as Incremental and Sliced. It is recommended to select incremental only if the changes are minimal.

4.    Select the ERwin XML File for upload from the File Name drop-down list. The list displays the ERwin files that reside in the default server path (that is, ftpshare(Application layer/<infodom>/erwin/erwinXML). See Frequently Asked Questions for more details on functionality changes.

5.     In the Upload Options grid, select either Yes / No to directly Update the Database Schema with Model changes.

§       If you select Yes, the generated SQL scripts are executed at runtime to update the Model changes in the database.

§       If you select No, it restricts the system from updating the database automatically with Model changes and only the model scripts will be created. Later you should execute the SQL scripts in a correct sequence, in order to make the Infodom Schema to be consistent with the DATABASE.xml. For more information, see Sequence of Execution of Scripts section.

Also when you select No, ensure the following:

§       You have a third party tool or ETL tool to manage the schema updates.

§       Database consistency and schema updates are maintained manually by the database administrator.

6.    In the Upload Options grid, select Yes for the Generate DDL Execution Logs option if you want execution audit information such as execution start time, end time, and status of each SQL statements run as part of the model upload process. The execution log file will be available under ftpshare/<INFODOM>/Erwin/executionlogs folder.

7.     Select Yes for Refresh Session Parameters option to use Database session parameters during model upload process. For more information, see Configuring Session Parameters section.

8.    In the Upload Options grid, you have an option to select either Yes / No to directly update the Alter constraints in NOVALIDATE State. During incremental or sliced model upload, alterations to constraints consumes a lot of time as the constraints need to be validated.

§       If you select Yes, an option to alter the constraints in NOVALIDATE state is enabled and it will not check the existing data for the integrity constraint violation. It is quite useful in cases where it is known that the existing data is clean. So, NOVALIDATE can potentially reduce the additional overhead of the constraint validation and it would enhance the performance.

§       By default the option is selected as No. If you select No, then the option to alter the constraints is not enabled and it will check the existing data for the integrity constraint violation.

9.    Click Upload Model.