T2T Load Logging Incorrect Number Of Loaded Records in the Log File and ETLLOADHISTORY
Last updated on NOVEMBER 17, 2011
Applies to:Oracle Financial Services Analytical Applications Infrastructure - Version: 7.2.9
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA) - Version 5.x
Source table stg_loan_contracts_1 had 186 records and 1 record rejected during load to stg_loan_contracts table and after T2T stg_loan_contract only had 185. No of records loaded is correctly showing as 185 but rejected is showing as 0 instead of 1.
Log file however does not reflect the 1 rejected row due to duplicate:
2011-09-09 | 07:11:29 | t2tserver | DEBUG | | | No. of rows loaded :185
2011-09-09 | 07:11:29 | t2tserver | DEBUG | | | No. of rows rejected :0
2011-09-09 | 07:11:29 | t2tserver | SEVERE | | | ClsUDBConnect::checkTableExists, returning from checkTableExists = 0
2011-09-09 | 07:11:29 | t2tserver | INFO | | | ClsUTableToTableLoad::directLoad, UPDATING BATCHID SUCCESSFUL.
2011-09-09 | 07:11:29 | t2tserver | INFO | | | ClsUTableToTableLoad::ExtractLoad, Success, direct table to table load successful
2011-09-09 | 07:11:29 | t2tserver | INFO | | | Status from extract load ... 0
2011-09-09 | 07:11:29 | t2tserver | DEBUG | | | T2TLoad::main, INFO, Status Returned from Table To Table Loading: 0
Expect the No. of rows rejected to also include any duplicate rows rejected.
The issue can be reproduced at will with the following steps:
1. Run T2T with bulk load with disable PK and delete duplicate option.
2. Have at least 1 duplicate row that will be rejected in the source data.
3. Check the resulting log file.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms