Flashback area !!!

Can anyone tell me how clean my flashback area ???
it is full ...
regards,
george

Hello,
In fact flashback logs are automatically deleted by the database, if you delete them manually, next database startup may fail with the following error in the Alert log:
ORA-38701: Flashback database log 1 seq 1 thread 1: "string"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.So, you may do as follow:
sqlplus /nolog
connect / as sysdba
shutdown immediate
startup mount
alter database flashback off;
alter database flashback on;
alter database open;Normally, all the flashback logs will be deleted.
If you have some Restore Point, you'll have to drop them before disabling and re-enabling flashback.
For dropping Restore Point you may have a look on the following link:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/rpfbdb002.htm#CEGFIBEA
Afterwards, you may reduce the DB_FLASHBACK_RETENTION_TARGET parameter or, increase the disk space for the FRA and increase DB_RECOVERY_FILE_DEST_SIZE accordingly.
Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Jul 18, 2010 11:22 AM

Similar Messages

After resotre a database, what should do with flashback area?

After resotre a database, did a alter database open resetlog.
what should do with flashback area?

neem wrote:
what need to be done to make flashback also work functional after db restore?
for example, after db restore, you run "flash database to ....." will not work.It will not work cause after opening the database in resetlogs mode will make invalid alls database backup for that current incarnation,yours flashback logs are for previous incarnation now,and yours current incarnation cannot sense it valid ,though you can go with previous incarnation
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/flashptr006.htm#BRBSC44153[/pre
[pre]http://oraware.blogspot.com/2008/03/how-to-recover-database-with-previous.htmlKhurram

Metric Extension for Flashback area utilization monitoring

OEM:12.1.0.3
How to create a metric extension for flashback area utilization monitoring.

Also refer the below document for creating metric extension on flash recovery area.
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/metric_extension.htm#CACJABFC

Converting to flashback area

Currently I am putting my rman backups to an asm disk group RBACKUP.
If I want to convert that diskgroup to a flashback area, will I lose the backup that is currently there? I mean, does the conversion do any kind of formating of the diskgroup?

Thanks all for the confirmation, it's just as I suspected.
I would have loved this as a feature request, because logically the guaranteed restore point requires space and would halt operations to do so, whereas the normal restore point is a 'nice to have':
- save pre-upgrade database state with a guaranteed restore point pre_deploy
- do "X" transaction (upgrade, deploy, application release) successfully
- convert pre_deploy from guaranteed to normal restore
the pre_deploy save point becomes non-critical but a good thing to have in case we want to flashback to prior snapshots of specific tables or something as time goes on. As the flashback points age-off, I wouldn't want to hold the instance hostage just to keep an old flashback point which we technically wouldn't need, but may be.
My workaround solution will likely be to create TWO flashback points:
CREATE RESTORE POINT pre_deploy_guaranteed guarantee flashback database;
CREATE RESTORE POINT pre_deploy;
After the success, I delete the guaranteed one:
drop restore point pre_deploy_guaranteed;

Cleanup Flashback area

Hi,
I got a problem that the flashback area on 10g just keeps growing. The problem seems to be the flashback logs which are now using more then 300GB of spaces. The retention policy for flashback database is set for a only a few hours, setting this even lower made no difference. The flashback logs just keep growing!
What can I do to make the expired data disappear.
Note: there is nothing else in the flashback area except the logs.
thx.
Steve.

Yes, you can use following to perform cleaning
BACKUP RECOVERY AREA
CROSSCHECK
DELETE EXPIRED
there is another way of cleaning your flash recovery area (not recommended though)
reduce the value of db_recovery_file_dest_size. Make it less than the total space occupied by the flash back logs.
Hope it helps.
Rgds
Adnan

Flashback area filled. Need help

I'm getting the below error and have not clue as to what to do. How do I prevent this from happening in the future?
ERROR at line 1:
ORA-16038: log 2 sequence# 246 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: 'E:\ORACLEDATA\SILO5\REDO02.LOG'
ORA-00312: online log 2 thread 1:
'H:\ORACLE\PRODUCT\10.1.0\ORADATA\SILO5\REDO0202.LOG'

Daniel, considering that the flashback area amounts to a hot online backup then it should be configured to hold a full database backup and all archived redo log files generated between backups. This means to take full advantage of the feature you need for the flashback area to be larger than the database.
But if you cannot afford this much space you can set the db_flashback_retention_target to a shorter period of time. This will reduce the period of time that you can flashback to but it will reduce the space requirements of the feature.
HTH -- Mark D Powell --

Flashback area size

Hey,
I need a brief summary how flashback works.
Flashback is on. The destination is an ASM Storage +Flash/Flashback
These are the settings:
db_flashback_retention_target 4800 (minutes)
db_recovery_file_dest +FLASH
db_recovery_file_dest_size 147000M
But my Flashback area is filling up.
Why are the files are not deleted automatically ?
Does the parameter db_recovery_file_dest_size have any impact on that configuration.
Is it filling up to this limit until its cleanup ?
What other parameters does have an impact to the flashback area and cleanup process ?
Christian

user3930650 wrote:
Hey,
I need a brief summary how flashback works.
Flashback is on. The destination is an ASM Storage +Flash/Flashback
These are the settings:
db_flashback_retention_target 4800 (minutes)
db_recovery_file_dest +FLASH
db_recovery_file_dest_size 147000M
But my Flashback area is filling up.
Why are the files are not deleted automatically ?
Does the parameter db_recovery_file_dest_size have any impact on that configuration.
Is it filling up to this limit until its cleanup ?The retention parameter is NOT for all the files except just the flashback logs. So if you have a flashback logs available older than the retention parameter given, those would be deleted automatically. Other files are based on the retention policy that you have set for your databae which would trigget whether the files are eligible to get deleted or not. Oracle would throw an alert if the FRA is filled up to 90% of the total space but it won't increase it automatically so for that, you do need to increase the size manually.
What other parameters does have an impact to the flashback area and cleanup process ?Please see my above reply for the same.
Also, please mention your db version all the time even when you think it would be completely not required!
HTH
Aman.....

Flashback area sync

Hi guys.
I have problem with the flashback logs.
I deleted the logs with the os command and i suppose i have a problem with sinchronization
of the database and the real state on the filesystem where the flash logs are(were).
This is the output from :
select * from v$FLASH_RECOVERY_AREA_USAGE
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                86.61                         0            3422
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG              13.42                         0             106..destination
sho parameter db_recovery
NAME                                 TYPE        VALUE
db_recovery_file_dest                string      /u01/lun0/gmigr1/archcount of the files in the destination :
pwd
/u01/lun0/gmigr1/arch
find . -type f | wc -l
466and db_recovery_file_dest_size is
db_recovery_file_dest_size           big integer 350G
df -h
794G 578G 217G 73% /u01With this setup I have the entry in the alert log all the time :
ORA-19815: WARNING: db_recovery_file_dest_size of 375809638400 bytes is 100.00% used, and has 0 remaining bytes available.I try to do sync with the RMAN crosschek and delete but v$FLASH_RECOVERY_AREA_USAGE still shows the wrong status.
Maybe i didn't do it like i shoud.
Do you have any suggestions ?
DB is 10.2.0.2 on RHEL 4
Thanks,
Toni

Thanks vathomas .
I did it this way:
RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;..it appeared i had expired archive logs which coused Oracel to wrong interpret flash area usage....
thanks you for advice.
Cheers

Flashback Recovery area Full in Oracle 10g

Before the flashback recovery area is full our
Archive destination is USE_DB_RECOVERY_FILE_DEST
Our DB_RECOVERY_FILE_DEST =/S01/app/oracle/flash_recovery_area/
We got the Error:- ORA-00257
Inorder to resolve the error we changed the log_archive_dest_1='/S01/app/oracle/db/archive'
now the archive destination is changed to /S01/app/oracle/db/archive
Archive logs getting generated in the above directory from now onwards.
In the mean time i moved all the files from /S01/app/oracle/flash_recovery_area/
to diff directory.
But the below query gives still the space used is 3935.27 MB, where physically there are no files in /S01/app/oracle/flash_recovery_area/
When will these values in the query update. Is there anything i have to do to reclaim the space 3935.27 MB (in the query below). Now after reclaiming the space, i want to use the Flash Back Recovery area (/S01/app/oracle/flash_recovery_area/) for the archive logs, like a switchback to where we are initially. How to reclaim the space ? How to switch back archive logs to Flash Back Recovery Area (/S01/app/oracle/flash_recovery_area/).
Please the below report for the above conversation.
Sat May 20 page 1
Flash Recovery Area Status
Space Space Reclm
Limit Used Space
File Name (MB) (MB) (MB) Files
/S01/app/oracle/flash_recovery_a 4000.00 3935.27 3935.27 90
rea
Experts share your experience. Appreciate your reply in this regard..........
Thanks

In UNIX style environments you often don't see reclaimed space until the database is restarted. Backup the database and archivelogs and the flashback area shoudl take care of itself in future. If not, you can always delete obsolete archivelogs manually by using the DELETE command in RMAN.
To cleanup now, first you must tell RMAN that the files you've moved are no longer available:
crosscheck archivelog all;
You can then delete the obsolete archivelogs using the following RMAN command:
delete obsolete;
I'm assuming you use RMAN for all your backups :)
Cheers
Tim...

Flashback Recovery Area Usage near 100% - what happens next?

Hello,
I am fairly new to Oracle flashback. I have a database which is nearing 100% usage of the flashback area. Until now, I've just been increasing the size to delay the inevitable. I've also gone and pruned archivelogs (using OS commands) from the fra, but this does not seem to have any effect. What I wanted to know is, what will happen if I let it reach 100%. Will the database cease functioning or will it prune files that it no longer needs and free space on its own?
Thanks for any insight you can provide.

geeter wrote:
Thank you.
With respect to "how" I am using flashback, this is something that also confuses me. It seems as if "Flashback Database" has NOT been enabled, but I know that I can flashback a table within my database by enabling row movement on it. I have specified USE_DB_RECOVERY_FILE_DEST as the location to multiplex archivelogs and I use the EM dbconsole to take full backups of the database which seems to also populate a directory "autobackup" even though the backups are directed somewhere else. My guess is that I do NOT have flashback enabled in the sense you meant. I'd appreciate any clarification.To enabling flashback you have to issue ALTER DATABASE FLASHBACK command at mount stage in 10g(can at open stage in 11g) and you can check it from V$DATABASE.FLASHBACK_ON column.If it is 'YES' then that is enabled else is not.In additionally you performed FLASHBACK TABLE feature this is based on undo tablespaces(undo information and related undo settings/parameter) and nothing relationship with FLASHBACK DATABASE.

Why do we have to flashback the failed primary DB to make it the new standby ?

RDBMS Version: 11.2.0.3
Platform : RHEL 5.8
Standby Type : Physical Standby
Primary DB name : berlin
Standby DB Unique name : lisbon
Lets say berlin DB goes down due to a hardware failure so lisbon is made the Primary DB. Now lisbon is running without a standby DB.
berlin crashed --------> at SCN 4000
lisbon takes over ------> from SCN 4000 and proceeds
In the below url, some steps involving flashback are mentioned on how to make the failed primary (berlin) the new physical standby.
http://docs.oracle.com/cd/E11882_01/server.112/e25608/scenarios.htm#i1050055
berlin DB crashed at SCN 4000. So, to make berline the new physical standby , can't we just run
SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
and mount the DB and start the Redo apply ?
Why do we need to flashback the old primary DB to SCN 4000. Wasn't berlin DB already at SCN 4000 when it crashed?

Hello;
The key is the SCN must be at exactly the same point the Standby became Primary.
Generally you want to use Flashback so the "Old primary" can be at a point where it can become the new Standby. Once you are there you can use Switchover to return the Data Guard setup.
To get the correct SCN I use :
SELECT TO_CHAR(STANDBY_BECAME_PRIMARY_SCN) FAILOVER_SCN FROM V$DATABASE;
Example
SQL> FLASHBACK DATABASE TO SCN 1011295;
Flashback complete.
SQL>ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
Database altered
If you don't have flashback you can use RMAN to perform the same thing.
Best Regards
mseberg

Problem with SPACE_RECLAIMABLE in Oracle Flashback

Hi All,
I have oracle 11.2.0.3 version running. I have some queries.
Recently I am learning about flashback technology.
What my issue is that the SPACE_RECLAIMABLE column always shows 0 although there is enough space in the flashback area.
Snapshot is as below.
SQL> select * from v$recovery_file_dest;
NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
C:\app\mudassar\fast_recovery_area 4353687552 104857600 0 2
I am not able to understand why? Where is the issue?
As per my understanding this should show the space that is free..
Please guide me on same.

822922 wrote:
Hi All,
I have oracle 11.2.0.3 version running. I have some queries.
Recently I am learning about flashback technology.
What my issue is that the SPACE_RECLAIMABLE column always shows 0 although there is enough space in the flashback area.
Snapshot is as below.
SQL> select * from v$recovery_file_dest;
NAME SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
C:\app\mudassar\fast_recovery_area 4353687552 104857600 0 2
I am not able to understand why? Where is the issue?
As per my understanding this should show the space that is free..
Please guide me on same.http://docs.oracle.com/cd/E11882_01/server.112/e25513/dynviews_2125.htm#REFRN30304
{code}
SPACE_RECLAIMABLE NUMBER Total amount of disk space (in bytes) that can be created by deleting obsolete, redundant, and other low priority files from the fast recovery area
{code}
and probably
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV89614
It does not show the space that is free, it shows the space that COULD BE freed if you removed files (see the list of possible files above) from the FRA.
Cheers,

Flashback database log status

My question are
- how come the oldest_flashback_scn is 0
- how come oldest_flashback_time is empty
And I can still do "as of" query
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
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
SQL> select
2 OLDEST_FLASHBACK_SCN,
3 to_char(oldest_flashback_time,'Dy DD-Mon-YYYY HH24:MI:SS'),
4 RETENTION_TARGET,
5 FLASHBACK_SIZE,
6 ESTIMATED_FLASHBACK_SIZE
7 from v$flashback_database_log;
OLDEST_FLASHBACK_SCN TO_CHAR(OLDEST_FLASHBACK RETENTION_TARGET FLASHBACK_SIZE ESTIMATED_FLASHBACK_SIZE
0 15 151461888 67700736
SQL>
SQL> select count(*) from test1 as of scn 364263;
COUNT(*)
2097152

I've setup Flashback and was working properly. I meant to setup a very small size of flashback area and tried to make it to be filled then I get oldest flashback scn "0" from the view v$flashback_database_log. Can anyone explain this for me please?
OLDEST_FLASHBACK_SCN TO_CHAR(OLDEST_FLASHBACK
0
and it was like this
OLDEST_FLASHBACK_SCN TO_CHAR(OLDEST_FLASHBACK
545777 Thu 25-Mar-2010 16:56:27
Thanks gurus
Edited by: HenryLiu on 25/03/2010 15:16
Edited by: HenryLiu on 25/03/2010 15:21

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

How to delete archivelogs once they are applied on Physical Standby

We have 10.2.0.4 Primary and Physical Standby.
According to Note, ID 331924.1, we have
on Primary:
RMAN> SHOW ARCHIVELOG DELETION POLICY;
RMAN configuration parameters are:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
on Standby:
RMAN> SHOW ARCHIVELOG DELETION POLICY;
RMAN configuration parameters are:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
I would like to delete the archivelogs from Primary(as soon as they are applied to standby) as well as from standby and schedule a RMAN script which will run every hourly. The archivelogs are taken on flashback area.
Please guide.

Handle: chakra
Status Level: Newbie
Registered: Oct 27, 2006
Total Posts: 107
Total Questions: 56 (46 unresolved)
Name Anirban
Why so many open questions. Close the answered questions, give points and keep forum clean.
Refer the below link
Best Way to monitor standby, primary databases, including alert logs, etc.
Edited by: jazz81 on 10-May-2012 16:38

Flashback area !!!

Similar Messages

Maybe you are looking for