My Oracle Support Banner

T2T rejected records count is showing incorrect number when verified with TABLE_NAME$ table. (Doc ID 2695417.1)

Last updated on MARCH 04, 2022

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.7.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 8.0.7 version, Administration_OFSS

ACTUAL BEHAVIOR
---------------
As per current functionality, below query is fired to retrieve the rejected records count during T2T process. Same count is showing up in event log under Batch Monitor screen
select count(*) from ( select distinct * from TABLE_NAME$ where ORA_ERR_TAG$ = 'BATCH_RUNID');

EXPECTED BEHAVIOR
-----------------------

Duplicate records are also considered as erroneous data and hence to be counted in rejected records.Query to be framed as below:-
select count(*) from TABLE_NAME$ where ORA_ERR_TAG$ = 'BATCH_RUNID'

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Try to execute T2T and check the rejected records count in TABLE_NAME$ and in event log under Batch Monitor screen. Numbers will not be in sync.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot determine the exact rejected records count.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.