
===============================================================================
                    Oracle Server Management Readme File

                             Release 11.1.0.0.0
===============================================================================



1. Changes from Release 10.2.0.1.0
2. References
3. Known Problems/limitations

=================================
1. Changes from Release 10.2.0.1.0
=================================

SRVCTL now supports adding and removing listener configuration as well as
starting and stopping listeners.  See 'srvctl add/remove/modify listener -h"

SRVCTL can now modify the Oracle home for ASM configuration.  
See the -o flag for "srvctl modify asm"

=============
2. References
=============
For detailed information on setting up the cluster database for management by 
EM, refer to:

    Oracle Clusterware and Oracle Real Application Clusters Installation and 
      Configuration Guide 11g Release 1
    Oracle Clusterware and Oracle Real Application Clusters Administration 
      and Deployment Guide 11g Release 1

=============================
3. Known Problems/limitations
=============================

Do not change a hostname after CRS installation.   This includes
adding or deleting a domain qualification. Instead remove and re-add
the affected node using MetaLink note 276434.1
 
Bug 4675276: REMOVING SERVICE TROUGH SRVCTL DOESN'T REMOVE ALL RELATED OBJECTS. PRKP-1029
DESCRIPTION: When creating a service with the same instance as both perferred and 
available for the service, as in 
srvctl add service -d mydb -s myservice -r inst1 -a inst1
the removal of this service may leave some CRS resources behind.  
These resources can interfere with subsequent re-creation of the same service.
WORKAROUND: Don't specify the same instance as both a preferred instance and an 
available instance.

Bug 3377903: INST OFFLINE AFTER SHUTDOWN AND STARTUP FROM SQLPLUS 
DESCRIPTION: When shutting down an instance and immediately starting it 
again using SQL*Plus, sometimes the CRS resource for the instance does not 
get started, because it is still busy stopping. In this case, 
srvctl status instance -d <name> -i <sid>
will incorrectly report the instance not to be running.
WORKAROUND: Start the instance's CRS resource with 
srvctl start instance -d <name> -i <sid>

Bug 4417761: ONS ENVIRONMENT NEEDS TO BE SET TO CRS_HOME LOCATION
DESCRIPTION:  The TNS listener when started using lsnrctl  instead of by
srvctl, cannot communicate with ONS.  This causes the TNS listener to fail
to drop service handlers for instances on nodes that have failed, which it
usually does by receiving an ONS event notification.
WORKAROUND: When starting the TNS listener with lsnrctl, first set the
environment variable ORACLE_CONFIG_HOME to CRS home.  Alternatively, use
the "srvctl start listener" command to start the listener.

Bug 4241481: CRSD PASSES NULL AS TZ WHEN STARTING THE DATABASE 
DESCRIPTION: When the OS local timezone is different from that specified
by the Oracle user's TZ environment variable, any database instances
started by CRS will use the OS local timezone.  This is because CRS will
start the instance with an empty TZ, rather than the Oracle user's TZ.
WORKAROUND: There are three possible workarounds
1) modify /etc/localtime so that it provides the default timezone that you
want. This file controls the behavior in the case that TZ is undefined.
2) srvctl setenv database -d <name> -T TZ=<val> 
This will result in the given value of TZ always being used to start instances
of the given database.
3) Use sqlplus instead of srvctl to start the database instances

Cluster Installation
--------------------

1. Pre-Installation Setup
-------------------------

Before invoking the Oracle Universal Installer to start Oracle10g Enterprise
Edition installation for CRS or RAC, perform the following steps.

a. Set up the oracle user equivalence on all nodes of the cluster, including
   the local node.

b. If the file /var/opt/oracle/srvConfig.loc exists, ensure that the user
   performing the installation has permissions to read it.  If not, change
   the permissions with
   % chmod 644 /var/opt/oracle/srvConfig.loc
   The group of this file should be the OSDBA group.

c. Stop any 9.2 or earlier GSDs, if present

