Oca Dba
Oca Dba
Oca Dba
Software directories syntax: Store each version of the Oracle software in a directory matching
the pattern: /pm/h/u/product/v. An OFA-compliant installation of the Oracle Database
10g version 10.2.0 looks like:
/u01/app/oracle/product/10.2.0
Naming subdirectories syntax: To facilitate the organization of administrative data, you should
store database-specific administration files in subdirectories matching the pattern:
/h/admin/d/a/. Here, h is the Oracle software owners home directory, admin is a literal,
d is the database name, and a is a subdirectory for each of the database administration files. The
following is a list of these administration file subdirectories:
adhoc: Ad hoc SQL scripts for a particular database
arch: Archived redo log files
adump: Audit files (Set the AUDIT_FILE_DEST initialization parameter to the adump
directory. Clean out this subdirectory periodically.)
Bdump: Background process trace files
Cdump: Core dump files
Create: Programs used to create the database
Exp: Database export files
Logbook: Files recording the status and history of the database
Pfile: Instance parameter files
udump: User SQL trace files
File-naming syntax: The following naming convention for database files ensures that they are
easily identifiable:
Control files: /pm/q/d/controln.ctl
Redo log files: /pm/q/d/redon.log
Data files: /pm/q/d/tn.dbf
The variables used in these file names are:
pm: A mount point name as described previously
q: A string distinguishing the Oracle data from all other files (commonly named ORACLE
or oradata)
d: The value of the initialization parameter, DB_NAME (the database name)
t: An Oracle tablespace name
n: A two-digit string
Note: Do not store files other than control files, redo log files, or data files associated with the d
database in the /pm/q/d/path.
Setting Environment Variables
ORACLE_BASE: Specifies the base of the Oracle directory structure for OFA. Use of this
is optional, but if used, this can facilitate future installations and upgrades. It is a directory
path, as shown in this example:
/u01/app/oracle
$ORACLE_BASE/product/10.2.0/db_1
NLS_LANG: Specifies the initial National Language Support (NLS) settings for a session
in the form of language_territory.character set. For example, a setting of:
AMERICAN_DENMARK.WE8MSWIN1252
You can query the actual NLS settings of your current session using:
select * from nls_session_parameters;