Consequences in purging the table by the procedure such as "create as select + drop table rename table"
(Doc ID 1909455.1)
Last updated on APRIL 20, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.1.0 and laterInformation in this document applies to any platform.
Goal
What is the risk to purge 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 > <POD ID> )
2) Drop Original tables (*).
3) Rename new tables with the name of original tables.
Solution
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
Goal |
Solution |