Livelink 9.5 SP1 ISO-LATIN1 to UTF-8

[fwibowo]

We are currently running LL 9.5 SP1 ISO_LATIN1 and would like to upgrade to LL 9.5 SP1 UTF-8. Our Oracle DB connected to LL is already in UTF-8. All documentations from LL are written for LL where the DB is ISO-LATIN 1.
I was wondering if all 13 steps must be executed if the is already in UTF-8. Anybody in similar situation has doen this?

Here are the 13 steps from LL documentation for the upgrade
1. Run the Livelink 9.5.0 UTF-8 installation utility, using the Upgrade Server option (see "Installing Livelink 9.5.0 UTF-8," page 13).
2. Migrate your existing search indexes if you want to retain them (see "Migrating Existing Search Indexes," page 17).
3. Install the UTF-8 Conversion Tools (see "Installing the UTF-8 Conversion Tools," page 18). Is this the correct one UTF8Converter_10014_WIN.exe ?
4. Apply the latest monthly patch for Livelink 9.5.0 (see "Applying the Latest Monthly Patch for Livelink," page 20).
5. Run the Oracle Conversion Script (see "Running the Oracle Conversion Script," page 21).
6. If necessary, run the alter.log script (see "Executing the alter.log Script," page 23).
7. Export the converted database (see "Exporting the Converted Oracle Database," page 25).
8. Configure Livelink server parameters (see "Configuring Livelink Server Parameters," page 25).
9. Create a new Oracle database user to own the Livelink tables in the UTF-8 Oracle instance (see "Creating a New Oracle Tablespace and User," page 26).
10. Import the converted database into the UTF-8 Oracle tablespace, and then connect Livelink to the imported database (see "Importing and Connecting the Converted Oracle Database," page 28).
11. Install and execute the Text and Binary Conversion Tool from the Livelink Administration page (see "Installing and Executing the Text and Binary Conversion Tool," page 29).
12. Upgrade any optional modules (see "Upgrading Optional Modules," page 30).
13. Reestablish search indexes (see "Reestablishing Search Indexes," page 30).

 

[appnair]

I am not familiar with this but I would if you can thru OpenText KB touch base with the ConocoPhillips livelink folks.I was at one time the COP LL admin.Of late thru my informal talks with people there I came to understand that the upgrade is not the most smoothest one can expect.Perhaps your environment is not that complicated.Our was very complicated and customized.What did OT say wehen you asked this qn.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[ggriffit]

I'd suggest you replicate this in a test system and test and retest the upgrade until you have it fine tuned. This is how I've managed upgrades, LL and Non-UTF8 to UTF8, in this way and they have all been done in that format.

Once you've followed the published process, you can try reducing the number of steps, changing the order etc until you get a process you are happy with.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/