Error: error code=300 component=REP message=literal does not match format string – running Account Profile Report

When running an Account Profile Report, an error pops up:

error code="300" component="REP" message="literal does not match format string
select 'ad' , ad . account_id ad_account_id , at
OK : Request submitted - Length of stream : 436
*** XML-Parsed - Following Structure discovered :
*** Checking elements!
serverQueues ()
*** Checking attributes!
error
*** Checking attributes!
__code = 300
__component = REP
Error in run_report: -06502: PL/SQL: numeric or value error: character string buffer too small
*
* Debugging turned OFF **************************
*
Encountered unexpected error running the report: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
Completed report: AMACCPRF - HFHI Account Profile Report <MDUNSTON> on 02/18/2016 at 16:50:44
Waiting for a request...


 
The error may indicate that the data in a field is not formatted properly.  Possibly a date that is not following the mm/dd/yyyy format.  Looking in the log you may see something that looks like this:

   <error code="300" component="REP" message="literal does not match format string
select 'ad' , ad . account_id ad_account_id , at
      OK : Request submitted - Length of stream : 436


In the example above is indicating that during whatever the process was doing when it had an error, it was at something that was aliasing a table as 'ad'.   AD is normally used for the Addresses table, so at that point, you would check the Addresses table to search for a field that is not formatted properly.  It may take some trial and error to figure out where the issue is.

In the above example, the fields with bad formatting were From_Date and Through_Date. The date was listed like 0516, which is both formatted wrong (should be mm/dd.yyyy) and is missing either the date or a year.  The bad dates need to be corrected or moved.

Environment

 RSR
 TA

Was this article helpful?