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)

DB Upgrade and effect on cloning steps

Oct 20, 2015 9:08PM edited Feb 1, 2018 4:02AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 6 commentsAnswered ✓

My current environment is R12.1.3 running on Red Hat Linux and an 11.2.0.3 database. Prod on one set of servers Test/Dev on another set.

I am planning on upgrading the database to 12.1.0.2 and in fact have done our Test instance.

Now I'm just trying to remember what steps I will have to take to reproduce that change in my cloned environments once I've upgraded Prod.

I will use rman to refresh the database but I'm a little fuzzy in what steps I'll need to do to setup my new Oracle_Home etc.

I have a two node config with DB Tier and App tier.

Tagged:

EBS-ATG-Patch

1

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