TDM Subset: Expand all tables (Oracle) to use with Javelin

Document ID : KB000010752
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

This document will describe how to expand all the parent / child tables to be used with Javelin automation.

Environment:
OS: WindowsDB: OracleTDM Subset
Instructions:

Step 1:

In GTSubset, click on <configuration> ,  <Get Tables and FKs from repository>

img_1.png

Step 2:

Make sure ALL the tables of interest are registered in Datamaker.

 

Step 3:

Restart GTSubset. If starting standalone, there will be a prompt for the project and version where the tables are registered.

Start with extra memory as below:

Start GTSubset from a command line with the extra memory parameters   (* this action will take longer due to loading additional meta data into memory *)

C:  java -Xms1000M -Xmx 2000M -jar GTSubset.exe

 

Step 4:

Once GTSubset has restarted, select <configuration>, <Restrict rules branch>

img_2.png

Check the box for Restrict Rules branch to one occurrence per rule.

img_3.png

Build the Subset design as before by selecting a driving table, adding SQL to the driving table, then expanding all one level, repeat as required.

 

Step 5:

Save the Subset extract.

 

Step 6:

From the Javelin menu, click <Javelin>, <Save Javelin Subset Levels.

img_4.png

Select the saved extract and any data tables required, then select the staging database connection from the drop down.

img_5.png

If any tables do not have a Primary Key, or Unique index, the following error message appears:

img_6.png

The SQL generated for tables without a PK or UK will be as follows:

INSERT INTO travel_e.HOTEL_FACILITIES(HOT_ID,FACILITY_TYPE,FACILITY_TYPE_NAME,FACILITY_TEXT,gtrowid)

SELECT HOT_ID,FACILITY_TYPE,FACILITY_TYPE_NAME,FACILITY_TEXT,rowid FROM travel.HOTEL_FACILITIES

WHERE EXISTS (SELECT 1 FROM TRAVEL.HOTEL_FACILITIES L19 JOIN travel_e.HOTELS ON  L19.HOT_ID = travel_e.HOTELS.ID

AND  NOT EXISTS (SELECT 1 FROM  travel_e.HOTEL_FACILITIES T WHERE T.gtrowid = L19.rowid))

 

This will require an extra column in these type of tables in the staging schema (alter table tablename add column gtrowid rowid)

 

Javelin Steps

Step 1:

Click the import XML/CSV button.

img_7.png

Step 2:

Set the type to Subset Crawler XML, and then browse to the subset levels xml file you saved.

img_8.png

Step 3:

Once imported, click the run button to insert data into stage.

img_9.png

Additional Information:

If you experience any further issues, please open a support case by going to https://support.ca.com/us.html