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.

Similar Messages

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;

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.

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

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

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

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

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.

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

Essbase in read-only mode

Gurus,
I have three essbase databases in my environment, and I am planning to run a command to sync the three dataases.
During the sync process, I do not want the users to log in to any of the databases, meaning I dont want users to have access to any of them or change any data in the databases.
Is there a way where I can put the databases in 'read-only' mode so that I can run the command.
Or is there any other script or any process I can use so that users wont have access until I complete the sync process.
Any suggestion is appreciateD
Thanks

Maxl would probably be your best bet since you are likely using it with the data migrations.
alter application "appName" disable connects; /* nobody lower than applciation manager can connect */
This has a number of options
- disable updates
- disable commands (Prevent all requests to databases in the application, including non-data-specific requests, such as viewing database information or changing database settings. All users are affected, including other administrators. Administrators are affected by this setting as a safety mechanism to prevent accidental updates to databases during maintenance operations.)
More detailed info is at http://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/maxl_altapp.html.
Kyle Goodfriend
https://www.in2hyperion.com
EDITED
If this is a planning application, you will also want to deal with those connecting to Essbase through Planning. This is handled through the Application Mode (see http://in2hyperion.com/post/2012/09/26/Change-Application-Maintenance-Mode-via-Command-Line.aspx on automating). Keep in mind, any connection from Planning to Essbase uses an admin ID, not the user ID.
Edited by: Kyle Goodfriend on Oct 4, 2012 12:02 PM

Roll back segments into READ-ONLY Mode

To bring an v8 database into READ-ONLY Mode do we need to put the Roll back tablespace RBS also into READ-ONLY Mode?

You can put database in READ ONLY mode in Oracle 8i
READ ONLY / READ WRITE Example
The first statement below opens the database in read-only mode.
The second statement returns the database to read-write mode and clears the online redo logs:
ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ WRITE RESETLOGS;---
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a85397/stateme3.htm#2048938

Startup command starts database but alter database open read only gives error

Hi,
I'm having some strange behavior. I've 10.2.0.3 database on windows 2003.
The startup command starts database without any issues.
But if I try following it gives error.
startup mount (successful no errors)
alter database open read only; gives error that file Mnnnnnn is missing.
Why this is happening and how to fix it?
Thanks.

You really need to show us exactly what Oracle is telling you, using copy and paste, so we can have some clue. You can hide details like instance and host names if they show up.
I'm wondering if you had some messed up offline datafile in a tablespace, where Oracle handles it with startup, but gets upset when you try to open read-only. It's some bizarro sequence of events like: add a datafile to a tablespace, decide that was a mistake, alter it offline, then remove it from the OS without telling Oracle any more about it. I've come back from vacation to find scenarios like this, it winds up being a time-bomb trying to recreate a standby later. Or something like that, I could be unremembering some details.

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 errors - Alter database open read only

alter database open read only
AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
Signalling error 1152 for datafile 1!
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 216
Mon Dec 20 11:58:18 2010
Standby crash recovery need archive log for thread 1 sequence 216 to continue.
Please verify that primary database is transporting redo logs to the standby database.
Wait timeout: thread 1 sequence 216
Standby crash recovery aborted due to error 16016.
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!
Completed standby crash recovery.
Signalling error 1152 for datafile 1!
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
ORA-10458 signalled during: alter database open read only...
Mon Dec 20 12:13:46 2010
ALTER DATABASE RECOVER managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (MDM2)
Mon Dec 20 12:13:46 2010
MRP0 started with pid=23, OS id=18974
MRP0: Background Managed Standby Recovery process started (MDM2)
started logmerger process
Mon Dec 20 12:13:51 2010
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 216
Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
The above lines are from alert log of standby database.
Standby standbase
SQL> 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: '+MDMDG1/mdm2/datafile/system.280.738243341'
Parameters set on primary are
log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
log_archive_dest_state_1 ENABLE
log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
log_archive_dest_state_2 ENABLE
dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
fal_server MDM2
standby_file_management AUTO
log_archive_config dg_config=(MDM1,MDM2)
db_file_name_convert MDM2, MDM1
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
Standby pfile
*.archive_lag_target=900
*.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
*.db_block_size=8192
*.db_create_file_dest='+MDMDG1'
*.db_domain=''
*.db_file_name_convert='MDM1','MDM2'
*.db_name='MDM'
*.db_recovery_file_dest='+MDMDG2'
*.db_recovery_file_dest_size=10485760000
*.db_unique_name='MDM2'
*.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
*.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
*.fal_server='MDM11','MDM12'
*.instance_name='MDM2'
*.log_archive_config='dg_config=(MDM1,MDM2)'
*.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
*.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='MDM_%t_%s_%r.arc'
*.log_file_name_convert='MDM1','MDM2'
*.memory_target=838860800
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.processes=500
*.remote_login_passwordfile='exclusive'
*.sessions=555
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
On standby ASM
ASMCMD [+] > find * *
+MDMDG1/ASM/
+MDMDG1/ASM/ASMPARAMETERFILE/
+MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
+MDMDG1/MDM/
+MDMDG1/MDM2/
+MDMDG1/MDM2/CONTROLFILE/
+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
+MDMDG1/MDM2/CONTROLFILE/current.265.738243333
+MDMDG1/MDM2/DATAFILE/
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
+MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
+MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
+MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
+MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
+MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
+MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
+MDMDG1/MDM2/DATAFILE/USERS.278.738243347
+MDMDG1/MDM2/ONLINELOG/
+MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
+MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
+MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
+MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
+MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
+MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
+MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
+MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
+MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
+MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
+MDMDG2/MDM/
+MDMDG2/MDM/DG_CONFIG/
+MDMDG2/MDM2/
+MDMDG2/MDM2/AUTOBACKUP/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
+MDMDG2/MDM2/CONTROLFILE/
+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
+MDMDG2/MDM2/CONTROLFILE/current.271.738243335
+MDMDG2/MDM2/ONLINELOG/
+MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
+MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
+MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
+MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
+MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
+MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
+MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
+MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
+MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
+MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
+MDMDG3/MDM/
+MDMDG3/MDM/ARCH/
+MDMDG3/MDM2/
+MDMDG3/MDM2/ARCH/
-- Please can I know how to open read only standby database.

user5846399 wrote:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!archived log for thread 1 sequence# 216
This file is needed for recovery, Find it and move it to the standby database side.

Starting up an Oracle database in read only mode

Similar Messages

Maybe you are looking for