High cursor: mutex X after July 2019 RU installed
From: MacGregor, Ian A. <"MacGregor,>
Date: Tue, 24 Sep 2019 21:06:47 +0000
Message-ID: <SN6PR07MB5630E08ADE57808591E7271DE2840_at_SN6PR07MB5630.namprd07.prod.outlook.com>
Has anyone else run into this?
Date: Tue, 24 Sep 2019 21:06:47 +0000
Message-ID: <SN6PR07MB5630E08ADE57808591E7271DE2840_at_SN6PR07MB5630.namprd07.prod.outlook.com>
Has anyone else run into this?
One of our 12.2.0.1 databases suffered from a high number of cursor: mutex X waits after the July 2019 RU (patch 29757449) was applied. The reason for the problem was
12.2 CURSOR MUTEX X DUE TO SQL NOT SHARED BECAUSE OF BIND_EQUIV_FAILURE This is bug 28794230.
Oracle support gave me two underscore parameters to set instead.
The latest patch having to do with the bug was an overlay for the July 2018 RU. Since this database was not upgraded until earlier this yearI am wondering if the bug fix made it into an previous RU and the July 2019 RU caused a regression
Ian A. MacGregor
SLAC National Accelerator Laboratory
Computing Division
To offer the best IT service at the lab and be the IT provider of choice.
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Sep 24 2019 - 23:06:47 CEST