[ipac] rebuild HIP 3.x on Linux

[Casey Durfee]

I wrote a resolution back in 2001 for Dynix's knowledge base that describes exactly how to move the admin database from one platform to another.  We did it dozens of times when I worked there.  There's no reason why you should lose a single bit of data or customization in such a migration.
 
Basically you make a transportable backup of the DB (either using the gbak command-line tool or IBConsole), transfer the transportable backup file, and then restore the DB from the backup on the new server.  It's not rocket surgery, and it's really something that you'd expect someone doing your migration to know about.  
 
It's just pathetic that you're getting vastly better HIP support from the mailing list than from the company itself.  I had thought I was through working for Dynix, but it's more like they just no longer pay me...
 
--Casey

>>> ipac-request at lists.tblc.org 11/10/2006 12:25 PM >>>

Message: 1
Date: Fri, 10 Nov 2006 13:09:35 -0600
From: Natasha Stephan <stephann at lindahall.org>
Subject: [ipac] rebuild HIP 3.x on Linux
To: ipac at lists.tblc.org 
Message-ID: <200611101904.kAAJ4AHt025644 at copernicus.lindahall.org>
Content-Type: text/plain; charset=us-ascii; format=flowed;
x-avg-checked=avg-ok-5A8A68A9

Hi all,
We are in the process of migrating HIP 3.08 from a Solaris 8 box to a 
RH Linux box.

<gripe>
Actually, I should say we are recreating our HIP _from scratch_ on a 
new Linux box.  Not "just for kicks" (even I am not that 
masochistic).  No, we are recreating HIP from scratch because we _have_ to!
SirsiDynix came out last Thursday (Nov. 2) to do the migration of 
both our servers (HIP and db) to brand-new Linux boxes.  These are 
servers that we had SD spec out for us more than a year ago.  Servers 
whose specs changed when the recommendations for Horizon 8 came 
out.  Servers that were supposed to be able to run HIP and 
Horizon.  Servers that were purchased and staged in October of this year.
The SD tech and I tried three times to FTP our ipacadmin.gdb to the 
Linux box and start HIP.  When he finally called Provo for some help, 
he was told that it is not possible to migrate ipacadmin.gdb from 
Solaris to Linux.  Why no one knew this (or told us this) when our 
salesperson and I planned our migration, I have no idea.  What is 
even more amazing is that no one knew this (or told us this) when 
they sent the tech out to do our on-site install!  Either no one had 
tried this kind of migration before they promised to do ours (which 
demonstrates a severe lack of planning) or no one bothered to share 
this information with the people who were planning to do ours (which 
demonstrates a severe lack of communication).
</gripe>

Anyway, I am now setting up cron jobs on the new Linux box.  I used 
to run "rebuild.sh" against the admin database every weekend, while 
the Horizon database was unavailable (in single-user mode for 
DBCC).  The file lived in 
/opt/dynix/appserver/jboss/server/default/data on our Solaris 8 
box.  There is no such file in 
/opt/dynix/appserver/jboss/server/default/data on our new Linux 
box.  I can't find it anywhere.

Do those of you with Horizon 3.x ever run rebuild.sh?  If so, did 
SirsiDynix create the file for you, or did you create it?  And if you 
are running Linux on your HIP server, could you share the text of 
your rebuild.sh?
Thanks,
Natasha

---
Natasha Stephan
LEONARDO Project Leader
http://leonardo.lindahall.org ( http://leonardo.lindahall.org/ )
816-926-8750/1-800-662-1545 x750 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.tblc.org/pipermail/ipac/attachments/20061110/52504ec2/attachment.html