Pareto: la regla del 80/20.

This section describes special considerations for multiple OracleAS Metadata Repositories and OracleAS Metadata Repositories created using the OracleAS Metadata Repository Creation Assistant.

5.16.1 Special Considerations for Multiple OracleAS Metadata Repository

Configurations

By default, the credentials you specified in the asgctl connect command are used whenever one OracleAS Guard server connects to another OracleAS Guard server. However, there may be cases where you want to do either of the following:

■ Use different credentials for each system on a given site, see Section 5.16.1.1, "Setting asgctl Credentials".

■ Use a common set of credentials in the standby topology that are the same as the credentials used in the primary topology, see Section 5.16.1.2, "Specifying the Primary Database".

If the credentials for any host system are not the same as those used in the asgctl connect command, you must set the OracleAS Guard credentials so that the OracleAS Guard server can connect to each host system in the configuration.

5.16.1.1 Setting asgctl Credentials

To set different credentials for all the host systems belonging to the same topology, enter the following asgctl command at the asgctl prompt. Specify the node name of the host system to which the credentials apply and the ias_admin account name and password for the ias_admin account created during the Oracle Application Server

Special Considerations for Some OracleAS Metadata Repository Configurations

These settings are good for the current session.

ASGCTL> set asg credentials standbyinfra ias_admin/<iasadminpwd> for topology

When you specify the key words, for topology, you set the credentials for all the host systems that belong to the same topology as the specified system; otherwise, the credentials will apply only for the specified host system.

The set asg credentials command is also useful when you want to use different credentials for a specific server on the topology. In the previous example, the same credentials were set for all nodes on the standby topology, so that these credentials differ from the credentials used in the primary topology. The following command sets the credentials for a specific node, the standbyinfra node, on the standby topology.

ASGCTL> set asg credentials standbyinfra ias_admin/<iasadminpwd>

To summarize, if you set the credentials for a topology, these credentials are inherited for the entire topology. If you set the credentials for an individual host on the topology, the credentials (for this host) override the default credentials set for the topology. In addition, for topologies that have more than one Infrastructure, such as a collocated Oracle Internet Directory+OracleAS Metadata Repository and a separate Portal OracleAS Metadata Repository, OracleAS Guard requires that you set the credentials for each system on which an Infrastructure resides before performing any important OracleAS Guard operations, such as instantiate, sync, switchover, and failover. See set asg credentials for an example.

5.16.1.2 Specifying the Primary Database

To identify the OracleAS Infrastructure database on the primary topology, enter the following asgctl command at the asgctl prompt. Specify the user name and password for the database account with sysdba privileges to access the OracleAS Infrastructure Database on the primary topology and the TNS service name of the OracleAS Infrastructure database:

ASGCTL> set primary database sys/testpwd@asdb Checking connection to database asdb

ASGCTL>

The standby site uses the same values as specified for the primary database because the service name and password for both the primary and standby OracleAS

Infrastructure databases must be the same.

If a production or standby site has multiple OracleAS Metadata Repository instances installed and you are performing an instantiate, sync, switchover, or failover

operation, you must identify all of the OracleAS Metadata Repository instances by performing a set primary database command for each OracleAS Metadata Repository instance before performing either an instantiate, sync, switchover, or failover

operation. See set asg credentials for an example.

5.16.1.3 Setting OracleAS Guard Port Numbers

OracleAS Guard uses a default port (port) number of 7890; for example, port=7890. If there are any additional Oracle homes installed on a system, each additional Oracle

Note: If this is an OracleAS 10.1.3 installation, the user name must be oc4jadmin and the password for the oc4jadmin account created during the Oracle Application Server 10.1.3 installation.

home must have a unique OracleAS Guard port number, that is usually incremented by the value one, for example, port=7891, and so forth. See Section 5.4.6, "Supported OracleAS Disaster Recovery Configurations" for more information.

5.16.2 Special Considerations for OracleAS Metadata Repository Configurations

Created Using OracleAS Metadata Repository Creation Assistant

The following items are special considerations for an OracleAS Metadata Repository configuration created using OracleAS Metadata Repository Creation Assistant. These Metadata Repository databases are installed in Oracle homes with schemas containing user data. For this reason, there are some special considerations regarding OracleAS Disaster Recovery.

■ On the standby site, no Metadata Repository is created by OracleAS Disaster Recovery. The System Administrator must use the OracleAS Metadata Repository Creation Assistant on the standby site and create this Metadata Repository. ■ During a clone topology operation to the standby site no instantiate operation is

performed on the Metadata Repository.

■ Warning: Do not perform a clone operation to a standby system containing an existing Oracle home because it will get overwritten. Only perform a clone operation to a standby system where there is no Oracle home installed.

■ The OracleAS Disaster Recovery solution assumes that user schemas are already configured for Oracle Data Guard.

■ The OracleAS Disaster Recovery solution assumes that when using Oracle Data Guard, that the Metadata Repository is not in managed recovery mode.

■ OracleAS Disaster Recovery will not change the recovery mode of Oracle Data Guard for the Metadata Repository if it is found to be in managed recovery mode; instead, OracleAS Guard will issue a warning indicating that the database is in managed recovery mode and this feature must be set differently.

■ OracleAS Guard must be installed in every Oracle home on every system that is part of your production and standby topology configured for the OracleAS Disaster Recovery solution. OracleAS Guard can be installed as a standalone install a kit located on OracleAS Utility media #2. See the OracleAS Disaster Recovery installation information in Oracle Application Server Installation Guide for more information.

5.17 Special Considerations for OracleAS Disaster Recovery