ORA-01578 about standby database in read only mode

Hi,
I have an ORA-05178 (data block corrupted) about a standby database which in read-only mode. About production database, there is no problem.
After analyze, this is an index segment :
SELECT segment_name , segment_type , owner , tablespace_name
FROM sys.dba_extents
WHERE file_id = 58
AND 218173 BETWEEN block_id and block_id + blocks -1
SEGMENT_NAME SEGMENT_TYPE OWNER TABLESPACE_NAME
SICINHIS01 INDEX MOWIN IDX_DATA01
There is no constraint.
How can I repair this problem ?
Nicolas

Similar Messages

Error during open standby database in read only mode

hi,
alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u02/app/oracle/oradata/standby/system01.dbf'
Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
what is the reason of this.
Thanks in advance.

thanks for your reply.
[oracle@standby admin]$ cat listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
LISTENER_STANDBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME =/opt/app/oracle/product/11.2.0/db_1)
(PROGRAM = extproc)
tnsfile
[oracle@standby admin]$ cat tnsnames.ora
standby =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.124)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = standby)
ora11g =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.120)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ora11g)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.120)(PORT = 1521))
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
pfile
[oracle@standby standby]$ cat initstandby.ora
ora11g.__db_cache_size=130023424
ora11g.__java_pool_size=4194304
ora11g.__large_pool_size=4194304
ora11g.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
ora11g.__pga_aggregate_target=146800640
ora11g.__sga_target=276824064
ora11g.__shared_io_pool_size=0
ora11g.__shared_pool_size=121634816
ora11g.__streams_pool_size=8388608
*.audit_file_dest='/u01/app/oracle/admin/ora11g/adump'
*.audit_trail='db'
*.compatible='11.2.0.1.0'
#*.control_files='/u02/app/ora11g/oradata/ora11g/control01.ctl','/u01/app/oracle/flash_recovery_area/ora11g/control02.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='ora11g'
*.db_recovery_file_dest='/opt/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=4039114752
*.diagnostic_dest='/opt/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=ora11g)'
*.memory_target=2016M
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.undo_tablespace='UNDOTBS1'
*.audit_file_dest='/opt/app/oracle/admin/standby/adump'
*.audit_trail=none
#*.background_dump_dest='/opt/app/oracle/admin/standby/bdump'
#*.compatible='10.2.0.2.0'
#*.control_files='/opt/app/oracle/oradata/standby/control01.ctl'
#,'/opt/app/oracle/oradata/standby/control02.ctl','/opt/app/oracle/or
*.control_files='/u02/app/oracle/oradata/standby/control_sb01.ctl'
#,'/u02/app/oracle/oradata/standby/control_02.ctl','/u02/app/oracle/oradata/standby/control_03.ctl'
*.core_dump_dest='/u01/app/oracle/diag/rdbms/standby/standby/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
#*.db_name='standby'
#*.dispatchers='(PROTOCOL=TCP) (SERVICE=standby)'
*.job_queue_processes=10
*.log_archive_dest_1='location=/opt/app/oracle/arch'
*.log_archive_config='dg_config=(standby,ora11g)'
*.log_archive_dest_1='LOCATION=/opt/app/oracle/oradata/standby/archivelog'
*.log_archive_dest_2='service=orcl valid_for=(online_logfiles,primary_role) db_unique_name=ora11g'
*.log_archive_format='%t_%s_%r.dbf'
*.standby_file_management=auto
*.db_unique_name =standby
*.fal_server='ora11g'
*.fal_client='standby'
*.service_names='standby'
*.open_cursors=300
*.pga_aggregate_target=525336576
*.processes=1500
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1576009728
*.undo_management='AUTO'
*.undo_tablespace='undotbs02'
#*.user_dump_dest='/opt/app/oracle/diag/rdbms/standby/standby/trace'
*.standby_file_management ='manual'
*.instance_name =standby
#*.standby_archive_dest=/opt/app/oracle/oradata/standby/archivelog
*.db_file_name_convert=(/u02/app/ora11g/oradata/ora11g,/u02/app/oracle/oradata/standby)
*.log_file_name_convert='/u02/app/ora11g/oradata/ora11g','/u02/app/oracle/oradata/standby'
#*.remote_listener=LISTENER_ora11g

Opening a Standby Database in Read-Only mode

Is there anyway to open a Standby database up to date as of a certain time? I'm currently using the 2 commands to get close to the time required.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Such as, similar to this? RECOVER DATABASE UNTIL TIME '2012-01-25:15:00:00';
We're on 11.1.0.7, which I'm currently very unhappy with.
Thanks for any help, as my google-fu hasn't worked today.
James

Maybe
I did a quick test :
8:42 open the databases and start recovery
8:43 check status from primary
Shows sequence 75
and "TO STANDBY" for switchover status
Did log switches at 8:44, 8:45, and 8:46
8:50
SQL> alter database recover managed standby database cancel;
SQL> RECOVER STANDBY DATABASE UNTIL TIME ' 2012-01-25:20:43:00';
Media recovery complete.
SQL>
8:52
SQL> alter database recover managed standby database disconnect from session;
Database altered.
Check status
TO STANDBY and sequence 78Still need to check alert logs and do another log switch. It checks out so the quick test works.
However the quick test is incomplete since there was no before and after data in the test and the time period was very short.
Andy may be right, but I would test, test test. ( if you do please let us know the results )
Thanks Andy!
Best Regards
mseberg
Later
After sleeping on this I decided my first thought is probably correct. You cannot go back in time and still be in sync. While the test statement did not error or produce any alert log entries, it probably did nothing. Oracle is smart enough to know you cannot have your Cake and eat it too.

Unable to open database in READ ONLY mode

When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
1) Startup mount
2) SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-16005: database requires recovery
But database opens succesfully when opened in READ WRITE mode.

user12038051 wrote:
When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
1) Startup mount
2) SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-16005: database requires recovery
But database opens succesfully when opened in READ WRITE mode.
sqlplus '/as sysdba'
shutdown imediate;
startup;
shutdown imediate;
startup mount;
recover database;
alter database open read only;

How to open a "manual" Physical standby database in read/write mode

Hi,
I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
The standby database is started this way :
startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
alter database mount standby database;
Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
The thing is, if I shutdown immediate the database, then do just startup :
shutdown immediate;
startup;
The database opens with no error messages, but is still in read-only mode...
I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
Thanks,
Mat

Hello,
There're features which allows you to open a Standby database in Read/Write mode but for all I know
it needs Entreprise Edition.
In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
a way by using flashback database so as to rolling backward the database and avoiding to recreate
the Standby.
In Standard Edition I'm afraid that you'll have to recreate your Standby database.
Best regards,
Jean-Valentin

Putting apps database in Read-Only mode

Hi,
I want to put the apps database in read-only mode to that user will be able to login into the applications and see data but will not be able to update it.
What is the best way to do this?
Thanks

I am still looking at how to do this because if users
update the UAT/test database, when the prod upgrade
is completed, they will think that their updates will
be available and this will cause some issues.This is a training/expectation-setting issue, not a technical one. You need to make sure that your users understand the difference between a test system and production, and that changes made in testing will not be present in production. They also need to understand that this situation is actually to their benefit: it enables them to really work with the test system to uncover potential problems and learn new features, without fear of making changes that could negatively impact their day-to-day work in production.
Please note that I'm not trying to be a jerk here. I very respectfully submit that attempting to make an instance read-only for training purposes, even if possible, will involve a great deal of technical work for very little (and perhaps even negative) overall benefit to the users.
Regards,
John P.

Cannot open standby database in read only....

i do the following procedure on my standby database
ORACLE 9.2.0.7
SQL> startup nomount
ORACLE instance started.
Total System Global Area 538412112 bytes
Fixed Size 742480 bytes
Variable Size 402653184 bytes
Database Buffers 134217728 bytes
Redo Buffers 798720 bytes
SQL> lter database mount standby database;
SP2-0734: unknown command beginning "lter datab..." - rest of line ignored.
SQL> alter database mount standby database;
Database altered.
SQL> SQL> recover standby database until cancel;
ORA-00279: change 4274363673 generated at 09/18/2006 11:25:08 needed for thread
1
ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9135.arc
ORA-00280: change 4274363673 for thread 1 is in sequence #9135
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 4275275613 generated at 09/18/2006 14:03:09 needed for thread
1
ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9136.arc
ORA-00280: change 4275275613 for thread 1 is in sequence #9136
ORA-00278: log file '/u12/oradata/dbadmon/arch/dbadmon9135.arc' no longer
needed for this recovery
ORA-00308: cannot open archived log '/u12/oradata/dbadmon/arch/dbadmon9136.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
THEN i check in the alert...
Errors in file /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc:
ORA-00704: bootstrap process failure
ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
Mon Sep 18 13:59:16 2006
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 24028
ORA-1092 signalled during: alter database open read only...
followed by the trace file...
/u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
ORACLE_HOME = /u00/oracle/product/9.2.0.1
System name: AIX
Node name: eserver1
Release: 1
Version: 5
Machine: 000651FA4C00
Instance name: dbadmon
Redo thread mounted by this instance: 1
Oracle process number: 14
Unix process pid: 24028, image: oracle@eserver1 (TNS V1-V3)
*** SESSION ID:(11.1) 2006-09-18 13:58:57.859
Start recovery at thread 1 ckpt scn 4274363673 logseq 9135 block 2
*** 2006-09-18 13:59:00.215
Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9135.arc
*** 2006-09-18 13:59:11.868
Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9136.arc
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 27062Kb in 13.99s => 1.86 Mb/sec
Longest record: 8Kb, moves: 22/97639 (0%)
Change moves: 43706/193539 (22%), moved: 4Mb
*** 2006-09-18 13:59:14.688
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
Current SQL statement for this session:
select /*+ rule */ name,file#,block#,status$,user#,undosqn,xactsqn,scnbas,scnwrp,DECODE(inst#,0,NULL,inst#),ts#,spare1 from undo$
where us#=:1
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp+0148 bl ksedst 1029170CC ?
ksfdmp+0018 bl 01FD771C
kgeriv+0118 bl _ptrgl
kgesiv+0080 bl kgeriv FFFFFFFFFFEBEF0 ? 080000000 ?
101A6C640 ? 000000000 ?
FFFFFFFFFFEBE70 ?
ksesic5+005c bl kgesiv 70000000E517A78 ?
70000000E517748 ?
Can anyone gie me a hand please???
Thanks in advance.

Doc ID: Note:1038418.6
Please check permissions on dump desitnation directory.
Also check if dual table is present.

Standby Database - from READ-ONLY to Managed Recovery

We have a standby database set up for our production environment.
We are able to switch logfile on production and perform the managed recovery and then switch over to READ-ONLY mode. However, when the database is in READ-ONLY mode...I cannot close it if there are active connections.
There are 2 ways I can attempt to close the database...either by "shutdown immediate" or by issuing an "alter system kill session (##,##);"
If I issue the "shutdown immediate", then the RFS process does not transmit any more files...saying the connection to host is not there. Therefore this is not a valid solution.
I can use an alter system kill...to kill all active connections...but it would require to know what other connections are there.
Does anybody know how to best do this...to close the database by forcing all connections to end (except your current one) so you can "alter database close" and switch over to managed recovery?
Please HELP!
Thanks.
-Nicolas

u just shutdown the server and restart in standby mode. it will apply all pending archive autometically.

Starting database in Read only mode

hi,
i am using oracle 8i, we want to copy the Production database to other machine, but on starting that m/c database should be opened in read only mode without DBA interaction what to do for that. pl tell
thanx in advance

SQL> STARTUP MOUNT
ORACLE instance started.
Total System Global Area 177281688 bytes
Fixed Size 453272 bytes
Variable Size 150994944 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL> ALTER DATABASE OPEN READ ONLY;
Database altered.
SQL> DELETE FROM SCOTT.EMP;
DELETE FROM SCOTT.EMP
ERROR at line 1:
ORA-16000: database open for read-only access
kuljeet pal singh

Is it possible to have a 10g (R1) LOGICAL standby db in read-ONLY mode?

From what I've gathered reading the 10g (R 1) docs, the logical standby turns read-only when applying sql, and then in read-write mode otherwise. I have to meet a requirement that the remote database be strictly in read-only mode the entire time (so as to not risk writing to it), as well as being as up-to-date as possible off the primary. (Hence I decided on the logical vs. the physical) Does anyone pls. know if I can keep the logical read-only all the time?
Much appreciated,
Sophie

Oh, Ok. I guess i interpreted it differently. The direct quote from the docs: "Although the logical standby database is opened in read/write mode, its target tables for the regenerated SQL are available only for read-only operations." So I guess what it means, as you suggest, is the entire set of tables from the primary, and not just those few that happened to be updated at that particular time frame, are kept in read-only the entire time...

Starting up an Oracle database in read only mode

Is there a way to have an oracle database start up in "read only" mode every time the instance is shutdown and strated back up. I need to accomplish this without any sort of manual intervention? Is there a parameter that can be set in init.ora etc... ? I am using oracle version 9.2.
Thanks in advance.

Operating System info is useful.
On *nix, it's a simple matter to edit the dbstart script. On Windows, I'd start investigating the 'net start' command.

How Real Time Apply works while physical standby is open in Read Only mode

Hi,
With Active data guard option, we can open physical standby DB in read only mode, while redo log are being applied. (Real Time Query)
Standby Redo log (SRL) enables Real Time Apply (with "USING CURRENT LOGFILE" clause in recover database command on standby DB)
I am interested to know, how Real Time Query works ?
What is the mechanism with allows us to open physical standby DB in read only mode while redo logs are being applied continuously ?
Regards,
Sujit

Dear user7419391,
That is a new feature in Oracle Database 11g. MRP can use the real time apply in 10g but the concept here is different.
Taken from the following document;
http://www.ascent.co.za/documents/oracle/Oracle%20databse%2011g%20Active-Data-Guard%20datasheet.pdf
*Unique Advantages of Oracle Active Data Guard*
+Active Data Guard is an evolution of Data Guard technology, providing unique+
+performance advantages while leveraging all other enhancements included in Oracle+
+Data Guard 11g. For example, any Data Guard 11g physical standby database can+
+be easily converted to a Snapshot Standby. A Snapshot Standby is open read-write+
+and is ideally suited as a test system, able to process transactions independent of the+
+primary database. A Snapshot Standby maintains protection by continuing to receive+
+data from the production database, archiving it for later use. When tests are+
+complete, a single command discards changes made while open read-write and+
+quickly resynchronizes the standby database with the primary.+
The other link in the previous post is excellent and you really have to read it to understand the active data guard aspects.
Regards.
Ogan

Database open read only

Does the alert<sid>.log always show a warning message as such when a standby database is put into read only mode?
***Warning - Executing transaction without active Undo Tablespace

Hi,
It's a bug happen to 9i
Bug 3270493:EXCESSIVE QMNX TRACE FILES WHEN PLACING STANDBY IN READ ONLY MODE
This does not reproduce in 10g. It looks like there were some modifications made to kwqitnfy to check whether the database is in read-write mode before starting the QMNC process.
The workaround is to set aq_tm_processes=0 when using the database in read-only mode for the long-term. This can be done with a simple alter system command:
ALTER SYSTEM SET aq_tm_processes=0;
By running the above command, the errors would stop and therefore so would the trace files.
Note: Use spfile is applied in order to ensure aq_tm_processes will be zero after restart.
Mike

Database Open in Read Only Mode

Hi
I would like to open database in read only mode
like
SQL> startup mount
SQL> ALTER DATABASE OPEN READ ONLY
this will open database for read only mode for all user
i want to give read write access on database to one user
any idea how i can proccess
Thanks
Chetan

Hi,
Alter database open read only;
this should work fine and everything will be in read only mode. Hence if any auditing is going on and audit_trial=db then it fails to open the database in read only mode.
If you want to control only users to stop writing to it, you may remove tablespace quotas for those users. Also, you may control them through grants. Remove any current grants assigned to them or to roles through which the grants are assigned.
Several ways to do this. If you tell us the particular scenario then we might help in getting a solution.
Regards,
Vasu.

Read-Only mode for a Essbase DB

Is the a way to put my Essbase Db with Historical values in read-only?, I found that the Maxl Archieve option will do but I don't know if this is only for backup.
Regards,
Antonio

If you want to put the entire database into read-only mode, SoL (love that name) gave you the right direction.
If you only want to put part of the database into read-only mode, e.g., 2007 through 2009 data, you can use READ filters to do this.
Have a read here on the theory: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dsefilt.htm
Have a look here on how to do it: http://download.oracle.com/docs/cd/E12825_01/epm.111/eashelp/crtfilt.htm
Regards,
Cameron Lackpour

ORA-01578 about standby database in read only mode

Similar Messages

Maybe you are looking for