Re: Slow performance when upgrading to 11g from 10g
From: Ilmar Kerm <ilmar.kerm_at_gmail.com>
Date: Wed, 2 Feb 2011 18:44:36 +0200
Message-ID: <AANLkTinxD+e0jJZ5PferpttJNDkOV3TmmaL5LPyqEpG+_at_mail.gmail.com>
On Wed, Feb 2, 2011 at 6:12 AM, Aragon, Gabriel (GE, Corporate, consultant) <gabriel.aragon_at_ge.com> wrote:
> Hi guys,
>
> though I have collected some info on this, I would like to know if there is
> some tips that you can share on same, if after upgrading to 11g you detected
> slow performance on a database that was ok in 10g (same hw), and if
> possible some stories of success.
Date: Wed, 2 Feb 2011 18:44:36 +0200
Message-ID: <AANLkTinxD+e0jJZ5PferpttJNDkOV3TmmaL5LPyqEpG+_at_mail.gmail.com>
On Wed, Feb 2, 2011 at 6:12 AM, Aragon, Gabriel (GE, Corporate, consultant) <gabriel.aragon_at_ge.com> wrote:
> Hi guys,
>
> though I have collected some info on this, I would like to know if there is
> some tips that you can share on same, if after upgrading to 11g you detected
> slow performance on a database that was ok in 10g (same hw), and if
> possible some stories of success.
We did 10.2.0.4 EE -> 11.2.0.2 EE on Solaris x86_64 upgrade a few months ago. A few unexpected problems:
- When using ansi outer joins, 10.2 allowed some columns to be ambiguously defined in join conditions. Note 1111459.1.
- If you used in 10g to mass-create one-time DBMS_SCHEDULER jobs, then in 11.2 you need to set the job_style parameter to LIGHTWEIGHT, otherwise will hit the following issue with internal SQL (insert into access$...): http://www.usn-it.de/index.php/2010/08/04/oracle112-mutex-s-too-many-child-cursors/ Anydata arguments are not supported with lightweight jobs (no error message, but after some time job execution just stops).
-- Ilmar Kerm -- http://www.freelists.org/webpage/oracle-lReceived on Wed Feb 02 2011 - 10:44:36 CST