Additional Management Agent Install questions.

Question

Our Solaris hosts have 2 interfaces. How can I get the Agent to use the non-primary hostname (and thus prefered interface) during install?
Can the prefered hostname be supplied during a silent install?
Modifying the targets.xls and emd.properties files and replacing all "host" entries to the preferred hostname fixes most problems (after a 'default' install chooses primary hostname).
Have I missed any other files needing modification?
After cleaning out orphaned OMS entries & resecuring the agent all "seems" fine. Except - creation of standby databases (using Grid tools) won't work. After manually getting standby database going, creation of DG configuration using Grid tools fails - hosts are not 'registered'. "Registering' and Verification of other working DG Configurations (that can be switchover by DGMGRL) fail with 'hosts not registered'. Can anyone help?
Metalink documents 71911.1 and 73407.1 conflict on how /etc/hosts file should be configured.
Is it:
ip primaryhostname.domain primaryhostname
ip secondaryhostname.domain secondaryhostname
or
ip primaryhostname primaryhostname.domain
ip secondaryhostname secondaryhostname.domain
Any help/insights very appreciated.

Answer 1

Thank you for the suggestions, I will try them.
I have found out since my original posting that BOTH 9i and 10g Dataguard BROKER do NOT support virtual hostnames (as is used when refering to a remote host using secondary network on Solaris). This is NOT going to be fixed until Oracle Grid version 11 - whenever that might be.
We are dropping the use of 9i OMS and 10g Grid control because of this.
All dataguards are being set up using required (secondary/virtual) host names manually.
Switchovers are done manually. (When used, DG Broker would , "knowing better" alter remote archive log destinations during a switchover to the primary network, defeating our requirements)
Some traps for the unwary:
1. Version 1 of 9i DG concepts and admin manual makes no mention that during manual switchover (physical) you need to set, on original primary, remote dest entry to 'defer' and on new primary, remote dest entry to 'enable' . DG Broker , if used to do switchovers, does this for you.
2.DG Broker also does switchovers using 'non-standard/different to documented manual method' commands IE: Using "until change XXXXXXXXXXX" syntax (on Logical Db's for sure, on Physicals - unsure) You will need database links and tnsnames entries pre-configured if you attempt to emulate that method. You will also need to find the right query to get the change number required from originating primary database. I use the documented steps in the manual method for switchovers (with extra steps to enable/defer remote destinations) reliably.
3. 10gV2 Grid control has a BUG when making Standby databases - you must enter log_file_name_convert on 'OFS' screen. Can be identical entries though(and will be when 2 hosts involved).
4.No 9i dataGuard wizard graphs work on secondary network setups.
5.Oracle SR support staff were not aware of the bugs, even though some were documented on Metalink nearly a year ago.
All things considered, me might use 10gV2 Grid control (except for making or controlling DG configurations) for an 'overview' tool as it is now stable enough to use (10gv1 was a shocker).