  ù 	 ZISO8859-1             0  0  ˜    É  $  Ý            /    <    M 	   h 
   y        ®  $  Â    ç            2    H    e  '  z  '  ¢    Ê dY  ê e œ  	D f¸  	á g ó  š h@  Ž i  Ï j w  Õ k Ì  M lB   mÓ  ] n œ  1 o ý  Î p  Ì q s  ä rý  X s p  V t î  Ç u,  ¶ wÎ  ã xÞ  ² yì  !‘ zz  #~ {d  $ù |›  '^ }  )ú ~¦  , 
   &  .¼    .ã  !  .ù  !  /    /=    /[    >  /y  '  /¸  (  /à  3  0	    0=  <  0]  U  0š  R  0ð 	    1C 
 H  1d  6  1­  K  1ä  @  20    2q  {  2  U  3  #  3b  Q  3†    d  3Ø  K  4=  h  4‰  U  4ò  V  5H  i  5Ÿ  S  6	   6] 	 …  7o 
 ‚  7õ  …  8x    8þ  ¤  9Ž  Ù  :3  t  ;  /  ;‚  +  ;²  '  ;Þ  0  <  ™  <7  Q  <Ñ  P  =#  L  =t  —  =Á  Á  >Y d^  ? ( 
  I  @z    @Ä  #  @Ü  *  A   J  A+  $  Av  *  A›  F  AÆ 	   B 
   B* 2   .  BD  .  Bs  .  B¢  )  BÑ  ,  Bû  %  C(  ,  CN  '  C{ 	 <  C£ 
 %  Cà  (  D  o  D/  7  DŸ  ;  D×  2  E  '  EF <   8  En  K  E§  +  Eó  :  F P     FZ    Fi Z 	  G  Fx  8  FÀ  H  Fù  "  GB    Ge  /  Gƒ  @  G³  -  Gô 	 2  H"Select Specific Configuration You Wish To Create Select CFC Instance Add an Oracle CFC Application Server Oracle AS CFC Instance Name Application Name Primary Node Takeover Node(s) Oracle Metadata Repository Service IP Label Shared Volume Group(s) Oracle OID and SSO Components Select AFC Instance Add an Oracle AFC Application Server Oracle AS AFC Instance Name Participating Nodes Concurrent Volume Group(s) Select RDBMS Instance Add an Oracle RDBMS Instance Oracle Instance Name Modify an Oracle CFC Application Server Modify an Oracle AFC Application Server Modify an Oracle RDBMS Instance Add an Oracle Application Server Cold Failover Cluster
Instance to the HACMP cluster configuration.  HACMP will discover
configured SSO OID and MR (Metadata Repository) components for
Oracle 10g AS.

HACMP will construct one HACMP resource group for each of the
Oracle AS components, SSO, OID and MR.  Within the OID, and SSO
components will be HACMP application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)

Note: Release v10g r1 of Oracle AS includes a version of Oracle
v9.0.4, this version of the DB is detected and supported by the
Oracle smart assist tool.
 Oracle Application Server Cold Failover Cluster (CFC) Name
The is the selected Oracle Application Server Name as designated
in the OPMN configuration file.
 Application Name
An HACMP cluster wide unique name.  The application name is a
container for the HACMP resource groups, application servers, and
other cluster components generated to support the Oracle Application
Server or RDBMS Instance.

The application name must conform to the same rules for naming HACMP
resource groups.  The name can be no longer than 32 characters, and
must only contain alphanumerics and underline (_) characters.
 Primary Node Name
The primary node must be a node already defined to the HACMP cluster.
If the desired node is not already part of the HACMP cluster
configuration the node must be added to the configuration prior to
entering this SMIT dialog.
 Takeover Node(s)
The takeover node(s) must be an already existing HACMP cluster node.
Takeover nodes will participate in the resource groups generated to
support the Oracle application server components, and in the event of
a failure will takeover the selected SSO, OID, or MR components
designated in this SMIT dialog.
 Oracle Metadata Repository (MR Database)
A picklist is available to choose the MR database from the list of
existing Oracle SIDs available in the OFA directory structure
pointed to by the environment variable ORACLE_HOME.

If the ORACLE_HOME directory is not set, or if the ORACLE_HOME
environment variable is not set to a path where the directory
structure follows OFA guidelines, then no databases will be
available to select.

The MR database is an optional component, and therefore does not need
to be specified.
 Service IP Label
Select a service IP label to use for your Application Server, and/or
MR database to communicate over.
 Shared Volume Groups
The Oracle Application Server Smart Assist will auto-discover the volume groups
associated with the selected AS.  Additional volume groups can be
manually entered in this SMIT field.
 Oracle OID and SSO Components
The Oracle Internet Directory (OID) and Single Sign-On components
will be auto-discovered by the Oracle Application Server Smart Assist.
By default all SSO/OID components will be selected in the dialog.
Removing components from this list will remove the component from
HACMP control.

HACMP will generate two separate resource groups, one to contain the
SSO components, and another to support the OID components.
Within each resource group will be individual HACMP application
servers and monitors to control and monitor the OID or SSO
components.
 Add an Oracle Application Server Active Failover Cluster (AFC)
instance to the HACMP cluster configuration.  HACMP will discover
configured SSO OID components configured in AFC mode for Oracle 10g AS.

HACMP will construct one HACMP 'Online on All Nodes' resource group for
each of the Oracle AS components, SSO, and OID.  Within the OID, and SSO
components will be HACMP application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)
 Oracle Application Server Cold Failover Cluster (CFC) Name
The is the selected Oracle Application Server Name as designated
in the OPMN configuration file.
 Participating Nodes
Each node specified in the participating nodes list will start a copy of
the Oracle Application Server OID and/or SSO components defined in this
SMIT dialog.
The participating node names must already be defined to the HACMP
cluster.
 Concurrent Volume Group(s)
AFC Application Servers are active/active, therefore any shared
storage must be via enhanced concurrent volume groups. Alternatively
separate storage subsystems on each system must be utilized.

The HACMP Oracle AS smart assist will auto-discover any pre-configured
concurrent volume groups associated with the selected SSO/OID components.
Additional concurrent volume groups not discovered by the smart assist
can be manually entered within this field, or within the Extended
Resource configuration dialog.
 Select RDBMS Instance
Select the RDBMS Instance to make highly available in a Cold Failover
Cluster configuration.
 Add an Oracle RDBMS Instance
Add an Oracle application database to the HACMP cluster configuration.
RDBMS instances will be added as Cold Failover Cluster (CFC) /
hot-standby configurations.

The HACMP Smart Assist for Oracle will configure a hot-standby
resource group containing an application server to bring up/down the
selected Oracle DB.  In addition, an HACMP application monitor will be
added to monitor the core Oracle processes, required database
listeners, and connectivity to the Oracle database.
 Oracle Instance Name
Oracle SID as discovered in the ora configuration file, selected in
the prior SMIT screen.
 Primary Node
The primary node must be a node already defined to the HACMP cluster.
If the desired node is not already part of the HACMP cluster
configuration the node must be added to the configuration prior to
entering this SMIT dialog.
 Takeover Node(s)
The takeover node(s) must be an already existing HACMP cluster node.
Takeover nodes will participate in the resource groups generated to
support the Oracle RDBMS instance, and in the event of
a failure will takeover the selected Oracle RDBMS instance designated
in this SMIT dialog.
 Service IP Label
In most cases the service IP label is the listener IP label used by
the selected Oracle RDBMS database instance.
The Oracle Application Server Smart Assist will by default choose the first listener IP
address discovered in the Oracle DB configuration.  Alternatively, any
service IP label already defined to HACMP can be choosen, or a new 
service IP label will be created if the label does not already exist
in the HACMP cluster configuration.
 Shared Volume Group(s)
The default list of volume groups auto-discovered by the Oracle Application Server Smart
Assist is the list of volume groups associated with the Oracle RDBMS
data, control and log files.  Additional volume groups can be
specified.

Each volume group specified must be shared between the primary and
takeover nodes specified in the dialog.  The volume groups specified
must already exist, and at least one of the nodes must have the volume
group imported.
 Modify an Oracle RDBMS Instance
Modify an existing HACMP defined Oracle application database.
The existing HACMP components will be modified for the selected
RDBMS instance.

The HACMP Smart Assist for Oracle will configure a hot-standby
resource group containing an application server to bring up/down the
selected Oracle DB.  In addition, an HACMP application monitor will
be added to monitor the core Oracle processes, required database
listeners, and connectivity to the Oracle database.
 Modify an Oracle Application Server Active Failover Cluster (AFC)
instance in the HACMP cluster configuration. 

HACMP will construct one HACMP 'Online on All Nodes' resource group for
each of the Oracle AS components, SSO, and OID.  Within the OID, and SSO
components will be HACMP application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)
 Modify an Oracle Application Server Cold Failover Cluster
Instance defined to the HACMP cluster configuration.  HACMP will
discover configured SSO OID and MR (Metadata Repository) components
for Oracle 10g AS.

HACMP will construct one HACMP resource group for each of the
Oracle AS components, SSO, OID and MR.  Within the OID, and SSO
components will be HACMP application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)

Note: Release v10g r1 of Oracle AS includes a version of Oracle
v9.0.4, this version of the DB is detected and supported by the
Oracle smart assist tool.
 Add an Oracle Application Server Cold Failover Cluster
Instance to the PowerHA SystemMirror cluster configuration.  PowerHA SystemMirror will discover
configured SSO OID and MR (Metadata Repository) components for
Oracle AS.

PowerHA SystemMirror will construct one PowerHA SystemMirror resource group for each of the
Oracle AS components, SSO, OID and MR.  Within the OID, and SSO
components will be PowerHA SystemMirror application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)

Note: Release r1 of Oracle AS includes a version of Oracle
v9.0.4, this version of the DB is detected and supported by the
Oracle smart assist tool.
 Add an Oracle Application Server Active Failover Cluster (AFC)
instance to the PowerHA SystemMirror cluster configuration.  PowerHA SystemMirror will discover
configured SSO OID components configured in AFC mode for Oracle AS.

PowerHA SystemMirror will construct one PowerHA SystemMirror 'Online on All Nodes' resource group for
each of the Oracle AS components, SSO, and OID.  Within the OID, and SSO
components will be PowerHA SystemMirror application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)
 Modify an Oracle Application Server Cold Failover Cluster
Instance defined to the PowerHA SystemMirror cluster configuration.  PowerHA SystemMirror will
discover configured SSO OID and MR (Metadata Repository) components
for Oracle AS.

PowerHA SystemMirror will construct one PowerHA SystemMirror resource group for each of the
Oracle AS components, SSO, OID and MR.  Within the OID, and SSO
components will be PowerHA SystemMirror application servers that start and stop
the various daemons (HTTP_Server, OC4J, dcm-server...)

Note: Release r1 of Oracle AS includes a version of Oracle
v9.0.4, this version of the DB is detected and supported by the
Oracle smart assist tool.
 Oracle Application Server Smart Assist Oracle RDBMS Database Oracle Application Server AFC 10g Oracle Application Server CFC 10g Oracle Application Server CFC Oracle Application Server AFC Creating HACMP resource group: %s to support
MR Database: %s.
 	Creating HACMP application server: %s
 	Creating HACMP application monitor: %s
 Adding MR Database: %s to the HACMP configuration.
 	Creating service IP label: %s
 	Adding Oracle AS component: %s to HACMP resource group
	%s
 Creating HACMP resource group: %s to support
Oracle Application Server component: %s
 	Adding HACMP application monitor: %s
	for Oracle Application Server component %s
 	Oracle MR Database version: %s
 	Adding Oracle MR Database Listener
	[ IP Label: %s, Listener Name: %s]
 Adding RDBMS database: %s to the HACMP configuration.
 	Adding Oracle RDBMS Database Listener
	[ IP Label: %s, Listener Name: %s]
 Creating HACMP resource group: %s to support
RDBMS Database: %s
 #
# Oracle CORE Version: %s
#
 #
# WARNING: Database is not running. Volume groups where
# logs, control files, and tablespaces, reside will be missing
#
 Modifying Oracle Application Server: %s, removing existing
HACMP cluster components.
 	Oracle RDBMS Database version: %s
 Modifying Oracle RDBMS Database: %s, removing existing
HACMP cluster components.
 ERROR: The HACMP resource group: %s already exists.
Please choose another name for the application.
 Unexpected error encountered while attempting to create
resource group: %s
 ERROR: The HACMP application server: %s already exists.
Please choose another name for the application.
 Unexpected error encountered while attempting to create
HACMP application server: %s
 Unexpected error encountered while attempting to create
HACMP application monitor: %s
 ERROR: The HACMP application monitor: %s already exists.
Please choose another name for the application.
 Unexpected error encountered while attempting to create
HACMP service IP label: %s
 ERROR: Unable to create the service IP label: %s
There are no available HACMP networks defined.  Please either defined one
or more HACMP networks.  Or, alternatively define the service IP label
within the HACMP configuration prior to re-running the Oracle smart
assistant.
 Unexpected error encountered while attempting to associate
the HACMP resource group: %s with the Oracle smart assist application
%s.
 ERROR: An application with the name: %s is already
defined to HACMP.  Please choose another Oracle smart assist application
name.
 Unexpected error encountered while attempting to add 
Oracle Application Server component resources to the HACMP resource
group: %s.
 Unexpected error encountered while attempting to add
Oracle Application Server metadata to the HACMP configuration for
application server: %s.
 ERROR: Unable to locate the OPMN configuration file
%s on the local system.
The ORACLE_HOME must follow the Oracle Flexible Architecture (OFA) directory
hierarchy.
 ERROR: The environment variable ORACLE_HOME must be set.
Please set the ORACLE_HOME to an appropriate Oracle Application Server, or
Oracle RDBMS database, then re-run the HACMP Oracle Application Server Smart Assist.
 Unexpected error encountered while attempting to add
HACMP application monitor: %s for
HACMP application server: %s
 ERROR: %s missing argument -a application_name
 ERROR: %s missing argument -c component id
 ERROR: %s missing argument -i instance
 ERROR: %s missing argument -d database instance
 ERROR: The Service IP label: %s is not resolvable on the
local system.  Please check to ensure the IP label is resolvable via either
DNS, or /etc/hosts.
 Unexpected error encountered while attempting to remove
application monitor: %s.
 Unexpected error encountered while attempting to remove
application server: %s.
 Unexpected error encountered while attempting to remove
resource group: %s.
 Unexpected error encountered while attempting to remove
application: %s Oracle smart assist component references from the HACMP
cluster configuration.
 ERROR: The ORACLE_HOME directory used for Oracle application
Server: %s does not exist on the local node: %s
Please perform modifications on a node where the Oracle application server
resides.
 Please contact HACMP support to resolve the error reported above.
A copy of the Oracle Application Server Smart Assistant log file: /var/hacmp/log/oraappsa.log
will be required to diagnose this error.  A copy of this log file has been
saved to the location: %s
.
This log file will be captured as part of a snap -e, or can be transmitted
separately.
 Requested STOP of AS instance: %s component: %s
in HACMP application %s.
 Setting ORACLE_HOME=%s
 Failed to STOP Oracle component %s
 Successfully STOPPED Oracle component: %s
 Requested START of AS instance: %s component: %s
in HACMP application %s.
 Failed to START Oracle component %s
 Successfully STARTED Oracle component: %s
 Monitoring AS instance: %s and component: %s
in HACMP application: %s
 Component %s is NOT RUNNING
 Component %s is running.
 DB Background Processes STARTED successfully.
 DB Background Processes could NOT be STARTED.
 DB Background Processes STOPPED successfully.
 DB Background Processes was not STOPPED.
 Successfully STOPPED Oracle DB Instance: %s
 Failed to STOP Oracle DB Instance %s
 Successfully STARTED Oracle DB Instance: %s
 Failed to START Oracle DB Instance: %s
 Oracle SID: %s is not in the OPEN state
Marking DB as DOWN.
 Oracle SID: %s is in the OPEN state.
 Mandatory DB Process %s is NOT running.
 Failed Oracle Database Process Test for Oracle SID: %s.
See the message above for the missing process name(s).
 All mandatory processes are running for Oracle SID: %s
 Failed Oracle Listener are NOT running for Oracle SID: %s.
 Oracle Listener(s) are running for Oracle SID: %s
 Performing command: %s on listener: %s
 Unable to start Background Processes.  DB START FAILED.
 Failed to start DB listeners, shutting down Database background
processes.
 Unable to stop listeners.  DB STOP FAILED.
 Unable to stop DB Background Processes. DBStopAll FAILED.
 Oracle 10g CFC Oracle 10g AFC Problem with XML configuration file. Ensure a valid XML file supplied.
 Supplied directory %1$s for ORACLE_HOME does not exist.
 PFILE or SPFILE for the supplied ORACLE_SID does not exist at %1$s/dbs.
 Volume Group %1$s does not exist.
 User ID %1$s does not exist.
 Primary Node %1$s is not valid in the cluster.
 One of the Takeover node from %1$s is not valid in the cluster.
 Problem in parsing %1$s tag in function %2$s
 %1$s is not a valid Instance Name as per opmn.xml
 