No editing of the SPFILE is necessary, or even possible without
corrupting the SPFILE itself.
Although you cannot mirror a parameter file or SPFILE per se, you can back up an SPFILE to an
init.ora file, and both the init.ora and the SPFILE for the Oracle instance should be backed up using
conventional operating system commands or using Recovery Manager in the case of an SPFILE.
When the DBCA is used to create a database, an SPFILE is created by default.
Alert and Trace Log Files
When things go wrong, Oracle can and often does write messages to the alert log and, in the case
of background processes or user sessions, trace log files.
The alert log file, located in the directory specified by the initialization parameter
BACKGROUND_DUMP_DEST, contains both routine status messages as well as error conditions.
When the database is started up or shut down, a message is recorded in the alert log, along with
a list of initialization parameters that are different from their default values. In addition, any alter
database or alter system commands issued by the DBA are recorded. Operations involving
tablespaces and their datafiles are recorded here, too, such as adding a tablespace, dropping a
tablespace, and adding a datafile to a tablespace. Error conditions, such as tablespaces running
out of space, corrupted redo logs, and so forth, are also recorded here.
The trace files for the Oracle instance background processes are also located in
BACKGROUND_DUMP_DEST.
Pages:
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103