Deleted guarantee restroe point (flashback database)?

Hi!
User create restore "guarantee" restore point like:
create restore point full_restore guarantee flashback database;By mistake he/her delete all flashback content. Database is shutdowned.
After trying to open, there is a know problem with flashback restore point.
All around the internet there is a hint like:
startup mount;
alter database flashback off;
alter database flashback on;
alter database open resetlogs;But here is a problem with "guarantee" restore point which doesn't allow to open the database without having flashback files that will ensure "guarantee restore point".
Oracle will rather die then not to ensure "guarantee" statement!!! All looks that this is a dead end situation!
My question is : What to do in such a situation if you do not have backup ed flashback area and content is somehow lost.
This lead to very interesting question: How danger is "guaranteed restore point" in such a cases?
Any hint or comments more then welcome.
THX
Sorry if this is not right group for asking about flashback....

'Flashback database' is a nice feature, but you should never rely on it entirely. If you've lost your flashback logs and NO regular backups are available, in case of a media crash, you are in a bad situation, because you cannot restore/recover,
Werner

Similar Messages

Unable to do flashback database!!

Hi all,
I have enabled flashback database and created a restore point with guaranteed flashback database so that i can do a flashback database. When i do a flashback database, its says it needs archivelogs to do recovery. The flashback log usually will have all modified data in a flashback log files to use it for flashbacking a database. why its asking for archivelogs when all the modified data is present in flashback log itself? kindly clarify me.
Regards,
Pradeep. V

Hi,
Flashback database required the Archive log files.
"Flashback Database is similar to conventional point-in-time recovery in its effects. It enables you to return a database to its state at a time in the recent past. Flashback Database is much faster than point-in-time recovery because it does not require restoring datafiles from backup and requires applying fewer changes from the archived redo logs."
"No file in the fast recovery area is eligible for deletion if it is required to satisfy a guaranteed restore point. However, archived redo logs required to satisfy a guaranteed restore point may be deleted after they are backed up to disk or tape. When you use the RMAN FLASHBACK DATABASE command, if the archived redo logs required to satisfy a specified guaranteed restore point are not available in the fast recovery area, then they are restored from the backups."
Ref Doc:Using Flashback Database and Restore Points
HTH

Can I use flashback database to flashback a pluggable database?

Hi All,
I created a container database and then created a pluggable database.
In the pluggable 12.1 datbase, I loaded the user data.
I performed the below
sqlplus / as sysdba;
create restore point CLEAN_DB guarantee flashback database;
And I performed the transactions on the pdb.
Now my intention is to restore to the restore point CLEAN_DB as created from the above step.
If I perform the below, will it restore my pdb to the initial state?
flashback database to restore point CLEAN_DB;
Regards,
Kamal.

Hi,
You cannot use FLASHBACK DATABASE for pluggable database.
Flashback query/versions queryis UNDO based and work in PDB’s
Flashback transaction query/flashback transactionis UNDO and REDO based and work in PDB’s
Flashback data archiveUNDO gernerated archives
Flashback table
before drop –> Rename segment name of recylebin, which is based on UNDO, work in PDB’s
flashback table to –> is UNDO based, work in PDB’s
Flashback databasedoesn’t work in PDB’s:
RMAN> flashback pluggable database prmdb01 to time "to_date('23:00 20-11-2013','hh24:mi dd-mm-yyyy')";
Starting flashback at 25-NOV-13
using channel ORA_DISK_1
using channel ORA_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of flashback command at 11/20/2013 23:00:00
RMAN-05108: Command is not supported for pluggable database
Regards
Mahir M. Quluzade
p.s. Command exists but not supporting, may be next release come support.

Create guaranteed restore point in oracle 10g RAC ASM

Hi DBAs,
In our production environment we have 2 node master RAC database (Oracle 10.2.0.5) (node1 name=master1 and node2 name=master2)
for which there is going to be a release tonight so want to create a guaranteed restore point for this RAC database.
I have googled many and found some ways, but before I implement it wanted a reviews from experts here.
Note: We already have db_recovery_file_dest set up in ASM...db_flashback_retention_target=1440 and db_recovery_file_dest_size=200GB with arch mode ON.
The steps are
STOP the RAC Database on Both Nodes...
Node1:
$srvctl stop database -d
$Srvctl stop database –d master1
Node2:
$srvctl stop database -d
$Srvctl stop database –d master2
And now start one instance only in mount state:
On node1:
SQL> startup mount
Now enable flashback on Node1...
SQL> alter database flashback on;
SQL> alter database open;
SQL>CREATE RESTORE POINT before_upgrade GUARANTEE FLASHBACK DATABASE;
Now start the second instance…
$srvctl start instance -d -i
$srvctl start instance –d master1 –d master2
Please let me know if there is something needs to be rectified.
Regards,
Ritz

The steps look fine.
Presumably you've already checked to see if the database is in flashback mode and it isn't...hence you putting it into flashbac mode?
Probably just typos but it looks like you have interchanged database names and instance names in your commands....you have the following commands. The srvctl commnds can be run from any node (ie you do not have to run it on node1 to shutdown instance1 and node2 to shutdown instance2).
Node1:    srvctl stop database –d master1
Node2:    srvctl stop database –d master2
You would run either:
Any node:    srvctl stop database -d master (assuming you database name is master...this will shut down both instances)
OR shutdown each instance individually
Any node:    srvctl stop instance -d master -i master1
Any node:    srvctl stop instance -d master -i master2
Same commnds as above to start using "srvctl start"...the following start commands do not look right to me:
srvctl start instance -d -i
srvctl start instance –d master1 –d master2

FLASHBACK Database : rman vs sql command differnces

I am new to Oracle and want understand the difference and which is the correct way of flashing back the database?
RMAN command vs SQL Command on using FLASHBACK DATABASE
SQL> FLASHBACK DATABASE TO RESTORE POINT BEFORE_ONLINE_TEST; {CODE} Vs rman> run{
     flashback database to restore point BEFORE_TEST_320130313;
     sql "alter database open resetlogs"; }
Referring this article on http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmflash.htm#BGBDCAFA it says we can use both RMAN and SQL command for database flashback.
Questions:
1. Difference between using RMAN and SQL command on database flashback?
2. When to use RMAN or SQL on the database flashback?
3. Which is the Oracle recommended or best way ?
Edited by: Sivaprasad S on Mar 15, 2013 7:26 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:26 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:27 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:27 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:28 PM
Edited by: Sivaprasad S on Mar 15, 2013 7:29 PM

When I issue the SQL Plus command of
SQL> flashback database to restore point BEFORE_TEST_20130313 ;
flashback database to restore point BEFORE_TEST_20130313
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38762: redo logs needed for SCN 87612483975 to SCN 87612485856
ORA-38761: redo log sequence 1 in thread 1, incarnation 3 could not be accessedHowever on running this on RMAN
RMAN>
list backup of archivelog scn between 87612483975 and 87612485856
RMAN> ;
starting full resync of recovery catalog
full resync complete
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
5212758 19.75M     SBT_TAPE    00:00:04     13-MAR-2013 16:36:17
        BP Key: 5212765   Status: AVAILABLE Compressed: NO Tag: TAG20130313T163611
        Handle: <TestDB_60:809973373:1>.al   Media: 945c30b6:506c6cd2:3a14:0001
List of Archived Logs in backup set 5212758
Thrd Seq     Low SCN    Low Time             Next SCN   Next Time
1    1       87612468290 13-MAR-2013 13:28:19 87612484321 13-MAR-2013 16:36:06
1    2       87612484321 13-MAR-2013 16:36:06 87612484339 13-MAR-2013 16:36:09
BS Key Size       Device Type Elapsed Time Completion Time
5212759 896.50M    SBT_TAPE    00:00:17     13-MAR-2013 16:36:30
        BP Key: 5212766   Status: AVAILABLE Compressed: NO Tag: TAG20130313T163611
        Handle: <TestDB_59:809973373:1>.al   Media: 945c30b6:506c6cbd:39f5:0001
List of Archived Logs in backup set 5212759
Thrd Seq     Low SCN    Low Time             Next SCN   Next Time
1    5       87612363812 12-MAR-2013 14:22:26 87612659040 13-MAR-2013 03:04:08
run {
allocate CHANNEL dev_2 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
allocate CHANNEL dev_3 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
allocate CHANNEL dev_4 TYPE 'SBT_TAPE' format '%U' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8)';
flashback database to restore point BEFORE_TEST_20130313;
sql "alter database open resetlogs";
release channel dev_2;
release channel dev_3;
release channel dev_4;
starting media recovery
archived log for thread 1 with sequence 2 is already on disk as file +DG_PERF_FLASH_02/TestDB/archivelog/2013_03_14/thread_1_seq_2.3612.810054205
archived log for thread 1 with sequence 3 is already on disk as file +DG_PERF_FLASH_02/TestDB/archivelog/2013_03_14/thread_1_seq_3.1588.810054205
channel dev_2: starting archived log restore to default destination
channel dev_2: restoring archived log
archived log thread=1 sequence=1
channel dev_2: reading from backup piece <TestDB_60:809973373:1>.al
channel dev_2: piece handle=<TestDB_60:809973373:1>.al tag=TAG20130313T163611
channel dev_2: restored backup piece 1
channel dev_2: restore complete, elapsed time: 00:00:46
channel dev_2: deleting archived log(s)
archived log file name=+DG_PERF_FLASH_02/TestDB/archivelog/2013_03_15/thread_1_seq_1.2969.810106317 RECID=49 STAMP=810106318
media recovery complete, elapsed time: 00:00:05
Finished flashback at 10-MAR-2013 05:32:07
database reset to incarnation 5215723
When we issue the SQL Plus command, if there is need of old database backup of archive log, how does that SQL Plus communicate with rman recovery catalog and retrieve?

Flashback database in Dataguard environment

On primary if i flashback database to a restore point, do I need to rebuild standby environment. Is there any other option. Can I flashback standby to restore point also. Can you please detail me the steps.
These I think are the steps.
1) Create Flashback database Guarantee restore point on Standby.
2) Create Flashback database Guarantee restore point on primary.
Backout
1) Flashback Database to restore point on primary.
2) Flashback Database to restore point on standby
Is it possible if we follow the above steps we dont need to rebuild the standby after flashing back the primary database.

If I flashback database to a restore point, do I need to rebuild standby environment?
No, since the standby database should be synchronized to the primary (assumes no delay) it should come along for the ride.
Can I flashback standby to restore point also?
Yes, but the retention period must be greater or equal than the Primary database retention period.
There are very few cases where you would want to do this on the standby.
For example you might use it if a RESETLOGS was used on the Primary.
Setup
Guaranteed restore points provide a complementary capability to Flashback Database.
You might set them up during an upgrade.
Ex.
CREATE RESTORE POINT before_upgrade GUARANTEE FLASHBACK DATABASE;
FLASHBACK DATABASE TO RESTORE POINT before_upgrade;
Section 5 of B14192-03 has some good information on this.
This is worth a look too:
www.oracle.com/us/solutions/sap/wp-ora4sap-flashback11g-1-303814.pdf
Queries
SELECT
NAME,
SCN,
TIME,
DATABASE_INCARNATION#,
GUARANTEE_FLASHBACK_DATABASE,
STORAGE_SIZE
FROM
V$RESTORE_POINT;
SELECT
NAME,
SCN,
STORAGE_SIZE
FROM
V$RESTORE_POINT
WHERE
GUARANTEE_FLASHBACK_DATABASE = 'YES';Best Regards
mseberg

CAN FLASHBACK DATABASE BE USED WITH E-BUSINESS?

Reason I ask is that there are a number of database segments with NOLOGGING turned on. Will this possibly cause corruption when using FLASHBACK with either normal or guaranteed restore points?
Jeff

You should probably use "force logging" init.ora param.
It's also a requirement for dataguard.

Guaranteed Restore Point

I did set a guaranteed restore point for the database which was a business requirement and after a while the database had to be bounced and then restarted. I know that the restore point will still be there. But now my concern is do I have to create a new restore point after the database restarted or will the one created before the bounce will be good if I have to restore a database?

A guaranteed restore point will stay FOREVER until you manually drop it. It will stay across restart.
But now my concern is do I have to create a new restore point after the database restarted or will the one created before the bounce will be good if I have to restore a database?I think you are missing the point of a Restore Point as opposed to a Backup.
A Restore Point is a label for a SCN. If you make a Guaranteed Restore Point, Oracle will retain the flashback logs for as long the restore point exists so it can FLASHBACK (and not RESTORE) to that SCN. You do it before you want to do a big change in database and want to have a mean to rollback the database very fast if something goes wrong. You DO NOT create Guaranteed restore points and leave it there for long time. You take a BACKUP for this purpose.
Creating a new Restore Point is unrelated to the old one and in your case looks unnecessary.

Basic question about Flashback Database

Hi,
I have a very generic question about using Flashback Database.
On my testing systems, for performance testing and simulation purposes, I want to create a guaranteed restore point so I can test impact on batch when code change releases are done, before deployment in production. My confusion is with respect to redo logs, as summarized in the questions below:
1. Is it possible to change redo log files, when a guaranteed restore point has been configured?
2. If yes, will the Flashback to restore point, also change the size of the redo logs?
I could not find anything in the docs about this....hence my question....
Appreciate your time taken in responding to these questions....
Regards.

HI,
donneskold wrote:
Hi,
I have a very generic question about using Flashback Database.
On my testing systems, for performance testing and simulation purposes, I want to create a guaranteed restore point so I can test impact on batch when code change releases are done, before deployment in production. My confusion is with respect to redo logs, as summarized in the questions below:
1. Is it possible to change redo log files, when a guaranteed restore point has been configured?
1) Yes it is possible.
2. If yes, will the Flashback to restore point, also change the size of the redo logs?
2) It will not change the size of redo log file. Cannot resize a redo log file..
I could not find anything in the docs about this....hence my question....
Appreciate your time taken in responding to these questions....
Regards.
Thank you

Guaranteed restore point Vs catdwgrd.sql downgrade for oracle 12c

I understand that we have two ways to downgrade (assuming compatible parameter is not modified) when we upgrade a 11.2.0.3 database to oracle 12c.
I am curious to know advantages of catdwgrd.sql when compared to guaranteed restore point downgrade. I think guaranteed restore point looks very simple
compared to catdwgrd.sql. Also I think oracle doesn't exactly bring the database back to the same state when we use catdwgrd.sql whereas
guranteed restore point brings us back to the same state.
Thank You
Sarayu

Which method you choose will depend on your circumstances. This blog post may help
https://blogs.oracle.com/UPGRADE/entry/is_there_a_fallback_strategy
A third possible option is to simply restore the database from backups
HTH
Srini

Deletion of Measuring points from the Notification

Hi
I have created a notication and attched manully some measuring point. (Extras-->Measuing document, New Entries and added the measuing points). I want to delete the measuring points from the notification. It displayes the msg "1 MeasDocs cannot be deleted as they already exist in the database"
Note:The measuring points are not attached to the tech object.
Please let me know how can we delete this MP's or what alternative i need to follow.
The system msg display below:
HELP msg "
1 MeasDocs cannot be deleted as they already exist in the database
     Message no. IR 018
Diagnosis
     You are trying to delete measurement documents that the system has
     already written to the database.
System Response
     The system cannot perform the function.
     You can only delete measurement documents online at the creation stage.
     Once you have saved a measurement document, you can only delete it using
     a special reorganization program."
Thanks & regards,
Mujeeb

hi
For using archiving programme take help of basis help see firstly create programme on archiving object
PM_IMRG whcih is the object for measuring document then by ebtering this prepare the archving file run in test mode
then deletion of data with date wise reading in test mode follwed afterwards.
you have to confirm the data before the deletion
Regards
chandrashekhar

Cannot enable flashback database??

I am using 10gR2 10.2.0.1
Under EM Home: it shows under " High Availability ":
Last Backup Apr 14, 2007 8:03:33 PM
Usable Flash Recovery Area (%) 92.35
Flashback Logging Disabled
When I get to the "recovery settings", I have make sure I have turned on Archivelogmode, however, the "enable flashback database" section was missing.
What's wrong about my database settings?
I have tried to explicitly do the standard code and have got the following errors:
SQL> SHUTDOWN IMMEDIATE;
SQL>STARTUP MOUNT EXCLUSIVE;
//report: obsolete/deprecated parameter specified"
SQL> ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=2800 SCOPE=BOTH;
//no error
SQL>ALTER DATABASE FLASHBACK ON;
//error: ORA-00439: feature not enabled, flashback database
Message was edited by:
gilbert.lai

Dear Satish,
The results of v$version:
BANNER
Oracle Database 10g Release 10.2.0.1.0 - Production
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
The results of v$option:
PARAMETER VALUE
Partitioning FALSE
Objects TRUE
Real Application Clusters FALSE
Advanced replication FALSE
Bit-mapped indexes FALSE
Connection multiplexing TRUE
Connection pooling TRUE
Database queuing TRUE
Incremental backup and recovery TRUE
Instead-of triggers TRUE
Parallel backup and recovery FALSE
Parallel execution FALSE
Parallel load TRUE
Point-in-time tablespace recovery FALSE
Fine-grained access control FALSE
Proxy authentication/authorization TRUE
Change Data Capture FALSE
Plan Stability TRUE
Online Index Build FALSE
Coalesce Index FALSE
Managed Standby FALSE
Materialized view rewrite FALSE
Materialized view warehouse refresh FALSE
Database resource manager FALSE
Spatial FALSE
Visual Information Retrieval FALSE
Export transportable tablespaces FALSE
Transparent Application Failover TRUE
Fast-Start Fault Recovery FALSE
Sample Scan TRUE
Duplexed backups FALSE
Java TRUE
OLAP Window Functions TRUE
Block Media Recovery FALSE
Fine-grained Auditing FALSE
Application Role FALSE
Enterprise User Security FALSE
Oracle Data Guard FALSE
Oracle Label Security FALSE
OLAP FALSE
Table compression FALSE
Join index FALSE
Trial Recovery FALSE
Data Mining FALSE
Online Redefinition FALSE
Streams Capture FALSE
File Mapping FALSE
Block Change Tracking FALSE
Flashback Table FALSE
Flashback Database FALSE
Data Mining Scoring Engine FALSE
Transparent Data Encryption FALSE
Backup Encryption FALSE
Unused Block Compression FALSE
The strange thing is that whenever I issued
startup force;
or
startup mount exclusive;
with SYSDBA privileges, it reports: "obsolete / deprecate parameters specified ", is there sth wrong with the init parameters?

Flashback Database question

I have a question about the contents of flashback logs used in Flashback Database. Oracle documentation says Flashback Logs contain 'before images' of the blocks to undo changes to a point in time just before a specified target time or SCN. Does this make flashback logs similair to blocks in Undo Segments.
Also, in some books notably one Oracle Press book for OCA (1z0-042) preparation written by Damir Bersinic, it is mentioned that flashback logs contain 'altered blocks' rather than "images of blocks before the change" mentioned in Oracle Docs. If it is 'altered blocks', then that would make flash logs similair to redo logs. which one is right?

I would agree and go with Oracle Documentation (for obvious reasons..right!). Flashback logs contains 'before images"....and you are right then it would be similar to undo changes, but undo changes are not retained are preserved for whole lot of time right? so as to allow you to go to a point in time in the past. I am sure there would be differences in how the before images in flashback logs are stored than that of undo.
Thanks
Chandra Pabba

Why arhivelogs are required for performing FLASHBACK database

Please explain. Thanks.

Documentation says :
It is similar to conventional point in time recovery in its effects, allowing you to return a database to its state at a time in the recent past.
Flashback Database is, however, much faster than point-in-time recovery, because it does not require restoring datafiles from backup and it requires applying fewer changes from the archived redo logs.
It is reason of Flashback require archivelog mode on database.
Regards
Mahir M. Quluzade

10g flashback database limitations

When are you not able to Flashback Database?
· Media failure, corruption or datafile deletion.
· The control file has been restored or recreated
· A tablespace has been dropped
· A data file has been shrunk
· A RESETLOGS operation is required.
If you dropped a schema and want it back, you can use flashback database to get it back. But if you dropped both schema and tablespace, it is not possible to get the schema back with flashback database.
Is there any other scenarios to use flashback database?
jzc

I am trying to evaluate the benefit to turn on this feature. Please drop few lines of your opinion to help me.

Deleted guarantee restroe point (flashback database)?

Similar Messages

Maybe you are looking for