11g Deprecated system parameters && diag path changed

11g Deprecated system parameters with specified values:
  background_dump_dest
  user_dump_dest
 

参考 : 

 
Starting in Oracle11g we not longer have many of the original OFA file system structures and we see that the ancient
dump destination init.ora parms (core_dump_dest,  background_dump_dest, user_dump_dest) are placed by a single diagnostic_dest parameter,
the place to go when Oracle wants to take a dump. 

You can use the new initialization parameter diagnostic_dest to specify an alternative location for the diag directory contents.

New in Oracle 11g we see the new ADR (Automatic Diagnostic Repository) and Incident Packaging System, all designed to allow quick access to alert and diagnostic information.

The new $ADR_HOME directory is located by default at $ORACLE_BASE/diag, with the directories for each instance at $ORACLE_HOME/diag/$ORACLE_SID,
at the same level as the traditional bdump, udump and cdump directories and the initialization parameters background_dump_dest and user_dump_dest are deprecated in 11g.

You can use the new initialization parameter diagnostic_dest to specify an alternative location for the diag directory contents.

In 11g, each $ORACLE_HOME/diag/$ORACLE_SID directory may contain these new directories:

alert - A new alert directory for the plain text and XML versions of the alert log.
 
incident - A new directory for the incident packaging software.

incpkg - A directory for packaging an incident into a bundle.

trace - A replacement for the ancient background dump (bdump) and user dump (udump) destinations.
 
cdump - The old core dump directory retains it's 10g name.

Let's see how the 11g alert log has changed.

Alert log changes in 11g
Oracle now writes two alert logs, the traditional alert log in plain text plus a new XML formatted alert.log which is named as log.xml.

Prior to Oracle 11g, the alert log resided in $ORACLE_HOME/admin/$ORACLE_SID/bdump directory, but it now resides in the $ORACLE_BASE/diag/$ORACLE_SID directory. 

Fortunately, you can re-set it to the 10g and previous location by specifying the BDUMP location for the diagnostic_dest parameter. 

But best of all, you no longer require server access to see your alert log since it is now accessible via standard SQL using the new v$diag_info view:

select name, value from v$diag_info.