Since there is no data change in the table, whatever stats were last gathered, will be good enough even today, so the optimizer will refer to the same stats, stats will not be stale, or not needed to be gathered explicitly. So fresh stats in a nut shell.
Great, should we gather states for whole database or schema or tables or indexes and what will be the sequence? Should we gather first for database or which one is first and so on
Hi want to expertise PTuning , you told there are more than 16 ways to identify db problems. Can you do a session or series of sessions of these. I shall be very very thankful to you.
How can I automate the schema refresh? First of all, is it possible to automate the schema refresh? In our environment, we used to export schema first. Then copying dump file from production to test server. Then dropping and recreating the schema and finally we will import it in test server.
@@dbagenesis but that is not much easy. Here it comes a real challenge. The dump file name and schema name will not remains the same. It keeps changing everyday.
HELLO . my question is i have database server with 128gig ram G9 with centos 6.10 .how much ram is best for os + memory target +sga +pga ? database is RDBMS
You just need to set MEMORY_TARGET.. you can start with 20 GB and later increase / decrease based on DB performance / awr report / instance load profile.
It should be having fresh stat for the table who's any record wasn't update/inserted/deleted over last year and stats were taken then only. #dbaChallenge
