Subj: [datamgt] RE: [Summaryt] How to upgrade Intralink 3.2 to 3.3 on Unix  
Date: 8/25/2003 4:20:58 PM Eastern Daylight Time 
From: mferyn@keytronicems.com 
To: datamgt@ptcuser.org 
Sent from the Internet (Details) 
 
First, I want to thank everyone that replied to my question. The first reply
from Ian Cameron is what helped me the most, and allow me to do the upgrade
instead of a new install. Ian, thanks also for the list if patches that
should be applied. I also appreciate the answers on how to do a new install.
These replies allow me to be prepared in case the upgrade did not work. I
had called PTC Tech support, but they did not have the answers that I
needed. Here are the replies with my comments.

****************************************************************************
********
1. I had the same problem on my test server. After the second failure I 
opened a call with PTC and they had me run ptcsetup from the cdrom path 
( ie. /<mount_point>/dsrc/hpux11_pa32/obj/ptcsetup ) which worked like a 
charm.

Good luck,
Ian

(NOTE! This worked for me, whereas using, /<mount_point>/setup, did not
work, Maurice)

****************************************************************************
***********
2. These steps are very old but its the basics that we have been following
for a long time

The basic steps are - NOTE Assume using same file structure
1) Move Vaults to new location- anywhere so not deleted Intralink can find
2) Find out size of Intralink DBF files, used to resize on import
3) Delete Intralink Dataserver/fileserver
4) Clean Install of Intralink - ok to use new build
5) Resize Database files using DSMU
6) Import dump file
    a) From dataserver\intralink\export run, "ilink_import system/manager
<file>"
    b) If problems importing- almost always problem with dbf size, use DSMU
to resize database
    c) Run Intralink Patches to upgrade/patch database. specific steps
listed below.
    d) If system gives password problems, from
dataserver\intralink\tools\bin run "proipwd system manager"
7) Move vaults back to correct location, so Intralink can find
    a) if Fileserver or folder path has changed, can use either DSMU to move
or SQL (faster, recovery more difficult and I am not dba)
    b) Once Intralink thinks files are in correct location (by using DSMU)
then it is safe to move files into correct structure

Paul

<!--[if !supportLists]-->          <!--[endif]-->install patches

<!--[if !supportLists]-->A.      <!--[endif]-->cd p:

<!--[if !supportLists]-->B.
<!--[endif]-->\database\ilink_patches\tools

<!--[if !supportEmptyParas]--><!--[endif]-->

C.  set                   PROI_SYS_PWD = dschangeme

                ORA_SYS_PWD = manager

                FS_SYS_PWD = fschangeme

     ilink_patches                ORACLE ilnk <R> go get coffee

     ilink_patches                 SCHEMA english INTRALINK <R>

     ilink_patches VALIDATION english INTRALINK <R>

<!--[if !supportEmptyParas]--> <!--[endif]-->

(NOTE! Run ilink_patches.sh on Unix. Maurice)

****************************************************************************
*****
3. I would suggest making the database file autoextend for the import
instead
of setting them in the dsmu.  To do this logon to sql and run the following
commands.

First list your datafiles:
      col file_name format a45
      col tablespace_name format a15
      select file_name, tablespace_name from dba_data_files;
Now autoextend them:
      alter database datafile '<path and name of datafile>' autoextend on;
Do this for each datafile in the list from above.
Now you must run the patches.  From the dataserver
loadpoint/intrlaink/dbs/ilink_patches/tools directory Set the following
environment variables:
      set PROI_SYS_PWD=dschangeme
      set ORA_SYS_PWD=manager
      set FS_SYS_PWD=fschangeme
Now run the patches.
      ilink_patches.bat all ilnk intralink

Now that all is done I would change the datafiles back to not autoextend
and resize them to 20-30% larger that they currently are with the following
commands in sql.
      alter database datafile '<path and name of datafile>' autoextend off;
for each datafile
now set the size.
      alter database datafile '<path and name of datafile>' resize <size in
meg>;
for each datafile

Hope this helps,

Regards,
________________________
Aaron Haggard

(NOTE! I did turn on autoextend for the Temporary table. In the, alter
database datafile, command above, the word "datafile" worked to turn on
autoextend in Intralink version 3.2. After I upgraded to version 3.3, I had
to use the word "tempfile" to turn off autoextend. Maurice)


****************************************************************************
*****
-----Original Message-----
From: Feryn, Maurice [mailto:mferyn@keytronicems.com]
Sent: Monday, August 18, 2003 11:36 AM
To: datamgt
Subject: [datamgt] How to upgrade Intralink 3.2 to 3.3 on Unix


I need to upgrade IntraLink on our HP-UX system from 3.2 to 3.3 and would
like to hear any advice others may have from their experience upgrading a
Unix system. I have read many of the recent e-mails on upgrading, but I
still have a few concerns. 

I did try to use the upgrade process, but during the DataServer upgrade the
process got hung, I think because it failed to stop the dataserver process.
I am now planning to do a fresh install of the DataServer 3.3, and then
import the dump file from version 3.2.

I know I must increase the tablespace size and was told I can do this from
the DSMU after I install the DataServer, and before I import the dump file.
I would appreciate any comments about this procedure.

Also, after I import the dump file I must update the patches by running a
script called ilink_patches. I will like to know what the exact commands are
and any other info that is available.I have some concerns because the script
has a .tcl extension.

Thanks so much for any help that is offered. I am planning to upgrade this
coming weekend. I do not have a test server to try out any of this process.

Thank you,

Maurice Feryn
KeyTronicEMS.
509-927-5527
mferyn@keytronicems.com