Passfail status sequence

TS code, I need to change must have a sous-suite and the subsequence will be about 5 or 6 steps to check. What is the standard method to add the results of all these declarations to check to give an overall value of pass/fail for the subsequence? Other codes that I have watched, looks can be spent at several levels: i.e. a success/failure of sub-sub-sequence passes until the subsequence and he passes his success/failure up to the main sequence.

Seems strange that I have now that many screws in this suite for several months but never had to deal with the interpretation of pass/fail data before TS.

Thank you

JVH

Then, a precondition should work just fine. You can simply select Insert step Pass or insert step fails and then choose step. If you want to see the property, RunState.PreviousStep.Result.Status.

Tags: NI Software

Similar Questions

Roll forward standby database with the incremental backup, when a data file is deleted in primary education

Hello
I'm nologging operations + deleting some files in the primary and you want to roll forward the day before using the incremental backup Yvert.
I do in particular, as the files are dropped?
I got to meet ( Doc ID 1531031.1 ) which explains how to roll forward when a data file is added.
If I follow the same steps, to make the move to restore the data file newly added, will it work in my case?
Can someone please clarify?
Thank you
San

I was wondering if reocover noredo is performed before restored controlfile, oracle will apply the incremental backup error-free files, and in this case, what would be the status of the data file in the control file.

Why do you consider to retrieve the day before first and then in the restaurant of the controlfile will lead to problems. Please read my first post on this thread - I had clearly mentioned that you would not face problems if you go with the method of deployment.

Here is a demo for you with force logging is disabled. For the first time the day before resuming and restored then the controlfile ensures:

Primary: oraprim

Standby: orastb

Tablespace DataFile of MYTS is removed on primary:

SYS @ oraprim > select force_logging in the database of v$.

FORCE_LOGGING

---------------------------------------

NO.

Currently the tablespace is to have 2 data files.

SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

FILE_NAME

-------------------------------------------------------

/U01/app/Oracle/oradata/oraprim/myts01.dbf

/U01/app/Oracle/oradata/oraprim/myts02.dbf

In standby mode, the tablespace is to have 2 data files:

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

/U01/app/Oracle/oradata/orastb/myts02.dbf

Postponement of the day before on the primary log shipping

SYS @ oraprim > alter system set log_archive_dest_state_3 = delay;

Modified system.

Dropped 1 MYTS datafile on the primary.

SYS @ oraprim > alter tablespace myts drop datafile ' / u01/app/oracle/oradata/oraprim/myts02.dbf';

Tablespace altered.

Removed some archives to create a space.

[oracle@ora12c-1 2016_01_05] $ rm - rf * 31 *.

[oracle@ora12c-1 2016_01_05] $ ls - lrt

13696 total

-rw - r - 1 oracle oinstall 10534400 5 January 18:46 o1_mf_1_302_c8qjl3t7_.arc

-rw - r - 1 oracle oinstall 2714624 5 January 18:47 o1_mf_1_303_c8qjmhpq_.arc

-rw - r - 1 oracle oinstall 526336 5 January 18:49 o1_mf_1_304_c8qjp7sb_.arc

-rw - r - 1 oracle oinstall 23552 5 January 18:49 o1_mf_1_305_c8qjpsmh_.arc

-rw - r - 1 oracle oinstall 53760 5 January 18:50 o1_mf_1_306_c8qjsfqo_.arc

-rw - r - 1 oracle oinstall 14336 Jan 5 18:51 o1_mf_1_307_c8qjt9rh_.arc

-rw - r - 1 oracle oinstall 1024 5 January 18:53 o1_mf_1_309_c8qjxt4z_.arc

-rw - r - 1 oracle oinstall 110592 5 January 18:53 o1_mf_1_308_c8qjxt34_.arc

[oracle@ora12c-1 2016_01_05] $

Current main MYTS data files:

SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

FILE_NAME

-------------------------------------------------------

/U01/app/Oracle/oradata/oraprim/myts01.dbf

Current data of MYTS standby files:

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

/U01/app/Oracle/oradata/orastb/myts02.dbf

Gap is created:

SYS @ orastb > select the process, status, sequence # v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.

--------- ------------ ----------

ARCH. CLOSING 319

ARCH. CLOSING 311

CONNECTED ARCH 0

ARCH. CLOSING 310

MRP0 WAIT_FOR_GAP 312

RFS IDLE 0

RFS IDLE 0

RFS IDLE 0

RFS IDLE 320

9 selected lines.

Backup incremental RMAN is taken elementary school.

RMAN > incremental backup of the format of database of SNA 2686263 ' / u02/bkp/%d_inc_%U.bak';

From backup 5 January 16

using the control file of the target instead of recovery catalog database

the DISC 2 channel configuration is ignored

the DISC 3 channel configuration is ignored

configuration for DISK 4 channel is ignored

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 41 type device = DISK

channel ORA_DISK_1: starting full datafile from backup set

channel ORA_DISK_1: specifying datafile (s) in the backup set

Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oraprim/system01.dbf

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/sysaux01.dbf 00003

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/undotbs01.dbf 00004

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/users01.dbf 00006

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/myts01.dbf 00057

channel ORA_DISK_1: starting total, 1-January 5, 16

channel ORA_DISK_1: finished piece 1-January 5, 16

piece handle=/u02/bkp/ORAPRIM_inc_42qqkmaq_1_1.bak tag = TAG20160105T190016 comment = NONE

channel ORA_DISK_1: complete set of backups, time: 00:00:02

Backup finished on 5 January 16

Saved controlfile on primary:

RMAN > backup current controlfile to Eve format ' / u02/bkp/ctl.ctl';

Cancel recovery in standby mode:

SYS @ orastb > alter database recover managed standby database cancel;

Database altered.

Recover the day before by using the above backup items

RMAN > recover database noredo;

From pick up to 5 January 16

the DISC 2 channel configuration is ignored

the DISC 3 channel configuration is ignored

configuration for DISK 4 channel is ignored

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 26 type of device = DISK

channel ORA_DISK_1: from additional data file from the restore backup set

channel ORA_DISK_1: specifying datafile (s) to restore from backup set

destination for the restoration of the data file 00001: /u01/app/oracle/oradata/orastb/system01.dbf

destination for the restoration of the data file 00003: /u01/app/oracle/oradata/orastb/sysaux01.dbf

destination for the restoration of the data file 00004: /u01/app/oracle/oradata/orastb/undotbs01.dbf

destination for the restoration of the data file 00006: /u01/app/oracle/oradata/orastb/users01.dbf

destination for the restoration of the data file 00057: /u01/app/oracle/oradata/orastb/myts01.dbf

channel ORA_DISK_1: backup /u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak piece reading

channel ORA_DISK_1: room handle=/u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak tag = TAG20160105T190016

channel ORA_DISK_1: restored the backup part 1

channel ORA_DISK_1: restore complete, duration: 00:00:01

Finished recover to 5 January 16

Restored the controlfile and mounted the day before:

RMAN > shutdown immediate

dismounted database

Instance Oracle to close

RMAN > startup nomount

connected to the database target (not started)

Oracle instance started

Total System Global Area 939495424 bytes

Bytes of size 2295080 fixed

348130008 variable size bytes

583008256 of database buffers bytes

Redo buffers 6062080 bytes

RMAN > restore controlfile eve of ' / u02/ctl.ctl ';

From 5 January 16 restore

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 20 type of device = DISK

channel ORA_DISK_1: restore the control file

channel ORA_DISK_1: restore complete, duration: 00:00:01

output file name=/u01/app/oracle/oradata/orastb/control01.ctl

output file name=/u01/app/oracle/fast_recovery_area/orastb/control02.ctl

Finished restore at 5 January 16

RMAN > change the editing of the database;

Statement processed

output channel: ORA_DISK_1

Now the data file does not exist on the standby mode:

SYS @ orastb > alter database recover managed standby database disconnect;

Database altered.

SYS @ orastb > select the process, status, sequence # v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.

--------- ------------ ----------

CONNECTED ARCH 0

CONNECTED ARCH 0

CONNECTED ARCH 0

ARCH. CLOSING 329

RFS IDLE 0

RFS IDLE 330

RFS IDLE 0

MRP0 APPLYING_LOG 330

8 selected lines.

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

Hope that gives you a clear picture. You can use this to roll forward day before using the SNA roll forward Eve physical database using RMAN incremental backup | Shivananda Rao

-Jonathan Rolland

Gap of Eve

I have physical standby and primary database in 11.2.0.2 on linux. This is used for purposes of learning and today I could see that the waking state is saying as "pending gap" but when I query v$ archived_log, I see that the watch is synchronized. I'm a little confused about this.
Primary:

Sys@Prim> select thread #, max(sequence#) in Group v$ archived_log by thread #;

THREAD # MAX(SEQUENCE#)
---------- --------------
1 117

Standby time:

Sys@stndby > select thread #, max(sequence#) in v$ archived_log in case of application = 'YES' group by thread #;

THREAD # MAX(SEQUENCE#)
---------- --------------
1 117

Standby:

Sys@stndby > select process, status, sequence # in v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
MRP0 WAIT_FOR_GAP 50
RFS IDLE 0
RFS IDLE 0
RFS IDLE 0
RFS IDLE 113

Is there a gap?

OK, as said, 117 sequence seems to be of the previous incarnation.

Your database is currently looking for 50 sequence and a sequence gap 50 to 57.

You have backups of these archives? If so, then restore it from the backup on the primary and the standby will search automatically.

If this is not the case, use the roller before incremental YVERT backup method to get your watch synchronized.

You can return this Roll Forward Physical Standby Database using RMAN incremental backup | Shivananda Rao

HTH

-Jonathan Rolland

DG watch db, which complicates his report

Hi all
11.2.0.1
AIX 6.1
After that the MRP0 was declining and active, my waking state even once is not consistent.
In elementary SCHOOL, I run > select process, status, sequence # in v$ managed_standby;
STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
ARK OF WRITING 3505
ARCH. CLOSING 3515
ARK OF WRITING 3506
ARK OF WRITING 3507
LNS WRITTEN 3516
Then the day BEFORE, I also run > select process, status, sequence # in v$ managed_standby;
STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
ARCH. CLOSING 3504
CONNECTED ARCH 0
ARCH. CLOSING 3501
ARCH. CLOSING 3502
RFS IDLE 3516
IDLE 3506 RFS
IDLE 3507 RFS
MRP0 WAIT_FOR_LOG 3505
RFS IDLE 3505
9 selected lines.

Why is it my PRIMARY is already at 3516? While my watch is on at the 3505?

Help, please
Thank you

Odd;

I never had that happen, but I heard it reported before.

You may need to use this after the copy:

ALTER DATABASE REGISTER LOGFILE

Example:

ALTER DATABASE REGISTER LOGFILE ' / u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_21_716110538.arc';

She can raise a caveat that it is already registered.

I've never had much luck with V$ ARCHIVE_GAP. I could use the query from the link and see if the gap goes.

Best regards

mseberg

Monitoring of physical standby DG

Hi all
11.2.0.1
AIX 6.1
How will I know if my old db is currently being updated to the last roll forward or archive log?
This procedure is correct?
Primary:
========
SQL > select process, status, sequence # from v$ managed_standby;
STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
ARK OF WRITING 2182
ARK OF WRITING 2183
ARCH. CLOSING 2196
ARK OF WRITING 2184
LNS WRITTEN 2197
On hold:
========
SQL > select process, status, sequence # from v$ managed_standby;
STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
ARK OF CLOSING 2195
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
MRP0 WAIT_FOR_LOG 2182
RFS IDLE 2183
RFS IDLE 2184
RFS IDLE 2182
RFS IDLE 2197
What line here I need to check? Why is - this MRP0 waiting journal 2182 when he has to wait for 2198?
Thank you very much
zxy

cancel the recovery.

and in fast usage of sql recover standby database.

and yet once start the ASR.

The reason in would be that archive logs can have has been corrupted while they were carrying primary eve.

If that were the case then you must copy the production archive log, and then apply again.

DataGuard applied Log question
Hi gurus,

Oracle Version 9i
OS:-AIX

My request when I'm checking the log of the primary database it shows APPLIED = NO' while the DR it shows APPLIED = YES to the same log sequence. Can you let me know what could be the possible reason and how can I remedy.
I database is the way of datagurad and DG_BROKER = true.

DATABAS_E PRIMARY SCHOOL
On the primary database are running processes
SQL > select process, status, sequence # from v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CLOSING 596798 ARCH.
CLOSING 596797 ARCH.

SQL > select sequence #, applied, first_time, next_time dest_id v$ archived_log where sequence #= 596715;

SEQUENCE # APP FIRST_TIM NEXT_TIME DEST_ID
---------- --- --------- --------- ----------
* 596715 NO 9 MARCH 13 9 MARCH 13 1 *.
* 596715 NO 9 MARCH 13 9 MARCH 13 2 *.

On the SECONDARY DATABASE_

SQL > select process, status, sequence # from v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
MRP0 WAIT_FOR_LOG 596800
RFS RECEIVE 596798
RFS HOME 596797

SQL > show parameter dg_broker_start

VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
dg_broker_start Boolean TRUE

SELECT A BOW. THREAD # "Thread", ARCH. SEQUENCE # 'last received sequence', Appl. SEQUENCE # "last sequence applied", (the centre ARCH. SEQUENCE #-APPL.) Sequence #) 'the difference '.
Of
(SELECT THREAD #, SEQUENCE # FROM V$ ARCHIVED_LOG WHERE (THREAD #, FIRST_TIME) IN (SELECT THREAD #, MAX (FIRST_TIME) FROM V$ ARCHIVED_LOG GROUP BY THREAD #)) ARCH,
(SELECT THREAD #, SEQUENCE # FROM V$ LOG_HISTORY WHERE (THREAD #, FIRST_TIME) IN (SELECT THREAD #, MAX (FIRST_TIME) OF V$ LOG_HISTORY GROUP BY THREAD #)) APPL
WHERE
ARCH. THREAD # = APPL. THREAD #.
ORDER BY 1;

Last thread last sequence received sequence applied difference
---------- ---------------------- --------------------- ----------
1 596799 596799 0

SQL > select sequence #, applied, first_time, next_time dest_id v$ archived_log where sequence #= 596715;

SEQUENCE # APP FIRST_TIM NEXT_TIME DEST_ID
---------- --- --------- --------- ----------
* YES 596715 9 MARCH 13 9 MARCH 13 0 *.

Thank you
Meena
Ok

So according to this query
```
SELECT
   ARCHIVED_THREAD#,
   ARCHIVED_SEQ#,
   APPLIED_THREAD#,
   APPLIED_SEQ#
FROM
  V$ARCHIVE_DEST_STATUS;
```
```
ARCHIVED_THREAD# ARCHIVED_SEQ# APPLIED_THREAD# APPLIED_SEQ#
---------------- ------------- --------------- ------------
          1      596799                1       596714
          
```
The gap is 85. Yes, you have a problem.

You have all these newspapers archive on the main server or standby? So from 596714 up to 596799.

If Yes use statement ALTER DATABASE REGISTER LOGFILE of them to apply.

Best regards

mseberg

to make a cast or not cast varchar2 total length of index Resultatspour function?
I have a table where a set of four fields, plus a status must have a single status 'in progress' but can have many records of the status of "historic". Meanwhile, there is a synthetic independent status sequence key. I wrote a function index like this:

create an index only funcindex on mytable
(status of the case
When "history".
then to_char (synthetic_key)
When the 'current '.
then col1 | col2. COL3 | COL4
(end);

It seems to work, however, I'm curious to know how a data type is assigned and that what matters. The key to the synthesis is a number, but it is converted with "to_char' which does not have a length max. license terms 1-4 are varchar2 of different lengths.
Is there a need or enjoy adding the lengths of the passes 1-4 and cast the result of the case as varchar2 (sometotal) or the system should really be left to figure it out on its own?

PS - I use 11g and there is nothing special about the table. just a sequence and pk press the synth.
You can try to change the length of characters for VARCHAR2 columns and/or using the (x) NUMBER data type declaration and check how Oracle is calculation of index function based with key length:
```
select
column_name, column_length, char_length
from
user_ind_columns
where
index_name = 'FUNCINDEX';
```
See also http://jonathanlewis.wordpress.com/2009/06/05/online-rebuild/.

Out of sync Oracle DB on AIX machine
Hi Master,

Once again with the primary and secondary sync error log, but this time the DG_BROKER_START = TRUE.
My AIX machine.

Here are some details and the request that I pulled on the database of Dr. I tried the command 'ALTER DATABASE REGISTER LOGFILE "LOG file NAME" but it says already saved log file.
Please let me know what I should do to fix this problem.

SQL > * display parameter DG_BROKER_START *.

VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
dg_broker_start Boolean TRUE

SQL > * select switchover_status in the database of v$. *

SWITCHOVER_STATUS
------------------
ACTIVE SESSIONS

SQL > * select process, status, sequence # in v$ managed_standby; *

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
RFS RECEIVE 585297
RFS RECEIVE 585296

SQL > * select the sequence #, applied, first_time next_time of the order of v$ archived_log by sequence #. *

YES 585258 15 NOVEMBER 12 NOVEMBER 15, 12
YES 585259 15 NOVEMBER 12 NOVEMBER 15, 12
YES 585260 15 NOVEMBER 12 NOVEMBER 15, 12
585261 NOT 15 NOVEMBER 12 NOVEMBER 15, 12
585262 NOT 15 NOVEMBER 12 NOVEMBER 15, 12
585263 NOT 15 NOVEMBER 12 NOVEMBER 15, 12
585264 NOT 15 NOVEMBER 12 NOVEMBER 15, 12
|
|
585295 NOT 16 NOVEMBER 12 NOVEMBER 16, 12
585296 NOT 16 NOVEMBER 12 NOVEMBER 16, 12
585297 NOT 16 NOVEMBER 12 NOVEMBER 16, 12

SQL > * list of newspaper archive; *
Database log mode Archive Mode
Active AutoArchive
Archives/u03/oradata/ccnbdr/archive destination
More old sequence of journal online 585294
Log sequence to archive 0
Current log sequence 585298

SQL > * SELECT ARCH. THREAD # "Thread", ARCH. SEQUENCE # 'last received sequence', Appl. SEQUENCE # "last sequence applied", (the centre ARCH. SEQUENCE #-APPL.) Sequence #) "Difference."
* 2 TO *.
* 3 (SELECT THREAD #, SEQUENCE # FROM V$ ARCHIVED_LOG WHERE (THREAD #, FIRST_TIME) IN (SELECT THREAD #, MAX (FIRST_TIME) OF V$ ARCHIVED_LOG GROUP BY THREAD #)) ARCH, *.
* 4 (SELECT THREAD #, SEQUENCE # FROM V$ LOG_HISTORY WHERE (THREAD #, FIRST_TIME) IN (SELECT THREAD #, MAX (FIRST_TIME) OF V$ LOG_HISTORY GROUP BY THREAD #)) APPL *.
* WHERE 5 *.
* 6 ARC. THREAD # = APPL. THREAD #*.
* 7 ORDER BY 1; *

Last thread last sequence received sequence applied difference
---------- ---------------------- --------------------- ----------
1 585297 585260 37
Agreed.

What happens when you start MRP?

For this ORA-16089: archive log has already been saved

You can try:

ALTER DATABASE REGISTER or REPLACE PHYSICAL LOGFILE "full_path_log_onStandby";

Example of mine
```
ALTER DATABASE REGISTER OR REPLACE LOGFILE '/u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_21_716110538.arc';
```
Is not worth a glance
OERR: ORA-16089 archive log has already been registered [172821.1 ID]

Best regards

mseberg

Published by: mseberg on November 15, 2012 19:04

Log out of sync
Hi gurus,

Need urgent help... My logs of primary and secondary database is out of sync. I am new to this Dataguard and need help to fix this problem. I went through a few blogs and found people suggesting a restart of the system Dr. Pas sure it is correct or not. Have posted below my current state primary and DR databae: -.

DB PRIMARY
=================
Put on the last generated sequence
---------- -----------------------
1 52293
1 52293

SQL > list of archive logs
Database log mode Archive Mode
Active AutoArchive
Destination of archive E:\oracle\P01\oraarch\P01arch
More old sequence of journal online 52291
Log sequence archive 52294
Current log sequence 52294

SQL > show parameter DG_BROKER_START

VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
dg_broker_start boolean FALSE

+++++++++++++++++
SECONDARY
+++++++++++++++++
After following 52223 log sequence is missing, after that all the papers received but not applied

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
YES 52215 6 NOVEMBER 12 NOVEMBER 6, 12
52216 YES 6 NOVEMBER 12 NOVEMBER 6, 12
YES 52217 6 NOVEMBER 12 NOVEMBER 6, 12
YES 52218 6 NOVEMBER 12 NOVEMBER 6, 12
YES 52219 6 NOVEMBER 12 NOVEMBER 6, 12
52220 YES 6 NOVEMBER 12 NOVEMBER 6, 12
52221 YES 6 NOVEMBER 12 NOVEMBER 6, 12
YES 52222 6 NOVEMBER 12 NOVEMBER 6, 12
YES 52223 6 NOVEMBER 12 NOVEMBER 6, 12
52225. NO 6 NOVEMBER 12 NOVEMBER 7, 12
52226 NOT 7 NOVEMBER 12 NOVEMBER 7, 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52227. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52228. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52229. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52230. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52231. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52232. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52233. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52234. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52235. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52236. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52237. NO 7 NOVEMBER 12 NOVEMBER 7, 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52238. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52239. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52240. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52241. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52242. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52243. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52244. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52245. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52246. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52247. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52248. NO 7 NOVEMBER 12 NOVEMBER 7, 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52249. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52250. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52251. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52252. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52253. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52254. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52255. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52256. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52257. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52258. NO 7 NOVEMBER 12 NOVEMBER 7, 12
52259. NO 7 NOVEMBER 12 NOVEMBER 7, 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52260. NO 7 NOVEMBER 12 8 NOVEMBER 12
52261 NO 8 NOVEMBER 12 8 NOVEMBER 12
52262 NO 8 NOVEMBER 12 8 NOVEMBER 12
52263 NO 8 NOVEMBER 12 8 NOVEMBER 12
52264. NO 8 NOVEMBER 12 8 NOVEMBER 12
52265. NO 8 NOVEMBER 12 8 NOVEMBER 12
52266 NO 8 NOVEMBER 12 8 NOVEMBER 12
52267 NO 8 NOVEMBER 12 8 NOVEMBER 12
52268 NO 8 NOVEMBER 12 8 NOVEMBER 12
52269 NO 8 NOVEMBER 12 8 NOVEMBER 12
52270. NO 8 NOVEMBER 12 8 NOVEMBER 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52271 NO 8 NOVEMBER 12 8 NOVEMBER 12
52272 NO 8 NOVEMBER 12 8 NOVEMBER 12
52273 NO 8 NOVEMBER 12 8 NOVEMBER 12
52274 NO 8 NOVEMBER 12 8 NOVEMBER 12
52275 NO 8 NOVEMBER 12 8 NOVEMBER 12
52276 NO 8 NOVEMBER 12 8 NOVEMBER 12
52277 NO 8 NOVEMBER 12 8 NOVEMBER 12
52278. NO 8 NOVEMBER 12 8 NOVEMBER 12
52279 NO 8 NOVEMBER 12 8 NOVEMBER 12
52280 NO 8 NOVEMBER 12 8 NOVEMBER 12
52281 NO 8 NOVEMBER 12 8 NOVEMBER 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52282 NO 8 NOVEMBER 12 8 NOVEMBER 12
52283 NO 8 NOVEMBER 12 8 NOVEMBER 12
52284 NO 8 NOVEMBER 12 8 NOVEMBER 12
52285 NO 8 NOVEMBER 12 8 NOVEMBER 12
52286 NO 8 NOVEMBER 12 8 NOVEMBER 12
52287 NO 8 NOVEMBER 12 8 NOVEMBER 12
52288 NO 8 NOVEMBER 12 8 NOVEMBER 12
52289 NO 8 NOVEMBER 12 8 NOVEMBER 12
52290. NO 8 NOVEMBER 12 8 NOVEMBER 12
52291 NO 8 NOVEMBER 12 8 NOVEMBER 12
52292 NO 8 NOVEMBER 12 8 NOVEMBER 12

SEQUENCE # APP FIRST_TIM NEXT_TIME
---------- --- --------- ---------
52293 NO 8 NOVEMBER 12 8 NOVEMBER 12

Last thread last sequence received sequence applied difference
---------- ---------------------- --------------------- ----------
1 52293 52223 70

SQL > list of archive logs
Database log mode Archive Mode
Active AutoArchive
Destination of archive E:\oracle\P01\oraarch\P01arch
More old sequence of journal online 52291
Log sequence to archive 0
Current log sequence 52294
SQL > select process, status, sequence # from v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
ARCH. CLOSING 52292
ARCH. CLOSING 52293
ARCH. CLOSING 52289
ARCH. CLOSING 52290
ARCH. CLOSING 52291
MRP0 WAIT_FOR_LOG 52224
IDLE 52294 RFS
RFS IDLE 0
RFS IDLE 0
RFS IDLE 52224

MRP0 process is WAIT_FOR_LOG. I think that its hanging. Please let me know what I need to do in order to put the two secondary primary ad in sync.

Please let me know how to do it manually and what other options are available to me.

Thank you
Meena
Hello

So on the whole as a single sequence * 52224 * do not appear in the standby mode.
Let's see first if this sequence archive special is exist or not. It is exist and not transferred in standby mode, follow these steps

(1) stop MRP
(2) start MRP
(3) post 100 lines of the alert log file
If you gather any info from the main newspaper, then that's fine. And if there is no index using this script and post the output databases and relief.
http://www.Oracle-CKPT.com/dataguard_troubleshoot_snapper/

If there are no archives exist, try to restore backup if they are available. Is there a backup then you only option of differential rolls forward. Use link below.
http://www.Oracle-CKPT.com/RMAN-incremental-backups-to-roll-forward-a-physical-standby-database-2/

Thank you.

Move the data files on the standby server without moving primary Oracle 11 g r2

Hi all

Oracle 11g 2 with EBS 11.5.0.2 version.

The size of one of the mounting points on the standby is full and I'm going through one of the data files to another mount point without making any changes to the primary level.

I tried Google and came across this link:

http://oraclesea.blogspot.in/2011/12/move-datafiles-on-standby-server.html

But it did not work... I had to start the database with the spfile to work.

The steps mentioned in the blog:

Include below parameter in standby parameter file
DB_FILE_NAME_CONVERT = '/primary_location/xyz.dbf','/standby_location/xyz.dbf'
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE cancel;
shut immediate
startup nomount pfile=initSCSL.ora
alter database mount standby database ;
alter system set standby_file_management='MANUAL' SCOPE=MEMORY ; 
! cp /primary_location/xyz.dbf'  /standby_location/xyz.dbf
alter database rename file  '/primary_location/xyz.dbf' to '/standby_location/xyz.dbf';
alter system set standby_file_management='AUTO' SCOPE=MEMORY ; 
alter database recover managed standby database parallel 4 disconnect from session;

Can you please help me with the right steps...

Concerning
KK

Edited by: 903150 Sep 26, 2012 22:41

Here is an example for you.

Database pending:

SQL> select status,instance_name,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
OPEN         srprim           PHYSICAL STANDBY

SQL> select file_name from dba_data_files;

FILE_NAME
--------------------------------------------------------------------------------
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\USERS01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\UNDOTBS01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\SYSAUX01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\SYSTEM01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\USERS02.DBF

SQL> select process,status,sequence# from v$managed_standby;

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                154
MRP0      WAIT_FOR_LOG        154

7 rows selected.

SQL> show parameter name_convert

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_file_name_convert                 string
log_file_name_convert                string
SQL> alter database recover managed standby database cancel;

Database altered.

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

M:\>copy C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\USERS02.DBF C:\APP\SHIVANANDA.RAO\ORADATA\DBTEST\USERS02.DBF
1 file(s) copied.

M:\>sqlplus sys/oracle@srprim as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Thu Sep 27 14:57:16 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup mount
ORACLE instance started.

Total System Global Area  778387456 bytes
Fixed Size                  1374808 bytes
Variable Size             494929320 bytes
Database Buffers          276824064 bytes
Redo Buffers                5259264 bytes
Database mounted.
SQL> alter system set standby_file_management=manual;

System altered.

SQL> alter database rename file 'C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\USERS02.DBF' to 'C:\APP\SHIVANANDA.RAO\ORADA
A\DBTEST\USERS02.DBF';

Database altered.

SQL> alter database recover managed standby database disconnect from session;

Database altered.

SQL> select process,status,sequence# from v$managed_standby;

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                155
MRP0      WAIT_FOR_LOG        155

7 rows selected.

SQL> select name from v$datafile;

NAME
--------------------------------------------------
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\SYSTEM01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\SYSAUX01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\UNDOTBS01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\SRPRIM\USERS01.DBF
C:\APP\SHIVANANDA.RAO\ORADATA\DBTEST\USERS02.DBF

1. you must close the database pending.
2 copy the file that you want to move to the different mount point using the OS commands.
3. Mount the standby database.
4 rename the data through database level. Make sure that the standby_file_management is set to MANUAL
5. start the MRP on the standby database.

Please do not use more than one response to the thread ID. Because you created this thread with ID 903150, I propose to answer with the same ID, not the ID of the other.

ORA-01153: an incompatible media recovery is active

Hello

the eve of ments is created (11.1.0.7), time real usng apply.

go to the eve of the database:

SQL > select flashback_on from database v$.

FLASHBACK_ON
------------------
NO.

SQL > alter flashback database;
change the flashback of the database on
*
ERROR on line 1:
ORA-01153: an incompatible media recovery is active

question here:

1. If I use flashback in a database of pending?

2. If so, how can I turn it on?

Thank you
951932

Yes, you can do it. But to allow the return of flame, you must have your database in editing mode.

Example:

SQL> select max(sequence#) from v$archived_log where applied='YES';

MAX(SEQUENCE#)
--------------
546

SQL>
SQL> alter database recover managed standby database cancel;

Database altered.

SQL> alter system set db_flashback_retention_target=1440;

System altered.

SQL>
SQL> alter database flashback on;

Database altered.

SQL> alter database recover managed standby database disconnect from session using current logfile;

Database altered.

SQL> select process,status,sequence# from v$managed_standby;

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CLOSING             545
MRP0      APPLYING_LOG        547
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE                547
RFS       IDLE                  0

9 rows selected.

Database broker and dataguard Creaton of Eve
Hi Experts,

I use Linux with Oracle version 11 GR 2. We have plans to create a database of physical intelligence and also configure dataguard broker for the standby database.
Also, I read the documents that active dataguard is a feature on 11g. It is not possible on 10g?

Can someone give me please the steps to create the standby database and configure the dataguard broker.
Hello

Check this thread DR synchronize with primary

Also, to check whether or not the managed recovery is underway on the standby database, run the following query:

SQL > select process, status, sequence # from v$ managed_standby;

If process columns is a value such as MRP, then the managed recovery is underway on the standby database.

Hope this is clear.

1 disk of the DSO has been deleted by SA, now restored standby db, but she received the error
I need to restore our database pending since the last backup and bootable media and now when I try to open read-only, it keep saying East of the database for read and write.

and when I do the following question, it shows:
Select the process, status, sequence # v$ managed_standbySQL > SQL >;

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
ARCH. CLOSING 18768
ARCH. CLOSING 18769
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
RFS IDLE 0
RFS IDLE 0
RFS IDLE 0

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
RFS IDLE 0
RFS IDLE 0
RFS IDLE 18770
RFS IDLE 0
RFS IDLE 0

38 selected lines.

Seems no mrp0 process and rfs is inactive.

Needing urgent help, I can't sort of thinking now, because since last night very late and all day today.
Thank you
Hello;

I'm glad to hear that this had to be a ton of work.

Q: IS the orapw file already in the dbs folder? Yes, otherwise Data Guard would never work.

Q: why the tns-12514 error? It makes no sense to me. Are the names of the same patterns if yes how to delete and recreate. Is there any change this process affects the SYS schema?

Made curious password for Data Guard

Not only Data Guard requires a password file, but it also expects SYS to grant SYSDBA role.

Data Guard searches the password in $ORACLE / dbs (OK, not so strange).

V$ pwfile_users can provide a clue as to your question.

Password file works different in Oracle 11 Oracle Data Guard 10.

In Oracle 11 as the REDO_TRANSPORT_USER parameter can be used to select one different user SYS to authenticate redo them transport sessions. This user must have the SYSOPER privilege.

In the CARS for the primary and Standby, check the time stamps of all files on password and copy it later to all nodes.

In Oracle 11, you can create is no longer simply a new password for the database file physical standby. You must still copy the password of database primary in all physical databases ensures whenever a password for privileged user is changed (I wonder if she's?)

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

When we tell you how large your database was the first thought in my head was (Wow she must have its own weather system), but I could say out loud because of the pain he was causing to you at this time.

Best regards

mseberg

Edited by: mseberg January 6, 2012 18:18

ARCHIVELOG apply very slow to the backup site
I did a refresh of the data on the production site, then after the import is done, I found the file in the sync backup site password. After I synchronize files password on the two prod and Eve, Eve archivelog apply has been long out of sync.

Now get going, but it's very very slow. I don't think it's good. Here's some data:

Production:

SQL > SELECT
NAME IN STANDBY MODE,
SEQUENCE #.
APPLIED,
COMPLETION_TIME
Of
V$ ARCHIVED_LOG
WHERE
DEST_ID = 2
AND
NEXT_TIME > SYSDATE-1; 2 3 4 5 6 7 8 9 10 11

STANDBY SEQUENCE # APPLIED CAPS
-------------------- ---------- ---------- ---------
hysdev 18693 No. 2 January 12
hysdev 18696 No. 2 January 12
hysdev 18697 No. 2 January 12
hysdev 18698 No. 2 January 12
hysdev 18699 No. 2 January 12
hysdev 18700 No. 2 January 12
hysdev 18701 No. 2 January 12
hysdev 18702 No. 2 January 12
hysdev 18703 No. 3 January 12
hysdev 18704 No. 3 January 12
hysdev 18705 No. 3 January 12

STANDBY SEQUENCE # APPLIED CAPS
-------------------- ---------- ---------- ---------
hysdev 18706 No. 3 January 12
hysdev 18707 No. 3 January 12
hysdev 18708 No. 3 January 12
hysdev 18709 No. 3 January 12
hysdev 18710 No. 3 January 12

16 selected lines.

SQL > SELECT
MAX(SEQUENCE#)
Of
V$ ARCHIVED_LOG
WHERE
NEXT_TIME > SYSDATE-1;
2 3 4 5 6
MAX(SEQUENCE#)
--------------
18710

SQL > select thread #, max(sequence#) in Group v$ archived_log by thread #;

THREAD # MAX(SEQUENCE#)
---------- --------------
1 18710

SQL > select name, floor (space_limit/1024/1024) "Size MB", ceil (space_used/1024/1024) "used MB.
v $ recovery_file_dest
by name
2 3 4
SQL > /.

NAME
----------------------------------------------------------------------------------------------------
Size used Mo Mo
---------- ----------
+ HY_FRA
368640 367839

SQL > SQL > select ds.dest_id id
2, ad.status
ds.database_mode db_mode
3 4, type ad.archiver
5, ds.recovery_mode
6, ds.protection_mode
DS.standby_logfile_count 7, "litigants".
8, active ds.standby_logfile_active
9, ds.archived_seq #.
10 v $ archive_dest_status ds
, announcement of v$ archive_dest
where ds.dest_id = ad.dest_id
11 12 13 and ad.status! = 'INACTIVE '.
14 order by
15 ds.dest_id
16.

ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE
---------- --------- --------------- ---------- ----------------------- --------------------
SRls ASSETS ARCHIVED_SEQ #.
---------- ---------- -------------
1 VALID INACTIVE OPEN ARC MAXIMUM PERFORMANCE
0 0 18710

2 VALID LGWR OPEN_READ MANAGED AT THE TIME ONLY ONE REAL IS APPLIES TO MAXIMUM PERFORMANCE
8 2 16851

standby:
SQL > select process, status, sequence # from v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
ARCH. CLOSING 18703
ARCH. CLOSING 18704
ARCH. CLOSING 18705
ARCH. CLOSING 18706
ARCH. CLOSING 18707
ARCH. CLOSING 18708
ARCH. CLOSING 18709
ARCH. CLOSING 18710

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
CONNECTED ARCH 0
RFS RECEIVING 16852
RFS RECEIVING 16869
RFS RECEIVING 16863

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
RFS RECEIVING 16860
RFS RECEIVING 16872
RFS RECEIVING 16862
RFS RECEIVING 16878
RFS RECEIVING 16853
RFS RECEIVING 16866
RFS RECEIVING 16868
RFS RECEIVING 16876
RFS RECEIVING 16856
RFS RECEIVING 16877
RFS RECEIVING 16858

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
RFS RECEIVING 16874
RFS RECEIVING 16871
RFS RECEIVING 16870
RFS RECEIVING 16879
RFS RECEIVING 16855
RFS RECEIVING 16859
RFS IDLE 18711
RFS RECEIVING 16873
RFS RECEIVING 16861
RFS RECEIVING 16875
RFS RECEIVING 16857

STATUS OF PROCESS SEQUENCE #.
--------- ------------ ----------
RFS RECEIVING 16867
RFS RECEIVING 16865
RFS RECEIVING 16864
RFS RECEIVING 16880
RFS RECEIVING 16854
MRP0 WAIT_FOR_LOG 16852

61 selected lines.

SQL > select thread #, max(sequence#) from v$ archived_log in case of application = 'YES' group by thread #;

THREAD # MAX(SEQUENCE#)
---------- --------------
1 16851

SQL > select ds.dest_id id
2, ad.status
3, ds.database_mode db_mode
4, type ad.archiver
5, ds.recovery_mode
6, ds.protection_mode
DS.standby_logfile_count 7, "litigants".
8, active ds.standby_logfile_active
9, ds.archived_seq #.
10 v $ archive_dest_status ds
11, v$ archive_dest ad
12 where ds.dest_id = ad.dest_id
13 and ad.status! = 'INACTIVE '.
14 order by
15 ds.dest_id
16.

ID STATUS DB_MODE TYPE RECOVERY_MODE
---------- --------- --------------- ---------- -----------------------
LAR ACTIVE ARCHIVED_SEQ PROTECTION_MODE #.
-------------------- ---------- ---------- -------------
APPLY 1 VALID OPEN_READ ONLY MANAGED AT THE TIME VAULT REAL
0 0 18710 MAXIMUM PERFORMANCE

2 LGWR INACTIVE VALID UNKNOWN
MAXIMUM PERFORMANCE 0 0 0

32 INACTIVE VALID UNKNOWN ARCH
0 0 16851 MAXIMUM PERFORMANCE

SQL > SQL > home
Oracle@oracle01[home/Oracle]hysdev$ ps - ef | grep mrp
Oracle 20660 1 0 00:27? 00:00:00 ora_mrp0_hysdev

Last night the archivelog applied was a sequence 15100, this morning, it was 16851, which is extremely slow.

dgmgrl results:
DGMGRL > see the hysdev database

Database - hysdev

Role: STANDBY PHYSICS
State of destination: apply
Delay of transport: 1 day (s) 4 hours, 40 minutes and 52 seconds
Apply the Lag: 1 day (s 4 hours, 40 minutes and 53 seconds)
Real-time query: WE
Occurrence (s):
hysdev

State of the database:
SUCCESS

I do not understand why it is so slow and I wonder if the archivelogs are ignored? or is the area FRA prod is nearly full?

Help, please. Thanks in advance.
874437 wrote:
Thank you and msberg much, you guys always there when I need help. You both deserve a metal.

I'll watch the newspaper generate rates and I hope next time I can do better.

Thanks again for your time and your contribution.

Please close the thread, so that significant as she answered.

Mseberg contribution was great again.

Published by: CKPT on January 4, 2012 09:05

Doubt RMAN for recovey
Hello

I'm learing RMAN and beginner in this area. I have a doubt for recovey db.
I took hotbackup full db using controlfile deposit of GR 11, 2 db. Then I restored it on the same host, directory structure has also been even during the restoration restore n as it was during the backup.

Safeguard measures:
RMAN > configure redundancy 2 retention policy;
RMAN > set the parallelism of peripheral disc type 2;
RMAN > configure channel device type disk format ' / home/oracle/rman_backup/ora_df%t_b%s_p%p';
RMAN > configure controlfile autobackup on;
RMAN > configure CONTROLFILE AUTOBACKUP peripheral type disc format in ' / home/oracle/rman_backup/ora_cf%F';
RMAN > set up optimization backup;
RMAN > show all.
RMAN > backup the database archivelog;

Restore and refresh as follows:

*. On SQLPLUS, stop immediately
*. Remove all the data files, redo logs, control files, newspapers archived (of the oradata and flashback area)
*. On the RMAN command prompt:
1 RMAN > startup nomount;
2 RMAN > restore controlfile to ' / home/oracle/rman_backup/ora_cfc-4124714611-20110510-00';
3 RMAN > change the editing of the database;
4 RMAN > restore database;
5 RMAN > backup from the list of the archivelog all;
6 RMAN > recover database until sequence 6.
7 RMAN > alter database open resetlogs;

On the SQL command prompt:

8. SQL > select group # first_change #, status, sequence #, archived log v$. (this step was performed before you recover the database, that is to say prior to step 6)

GROUP # FIRST_CHANGE # STATUS # ARC SEQUENCE

1 962626 YES 4 INACTIVE
3 979898 6 CURRENT NO.
*2 979836 ACTIVE 5 YES*

Since up to SEQ 5 only, archives were present at the start, I got db up to seq 5, but RMAN showed following error:*.

RMAN > recover database until the sequence 5.

From pick up to 22 May 11
using channel ORA_DISK_1
using the ORA_DISK_2 channel
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 22/05/2011 22:36:21
RMAN-06556: datafile 1 must be restored from a backup that is older than SNA 979836

Then I cleaned new system and gave 6 SEQ next time during recovery as it is the highest seq, but since archivelog to seq 6 is not present or redo logs are present (as far as my backup rman understanding isn't back ups redo logs and I had deleted previous recovery of host newspapers before starting the recovery and restoration) , then how is the recovery completed successfully? +

Here are the steps of restoration and recovery with o/p for your reference:

target [oracle@purnima 112_db] $ rman.

Recovery Manager: release 11.2.0.1.0 - Production Wednesday, may 25, 22:19:49 2011

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

connected to the database target (not started)

1 RMAN > startup nomount;

Oracle instance started

Total System Global Area 619360256 bytes

Bytes of size 1338280 fixed
427820120 variable size bytes
184549376 of database buffers bytes
Redo buffers 5652480 bytes

2 RMAN > restore controlfile to ' / home/oracle/rman_backup/ora_cfc-4124714611-20110510-00';

From restoration to 25 May 11
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 19 type of device = DISK

channel ORA_DISK_1: restore the control file
channel ORA_DISK_1: restore complete, duration: 00:00:04
output file name=/home/oracle/112_db/oradata/honey/control01.ctl
output file name=/home/oracle/112_db/flash_recovery_area/honey/control02.ctl
Finished restoring to May 25, 11

3 RMAN > change the editing of the database;

mounted database
output channel: ORA_DISK_1

RMAN > show all.

Database with db_unique_name HONEY RMAN configuration parameters are:
CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / home/oracle/rman_backup/ora_cf%F';
SET UP THE DEVICE TYPE DISK PARALLELISM 2 TYPE OF BACKUP BACKUPSET.
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / home/oracle/rman_backup/ora_df%t_b%s_p%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / home/oracle/112_db/product/11.2.0/dbhome/dbs/snapcf_honey.f'; # by default

4 RMAN > restore database;

From restoration to 25 May 11
From implicit overlapping backup 25 May 11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 20 type of device = DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID = 21 type of device = DISK
Intersected 4 objects
Cut 3 objects
Finished the backup implicit intersection to 25 May 11

Starting copy of implicit intersection to 25 May 11
using channel ORA_DISK_1
using the ORA_DISK_2 channel
Copy of implicit overlap finished on 25 May 11

the search for all files in the recovery area
cataloging files...
not cataloged files

using channel ORA_DISK_1
using the ORA_DISK_2 channel

channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_DISK_1: restore datafile 00002 to /home/oracle/112_db/oradata/honey/sysaux01.dbf
channel ORA_DISK_1: restore datafile 00003 to /home/oracle/112_db/oradata/honey/undotbs01.dbf
channel ORA_DISK_1: restore datafile 00005 to /home/oracle/112_db/oradata/honey/example01.dbf
channel ORA_DISK_1: reading of the backup/home/oracle/rman_backup/ora_df750773827_b15_p1 element
channel ORA_DISK_2: from the restore backup set data file
channel ORA_DISK_2: specifying datafile (s) to restore from backup set
channel ORA_DISK_2: restore datafile 00001 to /home/oracle/112_db/oradata/honey/system01.dbf
channel ORA_DISK_2: restore datafile 00004 in /home/oracle/112_db/oradata/honey/users01.dbf
channel ORA_DISK_2: reading of the backup/home/oracle/rman_backup/ora_df750773827_b14_p1 element
channel ORA_DISK_1: piece handle = / home/oracle/rman_backup/ora_df750773827_b15_p1 tag = TAG20110510T121707
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:01:17
channel ORA_DISK_2: piece handle = / home/oracle/rman_backup/ora_df750773827_b14_p1 tag = TAG20110510T121707
channel ORA_DISK_2: restored the backup part 1
channel ORA_DISK_2: restoration complete, duration: 00:01:18
Finished restoring to May 25, 11

5 RMAN > backup from the list of the archivelog all;

List of backup sets
===================

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
16,29 6 M DISK 00:00:01 MAY 10, 11
BP key: 6 location: AVAILABLE Tablet: NO Tag: TAG20110510T121703
Item name: / home/oracle/rman_backup/ora_df750773823_b13_p1

List of newspapers archived on backup the value 6
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 4 962626 10 MAY 11 979836 10 MAY 11

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
22.50 9 K DISK 00:00:00 10 MAY 11
BP key: 9 situation: AVAILABLE Tablet: NO Tag: TAG20110510T121834
Item name: / home/oracle/rman_backup/ora_df750773914_b16_p1

List of newspapers archived on backup value 9
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 5 979836 10 MAY 11 979898 10 MAY 11

6 RMAN > recover database until sequence 6.

Starting recover at 25 May 11
using channel ORA_DISK_1
using the ORA_DISK_2 channel

starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archives Journal
Archives journal thread = 1 = 5 sequence
channel ORA_DISK_1: reading of the backup/home/oracle/rman_backup/ora_df750773914_b16_p1 element
channel ORA_DISK_1: piece handle = / home/oracle/rman_backup/ora_df750773914_b16_p1 tag = TAG20110510T121834
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:00:01
Archive log file name=/home/oracle/112_db/flash_recovery_area/HONEY/archivelog/2011_05_25/o1_mf_1_5_6xtfgqc6_.arc thread = 1 = 5 sequence
default channel: archived deletion or newspapers
RECID = STAMP 16 = 752106671 name=/home/oracle/112_db/flash_recovery_area/HONEY/archivelog/2011_05_25/o1_mf_1_5_6xtfgqc6_.arc archived log file
media recovery complete, duration: 00:00:01
Finished recover at 25 May 11

7 RMAN > alter database open resetlogs;

open database

8 RMAN > exit

Kind regards
Purnima Johari
I have no onlinelogs on the host. I deleted all the log files from the flash and oradata recovery area before you begin the process of restoration and recovery on the host (.dbf, .log, .ctl). When I tried with "database recovery command", he gave following error (it's just the excerpt from o/p):

Ah - yes: If you remove the onlinelogs then you receive the above error because a newspaper archive does not yet exist and the onlinelog with sequence 6 is missing too.

>

So you mean if we use up to clause with database recovery command, it always runs recovery up to n - 1. So imagine a scenario where all newspapers of recovery have been archived, if highest till SEQ that checked is generated is N, then to until I give SEQ N + 1 as up to execute it 'N' no time. Right?

It's just too. It goes same for the RCS. If you want to recover to the last SNA in a specific archivelog, you can query the column NEXT_CHANGE # of v$ archived_log , then you will run 'restore database until the SNA... "and give the RCS of NEXT_CHANGE #-because it will recover to NEXT_CHANGE #-1.

See you soon
Jörg

Passfail status sequence

Similar Questions

Maybe you are looking for