Last updated on JUNE 16, 2017
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206 and later
Information in this document applies to any platform.
On : ORMB 220.127.116.11 version, DB - Database
RMB Database CLOB Column Storage Question
On Tables like F1_OUTMSG, there are 4 CLOB columns XML_SOURCE, ERROR_DTL, XML_RAW_RESPONSE, and XML_RESPONSE.
We are planning to convert table clob storage clause from BASICFILES to SECUREFILES to improve read/write performance and also save storage.
Please let us know if ORMB product has any limitations or issues to this approach?
Qn1:Any thing in the metadata within application that we need to change or would you see this as just a simple alter DDL at table level with index rebuilds?
Qn2:Do we need to update any metadata with in application configuration like in ConfigLab to reflect the way CLOB is stored?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms