Sorry for the late reply, meetings all day today.  I will try to run the
installer as SHARED instead of upgrade.  I was hesitant on just copying
the whole directory as Remedy maybe does some type of file lock on
certain files but wasn't sure.  That is good to know that patch 20
didn't include everything and that you needed to run the installer.  We
did run the installer on our primary server (thank god).
 
Thank you guys for all your input.
 
 
Bob Halstead
Bresnan Communications

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, April 04, 2007 12:32 PM
To: [email protected]
Subject: Re: Updating a server via coping files directly


** 
It was a problem with a missing .so file and yes the way to fix that was
to run the installer to upgrade - else the patch would fail as there
would be a failure to bring up the AR Server..
 
Cheers
 
Joe


----- Original Message ----
From: Frank Caruso <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, April 4, 2007 1:31:18 PM
Subject: Re: Updating a server via coping files directly

** A couple of thoughts:

1. Since the production database has already been upgraded to patch 20
then I would think re-running the installer on the other box would do
nothing to the database. I believe it checks a table (control???) for
the dbase patch version. 

2. If the other box has version of ARS (say p19 installed) could you not
just copy the entire ARS directory (/opt/ar/ or /usr/ar) from the p20
server to the new other server? This would capture all ARS binaries,
libs, so, etc. 

I do remember seeing something about how p20 file down load did not
include all of the files, and that users had to download  the installer
to get the missing ones.

Frank




On 4/4/07, Halstead, Robert <[EMAIL PROTECTED]> wrote: 

        ** 
        I'm trying to upgrade a secondary server to patch 20. We're
running ARSystem with Oracle under Solaris.  We are creating a server
group so I can't use the installer to install the patch as it will touch
the production database.  So I'm copying files directly.
         
        While following the directions to do this under Unix, I noticed
that there is no "server" binary in the patch 20 files (arservora).
Also, I am a little confused on steps 3 and 5.
         
        "3) Copy the new patched binaries to the ARSystem installation
directory."
        Is this referring to the libiuc*bmc.so*, libxerces*bmc.so*,
libxalan*bmc.so* files that are listed under the "For Solaris:" part
under the "Files Patched" portion of the readme file?
        
        "5) Copy the other patched files into the ARSystem installation
directory."
        And, is this referring to the "File Patched: Unix and Linux"
portion of the readme file?
         
        Since I can't seem to find the arservora to rename it to
arserverd, I can't complete step 6.
        I usually use the installer to do the patches, so this is my
first time coping files.  Any help would be appreciated.
         
        Thanks,
         
        Bob Halstead
        Bresnan Communications
        __20060125_______________________This posting was submitted with
HTML in it___ 




-- 
Frank Caruso
Specific Integration, Inc.
Senior Remedy Engineer, ITIL Foundation Certified
www.specificintegration.com <http://www.specificintegration.com/> 
703-376-1249 __20060125_______________________This posting was submitted
with HTML in it___


  _____  

Expecting? Get great news right away with email Auto-Check.
<http://us.rd.yahoo.com/evt=49982/*http://advision.webevents.yahoo.com/m
ailbeta/newmail_tools.html> 
Try the Yahoo! Mail Beta.
<http://us.rd.yahoo.com/evt=49982/*http://advision.webevents.yahoo.com/m
ailbeta/newmail_tools.html>  __20060125_______________________This
posting was submitted with HTML in it___

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

Reply via email to