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)

Upgrading from12.1.3 to 12.2.9. how to fix Table must be owned by an EBS product schema, not APPS

Apr 14, 2021 3:25PM edited Aug 20, 2021 10:26AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 3 commentsAnswered

GSCC Report adzddbcc Section-19

Table must be owned by an EBS product schema, not APPS."

P2: Tables owned by APPS cannot be patched using online patching.

Fix: Move table to a product schema and then call the table

We have some custom tables which are owned by APPS. How can we move it to a custom schema with its Data, Constarint and Indexes.

Is there any specific API to do so?

The Table should have all definition as it was in APPS Schema. The Triggers also should work as it is.

The below steps seems will not work as the constraint and indexes will not get created..

Tagged:

EBS-ATG-Upgrade

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