Harvest

Hi everyone! I've been migrating an old CA Harvest 7.1 database to the one of the newest versions (CA Harvest 13), and I'm having an issue when it comes to upgrade the database, since the application convpw.exe doesn't find a library (hutilities.dll). Does anyone has any experience with this issue? Thanks in advance

Hi Edkeats,

Harvest 7.1 was a very old release and it had support of only 32 bit

Which platform are you working upon.?[Windows , Linux OR any Unix favours AIX etc.?]

Kindly review the below information and it could help resolve the issue.

CA Harvest SCM V13 includes support for both 32 bit and 64 bit

When you are upgrading from 7.1 to V13 ,first you need to upgrade to 32 bit version of Harvest SCM V13 and once it is successful ,you can choose further steps to migrate to CA Harvest V13 64 bit

[A]Harvest 7.1 [32 bit]                 ---->   CA Harvest SCM V13 [32 bit]

[B]CA Harvest SCM V13 [32 bit] ---->  CA Harvest SCM V13 [64 bit]

Verify the oracle support for the respective V13 release from the compatibility matrix posted in the support site from here

This could be a problem with a path of  direct migration from 7.1 32 bit to Harvest V13 64 bit

More detailed Notes:
----------------------------

If you intend to use 64 bit Harvest SCM server post upgrade, you would first need to upgrade to 32 bit Harvest SCM server only. If you want to use Harvest SCM 64 bit server on the same machine, please follow the steps below:

• Follow the procedure for upgrade from r7.1(32 bit) to V13 (32 bit) components.
• After successful upgradation, manually uninstall the V13 Harvest SCM 32 bit server and all the 32 bit components (for ex: client,agent etc.) if any exists on the same machine.
• Install the 64 bit server and other components (client, agent etc.) as required and configure the upgraded database to use the 64 bit server and database.
• You may need to follow the guidelines from Oracle/SQL Server to upgrade from 32 bit to 64 bit databases.
• If you want to use V13 Harvest SCM 64 bit server on a different machine using the upgraded database you need to configure the 64 bit server to use the upgraded database.

Please let us know if you need further assistance on this.

Regards,
Balakrishna.

Hi Shaba05:

First of all, thanks for your rapid answer, I really appreciate the information regarding the migration steps.

I'm working within a windows platform. The big problem here, is that we can't use the old machine where the oldest Harvest is installed, since it is using Windows Server 2003 as its OS. I read the compatibility matrix before, and I noticed that Harvest v13 is not supported/certificate for use on this machine, the same goes with the database that the old release is using (Oracle 10g, which is not being supported by Oracle anymore).

The workaround that I'm trying is to install a new instance of Harvest 13v on a Windows Server 2012 machine, and connect from there to a clone of the old schema located in another database (Oracle 10g as well). Then, I'm trying to upgrade the database by using the database configuration utility included in Harvest v13 (HDBSetup.exe). And here is where my problem arise, because the convpw.exe program can't find a library (hutilities.dll).

I can´t upgrade over the old machine due to various limitations, and the idea is to keep this old database working with Harvest 13v while we can work with another Harvest v13 instance with a new database for a few months.

I'll be glad to know if there is anything I can do in this scenario. 

Thanks again, I'm looking forward for your comments.

Best regards, 

Sebastián Pavez M.

Hi Sebastian,

Thanks for providing more detailed info on your environment .

1.Do you have plans to upgrade your oracle from 10g to supported release 11g or 12c.?

2.Harvest SCM V13 supports Oracle 11g and 12c as listed in the compatibility matrix

3.Have you installed Harvest SCM 32 bit or 64 bit on the windows 2012 machine.?

4. We can run convpw independently also without having to go through hdbsetup to identify and correct if any problem.

5.We would need more specific details on all your machine, database, SCM components installed to assist you further

Since this is a upgrade support , we would request you to raise a support ticket with CA to assist you further on this.

Please let us know if you need assistance raising a support ticket with CA.

Regards,
Balakrishna.

Hi Shaba05,

I'm answering your questions:

1.Do you have plans to upgrade your oracle from 10g to supported release 11g or 12c.?

 A: we are not planning on upgrading the old database, just keep it alive as long as it is necessary (May 2018 aprox.). The new instance of Harvest mentioned above will use an Oracle 12c database.

3.Have you installed Harvest SCM 32 bit or 64 bit on the windows 2012 machine.?

A: I installed the 64bit version on the Windows 2012 machine, should I try with the 32bit version first?

4. We can run convpw independently also without having to go through hdbsetup to identify and correct if any problem.

A: That is exactly what I did, and that's how I find out about the library issue.

5.We would need more specific details on all your machine, database, SCM components installed to assist you further

Since this is a upgrade support , we would request you to raise a support ticket with CA to assist you further on this.

A: I'll do that, thanks for your help, I appreciate it.

Best regards!

Sebastián Pavez M.

Hi Sebastian,

Thanks for providing detailed information and here are my responses.

1. As I understand ,you would still want to use Oracle 10g with CA Harvest SCM V 13 release.
This was never tested but theorotically it could work .
When you move to Oracle 12c approximately May 2018 , it would be a new instance
New instance is again a new harvest schema ,I believe OR perhaps this old schema with 10g will be imported into the Oracle 12c database.

2. Yes ,you can try with 32 bit first.
Uninstall all components of V13 -64 bit (Server ,Client,Agent) and try with 32 bit first on Windows 2012 box.

3. We can address this problem through your support ticket with CA.

and We can continue working on this through support ticket.

Regards,
Balakrishna.