Objective: Document control-file redundancy, archive configuration, logging mode, and online redo protection using evidence from an Oracle AI Database 26ai installation report.
You are reviewing a single-instance primary CDB named GL1 before its general ledger application goes live. The application uses PDB GLPDB. Use the fictional report below to document the configuration and recommend improvements. No downloads or database changes are required.
The report is an illustrative teaching dataset, not captured output from a production database. Selected values have been organized into tables for readability. Configuration and recorded archive metadata are evidence of the reported state, not proof that every file remains readable or that recovery has been tested.
| Source | Reported value |
|---|---|
| Session container | CDB$ROOT |
| V$INSTANCE.INSTANCE_NAME / STATUS | GL1 / OPEN |
| V$DATABASE.NAME / DATABASE_ROLE / LOG_MODE | GL1 / PRIMARY / ARCHIVELOG |
| V$PDBS: GLPDB OPEN_MODE | READ WRITE |
| SHOW PARAMETER spfile | /u01/app/oracle/config/spfileGL1.ora |
| SHOW PARAMETER control_files | /u02/oradata/GL1/control01.ctl |
| V$CONTROLFILE.NAME, complete list | /u02/oradata/GL1/control01.ctl |
| SQL*Plus ARCHIVE LOG LIST: Database log mode | Archive Mode |
| SQL*Plus ARCHIVE LOG LIST: Automatic archival | Enabled |
| Parameter | Value | V$ARCHIVE_DEST status / error |
|---|---|---|
| LOG_ARCHIVE_DEST_1 | LOCATION=/u04/archive/GL1 | VALID / none reported |
| LOG_ARCHIVE_DEST_2 | LOCATION=/u05/archive/GL1 | VALID / none reported |
Both destinations are enabled. The following selected V$ARCHIVED_LOG records have ARCHIVED = YES, STATUS = A, and DELETED = NO. They share RESETLOGS_CHANGE# = 1000000.
| THREAD# | SEQUENCE# | DEST_ID | NAME |
|---|---|---|---|
| 1 | 481 | 1 | /u04/archive/GL1/arch_t1_s481.arc |
| 1 | 481 | 2 | /u05/archive/GL1/arch_t1_s481.arc |
| Group | Thread | Sequence | Size | Members | Group status / archived | Member path |
|---|---|---|---|---|---|---|
| 1 | 1 | 480 | 512 MiB | 1 | INACTIVE / YES | /u02/oradata/GL1/redo01a.log |
| 2 | 1 | 481 | 512 MiB | 1 | INACTIVE / YES | /u02/oradata/GL1/redo02a.log |
| 3 | 1 | 482 | 512 MiB | 1 | CURRENT / NO | /u02/oradata/GL1/redo03a.log |
All three member rows have TYPE = ONLINE and a null member STATUS. Null is the reported member status, not an additional health test.
Report E: Storage assessment. The storage team has verified that /u02 and /u03 are separate storage failure domains. /u03 is writable and has capacity for another member of each existing redo group. The archive destinations /u04 and /u05 are also independently protected from each other and from /u02. These are explicit facts of this scenario; different mount-point names alone would not prove independence. No workload measurements, log-switch history, or restore-test results are supplied.
Answer each question using the report. Cite the report letter and relevant view, command, or value. Your five responses form the installation record for this exercise.
This exercise is worth 10 points: up to 2 points per question. After submission, compare your answers with the model responses and rubric. The page does not automatically grade free-text answers.