topic Re: PCM+ 3.2 to 4.0 Upgrade in PCM

PCM+ 3.2 to 4.0 Upgrade

Stephen Schickler — Fri, 16 Dec 2011 15:49:52 GMT

Going through the motions of doing an upgrade of PCM+ 3.2 to 4.0 when the install failed out.

Message in the dialogue box is: "Data migration failed. Please contact HP Networking Technical Support"

Any suggestions would be helpful.

Steve

Re: PCM+ 3.2 to 4.0 Upgrade

Hector Manzo — Fri, 16 Dec 2011 23:43:43 GMT

Hello Steve,

Could you post the content of the log file DbMigrationLog0.xml under folder ..\PNM\server\mysql\data and first part of the file SvrJCoreMain0.log.

Looking for any exceptions in the .xml file and looking for language variable in the SvrJCoreMain0.log file.

Sample output from xml file:

<message>Data migration failed due to unexpected runtime exception.</message>

<message>java.lang.NumberFormatException: For input string: "3,20"</message>

<frame>

<class>java.lang.NumberFormatException</class>

Sample from SvrJCoreMain0.log file:

cm_jre, sun.arch.data.model=64, user.language=en,

Thanks,
Hector

Re: PCM+ 3.2 to 4.0 Upgrade

TrondM — Fri, 23 Dec 2011 09:03:30 GMT

I am also experiencing problems when performing an upgrade from PCM+ v3.20 to PCM+ v4.0.

Error that occurs "Data migration failed. Please contact HP Support"

Please help.

Re: PCM+ 3.2 to 4.0 Upgrade

TrondM — Fri, 23 Dec 2011 09:06:57 GMT

Content of SvrJCoreMain0.log file:

2011-12-23T09:47:53 1324630073552 0 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm20To21' ... 2011-12-23T09:47:53 1324630073552 1 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm201To21' ... 2011-12-23T09:47:53 1324630073552 2 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm21To22' ... 2011-12-23T09:47:53 1324630073552 3 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm22To23' ... 2011-12-23T09:47:53 1324630073552 4 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm23To231' ... 2011-12-23T09:47:53 1324630073568 5 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm231To30' ... 2011-12-23T09:47:53 1324630073568 6 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm30To31' ... 2011-12-23T09:47:53 1324630073568 7 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm31To32' ... 2011-12-23T09:47:53 1324630073568 8 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 10 Successfully loaded migrator 'MigratorPcm32To40' ... 2011-12-23T09:47:53 1324630073677 9 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm20To21' ... 2011-12-23T09:47:53 1324630073677 10 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm201To21' ... 2011-12-23T09:47:53 1324630073677 11 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm21To22' ... 2011-12-23T09:47:53 1324630073693 12 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm22To23' ... 2011-12-23T09:47:53 1324630073693 13 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm23To231' ... 2011-12-23T09:47:53 1324630073693 14 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm231To30' ... 2011-12-23T09:47:53 1324630073693 15 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm30To31' ... 2011-12-23T09:47:53 1324630073693 16 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm31To32' ... 2011-12-23T09:47:53 1324630073693 17 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController loadIncrementMigrators 11 Successfully loaded migrator 'MigratorPcm32To40' ... 2011-12-23T09:47:53 1324630073693 18 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController migrate 11 Attempting migration from version '03.20' to version '04.00.00' ... 2011-12-23T09:47:53 1324630073693 19 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController migrate 11 Migration steps: 03.20->04.00.00 2011-12-23T09:47:53 1324630073693 20 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController$OverallProgressListener setProgress 11 [ migrator progress = 0 ] 2011-12-23T09:47:53 1324630073693 21 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController$OverallProgressListener setProgress 11 [ overall progress = 0 ] 2011-12-23T09:47:53 1324630073693 22 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController migrate 11 Begin migrating from '03.20' to '04.00.00' ... 2011-12-23T09:47:53 1324630073693 23 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController$ProxyMessageListener postMessage 11 Migrating from '03.20' to '04.00.00'. 2011-12-23T09:47:53 1324630073693 24 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController$OverallProgressListener setProgress 11 [ migrator progress = 0 ] 2011-12-23T09:47:53 1324630073693 25 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController$OverallProgressListener setProgress 11 [ overall progress = 0 ] 2011-12-23T09:47:53 1324630073755 26 com.hp.nis.migration INFO com.hp.nis.migration.MySqlUtil createConnection 11 Obtaining SQL connection to 'jdbc:mysql://localhost:3908/netmgmt' 2011-12-23T09:47:54 1324630074208 27 com.hp.nis.migration INFO com.hp.nis.migration.BaseMysqlMigrator migrate 11 Connection to database established. DB product name is 'MySQL', DB product version is '5.5.13-enterprise-commercial-advanced-log' 2011-12-23T09:47:54 1324630074255 28 com.hp.nis.migration SEVERE com.hp.nis.migration.MigrationController migrate 11 Data migration failed. Please contact HP Networking Technical Support. Reason code: UERE 2011-12-23T09:47:54 1324630074255 29 com.hp.nis.migration SEVERE com.hp.nis.migration.MigrationController migrate 11 Data migration failed due to unexpected runtime exception. java.lang.NumberFormatException: For input string: "3,20" java.lang.NumberFormatException forInputString java.lang.Integer parseInt java.lang.Integer parseInt com.hp.nis.migration.Version parseSegment 144 com.hp.nis.migration.Version <init> 41 com.hp.nis.migration.Version <init> 62 com.hp.nis.migration.BaseMysqlMigrator getSchemaVersion 596 com.hp.nis.migration.BaseMysqlMigrator migrate 271 com.hp.nis.migration.MigrationController migrate 363 com.hp.nis.migration.IaMigrationPanel$MigrationRunner run 131 java.lang.Thread run 2011-12-23T09:47:54 1324630074271 30 com.hp.nis.migration INFO com.hp.nis.migration.MigrationController migrate 11 Overall migration duration at point of failure: 578ms.

Re: PCM+ 3.2 to 4.0 Upgrade

L vd Linden — Tue, 03 Jan 2012 11:05:41 GMT

Any update on this? I am having the same issue on a relatively clean 64-bit version trial install.

Re: PCM+ 3.2 to 4.0 Upgrade

Hector Manzo — Wed, 11 Jan 2012 17:47:09 GMT

An important PCM v3 to PCM v4 migration issue has been found:

CR 108020 - PCM v3 is only supported with: English (US) Windows Installation and Windows Regional and Language Options set to English (US). Migrating from PCM v3 to PCM v4 when PCM v3 is running with a non-English (US) Windows installation orwith a Regional and Language Option set to other than English (US) will fail.

Workaround: Do not attempt to migrate at this time. HP is working on a fix that will allow a PCM v3 English (US) Windows installation with a Regional and Language Option set to other than English (US) to migrate to PCM v4 successfully.

Re: PCM+ 3.2 to 4.0 Upgrade

Hroc — Thu, 02 Feb 2012 13:22:50 GMT

when will the fix be released?

Re: PCM+ 3.2 to 4.0 Upgrade

emkay8480 — Tue, 08 May 2012 02:23:37 GMT

Hi,

I also having same problem with upgarde from ver 3.2 to 4.0.

Now PCM+ serviceses down and cant be restart at all.

I already install into another new server since existing PCM+ stop working but having problem with license activation coz my license running in old server.

I cant login the PCM Manager to uninstall the license.

Anyone please guide me.

Regards

Emkay

Re: PCM+ 3.2 to 4.0 Upgrade

Stuggi — Tue, 05 Jun 2012 06:37:31 GMT

Any updates on this? I was just getting ready to upgrade when I read this...

Re: PCM+ 3.2 to 4.0 Upgrade

Hroc — Wed, 06 Jun 2012 08:06:33 GMT

the problem seems to be fixed, at least the release notes say so

The following issues are resolved in PCM+/PCM 4.0 (04.00.00.1619):

■ CR _108020 - If Windows or locale is not English during a PCM 3.x to 4.0 upgrade, then a Data
Migration Failed error message appears, and the database becomes no longer accessible.

Re: PCM+ 3.2 to 4.0 Upgrade

Arimo — Wed, 06 Jun 2012 10:03:55 GMT

There were two situations when you might run into this problem. First of them was that you're runnign a non-English Windows, where PCM 3 isn't supported. The second option is that you're running an English OS but a non-English localization, where PCM 3 is supported.

The current installer contains fix for 108020. This will allow a successful migration when OS is English but localization is non-English. This will not allow a successful migration when OS itself is non-English. There's no way to fix that, the problem is that registry keys in English and non-English OS aren't the same.

For you people who already have run into this problem and see the "Data Migration failed" -error there is an unsupported option which may allow a successful migration:

Note down the original PCM version and Autoupdate level.
Backup the database using the Backup facility.
Install the same PCM version on a clean Windows on a supported environment.
Uninstall PCM 3 on the original server to get Uninstall IDs required for license transfer.
Go to My Networking portal and transfer the licenses to the new Install ID.
Apply the licenses to the new server.
Update to the same Autoupdate level with the original server.
Restore the database to the new server with the Restore facility.
Upgrade the new server to PCM 4.

I have to stress again: this is an untested, unsupported recovery method, so if it fails there's nothing support can do for you. Before doing it you should restore the system from previous backup before the migration.

If it fails, there's only the other option left... doing a clean PCM v4 installation, and transferring the PCM v4 licenses to the new Install ID.

Re: PCM+ 3.2 to 4.0 Upgrade

Stuggi — Wed, 06 Jun 2012 11:45:25 GMT

Okay, good to know, english (US) windows isn't a problem, we've always run English windows on every server since the dawn of time here. :)

Re: PCM+ 3.2 to 4.0 Upgrade

Stuggi — Fri, 08 Jun 2012 08:01:54 GMT

Yeah, English (US) with Swedish/Finnish localisation worked perfectly.

Re: PCM+ 3.2 to 4.0 Upgrade

Arimo — Wed, 13 Jun 2012 10:34:20 GMT

Hi Stuggi

Nice to know, thanks :-)

Re: PCM+ 3.2 to 4.0 Upgrade

Stuggi — Fri, 15 Jun 2012 05:39:02 GMT

Well, it wasn't that simple after all, now "jawaw.exe" from C:\Program Files\Hewlett-Packard\PNM\pcm-agent\jre... consumes about 99% of the CPU, which results in the server going incommunicado. Does this mean that my server is just too overloaded to cope with the increased preformance demands PCM+ v.4, or is something wrong? The server is running a whole lot of other nice to have mangement tools, so I'm thinking of migrating the PCM installation to a fresh install on a new 2008R2 server instead of the old 2003 server it's running on at the moment.