Community Tip - You can change your system assigned username to something more personal in your community settings. X
Hi to all in the Intralink 3.x community
I have all the media i need to upgrade to M062 based on feedback from PTC support. The more i study what is needed to perform upgrade from M012 to M062 the moremixed signalsI get. We have one FS, one DS and one vault location. Please, if someone can, share the steps needed to accomplish this upgrade. I have taken over the admin spot (temporarily) and would like to move handful of users to WF4.
Thank you all in advance
JB
Hi to all in the Intralink 3.x community
I have all the media i need to upgrade to M062 based on feedback from PTC support. The more i study what is needed to perform upgrade from M012 to M062 the moremixed signalsI get. We have one FS, one DS and one vault location. Please, if someone can, share the steps needed to accomplish this upgrade. I have taken over the admin spot (temporarily) and would like to move handful of users to WF4.
Thank you all in advance
JB
Thanks to those individuals who offered up suggestions..I didupdate from M012 to M062 yesterday and all went well, thanks in partto details provided by users onthis list and our own,very knowledgeable IT guy. Thank you and best regards,
Jim
I recall from some PTC document that you have to first install M060, then only youshould install M062.
I am in the process of moving my Intralink 3.3 M022 server to Intralink 3.4 M062. According to PTC these are the steps to take from M012 to M062.
Then we need to re-export the dump using the same command which we did earlier so that thiscan be imported to the Pro/INTRALINK 3.4 M062
Exporting a dump file run the following command on the dataserver machine command line:
cd %proi_home%
cd export
ilink_import manager <name of=" dump=" file=">
example:
ilink_import manager c:\dump\today.dmp
26. Once this is done then we have to uninstall the Fiileserver, Dataserver, OSA from the system and delete the corresponding folders. 27. Even though we do this we will not be able to get rid of the Oracle so to uninstall the oracle please follow the following method: 1)Shutdown all the Oracle services. 2).Delete the folder C:\Program Files\Oracle 3).Delete the <oracle loadpoint="> folder. 4).Open windows registry editor and remove the following entries: 1.HKEY_LOCAL_MACHINE=>SOFTWARE=>ORACLE 2.HKEY_LOCAL_MACHINE=>SYSTEM=>CurrentControlSet=>Services and remove all Oracle related service 5)Delete the hidden folder, “Zero G Registry” located in the folder C:\Program Files and delete the OSIA registry key “My Computer\HKEY_LOCAL_MACHINE\Software\PTC\OSIA” 6)Re-boot the machine. Delete the following environment variables if they exist: 1)Right click on #My computer #Advanced #Environment 2)Delete the LANGUAGE variable 3)Delete the ORACLE_HOME variable 4)Delete ORACLE_SID variable 5 )Clean the PATH variable if they have reference to old Oracle or dataserver installation. 28. Once this is done then re-boot the machine. 29. After the reboot we need to start the installation for Pro/INTRALIN 3.4 M062. The CD required for the installation are as follows: a. R3.4 PRO/INTRALINK SERVICE PACK CD SET 3.4 M062 b. R3.4 PRO/INTRALINK ORACLE SOFTWARE ASSISTANT CD 3.4 M060 c. R10GR2 ORACLE 10.2.0.1.0 FOR WINDOWS 32 DVD 10G 2005000 d. ORACLE 10.2.0.3.0 PATCH SET 10G 2007100 30. We need to start the installation with OSA 3.4 M060 which will ask for Oracle 10.2.0.1.0 DVD 31. Then it will ask for oracle 10.2.0.3.0 Patch. 32. After this we need to install the pro/INTRALINK 3.4 M062 Fileserver, Dataserver in the similar way we did for Pro/INTRALINK 3.4 M012 33. After this we need to import the dump which we have taken from Pro/INTRALINK 3.4 M012. 34. Then after the dump once again run the ilink patches and this will complete the installation of Pro/INTRALINK 3.4 M062. 35. Now as the dataserver is installed we need to point the dataserver to the correct vault. 36. For that there is another file attached with this mail. 37. Please download it and run as follows: 1.Save the attached ‘create_vault_script.sql’ script to c:\temp or /tmp directory 2.Open a DOS command prompt and then change directory to c:\temp eg: cd c:\temp 3. sqlplus system/manager 4. @create_vault_script.sql Step 4. Should create the file ‘update_vaults.sql’ at the location c:\temp 5.Open the file update_vaults.sql in the WordPad and then edit the value of FSVHOST, POOLHOST and POOLPATH. 6.Save the file ‘update_vaults.sql’ 7.In the DOS window @update_vaults.sql 8.Exit