This action might not be possible to undo. Are you sure you want to continue?
One (if not the, most important) jobs of the Oracle DBA is to ensure that the databases in their care are protected. Databases, or data in the database, can be lost through a variety of ways including: * User error * Hardware failure * Software failure * Disasters * Application errors To protect your database, you will need to know how to back it up and you will need to know how to recover your database. Backup and recovery is what this last chapter is all about. Backup and recovery can be a very difficult and complex topic, for there are a number of different options for you to choose from when it comes to backing up a database. In this chapter, we aim to set you on the right course, showing you how to perform basic database backup and recovery operations. In this chapter we will use the Oracle RMAN tool. It comes with the Oracle RDBMS and it¶s free. In this chapter we will cover: * Backing up your database with RMAN * Restoring your database with RMAN So, without further delay, let¶s get started on getting your database backed up.
Backup Your Database with RMAN
Database backups with RMAN are actually quite easy. Your database can be in one of two modes, ARCHIVELOG or NOARCHIVELOG mode. The mode your database is in determines what kinds of backups you can perform on your database. In this section we will cover the following topics:
The RMAN client is started from the operating system prompt. To use RMAN, simply set the Oracle environment as you would before you use any other Oracle client (like SQL*Plus). Once the environment is set, then you start RMAN as seen in this example:
rman target=/ Once you have started RMAN you will find yourself at the RMAN prompt. We are then ready to begin our database backup.
Perform an Offline (Cold) Backup of your Database with RMAN
In this section we will show you how to perform an offline (or cold) backup using RMAN. This will require that the database be down (that¶s why it¶s called an offline backup). Oracle supports online backups also, and we will be covering these shortly. Before we can use RMAN we need to configure a few settings. In this section we will look at configuring the database for our backup, and then we will proceed to do the backup.
Configure Oracle and RMAN for Backup
Before we can use RMAN we will need to configure a few settings. In this section we will assume: 1. That you will be backing up to a file system called /u01/app/oracle/backup. You will need to create this file system if it does not already exist. 2. That you are using an SPFILE. Note that if you created your database as we described earlier in the book, you should already be using an SPFILE. The configuration is pretty basic. First, we need to configure a couple of database parameters. These parameters will configure the Flash Recovery Area of the database. This is the location that all the disk backups will be made to. To configure the flash recovery area we will use the alter system command to set the value of two database parameters: * db_recovery_file_dest ± Determines the location of the flash recovery area. * db_recovery_file_dest_size ± Determines how much space can be used by Oracle in the flash recovery area. We will configure the flash recovery area to the value of /u01/app/oracle/backup, and we will assign it a 2 Gigabyte limit. Note! Oracle flash recovery area re-named to fast recovery area You may need to assign your flash recovery area more space depending on the following factors: * The size of your database
-. This assumes your database is using a SPFILE which we discussed in earlier chapters: Alter system set db_recovery_file_dest=¶/u01/app/oracle/backup¶. Oracle 10g New Features: Flashback and RMAN Oracle 10g New Features: Flashback and RMAN. We will also want to set a couple of RMAN settings before we do our first backup. Now that RMAN and the database are configured. see my notes on the different backup types and the differences between incremental cumulative and incremental differential backups. Start RMAN as detailed earlier in this section with: $ rman target / Now. Here is an example of configuring the flash recovery area for the settlings listed previously. RMAN>configure controlfile autobackup on. we are ready to proceed to backup the database. RMAN> configure retention policy to redundancy 2. Alter system set db_recovery_file_dest_size=2G.Configure the retention policy to redundancy of 2. we can use the RMAN configure command to configure these settings as seen in this example: -. Also.This means RMAN will try to keep 2 copies of the database backups. -.Configure automated backups of the control file and SPFILE. * Retention policy to a redundancy of 2 Next.* The number of backups you want to keep * If you are running your database in ARCHIVELOG mode (which we will discuss later in this chapter). . we want to configure the following: * Automatic backups of the control file and SPFILE.
This in turn lets you restore full resiliency after a failure more quickly.Oracle now provides a way to restore tables that were dropped accidentally. Madhu Tumma and Daniel Liu. published by Rampant TechPress. You can do this by using the SQL statement FLASHBACK DATABASE to roll back the primary database in time to synchronize with the standby database.This feature reduces the need to reinstantiate the old primary database following a failover. You no longer need to specify a log apply delay. because you do not need to restore the backups. flashback functionalities provide fast and flexible data recovery. . This results in much less downtime following data corruption or human error. This operation is fast. Here is a list of extended flashback features: Flashback Database . Flashback Drop . Flashback Standby Database . When physical or media corruption occurs in the database. It allows you to quickly bring your database to a prior point in time by undoing all of the changes that have taken place since that time.from the bestselling Oracle10g book Oracle Database 10g New Features by Mike Ault.This feature introduces the FLASHBACK DATABASE statement in SQL. RMAN delivers an improved and simplified recovery method. When user errors and logical corruptions occur in the database. Two improvements have been made in the backup and recovery areas in Oracle 10g. Flashback Reinstantiation . because you can now roll back the standby database if an error occurs on the primary and is propagated to the standby.This feature introduces the FLASHBACK TABLE statement in SQL.This feature improves the switchover and failover time of a standby database. Flashback Table .
The Recovery Manager (RMAN) BACKUP command has been enhanced to perform image copy backups at the database.Image backups provide fast recovery by being readily usable. because you do not always have to back up the whole database. This is an . because fewer logs need to be applied. you can diagnose problems. This results in reduced recovery time.You no longer have to backup your database following an incomplete recovery or an OPEN RESETLOGS operation. Here is a list of enhanced RMAN features: Automated Channel Failover for Backup and Restore . and datafile level. and reduced time to back up the database. Flashback Row History . Simplified Backups to Disk . Flashback Transaction History .This feature enhances RMAN recovery by automatically creating and recovering datafiles that have never been backed up.which lets you quickly recover a table to a previous point in time without restoring a backup. Automated File Creation During Recovery .This feature lets you examine changes to the database at the transaction level. tablespace. Incrementally Updated Backups . Proxy Copy Backup of Archivelogs .Recovery Manager (RMAN) now automatically retries a failed backup or restore operation.You can now apply a Recovery Manager (RMAN) incremental backup to a datafile image backup. Simplified Recovery Through Resetlogs .You can now back up archive logs by using the Recovery Manager (RMAN) Proxy Copy. and audit transactions. reducing the risk of stranding you without a backup of the Oracle database because of an error. perform analysis.Using undo data stored in the database. you can now view the changes to one or more rows along with all the metadata of the changes. With flashback transaction history.
Full Database Begin Backup Command .By using a new type of log file to track blocks that have changed in the database.This feature automatically creates the auxiliary instance needed to perform tablespace point-in-time recovery (TSPITR) and incorporates the RMAN TSPITR operations.enabling feature for Flashback Reinstantiation.The new DROP DATABASE and UNREGISTER DATABASE RMAN commands remove the database and its entry from the RMAN recovery catalog. archivelogs. If a backup is overwritten .It is no longer necessary to issue a separate command to place each tablespace in hot backup mode. Simplified Recovery Manager Cataloging of Backup Files .This release supports automated disk-based backup and recovery. the amount of data scanned is proportional to the amount of data changed. which reduces the time needed to restore a file from tape. Also. You can now use the ALTER DATABASE statement to place all tablespaces in backup mode. and any other files needed for Oracle recovery. Recovery Manager (RMAN) can avoid scanning the entire datafile during an incremental backup. The result is a simplified and unified storage location for backups.You can now catalog RMAN proprietary backup metadata into a backup repository. It reduces the risk of an out-of-space condition on disk by deleting files that are no longer necessary for successful database recovery. Instead. Change-Aware Incremental Backups . It also provides automatic deletion of the files after they have been successfully backed up by RMAN. Automated Disk-Based Backup and Recovery . Changes to the ALTER DATABASE END BACKUP Command . the BEGIN BACKUP command now runs faster than before. and the equivalent of a disk cache for tape.You can issue the ALTER DATABASE END BACKUP command when the database is open. RMAN Database Dropping and Deregistration . Automated TSPITR Instantiation .
a new RVWR background process is started. not the size of the database. Flashback Database Flashback Database is faster than traditional point-in-time recovery. The new process writes Flashback Database data to the Flashback Database logs.in the control file. the flashback functionality has been greatly extended. Flashback Database is implemented using a new type of log file called Flashback Database logs. The Oracle database server periodically logs before images of data blocks in the Flashback Database logs. The time to restore a database is proportional to the number of changes that need to be backed out. Flashback Database reduces the time required to recover the database to a previous point. . Traditional recovery uses redo log files and backups. Extended Flashback Functions In Oracle 10g. This process is similar to the LGWR (log writer) process. The data block images are used to quickly back out changes to the database during Flashback Database. then you can easily uncatalog the backup metadata from the repository. or a backup file is moved to a new location on disk. RVWR Background Process When Flashback Database is enabled.
Open the database in MOUNT EXCLUSIVE mode and turn on the flashback feature: .Figure 12. Make sure the database is in archive mode. Configure the recovery area by setting the two parameters: . 2. $ ps -ef | grep grid oracle 25124 oracle 25116 oracle 25169 oracle 25112 oracle 25110 oracle 25108 oracle 25114 oracle 25118 oracle 25120 oracle 25122 oracle 25106 1 1 1 1 1 1 1 1 1 1 1 0 16:32:05 ? 0 16:32:04 ? 0 16:32:22 ? 0 16:32:04 ? 0 16:32:04 ? 0 16:32:04 ? 0 16:32:04 ? 0 16:32:04 ? 0 16:32:04 ? 0 16:32:04 ? 0 16:32:04 ? 0:00 ora_s000_grid 0:00 ora_reco_grid 0:00 ora_rvwr_grid 0:00 ora_ckpt_grid 0:00 ora_lgwr_grid 0:00 ora_dbw0_grid 0:00 ora_smon_grid 0:00 ora_cjq0_grid 0:00 ora_rbal_grid 0:00 ora_d000_grid 0:00 ora_pmon_grid Enabling Flashback Database You can enable Flashback Database using the following steps: 1.db_recovery_file_dest .1 RVWR Background process and Flashback Database Logs The list below shows all the background processes for the 'grid' instance.db_recovery_file_dest_size 3.
10. YES FLASHBACK_ON -----------SQL> select flashback_on 2 from v$database. Determine if Flashback Database is enabled: 7. 5. 11. 8.2 Disabling Flashback Database in Enterprise Manager Monitoring Flashback Database . SQL> ALTER DATABASE FLASHBACK ON. SQL> STARTUP MOUNT EXCLUSIVE.4. Set the Flashback Database retention target: .db_flashback_retention_target 6. Disabling Flashback Database Issue the following command to disable Flashback Database: SQL> ALTER DATABASE FLASHBACK OFF. 9. You can also perform the same task in Enterprise Manger: Figure 12.
flashback_data. BEGIN_TIME FLASHBACK_DATA DB_DATA REDO_DATA ESTIMATED_FLASHBACK_SIZE -------------------.------------------ . redo_data. You can use the v$flashback_database_log to monitor the Flashback Database retention target.-------------.---------------.-------------.---------.-----------------------Oct 08 2003 14:17:34 753664 5324800 970752 0 Oct 08 2003 13:17:32 1720320 4751360 3124224 21749760 Oct 08 2003 12:17:31 1802240 4833280 3168256 21774336 Oct 08 2003 11:17:28 1867776 4587520 3146752 21774336 Oct 08 2003 10:17:24 1835008 4800512 3115008 21749760 Oct 08 2003 09:17:22 1785856 4702208 3120128 21749760 Oct 08 2003 08:17:17 1703936 4571136 3102720 21749760 Oct 08 2003 07:17:14 2768896 5767168 3237888 21798912 Oct 08 2003 06:17:11 1753088 4636672 3142656 21479424 Oct 08 2003 04:47:09 2686976 7143424 4862976 21479424 Oct 08 2003 03:47:05 1703936 4685824 3145728 21479424 Oct 08 2003 02:46:57 1785856 4653056 3137536 21528576 Oct 08 2003 01:46:52 1785856 4620288 3107840 21528576 Oct 08 2003 00:46:47 1769472 4964352 3245056 21528576 Oct 07 2003 23:46:44 1720320 4587520 3130368 21528576 Oct 07 2003 22:46:40 1769472 4669440 3112960 21577728 Oct 07 2003 21:46:38 1703936 4800512 3161088 21577728 Oct 07 2003 20:46:35 1785856 4653056 3155968 21626880 Oct 07 2003 19:46:30 1802240 4784128 3164160 21651456 Oct 07 2003 18:46:28 1753088 4685824 3120128 21528576 Oct 07 2003 17:46:26 1687552 4718592 3143680 21553152 Oct 07 2003 16:46:24 1851392 4603904 3120128 21577728 Oct 07 2003 15:46:21 1720320 4816896 3154944 21577728 Oct 07 2003 14:46:18 1736704 4587520 3196928 21577728 Oct 07 2003 13:46:16 1736704 4685824 3194880 21602304 25 rows selected.--------------------. OLDEST_FLASHBACK_SCN OLDEST_FLASHBACK_TIME RETENTION_TARGET FLASHBACK_SIZE EST_FLASHBACK_SIZE -------------------.---------. SQL> select * 2 from v$flashback_database_log. ESTIMATED_FLASHBACK_SIZE v$flashback_database_stat.The following displays a selection of the Flashback Database logs: SQL> select begin_time. 2 3 from db_data.
Flashback Standby Database If you have multiple standby sites. the first scenario in the diagram below has only one standby database. ESTIMATED_FLASHBACK_SIZE -----------------------21823488 Example 1: Flashback a Database using RMAN RMAN> FLASHBACK DATABASE 2> TO TIME = TO_DATE 3> ('06/25/03 12:00:00'. . For example. Example 2: Flashback a database using SQL command The database must be in mount state to issue these commands: SQL> FLASHBACK DATABASE TO TIMESTAMP (SYSDATE . You must issue the following command afterwards: SQL> ALTER DATABASE RESETLOGS.5/24).'MM/DD/YY HH:MI:SS'). SQL> FLASHBACK DATABASE TO SCN 76239.2. Here. You can also use the v$flashback_database_log view to assist in adjusting the recovery area disk quota: SQL> select estimated_flashback_size 2 from v$flashback_database_log. you may utilize the DELAY option in Data Guard to prevent physical/logical corruption or user errors in your primary database.2029E+12 Oct 06 2003 09:44:42 1440 48316416 21774336 Note: The default flashback retention time is 1400 minutes.
3 Using Flashback Database in a Standby Database Configuration However. Figure 12. you can configure the standby database with Flashback Database to achieve the same benefit as the DELAY option. there is no need to implement a second standby database with the DELAY option. This will prevent the corruptions on the second standby database and allow recovery from a possible physical/logical corruption or user errors in the primary database. To avoid such a pitfall. in Oracle 10g. you can implement a second standby database with the 'Delay' option (introducing a delay of minutes or hours on the second standby database for applying archive log changes). You can issue the following command to accomplish this: SQL> alter database recover managed standby database delay 60 disconnect.a logical or physical corruption in the primary database will cause an immediate corruption in the standby database. . Therefore.
Figure 12. This operation invalidates the old primary database. a failover operation leads to a resetlogs. and then re-create a new standby database. and your new primary database is vulnerable during this period. On your new primary database (Instance B): SQL> select standby_became_primary_scn from v$database. This is accomplished by using the SQL statement FLASHBACK DATABASE to roll back the old primary database in time to synchronize with the old standby database. The new Flashback Re-instantiation feature reduces the need to reinstantiate the old primary database following a failover. STANDBY_BECAME_P . This feature allows you to quickly restore full resiliency after a failure. you need to perform a hot backup on the new primary database immediately.4 Flashback Re-instantiation of Standby Database Here are the steps to perform Flashback Re-instantiation: 1. Therefore.Flashback Re-instantiation In an Oracle9i Data Guard environment. This operation can take a long time.
---------------2960985 2. Flashback the old primary database (Instance A) to the SCN. SQL> alter database flashback on. The Managed Recovery process (MRP) will hit the End-Of-Redo and then need to be restarted. Shutdown the old primary database (Instance A). 10. Enable transport from the new primary database (Instance B) SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE. On the new standby database (Instance A).ctl 7. 4. 8. a DROP command places the object in the recycle bin. The extents allocated . SQL> startup mount. 5. In Oracle 10g. Bring up the old primary database as a new physical standby database (Instance A). On the old primary database (Instance A). create a standby control file. Turn flashback back on the new primary database (Instance A). 6. SQL> shutdown immediate.f' reuse.f /u02/oradata/sid/control01. and replace the control files with the new standby control files.ctl $ cp /dba/standby/stbyct. start real time apply. Disable Flashback on the old primary database (Instance A). $ cp /dba/standby/stbyct. 9. 11. Mount the old primary database (Instance A). SQL> alter database create standby controlfile as'/dba/standby/stbycf. Flashback Drop Prior to Oracle 10g.f /u02/oradata/sid/control02. SQL> RECOVER MANAGED STANDBY DATABASE using current logfile DISCONNECT. SQL> STARTUP MOUNT 3. SQL> RECOVER MANAGED STANDBY DATABASE using current logfile DISCONNECT. a DROP command permanently removed objects from the database. SQL> flashback database to scn 2960985. SQL> ALTER DATABASE FLASHBACK OFF.
the name of the object is changed when it is dropped and moved to the recycle bin.to the segment are not reallocated until you purge the object. it has minimum impact to other database users. The recycle bin also keeps the original name of the object. Table created.You permanently drop them with the PURGE command.dba_recyclebin . no rows selected SQL> drop table test.lists all dropped system-wide objects Example 1: Dropping an Object In the example below. This feature eliminates the need to perform a point-in-time recovery operation. original_name.There is no room in the tablespace for new rows or updates to existing rows. type from user_recyclebin.The tablespace needs to be extended. This feature allows you to create a new object of the same name and then drop it again. . . . Therefore. You can view the dropped objects in the recycle bin from two dictionary views: . SQL> create table test (col_a varchar(4)). . . SQL> select object_name. Recycle Bin A recycle bin contains all the dropped database objects until. You can restore the object from the recycle bin at any time.lists all dropped user objects .user_recyclebin .Recover the dropped objects with the UNDROP command.
SQL> select object_name.---------------RB$$42513$TABLE$0 TEST TYPE -----------------TABLE SQL> create table test (col_b varchar(4)).Table dropped.---------------RB$$42513$TABLE$0 TEST TYPE -----------------TABLE SQL> drop table test. ORIGINAL_NAME TYPE --------------------------------TEST TABLE TEST TABLE Example 2: Restoring a Dropped Object This example will restore a dropped table test. . OBJECT_NAME ORIGINAL_NAME -----------------------. OBJECT_NAME -----------------------RB$$42513$TABLE$0 RB$$42514$TABLE$0 original_name. type from user_recyclebin. type from user_recyclebin. type from user_recyclebin. OBJECT_NAME ORIGINAL_NAME -----------------------. SQL> select object_name. original_name. original_name. Table created. SQL> flashback table RB$$42514$TABLE$0 to before drop. SQL> select object_name. Table dropped. Flashback complete.
Recyclebin purged. Example 5: Purging the Recycle Bin This statement purges the user recycle bin: SQL> purge recyclebin. Objects in the recycle bin of tablespace users will be purged: SQL> drop tablespace users. SQL> drop tablespace users including contents. This statement removes the table permanently: SQL> purge table RB$$42514$TABLE$0. objects in the tablespace users are dropped.Example 3: Dropping a Table Permanently This statement puts the table in the recycle bin: SQL> drop table test purge. When you issue this command. Table purged. DBA Recyclebin purged. Any objects in the recycle bin belonging to the tablespace users are purged. They are not placed in the recycle bin. Example 4: Dropping a Tablespace You can only issue this command when the tablespace users is empty. This statement removes all objects from the recycle bin: SQL> purge dba_recyclebin. .
DROP PARTITION . Flashback Table Flashback Table allows you to recover a table or tables to a specific point in time without restoring a backup... When you use the Flashback Table feature to restore a table to a specific point in time. deletes. constraints. However.ALTER TABLE .Materialized views .Remote tables (via database link) Flashback Table is extremely useful when a user accidentally inserts. such as indexes.System tables . It provides a way for users to easily and quickly recover a table to a previous point in time.Tables that are part of a cluster .CREATE CLUSTER . if the following DDL commands are issued. or updates the wrong rows in a table.Partitions of a table . and triggers will be restored.Advanced Queuing tables . Tablespace purged.This statement purges all objects from tablespace users in the recycle bin: SQL> purge tablespace users.Static data dictionary tables .ALTER TABLE .. the flashback table command does not work: . all associated objects.. Flashback Table operations are not valid for the following object types: . DROP COLUMN .
Guaranteed Retention When an active transaction uses all the available undo tablespace.. Example 2: Flashback Table using TIMESTAMP .dbf' SIZE 1 G RETENTION GUARANTEE. Example 1: Flashback Table using SCN This statement brings a table 'billing' back to a certain SCN number. Flashback Table Privileges You must have the FLASHBACK TABLE or FLASHBACK ANY TABLE system privilege to use the Flashback Table feature. You can use the parameter undo_retention to set the amount of time you want undo information retained in the database. issue the following command: CREATE UNDO TABLEAPCE undo_tbs DATAFIEL '/u02/oradata/grid/undo_tbs01.. table row movement must be enabled as a prerequisite: SQL> FLASHBACK TABLE billing TO SCN 76230. To create an undo tablespace with the RETENTION GUARANTEE option.. unless you have specified RETENTION GUARANTEE for the tablespace. the system will start reusing undo space that would have been retained.TRUNCATE TABLE .ALTER TABLE . MOVE undo_retention Parameter Data used to recover a table is stored in the undo tablespace.
This statement brings a table 'billing' back to a certain timestamp: SQL> FLASHBACK TABLE billing TO TIMESTAMP TO_TIMESTAMP('06/25/03 12:00:00'. SQL> commit. This type of query is called Flashback Row History. You can now retrieve all versions of the rows that exist or ever existed between the time the query was issued and a point back in time. Flashback Row History Flashback Query was first introduced in Oracle9i to provide a way to view historical data. SQL> update emp set salary = 3000 where name = 'DANIEL'.2)).'MM/DD/YY HH:MI:SS').2000). You can use the VERSIONS BETWEEN clauses to retrieve all historical data related to a row. Let's take a look at the example below: SQL> create table emp (name varchar2(10). Commit complete. Table created. salary number(8. this feature has been extended. SQL> commit. 1 row created. . 1 row updated. In Oracle 10g. SQL> insert into emp values ('DANIEL'.
you may not be able to see all the row histories. NAME SALARY ---------.---------DANIEL 3000 DANIEL 2000 As you can see. If a new transaction needs to use undo space and there is not enough free space left. . You can use the transaction ID obtained from Flashback Row History to perform transaction mining using LogMiner or Flashback Transaction History (see next section) to obtain additional information about the transaction. SQL> select * from emp. you cannot use the VERSION BETWEEN clause in a view definition. NAME SALARY ---------.Commit complete. the Flashback Row History feature retrieves all committed occurrences of the row. The row history data is stored in the undo tablespace. In addition. You can use the clause in a SELECT statement against a view. you can set the undo tablespace option to RETENTION GUARANTEE to retain all row histories. The VERSION BETWEEN clause does not change the query plan. any undo information older than the specified undo retention period will be overwritten. It provides you with a way to view and repair historical data. Therefore. The undo_retention initialization parameter specifies how long the database will keep the committed undo information. it also provides a new way to audit the rows of a table and retrieve information about the transactions that changed the rows.---------DANIEL 3000 SQL> select * from emp versions between scn minvalue and maxvalue. However. However.
TABLESPACE_NAME -----------------------------SYSTEM UNDOTBS1 SYSAUX TEMP EXAMPLE USERS RETENTION ----------NOT APPLY NOGUARANTEE NOT APPLY NOT APPLY NOT APPLY NOT APPLY 6 rows selected. The Flashback Transaction History provides a faster way to undo a transaction than LogMiner.-------. You can retrieve the transaction history from dba_transaction_query view: SQL> desc dba_transaction_query Name Null? Type -----------------------------------.To verify the retention value for the tablespace.---------------XID START_SCN START_TIMESTAMP COMMIT_SCN COMMIT_TIMESTAMP LOGON_USER UNDO_CHANGE# OPERATION TABLE_NAME TABLE_OWNER ROW_ID RAW(8) NUMBER DATE NUMBER DATE VARCHAR2(30) NUMBER VARCHAR2(32) VARCHAR2(256) VARCHAR2(32) VARCHAR2(19) . You can also use this feature to audit user and application transactions. you can issue the following statement: SQL> select tablespace_name. You can use this feature in conjunction with the Flash Row History feature to roll back the changes made by a transaction. It allows you to diagnose problems in your database and perform analysis and audit transactions. retention 2 From dba_tablespaces. Flashback Transaction History The Flashback Transaction History feature provides a way to view changes made to the database at the transaction level.
Mike has priced his collection of 465 scripts at $39. one of the world's most widely-read Oracle experts.rampant-books. The above is an excerpt from the bestselling Oracle10g book Oracle Database 10g New Features by Mike Ault. This is the definitive collection of Oracle monitoring and tuning scripts.UNDO_SQL VARCHAR2(4000) SQL> select versions_xid. Mike Ault. has finally consented to release his complete collection of more than 450 Oracle scripts. name. salary 2 from emp 3 versions between scn minvalue and maxvalue.---------0003000E00000FE2 DANIEL 3000 DANIEL 2000 SQL> select * 2 from dba_transaction_query 3 where xid = '0003000E00000FE2'.htm . You can download them immediately at this link: http://www.95. VERSIONS_XID NAME SALARY ---------------. and it would take thousands of hours to re-create this vast arsenal of scripts from scratch. less than a dime per script. published by Rampant TechPress.com/download_adv_mon_tuning.---------. Madhu Tumma and Daniel Liu. covering every possible area of Oracle administration and management.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.