Consequences in purging the table by the procedure such as "create as select + drop table rename table"
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
What is the risk if we purge a BRM table by the procedure given below:
1) Create a new table for each existing table considering only records not to be removed (e.g. select * from invoice_t where poid_id0 > XXXXXXX )
2) Drop Original tables (*).
3) Rename new tables with the name of original tables.
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