DataGuard archiving logs go?

Hi all

OEL5

I'm following the dataguard configuration document.

One of the tasks is to run:

RMAN > backup filesperset remove all 10 ArchiveLog entry;

He created an output file > piece handle = / p01/oradata/PROD/dbs/06dlfmmt_1_1

Can it remove the archive logs.

My problem is, I want to still manually restore another set of database for replication so I still need that archive logs to be applied to this database 2 (non-dataguard).

Can I use this backup of archive logs merged to manually apply on my second instance?

Thank you very much

Yes, controlfile of today can be used for backup of database of yesterday. However, if you have added new data files or tablespaces from backup, they would be reflected in the controlfile but not in the backup.

Hemant K Collette

Tags: Database

Similar Questions

DataGuard archiving log not applied
Hello

I met archive log apply errors in the physical standby database. Below are the errors.

SQL > SELECT SEQUENCE #, FIRST_TIME, NEXT_TIME, APPLIED from V$ ARCHIVED_LOG SEQUENCE ORDER #;

SEQUENCE # FIRST_TIM NEXT_TIME APP
---------- --------- --------- ---
10 24 AUGUST 11 NO. 24 AUG 11
10 24 AUGUST 11 NO. 24 AUG 11
11 AUGUST 24, 11 NO. 24 AUG 11
12 24 AUGUST 11 NO. 25 AUG 11
13 25 AUGUST 11 NO. 25 AUG 11
14-25 AUGUST 11 NO. 25 AUG 11

6 selected lines.

SQL > select database_role, open_mode from v$ database;

DATABASE_ROLE OPEN_MODE
---------------- ----------
FIRST READING WRITING

SQL > select message from v$ dataguard_status;

ARCs: Started archiving
CRAT: Started archiving
CJACBR: become the "no FAL' ARCH
CJACBR: become the "no SRL" ARCH
ARCm: Become the heartbeat ARCH

Message
--------------------------------------------------------------------------------
Again shipping customer logged in as PUBLIC
-User is valid
RFS [1]: assigned to the RFS 3389 process
RFS [1]: do not use real application clusters
LGWR: Error 16009 creation archivelog file "DBSOURCE.
LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
Again shipping customer logged in as PUBLIC
-User is valid
RFS [2]: assigned to the RFS 3393 process
RFS [2]: do not use real application clusters
FAL [server, ARCo]: error 16009 file creation remote archivelog 'DBSOURCE.

Message
--------------------------------------------------------------------------------
Again shipping customer logged in as PUBLIC
-User is valid
RFS [3]: assigned to the RFS 3397 process
RFS [3]: do not use real application clusters
Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.
Again shipping customer logged in as PUBLIC
-User is valid
RFS [4]: assigned to the RFS 3429 process
RFS [4]: do not use real application clusters
Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.

54 selected lines.

Of the primary alerts on DB log errors
Using the default value for the parameter STANDBY_ARCHIVE_DEST as/u01/app/oracle/oradata/DBSOURCE
Again shipping customer logged in as PUBLIC
-User is valid
RFS [1]: assigned to the RFS 3389 process
RFS [1]: do not use real application clusters
Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3389.trc file:
ORA-16009: destination of the journal archive remote must be a database of the EVE
Game Aug 25 12:17:10 2011
Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_lns1_3349.trc file:
ORA-16009: destination of the journal archive remote must be a database of the EVE
LGWR: Error 16009 creation archivelog file "DBSOURCE.
LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
Game Aug 25 12:17:30 2011
Again shipping customer logged in as PUBLIC
-User is valid
RFS [2]: assigned to the RFS 3393 process
RFS [2]: do not use real application clusters
Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3393.trc file:
ORA-16009: destination of the journal archive remote must be a database of the EVE

initDBSOURCE.ora params
DB_NAME = DBSOURCE
DB_UNIQUE_NAME = DBSOURCE
LOG_ARCHIVE_CONFIG = 'DG_CONFIG = (DBSOURCE, DBTARGET)'
LOG_ARCHIVE_DEST_1 =
"LOCATION = / u01/app/oracle/oradata/DBSOURCE"
VALID_FOR = (ALL_LOGFILES, ALL_ROLES)
DB_UNIQUE_NAME = DBSOURCE'
LOG_ARCHIVE_DEST_2 =
"SERVICE = DBSOURCE LGWR ASYNC
VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE)
DB_UNIQUE_NAME = DBTARGET'
LOG_ARCHIVE_DEST_STATE_1 = ENABLE
LOG_ARCHIVE_DEST_STATE_2 = ENABLE
REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE LOCK
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES = 30

I have 1 more question. I copied all db files, control files, and archived logs of the remote db DBTARGET but with the standby control file I could mount the db in the remote server but the dbname is always DBSOURCE instead of DBTARGET.

I tried running NEST to change on the site of relief the dbname but it errored out with
Copyright (c) 1982, 2007, Oracle. All rights reserved.

Connected to database DBSOURCE (DBID = 977273159)

NEST-00131: control file is not current

Change of database name failed during validation - database is intact.

Could if apply the newspaper ceased due to the DBNAME is the same on the eve of primary and physical please help

Edited by: 880215 August 25, 2011 10:02
```
dbname is still DBSOURCE instead of DBTARGET
```
The database must be DBSOURCE on both. It's the same data in two different roles, role PRINCIPAL and ROLE of the day BEFORE.

Oracle, said by the DB_UNIQUE_NAME parameter.

What I have is copy the control file before on the basis of pending data down and then copy and rename the control file that are there.

Does make sense?

I have some notes here if it helps:

http://www.Visi.com/~mseberg/data_guard_on_oracle_11_step_by_step.html

Best regards

mseberg

DataGuard slowed db: generating the archive logs?

Hello
I have a 11.2.0.4 db using Data Guard to play with. I just set up and could do a failover and vice versa.
However I have noticed there are great number of generated archive logs, one every minute. As it is an empty database, I wonder why?
No recovery is generated by sessions:
Select v$ session.sid, username, value/1024/1024 redo_size_MB
v $ sesstat, v$ statname of v$ session
where v$ sesstat. STATISTICS of # = v$ statname. STATISTICS FROM #.
and v$ v = session.sid $sesstat.sid
and name = "redo size."
and > 0
and username is not null
2 3 4 5 6 7 8 value order;
no selected line
Logs are generated on the disc:
-rw - r - 1 oracle oinstall K 77, 30 Nov 12:06 o1_mf_1_1119_c5rcg7b1_.arc
-rw - r - 1 oracle oinstall 35K 30 Nov 12:07 o1_mf_1_1120_c5rcj3gh_.arc
-rw - r - 1 oracle oinstall 103K 30 Nov 12:08 o1_mf_1_1121_c5rckzo0_.arc
-rw - r - 1 oracle oinstall 36K 30 Nov 12:09 o1_mf_1_1122_c5rcmvo2_.arc
-rw - r - 1 oracle oinstall 35K 30 Nov 12:10 o1_mf_1_1123_c5rcoqry_.arc
-rw - r - 1 oracle oinstall 35K 30 Nov 12:11 o1_mf_1_1124_c5rcqmxm_.arc
-rw - r - 1 oracle oinstall 35K 30 Nov 12:12 o1_mf_1_1125_c5rcsj2j_.arc
-rw - r - 1 oracle oinstall 35K 30 Nov 12:13 o1_mf_1_1126_c5rcvd3t_.arc
Someone has an idea of what to check?
Concerning
3

Something abnormal. If this a test box, are you allowed to bounce the DB?

If so, give it a shot and try.

-Jonathan Rolland

Data Guard - RMAN removing archive log

Hello
I ' v DataGuard with physical standby.
I do a backup only on the primaries. Both sites have ther separate backup systems.
I ' v FRA and configured archivelog deletion with RMAN configuration:
on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;
It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?
1 should I reconfigure RMAN?
change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;
2. make full backup

Hello

1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

section: "all archived Redo Log deletion policy."

Document provides the best algorithm to analysis of work

You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

It will be useful.

-Thank you

Pavan Kumar N

When ALTER SYSTEM ARCHIVE LOG happens implicitly...
Hello

When you scan the v$ archived_log SIDE primary SCHOOL, I saw below output

NAME OF CREATOR REGISTR SEQUENCE # FAL
-------------------------- ------- ------------ ----------------- ---
/U05/prod/archivelogs/ARC_816992406_1_22885.dbf ARCH ARCH 22885 No.
/U05/prod/archivelogs/ARC_816992406_1_22886.dbf FGRD FGRD 22886 No.

Then I went to the alert log file and search for the sequence #, I found that

When the newspaper switch happens through * ALTER SYSTEM ARCHIVE LOG *, then this sequence archive log CREATOR and REGISTRAR will be FGRD.
What command of newspaper happens automatically (90% complete log file), then this sequence archive log CREATOR and REGISTRAR will be ARCH.

If * ALTER SYSTEM ARCHIVE LOG * happens synchronously means control will not return to the process unless and until the underlying log file has been
archived completely, so the CREATOR and the REGISTRAR is FGRD.

My question is, under what circumstances * ALTER SYSTEM ARCHIVE LOG * happen implicitly.

Thank you
Hello

user9085814 wrote:
Thanks for the reply...

I agree with you.

The environment that I take abt is DATAGUARD Enviornment.

I have not published ALTER SYSTEM ARCHIVE LOG CURRENT of any session (foreground process) of the primary DB.
But I can still see ALTER SYSTEM ARCHIVE LOG in the log to alter.

When you call the command ALTER SYSTEM ARCHIVE LOG CURRENT , then oracle write in the journal of the alerts as:

On primary
```
 Wed May 15 09:16:56 2013
 Archived Log entry 789 added for thread 1 sequence 396 ID 0xf23a6e3f dest 1:
 *ALTER SYSTEM ARCHIVE LOG*
 Thread 1 cannot allocate new log, sequence 398
```
>

So my question on what scenario ALTER SYSTEM ARCHIVE LOG will be captured in the log of alerts.
because it's a mistake to run foreground process ALTER SYSTEM ARCHIVE LOG .

Have you had a logs archived backup RMAN script which is called ALTER SYSTEM ARCHIVE LOG CURRENT
```
 RMAN> run
           {
              sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
              backup  archivelog all delete all input;
           }
```
If you try the command ALTER SYSTEM ARCHIVE LOG CURRENT on stanby, you get error ORA-01109: database is not open. This means database is not open READ/WRITE mode.
Then we can use ALTER SYSTEM ARCHIVE LOG CURRENT on the standby database.

Thanks for the interesting thread
Mr. Mahir Quluzade
http://www.Mahir-quluzade.com

Secondary destination for archived logs
Version: 10.2, 11.1, 11.2

Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?

I think that LOG_ARCHIVE_DEST_2 is reserved for archiving to Dataguard standby DB logs in which specify you the day before tns input using the parameter of the shipping SERVICE.

Can I specify LOG_ARCHIVE_DEST_3 as my secondary site in case LOG_ARCHIVE_DEST_1 saturates? -What is LOG_ARCHIVE_DEST_n meant for? Even though the documentation says that you can have up to 10 locations, I'm confused, if they are intended to store copies of archive logs multiplex? This is not what I'm looking for?
>

Hi Tom,

Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How
can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?

From [https://forums.oracle.com/forums/thread.jspa?threadID=1033460 url] here:

LOG_ARCHIVE_DEST_STATE_n = ALTERNATE
To specify the nth destination metnioned in the LOG_ARCHIVE_DEST_n as a destination alternative.

Look at "replacement" [url http://docs.oracle.com/cd/E14072_01/server.112/e10595/archredo004.htm] here - if all else fails, read the docco ;)

Also check out here [url http://docs.oracle.com/cd/B10501_01/server.920/a96521/archredo.htm].
HTH,

Paul...

With RMAN for backup, but not with the archive logs
We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.

Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.

My question is around logs archiving and RMAN.
Our current situation is:
-We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
-We set the archive_lag_target so archiving logs is produced every 30 minutes.
-a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
-daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.

I'm interested in feedback as to if our strategy around archiving logs is correct or not.

Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.

Curious to know what others are doing.
Hello

Welcome to OTN!

Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

On the disk space, you can delete the archives once they were saved by RMAN.

RMAN > delete any backup archivelog entry;

This supports the archivelogs and then remove the archives from the disk.

If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

RMAN > configure archivelog political of deletion to applied pending;

Manually apply archive logs waiting

RDBMS Version: 11.2.0.4
OS: RHEL 6.6
As I understand it, if I want to manually apply archive logs, I do the 2 steps.
But, how can I do watch DB to accept (add it as part of the eve DB) logs archiving transferred manually?
That is to say. How can force you standby DB to add these archiving logs to its control file?
Step 1. First stop the current recovery process (MRP) as
ALTER database recover managed standby database cancel;
Then transfer must all logs archiving of primary school next door waiting and apply manually using below command.
Step 2. recover a database on hold until cancel;

Hello

To do this manually, you must:

(a) manually transfer logs archived redo of primary site on backup site

(b) lets say to the backup site, you have this path ' / archives/database / ' and in this way, there are the archived redo logs

Then, in the backup site, you must catalog the logs archived redo with RMAN

RMAN > CATALOGUE START WITH "/ archives/database /";

(c) Once catalogued recovery logs archived, you can start the recovery media

change recover managed standby database disconnect log file using current;

or

ALTER database recover managed standby database disconnect;

(d) monitor the alerts log to see if this transferred manually and asking unregistered archived redo logs

Kind regards

Juan M

Problem with the archive log when you use RMAN for backup and restore (11g 2)

Hello world
Please help me solve this problem.
I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
-First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
run{ allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ; backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile; backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input; crosscheck archivelog all; crosscheck backup; delete noprompt obsolete; release channel bkp; }

D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:
run{ allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ; backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile; backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input; crosscheck archivelog all; crosscheck backup; delete noprompt obsolete; release channel bkp; }
Repeat 7 times (Monday-> Saturday). And I got these files:
[oracle@rac ~]$ ls -l /u01/backup/ total 400280 -rw-r----- 1 oracle oinstall 10158080 Jan 20 07:23 c-1428943247-20160120-01 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:04 c-1428943247-20160120-02 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:05 c-1428943247-20160120-03 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:06 c-1428943247-20160120-04 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-05 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-06 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:09 c-1428943247-20160120-07 -rw-r----- 1 oracle oinstall 10158080 Jan 20 08:32 c-1428943247-20160120-08 -rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1 -rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1 -rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1 -rw-r----- 1 oracle oinstall 11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1 -rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1 -rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1 -rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1 -rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1 -rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1 -rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1 -rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1 -rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1 -rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1 -rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1 -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1 -rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1 -rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1
And
RMAN> list backup summary; List of Backups =============== Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 80      B 0 A DISK        20-JAN-16       1       1       YES        DB_FULL 81      B 0 A DISK        20-JAN-16       1       1       YES        DB_FULL 82      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL 83      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL 84      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL 85      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T072332 86      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 87      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 88      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 89      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080440 90      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 91      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 92      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 93      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080545 94      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 95      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 96      B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 97      B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080657 98      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 99      B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 100     B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 101     B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080801 102     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 103     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 104     B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC 105     B F A DISK        20-JAN-16       1       1       NO         TAG20160120T080844 106     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 107     B 1 A DISK        20-JAN-16       1       1       YES        DB_INC 108     B A A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
My configuration of rman:
RMAN> show all; RMAN configuration parameters for database with db_unique_name ORCL are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F'; CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p'; CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default
- Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here. RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08'; Starting restore at 20-JAN-16 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=18 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=20 device type=DISK channel ORA_DISK_2: skipped, AUTOBACKUP already found channel ORA_DISK_1: restoring control file channel ORA_DISK_1: restore complete, elapsed time: 00:00:09 output file name=/u01/app/oracle/oradata/orcl/control01.ctl output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl Finished restore at 20-JAN-16 RMAN> alter database mount; database mounted released channel: ORA_DISK_1 released channel: ORA_DISK_2 RMAN> restore database; Starting restore at 20-JAN-16 Starting implicit crosscheck backup at 20-JAN-16 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=20 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=18 device type=DISK Crosschecked 29 objects Finished implicit crosscheck backup at 20-JAN-16 Starting implicit crosscheck copy at 20-JAN-16 using channel ORA_DISK_1 using channel ORA_DISK_2 Finished implicit crosscheck copy at 20-JAN-16 searching for all files in the recovery area cataloging files... no files cataloged using channel ORA_DISK_1 using channel ORA_DISK_2 channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1 channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:01:15 Finished restore at 20-JAN-16
-Fourth, the problem here, I got the database; .. .every oky until this line... starting media recovery channel ORA_DISK_1: starting archived log restore to default destination channel ORA_DISK_1: restoring archived log archived log thread=1 sequence=15 channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1 channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15 unable to find archived log archived log thread=1 sequence=1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 01/20/2016 08:50:22 RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841 The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?) RMAN> list backup of archivelog all; List of Backup Sets =================== BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 82      2.16M      DISK        00:00:00     20-JAN-16              BP Key: 82   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL         Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1 List of Archived Logs in backup set 82 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    1       1154833    20-JAN-16 1177422    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 83      3.88M      DISK        00:00:00     20-JAN-16              BP Key: 83   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL         Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1 List of Archived Logs in backup set 83 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    1       1162729    20-JAN-16 1188784    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 84      10.68M     DISK        00:00:01     20-JAN-16              BP Key: 84   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL         Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1 List of Archived Logs in backup set 84 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    2       1177422    20-JAN-16 1201833    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 88      1.81M      DISK        00:00:01     20-JAN-16              BP Key: 88   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1 List of Archived Logs in backup set 88 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    3       1201833    20-JAN-16 1204844    20-JAN-16 1    4       1204844    20-JAN-16 1204893    20-JAN-16 1    5       1204893    20-JAN-16 1204958    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 92      143.00K    DISK        00:00:00     20-JAN-16              BP Key: 92   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1 List of Archived Logs in backup set 92 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    6       1204958    20-JAN-16 1205034    20-JAN-16 1    7       1205034    20-JAN-16 1205253    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 96      80.00K     DISK        00:00:00     20-JAN-16              BP Key: 96   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1 List of Archived Logs in backup set 96 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    8       1205253    20-JAN-16 1205354    20-JAN-16 1    9       1205354    20-JAN-16 1205433    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 100     18.00K     DISK        00:00:00     20-JAN-16              BP Key: 100   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1 List of Archived Logs in backup set 100 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    10      1205433    20-JAN-16 1205519    20-JAN-16 1    11      1205519    20-JAN-16 1205559    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 104     128.00K    DISK        00:00:00     20-JAN-16              BP Key: 104   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1 List of Archived Logs in backup set 104 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    12      1205559    20-JAN-16 1205624    20-JAN-16 1    13      1205624    20-JAN-16 1205739    20-JAN-16 BS Key Size       Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 108     8.00K      DISK        00:00:00     20-JAN-16              BP Key: 108   Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC         Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1 List of Archived Logs in backup set 108 Thrd Seq     Low SCN    Low Time Next SCN   Next Time ---- ------- ---------- --------- ---------- --------- 1    14      1205739    20-JAN-16 1205796    20-JAN-16 1    15      1205796    20-JAN-16 1205840    20-JAN-16
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.
Sorry for a long post.
> 1 and from the 1205841 SNA sequence The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840). The message channel ORA_DISK_1: restoring archives Journal Archives journal thread = 1 sequence = 15 channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC indicates that he has restored the sequence up to 15 You can check the log file alert database instance for messages on the fact of recovery. He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15. Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve. An uncomitted transaction is cancelled. Hemant K Collette

 
            
            
		     can't understand why an extract of the database restore fails (missing archive logs) 
			 Dear,
I'm completely back up my database ensures every night with following statement.
full backup AS BACKUPSET COMPRESSED ORCL_FULL_STBY format database tag ' / oradata/archive/fast_recovery_area/%d_%T_%s_%p_FULL_STBY' more tag ORCL_FULL_STBY archivelog delete all entries;
I wanted to check with 'restore... Preview' if my backup is good enough to restore the database from scratch.
result = failed!
Reason:
"any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore."
I have read the documentation oracle and articles for days, but I did not understand that even though I take online backup yesterday if I want to restore my database today I still need archival newspapers last month?
can you please review my analysis and tell me where I am doing wrong?
for example a piece from my last backup;
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
1008 full 199.25 M DISK 00:04:44 October 8, 15
BP key: 1010 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
Item name: / oradata/archive/fast_recovery_area/QIPDB1_20151008_1057_1_FULL_STBY
List of defined backup data files 1008
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
50570723 full 1 8 October 15 /oradata/data/qipdb1/system01.dbf
4 integer 50570723 8 October 15 /oradata/data/qipdb1/users01.dbf
as you can see "Cash SNA" is 50570723 so tells me that my understanding if restore these backups I need archived newspapers on top of the YVERT.
for me the best candidate is
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
65,25 M 1004 00:01 DRIVE: 24 OCTOBER 8, 15
BP key: 1006 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
Part name: /oradata/archive/fast_recovery_area/QIPDB1_STBY/backupset/2015_10_08/o1_mf_annnn_ORCL_FULL_STBY_c1dkfw9k_.bkp
List of newspapers archived in backup set 1004
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 79 50310555 7 OCTOBER 15 50570723 8 OCTOBER 15

BUT out of "restore...". Preview' RMAN stil tells me that
any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore
any backup log archived for thread 1 with sequence 66 and YVERT departure from 49020693 found to restore
any backup log archived for thread 1 with sequence 67 and YVERT departure from 49020696 found to restore
any backup log archived for thread 1 with sequence 68 and YVERT departure from 49020761 found to restore
any backup log archived for thread 1 with sequence 69 and YVERT departure from 49020836 found to restore
any backup log archived for thread 1 with sequence 70 and YVERT departure from 49020919 found to restore
any backup log archived for thread 1 with sequence 71 and YVERT departure from 49021021 found to restore
any backup log archived for thread 1 with sequence 72 and YVERT departure from 49155291 found to restore
any backup log archived for thread 1 with sequence 73 and YVERT departure from 49324912 found to restore
any backup log archived for thread 1 with sequence 74 and YVERT departure from 49498102 found to restore
When I look at V$ ARCHIVED_LOG I see seems indeed to these archived logs removed for cause of "more tag ORCL_FULL_STBY archivelog delete all entries ' that they have been deleetd after saving.
and because of my retention policy and script; I remove the logs also archived backups that are more than 2 days.
S SEQUENCE # FIRST_CHANGE # NEXT_CHANGE #.
- ---------- ------------- ------------
65 49020676 49020693 D
A 49020693 OF 49020676 65
D 68 49020761 49020836
66 49020693 49020696 D
67 49020696 49020761 D
69 49020836 49020919 D
70 49020919 49021021 D
49155291 49021021 71 D
72 49155291 49324912 D
D 73 49324912 49498102
74 49498102 49632131 D
I still don't understand why rman complains of the archived logs that are for an older sequence (SNA) as my last backup
because I was assuming that the concerned newspapers archived should have already applied to these files of data, right?
My final goal is to deliver below for the case that we have lost everything.
Run {}
restore the database;
recover the database;
}
Thanks in advance,
Halit
			 Hi guys,.
I found the root cause and workaround
RMAN-06025 - RMAN RESTORE DATABASE OVERVIEW to the backup site asks former newspaper (Doc ID 1599013.1)
CAUSE Checkpoint_change# standby controlfile not refreshed properly.  BUG 15876029 - RESTORE PREVIEW ASKING OLD ARCHIVE LOG IN STANDBY DATABASE  Closed as DUPLICATE of  BUG 8740124 - CURRENT STANDBY REDO LOG GROUP SHOULD BE INCLUDED IN THE DATABASE BACKUP BY RMAN SOLUTION  1) Workaround is to recreate the standby controlfile.  OR  2) upgrade to 11.2.0.4 or above where Bug 8740124  is fixed  OR  3) check for availability of patch 8740124
		    
            
            
		     Multiplex Archived Logs 
			 With the help of 11.2.0.4.0
I am trying to mux the newspapers archived (duplicate); However, do not know if I'm doing things.
I followed this http://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo004.htm and made the following
LOG_ARCHIVE_DEST_1 = 'LOCATION=Z:\FlashRecoveryArea\archlogs\'
LOG_ARCHIVE_DEST_2 = 'LOCATION=\\backupserver\archlogs_location'
I thought I was doing the right thing with handwritten copies in both places when I run
"alter newspaper archive of the current system. However, to take a closer look, looks like maybe it's different.
Z:\FlashRecoveryArea\archlogs has the logs archived LOG_1_68_xxxx. ARC and LOG_1_71_xxxx. ARC
\\backupserver\archlogs_location archived LOG_1_69_xxxx newspapers. ARC, LOG_1_70_xxxx. ARC and LOG_1_71_xxxx. ARC
I misunderstood the document? This is not duplication of archived newspapers?
Thank you
			 I think your problem is the backup archivelog and remove that happens at the same time as the journal was cheating (i.e. newspaper is too slow).
Just do this - see crossouts and "BOLD" text 'everything '...
RUN
{
SQL "alter session set nls_date_format = 'MON-DD-YYYY HH24:MI:SS' ';"
overlap archivelog all;
cross-checking of backup;
SQL 'alter system archive log current';
SQL 'alter system archive log current';
backup
(database FORMAT '\backupserver\full\FULLBKUP_%d.DBID%I.%T.%s.%p.rman')
more all archivelog delete all input FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' TAG = "FULLBKUP_PLUS_ARCHLOG";
window recovery obsolete report of 5 days;
delete noprompt obsolete recovery window of 5 days;
SPFile FORMAT '\\backupserver\full\SPFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' label backup = "BKUP_SPFILE";
SQL 'alter controlfile backup database path as "\\backupserver\full\ctlfilePROD.txt" RE-USE";
SQL "' create pfile =" \\backupserver\full\pfile_PROD.ora "of spfile"; "
SQL 'alter system archive log current';
SQL 'alter system archive log current';
backup FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' archivelog delete all all the entries TAG = "BKUP_ARCHLOG";
backup current controlfile FORMAT '\\backupserver\full\CTLFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' TAG = "BKUP_CTLFILE";
}
		   
 
            
            
		     Recovery media - cannot find the archived log 
			 Oracle 10g Release 2
Database works in mode noarchive - isn't my choice, so I'm stuck with it.
SQL> select startup_time,status,database_status from v$instance;

STARTUP_T STATUS       DATABASE_STATUS
--------- ------------ -----------------
20-AUG-15 MOUNTED      ACTIVE

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01113: file 2 needs media recovery
ORA-01110: data file 2: '/ads/database06/oracle/oradata/ODB1/UNDOTBS03.dbf'

SQL> recover datafile '/ads/database06/oracle/oradata/ODB1/UNDOTBS03.dbf';
ORA-00279: change 24699944499 generated at 08/08/2015 01:07:04 needed for thread 1
ORA-00289: suggestion :
/oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21/o1_mf_1_698472_%u_.arc
ORA-00280: change 24699944499 for thread 1 is in sequence #698472

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

ORA-00308: cannot open archived log
'/oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21/o1_mf_1_698472_%u_.arc'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3

$ cd /oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21

$ ls o1_mf_1_698472_%u_.arc
o1_mf_1_698472_%u_.arc: No such file or directory

The entire directory is empty.
There is no data for August 21, 2015, the database is offline for a few days.
The database has been cloned by the system administrator, so nobody was on this database. New server.
			 orclrunner wrote:
That was my thought as well. They have made a copy ' hot' all the files. I think they should have stop the database before copying files.
a ' hot' copy can succeed but each tablespace must have been in online BACKUP before doing the copy of OS files.
With DB mode noarchive, a copy hot may or may not succeed according to the DML activity & duration of the COPY
It's better to STOP NOW before copy of OS
		    
            
            
		     Archive log list does not sequence of current journal is awaiting data base 
			 Hi all
So I tried waiting for database physical installation in my local vm.
I apparently completed the Setup, but I am facing a problem which I cannot understand.
OS:-Linux 6.4
Oracle version: 12.1.0.2.0
primary data: ORA12C
backup database: ORASTD
Primary database: -.
SYS@ORA12C > list of archive logs;
Database log mode Archive Mode
Active AutoArchive
Archives/u01/app/oracle/fast_recovery_area of destination
More old sequence of journal online 14
Log sequence archive 16
Current log sequence 16
SYS@ORA12C > select name, database_role, controlfile_type from v$ database;
NAME DATABASE_ROLE CONTROL
--------- ---------------- -------
ORA12C CURRENT PRIMARY
SYS@ORA12C > select the sequence #, first_time, next_time, applied from v$ archived_log;
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
4 15 APRIL 15 APRIL 16 15 NO.
4 15 APRIL 15 APRIL 16, 15 YES
5 16 APRIL 15 APRIL 16 15 NO.
5 16 APRIL 15 APRIL 16, 15 YES
6 16 APRIL 15 APRIL 16 15 NO.
6 16 APRIL 15 APRIL 16, 15 YES
7 16 APRIL 15 APRIL 16 15 NO.
7 16 APRIL 15 APRIL 16, 15 YES
8 16 APRIL 15 APRIL 16 15 NO.
8 16 APRIL 15 APRIL 16, 15 YES
9 16 APRIL 15 APRIL 16 15 NO.
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
9-16 APRIL 15 APRIL 16, 15 YES
10 16 APRIL 15 APRIL 16 15 NO.
10-16 APRIL 15 APRIL 16, 15 YES
11 16 APRIL 15 APRIL 16 15 NO.
12 16 APRIL 15 APRIL 16 15 NO.
13 16 APRIL 15 APRIL 16 15 NO.
11-16 APRIL 15 APRIL 16, 15 YES
12-16 APRIL 15 APRIL 16, 15 YES
13-16 APRIL 15 APRIL 16, 15 YES
14 16 APRIL 15 APRIL 16 15 NO.
15 16 APRIL 15 APRIL 16 15 NO.
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
15 16 APRIL 15 APRIL 16 15 NO.
14-16 APRIL 15 APRIL 16, 15 YES
Waiting for the database: -.
Select the sequence #, first_time, next_time, applied from v$ archived_log;
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
4 15 APRIL 15 APRIL 16, 15 YES
5 16 APRIL 15 APRIL 16, 15 YES
6 16 APRIL 15 APRIL 16, 15 YES
7 16 APRIL 15 APRIL 16, 15 YES
8 16 APRIL 15 APRIL 16, 15 YES
9-16 APRIL 15 APRIL 16, 15 YES
10-16 APRIL 15 APRIL 16, 15 YES
11-16 APRIL 15 APRIL 16, 15 YES
12-16 APRIL 15 APRIL 16, 15 YES
13-16 APRIL 15 APRIL 16, 15 YES
15 16 APRIL 15 16 APRIL 15 IN-MEMORY
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
14-16 APRIL 15 APRIL 16, 15 YES
SQL > select name, database_role, controlfile_type from v$ database;
NAME DATABASE_ROLE CONTROL
--------- ---------------- -------
PHYSICAL STANDBY ORA12C STANDBY
SQL > archive logs list;
Database log mode Archive Mode
Active AutoArchive
Archives/u01/app/oracle/fast_recovery_area of destination
More old sequence of journal online 0
Log sequence to archive 0
Current log sequence 0
Now, here's my question is why the sequence of current newspapers shows 0. I tested the datas
database primary eve happens again. I'm totally out of index.
I tried to find it on google but nothing could help me until now.
Any kind of help would be very appreciated.
Thank you
Soumya
			 Hello
I am also testing in Data Guard 12.1 configurations.
Oracle support response is "it seems therefore that this information be removed.
So is the best way to check on the database pending:
SQL > select thread #, max(sequence#) ' last day before Seq received. "
v $ archived_log val, v$ database vdb
where val.resetlogs_change # = vdb.resetlogs_change #.
Group thread # order by 1;
SQL > select thread #, max(sequence#) ' last day before Seq applied.
v $ archived_log val, v$ database vdb
where val.resetlogs_change # = vdb.resetlogs_change #.
and val.applied in ('YES', "IN-MEMORY")
Group thread # order by 1;
concerning
		    
            
            
		     Retention policy for archive logs. 
			 Retention policy is set to "REDUNDANCY 2".
We do the complete disk backup without archive logs at 12:00.
After that, we make full backup with newspapers to archive tape at 18:00.
RMAN will consider newspapers to check-in after 12:00 as obsolete as it is backed up to tape?
Thank you.
			 REDUNDANCY applies only to the data files and control files. For archiving logs, there are POLICY of DELETE ARCHIVELOG. But "remove obsolete" won't use POLICY of DELETE ARCHIVELOG, so archiving logs should be removed separately if they meet this policy.
		    
            
            
		     Pull on the RMAN backup archive logs? 
			 Environment:
Oracle 11.2.0.3 EE on Solaris
Physical standby
I have a gap of journal archive at the moment.  The missing archive logs have been saved on the primary and have not yet been transferred to waiting due to some maintenance work performed on the standby server.
The database will be able to recognize that the missing archivelog files are in the RMAN backup files, restore them and send them to the update server standby for application?
If not, will it restore manually, copy them to the standby server and save them for their application?
Thanks a lot for your help!
-gary
			 Were the archivelogs deleted on the primary once they have been saved? If they have been deleted on the primary, then you can:
1 manually transfer the backup to forward files
2 replace the archivelog destination configured on the eve
3 restart the managed recovery on the standby process, and the computer should be able to detect and apply the missing archivelogs.
If they have not been deleted on the primary and are always available in the archivelog directory configured, then the process of Data Guard should be able to detect and automatically fix the gap.
If you have a long interval archivelogs missing and you use + ASM, you can also try to use an incremental backup to roll forward the database pending, this article provides a good step by step: the steps for Rolling forward a standby database using RMAN incremental backup. (Doc ID 836986.1)
Kind regards
Oscar

 
		 
          Maybe you are looking for 
           
            
		     Stream HP: System administrator disabled password code 59638073 
			 No password for my daughter's computer. Tried to restart USB. Now I can't have everything. Tried F11, esc, etc. Help, please. Eager to erase the entire system if necessary. 
		    
            
		     Satellite A80-132 Out TV does not 
			 Hi all I have a problem with the TV S-Video output on my laptop. When I tried first, he worked in black and white (NSTC I guess), but I could not change color (PAL, as I am in the United Kingdom) because the option appears in the Graphics controller  
		    
            
		     Stream 11 HP: HP flow 11 not answer anything 
			 I went and stopped a program to run at first upward and do not know which.  Now my computer does not respond. It opens not internet, open Task Manager, no indication for the Device Manager, nothing shows to restore or retrieve. I thought to go to the 
		    
            
		     Disable the TestStand 2014 report batch 
			 Hello I'm trying to disable batch report generation in the model batch of TestStand 2014. I found this thread back in 2005, but it seems that things have changed a bit since then with the addition of the Plugins model in new versions of TestStand. I  
		    
            
		     On a Pro 8600, how can I switch between the simple side and double-sided printing? 
			 I looked at the response to the more than 8600 pro, but when I go to print-preference-advance, I don't see the option of switching between duplex and single-sided.