Which two are prerequisites for setting up Flashback Data Archive?
Which two are prerequisites for setting up Flashback Data Archive?
To set up Flashback Data Archive, Automatic Undo Management must be enabled because it ensures that undo data is managed automatically without user intervention, which is necessary for Flashback operations. Additionally, the tablespace in which the Flashback Data Archive is created should have Automatic Segment Space Management (ASSM) enabled because ASSM provides efficient space management and is required for the storage and management of historical data in Flashback Data Archives.
You wish to create jobs to satisfy these requirements:
1. Automatically bulk load data from a flat file.
2.Rebuild indexes on the SALES table after completion of the bulk load.
How would you create these jobs?
The best method to create jobs that interact and have dependencies on each other, like an automatic bulk data load followed by an index rebuild, is to use Scheduler raised events. Scheduler raised events provide built-in mechanisms to handle job dependencies and event-driven scheduling, ensuring that tasks are executed in a specific sequence, such as rebuilding indexes only after the bulk load job completes successfully. Using Scheduler raised events for both tasks simplifies the process and ensures proper coordination between the jobs.
In your database, the tbs percent used parameter is set to 60 and the tbs percent free parameter is set to 20.
Which two storage-tiering actions might be automated when using Information Lifecycle Management (ILM) to automate data movement?
When using Information Lifecycle Management (ILM) to automate data movement, the movement of segments to a tablespace with a higher degree of compression on a different storage tier when the source tablespace exceeds a certain threshold is a typical action (option A). Setting the target tablespace to read-only after the segments are moved (option B) can also be a part of the process, ensuring that data is no longer modifiable and potentially optimizing performance and storage use.
You create a table with the period for clause to enable the use of the Temporal Validity feature of Oracle Database 12c.
Examine the table definition:
create table employees
(empno number, salary number,
deptid number, name varchar2(100),
period for employee_time);
Which three statements are true concerning the use of the Valid Time Temporal feature for the EMPLOYEES table?
The Temporal Validity feature in Oracle Database 12c allows for valid time periods to be managed in tables. When a table is created with the 'period for' clause, the valid time columns are automatically created. Therefore, the valid time columns employee_time_start and employee_time_end are automatically created. The same statement can filter on both transaction time and valid temporal time by using the AS OF TIMESTAMP and PERIOD FOR clauses. However, the valid time columns are not populated by the Oracle Server automatically; they must be populated by the application or process managing the data. The visibility settings for DML operations are managed by DBMS_FLASHBACK_ARCHIVE and do not directly relate to valid time temporal operations for static table descriptions.
Which two statements are true when row-archival management is enabled?
When row-archival management is enabled, the visibility of the ORA_ARCHIVE_STATE column is controlled by the row archival visibility session parameter. This means that whether or not this column is visible depends on the setting of a specific session parameter designed for this purpose. Additionally, the ORA_ARCHIVE_STATE column is updated manually or by a program that references activity tracking columns to indicate that a row is no longer considered active, making it possible for users to manage the archival status of rows based on certain criteria or actions.