The initialization parameter DIAGNOSTIC_DEST sets the base location for all diagnostic
directories; in the dw database I use throughout this chapter, the value of the parameter
DIAGNOSTIC_DEST is /u01/app/oracle. Figure 6-4 shows a typical directory structure starting
with the subdirectory /u01/app/oracle/diag.
Notice that there are separate directories for the ASM databases and the database (rdbms)
instances; within the rdbms directory, you can see the dw directory twice: the first-level directory
is the database dw, and the second dw is the instance dw. If this were a Real Application Clusters
(RAC) database, you would see each instance of the dw database under the first-level dw directory.
In fact, Oracle strongly recommends that all instances within a RAC database have the same
value for DIAGNOSTIC_DEST.
Because the location of all logging and diagnostic information is controlled by the initialization
parameter DIAGNOSTIC_DEST, the following initialization parameters are ignored:
BACKGROUND_DUMP_DEST
USER_DUMP_DEST
CORE_DUMP_DEST
?–
?–
?–
FIGURE 6-3 Alerts section on the instance home page
196 Oracle Database 11g DBA Handbook
For backward compatibility, however, you can still use these as read-only parameters to
determine the location of the alert log, trace files, and core dumps:
SQL> show parameter dump_dest
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
background_dump_dest string /u01/app/oracle/diag/rdbms/dw/
dw/trace
core_dump_dest string /u01/app/oracle/diag/rdbms/dw/
dw/cdump
user_dump_dest string /u01/app/oracle/diag/rdbms/dw/
dw/trace
You can still alter the values for these parameters, but they are ignored by ADR.
Pages:
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353