How To Manage Big Event_t Table
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 10-Sep-2012***
***Checked for relevance on 22-Jul-2014***
***Checked for relevance on 12-Sep-2016***
Table event_t is very large - 82 GB. The SQL query against it takes longer time because of it's size. What is the recommendation to deal with it?
The table is not partitioned. Here are the specific questions :-
1. Is partitioning recommended? If so, provide a sample script or the key (field name) to partition?
2. Any other method to deal with this table?
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