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.

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;

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

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

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

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.

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.

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

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.

Ways to put application in Read Only mode during monthly maintenance

Hello,
We have a situation where during monthly maintenance phase for 2-3 days i need to put the application in Read only mode. We already have dimension level security applied to each user but even to those users who have the write access to some members on the data forms etc, the application should just be read only during that time so that no users can enter any data.
From what I know putting the application in maintenance mode all the users will be locked out which is not what we want. The users should still be able to see the dataforms, reports etc. So, please let me know your ideas on this.
Any ideas are appreciated.
~ Adella

The same question was asked the other day - How can i make a application as read only ?
Cheers
John
http://john-goodwin.blogspot.com/

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

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

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

Remove Standby/Read only mode for a database in sql server 2005

Hi,
I have a problem in sql sever . my database is showing standby/read-only mode. i want to remove that mode.please help me for the issue.

HI
Did you assign any DB read only user?
check the administrator guide in your SAP Business one->Documntation->system setup->Administrator guide...
but removing DB read only user is impossible.....

Generating EXPLAIN PLAN on a database which is opened in READ-ONLY mode

Hi,
I am using Oracle 10.2.0.3 version.
If my database is opened in READ-ONLY mode, means no insert/update/delete operations are permitted here.
While generating EXPLAIN PLAN for any SQL, it does entries in PLAN_TABLE. But my database is opened in READ-ONLY mode, means no inserts can happen.
So how can I generate EXPLAIN PLAN for my SQL in this condition?
Thanks in advance.
Best Regards,
oratest

oratest wrote:
I am using Oracle 10.2.0.3 version.
If my database is opened in READ-ONLY mode, means no insert/update/delete operations are permitted here.
While generating EXPLAIN PLAN for any SQL, it does entries in PLAN_TABLE. But my database is opened in READ-ONLY mode, means no inserts can happen.
So how can I generate EXPLAIN PLAN for my SQL in this condition?
You can always do: "explain plan into some_table@remote_database" to avoid inserting into the local database. Unfortunately 10g added a sequence fetch to the "explain plan" code, and this is where the call would fail if you tried this remote approach on your version.
Here's an idea I haven't tested. If you set up a database link from your production database to the read-only database, you could then do an "explain plan" in the production database for the SQL statement by changing every object reference in the SQL statement to "object@readonlydatabase". In most cases this will allow the optimizer to recognise the statement as "fully remote" and get the optimizer on the readonly database to create the execution plan - which would then be written to the production database.
Regards
Jonathan Lewis

Putting apps database in Read-Only mode

Similar Messages

Maybe you are looking for