Table Classification Fails with Error 'ACCOUNT_NUMBER did not meet the column requirements'
Last updated on NOVEMBER 08, 2016
Applies to:Oracle Financial Services Asset Liability Management - Version 8.0.0 and later
Oracle Financial Services Profitability Management - Version 8.0.0 and later
Oracle Financial Services Funds Transfer Pricing - Version 8.0.0 and later
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
After installing the Oracle Financial Services Profitability Management (PFT) or Asset Liability Management (ALM) 8.0 pack, the table classification program Batch_Table_Class_Req fails and you get errors like the one below in FSI_MESSAGE_LOG:
Table FSI_PM_GENERATED_INSTRMTS ( 200)
"HINT1: Last query executed was select 0 from
user_tab_columns a,rev_tab_columns b,
where a.column_name = b.column_name
and a.table_name = b.table_name
and b.column_name = c.column_name
and c.column_name = 'ACCOUNT_NUMBER' and b.table_name = 'FSI_PM_GENERATED_INSTRMTS' and c.rev_data_type_cd = b.rev_data_type_cd and ( a.data_length = c.data_length or c.data_length = a.char_length)
and a.data_type = c.data_type"
HINT2: NO_DATA_FOUND exception encountered while validating table FSI_PM_GENERATED_INSTRMTS
HINT3: FSI_PM_GENERATED_INSTRMTS.ACCOUNT_NUMBER: rev_column_requirements.rev_data_type_cd is 21 rev_tab_columns.rev_data_type_cd is 21
HINT3: FSI_PM_GENERATED_INSTRMTS.ACCOUNT_NUMBER: rev_column_requirements.data_length is 50 user_tab_columns.data_length is 120 user_tab_columns.char_length is 30
HINT3: FSI_PM_GENERATED_INSTRMTS.ACCOUNT_NUMBER: rev_column_requirements.data_type is VARCHAR2 user_tab_columns.data_type is VARCHAR2
Table FSI_PM_GENERATED_INSTRMTS.ACCOUNT_NUMBER did not meet the column requirements. Check Column data type
HINT: check_table_class_req procedure returned status N while validating table FSI_PM_GENERATED_INSTRMTS for classification code 200
Table FSI_PM_GENERATED_INSTRMTS Failed (200)
The same error occurs for multiple tables and table classification numbers.
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