-
Hi,
Our production instance is OPS, our reporting instance is file system (the norm), when running a simple count(*) from a table where a column is null, we get substantially different elapsed times.
We have shrunk shared pool, and database buffer but no change at all.
any ideas?
Thanx
-
Gee, I understood nothing. So what is the problem? What is "a table where a column is null".
How can an instance be OPS?
Oracle Certified Master
Oracle Certified Professional 6i,8i,9i,10g,11g,12c
email: ocp_9i@yahoo.com
-
select count(*) from client where company_id is null, executes quickly in reporting db (filesystem) and slowly in OPS db. same init.ora, basically same config. the is not null returns in approximately the same time.
-
OPS - Oracle Parallel Server instance
-
Originally posted by acur8dba
select count(*) from client where company_id is null, executes quickly in reporting db (filesystem) and slowly in OPS db. same init.ora, basically same config. the is not null returns in approximately the same time.
same init.ora? How can you have the same init.ora for a DB mounted in exclusive mode and for a DB mounted in parallel.
All I understand is that some select count(*) is slow. How big is the table and how slow is slow? 5 seconds? 5 minutes?
Oracle Certified Master
Oracle Certified Professional 6i,8i,9i,10g,11g,12c
email: ocp_9i@yahoo.com
-
what app are you running? a home grown ? out of the box
you realize that in OPS unless your app is specifically designed to run with OPS perfromance will be horrible.
Have you done any partitioning at the oracle level?
I'm stmontgo and I approve of this message
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|