ORA-01111 UNNAMED file [message #311140] |
Thu, 03 April 2008 09:43 |
dhock194
Messages: 7 Registered: December 2007
|
Junior Member |
|
|
All:
Getting the following alert log error when attempting to start redo log apply for a DG standby node:
Errors in file /home/oracle/admin/stbydb2/bdump/stbydb2_mrp0_22855.trc:
ORA-01111: name for data file 309 is unknown - rename to correct file
ORA-01110: data file 309: '/home/oracle/product/10.2.0/db_1/dbs/UNNAMED00309'
ORA-01157: cannot identify/lock data file 309 - see DBWR trace file
ORA-01111: name for data file 309 is unknown - rename to correct file
ORA-01110: data file 309: '/home/oracle/product/10.2.0/db_1/dbs/UNNAMED00309
I have several references from Metalink and other on how to rename the target filename to eliminate the failed UNNAMED file write....however, it is not clear from the logs what the original filename was, and therefore, what the target file name should be. I am concerned that renaming it incorrectly will not eliminate the problem, or will change it from an UNNAMED file problem to an incorrectly named file problem. It not clear from the primary server logs either.
Any references on "expanding" the error in the alert log to ID the original file name that this needs to be renamed to?
Thanks!
|
|
|
|
|
|
Re: ORA-01111 UNNAMED file [message #311272 is a reply to message #311140] |
Thu, 03 April 2008 20:22 |
dhock194
Messages: 7 Registered: December 2007
|
Junior Member |
|
|
Repeating message in the Primary alert log....
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[7]: Assigned to RFS process 2356
RFS[7]: Database mount ID mismatch [0x4642ed95:0x458c988c]
RFS[7]: Client instance is standby database instead of primary
RFS[7]: Not using real application clusters
Errors in file /home/oracle/admin/orcl/udump/orcl_rfs_2356.trc:
ORA-16009: remote archive log destination must be a STANDBY database
This sequence been occurring since installation (> 1 year ago), and the ORA-16009 error is a known bug in 10.2.0 -- it goes all the way back to the initial installation, even though log application had been occurring up until several months ago.
|
|
|
|
Re: ORA-01111 UNNAMED file [message #311302 is a reply to message #311140] |
Fri, 04 April 2008 00:40 |
dhock194
Messages: 7 Registered: December 2007
|
Junior Member |
|
|
log archive parameters from Primary:
======================================
log_archive_dest string
log_archive_dest_1 string LOCATION=/home/oracle/product/10.2.0/arch
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=standby
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log archive parameters from Standby:
======================================
log_archive_dest string
log_archive_dest_1 string LOCATION=/home/oracle/product/10.2.0/arch
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=standby
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
On your other question, there are no other errors or alarms in the alert log of the primary related to adding or renaming files -- I have review going back for ~ 1 year, and dont see any of these references.
|
|
|
|
Re: ORA-01111 UNNAMED file [message #311796 is a reply to message #311140] |
Sun, 06 April 2008 21:53 |
dhock194
Messages: 7 Registered: December 2007
|
Junior Member |
|
|
I reviewed the Primary, and there was no file in any of the data, dbs or related directories ending with *309 or similar. So, I renamed the UNNAMED to a known unused name, and turned on standby_file_management=auto, and then executed "recover automatic standby database" --this then allowed all pending logs to be applied.
I still have an error occuring after the last log was applied -- reviewing this now -- more to come.
|
|
|
|
|
|
|
Re: ORA-01111 UNNAMED file [message #337712 is a reply to message #337707] |
Thu, 31 July 2008 17:17 |
dhock194
Messages: 7 Registered: December 2007
|
Junior Member |
|
|
Sonumalhi,
Sorry -- not sure about the others, but I did not see the previous emails from you inquiring about this. This problem was related to a previous company and project, and I no longer regularly engage on Dataguard, so I dont check the lists that often.
It has been a while, and the exact solution was a bit circuitous in finding -- as I remember, the error was related to one of the archive files being corrupted after it was sent from primary to backup, and so part of the solution was to:
- Close the backup instance
- Create a backup of the current archive directory
- Manually copy the archive files from the DG primary
to the backup
- Open/close the oracle instance in backup mode, and have
it start resyncing
As I noted, it has been while, so I would want a more seasoned DG expert to qualify the process I just described. Sorry I am not more details in my memory on this, but as I remember, this was one of several different problems I needed to know down to get these two Oracle instances resynced.
|
|
|