Re: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS

HJR, You write
"The making of a physical alteration to your
: primary database renders your standby database invalid, such that it needs
: to be re-created from scratch (one of the major pains-in-the-butt
regarding
: standby databases since time immemorial).
"

The only changes that would actually require rebuilding the Standby would be a RESETLOGS or a CLEAR LOG on the primary.

Surely, Oracle provides a mechanism to add the new file into the Standby as well ...
ALTER DATABASE CREATE DATAFILE ' ...' AS '...' ; so that Recovery can proceed.
That is why I do in my 8.1.7 database where I have a Standby.

9i DataGuard uses the "STANDBY_FILE_MANAGEMENT=AUTO" parameter but I haven't used 9iDG.
And I don't have the 8.1.7 documentation to quote from it as to how to use ALTER DATABASE CREATE DATAFILE and continue recovery.

Hemant

"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:40cd5b12$0$13621$afc38c87_at_news.optusnet.com.au...
:
: "yls177" <yls177_at_hotmail.com> wrote in message
: news:c06e4d68.0406132356.1965d961_at_posting.google.com...
: > i add a datafile to my production and did the same with my standby.
: > afterwhich, i synch back them but get the below
: >
: >
: > ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get
: > error below
: > ORA-01194: file 1 needs more recovery to be consistent
: > ORA-01110: data file 1: '/oracle/SID/data1/system_1/system.data1'
: >
: >
: > the log sequence in my production and standby servers are the same and
: > my archive log list shows the same sequence as well as given further
: > confirmation by my alert file.
: >
: >
: > is there any cause for alarm?
:
: Er, yes.
:
: We could analyze this really carefully, and um and ahh about how one goes
: about propagating physical database changes to a standby. But to do that,
we
: might need minor details such as Oracle version and operating system.
:
: The shorter story is: forget it. The making of a physical alteration to
your
: primary database renders your standby database invalid, such that it needs
: to be re-created from scratch (one of the major pains-in-the-butt
regarding
: standby databases since time immemorial).
:
: Regards
: HJR
:
:
Received on Wed Jun 16 2004 - 10:02:16 CDT