Location: Database

Discussion: Oracle 11g and the new DIAGNOSTIC_DEST parameterReported This is a featured thread

Category: Discussion Forum / General Discussion
Showing 4 posts
pierre.frances
pierre.frances
Oracle 11g and the new DIAGNOSTIC_DEST parameter
Nov 9 2007, 5:39 AM EST | Post edited: Nov 9 2007, 5:39 AM EST
hi all,

I would like to discuss about the new diagnostic_dest parameter.

It could be a good idea but i am surprised that it can't be possible to keep old dump parameters as deprecated parameters (they are directly obsolete parameters in 11g).

Most of dba startup/shutdowns & supervision scripts parse the alert.log file to return an exit code. So they need to be changed during the migration.

It seems that Oracle developpement teams didn't feel that this new feature has serious consequencies on production database. 0  out of 4 found this valuable. Do you?    

aryndin
1. RE: Oracle 11g and the new DIAGNOSTIC_DEST parameter
Nov 9 2007, 9:16 AM EST | Post edited: Nov 9 2007, 9:16 AM EST
Hello!

How you scripts use old parameters BACKGROUND_DUMP_DEST?
Oracle writes two versions of alert file: new xml and old plain text file.

Bye 1  out of 5 found this valuable. Do you?    
pierre.frances
pierre.frances
2. RE: Oracle 11g and the new DIAGNOSTIC_DEST parameter
Nov 9 2007, 10:12 AM EST | Post edited: Nov 9 2007, 10:12 AM EST
yes they are.

I don't know a better solution to know if for example a database is really open without issue.
For this, i search the line "alter database open" in last lines of the alert.log and then if i get it, i return 0 for the exit code.

I have changed scripts for 11g and now they are using the new directory for alert.log.

But now, i need to maintain two version of my scripts, one for 9i&10g, and one for 11g.... :-(
 1  out of 6 found this valuable. Do you?    
virag_sh
virag_sh
3. RE: Oracle 11g and the new DIAGNOSTIC_DEST parameter
Jan 20 2008, 11:20 PM EST | Post edited: Jan 20 2008, 11:20 PM EST
"hi all,

I would like to discuss about the new diagnostic_dest parameter.

It could be a good idea but i am surprised that it can't be possible to keep old dump parameters as deprecated parameters (they are directly obsolete parameters in 11g).

Most of dba startup/shutdowns & supervision scripts parse the alert.log file to return an exit code. So they need to be changed during the migration.

It seems that Oracle developpement teams didn't feel that this new feature has serious consequencies on production database."
Check following article , it gives detail about old directories and equivalent ADR directory.

http://virag.sharma.googlepages.com/oracle11gadrautomaticdiagnosticrepositor

Create a link from old *DUMP_DEST to ADR directory.

1  out of 3 found this valuable. Do you?