Enhance Skills Daily

October 01, 2026

Oracle DBA Lesson 24 Part 1 — Choose DBCA Identity, Container and Storage Settings

Oracle Database Configuration Assistant (DBCA) turns a database design into creation settings. This walkthrough connects the important fields: database name, instance identity, application container, database-file placement, and recovery storage.

Oracle DBA Lesson 24 Part 1 — Choose DBCA Identity, Container and Storage Settings

Screens and defaults can vary with the installed release update, template, and selected features.

Start with the intended installation and workload

Start the DBCA executable from the intended Oracle database home. After selecting the correct environment:

dbca

Select Create a database, then Advanced configuration. Advanced mode exposes the design choices. For an application that processes transactions, General Purpose or Transaction Processing supplies useful starting settings. Review and adjust them against the application requirements. See advanced-mode DBCA.

The installed executable documents its options:

dbca -help
dbca -createDatabase -help

Both examples request help. The second displays help for the creation operation. It does not start creation. Use the supplied response-file template and supported secret handling when automation is needed. Keep credentials out of shell history, process arguments, and exported configuration records.

Distinguish database identity from instance identity

DBCA fieldExampleWhat it controls
Global database nameapp.example.comThe database name with its domain.
SIDAPPThe instance identifier on this server. Confirm availability before creation.
Create as Container databaseSelectedCreates the container structure.
Number of PDBs1The number of requested user pluggable databases.
PDB nameAPP_PDBThe application pluggable database in this example.

The container database also has CDB$ROOT and PDB$SEED. The root supplies administration and common infrastructure. The seed supplies the starting template for creating PDBs. Application data belongs in the application PDB. Requesting zero user PDBs still leaves the root and seed. See creating and configuring a CDB.

Undo supports rollback and consistent reads. DBCA enables local undo by default for new CDBs. Each container uses its own undo. Confirm the effective configuration for the intended installation. See transactions and undo.

Choose physical storage and file naming

On Storage Option, choose the option to supply storage attributes: File System, a database-files destination of /u02/oradata, and Use Oracle-Managed Files.

Data files store database data on physical storage. The Oracle database software owner needs permission to write to the chosen destination. With Oracle Managed Files (OMF), the administrator chooses destinations and Oracle manages the database filenames. Confirm placement and capacity against the storage design. See Oracle Managed Files.

Set recovery location, quota, and archiving

On Fast Recovery Option, select Specify Fast Recovery Area. The location is /u03/fast_recovery_area. The recovery area can hold archived redo logs, backups, and other recovery files on disk.

The location and size are separate choices. The size entered is 20480 MBytes, conventionally representing 20 GB in Oracle's binary-unit sizing. This is a quota, not a recommended size or evidence of available capacity. Match the wizard's units and plan sufficient usable physical storage for the quota, other consumers, recovery workload, and retention policy. Separate directory names alone do not establish separate physical failure domains. See recovery area configuration.

Select Enable Archiving when archived redo is required by the recovery design. Oracle copies completed online redo into archived log files. The completed redo source and archive copy are distinct physical files. A usable backup and the required available redo support reproducing database changes after that backup. Plan retention, space, and actual backup operations.

Review the complete configuration before Finish

Network, configuration, administrative credentials, and other applicable settings still need to be completed. Memory, character sets, and the detailed remaining wizard process belong to the continuation of the creation walkthrough. The final Summary combines all selected settings. Compare it with the complete design and use Back to correct mismatches.

When Create database is selected, Finish starts physical file creation and configuration. Saving a template or generating scripts is a separate choice. Retain actual completion details and logs for later post-creation verification. See installing and creating a database with DBCA.

Recap

Start DBCA from the intended Oracle home with dbca. Select Create a database, then Advanced configuration, and review General Purpose or Transaction Processing against an application that processes transactions. dbca -help and dbca -createDatabase -help document options. The creation help does not start creation. Keep credentials out of shell history, process arguments, and exported configuration records. The global database name is app.example.com, the SID is APP, and one user PDB is named APP_PDB. CDB$ROOT and PDB$SEED remain even when zero user PDBs are requested, and application data belongs in the application PDB. DBCA enables local undo by default for a new CDB, and each container uses its own undo. Use File System storage at /u02/oradata with Use Oracle-Managed Files, so the administrator chooses destinations and Oracle manages the filenames. The fast recovery area is /u03/fast_recovery_area with a quota of 20480 MBytes. That number is not evidence of free capacity, and separate directory names do not establish separate failure domains. Select Enable Archiving when the recovery design requires archived redo. When Create database is selected, Finish starts physical file creation and configuration. Compare the Summary with the design and use Back before that point. Saving a template or generating scripts is a separate choice.

Quiz

1. Which value identifies the instance on the server?

2. If zero user PDBs are requested, is PDB$SEED absent?

3. What does Use Oracle-Managed Files change?

4. What does the fast recovery area size specify?

5. When Create database is selected, what does Finish do?

No comments:

Post a Comment

Vocabulary Revision 6 — Lessons 21 to 24

Lessons 21–24 · 16 words Watch on YouTube Contents https://www.apps-dba.com/ https://www.youtube.com/@EnhanceSkillsDaily Open ...