Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Install, Upgrade, Clone, Patch - EBS (MOSC)

invalids after upgrade keep coming back

Nov 22, 2015 10:58AM edited Sep 2, 2016 9:32AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 5 commentsAnswered ✓

R12.1.3 running on RHEL and recently upgraded db to 12c followed by lots of patches for HRMS and Financials.

Post upgrade all good, only 4 invalids. Couple of days later had about 2000 invalids. Recompiled and setup alerting to detect when it happens.

Next day all good until something runs at night and got alerts that there were 23 invalid objects.

Plan is to track what the objects are and try to determine when they go invalid and if same or not. I don't have the actual objects here to list.

Anybody run into this before?

Tagged:

EBS-ATG-Patch

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month