Continiously log switching, one node unavailable

We run 4-node RAC 9.2.0.4 on Solaris 9. Recently, one of nodes crashed due to hardware failure. After some time since this crash, i executed the command forcing log switching within the cluster: 'Alter system archive log current'. After this command, our redo logs started switching continuously - every 5-6 seconds. Generated archived logs where almost empty - they contained only a few blocks, often only one - header, i suppose. The problem was resolved only after the thread of the died node was disabled with command 'Alter database disable thread 4;'.
I made a few experiments to investigate this problem. It seems that every command forcing redo log switch in a RAC leads to such excessive log switching, when one of nodes in cluster is unavailable. I tested 'Alter system archive log current', ARCHIVE_LAG_TARGET parameter, and the command 'Alter system switch logfile', executing from an Oracle job. In all these cases redo logs began switching continuously when the commands had beed executed or it was time to switch logs by ARCHIVE_LAG_TARGET parameter. Is there any possibility to force redo logs switch in all threads in a cluster without any problems, when one node is unavailable? We would like to switch logs every 10 minutes - to limit the amount of data that can be lost in case of whole cluster failure...
Thanks in advance
Alexey Sergeyev
[email protected]

Joel, thank you for replay. I tested forcing log switch with one node down on different ways - within a job or without one. The command 'Alter system archive log current' was executed without any job from SQL*Plus command line. This triggered continuously log switching on working nodes. The parameter ARCHIVE_LAG_TARGET does'nt produce any job - at least this job is'nt shown in DBA_JOBS. This parameter leads to continuously log switching on survived nodes, when one node goes down.
I tried make a job, one per instance, with 'Execute immediate ''Alter system switch logfile''' command inside. Executing of such a job also triggered continuously log switching on working nodes...
It seems that forcing log switching in a cluster works only when all is fine - all nodes are running. Is it Oracle bug? Or is it expected, but not documented behaviour?
Alexey Sergeyev
[email protected]

Similar Messages

SCAN IP and all 2 VIP listner is unavailable for 1+ min when one node down

I have two redhat Linux nodes running the Oracle 11.2.0.3
Everything is OK except, when I powerdow one node (cold or soft reset). the VIP and SCAN lisnter stop working for 1+ minutes. (Using Navicat connection check, all connections are unavailabl for a while)
Is it normal? The problem is the application DB connection timeout is about 20 seconds.

Hi,
even though this sounds quite long (especially for a hard kill of the node, not a reboot), it does not matter if you configured your application correctly:
http://www.oracle.com/technetwork/products/clustering/overview/awm11gr2-130711.pdf
Since the application will move to the VIP/SCAN IP running on the second node after 3 sec (connection outbound timeout).
However failover of VIP and SCAN should be in seconds not minutes...
And it should not have an effect on all connections - just the ones going to that VIP/SCAN on that node.
Regards
Sebastian

Failover did not happen when one node went down!!! PLEASE HELP

Hi gurus,
Yesterday one disaster struck my RAC database. We have two node cluster and it is 10.2.0.2, both of them located in different sites, yesterday suddenly power went down and the one of the network switch went down and got destructed, node one of RAC database was connected to that switch, but the failover did not happen to the node two as this should be the case when one node goes down the other should be available for all the node one sessions/connections.
when I tried to ping/telnet the node 1, it was not happening because the switch was down, the network guyz connected the cables to other switch available. When I connected to the node 1, it was showing "Oracle is not available" message.
And when I tried the other node, it was the same case but I did not see any error in alert log file. Then my TL restarted both the nodes and then the database was available.
I am very confused that how the failover did not happen and how the database went down, PLEASE suggest something to how to identifiy what was happened. Thanks & Regards

Thanks for your reply,
after the network switch was replaced we connected to both the nodes and found that the instances are down with no reason given in the Alertlog file. We just restarted both the instances and then the database was up and the clients connected to both the instances with equal sessions on both the instances. I want to know that whether the failover can be done at the application side or it should be done on the database side i,e; in tnsnames.ora file with the required parameters? as in our scenario there is no failover configuration in the tnsnames.ora file.
Thanks & Regards

RAC-DATA FILE ACCESSING ISSUE FROM ONE NODE

Dear All,
We have a two node RAC (10.2.0.3)running on Hp Unix. From yesterday onwards, from one instance accessing data from a specific data file showing the below error, whereas accessing from other node to the same datafile is working properly.
Errors in file /oracle/product/admin/tap3plus/bdump/tap3plus4_dbw0_24950.trc:
ORA-01157: cannot identify/lock data file 75 - see DBWR trace file
ORA-01110: data file 75: '/dev/vg_rac/rraw_tap3plus_temp_live05'
ORA-27041: unable to open file
HPUX-ia64 Error: 19: No such device
Additional information: 2
Tue Jan 31 08:52:09 2012
Errors in file /oracle/product/admin/tap3plus/bdump/tap3plus4_dbw0_24950.trc:
ORA-01186: file 75 failed verification tests
ORA-01157: cannot identify/lock data file 75 - see DBWR trace file
ORA-01110: data file 75: '/dev/vg_rac/rraw_tap3plus_temp_live05'
Tue Jan 31 08:52:09 2012
File 75 not verified due to error ORA-01157
Tue Jan 31 08:52:09 2012
Thanks in Advance

user585870 wrote:
We have a two node RAC (10.2.0.3)running on Hp Unix. From yesterday onwards, from one instance accessing data from a specific data file showing the below error, whereas accessing from other node to the same datafile is working properly.That would be due to some kind of failure in the shared storage layer.
RAC needs the very same storage layer to be visible and available on each RAC node - thus this needs to be some form of shared cluster storage.
Should a piece of it fails on one node, that node would not be able to access the RAC database files on that shared storage layer - and will throw the type of errors you are seeing.
So how does this shared storage layer look like? Fibre channels (HBAs) connected to a Fibre Channel Switch and SAN - making SAN LUNs available as shared storage devices?
Typically a shared storage failure would throw errors in the kernel log. This is because the error is not an Oracle error, but a kernel error. As it is in your case. The bottom error on the error stack points to the root cause:
ORA-01157: cannot identify/lock data file 75 - see DBWR trace file
ORA-01110: data file 75: '/dev/vg_rac/rraw_tap3plus_temp_live05'
ORA-27041: unable to open file
HPUX-ia64 Error: 19: No such device
So HP-UX on that node is not seeing a specific shared storage device.

Filtering more than one node with the command SAPBEXFilterValue

Hello everybody,
i have an issue with the
Function SAPBEXsetFilterValue(intValue As String, Optional hierValue As String, Optional atCell As Range) As Integer
Filtering with cell atCell (if this parameter is missing, then the active cell is taken as the basis)
The internal filter value must be entered in the parameter intValue. Please note that this value can be displayed differently from the external value displayed in the filter cell. You can either use SAPBEXgetFilterValue or carry out the filter process once manually with the log book function switched on in order to determine the internal value for a known external value. The internal filter value is noted in the log.
Enter the parameter hierValue when dealing with a node of a certain characteristic hierarchy with the filter value.
"intValue = <blank>" means "do not filter anymore"
If no connection to a BW server exists the function starts a logon dialog.
The function produces a context error if atCell is not a filter cell.
My problem:
i would like to select inner nodes. With one node it is not a problem. I have just to use the technical name for the inner node as intValue. But I would like to select more than one node. I would like to filter 4 inner nodes with the SETBEXgetfilter command but it does not work.
i tried also to set them iteratively but when the second filtervalue is selected the first will be overwritten.
If i select more than one navigation panes to filter the nodes differently on a seperate navigation pane it also does not work because all navigation panes are connected and show the same.
Does anybody know how to filter more than one node in the same hierarchy. manually it works. So there should be a way to do that with VBA.
Thank you in Advance and kind regards,
Murat

solved

Excessive log switching after upgrading to RAC + DG

Hi everyone, I'm not sure if this should go in the RAC or the Data Guard section, seeing how I'm not sure which one is the potential culprit, but here goes:
I recently assisted in upgrading a database from Solaris 9i to HP-UX 10gR2 (10.2.0.4) using RAC and Data Guard (2 nodes). However after upgrading we noticed that there is now an increase in the redo log switches. We currently have 4 logfile groups for each thread sized at 100MB. Previously when the database was just a single instance, such a configuration was sufficient as we were only seeing 4 log switches per hour, max 8 at peak times. After the migration, this spiked up to around 40-60 log switches per hour, sometimes hitting 80.
The userbase/load of the database hasn't changed since the upgrade, we just migrated the database. Is this normal? Should I have to increase the redo logs after migrating to RAC + DG? I've implemented DG before as well as RAC, but not together so I'm not sure if this would be a factor, however I'm not totally sure if that line of thinking is correct. Any help would be much appreciated.

Previously when the database was just a single instance, such a configuration was sufficient as we were only seeing 4 log switches per hour, max 8 at peak times. After the migration, this spiked up to around 40-60 log switches per hour, sometimes hitting 80. Are all the ArchiveLogs actually 100MB each ? If Oracle has to switch logs more frequently, it doesn't necessarily mean that more Redo is being generated. Check the volum of Redo. (e.g. from v$sysstat, from StatsPack, from AWR, from V$ARCHIVED_LOG or by just listing the ArchiveLog file sizes)
Hemant K Chitale

Application deployed on one node is not getting displayed in second node

Our environment is linux x86_64 and FMW version 11g,weblogic 10.3.4.0 ,soa 11.1.1.4.
We have installed weblogic cluster :
node1: Admin server,soa_server1
node2:soa_server2
when we deploy any soa application in one node it is not getting published in second node.We have taken oracle support also still problem is not solved.
They told us to configure coherence ,we have taken owc from metalink .
very urgent.
Any one can help me.

You have a cluster consisting of soa_server1 and soa_server2 or are these stand-alone WebLogic instances?
Is soa-infra active on soa_server2?
Can you check if soa-infra can be reached on both the server instances (http://hostname:port/soa-infra/)
When soa_infra cannot be reached on soa_server2 can you check the logging to see what errors
are occuring.
Some examples that set-up a clustered envionment can be found here: http://middlewaremagic.com/weblogic/?p=6872
and here: http://middlewaremagic.com/weblogic/?p=6637

Is there a way to identify manual log switches?

Hi!
A while ago I upgraded a 10g database to 11.2.0.2 64 Bit Windows.
During the Upgrade we realized that redo logs were configured really small (~10MB) what resulted in a lot of log switches (a few hundred per day). So we adjusted redo log size to 100MB and set archive_lag_target to 1800.
The amount of log switches went down a little but less far than we expected it. After further analysing the situation we recognized that Oracle is switching logs far before reaching the 100MB log size (and also far before reaching 1800s). All the archived logs have a size of about 15MB. I know that 11g invented something like "preemptive log switching" that switches logs round about 20% before reaching the maximum value (if I remember it correctly..). But switching already at 15% of the maximum size seems strange to me...
I couldn't find any helpful stuff on Google or Metalink about that topic but today I had a different idea: what if it's the application software that's doing manual log switches?
(I have no idea why it should do that but I can remember that the application user does require the sysdba privilege - don't ask me why, I didn't write it, I won't defend it...)
So I checked the alert log but unfortunately I had to realize that there is no difference between an automatic switch and a manual one (only alter system archive log... does get an extra line).
So my questions are:
1) Does anybody know a way of distinguishing between an automatic log switch and a manual one? Is there a table or another logfile where this information is recorded?
2) Has anybody experienced a similar situation where Oracle is switching the logs way before reaching the maximum size?
Best regards,
Marcus

lebigmac wrote:
1) Does anybody know a way of distinguishing between an automatic log switch and a manual one? Is there a table or another logfile where this information is recorded?
Off the top of my head - I think the only way to do a manual log switch is to issue "alter system switch log file", and I think that any "alter system" command is written to the alter log in you version of Oracle. (I really ought to check both statements before posting this, but I've been up since 2:30 am).
2) Has anybody experienced a similar situation where Oracle is switching the logs way before reaching the maximum size?
It's very common with recent versions of Oracle when private redo threads come into play; but your example seems a little exaggerated. The log file switch has to start when there is enough space left in the log file for all the public and all (or maybe it's the previously used - i'll have to check my book) private redo threads. You could check x$kcrfstrand to see what this sizes look like: http://jonathanlewis.wordpress.com/?s=private+thread
Regards
Jonathan Lewis

Found the errors in CSSD logs of RAC node

Found the below error in CSSD logs in One of RAC nodes from 5:15 to 5:18 PM, after this the error got disappeared. Could anyone please have an idea what could be the reason of this error.
Also, at that time we didn't find any errors in the alert log.
[    CSSD]2009-07-19 17:15:51.048 [3600] >TRACE: Authorization failed (112bd2a70), timed out, start 17:13:51.041, duration 120009
[    CSSD]2009-07-19 17:15:51.048 [3600] >TRACE: Authorization prepare time: 2 ms
[    CSSD]2009-07-19 17:15:51.233 [3086] >TRACE: clssgmClientConnectMsg: Connect from con(112b67930) proc(112b680b0) pid(1049540) proto(10:2:1:1)
[    CSSD]2009-07-19 17:15:51.268 [3600] >TRACE: Authorization failed (112bd4a10), timed out, start 17:13:51.268, duration 120003
[    CSSD]2009-07-19 17:15:51.268 [3600] >TRACE: Authorization prepare time: 3 ms
[    CSSD]2009-07-19 17:15:52.544 [3086] >TRACE: clssgmClientConnectMsg: Connect from con(112b67930) proc(112b680b0) pid(786918) proto(10:2:1:1)
[    CSSD]2009-07-19 17:15:53.297 [3600] >TRACE: Authorization failed (112c38af0), timed out, start 17:13:53.290, duration 120009
[    CSSD]2009-07-19 17:15:53.297 [3600] >TRACE: Authorization prepare time: 3 ms
[    CSSD]2009-07-19 17:15:53.317 [3600] >TRACE: Authorization failed (112d356f0), timed out, start 17:13:53.320, duration 120000
[    CSSD]2009-07-19 17:15:53.317 [3600] >TRACE: Authorization prepare time: 2 ms
[    CSSD]2009-07-19 17:16:02.342 [3086] >TRACE: clssgmClientConnectMsg: Connect from con(112b932b0) proc(112b67d10) pid(1336252) proto(10:2:1:1)
[    CSSD]2009-07-19 17:16:02.977 [3600] >TRACE: Authorization failed (112d04f70), timed out, start 17:14:02.978, duration 120001
[    CSSD]2009-07-19 17:16:02.977 [3600] >TRACE: Authorization prepare time: 2 ms
[    CSSD]2009-07-19 17:16:03.007 [3600] >TRACE: Authorization failed (112d38210), timed out, start 17:14:03.006, duration 120002
[    CSSD]2009-07-19 17:16:03.007 [3600] >TRACE: Authorization prepare time: 2 ms
[    CSSD]2009-07-19 17:16:10.447 [3600] >TRACE: Authorization failed (112bd7e30), timed out, start 17:14:10.441, duration 120007
[    CSSD]2009-07-19 17:16:10.447 [3600] >TRACE: Authorization prepare time: 2 ms
[    CSSD]2009-07-19 17:16:10.847 [3600] >TRACE: Authorization failed (112d3ee70), timed out, start 17:14:10.840, duration 120008
[    CSSD]2009-07-19 17:16:10.847 [3600] >TRACE: Authorization prepare time: 2 ms
Thanks,
Mahi

Check the metalink note:
6996694-OCSSD.BIN CONSUMING 100% CPU AND ASM/DB HANGING

One node is failing

One node is periodically are failing . When users are connecting , they are getting the error :
ERROR: ORACLE connection error: ORA-01034: ORACLE not availableORA-27101: shared memory realm does not existLinux-x86_64 Error:
2: No such file or directory.
And then the command : srvctl status database -d te , is reporting , that one of instances are running , but other are not .
Please suggest , what log files to check .

user10890074 wrote:
One node is periodically are failing . When users are connecting , they are getting the error :
ERROR: ORACLE connection error: ORA-01034: ORACLE not availableORA-27101: shared memory realm does not existLinux-x86_64 Error:
2: No such file or directory.
And then the command : srvctl status database -d te , is reporting , that one of instances are running , but other are not .
Please suggest , what log files to check .How about you problem?
It seemed your node hung.
1. you should check alert log file.
2. you should check log file in CRS_HOME/log/<nodename)/ PATH

One node RAC pause/hang/block on other node shutdown

Hi,
We have a Java application running on Linux servers connecting to a 10.2.0.1 RAC cluster, also Linux. When the application starts it opens up a pool of connections to the databsae, and these are used throughout the life time of the application. One server connects to one RAC node.
AppA - DBA
AppB - DBB
When we shutdown one node, the application connecting to that node stops, which is what we would expect in this configuration.
What is strange is that the other application blocks for 63 seconds and then continues. So it is like the database is blocking, or the database connections are blocking.
We are not using TAF, FAN, FCN, LB, VIPs or any special features, just simple lightweight JDBC from one server to one database. In fact I do not thing we are unwittingly using any of these features, we have them switched off.
john

user1788323 wrote:
What is strange is that the other application blocks for 63 seconds and then continues. So it is like the database is blocking, or the database connections are blocking.How have you determined/diagnosed the 63s blocking? (more details in this regard may shed some light on the problem)
Assuming that the block is server side, then two basic reasons comes to mind.
Networking issue - the CRS on the surviving node has to perform certain functions, like switching the VIP of the node that left the cluster to a surviving cluster node. The listener may need to re-register services. A local firewall may need to be dynamically reconfigured for supporting the new failed-over VIP. Etc.
Thus these could result in some kind of delay or issue in the network layer that you are seeing from the client side.
Infrastructure issue. If the actual client request via JDBC reaches the server process, and it is slow in responding, then that is not a network issue - instead some underlying service or s/w layer that the server process needs to use to perform the client request is busy for those 63s.
This could be related to the Interconnect, the shared I/O storage layer or something along those lines. For example, how does the Interconnect and/or SAN switch re-act when a server node is powered down or rebooted?
There's not really sufficient information to make anything but a guesses.. You will need to isolate the problem with further testing.
I have seen similar problems with 10.1.0.3 CRS and RAC when a node is evicted from the cluster. In this case the "hung" period was in excess of 15 minutes and only for new connections (Listener unable to hand off to dedicated servers or dispatchers). Existing connections worked fine however and were unaware of any problems. But part of the issue in this case was a poor (outdated) driver layer - and also the last time we used proprietary binary drivers (kernel modules) from 3rd party vendors that results in a tainted (and very fixed and rigid) Linux kernel. Today we're sticking with an OpenSource driver layer only for Linux.

When one node reboot other node in RAC

Hi Friends,
I faced one situation where one node of RAC cluster had been rebooted by other node. This happen due to network interconnect link fluctuation.
Sep 13 16:23:48 kkvs1a su: [ID 810491 auth.crit] 'su admin' failed for wipro1 on /dev/pts/3
Sep 14 00:22:17 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe3: link down
Sep 14 00:22:21 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe3: link up, , full duplex
Sep 14 00:22:31 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe1: link down
Sep 14 00:22:31 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe3: link down
/opt/oracle/product/10.2.0/crs/log/node1/alertkk1a.log
==============================================
2013-09-14 00:22:05.180
[cssd(12561)]CRS-1612:node kk1b (2) at 50% heartbeat fatal, eviction in 14.251 seconds
2013-09-14 00:22:12.180
[cssd(12561)]CRS-1611:node kk1b (2) at 75% heartbeat fatal, eviction in 7.251 seconds
2013-09-14 00:22:13.180
[cssd(12561)]CRS-1611:node kk1b (2) at 75% heartbeat fatal, eviction in 6.251 seconds
2013-09-14 00:22:17.179
[cssd(12561)]CRS-1610:node kk1b (2) at 90% heartbeat fatal, eviction in 2.251 seconds
2013-09-14 00:22:18.180
[cssd(12561)]CRS-1610:node kkvs1b (2) at 90% heartbeat fatal, eviction in 1.251 seconds
This clearly shows CSSD of node kkvs1a has given node eviction message to kkvs1b node.
I got following messages on the instance which got rebooted:
ASM alert log:
Sat Sep 14 00:22:25 IST 2013
Error: KGXGN aborts the instance (6)
Sat Sep 14 00:22:25 IST 2013
Errors in file /opt/oracle/admin/+ASM/bdump/+asm2_lmon_8527.trc:
ORA-29702: error occurred in Cluster Group Service operation
LMON: terminating instance due to error 29702
A network fluctuation shouldn't give reboot like this. Then why oracle design like this way? Is this a bug? My oracle version is: 10.2.0.5.0
Could you tell me the other possible situations when 1 RC instance reboots other RAC instacne.

What you are describing is the expected behaviour: if your interconnect fails, you will have a node eviction. Releases < 11.2.0.2 evict a node by reboot, which can fix the problem: the NIC may come up correctly when the machine re-starts. Releases >= 11.2.0.2 can often evict without a re-boot. But either way, if your interconnect goes down, a node must be evicted to prevent uncoordinated disc writes.
If you are interested, you can find some discussion and demos of this in a series of webcasts I've recorded,
Free Oracle Database Tutorials for Administration and Developers
If you really don't like this behaviour and the problems are transient, you can try 'raising the CSS MISSCOUNT parameter.
John Watson
Oracle Certified Master DBA

Wrong Listener setting in 11.2.0.2 Grid with 11.2.0.2 ONE NODE(win 2008 R2)

Hello,
the listener on the second node doesn't use its endpoint-Entries and doesn't register the database or shows the running ASM-Instanz. No connection is possible on that node.
In Log of Listeners always:
TNS-12502: TNS:listener received no CONNECT_DATA from client
I installed RAC one Node on 2 Servers, first installed and configured grid for both nodes with SCAN. After it I installed the rdbms and created a ONE NODE Database. The grid infrastructure is running nicely and even the swich of the instanz/database to the second node is working.
BUT: on the second node the listener doesn't know the instance. Nor does ist know its asm-Instance. Registration (Alter system register) even doesnt't work.
In 11.2.0.2 the lsiteners are starteet from grid-home before database creation.
On the 1. node everthing is fine, as long as I don't switchover/failover.
On the second server there has been a second listener from RDBMS_HOME created by ? . I stopped it. Th Listener from GRID_HOME ist configured the same way as node 1, but doesn't uses its endpoint-Entries and doesn't register the database or shows the running ASM-Instanz.
listener.ora:
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))) # line added by Agent
LISTENER_SCAN3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN3)))) # line added by Agent
LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN2)))) # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))) # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN3=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent
lsnrctl status (if: lsnrctl services even no services)
Instanz +asm2 onenode_2 are running and I can connect with / as sysdba
LSNRCTL for 64-bit Windows: Version 11.2.0.2.0 - Production on 25-JAN-2011 15:52:05
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.2.0 - Production
Start Date 25-JAN-2011 15:49:46
Uptime 0 days 0 hr. 2 min. 22 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\11.2.0\grid\network\admin\listener.ora
Listener Log File C:\11.2.0\grid\log\diag\tnslsnr\VSLWMU022\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\LISTENERipc)))
The listener supports no services
The command completed successfully
I think, I have problems with the listener.ora and the environment settings, tha lsnrctl uses.
When i change listener settings, I get the message:
Failed to open service <OracleOraDb11g_home1TNSListenerLISTENER_DG> - this is the wron HOME!
I don't find an entry in the registry wher I can change listener-Settings.
Whe I try to change the settings (add entries like SID_LIST_LISTENER for a dataguard Konfiguration)on node 1, it behave like node 2: no more services/sid and endpoints.

Hello folks,
I found the bugs (2 independent annotations) and settings we need!
1. Aus: http://download.oracle.com/docs/cd/E11882_01/relnotes.112/e16777.pdf 5.3.9 (write name and public IP in etc\hosts)
2. http://download.oracle.com/docs/cd/E11882_01/relnotes.112/e16777/toc.htm#CJAHIGJE
I changed the wrong entry in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0 and rebooted the server.
Suddenly the listener knows its IPs and its servces.
Take care about yout local_listener setting in the instance: show parameter local_listener. This IP/name must be reachable. Sometimes I have had instance_2 running on node_1 with the vip_ip of 2 => this doesn not work.
alter system set local_listener='(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))' scope=both sid='*';
I am still not sure, if this values changes to (ADDRESS=(PROTOCOL=TCP)(HOST=+host+-vip)(PORT=1521)).
Check the IPS, that the listener ist running on: lsrnctl status
..Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\LISTENERipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.20.121)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.20.124)(PORT=1521)))...
Hopefully this will help you (and will be found in Windows-Documentation soon).
By
Marion

Dataguard- scheduling manual log switch to have minimal lag

Hi,
I need some suggestion..
Recentry I had configured a physical standby for my 10g production database in maximum performance mode.
Now , to reduce the lag between the primary and standby , I put one cron job which will do a manual log switch(alter system switch logfile) in every 30 minutes.
and it is doing the job..!
Does this have any impact on my databases...?
Looking forward for your invaluable responce...
Regards
Noushad
DBA

Maybe you should let Oracle do it's job, configure this parameter which signifies that no buffer will remain dirty (in the cache) for more than 1800 (or whatever you want) seconds:
LOG_CHECKPOINT_TIMEOUT = 1800:p

Redo logs switches too frequent after migrating the db to different server

Dear Experts,
A couple of days back, we migrated our database (belonging to EBusiness Suite) to a different server, to get good performance benefit. The database is 10.2.0.4 and it was migrated from AIX 5.3 to Linux x86 64.
Users are happy with the performance, but I am getting below errors in the alert logs
a) Thread 1 cannot allocate new log, sequence 498
b) Private strand flush not complete
c) ORACLE Instance PROD - Can not allocate log, archival requiredOracle support is saying the issue is coming because of too frequent log switches. I am wondering how the log switches has become frequent in the new server. In the old server it was about 10 mins for every switch, now it is as frequent as 1 minute?
Any idea, what could be the reason behind this? Do you agree this issue is coming because frequent log switches?
Thanks
ARS

Kanchana Devasurendra wrote:
Hi ARS,
Please check the following item in your new database.
1. log_archive_max_processes Most properbly value set for this parameter is low ( may be it's set to 1.) Please increase up ( 4)I am curious to know what makes you think 4 is the right magic number for log_archive_max_processes - after all, he's only got one archive destination.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
A general reminder about "Forum Etiquette / Reward Points": http://forums.oracle.com/forums/ann.jspa?annID=718
If you never mark your questions as answered people will eventually decide that it's not worth trying to answer you because they will never know whether or not their answer has been of any use, or whether you even bothered to read it.
It is also important to mark answers that you thought helpful - again it lets other people know that you appreciate their help, but it also acts as a pointer for other people when they are researching the same question, moreover it means that when you mark a bad or wrong answer as helpful someone may be prompted to tell you (and the rest of the forum) what's so bad or wrong about the answer you found helpful.

Continiously log switching, one node unavailable

Similar Messages

Maybe you are looking for