High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Migrating a Standalone to a Primary - how to patch the Standby afterwards?

in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered ✓

Hi all,

I need to migrate a Standalone database system to a Data Guard environment. The Standalone database already exists and was patched to release/version 19.21. To migrate this database to a Primary database seems not to be that complicated: I plan to add some parameters (e.g. DB_UNIQUE_NAME, FAL_SERVER, DB_FILE_NAME_CONVERT etc.) to the INIT.ORA file and start the database with this INIT file. Afterwards I will create the Standby database with the RMAN command "duplicate target database for standby backup location '/…/…/…' nofilenamecheck;" Of course do I need to prepare the LISTENER on both hosts before. This is the method I used

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center