ORA-01157 error on STANDBY after adding a datafile on primary [message #172972] |
Thu, 18 May 2006 15:21 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
andreiu
Messages: 2 Registered: May 2006
|
Junior Member |
|
|
Hi,
I'm using 9.2.0.4.0
on Linux with physical standby (not DataGuard). Working OK for a while:
To add new datafile on primary I did the following on primary:
alter system set STANDBY_FILE_MANAGEMENT = AUTO
-- system altered
alter TABLESPACE ... add datafile size 1024M AUTOEXTEND ON NEXT 1024M
MAXSIZE 30720M;
-- tablespace altered, file is there.
ALTER SYSTEM ARCHIVE LOG CURRENT;
-- after a minute, file shows up in V$DATAFILE on standby server
NOW THE PROBLEM:
- file was not copied in the UNIX fine system on standby server, AND
- got error on standby: ORA-01157: cannot identify/lock data file 23...
AND
- process MR(fg) not running in V$MANAGED_STANDBY any longer
I copied the file manually, ran ALTER SYSTEM CHECK DATAFILES.
Also turned STANDBY_FILE_MANAGEMENT to AUTO on secondary.
Yet the file is still in RECOVER status in V$DATAFILE, and the MR(fg) process in V$MANAGED_STANDBY still does not show up.
If I try:
ALTER DATABASE OPEN READ ONLY;
get the error:
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: '/opt1/oracle/oradata/totaleon/system01.dbf'
Tried:
SQL> RECOVER STANDBY DATABASE;
no change.
Any ideas ? I appreciate any and all help you can give me.
Thanks much
Andrei
|
|
|
Re: ORA-01157 error on STANDBY after adding a datafile on primary [message #173149 is a reply to message #172972] |
Fri, 19 May 2006 11:47 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
andreiu
Messages: 2 Registered: May 2006
|
Junior Member |
|
|
FYI, here is the solution that worked for me, which I got from another forum, from Krystian Zieja:
Your mistake was that you setup STANDBY_FILE_MANAGMENT=AUTO on Primary database you should setup it on Standby database.
You can try following it correct it (Warning may not work):
On Standby:
Alter system set standby_file_managment=manual
rm this datafile from filesystem
alter database create datafile ‘path’ as ‘orginalpath’ [size];
alter system set standby_file_managment=auto
alter database recover managed standby database disconnect;
|
|
|
|