Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.
These questions are related to the ASAP database performance impact due to a full table scan of a few SQL Queries.
Q1: We are using ASAP Out Of the Box purging and stats gathering scripts, the purging script is purging 13 dynamic tables and we expect stats gathering script to collect stats on these 13 dynamic tables. The Stats gathering script does not appear to be aligned with the purging script. Why is this?
Q2: SSP_gather_asap_stats gathers statistics for objects in the database (tbl_wrk_ord). The information includes the distribution of data, the number of rows in the table and other important statistics.
Statistics gathering is governed by the following parameters in ASAP.cfg:
¦ GATHER_STATS = 1 # Enable Gathering statistics for tables and indexes
¦ GATHER_STATS_PROC = SSP_gather_asap_stats # Gather statistics procedure on SARM db.
¦ DB_PCT_ANALYZE = 20 # Pct of table to analyze when gathering stats
¦ DB_PCT_ANALYZE_IDX = 40 # Pct of index to analyze when gathering stats
¦ GATHER_DEGREE 1 # Degree of parallelism when gathering stats
The question is how to customize these parameter values i.e. what should be input point of considerations to increase/ decrease the values ?
Q3: What are the recommendations for gather stats?
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