Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Linux x86
B19312-02
  Go To Documentation Library
Home
Go To Table Of Contents
Contents

Previous
Previous
Next
Next
 

4 High Availability

This chapter describes issues related to highly available topologies. This chapter contains the following issues:

4.1 OracleAS Disaster Recovery: Discover Topology Command

If you run the "discover topology" command on a node that contains more than one Oracle home, and one of the Oracle homes is invalid for some reason (that is, the Oracle home does not appear in the Oracle Universal Installer), the "discover topology" command generates a warning:

ASGCTL> discover topology oidpass=welcome1
Discovering topology on host "hasun1" with IP address "123.45.67.89"

hasun1:7890
 Connecting to the OID server on host "hasun12vip1.mydomain.com"
   using SSL port "636" and username "orcladmin"
 Getting the list of databases from OID
 Gathering database information for SID "orcl" from host
                                               "hasun12vip1.mydomain.com"
 Getting the list of instances from OID
 Gathering instance information for "immr.hasun12vip1.mydomain.com" from host
                                               "hasun12vip1.mydomain.com"
 Gathering instance information for "asmid.haqadr01.mydomain.com" from host
                                               "haqadr01.mydomain.com"
      **********  WARNING  **********
hasun1: -->ASG_IAS-15779: Error getting instance information for instance
 "asmid.haqadr01.mydomain.com" from host "haqadr01.mydomain.com".  This instance
 will be excluded from the topology.xml file
drmt: -->ASG_IAS-15632: The home that contains instance 
 "asmid.haqadr01.mydomain.com" could not be found
drmt: -->ASG_DUF-4950: An error occurred on host "drmt" with IP "130.35.45.23" and
 port "7890"
      ********  END WARNING  ********
The topology has been discovered. A topology.xml file has been written to each
home in the topology.

To work around this issue, delete the entry for the invalid Oracle home from the Inventory.xml file in the oraInventory directory, then rerun the "discover topology" command.