Recovery of archived notification

How to retrieve the view that I have archived after they are received?

OK, I think you're talking about emails Gmail, right? When you want to locate an email archived on the phone, open your Inbox in Gmail app, and then tap Menu-> view-> all mail labels. You should be able to find archived in this email. I hope this helps.

Tags: Motorola Phones

Similar Questions

Cannot create recovery logs archived
Oracle 11.2.0.3 in Windows Server 2008 64 bit.
I try to put in place the mode archive in a database:

C:\Users\Admin > SET ORACLE_SID = BDSPROD

C:\Users\Admin > SQLPLUS/nolog

SQL * more: Production of liberation 11.2.0.3.0 Thu Oct 25 12:28:59 2012

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

SQL > connect sys/oracle as a sysdba
Connected.
SQL > select log_mode from v database $;

LOG_MODE
------------
NOARCHIVELOG

SQL > ALTER SYSTEM SET log_archive_start = TRUE SCOPE = spfile;

Modified system.

SQL > ALTER SYSTEM SET log_archive_dest = a: \oradata\BDSPROD\archivelogs\' SCOPE = spfile;

Modified system.

SQL > shutdown immediate;
The database is closed.
The database is dismounted.
ORACLE instance stops.
SQL > SHUTDOWN IMMEDIATE;
ORA-01012: not connected
SQL > STARTUP MOUNT;
ORA-32004: outdated or obsolete parameters specified for the instance of RDBMS
ORACLE instance started.

Total System Global Area 6781128704 bytes
Bytes of size 2268064 fixed
3539993696 variable size bytes
Buffers data 3221225472 bytes
Redo buffers 17641472 bytes
Mounted database.
SQL > ARCHIVE LOG START;
Statement processed.
SQL > ALTER DATABASE ARCHIVELOG;

Database altered.

SQL > ALTER DATABASE OPEN;

Database altered.

SQL > alter system switch logfile;

Modified system.

SQL > select log_mode from v database $;

LOG_MODE
------------
ARCHIVELOG
however, there is no archived log generated in the folder recovery: D:\oradata\BDSPROD\archivelogs\
I also tried with log_archive_dest = SET has: \oradata\BDSPROD\archivelogs' (without the last "------"), but the same behavior, no restoring archived log is created.

Published by: user521219 on October 25, 2012 10:45
SQL > ALTER SYSTEM SET log_archive_dest = a: \oradata\BDSPROD\archivelogs\' SCOPE = spfile;

Which shows the output when you use query below?
SQL > select name from v$ archived_ log;

And don't use any specific destination with the use of the attribute location below the number and try again.

SQL > ALTER SYSTEM SET log_archive_dest_1 =' location = ' D:\oradata\BDSPROD\archivelogs;

Thank you

A copy of recovery/db + archive logs
Hi champions.
There is a confusion in the recovery of a database. Version 10g.
I have a hot (using the copy command) of a database backup (mode of journal archive) I took to 22.00.00 on Sunday.
Now, my database is up and running Monday, Tuesday, Wednesday in archive log mode. Since the last backup .and (Sunday 10 pm) my database got crashed Wednesday 14.00 completely lost everything (CDR files) archive logs only is with me, I have the newspaper archive...
Can I recover my database using the backup from Sunday + newsletter archive until it crashed.
Kind regards
Shitesh Shukla
If you have an old backup of the controlfile, you use restore database with backup cotrolfile to cancel. Backup Controlfile as of old, he would keep asking for the archivelogs to provide for backup if you need to cancel the recovery.

HTH
Aman...

Problem taken Recovery Mode Archive No. with redo a log backup
While recovering a log roll forward in Mode No Archive, I faced the following problem: -.

SQL > shutdown normal;
Then taken backup to all redo logs, control files and data files in a folder "Bkp".
After that, when I tried to delete a data file manually "EXAMPLE01. DBF' of Oradata... I was asked to say error
"Unable to remove example01.dbf, as it is used by another person or program" and I am not not able to understand... Help, please...
Hello

Bring down the service for the database... GoTo run-> type service.msc and stop the service for the particular db and try to delete the data file. I think that the DB was not properly closed...

Thank you
Deepak

Need help with Toshiba record after recovery installed

After that I completely reinstalled my laptop with the recovery CD, Toshiba notifications (icon in the lower right corner) program no longer works because it asks me to register and when I do, I said already registered BUT I can't use it again and it continues to display after each start upward.

What can I do to work for him again?

Maybe the TEMPO system has something to do about it. I'd appreciate some research more on this issue, because I have a similar problem. Greetings

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

RMAN restore and recovery

Hello
If I have two full backups in my FRA (say 7 to 14 days)
Q1. I assume that if I run it.
RMAN > restore database;
It will go to the last backup (7 days ago)?
Q2. How to restore the backup of ago 14 days instead?
Q3. If I restore the database of 14 days but then question
RMAN > recover database until < 3 days >
RMAN would simply apply the recovery logs archived for 14 days to the point of recovery or it would be smart enough to realize, there a backup to restore all first 7 days ago, then apply 7 days recovery logs, to the point of recovery?
Q4. Can you do an online backup as a copy of the Image instead of a backup set or you can offline backups when you use a copy of the Image?
All wisdom, greatly appreciated
Jim

(1) switching is not required for recovery. You have just enough do to standardize the data files. It doesn't matter if the switch is produced or not.

(2) "extra small set of archivelogs" can be enormous if the backup is long-term with many DML during backup.

You need a sufficiently archivelogs, regardless of the copy backupset or image, to make the data files in compliance.

(3) hot RMAN copy backup data files, while they are updated, but in order to avoid a block inconsistent read to avoid corruption. The data files are not frozen, as with the hot user managed backup.

Spend my DB no Archive Log Mode 11 g
I have a big database running on release of oracle 11g 2 with a large number of users and huge daily transactions running in archivelog mode, I will change the mode of the database in any mode of journal archive

the following steps: -.

SQL > shutdown immediate

SQL > startup mount

SQL > alter database noarchivelog;

SQL > alter database open;

is there a risk to do

can the database after change in noarchivelog mode, could not be opened?

What are the reserves to take before doing this work?

Thank you very much.
Hello

I think that you must not need change size of db recovery file destination.
You must use the parameter log_archive_dest_n with LOCATION, witch's location is your destination to archive.
Log_archive_dest_1 default value is use_db_recovery_file_dest, you must change this value.

If you do not need to archive newspapers, then you can remove all the recovery logs archived after backup with RMAN.
```
  RMAN> backup database plus archivelog delet all  input;
```
Thank you
Mr. Mahir Quluzade
http://www.Mahir-quluzade.com

Recovery of control files. I need to restore database?
I am using below command procedure files recovery: restore the backup controlfile. I'm not restore database in this procedure with RESTORE DATABASE

==================================================================================
QUESTION: Do I need to restore a full database to be consistent?
=====================================================

SQL > select name from v$ controlfile;

NAME
--------------------------------------------------------------------------------
/ QA/Data/OBT/QA112QA/Data/control01. CTL
/ QA/Data/OBT/QA112QA/Data/control02. CTL
/ QA/Data/OBT/QA112QA/Data/control03. CTL

[oracle@rh56b64-1 rmanbackup] $ rm /qa/data/obt/QA112QA/data/control01.ctl /qa/data/obt/QA112QA/data/control02.ctl /qa/data/obt/QA112QA/data/control03.ctl

SQL > stop the demolition
ORACLE instance stops.

SQL > startup
ORACLE instance started.

Total System Global Area 275615744 bytes
Bytes of size 2212496 fixed
184552816 variable size bytes
Buffers data 83886080 bytes
Redo buffers 4964352 bytes
ORA-00205: error in the identification of control files, see log alerts for more information

[oracle@rh56b64-1 rmanbackup] $ pwd
/ QA/Data/OBT/rmanbackup

[oracle@rh56b64-1 rmanbackup] $ ls - ltr
Total 591368
-rw - r - 1 oracle oinstall 586711040 24 Dec 19:25 1antmgo6_1_1
-rw - r - 1 oracle oinstall 1435648 24 Dec 19:25 1dntmgov_1_1
-rw - r - 1 oracle oinstall 16809984 24 Dec 19:25 d to cfc-1266678734-20121224-0

-set DBID - get the name of the controlfile autobackup.
-For example, if the name of auto backup is
-CTL_SP_BAK_C-1507972899-20050124-00 the the DBID is
-1266678734. This step is not necessary if the instance is
-Start RMAN

RMAN > set dbid 1266678734

executing command: SET DBID

RMAN > restore controlfile to ' / qa/data/obt/rmanbackup/EFA-1266678734-20121224-0;

From restoration to December 24, 12
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 135 type device = DISK

channel ORA_DISK_1: restore the control file
channel ORA_DISK_1: restore complete, duration: 00:00:03
output file name=/qa/data/obt/QA112QA/data/control01.ctl
output file name=/qa/data/obt/QA112QA/data/control02.ctl
output file name=/qa/data/obt/QA112QA/data/control03.ctl
Finished restore at December 24, 12

RMAN > change the editing of the database;

mounted database
output channel: ORA_DISK_1

RMAN > restore database;

From back to December 24, 12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 135 type device = DISK

starting media recovery

Journal archived for thread 1 sequence 2 is already on the disc in the file /qa/data/obt/QA112QA/data/redo02.log
Journal archived for thread 1 with sequence 3 is already on the disc in the file /qa/data/obt/QA112QA/data/redo03.log
Journal archived for thread 1 with sequence 4 is already on the disc in the file /qa/data/obt/QA112QA/data/redo01.log
Archive log file name=/qa/data/obt/QA112QA/data/redo02.log thread = 1 sequence = 2
Archive log file name=/qa/data/obt/QA112QA/data/redo03.log thread = 1 = 3 sequence
Archive log file name=/qa/data/obt/QA112QA/data/redo01.log thread = 1 sequence = 4
media recovery complete, duration: 00:00:01
Finished recover at December 24, 12

RMAN > alter database open resetlogs;

open database
Hello

==================================================================================
QUESTION: Do I need to restore a full database to be consistent?
=====================================================

You don't have to restore the full database. You just need to restore the backup controlfile and restore the database.
The steps you mentioned are good restore the controlfile. After recovery, you must open the database in resetlogs.

Also, you can take a look at this http://neeraj-dba.blogspot.com/2011/04/loss-of-control-file-in-various.html

Kind regards
Shivananda

RMAN recovery is data loss - tips welcome
Hello

I really need help here if someone is a guru RMAN n.

Problem
------------

The system I have recover aid that the rman backup below does not include the table that I created after the backup was completed, the database has been recovered, but somehow the creation and populating a table after the backup is complete have been lost. Can you see what I did wrong here, the text is based on an existing script I need to also change little this is used in Prod dystsems elsewhere

DB is:-11.2.0.1

Please adsvise where I'm wrong...

Target of $ORACLE_HOME/bin/rman / log = $BACKUP_LOG < < EOF
Run {}
delete noprompt obsolete device type disk;
affect the disc channel d1 device format type "$ORACLE_BACKUP_DIR_LOC/%Y_%M_%D/database_%U."
allocate channel device d2 disc format type "$ORACLE_BACKUP_DIR_LOC/%Y_%M_%D/database_%U."
backup as compressed backupset database include current controlfile;
output channel d1;
output channel d2;
SQL 'alter system archive log current';
affect the disc channel a1 device format type "$ORACLE_BACKUP_DIR_LOC/%Y_%M_%D/archivelog_%U."
Backup to compressed backupset archivelog all;
output channel a1;
delete noprompt obsolete device type disk;
}
backup from the list;
output
EXPRESSIONS OF FOLKLORE

What I've done
------------------

Create a table and insert a line first (backup before): -.

create table rman_test (empname varchar2 (20), varchar2 (20)) of the city.

insert into rman_test values ('azar', 'riyadh');
insert into rman_test values ('jabar', 'chennai');
commit;

Select count (*) in the rman_test;
2 rows

Run the script of backup as follows: -.
CD/u01/scripts
SH hot_backup_db.bash emrep/u01/backup/u01/scripts
Parameter 1 - SID ORACLE
Parameter 2 - directory where will backups rman
Parameter 3 - directory where rman records go

Create a table after backup so we can verify that the data is not lost

create table rman_test1 (empname varchar2 (20));
insert into rman_test1 values ('kareem');
insert into rman_test1 values ('syed');
commit;
Select count (*) in the rman_test1;
2 rows

Stop and rename the db files to impersonate a systems crash

Closing of the database '
Rename/u01/oradata/emrep in emrep-ren

Renamed the spfile;
CD $ORACLE_HOME/dbs
MV spfileemrep.ora spfileemrep.ora_ren

Prepare for recovery

Look at the rman backuplog: -.

Search the DBID:-e, g, connected to the target database: EMREP (DBID = 4012088007)

Looking for where are the backups spfile and controlfile;
Item name: / u01/backup/2012_07_25/database_2jnh03ua_1_1
Control file included: cash SNA: 1344967 cash time: July 25, 12 16:16:10
Item name: / u01/backup/2012_07_25/database_2knh03uc_1_1
SPFILE included: Modification Date: July 25, 12 14:27:55

Note the path and the name of the backup items to the location of backup for the last backup.

Recover the database (all nuked)
----------------------------------------------------------

RMAN target /.
the value of dbid 4012088007

startup nomount

Restore spfile to ' / u01/backup/2012_07_25/database_2knh03uc_1_1 ";

Restore controlfile to ' / u01/backup/2012_07_25/database_2jnh03ua_1_1 ";
From restoration to 24/07/2012 10:32:24
using channel ORA_DISK_1
channel ORA_DISK_1: restore the control file
channel ORA_DISK_1: restore complete, duration: 00:00:01
output file name=/u01/app/oracle/product/11.2.0/dbhome_1/dbs/cntrlemrep.dbf
Finished restore at 24/07/2012 10:32:25

immediate stop
startup nomount

Restore controlfile to ' / u01/app/oracle/product/11.2.0/dbhome_/dbs/cntrlemrep.dbf';
change the editing of the database;

Catalogue backuppiece ' / u01/backup/2012_07_25/database_2hnh03u3_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/database_2inh03u3_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/database_2jnh03ua_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/database_2knh03uc_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/archivelog_2lnh03vg_1_1 ";

restore the database;

recover the database;

This experience: -.

Archives journal thread = 1 sequence = 49
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 25/07/2012 13:42:54
RMAN-06054: unknown request media recovery log archived for thread 1 with sequence 49 and from the 1330997 SNA

ALTER database open resetlogs;

Select count (*) in the rman_test;
Select count (*) in the rman_test1;

QL > select count (*) in the rman_test;
Select count (*) in the rman_test1;

COUNT (*)
----------
2

SQL > select count (*) in rman_test1
*
ERROR on line 1:
ORA-00942: table or view does not exist

How can I recover it?
Welcome to all the advice I can get. Select count (*) rman_test1 should return 2 rows.

Cheers, Rob Ford, DBA Oracle recent to rman
RMAN-06054: unknown request media recovery log archived for thread 1 with sequence 49 and from the 1330997 SNA

This sequence might not have been archived, and it could be your with the State CURRENT redolog file.

During my recovery, give the path of your redolog file RUNNING when he asks sequence 49.

SQL > restore database using backup controlfile until cancel;

Published by: renee_mathieu on July 26, 2012 14:49

Archiving logs - relocation
Good evening everyone. A bit of my environment:

E-Business R12
Oracle Enterprise DB 10.2.0.4.0

Split Architecture components:

Server 1 / DB Node (Redhat 5.5 32-bit)
2 server / applications node

My PROD database resides on a server that has the following specifications (those relevant to my post) about:

Sheet music:

/ = 1 TB of total space used 99%

/ Backup = 1.75 TB of total space 35% used

/ boot = 200 MB

The partitions ' / ' and ' / backup ' are physically different RAID volumes but on the same controller. / is an array of RAID 10 SAS drives the fastest available. /Backup is a RAID 1 array of two 1 TB mirrored SATA drives. I instance db PROD in the partition ' / backup ' keeping on safeguards on deep disk a few days since I backup and then against backups from disk to a tape backup library.

The purpose of my post is to ask for advice on what to do to get out me of the 99% used disk space on my partition condition "/" where is the Pb of PROD. My archives logs files take up to 200 GB. How it would be difficult to move these files on my partition "/ backup" and what effect or consequences that would have the performance since the will ' / backup ' have lower performance of IO and what effect will this have on the RMAN backups?

My database uses a PFILE file so I just change the archivelog destination it and bounce the DB? What would happen then to archive logs on the partition ' / '? Couuld I can just move these files to the same destination that I specified in the PFILE file?
ovlz wrote:
Thank you for your comments. I must tell you that I am relatively new to work s/n, but I was a sysadmin for a long time. In no time, I learned a lot, but I still have a way to go. At the urging of my essay, I run instead of pfile-spfile. On the PROD, I guess I got scared to make many changes because that's how the senior DBA who has contributed to the implementation done things. I did a bunch of stuff that they did; OEM, discoverer, divide the stands, etc., but I did everything quite yet. These forums are my mentor, for example, if I appreciate the help. Backups and backup strategy are not inherited something I designed, except for the part where I backup the backups on tape.

Back to point. One of my test case that is a very recent clone works PFILE. I'll change for SPFILE and try to achieve what you have mentioned - change the destination of the archive logs. Once I have change the destination, how to maintain the archive logs existing? Is this something that happens through RMAN? If I change archivelog destination box and then delete old logs archiving? Where is the size or chronological depth of the configured archive logs?

When an archivelog is written, the information on this specific archivelog are written in the control file. This means that during a recovery, if archive is required, the location, he wrote is known, even if the archivelog destination has been changed because it is written. In other words, destination of the newspaper archive shows the database where to write the new archivelogs. It is not used to tell rman where to find an archivelog existing.

' Housekeeping is done with rman '-' backup archivelog all delete input "- or a variation of that you will find in the docs. This command creates a backupset that contains a copy of the archivelogs, then deletes those that were backed up, freeing the space they occupied.

ORA-01194: file 1 needs a recovery more match
Hello

I tested on Linux Redhat 5.4 RMAN / Oracle 11.2.0.2 and had the following problems:

My configuration:

>
RMAN > show all.

Database with db_unique_name TESTDB RMAN configuration parameters are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/%F';
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/snapcf_TESTDB.f';

>

My 2 backups:

>

RMAN > list backup;

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

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
* Incr 43 0 M DISK 00:14:17 971,77 2 March 11 *.
BP key: 44 status: AVAILABLE Tablet: NO Tag: TAG20110302T062419
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66ikk_1_1
List of defined backup data files 43
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
* 1 0 incr 1001503 /CDATA/TESTDB/system01.dbf* March 2, 11
* 2 0 1001503 /CDATA/TESTDB/sysaux01.dbf* incr 2 March 11
* 3 0 incr 1001503 /CDATA/TESTDB/undotbs01.dbf* March 2, 11
* 4 0 incr 1001503 /CDATA/TESTDB/users01.dbf* March 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
* 53 full 9.36 M DISK 00:00:11 March 2, 11 *.
BP key: 58 situation: AVAILABLE Tablet: NO Tag: TAG20110302T063849
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528028017-20110302-00
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 1002272 cash time: March 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
Incr 78 0 M DISK 00:13:38 970,24 March 2, 11
BP key: 81 situation: AVAILABLE Tablet: NO Tag: TAG20110302T064449
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m66jr1_1_1
List of defined backup data files 78
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
1 0 incr 1002771 /CDATA/TESTDB/system01.dbf March 2, 11
2 0 1002771 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
3 0 incr 1002771 /CDATA/TESTDB/undotbs01.dbf March 2, 11
4 0 incr 1002771 /CDATA/TESTDB/users01.dbf March 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
93 full 9.36 M DISK 00:00:10 March 2, 11
BP key: 98 situation: AVAILABLE Tablet: NO Tag: TAG20110302T065836
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528028017-20110302-01
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 1003421 cash time: March 2, 11

RMAN >

>

I want to rebuild the database from the first backup and I always get the error:

>
RMAN > RUN
2 > {}
3 > # STARTUP NOMOUNT;
4 > # RESTORE SPFILE to ' / u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' tag "TAG20110302T063849".
5 > # SHUTDOWN IMMEDIATE;
6 > # STARTUP NOMOUNT;
7 > # RESTORE CONTROLFILE tag "TAG20110302T063849".
8 > # STARTUP MOUNT;
* 9 > SET up to this THAT SNA 1002272. *
10 > RESTORE database;
11 > RECOVER DATABASE;
12 > ALTER DATABASE OPEN RESETLOGS;
{13 >}
executing command: SET until clause

From restoration to March 2, 11
using channel ORA_DISK_1

channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_DISK_1: restore datafile 00001 to /CDATA/TESTDB/system01.dbf
channel ORA_DISK_1: restore datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
channel ORA_DISK_1: restore datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
channel ORA_DISK_1: restore datafile 00004 in /CDATA/TESTDB/users01.dbf
channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66ikk_1_1 piece reading
channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66ikk_1_1 tag = TAG20110302T062419
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:20:06
Finished restore at March 2, 11

From back to March 2, 11
using channel ORA_DISK_1

starting media recovery

Cannot find the archived log
Archives journal thread = 1 = 3 sequence
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 02/03/2011 08:06:37
RMAN-06054: unknown request media recovery log archived for thread 1 with sequence 3 and from the 1001503 SNA

RMAN > * end-of-file *.

RMAN > ALTER DATABASE OPEN RESETLOGS;

RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 02/03/2011 08:14:59
ORA-01194: file 1 needs a recovery more match
ORA-01110: data file 1: ' / CDATA/TESTDB/system01.dbf'

>

I don't know since 2 days where it's a mistake? Help, please.

Help, please!

hqt200475
concerning
Hello

Please also visit:

DATAFILE NEEDS MORE RECOVERY TO BE CONSISTENT [ID 417710.1]

Respect of
HELIOS

How recovery works after an online backup
Hello

Although conceptually tent understand how backup and restoration works, I stumbled upon a question about the hot (on-line) backup.
It is a conceptual question (I'm trying to understand how things work), is not a ' how can I do / what should I do step by step "question.

As far as I understand, an online backup of a tablespace can be done by copying files operating system place a tablespace while the database is in place and used (i.e. transactions are changing data in the database). Before the copy of the operating system starts, the Oracle RDBMS should be informed that an online backup is taken through 'ALTER '.... BEGIN "(such as additional information are written to the log again, that may be required for subsequent recovery using the backup online BACKUP). During recovery, the Oracle RDBMS uses copies of the OS as well as the line and archived files redo logs in order to rebuild all committed transactions and it uses more (uncommitted) transactions ongoing restoration UNDO tablespace.

Think about it, it seems to me that, so that it works in all possible scenarios to cancel it, information from moment has been the backup may be required. So the UNDO tablespace backup suits as well (see the explanation of this assumption below). However browsing the internet (including the Oracle online documentation) I find all instructions for the backup of the UNDO tablespace when an online backup is taken. More I couldn't understand when exactly such a backup of the UNDO tablespace must be done to ensure that the database can be retrieved in all scenarios.

I believe that the cancellation as soon as the last hot backup information can be held for example in the following scenario:
Suppose we take a backup of a given tablespace hot, i.e. we copy all files of the OS that make up this tablespace, while the database is potentially used. Either D1 one of the data files in the space of our table and let the T1 transaction change datafile D1. Allow transaction T1 still be engaged during the copy of datafile D1 are made and allow of (at least part of) T1 changes included in backup D1' D1 (because DBWR has already written the changed blocks to the moment where they have been copied to the backup). Allow transaction T1 be restored once the copy is complete. D1' will therefore include changes in T1, while D1 do not.

Now some time later, the D1 data file is lost. When you get the copy of D1 D1 ", recovery logs (archived) apply to D1. Before that, transaction T1 must be restored in the copy of D1 ", because changes to the T1 should not appear in the version retrieved from the database.
I have however not, understand the information in the statement rollback transaction T1 out exactly. It can still be in the current UNDO tablespace. I guess however that rollback information is not maintained in the UNDO tablespace forever. I see three possible answers to this
(a) there are some requirements that missed me so far for the backup UNDO tablespace whenever a hot backup is found.
(b) given that the Oracle "RDBMS" must be notified that you made an online backup, it can store all the information relevant cancellation (e.g. write it in the redo log) when the tablespace is put in backup mode.
(c) there are situations where recovery is not possible due to the "old UNDO information missing.

Answer (b) seems the most plausible to me. However, I found no confirmation of this and if (b) is really the answer, I'd be interested to understand what information is stored where by the RDMBS Oracle and how it is used for recovery.

To summarize, I have the following questions:
(I) is there any obligation to save the UNDO tablespace and an online of a tablespace backup, and if so, where is this stated in the Oracle documentation?
(II) mechanisms to ensure that uncommitted transactions can be identified the copy a tablespace online (potentially very long once the copy has been made)?
(III) you know all the links (Oracle documentation or other online resources) explaining these datails?

Thank you for any advice and answers
Kind regards
Martin
However I don't see how T cancellation of transaction information can be recovered without such a backup of the UNDO tablespace

Taking your scenario that only datafile D is lost and only this data file must be restored when the loss is discovered in time t8:

At the time the restored datafile D t9 is from t4.

However, Oracle notice now that, while the rest of the database (i.e. all the other data files) from t9, this data file is from the t4. This cannot be permitted (a data file cannot be inconsistent with the rest of the database unless it is offline). That's why Oracle requires you to RECOVER DATAFILE D.
Get it BACK then if applies to all again them (archivelogs) T4 starting until t9 that relates to this data file.
The price drop happened in the t6 is also re-played - of the redo (no cancellation). {Don't forget that again picking up all of the changes, including restorations! so the cancellation at the t6 was also captured in it again!}
For example, the data file is presented in a consistent state without having to redo cancel them.
No matter if the information contained in the cancellation had been released and crashed between t6, t8 and t9.

When Oracle made a recovery of media to a data file, there no need to cancel - media recovery does not care if the blocks are table, index, LOB, transactions, commits, restorations; It was simply a record physical of all the changes.

PS: This has nothing to do with what version you use V6 11.2
If the tablespace is called 'UNDOTBS1' or 'RBS' is irrelevant.

Hemant K Collette
http://hemantoracledba.blogspot.com

Published by: Hemant K grapple Sep 28, 2010 22:16

Published by: Hemant K grapple Sep 28, 2010 22:21

Published by: Hemant K grapple Sep 28, 2010 22:22

Size of the log file Archive
Redlogfile size is 16 MB and generating the archivelog file size is approximately 10 Mb. what could be the reason?

Oracle Version: 10.2.0.4

OS: Windows

Published by: Deccan charger 19 April 2010 23:31
First of all:

a redo log contains a lot of things necessary for instance etc. recovery an archived log is used only for the restorations - he didn't need all the stuff that is in a redo log, so when written CRA the archiving log that he does not write all knowledge, all that is required for restores

Second:

Archive logs is created with dimensions smaller, irregular, as the original redo logs. Why? [388627.1 ID]

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

Last updated 2 June 2007 Type status MODERATE HOWTO

In this Document
Goal
Solution
References

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

This document is available to you through process of rapid visibility (RaV) of the Oracle's Support and therefore was not subject to an independent technical review.

Applies to:
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1
Information in this document applies to any platform.

Goal
Archive logs is created with dimensions smaller, irregular, as the original redo logs.
Commands like:
ALTER SYSTEM SWITCH LOGFILE
or
ALTER SYSTEM ARCHIVE LOG...
are not used to generate archives or change the log file. Thus, there is no parameter ARCHIVE_LAG_TARGET set.
What else could cause this behaviour?
Solution
From:
Bug: 5450861: NEWSPAPERS ARCHIVE IS GENERATED with one SIZE SMALLER THAN THE REDO LOG FILES
the explanation of this situation has 2 main reasons:
1 archiving logs do not have to be in the same size. This was decided very long ago, when blank padding archiving logs stopped for a very good reason - in order to save disk space.

2. the log command does not exist when a redo log file is 100% full. There is an internal algorithm that determines when to switch journal. It also has a very good reason - do the command of newspaper at the last moment may incur performance problems (for various reasons, outside the scope of this note).
So, after that newspaper ordering occurs the archivers are only copying the information from the redo log files. As recovery logs are not 100% full after the command to log and archive logs are empty not filled after the copy operation is complete, this results in unequal files smaller than the original of redo log files.
This is very apparent for very low (less than 10 MB) log files; as a result, produced 2.5 MB archive logs of 5 MB recovery logs are very visible.
Just note that currently, the default log files are 100 MB in size. If the archives log files would be between 98 and 100 MB person would notice.
The main concern that one must have for newspapers of archives files is a possible corruption. This can be easily verified by attempting a resumption of testing. When it's ok, the size of the log archive uneven should be of no interest, as is expected.

RMAN recovery error? Why is it so? s ' Please help :)
Hi guys,.

First of all, 1 million of thanks and gratitude to those who are willing to spend time reading my thread and using all the less out / give suggestions.

I am very very very new for backup and restore, so I really hope that you guys will give me with your utmost patience and tolerance, if I by no risk stupid or dumb questions or if there is very direct terms that I don't apprehand...

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

Current configuration.

I have 2 database each on a different server, but the configuration of file directories are the same for both (prod, 1 stage 1)

(1) on the prod, I do a daily backup of 03:00.
(2) my full backup includes controlfile autobackup and archivelogs.
(3) after that, I'll do a RSYNC to send all items to backup to the staging server.
(3) on stage, I will / want to apply the daily backup of prod on it. I don't mind not seen the last DB (changes after 03:00 not recorded)
(4) I don't use rman catalog. If all the backup information store in the control file.

I made a backup in the RMAN LIST on production and saw all the backup information including these...

Part name: /u02/rmanbkp/STARHUB_lskv1oi0_1_1.rmanbk

List of newspapers archived in defined backup 5819
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 8910 2440140540 22 NOVEMBER 09 2440223507 22 NOVEMBER 09
1 8911 2440223507 22 NOVEMBER 09 2440363724 22 NOVEMBER 09
1 8912 2440363724 22 NOVEMBER 09 2440508680 22 NOVEMBER 09

Overhere, we are sure that the archivelogs are backed up and I don't want to apply these archivelog when I restore the database.

 please NOTE THAT the backup is on/U02/rmanbkp / 

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

Now more to STAGE, where I restore / recover (please see the BOLD characters)


RMAN > restore controlfile autobackup.

From restoration to 23 November 09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 157 devtype = DISK

channel ORA_DISK_1: looking for autobackup day: 20091123
channel ORA_DISK_1: autobackup found: / u02/rmanbkp/c-690163925-20091123-00
channel ORA_DISK_1: restore full automatic backup of control file
output filename=/u03/oradata/starhub/control02.ctl
output filename=/u01/oradata/starhub/control01.ctl
Restoration finished November 23 09

RMAN > change the editing of the database;

mounted database
output channel: ORA_DISK_1

RMAN > restore database;

From restoration to 23 November 09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 157 devtype = DISK

channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00003 to /u03/oradata/starhub/sysaux01.dbf
restoring datafile to /u03/oradata/starhub/starhub02.dbf 00006
restoring datafile 00009 to /u03/oradata/starhub/starhub05.dbf
channel ORA_DISK_1: backup /u02/rmanbkp/STARHUB_m7kv1ols_1_1.rmanbk piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u02/rmanbkp/STARHUB_m7kv1ols_1_1.rmanbk tag = TAG20091123T030220
channel ORA_DISK_1: restore complete, duration: 00:02:26
channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00001 to /u03/oradata/starhub/system01.dbf
restoring datafile 00002 to /u03/oradata/starhub/undotbs1.dbf
restoring datafile 00007 to /u03/oradata/starhub/starhub03.dbf
channel ORA_DISK_1: backup /u02/rmanbkp/STARHUB_m8kv1opp_1_1.rmanbk piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u02/rmanbkp/STARHUB_m8kv1opp_1_1.rmanbk tag = TAG20091123T030220
channel ORA_DISK_1: restore complete, duration: 00:02:26
channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00004 in /u03/oradata/starhub/tbs1.dbf
restoring datafile 00005 to /u03/oradata/starhub/starhub01.dbf
restoring datafile 00008 to /u03/oradata/starhub/starhub04.dbf
channel ORA_DISK_1: backup /u02/rmanbkp/STARHUB_m9kv1ov0_1_1.rmanbk piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u02/rmanbkp/STARHUB_m9kv1ov0_1_1.rmanbk tag = TAG20091123T030220
channel ORA_DISK_1: restore complete, duration: 00:02:15
Restoration finished November 23 09

RMAN > restore database;

From pick up to 23 November 09
using channel ORA_DISK_1

starting media recovery


Archive journal 1 sequence 8935 thread is already on the disk that the file /u01/oradata/starhub/arch/log1_8935_656935637.arc--repertoire of the OPINION it IS READING /U01/
archive log thread = 1 sequence = 8935 filename=/u01/oradata/starhub/arch/log1_8935_656935637.arc
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8936_656935637.arc thread = 1 sequence = 8936
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8937_656935637.arc thread = 1 sequence = 8937
archive log thread = 1 sequence = 8938 filename=/u01/oradata/starhub/arch/log1_8938_656935637.arc
archive log thread = 1 sequence = 8939 filename=/u01/oradata/starhub/arch/log1_8939_656935637.arc
archive log thread = 1 sequence = 8940 filename=/u01/oradata/starhub/arch/log1_8940_656935637.arc
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8941_656935637.arc thread = 1 sequence = 8941
archive log thread = 1 sequence = 8942 filename=/u01/oradata/starhub/arch/log1_8942_656935637.arc
archive log filename=/u01/oradata/starhub/arch/log1_8943_656935637.arc = 1 sequence = 8943 thread
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8944_656935637.arc thread = 1 sequence = 8944
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8945_656935637.arc thread = 1 sequence = 8945
archive log thread = 1 sequence = 8946 filename=/u01/oradata/starhub/arch/log1_8946_656935637.arc
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8947_656935637.arc thread = 1 sequence = 8947
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8948_656935637.arc thread = 1 sequence = 8948
archive log thread = 1 sequence = 8949 filename=/u01/oradata/starhub/arch/log1_8948_656935637.arc
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 23/11/2009 15:36:21
RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' / u01/oradata/starhub/arch/log1_8948_656935637.arc'
ORA-00310: archived log contains sequence 8948; 8949 sequence required
ORA-00334: archived log: ' / u01/oradata/starhub/arch/log1_8948_656935637.arc'



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

My questions are

T1) I restore the database (I see that these backup item is read from the rmanbkp/u02/and these data, the files are restored).
Now, I want to recover the database, so I think I must apply these archivelogs backup for recovery.

However, if you notice, RMAN is reading about (deprecated) /U01/ on the archivelogs instead of the archivelogs saved in /U02/rmanbkp. 

Why so much? Is this the correct behavior? How can I make RMAN uses these elements to backup archivelog on/U02/rmanbkp

Q2) that I encounter this error ORA-00310: and I get autour. It is saying that I need to use a BACK up to WHAT if I don't want this error.

However, I believe that information of hold of FILE OF CONTROL over where and how long does RETRIEVE UNTIL, isn't? (and since I'm on the CONTROL FILE of the recovery, why I always see this error?

Your kind advice/help would be really appreciated.

Best regards
Noob
Hey Noob,

A1) because the controlfile comes from the production server where the archived redologs are available in
/ U01/oradata/StarHub/Arch, you must run an overlap on the stage for the controlfile node is updated.

change archivelog than any overlap;

remove expired archivelog all;

To move forward with recovery of database until...;

A2)
You must specify a point in time, scn, or logsequence if you want to recover to a point in the past (which is what you want to do).
If you get it back until the clause, rman performs a recovery complete (up to the last committed transaction) to do this, you need the redologs online that are not backed up by rman.

Kind regards

Tycho

Recovery of archived notification

Similar Questions

Maybe you are looking for