Standby database SWITCHOVER_STATUS field is always NOT ALLOWED

standby database:
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
NOT ALLOWED
select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME          DATABASE_ROLE     OPEN_MODE LOG_MODE     PROTECTION_MODE
omu0               PHYSICAL STANDBY MOUNTED ARCHIVELOG     MAXIMUM AVAILABILITY
select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CLOSING ARCH     539
ARCH     CONNECTED ARCH          0
ARCH     CLOSING ARCH     540
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
MRP0     APPLYING_LOG N/A     541
RFS     IDLE     LGWR     541
RFS     IDLE     ARCH          0
RFS     IDLE     N/A          0

primary datase:
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME          DATABASE_ROLE     OPEN_MODE LOG_MODE     PROTECTION_MODE
omu2               PRIMARY          READ WRITE ARCHIVELOG     MAXIMUM AVAILABILITY
select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CLOSING ARCH     541
ARCH     CLOSING ARCH     542
ARCH     CLOSING ARCH     543
ARCH     CLOSING ARCH     544
ARCH     CLOSING ARCH     545
ARCH     CLOSING ARCH     546
ARCH     CLOSING ARCH     547
ARCH     CLOSING ARCH     548
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CLOSING ARCH     540
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
ARCH     CONNECTED ARCH          0
LGWR     WRITING LGWR     549
31 rows selected.

Similar Messages

Field VBUND does not allow changes to the document ?

If you post the trading partner, the trading partner(Field VBUND)does not allow changes to the document.
I can't change trading partner.
Thanks!!
Message was edited by: Rico Wang

Rico,
Using trn code SM30, modify table V_TBAER and insert the entry
BSEG-VBUND for account type S, D, K, A
and see the effect.
Thanks
Mohit
ps: you may want to check OSS notes as well.

PO price field in PR not allow to change

Hi,
We have facing the problem related to PO price field in PR
Network through we are creating the PR, so system showing the field PO price under the valuation tab is always u201DAs Net Priceu201D and not allowing to change for this field.
My Quire is,
1) How to make this field to default to u201CDo Not Adoptu201D instead of u201CAs Net Priceu201D
2) How to allowing to change this field.
Could you please suggest the solution?
Devendra

One query has been resolved -u201CHow to allowing to change PO price field in PRu201D of follows to steps.
1) Create a Function Authorization
SPRO - Material Management - Purchasing - Authorization Management - Define Function Authorizations for Buyers and create Function Authorizations Ex-1
2) Assign the Function Authorization of specify User ID (SU53), Parameter ID-EFB / EVO & Give Parameter value-1
http://www.kowboyz.nl/blog/copy-price-purchase-requisition-purchase-order/
Network through created the PR system showsu201DAs Net Priceu201D in PO price field. But I want u201CDo Not Adoptu201D in this filed.
Please suggest me.
Devendra

Field exit showing---not allowed to change cross client customizing

hi all ,
when im trying to activate field exit . Its showing---not allowed to change cross client customizing.
how to correct that.
thanks in advance.
sg

hi SG,
first and foremost thing while using field exit is, ask your basis person to include the parameter abap/fieldexit = Y in your instance profile.
Otherwise u can't use the field exits.
Regards....
Arun.
Reward points if useful.

Field WSTAT does not allow changes to the document FI

I try leave the field BSEG-WSTAT changeable in document FI. for this, I added field In the table TBAER for account type S, D, K, A. But in the test the field in document is not ready for input.
Please help me

Dave
Thank for you answer
But, in fact, that is what I did, and like result the field this in the table TBAER. However the field is not ready for imput.
I must rectify the name of the field is BSED-WSTAT, not BSEG-WSTAT
any idea?

Switchover failed,primary status is 'not allowed'

hi,
i used AS5+11gR2+dg and got a problem after normal switchover.
1.the switchover_status of primary shows 'not allowed'
2.log seems not SYNC.
3.dgmgrl shows 'incorrect database role'.
everything goes OK before switchover, how could this happen and how to switchover back?
thanks all.

MahirM.Quluzade 撰写:
Can you paste here:
DGMGRL> show configuration;
DGMGRL> show database verbose <primary>
DGMGRL> show database verbose <standby>
Mahir
1.
DGMGRL> show configuration
Configuration - DRtestdb
Protection Mode: MaxPerformance
Databases:
    testdb     - Primary database
      Error: ORA-16816: incorrect database role
    sztestdbdg - Physical standby database
      Error: ORA-16810: multiple errors or warnings detected for the database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
2.
DGMGRL> show database verbose 'sztestdbdg';
Database - sztestdbdg
Role:            PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag:   (unknown)
Apply Lag:       (unknown)
Real Time Query: OFF
Instance(s):
    sztestdbdg
Database Error(s):
    ORA-16816: incorrect database role
    ORA-16700: the standby database has diverged from the primary database
    ORA-16766: Redo Apply is stopped
Properties:
    DGConnectIdentifier             = 'sztestdbdg'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'OPTIONAL'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg/'
    LogFileNameConvert              = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg/'
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = 'sztestdbdg'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.9.198)(PORT=1528))(CONNECT_DATA=(SERVICE_NAME=SZTESTDBDG_DGMGRL)(INSTANCE_NAME=SZTESTDBDG)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = '/arch/sztestdbdg'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
ERROR
3.
DGMGRL> show database verbose 'testdb';
Database - testdb
Role:            PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
    testdb
Database Error(s):
    ORA-16816: incorrect database role
Properties:
    DGConnectIdentifier             = 'testdb'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'MANUAL'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg'
    LogFileNameConvert              = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg'
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = 'testdb'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.9.197)(PORT=1528))(CONNECT_DATA=(SERVICE_NAME=testdb_DGMGRL)(INSTANCE_NAME=testdb)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = '/arch/testdb'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
ERROR

Physical vs Logical standby database

In the Oracle HA guide, it is mentioned that we must take Logical backup "in addition" to Physical backup (not instead of Physical Backup)
If I run have two systems i.e a Primary System and a Logical standby database system , is it not sufficient protection ? If the primary fails, can I not recover the primary system using the nightly backup I take from the Logical Standby Database.
If it is not sufficient protection, what exactly I will lose ?
Assume I take the nightly complete hot backup backup from the Logical Standby Database instead of the Primary System to save CPU cycles of the primary system.
In other words, it is said that "physical standby database provides zero data loss without any allowance for data divergence" -- What exactly is meant here ?

Thanks Werner for the reply.
1. If there is a human error (dropping a table by mistake), it will be applied to the standby database irrespective of whether it is physical standby or Logical standby. I am unable to see any advantage with Logical standby database in this case. Am I missing something here ?
Or are there any other type of user errors where Logical standby provides an advantage ? Can you please name some ?
2. If I backup from the logical database and if I am willing to "restore" (instead of recover) the primary from this backup in case of a primary failure, is it not the same effort ?
3. Can't we set up a Logical Standby with Maximum Protection Mode ?
I am aware physical standby offers a better performance and it has no data type restrictions. I do not care about these two. Also, I am aware of the extra features provided by Logical database.
Overall, I am trying to see whether physical standby database has any "feature" which I will miss with Logical standby database. I tried my best with Oracle documentation, but I could not get a clear answer.
Any help is appreciated.

Archive apply issue for standby database in Standard Edition.

We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
alter database recover managed standby database disconnect from session;
======================================================================================
This is the status:
SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

The DB version is 10.2.0.5
I can do this to apply at standby DB:
SQL> set autorecovery on
SQL> recover standby database;
Then I tried to run this to leave the session:
alter database recover managed standby database disconnect from session;
Do not seen any apply.
=============================
Here is the last lines of alert log:
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
Clearing online log 1 of thread 1 sequence number 10158
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 10166
Thu Sep 06 15:08:35 EDT 2012
Completed: alter database recover managed standby database disconnect from session
======
We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
Thanks!

Logical standby database questions

Hi,
1.Is it possible to encrypt just the logicals standby database? ie primary is not encrypted but when the data comes to logical standby it gets encrypted?
2. Is it possible to replicate only certain schemas to logcial standby?
Please let me know,
Thanks a lot
Sumathy

Hi Sumathy,
1.) Yes this is possible
2.) Yes also possible. However Logical Standby will always gather all information from the primary, and only skip in the apply process.
If you want to lessen your transfer, then you should use other replication mechanism like
- Golden Gate (preferred but does cost money)
- Streams (free, but depricated)
Regards
Sebastian

URGENT:Diagnose The Steps for Creating a Standby Database

Why Following Steps Can Not Succeed? What are the problems?
The Steps of Creating a Physical Standby Database
SQL>alter system set db_recovery_file_dest_size=2000m scope=both;
SQL>alter system set db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area' scope=both;
SQL> shutdown immediate
SQL> startup mount
SQL> alter database archivelog;
SQL>alter system set db_flashback_retention_target=120 scope=both;
SQL> alter database flashback on;
SQL> alter database force logging;
#The Primary Database Pfile after being edited
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# SGA Memory
sga_target=370147328
# Job Queues
job_queue_processes=10
# Shared Server
dispatchers="(PROTOCOL=TCP) (SERVICE=orcl10XDB)"
# Miscellaneous
compatible=10.2.0.1.0
# Security and Auditing
audit_file_dest=C:\oracle\product\10.2.0/admin/orcl10/adump
remote_login_passwordfile=EXCLUSIVE
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=122683392
# Database Identification
db_domain=""
db_name=orcl10
# File Configuration
control_files=("C:\oracle\product\10.2.0\oradata\orcl10\control01.ctl", "C:\oracle\product\10.2.0\oradata\orcl10\control02.ctl", "C:\oracle\product\10.2.0\oradata\orcl10\control03.ctl")
db_recovery_file_dest=C:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size=2147483648
# Cursors and Library Cache
open_cursors=300
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_tablespace=UNDOTBS1
# Diagnostics and Statistics
background_dump_dest=C:\oracle\product\10.2.0/admin/orcl10/bdump
core_dump_dest=C:\oracle\product\10.2.0/admin/orcl10/cdump
user_dump_dest=C:\oracle\product\10.2.0/admin/orcl10/udump
# Processes and Sessions
processes=150
# Cache and I/O
db_block_size=8192
db_file_multiblock_read_count=16
DB_NAME=orcl10
DB_UNIQUE_NAME=orcl10
LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl10,stdby4)'
LOG_ARCHIVE_DEST_1=
'LOCATION=/arch1/orcl10/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=orcl10'
LOG_ARCHIVE_DEST_2=
'SERVICE=stdby4 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=stdby4'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES=30
FAL_SERVER=stdby4
FAL_CLIENT=orcl10
DB_FILE_NAME_CONVERT='stdby4','orcl10'
LOG_FILE_NAME_CONVERT=
'/arch1/stdby4/','/arch1/orcl10/','/arch2/stdby4/','/arch2/orcl10/'
STANDBY_FILE_MANAGEMENT=AUTO
SQL> create spfile from pfile;
RMAN> connect target
RMAN> backup database;
###TheBackupHandle==C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL10\BACKUPSET\2007_11_06\O1_MF_NCSNF_TAG20071106T064915_3LZ7LRN8_.BKP
RMAN> backup datafile1,2,3,4,5;
C:\DocumentsandSettings\Administrator>mkdir C:\ORACLE\PRODUCT\10.2.0\ORADATA\temp\stdby4
SQL> alter database create standby controlfile as '/temp/stdby4.ctl';
SQL> create pfile='/temp/initstdby4.ora' from spfile;
#Pfile Edited for The Physical Standby Database
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# SGA Memory
sga_target=370147328
# Job Queues
job_queue_processes=10
# Shared Server
dispatchers="(PROTOCOL=TCP) (SERVICE=stdby4XDB)"
# Miscellaneous
compatible=10.2.0.1.0
# Security and Auditing
audit_file_dest=C:\oracle\product\10.2.0/admin/stdby4/adump
remote_login_passwordfile=EXCLUSIVE
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=122683392
# Database Identification
db_domain=""
db_name=orcl9
# File Configuration
control_files=("C:\oracle\product\10.2.0\oradata\stdby4\control01.ctl", "C:\oracle\product\10.2.0\oradata\stdby4\control02.ctl", "C:\oracle\product\10.2.0\oradata\stdby4\control03.ctl")
db_recovery_file_dest=C:\oracle\product\10.2.0/stdby4/flash_recovery_area
db_recovery_file_dest_size=2147483648
# Cursors and Library Cache
open_cursors=300
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_tablespace=UNDOTBS1
# Diagnostics and Statistics
background_dump_dest=C:\oracle\product\10.2.0/admin/stdby4/bdump
core_dump_dest=C:\oracle\product\10.2.0/admin/stdby4/cdump
user_dump_dest=C:\oracle\product\10.2.0/admin/stdby4/udump
# Processes and Sessions
processes=150
# Cache and I/O
db_block_size=8192
db_file_multiblock_read_count=16
DB_UNIQUE_NAME=stdby4
LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl10,stdby4)'
DB_FILE_NAME_CONVERT='orcl10','stdby4'
LOG_FILE_NAME_CONVERT=
'/arch1/orcl10/','/arch1/stdby4/','/arch2/orcl10/','/arch2/stdby4/'
LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc
LOG_ARCHIVE_DEST_1=
'LOCATION=/arch1/stdby4/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=stdby4'
LOG_ARCHIVE_DEST_2=
'SERVICE=orcl10 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=orcl10'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
STANDBY_FILE_MANAGEMENT=AUTO
FAL_SERVER=orcl10
FAL_CLIENT=stdby4
C:\Documents and Settings\Administrator>oradim -new -sid stdby4 -startmode manual
Create Listener and Network Service Name for Standby Database.Stop and start listener(not need)
SQL>create spfile from pfile='/temp/initstdby4.ora';
C:\Documents and Settings\Administrator>set oracle_sid=stdby4
SQL> startup mount;
ORA-01078: failure in processing system parameters
LRM-00109: ???????????????? 'C:\ORACLE\PRODUCT\10.2.0\DB_10\DATABASE\INITSTDBY4.ORA'
Message was edited by:
frank.qian
Message was edited by:
frank.qian

you have now two different pfiles: one in c:\temp\initstdby4.ora. and %ORACLE_HOME%\database\initstdby4.ora.
You are using the latter, as you didn't specify pfile= in your startup mount.
Also, if you are using a spfile, the only line in a pfile should be: spfile=....
In your pfile you are mixing up Unix like file locations with \ and Windows file locations with /
Could you please read the docs
more closely
more closely
more closely
and work
more carefully
more carefully
more carefully
It is very simple, but you must work carefully.
Sybrand Bakker
Senior Oracle DBA

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Creating standby database from ASM production database in standard edition

Hi,
I am using oracle 10g release 2 standard edition. I recently created a database instance and wanted to create a standby database instance. After sorting out how to achieve this without managed standby and data guard I finally got it working and the shipped archive logs are applied and working well on the standby database.
Now I am thinking of re-creating my production database and using ASM for storage managment. By doing this can a standby database still be created from a primary database using ASM? I want to be sure I can before I commit to using ASM for the production instance and manually creating a standby database from that instance.
Note: I am using standard edition not enterprise edition.

Hi
For Oracle SE standby, you can visit www.anbultechnologies.co.uk , they have a brilliant product name DRMC which is Automatic disaster recovery solution with automatic failover in case primary goes down due to any reason.
We are using this product for more than 2 years and it works like a dream using Oracle Standard Edition. We have depolyed more databases and Standby solution within the prices of 2 EE edition licenses.
You can give ma try as well.
website address is www.anbultechnologies.co.uk

Creating new tables in Logical Standby database

Hi
I have a requirement to create new tables in logical standby database. These tables will not be present on primary database. Is it possible to do this ?
I have a new schema already created which has the privilege to CREATE new table.
I have stopped the logical standby apply.
When I am now trying to create a new table but it is failing with error : insufficient privileges.
When I am trying to run below statement on new schema it is also failing with error of insufficient privileges.
alter session disable dataguard;
Please help.

user8819121 wrote:
Thanks Mahir,
I was able to create the table after logging in as sysdba.
But I need my user on that table to execute DML statements. My user has privileges to insert,delete and update any table.
I tried the following statements to disable the guard but it is sill not working
ALTER DATABASE GUARD STANDBY.
Do I need to skip the tables created using dbms_logstdby package to not making it part of SQL Apply ? I guess not since the table is not in primary database.
Amit
You can skip only on primary, your created schema on Standby is not in primary.
Then you must change Status of data guard to NONE. NONE is means is not any security on your data.
In Guard status NONE can change all schema data.
Please check link: http://docs.oracle.com/cd/E11882_01/server.112/e10700/manage_ls.htm#CHDGFGHG
Following tests on user created before guard status is change from ALL to STANDBY.
C:\Users\Administrator>sqlplus / as sysdba
SQL> conn test/test
Connected.
SQL> select table_name from user_tables;
TABLE_NAME
T
SQL> insert into t values(22);
insert into t values(22)
ERROR at line 1:
ORA-16224: Database Guard is enabled
SQL> conn / as sysdba
Connected.
SQL> select guard_Status from v$database;
GUARD_S
ALL
SQL> alter database guard standby;
Database altered.
SQL> conn test/test
Connected.
SQL> insert into t values(1);
insert into t values(1)
ERROR at line 1:
ORA-16224: Database Guard is enabled
SQL> conn / as sysdba
Connected.
SQL> select guard_Status from v$database;
GUARD_S
STANDBY
SQL> alter database guard none;
Database altered.
SQL> select guard_Status from v$database;
GUARD_S
NONE
SQL> conn test/test
Connected.
SQL> insert into t values(1);
1 row created.
SQL> commit;
Commit complete.And Now I want share with you new tests :)
Now user creating when after guard status change
SQL> drop user test cascade;
User dropped.
SQL> select guard_status from v$database;
GUARD_S
STANDBY
SQL> create user test identified by test;
User created.
SQL> grant create session, resource, create table to test;
Grant succeeded.
SQL> conn test/test
Connected.
SQL> create table t (n number);
Table created.
SQL> insert into t values(1);
1 row created.
SQL> commit;
Commit complete.
SQL>It means when guard status is ALL then all of user created guarding.
When you changed status to STANDBY then Logical Standby guard only primary schema and created schema before change.
NONE is not guard any schema. it means you can delete standby schema data too.
Regards
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on Apr 19, 2013 4:07 PM

Implementation of ORACLE9i RMAN physical standby database`

Sir's,
How to implement RMAN in the physical standby database

Hi Ashu Goel,
Can u let me know any thing abot the prerequistw of implementation with the configuration settings of the above said.If I understand you correctly you want to use rman to backup an already existing dataguard setup.
Doing this would be very similar as a normal rman backup with the limitation you have to stop the recovery during the backup window and run the backup in mount mode.
To make a consistent backup of the standby database, make sure that the last shutdown of the standby database was clean and that it was not placed in recovery mode after that time, and then mount the control file. For example:
sqlplus SYS/oracle@sbdb1 <<EOF
SHUTDOWN IMMEDIATE
STARTUP NOMMOUNT PFILE=initSTANDBY.ora
ALTER DATABASE MOUNT STANDBY DATABASE;
EOF
You can back up the standby database when it is in any other mode, but the backups will be inconsistent.
Start RMAN and connect to the standby database with the TARGET keyword (not the AUXILIARY keyword) and the recovery catalog database. You must be connected to the recovery catalog. For example, enter:
% rman TARGET SYS/oracle@sbdb1 CATALOG rman/cat@catdb
If do not have automatic channels configured, then manually allocate one or more channels of type DISK or sbt. Note that you are connected to the standby host, so the backups are made by server sessions on the standby (not the primary) host.
This example backs up all the standby datafiles as well as the control file and archived logs by using automatic channels:
BACKUP DATABASE PLUS ARCHIVELOG;
Regards,
Tycho

Physical Standby database Oracle 10g Standard Edition

Hello,
I open a new question about testing a standby database a because of this:
I realize that my standby database is 10g Standard and not Enterprise and not 11g.
Because for testing we plan to modify data on Standby, we are looking for some way to restore Standby to the point before testing.
So, I can't use Flashback Recovery Area for restoring my database to a certain point after testing.
In this scenario, the only way that I think is:
On Standby
- Shutdown database
- Copy by O/S all datafiles, temp files, control files and redo logs. That will be my backup before testing.
- Open database, test and modify data
- When test is finished, shutdown database
- Copy and replace by O/S all datafiles, temp files, control files and redo logs from backup place
- Open database as standby and apply all archived redo logs needed.
Would be it work without problem or should I copy other files?

user521219 wrote:
Hello,
I open a new question about testing a standby database a because of this:
I realize that my standby database is 10g Standard and not Enterprise and not 11g.
Because for testing we plan to modify data on Standby, we are looking for some way to restore Standby to the point before testing.
So, I can't use Flashback Recovery Area for restoring my database to a certain point after testing.
In this scenario, the only way that I think is:
On Standby
- Shutdown database
- Copy by O/S all datafiles, temp files, control files and redo logs. That will be my backup before testing.
- Open database, test and modify data
- When test is finished, shutdown database
- Copy and replace by O/S all datafiles, temp files, control files and redo logs from backup place
- Open database as standby and apply all archived redo logs needed.
Would be it work without problem or should I copy other files?yes, It will work.
it comes under Refresh of database, use --> cleanup --> restore.
If its enterprise edition , you can use procedure mentioned in this note How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]
Edited by: CKPT on Jul 5, 2012 11:01 PM

Standby database SWITCHOVER_STATUS field is always NOT ALLOWED

Similar Messages

Maybe you are looking for