Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



RE: [MAXIMO List] Re: Issues with latest Oracle CPU

From: Lonnie Stone (2014-08-13 08:45)

What patch version on oracle? I am not seeing it in the email thread.
Lonnie Stone
@LonStone3
-----Original Message-----
From: "'Hanna, Christopher A CTR' christopher.a.hanna@uscg.mil [MAXIMO]" <MAXIMO@yahoogroups.com>
Sent: ‎8/‎13/‎2014 7:17 AM
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Subject: RE: [MAXIMO List] Re: Issues with latest Oracle CPU

Sorry, I'm not a DBA so my details are a little vague. Wouldn't surprise me if this issue doesn't affect everyone (or maybe anyone else). Could be something about the tight controls on our DB that the patch breaks.
We had to back the patch off our dev environment. Had to drop and rebuild all the text indexes too. Our DBA has been actively working with Oracle support for almost three weeks now without resolution. IBM support has also been informed.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Tuesday, August 12, 2014 7:12 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Issues with latest Oracle CPU
We tested in our dev environment and did not see any text corruption. I created four new work orders, waited 15 minutes for the text indexes to refresh, and performed a description search. All four of those new work orders appeared in the search result. So, for our environment, we are unable to reproduce the issue.
Did you apply the security patches, CPU patches, or BOTH?
Perhaps we need to try some other steps?
Is this issue resolved on your end? If so, what steps did you take?
The DBA is going to apply the patch to production on Wednesday night. They have a backout plan, but wanted to see if we could reproduce the issue in our dev environment before applying any patches in production.


From: Hanna, Christopher A CTR (2014-08-14 14:00)

It's the July Oracle Critical Patch for 11.2.0.3 - Patch 32 (aka 18940194) for 64-bit Windows

-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Wednesday, August 13, 2014 8:46 AM
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Re: Issues with latest Oracle CPU



What patch version on oracle? I am not seeing it in the email thread.

Lonnie Stone
@LonStone3

-----Original Message-----
From: "'Hanna, Christopher A CTR' christopher.a.hanna@uscg.mil [MAXIMO]" <MAXIMO@yahoogroups.com>
Sent: ‎8/‎13/‎2014 7:17 AM
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Subject: RE: [MAXIMO List] Re: Issues with latest Oracle CPU

Sorry, I'm not a DBA so my details are a little vague. Wouldn't surprise me if this issue doesn't affect everyone (or maybe anyone else). Could be something about the tight controls on our DB that the patch breaks.

We had to back the patch off our dev environment. Had to drop and rebuild all the text indexes too. Our DBA has been actively working with Oracle support for almost three weeks now without resolution. IBM support has also been informed.

-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Tuesday, August 12, 2014 7:12 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Issues with latest Oracle CPU

We tested in our dev environment and did not see any text corruption. I created four new work orders, waited 15 minutes for the text indexes to refresh, and performed a description search. All four of those new work orders appeared in the search result. So, for our environment, we are unable to reproduce the issue.
Did you apply the security patches, CPU patches, or BOTH?

Perhaps we need to try some other steps?

Is this issue resolved on your end? If so, what steps did you take?

The DBA is going to apply the patch to production on Wednesday night. They have a backout plan, but wanted to see if we could reproduce the issue in our dev environment before applying any patches in production.