Home » RDBMS Server » Server Administration » WARNING: db_create_file_dest is same as db_recovery_file_dest (10.1.0.3)
WARNING: db_create_file_dest is same as db_recovery_file_dest [message #282107] Tue, 20 November 2007 22:26 Go to next message
sisrahul
Messages: 1
Registered: November 2007
Junior Member
Hi ,
I am getting above warning in database event & message log file "alert_bgw.log" at the path given to "background_dump_dest" .

However db_create_file_dest and db_recovery_file_dest is indeed not the same. Looking in the alert_bgw.log during a startup, this is displayed:
db_create_file_dest = /var/opt/mediation/ora//oradata
db_recovery_file_dest = /var/opt/mediation/ora//flash_recovery_area

I am using Oracle 10.1.0.3 on Solaris.
any idea why this warning is coming into log file will be highly appreciated.

Thanks in advance
Rahul
Re: WARNING: db_create_file_dest is same as db_recovery_file_dest [message #282113 is a reply to message #282107] Tue, 20 November 2007 22:56 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

1. You can ignore it.
2. Your database running in NO ARCHIVELOG MODE ?
Re: WARNING: db_create_file_dest is same as db_recovery_file_dest [message #282153 is a reply to message #282107] Wed, 21 November 2007 00:44 Go to previous messageGo to next message
Arju
Messages: 1554
Registered: June 2007
Location: Dhaka,Bangladesh. Mobile:...
Senior Member

You use oracle managed file system or user managed file systems?
Re: WARNING: db_create_file_dest is same as db_recovery_file_dest [message #282267 is a reply to message #282107] Wed, 21 November 2007 06:02 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
This is harmless bug 3837794 that has been fixed in 10.2.
Re: WARNING: db_create_file_dest is same as db_recovery_file_dest [message #282273 is a reply to message #282267] Wed, 21 November 2007 06:27 Go to previous message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

Right it is bug.
but I think it is also fix in 10gr1 latest patchset 10.1.0.5.0

becuase i recently upgraded my production database after upgrade i didn't see warning message in my alert<sid>.log file.

Regards
Mohammed Taj
Previous Topic: redo transport services
Next Topic: Database in not respondin
Goto Forum:
  


Current Time: Sun Dec 04 10:47:28 CST 2016

Total time taken to generate the page: 0.07221 seconds