PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

How to Move from Oracle 11.2.0.3.5 to 11.2.0.3.7

edited Sep 27, 2013 8:33AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 2 commentsAnswered
I have a DBA question about the following Oracle 11 bug: "Wrong Cardinality estimations for columns with DESC indexes)"

We are running PeopleTools 8.52.17, HR 9.1 on 11.2.0.3.5 and are stuggling with performance problems after upgrading from 10.2.0.5.  We are preparing to move to 11.2.0.3.7 with the hope that the resolution for the above bug will help.  However, I am curious what would be the correct way to implement this patch, or any related Oracle patch that indicates: "The statistics on the DESC columns were being gathered wrong." 

When an Oracle patch is released for bugs related to incorrect stat gathering (such as this one), does applying the patch automatically recreate or drop the "wrong" stats, or is it recommended for customers to drop and recreate stats for the required schemas (such as SYSADM) after the patch is applied.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT PeopleTools Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center