ZISO8859-1009$Mr      $2Ws'':dZe f g hO ijwkbl\myno 5p&Bqsir*spt yu;wx!y(#hz%{'H|)},~. 1V1s!1!111M2 62W72B23 K3)d3ua3 4< H4] E4 K4 O585{5d6##6`6<7 77J7h8Bs8K9w9kd9e:Hx:b;'>; < =^ = > ?$?@/A2+Ab'A0AAQBPBLC$CqDdZDeF5f0FgG hGiH( XII#J*J$YJO$J*JUJ KO Kl 1K2.K.K.L)LE,Lo%L,L'L <M %MT (Mz oM 7N;NK2N'N-N(O-O9&Og<8OKO+P:P?PPzPZ GP8PHQ"QbQ/Q@Q-R KRBSelect Specific Configuration You Wish To CreateSelect CFC InstanceAdd an Oracle CFC Application ServerOracle AS CFC Instance NameApplication NamePrimary NodeTakeover Node(s)Oracle Metadata RepositoryService IP LabelShared Volume Group(s)Oracle OID and SSO ComponentsSelect AFC InstanceAdd an Oracle AFC Application ServerOracle AS AFC Instance NameParticipating NodesConcurrent Volume Group(s)Select RDBMS InstanceAdd an Oracle RDBMS InstanceOracle Instance NameModify an Oracle CFC Application ServerModify an Oracle AFC Application ServerModify an Oracle RDBMS InstanceAdd 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 10g 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 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 PowerHA SystemMirror cluster wide unique name. The application name is a container for the PowerHA SystemMirror 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 PowerHA SystemMirror 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 PowerHA SystemMirror cluster. If the desired node is not already part of the PowerHA SystemMirror 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 PowerHA SystemMirror 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 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 Smart Assist. By default all SSO/OID components will be selected in the dialog. Removing components from this list will remove the component from PowerHA SystemMirror control. PowerHA SystemMirror 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 PowerHA SystemMirror 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 PowerHA SystemMirror cluster configuration. PowerHA SystemMirror will discover configured SSO OID components configured in AFC mode for Oracle 10g 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...) 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 PowerHA SystemMirror 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 PowerHA SystemMirror 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 PowerHA SystemMirror cluster configuration. RDBMS instances will be added as Cold Failover Cluster (CFC) / hot-standby configurations. The PowerHA SystemMirror 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 PowerHA SystemMirror 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 PowerHA SystemMirror cluster. If the desired node is not already part of the PowerHA SystemMirror 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 PowerHA SystemMirror 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 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 PowerHA SystemMirror can be choosen, or a new service IP label will be created if the label does not already exist in the PowerHA SystemMirror cluster configuration. Shared Volume Group(s) The default list of volume groups auto-discovered by the Oracle 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 PowerHA SystemMirror defined Oracle application database. The existing PowerHA SystemMirror components will be modified for the selected RDBMS instance. The PowerHA SystemMirror 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 PowerHA SystemMirror 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 PowerHA SystemMirror cluster configuration. 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 10g 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 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 Database Smart AssistOracle RDBMS DatabaseOracle Application Server AFC 10gOracle Application Server CFC 10gOracle Application Server CFCOracle Application Server AFCCreating PowerHA SystemMirror resource group: %s to support MR Database: %s. Creating PowerHA SystemMirror application server: %s Creating PowerHA SystemMirror application monitor: %s Adding MR Database: %s to the PowerHA SystemMirror configuration. Creating service IP label: %s Adding Oracle AS component: %s to PowerHA SystemMirror resource group %s Creating PowerHA SystemMirror resource group: %s to support Oracle Application Server component: %s Adding PowerHA SystemMirror 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 PowerHA SystemMirror configuration. Adding Oracle RDBMS Database Listener [ IP Label: %s, Listener Name: %s] Creating PowerHA SystemMirror 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 PowerHA SystemMirror cluster components. Oracle RDBMS Database version: %s Modifying Oracle RDBMS Database: %s, removing existing PowerHA SystemMirror cluster components. Successfully added Listener monitors of DB instance: "%1$s" Failed to add Listener monitors of DB instance: "%1$s" PowerHA SystemMirror supports maximum of %1$d listener application monitors per oracle database application server. Created %2$d listener application monitors for application server "%3$s". ERROR: Oracle file system should be mounted and available before trying to modify the oracle instance. ERROR: The PowerHA SystemMirror resource group: %s already exists. Please choose another name for the application. Unexpected error encountered while attempting to create resource group: %s ERROR: The PowerHA SystemMirror application server: %s already exists. Please choose another name for the application. Unexpected error encountered while attempting to create PowerHA SystemMirror application server: %s Unexpected error encountered while attempting to create PowerHA SystemMirror application monitor: %s ERROR: The PowerHA SystemMirror application monitor: %s already exists. Please choose another name for the application. Unexpected error encountered while attempting to create PowerHA SystemMirror service IP label: %s ERROR: Unable to create the service IP label: %s There are no available PowerHA SystemMirror networks defined. Please either defined one or more PowerHA SystemMirror networks. Or, alternatively define the service IP label within the PowerHA SystemMirror configuration prior to re-running the Oracle smart assistant. Unexpected error encountered while attempting to associate the PowerHA SystemMirror resource group: %s with the Oracle smart assist application %s. ERROR: An application with the name: %s is already defined to PowerHA SystemMirror. Please choose another Oracle smart assist application name. Unexpected error encountered while attempting to add Oracle Application Server component resources to the PowerHA SystemMirror resource group: %s. Unexpected error encountered while attempting to add Oracle Application Server metadata to the PowerHA SystemMirror 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 PowerHA SystemMirror Oracle Smart Assist. Unexpected error encountered while attempting to add PowerHA SystemMirror application monitor: %s for PowerHA SystemMirror 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 PowerHA SystemMirror 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 PowerHA SystemMirror support to resolve the error reported above. A copy of the Oracle Smart Assistant log file: /var/hacmp/log/oraclesa.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. ERROR: The environment variable ORACLE_USER must be set. Export ORACLE_USER with appropriate Oracle Application Server user and re-run the HACMP Oracle Smart Assist. ERROR: "%1$s" missing argument -l listener name ERROR: Modification of ORACLE_HOME is not allowed if any of the cluster nodes are in unmanage state. Node(s) in UNMANAGE state are: %1$s ERROR: Modification of ORACLE_HOME is not allowed while the cluster services are running on the other cluster nodes (%1$s). This command must be run from a node where cluster services are running, in order for the Dynamic Reconfiguration to proceed. WARNING: Failed to restore GLVM replicated resource for Smart Assist Resource Group %1$s. Run following command manually to make sure GLVM statistics are collected and shown in PowerHA GUI. /usr/es/sbin/cluster/glvm/utils/cl_glvm_configuration -c %1$s Requested STOP of AS instance: %s component: %s in PowerHA SystemMirror 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 PowerHA SystemMirror application %s. Failed to START Oracle component %s Successfully STARTED Oracle component: %s Monitoring AS instance: %s and component: %s in PowerHA SystemMirror application: %s Component %s is NOT RUNNING Component %s is running. Monitoring PowerHA SystemMirror application: %s. 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 Successfully STARTED Oracle Listener: "%1$s" Failed to START Oracle Listener: "%1$s" Successfully STOPPED Oracle Listener: "%1$s" Failed to STOP Oracle Listener:"%1$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 CFCOracle 10g AFCProblem 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 Supplied value for %1$s tag is invalid. Considering default option "%2$s".