Managing Databases using Enterprise Manager (MOSC)

MOSC Banner

Duplicate database - overwrite already monitored database - monitoring fails

in Managing Databases using Enterprise Manager (MOSC) Question

Hi,

I have recently started to use RMAN and DUPLICATE DATABASE from backups to duplicate a prod DB to UAT, this DB is monitored using OEM (v 12.1.0.1).

We used to use RMAN and a straight RESTORE/RECOVER but duplicate seemed like the better option.

I've found that after the duplicate completes, I get a "Count of targets not uploading..." alert, and the DB target is no longer uploading.  I'm assuming this is because the DBID has changed, can anyone confirm this?

As an example of the trouble it's caused, this also seems to make the target completely unsuable within OEM - selecting the target for deletion or trying to view the target just gives an eternal spinner.  I was able to delete the target from OEM by deleting the System, but this left it in a state where I couldn't add it back in, claiming that there was a duplicate target.  I had to use these two commands to remove the unresponsive target from OEM and I'm not too happy - tinkering in this way isn't ideal:

Tagged:

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