Frank,

I do not know that this will do all of what you want it to do... but
have you tried this? :

Installing-710.pdf Pg 158
"
Command options to suppress installation forms

To suppress the installation of all installation forms, including the
User and Group
forms, enter the following command:
      # ./ar_install -noschemas

NOTE: Use this option only when you intend to immediately load forms
from a previous
installation of AR System.
"

I would think it should be ok to use this option when installing
multiple nodes to an app server cluster.


Also... check out page 34... it has this to say:
"
Upgrading servers in a server group

To upgrade servers that are part of a server group, remember these guidelines:

* Stop all AR System servers except the server that owns the Admin
operation. (To verify this, open the Configuration tab on the AR
System Administration: Server Information form, and make sure that the
Disable Admin Operations check box is not selected.)

* Upgrade the server that owns the Admin operation first. Select the
Upgrade (AR System database) option during the upgrade.

* Upgrade the other servers in the group next. Select the Share (AR
System database) option.

* Do not start the "non-Admin" servers before performing the upgrade
installation on them.
"

So ... maybe if the ARS Server is stopped then it can not talk to the
DB? Maybe the "Share" install simply updates the file system and
quietly errors about failed imports? (Or were you doing a clean host
install on the other nodes in the cluster during your previous
testing?)

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.




On Tue, Oct 28, 2008 at 3:26 PM, Frank Caruso <[EMAIL PROTECTED]> wrote:
> ** Migrating from a 6.3 database to 7.1p3. All home grown stuff with no OOB
> applications. Also migrating to brand new application hosts and database
> hosts. This will allow us to leave the entire production environment
> untouched while we do the upgrade.
>
> ARS is Solaris 9 with Sybase 12.5 on RHEL
>
> Abbreviated Steps:
> 1. Take a COLD copy of the production database and import to new database
> host.
> 2. Run 7.1 install on first server  which will perform the necessary updates
> to the database. This will also include running email and flash boards
> install.
> 3. Run 7.1 install on second server and run as a shared install not upgrade.
> This will also include running email and flash boards install.
>
> Question:
> Step 3: All three installs appear to importing the same forms even though
> the first install took care of that. This step seems to take the longest,
> about 25 minutes. I'm talking about the Administrator, email and flash
> boards forms.
>
> A. Is is possible to run the shared install but have it not import anything
> but just install the necessary files on the host?
> B. If not, can I just copy the entire install directory from the first host
> to the second and make sure any host specific files are updated?
>
> I was able to actually do part B without any issues but wanted to get the
> communities take on doing an install that way.
>
> Thank you.
>
> Frank

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to