{"id":1982,"date":"2021-03-02T08:00:00","date_gmt":"2021-03-02T05:00:00","guid":{"rendered":"https:\/\/www.dataplatform.gr\/?p=1982"},"modified":"2025-01-15T14:35:15","modified_gmt":"2025-01-15T11:35:15","slug":"pos-gyrname-piso-sto-chrono-mia-vasi-de","status":"publish","type":"post","link":"https:\/\/www.dataplatform.gr\/en\/pos-gyrname-piso-sto-chrono-mia-vasi-de\/","title":{"rendered":"How to Flashback an Oracle Database (Flashback Database)"},"content":{"rendered":"

In previous article<\/a> we had analyzed how to do flashback database<\/strong> in guarantee restore point<\/strong> in an Oracle database. In this article we will see how it is done through technology flashback database<\/strong> without using restore point to let's go back in time<\/strong> the database.<\/p>\n\n\n\n

What does flashback database mean?<\/h5>\n\n\n\n

The flashback database<\/strong> it belongs to the category of data protection and provides the ability to quickly return to the image that the base had at a point in time.<\/p>\n\n\n\n

But why would we want to flashback a database?<\/h5>\n\n\n\n

With its operation flashback database<\/strong> we can restore the database in a very short time in case something goes wrong without having to restore<\/strong>.<\/p>\n\n\n\n

How we activated the flashback database function<\/h2>\n\n\n\n

To begin with, we should define the size and the location we want to have flash recovery area<\/strong>. From its activation flashback database<\/strong> and then they will be created recovery files<\/strong>. As changes are made to the database, the size of these files will increase according to the size of the data that has changed.<\/p>\n\n\n\n

To set the size in gigabytes:<\/p>\n\n\n\n

alter system set DB_RECOVERY_FILE_DEST_SIZE ='megethos'G scope=both;<\/pre>\n\n\n\n
To define where the recovery files will be saved:<\/p>\n\n\n\n
alter system set db_recovery_file_dest='path';<\/pre>\n\n\n\n
We can choose up to how many minutes back we want to be able to turn the base in time. The default is one day behind (1440 minutes):<\/p>\n\n\n\n
alter system set DB_flashback_Retention_target = 'MINUTES' scope=both; <\/pre>\n\n\n\n
At this point we have to check that the base works in archived log mode, that is, that the logs are kept as archived, otherwise we will not be able to activate the flashback:<\/p>\n\n\n\n
select log_mode,flashback_on from v$database;<\/pre>\n\n\n\n
To enable flashback:<\/p>\n\n\n\n
alter database flashback on;<\/pre>\n\n\n\n
How do we restore the base to a past point in time<\/h2>\n\n\n\n
In case of single instance<\/h5>\n\n\n\n
shutdown immediate;\nstartup mount;\nflashback database to timestamp TO_TIMESTAMP( '2020-05-29 08:00:00','YYYY-MM-DD HH24:MI:SS');\nalter database open resetlogs;<\/pre>\n\n\n\n
In case of RAC (Real Application Cluster)<\/h5>\n\n\n\n
In case we have multiple instances for database (RAC) <\/strong>the base should go down and only go up an instance<\/strong> her. Accordingly, after the flashback, the instance should be downloaded and the database with all its instances should be uploaded:<\/p>\n\n\n\n
srvctl stop database -db db1 -stopoption immediate\nsrvctl start instance -db db1 -instance instance1 -startoption mount\nflashback database to timestamp TO_TIMESTAMP( '2020-05-29 08:00:00','YYYY-MM-DD HH24:MI:SS');\nalter database open resetlogs;\nsrvctl stop database -db db1 -stopoption immediate\nsrvctl start database -db db1<\/pre>\n\n\n\n
If we have many services they should be uploaded:<\/p>\n\n\n\n
srvctl start service -d db1 -s service_tade<\/pre>\n\n\n\n
Sources:<\/h2>\n\n\n\n