Re: datguard issue

  • From: Bradd Piontek <piontekdd@xxxxxxxxx>
  • To: kp0773@xxxxxxxxx
  • Date: Thu, 14 Jan 2010 08:33:46 -0600

As far as I know, you aren't going to be able to do this. You are running an
unmanaged standby (shipping the logs yourself). You might be able to pull
this off by running SQL on the standby to register each archived logfile ,
and then managed recovery will pull it in, but Managed Recovery is intended
to be used with automatic log shipping. Part of that process is to register
the logfile with the standby. I can't think of a way MRP is going to know to
recover the next logfile.

Bradd Piontek
  "Next to doing a good job yourself,
        the greatest joy is in having someone
        else do a first-class job under your
        direction."
 -- William Feather


On Thu, Jan 14, 2010 at 8:16 AM, K R <kp0773@xxxxxxxxx> wrote:

> Thanks Dick.
>
> on primary log_archive_dest is not blank.  log_archive_dest_n is all blanks
>  on primary .  we are not  configuring any parameter change for  the
> logshipping to standby  on primary . we are  using a cron script to transfer
> the archivelogs from primary to standby into archive_archive_dest  with
> standby_file_management set to AUTO.  if i do recover standby database then
> it is seeing all the archivelog . but my observation so far is that it is
> not seeing the MRP process.
>
> I see few message on v$dataguard_message showing
>
> Log Apply Services       Warning                0           7
>          0 NO  13-JAN-10
> Media Recovery Waiting for thread 1 seq# 4239
>
> and on v$archive_dest_status
> LOG_ARCHIVE_DEST_11
> VALID     PHYSICAL       MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
> /arch/DEVD4/
>                     0                      0                0
>             0               0            0
>                                                                   NO
>
> and v$managed_standby
>
>   1* SELECT * from v$managed_standby
> SQL> /
>
> ARCH            6107 CONNECTED    ARCH
> 7005
> N/A
> N/A                                               0          0
>          0          0          0            0             0
>
> ARCH            6101 CONNECTED    ARCH
> 7007
> N/A
> N/A                                               0          0
>          0          0          0            0             0
>
> MRP0            6124 WAIT_FOR_LOG N/A
> N/A
> N/A
> N/A                                               1       4239
>          0          0          0            0             0
>
>
> Thanks
>
>
> On Thu, Jan 14, 2010 at 5:59 AM, Goulet, Richard <
> Richard.Goulet@xxxxxxxxxxx> wrote:
>
>>  Kar,
>>
>>     On the primary did you set the log_archive_dest_n parameters and
>> leave log_archive_dest blank?  Also can the primary tnsping to the standby?
>>
>>
>> *Dick Goulet***
>> Senior Oracle DBA/NA Team Lead
>> PAREXEL International
>>
>>
>>  ------------------------------
>> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
>> oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *K R
>> *Sent:* Wednesday, January 13, 2010 11:42 PM
>> *To:* Oracle-L@xxxxxxxxxxxxx
>> *Subject:* datguard issue
>>
>> Hi,
>>
>>
>> Oracle 9i database running on hp-ux ..  I am trying to create a standby
>> database .
>>
>> did all the standby setup . but I have not done any standby changes for
>> primary database.
>>
>> However  when i mount the standby database and do a recover standby
>> database then it is finding the archive log files on the standby server .
>>
>> However when i try to do the managed standby database it do not find the
>> archivelog file .
>>
>> What am I missing ?    appreciate any pointers
>>
>> thanks in advance
>> Kar
>>
>
>

Other related posts: