QUESTION POSED ON: 07 May 2009 We have a nightly batch job that refreshes the data warehouse tables. The PL/SQL and SQL code is very old ( from 2002). It runs OK in 9i, but when we test in 10g some of the UPDATE statements are extremely slow. The job runs forever, so we have to kill the job. How would you go about the problem? Are there any parameters that you would change?
>
It is not uncommon for an SQL statement in one major version to run slower when upgrading to a new major version. One would need to tune the SQL statements on the new version. This should be done in a test environment before touching production. I would start by examining the UPDATE statements that need to be tuned, and you may need to look at adjusting initialization parameters that affect the Cost Based Optimizer's behavior in Oracle 10g, or look toward Plan Stability.
Search and Browse the Expert Answer Center Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.