Close, I took a look at v$database, and there is a activation# field in it, and the number, converted to hex, matches the number reported in the error messages on the standby database. So that is my problem. That activation# changed when the primary was restored onto the new server. But, activation# and dbid do not match. Not even close. Now I know what and where it is, but not how to change it...time to update the TAR... -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Mladen Gogala Sent: Thursday, March 25, 2004 2:05 PM To: oracle-l@xxxxxxxxxxxxx Subject: Re: Dataguard - primary database moved to another server On 03/25/2004 01:52:40 PM, "Grabowy, Chris" wrote: > Huh? How do you know that DBID is the same as the standby activation id???? > > What secrets are you keeping?? No secrets here, I definitely talk too much. The word "secret" isn't even a part of my vocabulary. As for the DBID, isn't that the error that you are getting? I believe that standby ID and the main database ID should definitely be the same. ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html ----------------------------------------------------------------- ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------