RE: Importing AWR data and changing DBID

  • From: Mayen.Shah@xxxxxxxxxx
  • To: Finn.Jorgensen@xxxxxxxxxxxxxxxxx
  • Date: Tue, 10 May 2011 15:00:08 -0400

I was going to suggest that....
If you use RMAN cloning, it will automatically assign new DBID as a 
cloning process.


From:   "Jorgensen, Finn" <Finn.Jorgensen@xxxxxxxxxxxxxxxxx>
To:     "'kylelf@xxxxxxxxx'" <kylelf@xxxxxxxxx>, "'ORACLE-L'    " 
Date:   05/10/2011 02:55 PM
Subject:        RE: Importing AWR data and changing DBID
Sent by:        oracle-l-bounce@xxxxxxxxxxxxx

This is a little backwards, but why don’t you assign a new DBID as part of 
the cloning process? That would take care of this problem as well as any 
RMAN central repository issues.
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] 
On Behalf Of kyle Hailey
Sent: Tuesday, May 10, 2011 2:47 PM
Subject: Importing AWR data and changing DBID

Just to avoid re-inventing the wheel ...
has anyone written something to change the DBID of AWR data when importing 
into a shared repository?
SInce many of my databases are clones they all have the same DBID, thus in 
order to distinguish the different database statistics in a shared AWR 
repository, I want  to change the DBIDs.

- Kyle

>>> This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for 
addressee.  If you are not the intended recipient, do not use the 
in this e-mail in any way, delete this e-mail and notify the sender. 

Other related posts: