Rational Insight ETL process for large Rational RequisitePro projects fails with premature EOF exception

Resolving The Problem

Customize the ETL process to deliver raw data directly to a temporary table and then to transform that data into the target table. This consists of the following four high-level steps:

1. Create a temporary table with the correct privileges.
2. Configure WebSphere Application Server.
3. Customize the ETL process.
4. Execute the ETL job.

Step 1: Create a temporary table with the correct privileges

Use the code snippet appropriate for your database. Substitute <USER_NAME> with the user name used for running the ETL jobs.

• To create the table in an IBM DB2 database:
  
  

  SET CURRENT SCHEMA RIODS;
    	CREATE TABLE TEMP_REVISION_HISTORY (
    		VERSION_ID CHAR(40) NOT NULL,
    		REQ_UNIQUEID CHAR(40) NOT NULL,
    		REVISION_NUMBER VARCHAR(50) DEFAULT '0' NOT NULL,
    		USER_ID CHAR(40) DEFAULT '-1' NOT NULL,
    		CHANGE_DATE DATE DEFAULT CURRENT DATE NOT NULL,
    		SOURCE_ID VARCHAR (36) DEFAULT '-1' NOT NULL
    	)IN VNF_32K INDEX IN VNF_IDX;	
    	GRANT SELECT, UPDATE, INSERT, DELETE on "RIODS"."TEMP_REVISION_HISTORY" to USER <USER_NAME> 



• To create the table in an Oracle database:
  

  ALTER SESSION SET CURRENT_SCHEMA= RIODS;
    	CREATE TABLE TEMP_REVISION_HISTORY (
    		VERSION_ID CHAR(40) NOT NULL,
    		REQ_UNIQUEID CHAR(40) NOT NULL,
    		REVISION_NUMBER VARCHAR(50) DEFAULT '0' NOT NULL,
    		USER_ID CHAR(40) DEFAULT '-1' NOT NULL,
    		CHANGE_DATE DATE DEFAULT CURRENT_DATE NOT NULL,
    		SOURCE_ID VARCHAR (36) DEFAULT '-1' NOT NULL
    	) TABLESPACE VNF_32K ;
    	GRANT SELECT, UPDATE, INSERT, DELETE on "RIODS"."TEMP_REVISION_HISTORY" to <USER_NAME> ;



• To create the table in an SQL Server database:
  

  USE $(DBNAME)
    	GO
    	CREATE SCHEMA AUTHORIZATION RIODS
    	GO
    	CREATE TABLE TEMP_REVISION_HISTORY (
    		VERSION_ID NCHAR(40) NOT NULL,
    		REQ_UNIQUEID NCHAR(40) NOT NULL,
    		REVISION_NUMBER NVARCHAR(50) DEFAULT '0' NOT NULL,
    		USER_ID NCHAR(40) DEFAULT '-1' NOT NULL,
    		CHANGE_DATE DATETIME DEFAULT GETDATE() NOT NULL,
    		SOURCE_ID NVARCHAR (36) DEFAULT '-1' NOT NULL
    	) ON VNF_32K 
    	GO
    	GRANT SELECT, UPDATE, INSERT, DELETE on RIODS.TEMP_REVISION_HISTORY to <USER_NAME>
    	GO

1. Open the WebSphere Application Server admin console.


2. Locate the view named WebSphere application server. By default, it is listed under Servers > Server Types.


3. Click the resource listed on the main page. By default, the resource name is RationalReportServer.


4. Click the Configuration tab. Then click Server Infrastructure > Java and Process Management > Process Definition.


5. Click Java Virtual Machine.


6. In the Generic JVM arguments field, put the following string: -DRJCB_IN_MTA_ONLY='RJCB' -Xquickstart

1. Restore the Rational Insight sample ETL catalog. For instructions, see Preparing the ETL catalog.


2. Configure all database connections. For instructions, see Creating the data warehouse connections.


3. Create a copy of the ReqProUseCase_ReqRevision_Lookup node.
   
   
   



4. Right-click ReqProUseCase_ReqRevision_Lookup, and click Properties.


5. Change the Name and Business Name to ReqProUseCase_ReqRevi_Lookup_STG, and click OK.


6. Select ReqProUseCase_ReqRevi_Lookup_STG and, on the panel at the right, right-click Transformation Model and click Mapping.
   
   



7. Delete the elements highlighted in red.

   

   Then click Auto Map > Create new elements as attribute, and click OK. To close the Add New Elements dialog, click OK.


8. Double-click the table delivery node to open the properties dialog.

   



9. Change the properties as follows:

   



10. Click the Module Properties tab, change the Refresh Type to REPLACE. Click OK.


11. Locate the copy that you created in step 3. Follow steps 4 and 5 to change the name of the node to ReqProUseCase_ReqRevision_Lookup.


12. Select ReqProUseCase_ReqRevision_Lookup and on the panel at the right, delete all except one of the data
    sources.



13. Right-click the remaining data source and click Properties.


14. Click the Query tab and make the following changes:

    



15. Click the Result columns tab, click Refresh, and then click OK.


16. Double-click the Data Stream node to open its properties dialog.

    



17. Map the stream items as shown below and then click OK.

    




18. Select the UseCase job.



19. Locate the reference to the original node ReqProUseCase_ReqRevision_Lookup, and delete the link after that node.

    
    



20. Right-click anywhere in the empty space and click Insert Fact Build Node.

    



21. Move mouse to the place where teh new node is to be placed and click. A Fact Build Node Properties dialog Opens. Specify the Associated Build property by clicking the browse button and selecting the node named ReqProUseCase_ReqRevision_Lookup that you created in step 11.

    

    Click OK to close the Item List dialog and the Fact Build Node Properties dialog.



22. Build up the link as shown below:



23. To save all changes, click the Save button on the tool bar.


24. Repeat steps 3 through 23 for all builds named ReqProXXX_ReqRevision_Lookup in the following folders: UseCases, Composite, BusinessModeling, GlobalRequirement, RUP and Traditional.


25. Save all changes.

Right-click the OOTBE2E node and click Execute.