Alter tablespace RW on standby database

I work with Oracle8i for Solaris.
I've created a stanby database which is opened in read only.
Now, I need to use a temporary tablespace, so
I've tried :
"alter tablespace temp nologging read write;"
But, oracle answer me an ORA-16000 error (database open for read-only access).
So :
1) Is it possible to use a temporary tablespace in standby mode ?
2) How.
Thanks,
Philippe
null

Hello,
Since the table sizes is about 100GB , it takes time to move and rebuild the indexes and the end user application doesnot work if any of the index is unusable or not present.I think it will generate a lot of Archived logs, so it will be very heavy to manage and apply to your Standby.
If it's possible, it will be faster to put your Primary database in NOARCHIVELOG mode then, you make the Move and Rebuild.
Afterwards, you put again the Primary in ARCHIVELOG mode and take a good BACKUP of it.
Later, when nobody work on Standby, you recreate it.
Hope this help.
Best regards,
Jean-Valentin

Similar Messages

How to exclude tablespace in logical standby database

Dear all,
In which way does the creation procedure of a logical standby database differ than the standard ORA9.2 procedure (http://www.oracle.com/pls/db92/db92.to_pdf?pathname=server.920%2Fa96653.pdf&remark=docindex) if I want to exclude a tablespace in my standby database?
Excluding tablespace in physical standby database is impossible.
Thanks in advance.

The goal of a stand by database is to become a clone fed online with transactions coming from the active database. If the cloned database in a physical dataguard configuration diverges from the active database it is useless, as transaction control takes place at a lower level (physical addresses are involved).
~ Madrid

Force logging at tablespace level for standby database

Hi
Can we create a standby database by enabling force logging at tablespace level instead of enabling it at database level.I want to out the tablespace containing indexes in nologging mode so that when I rebuild the indexes no logs will be generated.

Technically, you can create a Standby without having set FORCELOGGING at the Primary database.
You can also then selectively FORCELOGGING for all your important tablespaces (beginning with SYSTEM, SYSAUX, UNDO ....)
However, for a Physical Standby Redo Apply will mark the blocks (e.g. those populated by the CREATE INDEX .. NOLOGGING) as "corrupt". You will get Read Errors (ORA-1578 and ORA-26040) when you attempt to read the index (e.g. for a Table query).
So you have to monitor your NOLOGGING operations and the datafiles where NOLOGGING is applied. You can take Incremental RMAN Backups of such datafiles and restore them to the Standby immediately after the NOLOGGING operations.
Hemant K Chitale

Create an Object in Logical standby database in Oracle 10G

Hi,
I have logical standby database in oracle 10g R2 for reporting purpose.Now i want to create procedure in logical standby which is use to create new temp table in logical standby and contained data generated from select operation on existing table.
Can i create a new user in logical standby database,add new tablespace in logical standby which can insert,update and delete data in standby database base table?
kindly provide me the steps to implement all this.What will be effect if i set guard_Status in v$database is NONE in logical standby?
Thanks,
Shital Patel

Hi Shital,
Guard_status protects the data from being changed.
ALL- By default it is not possible for a non-privileged user to modify data on a data guard SQL apply database. This is because the database guard is automatically set to ALL.
With this level of security, only SYS user can modify the data.
STANDBY- When you set this level of security, users are able to modify data that is not maintained by the Logical apply engine.
NONE permits any users to access the standby database as long as they have correct privileges. This is the normal security for all data in the database.
You can change the guard status value from ALL to NONE in order to allow non-privileged users to modify data and Yes you can create user and extra tablespace in logical standby database..this is what the one of advantage of using Logical standby database.
SQL> ALTER DATABASE GUARD NONE;
Thanks

Standby Database Creation problem

Hi,
I have setup Standby Database for our Primary DAtabae,
I am facing probel while applying redo logs, if somebody nows the solution, Please help me.
SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
ORACLE instance started.
Total System Global Area 730931140 bytes
Fixed Size 454596 bytes
Variable Size 285212672 bytes
Database Buffers 444596224 bytes
Redo Buffers 667648 bytes
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
Database altered.
SQL> RECOVER STANDBY DATABASE;
ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed
for threa
1
ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
ORA-00280: change 7990686470 for thread 1 is in sequence #7032
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8388681], [1],
[7032],
[137367], [16], [], []
ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
ORA-10564: tablespace UNDOTBS1
ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
ORA-10560: block type 'KTU SMU HEADER BLOCK'
ORA-01112: media recovery not started
Ramesh
pls mail me : [email protected]
+91 080 9341018616

Hi,
I have setup Standby Database for our Primary DAtabae,
I am facing probel while applying redo logs, if somebody nows the solution, Please help me.
SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
ORACLE instance started.
Total System Global Area 730931140 bytes
Fixed Size 454596 bytes
Variable Size 285212672 bytes
Database Buffers 444596224 bytes
Redo Buffers 667648 bytes
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
Database altered.
SQL> RECOVER STANDBY DATABASE;
ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed
for threa
1
ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
ORA-00280: change 7990686470 for thread 1 is in sequence #7032
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8388681], [1],
[7032],
[137367], [16], [], []
ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
ORA-10564: tablespace UNDOTBS1
ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
ORA-10560: block type 'KTU SMU HEADER BLOCK'
ORA-01112: media recovery not started
Ramesh
pls mail me : [email protected]
+91 080 9341018616

Add temporary datafiles after creating standby database

I used data guard manager to create standby database and it went fine. Before finish, system pop up a window and says,
"The data guard configuration has been created in a disabled state. It must be enabled using the Enable option in the configuration menu. Pior to ebaling the configuration, please verify the following:
The Primary database contains temporary datafiles. The files will not be duplicated in the new standby database. You must manually recreate the temporary files on the standby node by adding them to their respective tablespaces in the standby database after creation process in complete."
The problem is, in the standby database, how do I add tempfile without open the standby database? the documentation is very unclear...

Thanks for the reply and the useful link. I had followed the instructions when creating the standby database, although under database options there is a difference between the OEM version we are using and the version shown, whereby the 'RMAN backup location' option has been replaced with 'working directory location'.
Just found the following and am guessing this is the issue.
NFS mounts established within a zone are local to that zone. The mounts cannot be accessed from other zones, including the global zone.
I suspect I will need to copy the backup pieces onto the local server in order to create the standby database using OEM. Not something I was expecting to have to do as copying will take a long time due to the size of the backup, but unless anyone else can shed any light on the reason for the initial error
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
then I guess this is the only way forward.
Regards,
JP

Reaction at Standby Database in 10g for alter , addtion, deletion tablespac

Deal All,
I want to know that what will be reaction on standby database (10g) if i alter , add , delete tablespace or datafile at primary database.

depends on the parameter STANDBY_FILE_MANAGEMENT . please check
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010428

Temporary tablespaces in standby database

Dear experts!
i have just opened in read only mode my standby database for testing purposes.. The tempfiles are not there:
SQL> select * from v$tempfile;
no rows selected
SQL>
how do i proceed?
thanking you in advance for your replies
kind regards
yogeeraj

Hi Yogeeraj,
You can add tempfiles to the temporary tablespace on standby database with alter tablespace command. It only requires tempfile.
Regards
Kamlesh

RMAN-11001: alter database mount standby database

I'm doing a duplicate for a standby database and I'm getting this error
Oracle 8i Tru64
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-03015: error occurred in stored script Memory Script
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel clone_defaul
t
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter database moun
t standby database
RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
Recovery Manager complete.
Any help please

Check for parameter mismatches between parameter file and control file.
Check your parameter file. Check db_name paramter in paramter file used in the standby database.

What is the Use of "Alter database activate standby database"

Hi ,
I appreciate your time.
I just wanted to know what is the use of "Alter database activate standby database" command when doing the failover. How different it will act in failover process. Can we use this command in SwitchOver.
Thanks in advance.

Hi Uwe Hesse,
Wonderfull... good info....
So my understanding is that the use of "ACTIVATE PHYSICAL STANDBY DATABASE" is conditional and depends on the redo log gap and the Database status(Able to mount or not).
Condition 1: If the Db is in Mount state and Redo log gap is successfully filled.
1) Flush any unsent redo from the primary database to the target standby database.
SQL> ALTER SYSTEM FLUSH REDO TO target_db_name;
Note: If the above Statement Completes successfully without any errors.
2) Stop Redo Apply.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
3) Finish applying all received redo data.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
4) Verify that the target standby database is ready to become a primary database.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
5) Switch the physical standby database to the primary role.
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
Condition 2: If the DB is not able Mount and Redo Gap can't be filled.
Important Note: If the the above command in STEP3 gives error, some received redo data was not applied. Try to resolve the cause of the error and re-issue the statement before proceeding.
If the error condition cannot be resolved, a failover can still be performed (with some data loss) by issuing the following SQL statement on the target standby database:
SQL> ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE;
Thanks in advance.

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.

ALTER DATABASE RECOVER MANAGE STANDBY DATABASE

During the creation of Logical Standby database (NOAA2), after issuing the statement:
"ALTER DATABASE RECOVER MANAGE STANDBY DATABASE"
the following error appears:
FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 46 destination NOAA2)
ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
PING[ARC1]: Error 3113 when pinging standby NOAA2.
Can someone please shed any light on the problem.
Thank you.

Perform these steps on Standby and see if it works
%lsnrctl stop
%lsnrctl start

Bringing a Physical Standby database online without (a) tablespace(s)

Dear all,
Is it possible to create a kind of "dblink" in a physical standby database residing in a remote host (another host than the primary production database)? We want to make this standby DB to be online without one tablespace.
Our database consists of 2 parts: a core part (around 55 Gb) - stored in 2 tablespaces, residing in one mounted disk - and an "attachment" part (around 550 Gb) - stored in one tablespace, residing in 2 mounted disks. The attachment part is of less importance. We would like to make a standby DB for the core part and exclude the attachment part (because of its extensive size) to be online.
Currently we can not put this physical standby DB online, since it requires the attachment datafiles to be available.
Would it be a problem if we NFS mount these 2 disks on the host where the standby database resides?
The best solution would be if we can tell the standby DB that there is no need to update the attachment tablespace.
Thanx a lot for anyone reading, thinking and most of all give the solution for my problem...
Agape
Thanx in advance.

Hi Sybrand,
Since we only will use the standby DB in read only mode, maybe the use of a Logical one will be usefull afterall.
Can you please explain how to configure this need (having a standby DB without this one large TB) in a Logical standby DB?
Your help will be highly appreciated.
Thanx
Solution found: Bringing physical standby database to online

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE

Hi,
on 10g R2, how to know if :
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
DISCONNECT;
is already applied ?
thank you.

user522961 wrote:
thanks to all.
Should I issue the following and others on standby or on primary ?
select process,status from v$managed_standby;
Regards.You need execute that from standby instance.In additionally you can see standby instances alert.log.And if this process is active then if you execute this command again then you will get an error like "Media recover is active".

What is the difference between alter database and alter tablespace?

Hi
I was searching for the difference between these 2 commands and have gotten not much conclusive result. Can anyone enlighten me on what is the difference if I were to use ALTER DATABASE OPEN READ ONLY compared to ALTER TABLESPACE x READ ONLY?
My objective to is control, such that sometimes users can edit the database, and other times, not possible to do so.
Thanks in advance.
wy

Hi,
A database can be made with more than one tablespace.
You can have a table called A into a tablespace TSA and a table called B into a tablespace TSB, then if you use ALTER DATABASE OPEN READ ONLY any tablespace can be writen, but if you use ALTER TABLESPACE A READ ONLY, you can't write, insert into table A because it is read only, but you can write, insert rows into the table called B because the tablespace B isn't read only.
You need to do ALTER TABLESPACE B READ ONLY to deny the inserts into table B.
You should do this for all tablespace that make the database.
Regards,
Jordi

Alter tablespace RW on standby database

Similar Messages

Maybe you are looking for