From: Harald Wakonig (Harald.Wakoning@oskarmobil.cz)
Date: Tue Jan 07 2003 - 13:19:21 EST
Operating System and Version: Solaris8, SunCluster 3.0, Oracle RDBMS Version:
8.1.7
We are NOT running OPS (Oracle Parallel Server, = RAC - Real Application
Cluster), just a normal instance which should fail over to second
(standby-node) if really required using Sun Cluster HA for Oracle Agent.
The Sun-HA Agent for Oracle runs on second node and connects every minute to
the database on the other node. If it cannot connect it decides to fail over.
But in Default-configuration the Instance also fails over if just the
Archivelog-Destination is full (because no new connects are allowed...). Of
course the database cannot start on other node as the archivelog destination
is still full.
In this case the it's better if the database just stays "frozen" and (most)
applications will continue after archive log destination is free again...
(after a failover we need a little bit more cleanup....)
The Sun Documentation "Sun Cluster .30 Agents - Data Services installation and
Configuration Guide" contains following:
==============- start quote Sun Docu ====================
If the database transaction fails, the main process checks the internal action
table for an action to be performed and performs the predetermined action. If
the action executes an external program, it is executed as a separate process
in the background. Possible actions include the following.
switchover
stopping the server
restarting the server
stopping the resource group
restarting the resource group
The probe uses the time-out value that is set in the resource property
Probe_timeout to determine how much time to spend to successfully probe
Oracle.
The server fault monitor also scans Oracle's alert_log_file and takes action
based on any errors that the fault monitor finds.
The server fault monitor is started through pmfadm to make the monitor highly
available. If the monitor is killed for any reason, the Process Monitor
Facility (PMF) automatically restarts the monitor
============== quote end ============
Question:1) Where is this "internal action table" ?
Question 2) Where is the documentation of this action table?
===> How to configure Sun HA Agent for Oracle that Database does NOT failover
if Archivelog-Destination is full (ora 257, 270)
Note: On our old SC2.x Cluster I found a plain ASCII configuration file - that
might be this "internal action table" . But I did not find it on our new
SC3.0
/etc/opt/SUNWscor/haoracle_config_V1
====================================
which allowed for each Oracle-Error a defined action (none, restart, stop,
takeover).
Unfortunately I cannot find that file on our new Solaris8 / SunCluster 3.0
installation.
Thanks for any hint...
Harald
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:32 EDT