Standby doubts

Hello all,
1)Standby Redo Logs do not to be multiplexed. Is it bacause to prevent additional writes by RFS process to SRL?
2) How can I open the standby in read only mode if I have no online redo logs?
3)If standby redo logs files is not present then RFS process directly creates archive logs?

1)Standby Redo Logs do not to be multiplexed. Is it bacause to prevent additional writes by RFS process to SRL? Yes, if you configure multiplexed standby redo log files it has to write simultaneously.
2) How can I open the standby in read only mode if I have no online redo logs?To open standby database in open-mode still it wont use any Online redo log files, In read only it wont perform any read/write operations, hence no need of online redo log files. Moreover if you have duplicated the online redo log files exist but they will be in idle mode, Once you performed role transition like switchover/failover then only they will be used.
3)If standby redo logs files is not present then RFS process directly creates archive logs?Yes, it will create.

Similar Messages

How to upgrade standby doubt

hello,
I read various Oracle documents, guides and metalink notes but I still have some doubts. Perhaps I missed something.
starting env: dataguard (manual config, without broker) env with primary and physical standby in 11.2.0.1 on Linux x86_64
I don't want to go with rolling upgrades or similar; I'm on a test environment and also for production I can tolerate some downtime during the week end.
My upgrade scenario is to install sw in new oracle_home as recommended.
One note: the link provided in note 884522.1 gives a file for preupgrade (utlu112i.sql) that is not current ... I had to make a clean install of 11.2.0.2 and get the file provided inside rdbms/adin directory....
I start runInstaller with primary DB open and physical in mount with managed recovery and in sync
I install new binaries and then complete the dbua step (100% without errors)
I only had to change my log_archive_dest_2 that was
service=TESDB1DR ASYNC DB_UNIQUE_NAME=TESDB1DR VALID_FOR=(primary_role, online_logfile) COMPRESSION=ENABLE
and worked in 11.2.01. but dbua complained about syntax and so I had to change in:
service=TESDB1DR ASYNC DB_UNIQUE_NAME=TESDB1DR VALID_FOR=(online_logfiles,primary_role) COMPRESSION=ENABLE
Now I have my primary db in new version.
dbua didn't update the tnsnames.ora, so I get this on primary alert.log
Thu Nov 04 15:25:33 2010
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'TESDB1DR'. Error is 12154.
while at the end of upgrade, on standby alert.log I got:
TNS-00507: Connection closed
nt secondary err code: 0
nt OS err code: 0
Error 12537 received logging on to the standby
FAL[client, USER]: Error 12537 connecting to TESDB1 for fetching gap sequence
Errors in file /app/oracle/diag/rdbms/tesdb1dr/TESDB1DR/trace/TESDB1DR_pr00_21338.trc:
ORA-12537: TNS:connection closed
Errors in file /app/oracle/diag/rdbms/tesdb1dr/TESDB1DR/trace/TESDB1DR_pr00_21338.trc:
ORA-12537: TNS:connection closed
Thu Nov 04 13:23:12 2010
What are the steps to do at standby? The same as in primary:
1) install binaries for 11.2.0.2
2) upgrade db
and only at the end
3) modify parameters on both instances tnsnames.ora so that they are able again to communicate
Can the standby db stay in mount + recovery mode while upgrading?
I hope I have not to refresh the whole standby....
Thanks for suggestions,
Gianluca

What do you mean by "Do I have to manually update my .ora files?" and where Primary or Standby?When on standby I select install software only, I get a new $ORACLE_HOME/network/admin that is empty
So I presume I have to copy my 11.2.0.1 tnsnames.ora and listener.ora to the new path
And to change inside my listener.ora the line
(ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1)
matching now
(ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_2)
at least for the instances I want to upgrade (if more than one)
Also, I noticed that upgrading the primary with dbua, it got as a result this kind of "strange" tnsnames.ora:
# tnsnames.ora Network Configuration File: /app/oracle/product/11.2.0/dbhome_2/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
TESDB1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = primary_server_name)(PORT = 1522))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = TESDB1)
LISTENER_TESDB1 =
(ADDRESS = (PROTOCOL = TCP)(HOST = primary_server_name)(PORT = 1522))
And this listener.ora
# listener.ora Network Configuration File: /app/oracle/product/11.2.0/dbhome_2/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1522))
(ADDRESS = (PROTOCOL = TCP)(HOST = primary_server_name)(PORT = 1522))
ADR_BASE_LISTENER = /app/oracle
So it seems it didn't update the network config. It has no knowledge of my standby TESDB1DR
I presume I can copy listener.ora and tnsnames.ora as configured in 11.2.0.1...
From 11.2.0.1 to 11.2.0.2 I don't think about major changes in these files... am I correct?
Thanks for your time.
Gianluca

Few Standby doubts

Hello all,
I have few queries regarding standby database.
1)Correct me if I am wrong. On primary Database Standby Redo log is required for switchover and on standby database Standby Redo log is required for
--Real time Apply
--Maximum protection or Maximum availability
Am I correct?
2)My database is in Maximum Performance mode. I set up following entry on init.ora:
LOG_ARCHIVE_DEST_2=’service=standby LGWR ASYNC’. My question is do I need to have STANDBY Redo log file on standby database in order to use LGWR transport (LGWR ASYNC)mode from primary? Without Standby redo log on standby database can it transport redo data from primary to standby using LGWR transport mode (LGWR ASYNC)?
3)I have changed from the "ARCH" attribute to "LGWR" attribute of the LOG_ARCHIVE_DEST_n initialization parameter. But I have not changed the protection mode. I would like to know whether is there any impact in the behavior of the database, if we do not change the mode from "MAXIMUM PERFORMANCE" to "MAXIMUM AVAILABILITY"?
Thanks ans reagrds

Hi,
concerning your questions
What Version of Oracle you are using?
1)Correct me if I am wrong. On primary Database Standby Redo log is required for switchover and on standby database Standby Redo log is required for
In Oracle Release 11.2 you should have to create Standby Redolog in all protection modes.
Yes, you create on the primary side Standby Redologs if you do a role change.
2)My database is in Maximum Performance mode. I set up following entry on init.ora:
LOG_ARCHIVE_DEST_2=’service=standby LGWR ASYNC’. My question is do I need to have STANDBY Redo log file on standby database in order to use LGWR transport (LGWR ASYNC)mode from primary? Without Standby redo log on standby database can it transport redo data from primary to standby using LGWR transport mode (LGWR ASYNC)?
Yes, you should create standby redologs. ARCH transport is in Oracle 11g deprecated.
3)I have changed from the "ARCH" attribute to "LGWR" attribute of the LOG_ARCHIVE_DEST_n initialization parameter. But I have not changed the protection mode. I would like to know whether is there any impact in the behavior of the database, if we do not change the mode from "MAXIMUM PERFORMANCE" to "MAXIMUM AVAILABILITY"?
I don't understand your question. You said under point 2.) that LGWR ASYNC in is configured. But now you say LGWR ARCH.
Only in Oracle Version 11.2 it is possible to change the protection mode via dgmgrl command without restart the database.
So first of all what plattform and Oracle Release you are using?
regards
SPA2

Standby doubt

Hi Experts im on 11G R2 database on linux 5.4, while configuring a physical standby from scratch, remember i dont want to use RMAN, when i copy datafiles from primary to standby, is it necesarry to shut down primary and then copy datafiles ? or i can use SCP command and copy even though primary is up in read write mode ?

Hello;
"SCP command and copy even though primary is up in read write mode"
The answer to this is no.
If you want to SCP your primary you have to:
1. Create the directories for the file on the Standby server
2. Shutdown the primary database and then SCP the data files, online logs and temp files over.
If you use this method you still have to account for the standby control file and the password file.
My notes on this method are here:
Data Guard Setup on Oracle 11 Step by Step
Best Regards
mseberg

Logical Standby Database - Doubts

Hi everyone,
I have a doubt about this view: dba_logstdby_unsupported;
This view shows up me 400 tables, so i understand that an operation DML on these tables won't be replicated in the other node?, or only the fields allowed will be replicated in the news record? or new record on these tables will be replicated if these records have NULL value in the fields doesn't allow.
Thank you very much if someone can help me with this doubts.
Regards

This is what the documentation says:
If the primary database contains unsupported tables, SQL Apply automatically excludes these tables when applying redo data to the logical standby database.Source: Unsupported Tables

Standby database doubts

Hi All,
I have some doubts in Oracle Standby database configuration and log transfer and redo apply.
I have read the below document.
Oracle® Data Guard Concepts and Administration
Now my doubts are *(in Physical standby database with Maximum performance mode)*
1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?
Please Advice..
TIA,

1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?It is not for role transition.
A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases.
You can recover more data than only applying archive logs in case of failure.
SRLs' are a must for real time apply.
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?The data is directly written from production to SRL of standby database using lgwr process(with the help of RFS), that is why it real time. Not waiting for a log switch. See the [diagram.|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1021537]
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?No. Only standby redo log will generate archived logs.
Regards,
S.K.

Few errror/doubts in Primary and Standby server - Need Help

Hi All,
I am having below doubts/errors. I need help to solve all the below questions.
I configured Dataguard successfully. Now the sync is upto date using the below parameters (using 11g):
at primary:
log_archive_dest_1=
log_archive_dest_2='SERVICE=standby.123 arch'
standby_file_management=auto
at sandby:
log_archive_dest_1=
standby_file_management=auto
Still i face below messages in the alertliog. Can anybody clearly explain me all the points.
Primary:
ORA-1652: unable to extend temp segment by 640 in tablespace NEWTEMP
I get this error when my archvie destination got filled up, later we released the enough space, the archived are generating. Still i see this message once in between. Need to solve this.
Primary:
Checkpoint not complete ( i see this message very often, want to get rid of this)
standby:
kcrrvslf: active RFS archival for log thread 1 sequence (sometimes i see this KCRRVSLF)
standby:
check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain afequate log switch information to resolve archivelog gaps. (also get this message in between the alertlog file in standby)
Standby:
FAL[client]: Error fetching gap sequence, no FAL server specified (this is very often message. How to remove this, what needs to be added. Do i need to add the below parameters)
FAL_CLIENT
FAL_SERVER
Thanks in advance.
Pas Moh
[email protected]

Pas Moh wrote:
Hi All,
I am having below doubts/errors. I need help to solve all the below questions.
I configured Dataguard successfully. Now the sync is upto date using the below parameters (using 11g):
at primary:
log_archive_dest_1=
log_archive_dest_2='SERVICE=standby.123 arch'
standby_file_management=auto
at sandby:
log_archive_dest_1=
standby_file_management=auto
Still i face below messages in the alertliog. Can anybody clearly explain me all the points.
Primary:
ORA-1652: unable to extend temp segment by 640 in tablespace NEWTEMP
I get this error when my archvie destination got filled up, later we released the enough space, the archived are generating. Still i see this message once in between. Need to solve this.This error has absolutely nothing to do with the handling of archive logs, the status of archivelog destination, or primary/standby. Any relation you thought you saw was pure coincidence.
>
>
Primary:
Checkpoint not complete ( i see this message very often, want to get rid of this)
Here is the very first hit I got when I googled "oracle checkpoint not complete". Tom says it better than I would have.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:69012348056
standby:
kcrrvslf: active RFS archival for log thread 1 sequence (sometimes i see this KCRRVSLF)
A quick google of that one, and it looks like it is not even an error, but rather simply an informative
>
standby:
check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain afequate log switch information to resolve archivelog gaps. (also get this message in between the alertlog file in standby)
In that case I would check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large enough to maintain adequate log switch information to resolve archivelog gaps.
How big is that? Well, at least bigger than it is now. Beyond that, it would have to be "large enough to maintain adequate log switch information to resolve archivelog gaps" Just play with it until you get the result you want.
>
Standby:
FAL[client]: Error fetching gap sequence, no FAL server specified (this is very often message. How to remove this, what needs to be added. Do i need to add the below parameters)
FAL_CLIENT
FAL_SERVER
Thanks in advance.
Pas Moh
[email protected]

Doubt regarding switchover from logical standby to primary

I am using Oracle 10g databases on Linux environment
I was trying creating a data guard configuration and once I was successfully done I created a logical standby database from the physical standby . Then I was trying to do a switchover .
By mistake I gave the prepare switchover command in the logical standby before executing it in the primary . And then when I gave it in the primary both the status turned to be "PREPARING SWITCHOVER"
In logical standby
SQL> ALTER DATABASE PREPARE TO SWITCHOVER TO PRIMARY;
Database altered.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
PREPARING SWITCHOVER
In primary
SQL> ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY;
Database altered.
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
PREPARING SWITCHOVERNow I am not able to commit any of them to primary or logical standby
In primary
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;
ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY
ERROR at line 1:
ORA-16217: prepare to switchover has not completed
ORA-06512: at line 1
In logical standby
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
ALTER DATABASE commit TO SWITCHOVER TO PRIMARY
ERROR at line 1:
ORA-16109: failed to apply log data from previous primaryLet me know what should be done now ? Is there anyway to solve this issue ?

Can you try using the following first on Primary and then on Standby?
ALTER DATABASE PREPARE TO SWITCHOVER CANCEL;

Initial setup for standby database - doubts ??

Hi,
While creating a physical standby database from a primary database what is the initial setup in case of the standby database which will be created.
1.Is it that I will only install the oracle with no starter database and then continue with the steps for creating standby database.
2. The SID has to be the same for both the database or can it be different.
Waiting for your answer.
sl

1)
Fulfill the prerequisites
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14239/standby.htm#i58150
2) It has to be same.

What is the diffrence between ' Contolfile ' and ' Standby Controlfile' ???

Hi Guru's,
Can someone please help me out with the diffrences between a 'Control File' and 'Standby Controlfile'.
Thanks in advance
Regards,
Girish

Kind of reply you can always expect from Sybrand...anyways...the controlfile of any production database would always be having a bit in itself which identifies a database as a primary or a standby database, so whenever you try to query select database_role from v$database; for any production database it would always give output as PRIMARY and for a standby it would always give output as PHYSICAL STANDBY..Hope it clears your doubts
Regards,
Ajinkya

Creating a Standby Database with the Same Directory Structure

Hello gurus,
I am self-learning the feature Oracle Data Guard, so I am testing it on Oracle 10g R2.
At Oracle documentation there is a section F.4.: Creating a Standby Database with the Same Directory Structure*, that explains how to create a standby database with RMAN but there is something that I don´t understand:
In the standby server, I created a database with the SID equal to production database* with the objetive to have the same directory structure, but when I try to startup nomount the standby database with pfile appear this expected error:
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
So my question is: Is possible have the Same Directory Structure on both: Production and StandBy server?
Thanks in advanced.

Uwe and mseberg: thanks for your quick answers
I have a doubt: How can you have the same directory structure if you have differents SIDs?, for example if you follow the OFA suggestions you would must have:
On Production server: */u01/app/oracle/oradata/PRIMARY/system.dbf*
On StandBy server: */u01/app/oracle/oradata/STANDBY/system.dbf*
Or you created the directory structure manually on StandBy server? For example replacing the string STANDBY* to PRIMARY* before create the database using dbca.
Do you understand my doubt? Excuse me for my english.
Thanks.

Differences in creating a Standby database in RAC

Hi All
   SO...: Solaris 11 SPARC 64
   DB...: 11.2.0.3.6 (64 bits)
   My experience regarding creating Physical Standby Databases is restricted in only single instances to single instances. I am reading the book "Oracle Database 11g Release 2 High Availability", but, in parallel, i would like to hear from the experienced DBAs here some opinions and recomendations in how to implement a RAC to RAC solution. Below are my doubts:
   1) In single instance, using RMAN Backup to create the Physical Standby, i have to create manually a static Listener Entry. But in a RAC env, the listener is a resource, so, i have to create that resource in the Clusterware manually, or there is other approach?
   2) I have to create a pfile and start the instance in NOMOUNT mode, but in RAC, i have to start all the nodes in NOMOUNT, or just one node is sufficient?
   3) The archives will be replicated from FRA to FRA. Is this the best approach?
   My main concern is with the Listener and SCAN questions... If you have any considerations, they will be most welcome.
   Thanks in advance.

Following link might be helpful
http://www.oracledba.org/11gR2/dr/11gR2_dataguard_RAC_to_RAC.html

Archive log shipping error in Logical standby database

Hi,
We have Primay and logical database configuration both in RAC in Production. both database are in 10.2.0.4.
Everyday we having issue of some archivelog not transfered to logical server around 2AM. I am having good exposure in Logical/Log minor/Goldgendate and can say fal server/client server configuration is correct.
Can you guys please give some input of what can cause this.
Yes we take RMAN backup of both database around 1:30 using control file instead of recovery catalog and I doubt this put lock on control file and cause this issue.
I would be glad of you could help me out in this.
Thanks a lot!
Pradeep
Below is the configuration of archive/fal on both database.
PIP1REP2 is logical database(instance 2) where apply process is running/configured.
Primary server configuration on (PIP11) (same are on other instances).
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP2
fal_server string PIP11
SQL> sho parameter archive
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=+ARCH01
log_archive_dest_2 string SERVICE=pip1rep2 lgwr async
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string ENABLE
llog_archive_local_first boolean TRUE
log_archive_max_processes integer 10
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
Logical server configuration
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP
fal_server string pip11, pip12, pip13, pip14, pi
p15
SQL> sho parameter archive
NAME TYPE VALUE
alog_archive_dest_1 string LOCATION=+ARCH01/PIP1REP valid
for=(onlinelogfiles, all_rol
es) db_unique_name=pip1rep
log_archive_dest_2 string LOCATION=+ARCH01/PIP1REP/ARCH_
DEST2_STANDBY_LOGS VALID_FOR=(
STANDBY_LOGFILES,STANDBY_ROLE)
db_unique_name=pip1rep
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string enable
log_archive_local_first boolean TRUE
log_archive_max_processes integer 20
log_archive_min_succeed_dest integer 1
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string +ARCH01

Do you think creating recovery catalog will resolve it?
Yes, I do. (But I do not know for sure)
If it helps when I got to this part I decided to backup either the Primary or the Standby, but not both.
I decided Primary only and documented how to recreate my standby without downtime.
I hope this helps.
regards.

Logical Standby Issue

Hi Friends,
I have 4 doubts. Please help me to clear my confusion.
Doubt 1:-
I have one primary and one logical standby database. When i restart the primary database or logical standby database or whenever data is not transffering to standby database, I execute the package "EXECUTE DBMS_LOGSTDBY.BUILD;". Then it starts to transfer the data to standby. My question is executing this package many times will affect the primary database? or my configuration is wrong?
Doubt 2:-
I configured DGMGRL for both database and i can switch over and switch back to logical standby database. It automatically start to apply the data to new logical standby database. But when i switch back to old primary database, It didnt transfer the data automatically. So i execute the package "EXECUTE DBMS_LOGSTDBY.BUILD;" in primary. Then it starts to transfer the data. My question is my switchback is wrong? or it happens like that only?
Note:- I check the verbose of both database before switchback. It show success.
Doubt 3:-
When i check the switchover status in logical standby database, It show "NOT ALLOWED". Even though i can switch over by using dgmgrl. Why logical standby database showing "NOT ALLOWED"?
Doubt 4:-
Is it any possible to view that what commands executing by dgmgrl process in background while it switchovering to logical standby database.?
Because when i try to switchover manually it didnt work. Many times i tried. But in dgmgrl, I simply give "switchover to logdb;", It works.
Please help to me to understand clearly.
Thank you in advance.

Wrong forum mate. This forum deals with SQL and PL/SQL languages and related issues - not database administration and configuration issues.
The shared memory error is not unusual though ito SQL and PL/SQL. It is often a result of not using sharable SQL - in other words, SQL statements that are not using bind variables.
This causes additional consumption and fragmentation of shared pool memory. The very worse thing to do in this case would be to increase the size of the shared pool. That is akin to moving the wall a bit further away so that one can run even faster and harder into it.
But I'm merely speculating as you may have another cause for this problem. I suggest that you:
- post this in the [url http://forums.oracle.com/forums/forum.jspa?forumID=61]Database Forum
- research this error on [url http://metalink.oracle.com]Metalink

Impact of force_logging on standby database in 10g?

Hi there,
We have a 10.2.0.5 database from which we want to setup a standby database...
We took a hot backup of the primary and send it to the standby server but at that time we realized that force logging is not enabled at the Primary before we took the hot backup!
Can you please suggest what are our options at this stage without losing any data and without a need to redo the hot backup again since it is a huge database?
- If we turn the force_logging on now(on Primary) and then set up the standby using the backup taken prior to force_logging ON - would it cause any issues?
Any help would be greatly appreciated.
Thanks.

No it won't because the hot backup is a copy period. So do it ASAP and the Archive will handle the rest.
So your hot backup is the Standby copy ( exact copy ). Just make sure forced logging is on and the archive with keep the data in sync.
If you delay then you are up the creek without a paddle as NOLOGGING actions are bound to occur and then the Standby data will not match the Primary.
If you have doubts your best option is to roll the standby forward using RMAN Incremental Backups :
http://www.oracle-ckpt.com/?s=incremental&op.x=31&op.y=11
Best Regards
mseberg

Standby doubts

Similar Messages

Maybe you are looking for