IntroductionIn-database archiving enables you to archive rows within a table by marking them as invisible. These invisible rows are in the database and are optimized using compression, but are not visible to an application. The data in these rows is available for compliance purposes if needed by setting a session parameter.
With in-database archiving you can store more data for a longer period of time within a single database, without compromising application performance. Archived data can be compressed to help improve backup performance, and updates to archived data can be deferred during application upgrades to improve the performance of upgrades.
To manage in-database archiving for a table, you must enable ROW ARCHIVAL for the table, manipulate the ORA_ARCHIVE_STATE hidden column of the table, and specify either ACTIVE or ALL for the ROW ARCHIVAL VISIBILITY session parameter.
Scenarioyou first create a copy of the HR.EMPLOYEES table and enable row archival on the copy. Next, you flag the archived rows in the archival enabled table. You then query the table to verify that the archived rows are not displayed unless you enable the rows to be visible for the session.
- Oracle Database 12c should be installed.
- You need a container database with a pluggable database which has the HR sample schema.
- ORACLE_HOME: /u01/app/oracle/product/12.1.0
- TNS Listener port: 1521
- Non-container database info:
- SID: noncdb
- Container database info:
- SID: cdb1, with pluggable databases pdb1, and pdb2
- SID: cdb2, with no pluggable databases
- Perform the following steps to reset your environment prior to repeating the activities covered in this OBE or starting another OBE.