Success of verfying archives log shipping
RDBMS version: 11.2.0.2Platform: Solaris 10
How can I check if an individual archived Journal (or a set of newspapers archived after a certain time) in the primary DB server was successfully sent to the server of the DB of the day before?
Hello
If you are using dataguard broker, I think this might help you
http://docs.Oracle.com/CD/B10501_01/server.920/a96629/dbpropref.htm#92312
Tags: Database
Similar Questions
-
The archive logs shipped but more old logs do not applied...
Environment:
Oracle on Solaris 11.2.0.3 10.5
The Data Guard environment working fine for 6 months.
I recently had problems with disk space on the day before and had to copy some files from newspapers of the archives to a mount point different that had been shipped to the waiting, but not yet applied because I had to cancel the paper application process.
After having cleared the space problem and start log shipping and return application log on (change database recovery managed to sleep...) I have the new logs shipped but my watch is a bunch of log files behind. I can see it in the V$ ARCHIVED_LOG on intelligence, where the last seq # applied is 8083 in my case and the more current seq # is currently more than 8200.
I have all the archives always connects in 'other' the mount point and can move back the directory the correct archive according to needs.
Since the next file that the application requires is seq # 8084, I moved this file in the/arch directory awaits the day before 'see' and apply it. No luck.
By searching in the alert log just before after execution of the 'alter database recover managed standby database disconnect;' I see the following:
and also:Media Recovery Waiting for thread 1 sequence 8084
and just below that:Fetching gap sequence in thread 1, gap sequence 8084-8084
I thought I read in the docs that the FAL_SERVER and the FAL_CLIENT are no longer needed. (?)FAL[client]: Error fetching gap sequence, no FAL server specified
I also found a CKPT script that lists information about DG Environment. For the primary side to hang on, but the day before one produces this output:
I do not use a fast recovery area.NAME DISPLAY_VALUE ------------------------------ ------------------------------ db_file_name_convert /u01/oradata/APSMDMP1, /u01/or adata/APSMDMP1, /u02/oradata/A PSMDMP1, /u02/oradata/APSMDMP1 , /u03/oradata/APSMDMP1, /u03/ oradata/APSMDMP1, /u04/oradata /APSMDMP1, /u04/oradata/APSMDM P1 db_name APSMDMP1 db_unique_name APSMDMP1STBY dg_broker_config_file1 /u01/app/oracle/product/11203/ db_2/dbs/dr1APSMDMP1STBY.dat dg_broker_config_file2 /u01/app/oracle/product/11203/ db_2/dbs/dr2APSMDMP1STBY.dat dg_broker_start FALSE fal_client fal_server local_listener log_archive_config DG_CONFIG=(APSMDMP1,APSMDMP1ST BY) log_archive_dest_2 SERVICE=APSMDMP1 ASYNC VALID_F OR=(ONLINE_LOGFILES,PRIMARY_RO LE) DB_UNIQUE_NAME=APSMDMP1 MA X_CONNECTIONS=2 log_archive_dest_state_2 ENABLE log_archive_max_processes 4 log_file_name_convert /u01/oradata/APSMDMP1, /u01/or adata/APSMDMP1 remote_login_passwordfile EXCLUSIVE standby_archive_dest ?/dbs/arch standby_file_management AUTO NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE ---------- ------------------------------ --------------- ---------- -------------------- APSMDMP1 APSMDMP1STBY MAXIMUM PERFORM PHYSICAL S READ ONLY WITH APPLY ANCE TANDBY THREAD# MAX(SEQUENCE#) ---------- -------------- 1 8083 PROCESS STATUS THREAD# SEQUENCE# --------- ------------ ---------- ---------- ARCH CLOSING 1 7585 ARCH CLOSING 1 7588 ARCH CLOSING 1 6726 ARCH CLOSING 1 7581 RFS RECEIVING 1 8462 MRP0 WAIT_FOR_GAP 1 8084 RFS IDLE 0 0 NAME VALUE UNIT TIME_COMPUTED DATUM_TIME ------------------------------ ---------- ------------------------------ ------------------------------ ------------------------------ transport lag +00 00:01: day(2) to second(0) interval 08/16/2012 13:24:04 08/16/2012 13:23:35 59 apply lag +01 23:08: day(2) to second(0) interval 08/16/2012 13:24:04 08/16/2012 13:23:35 43 apply finish time +00 00:17: day(2) to second(3) interval 08/16/2012 13:24:04 21.072 estimated startup time 15 second 08/16/2012 13:24:04 NAME Size MB Used MB ------------------------------------------------------------ ---------- ---------- 0 0
What should I do to get the old logs to check-in begins to apply again?
The alert log says something about "Adding value to the media", but I don't know why I would need that since I have the log files itself.
Any help is appreciated.
Also, I spend a significant amount of time to read through this forum and many articles on the web but couldn't find exactly the solution I was looking for.
Thank you very much!!
-garyTry to save the log file
alter database register logfile 'full path for the 8074 sequence.
and check select message from v$ dataguard_status;
-
Hi guys,.
I use oracle 10.2.0.4.0 on windows server 2003. I created a standby database using the RMAN duplicate command. I also created re file password on the principal database as follows
C:\oracle\10.2.0\database > file orapwd = password orapw$ ORACLE_SID = XXXX force = y
and copied everywhere in standby mode. My backup database was created successfully, but my archive logs is not shipped in standby mode. I did also tnsping and it looks like okie. I pulled the following query in the standby mode:
SQL > SELECT THREAD #, SEQUENCE #, APPLIED TO V$ ARCHIVED_LOG
2 order of SEQUENCE #.
3;
no selected line
No idea where I am going wrong. Would appreciate your help :)
Thanks in advance!
ConcerningCheck whether the user of your operating system is part of the ORA_DBA group. You can find this group by going to start > RUN > compmgmt.msc (type). Click OK. Click local users and groups, and then double-click groups. Yet once, double-click ora_dba. Find out if the user is member of this group. If not, add a user in the format domainname\username. Click on apply and OK.
KK is right. If you cannot do the following primary school
sqlplus sys/yyyy@standby
then your logs will not be sent to standby mode.Also create password for Eve files separately (I mean create the standby server) rather than creating primary and took overall in standby mode, of course you can use the same password...
Hope this works
Published by: jazz81 on November 10, 2010 16:31
-
Automatic shipping of the archiving log
Hello
I use Oracle 10 g (10.2.0.1) in RHEL 5 server. I have reproduced my prod standby database, and I want my archive logs to be shipped automatically. I used the alter system log_archive_dest_2 = 'service = reopen optional STANDBY = 20' in my prod database but the Archives of newspapers are not provided automatically. What could be the reason?
Kind regards
007Hello
ORA-16191: customer main newspaper not connected waiting for shipment
Cause: An attempt to ship again standby without connect to standby or invalid user credentials.Action: Make sure that primary and standby use password and that primary and standby files have the same SYS password. Restart primary or standby after making sure that the password file is accessible and parameter initialization REMOTE_LOGIN_PASSWORDFILE shared or EXCLUSIVE.
Mseberg provides you with the solution. Copy the password of the primary database to the standby server and rename it in the format 'orapw
. -
Archive log gap is asleep when the audit function is set to DB
Hello
I'm a new dba. I am facing a problem to the production server, that whenever audit_trail is set to db, gap journal archive is created on the site of the previous day.
My version of the database is 10.2.0.4
Operating system is windows 2003 R2
Audit_trail is set to db only to the main site, after you have set the parameter DB when I bounced the database and set the log file, gap journal archive is created in the waiting... I use the LGWR log transport mode.
Is there any transport of newspapers and relationship beteen audit_trail?
Please note that my log location archive two sites has enough disk space and the drive works very well. Also my primary and standby is in WAN.
Please help me in this. Any help will be much appreciated.
Here's a trace file that can be useful to give an opinion.
D:\oracle\admin\sbiofac\bdump\sbiofac_lns1_6480.TRC dump file
Kill Jun 05 13:46:02 2012
ORACLE V10.2.0.4.0 - Production vsnsta = 0
vsnsql = 14 vsnxtr = 3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 V5.2 Service Pack 2 Version
CPU: 2 - type 586, physical cores 1
Process affinity: 0x00000000
Memory (success/Total): Ph: 16504 M / 18420 M, Ph + FCP: 41103/45775 mafuta, GOES: 311 M / 2047 M
Instance name: sbiofac
Redo thread mounted by this instance: 1
Oracle process number: 21
Windows thread ID: 6480, image: ORACLE. EXE (LNS1)
NAME OF THE SERVICE :() 13:46:02.703 2012-06-05
SESSION ID: (534.1) 2012-06-05 13:46:02.703
kcrr.c 13:46:02.703 58902 2012-06-05
LNS1: initialization of communication LGWR
LNS1: connection to the KSR channel
Success
LNS1: subscribe to channel KSR
Success
2012-06-05 13:46:02.750 58955 kcrr.c
LNS1: successfully initialized ASYNC = 1
Destination is specified with ASYNC = 61440
kcrr.c 13:46:02.875 73045 2012-06-05
Sending thread 1 seq 2217 online journal [1 logfile] in standby mode
Repeat customer shipping performing a pending connection
kcrr.c 13:46:03.656 66535 2012-06-05
Connected mode standby successfully
Customer logon and security successful trading!
Archiving on blocks of destination sbiofacdr ASYNC = 20480
Allocation of blocks of ASYNC: previous blocks = 0 new blocks = 20480
Open log file [logno 1]
2012-06-05 13:46:44.046
Error 272 writing log file archive ensures the host 'sbiofacdr '.
ORA-00272: the archive log write error
kcrr.c 13:46:44.078 62692 2012-06-05
LGWR: I/O error 272 archiving log 1 to 'sbiofacdr '.
kcrr.c 13:46:44.078 60970 2012-06-05
kcrrfail: err dest:2: 272 explosion of strength: 0:1
2012-06-05 13:47:37.031
kcrr.c 13:47:37.031 73045 2012-06-05
Log fil 1 seq 2218 online shipping [logfile 2] in standby mode
kcrr.c 13:47:37.046 73221 2012-06-05
Stop [due to no ASYNC destination more]
Again Push Server: Release the buffer ASYNC PGA
LNS1: Make a channel of delivery for the next time around...Hello again;
I believe you can discover that restore you rates of production using LOG_ARCHIVE_TRACE:
SQL > show parameter LOG_ARCHIVE_TRACE
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
log_archive_trace integer 0http://docs.Oracle.com/CD/B19306_01/server.102/b14237/initparams107.htm
In addition to the SDU, you can define SEND_BUF_SIZE and RECV_BUF_SIZE
This is the Oracle document on this:
http://docs.Oracle.com/CD/B19306_01/network.102/b14212/performance.htm
You can define SDU in the tnsnames.ora thus:
PRIMARY = (DESCRIPTION = (SDU=32767) (ADDRESS=(PROTOCOL=tcp) (HOST=) (PORT=1521)0 (CONNECT_DATA= (SERVICE_NAME=PRIMARY.hostname)) ) The 'database Net Services Administrator's Guide' post above link is probably the best source of information.
Best regards
mseberg
-
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 UPintegerTIMES TO DEVICE TYPEcommand 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 UPintegerTIMESclause, then aBACKUP ARCHIVELOG, the command copy newspapers, unlessintegeralready exist on the specified device type backups. Ifintegerare backups of logs, then theBACKUP ARCHIVELOGcommand ignores the newspapers. In this way, the deletion of archived newspaper policy works as a defaultNOT BACKED UPintegerTIMESclause on theBACKUP ARCHIVELOGcommand. Note that you can override the deletion policy by specifying theFORCEoption on theBACKUPcommand.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
-
Hello
My oracle database is 11.2.0.2 RDBMS RAC on RHEL 5. 6
We have recently established physics of the standby database. How to remove archive logs waiting for physical standby mode?Hello;
There is a little different to do this. I would consider these notes:
How to ensure that RMAN is NOT delete archived logs that have not yet shipped to standby [394261.1 ID]
RMAN removes records of logs on the primary database not applied pending physical [ID 1324759.1]
Configure RMAN to purge the archivelogs after application on hold [728053.1 ID]
You can use an RMAN script to do this:
echo "Starting RMAN..." $ORACLE_HOME/bin/rman target / catalog user/password@rcatalog << EOF delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8'; exit EOFBest regards
mseberg
-
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...
-
RMAN-06059: expected archived log not found
DB version: 11.1.0.7
Operating system: Solaris 10
Our cron job RMAN has met the following error.
-First save attempt (complete bkp more archive log) done by connecting to the catalog
Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.Starting backup at 14-MAR-12 current log archived released channel: ch00 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58 RMAN-06059: expected archived log not found, lost of archived log compromises recoverability ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'
-Use the control as a catalog file
Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.$ rman target / Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012 Copyright (c) 1982, 2007, Oracle. All rights reserved. connected to target database: PQWSP (DBID=1638594930) RMAN> crosscheck archivelog all; using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK validation succeeded for archived log archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587 validation succeeded for archived log archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270 validation succeeded for archived log . . . . . Crosschecked 14 objects
So I ran a
and this backup was successful.BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?No idea why the first attempt failed when there were not all logs archived expired?
this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.
Thank you
Tylay Singh -
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:02dbname is still DBSOURCE instead of DBTARGETThe 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
-
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_p1And
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_INCMy 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 recoverychannel 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:22RMAN-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
-
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
-
Redo log shipping after a stop pending physical
Hallo,
I just have a question for redo log shipping
in a configuration simple primary/secondary 11g.
In a shutted down an instance physical standby, redoshipping is active? Primary redo file transfer is still ongoing?
Thanks in advance
Hello;
I'm not going to say no. I still SEE on the primary side before I shutdown, maintains false alarms from happening.
Test
Using this query
http://www.mseberg.NET/data_guard/monitor_data_guard_transport.html
DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP
---------- -------------- ------------ ----------- -------------- -------
TDBGIS01B PRIMARY 5558 5557 21-OCT/12:51 1
Stop waiting
SQL > alter database recover managed standby database cancel;
Database altered.
SQL > shutdown
ORA-01109: database is not open
The database is dismounted.
Journal of strength comes on primary side
SQL > alter system switch logfile;
Modified system.
(3)
Journal of before was 5558 check so make sure 5559 or higher
Last log is
o1_mf_1_5558_c2hn5vdf_.arc
Wait a few minutes, no change
Best regards
mseberg
-
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.dbfas 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 isTime 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_.bkpList 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 thatany 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 restoreWhen 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 DI 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,
HalitHi 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
Maybe you are looking for
-
I want to uninstall and reinstall Firefox, but I encounter some errors that I need help: alert.
Basically, I had some problems to where I couldn't actually open the Firefox browser, which was never fixed (I'm using chrome right now). I am trying to download Adobe Flash Player, but when I try, it says "You must close all Firefox Windows in order
-
Satellite L505-13D web cam driver needed
I have lost the motherboard drivernow sorely need driver webcam Satellite L505-13D. concerning
-
15 - r110na: enter the password of administrative or power on password
I received a message on my phone after using it not for a week after an administrative password. A message more later said there was a system disabled with the following code: 51803013. Could you please help me with this so I can get into my laptop p
-
can't find Toshiba Equium online, can not upgrade the BIOS
Hello all, I tried to update my laptop Toshiba, such that requested by engine software, accessed via the link provided, toshiba site to my confussion my model is EQUIUM was not listred nor the model, I also found the site of toshiba very unhelpful an
-
Hello Does anyone know if it is possible to export the rules to a new instance of an instance of Foglight? We set up a separate foglight for non-produits env and I want to move our customs regulations export and import if possible rather than recrea