Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 324
  • Last Modified:

how to improve stats gathered on database objects

I understand that Oracle 10g by default runs a job that updates the statistics on all database objects. However, I looked at the reports generated from this job and noticed that statistics on most of objects are timing out. Therefore, the statistics remains stale. I am trying to get total records counts for all non system schema account tables. I have run a script that queries dba_tables. However, because the statistics is stale or hasn't been successfully run on most of the tables I am not getting an accurate count. The database is A RAC environment with 2 nodes and  is 6 terabytes in size. There are tables that have partitions using range. The system is production and is heavily used. Even during non business hours there are ingestion scripts being run. I am trying to figure out a way to get an accurate count at a point in time and not jeopardize the availability of the database. The database is version 10.2.0.4 however, due to other issues it is not safe to apply anymore patches. However, we are currently migrating to a 11g virtual environment and getting these row counts is a part of that migration. Can anyone suggest a way to get an accurate count under these circumstances?
0
sikyala
Asked:
sikyala
  • 3
  • 3
  • 2
2 Solutions
 
slightwv (䄆 Netminder) Commented:
Even with stats the num_rows from the tables view isn't accurate.  As you mentioned, new data is being added all the time.

The only accurate way is a select count(*) from the tables.

Back to stats:
You can always manually generate the stats with the dbms_stats package.

Have you looked at user_indexes and the num_rows column?  Generating stats for a primary key index should be faster than the table and the num_rows for a primary key should have as accurate of info as the one from the tables view.
0
 
sikyalaSenior Database AdministratorAuthor Commented:
ok I will try looking at the user_indexes. i have tables that have huge amounts of data billions of records. Doing a select count always causes it to hang and not return results for long periods of time and so I am tring to avoid having to do that.
0
 
slightwv (䄆 Netminder) Commented:
>>hang and not return results for long periods of time and so I am tring to avoid having to do that.

It all depends on the level of accuracy you are comfortable with.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
Wasim Akram ShaikCommented:
Just to add you can use parallel clause in the count query to retrieve it little bit faster than you used to run a normal select (for eg: select /*+ PARALLEL (t,4) */ count(1) from Tab t;

before you run with parallel check out the explain plan of the queries,   with parallel without parallel, there is a sample illustration and results of using parallel clause in tom kyte's blog

https://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:885628301719
0
 
sikyalaSenior Database AdministratorAuthor Commented:
I tried the select with parallel and it still timed out on me. I checked and some of the tables don't have a primary key. So I don't know what alternative I would have.
0
 
slightwv (䄆 Netminder) Commented:
>>So I don't know what alternative I would have.

DISCLAIMER:  I CANNOT STRESS ENOUGH HOW BAD OF AN IDEA THIS IS

I can only think of one and I REALLY REALLY don't like it.

Create a table that has a list of all the tables you want to check and a count column.  Create an insert/delete trigger on all the tables that will maintain your table_count table.

The MAIN problem with it is that the trigger could have an issue with the update of your table and cause a legitimate transaction on the main table to fail.

THIS MAKES IT VERY DANGEROUS!!!!!

But it is an alternative...
0
 
Wasim Akram ShaikCommented:
==>I tried the select with parallel and it still timed out on me.

What degree have you used , try to increase it further .

if you have used parallel clause in your query, you can actually check its progress in v$session_longops, rather than saying time out, you can actually check where it has got timed out and upto what level it has performed the activity.

you can check the number of parallel sesssion by using the query

select * from v$px_session

use qcsid column to identify your parent session and monitor the progress before time out  by using long ops

select * from v$session_longops where sofar<>totalwork and sid =<sid_from_px_session>

you can try to increase the degree of parallel clause by checking out the progress like this
0
 
sikyalaSenior Database AdministratorAuthor Commented:
thanks
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now