Backing up database with read-only tablespaces

I am trying to develop a script that will dynamically build RMAN scripts for backing up
a database with read-only tablespaces. The application running on this database creates
new tablespaces in read-write mode on weekly basis, populates them, and then puts them in read-only mode. So I need to backup all read-write tablespaces plus take backup of all read-only tablespaces once. The problem is that the application also includes a process that puts a tablespace back into read-write mode, updates it, and puts it back into read-write mode. So I need to be able to access "a history" of the tablespace - when was it put into read-only mode - to compare it with a history of backups. While history of backups is available in RMAN views, I couldn't find any way to extract tablspaces
history.
There should be RMAN command to the effect
"backup all read-write tablespaces and read-only tablespaces if they have not been backed up at least once since becoming read-only".
Regards,
Sev
null

just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off.

Similar Messages

I want to use ZFS filesystem compression on a history database with read-only tablespaces. What is the best way to get the datafiles compressed?

I have 5 history databases that total about 2.2 Terabytes. They use about 15 filesystems, but I can start with 2 that are isolated to only one database. I have asked for ZFS compression to be set on the filesystems, but since these are read-only tablespaces, I do not think any compression will happen. Can I simply offline, copy and rename the files from one filesystem to the other to make the compression happen?

just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off.

Why r we not use tablespce begin backup with read only tablespace

why r we not use tablespce begin backup with read only tablespace

Please learn English prior to posting. The schools in India are not that bad!
Please RTFM.
Please stop asking doc questions at lightning speed.
Please go figure
Sybrand Bakker
Senior Oracle DBA

How to backup read only tablespace in rman

Hi,
I am using oracle 10gR2 in solaris 10.
I am taking Rman full backup using catalog.
My target database have 5 datafiles, in that one datafile is in read only mode.
When I issue the backup command in rman. it takes only 4 datafiles. its not taking the readonly datafile.
I want to take backup of all 5 datafiles.
kindly help me..
Many Thanks

My target database have 5 datafiles, in that one datafile is in read only mode.I presume that you mean to say that 1 Tablespace consisting of 1 datafile is Read Only.
What does SHOW ALL in RMAN present ?
If you have BACKUP OPTIMIZATION set to ON, the Read Only Tablespace will not be backed up after the first backup.
You could still explicitly backup the tablespace with a BACKUP TABLESPACE tablespacename; , although a BACKUP DATABASE would exclude it.
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on May 3, 2010 12:02 AM

Data warehouse backups and read only tablespaces

Hi all,
I am working on a data warehouse database with following specs:
Version: Oracle 10.2.0.3 Enterprise
OS: Solaris
App: Data warehouse
We use RMAN to take 'level 0' & 'level 1' backups. We have block change tracking enabled and RMAN backups up data files and archive logs straight to tape.
I am exploring ways of reducing the 'level 0' backups and was specifically focussing on using read-only tablespaces for this purpose.
I have often seen it mentioned that a best practice in D/Ws is to store the old static partitions of fact tables in read only tablespaces so as to reduce the backup size.
In case you have already implemented such a scheme, I would like to know how you have implemented it.
I am thinking of the following mechanism:
-- Start using backups at tablespace level rather than 'level 0' at database level.
-- Record the latest SCNs of all datafiles prior to back up.
-- If the latest SCN has not changed since last backup and the tablespace is in read only mode then
-- Check if a backup copy of the tablespace has been done within the recovery window and is accessible.
-- If the copy exists then don't backup that tablespace, else backup the tablespace.
-- If the tablespace is read/write then back it up.
I haven't delved into the low level details, but this seems to be lot of work. So just wanted to know from you if there's any ready made feature which makes all this easier.
Many thanks in advance.

Thank you so much for your help.
Backup optimization was indeed the thing I was looking for. To be honest I had done a bit of RTFM, but I didn't check the advanced user guide.
Although my specific question has been answered, it would be interesting to know what other things other people are implementing to reduce backups etc.
I am also thinking of following options:
-- Turn on index monitoring to get rid of unused indexes.
-- Stop the backups of 'index' tablespaces.
-- Archive off old data.
Any other ideas for reducing DW backup size?
Many thanks.

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.

Using Data Pump when database is read-only

Hello
I used flashback and returned my database to the past time then I opened the database read only
then I wanted use data pump(expdp) for exporting a schema but I encounter this error
ORA-31626: job does not exist
ORA-31633: unable to create master table "SYS.SYS_EXPORT_SCHEMA_05"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 863
ORA-16000: database open for read-only access
but I could by exp, export that schema
My question is that , don't I can use Data Pump while database is read only ? or do you know any resolution for the issue ?
thanks

You need to use NETWORK_LINK, so the required tables are created in a read/write database and the data is read from the read only database using a database link:
SYSTEM@db_rw> create database link db_r_only
2 connect to system identified by oracle using 'db_r_only';
$ expdp system/oracle@db_rw network_link=db_r_only directory=data_pump_dir schemas=scott dumpfile=scott.dmpbut I tried it with 10.2.0.4 and found and error:
Export: Release 10.2.0.4.0 - Production on Thursday, 27 November, 2008 9:26:31
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-02054: transaction 1.36.340 in-doubt
ORA-16000: database open for read-only access
ORA-02063: preceding line from DB_R_ONLY
ORA-39097: Data Pump job encountered unexpected error -2054
I found in Metalink the bug 7331929 which is solved in 11.2! I haven't tested this procedure with prior versions or with 11g so I don't know if this bug only affects to 10.2.0.4 or 10* and 11.1*
HTH
Enrique
PS. If your problem was solved, consider marking the question as answered.

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 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.

The back up volume is read only?

Can anyone help me with this? When time machine tries to run a back-up I get two errors and it fails. The first says:
Time Machine Error
The back up volume is read only.
The second one says:
Disk Repair
The disk was not repairable by this computer. It is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible.

AndyPrior wrote:
The back up volume is read only.
see C6 in [this_|http://web.me.com/pondini/TimeMachine/Troubleshooting.html] user guide.
JGG

MS Access database opens read only

An Access application with linked databases opens read only, but sometimes is editable. The system was developed in Access 10 on a Win 7 machine and migrated to a standalone laptop running Win 8 and Office 365.
The Access 10 has no problem in operating the application. The Win 8 laptop randomly opens the application read only. I have reviewed Trust settings and there is no difference between the different laptops and systems.
Is this a common problem? Is it associated with Win 8? Is it associated with Access form Office 365? The application is crucial to the business and we are getting way behind because we don't have a reliable or useful system. Last year the same application
ran satisfactorily on Win 7 and Access 10.
I would welcome some thoughts leading too a solution.

Hi,
Did you get the error message like "You are trying to open a read-only database". If yes, this issue may be due to the permission of the Access database. If we migrate the Access database from Access 2010 to Access 2013, the user/account's permission
may be changed with different Windows operation system. We need the full control permission of the Access database. To workaround this issue, follow these steps:
On the desktop, double-click My Computer.
Locate the Microsoft Access database that you moved.
Right-click the database name, and then click Properties.
In the Properties dialog box, clear the Read-only check box under
Attributes.
Click OK to apply the change.
Open your database in Access.
Please note: Make sure the user has full control of the root folder.
If no, please tell us the whole error message, we'd like to do further troubleshooting.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

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

How to create a user with read only access for ESB / BPEL Console

I need to create a user with read only access to ESB Console & BPEL Console. I have created a user
(esbreadonly) and assigned ascontrol_monitor role but user is still able to
delete services from ESB systems (such as DefaultSystem). Is there any way to
create a user that has strickly read only access to ESB Console & BPEL
Console
Thanks
Dinesh Patel

Check out this post.. I'm in the process of testing.
http://chintanblog.blogspot.com/2007/12/i-saw-numerous-people-asking-about-bpel_290.html

Read Only Tablespace Backup Issue

Hii!!
I had been trying to to take Read Only Table space Backup. So, firstly changed the tablespace using
SQL> alter tablespace users read only;
Tablespace altered.
2. Then took backup of all the data files using OS Copy command.
Now , the issue i am facing is that can i change the table space to read_write mode???? If yes , then how?? , plz help...

I had been trying to to take Read Only Table space Backup. So, firstly changed the tablespace using
SQL> alter tablespace users read only;
Tablespace altered.
2. Then took backup of all the data files using OS Copy command.
Now , the issue i am facing is that can i change the table space to read_write mode???? If yes , then how?? , plz help...Yes you can do,
SQL> alter tablespace users read write;After successful restore,
sys@11GDEMO> select tablespace_name,status from dba_tablespaces where tablespace_name='CKPT';
TABLESPACE_NAME                STATUS
CKPT                           ONLINE
sys@11GDEMO> alter tablespace ckpt read only;
Tablespace altered.
sys@11GDEMO> select tablespace_name,status from dba_tablespaces where tablespace_name='CKPT';
TABLESPACE_NAME                STATUS
CKPT                           READ ONLY+
sys@11GDEMO> alter tablespace ckpt read write;+
Tablespace altered.
sys@11GDEMO> select tablespace_name,status from dba_tablespaces where tablespace_name='CKPT';
TABLESPACE_NAME                STATUS
CKPT                           ONLINE+
sys@11GDEMO>
Edited by: CKPT on Jul 6, 2011 11:22 AM

Backing up database with read-only tablespaces

Similar Messages

Maybe you are looking for