How do I get a clean default/basic install of iMC 7.3 ?

[Colorado-Bob]

We have iMC 5.2 running on MySQL on a CentOS Linux server.  We want to migrate this to a Windows server box.  We started with  support and literally got, are you sure iMC is an HPE product?  What kind of appliance is it?  etc...  Finally get to someone who could spell iMC but her procedure killed our server. 

So, we are left with a doing a clean default/basic install of MySQL and iMC on a Windows Server.  All we want is one server running both iMC and local MySQL. 

I am fairly new to iMC and MySQL.  We have an HP G7 server with Windows Server 2016 installed.  I installed MySQL 5.7 on that server which took quite a bit of config tweaking.  Finally got it installed and running.  Now we are trying to install iMC 7.3 on the Windows server 2016 w/MySQL 5.7 server .

 I got to a certain point and then it quit with an error,

"Result: failed

Fail reason: Slave deploy failed "

 I poured over logs and manuals and never found a definitive answer.  So I ran the install again.  It said it already was installed and opened up the deployment monitoring agent.  I went to the deploy tab and started at the top with the resource management and said deploy.  It quit with an error:

2018-01-17 07:09:54 [ERROR] [SwingWorker-pool-3-thread-6] [com.h3c.imc.deploy.tasks.BuildDatabaseTask$a::a(917)] Execute database script error! return value: 1. For details, see log file: C:\Windows\iMC-Reserved\log\dbresult_2018011707094810.log

2018-01-17 07:09:54 [ERROR] [Thread-29] [com.h3c.imc.deploy.dma.wizard.DeployingPanelDescriptor$c::run(347)] Task execute failed

So I follow the link and see this:

"Begin to install database and data...

    --------------------------------

Begin to create config_db foreground tables and data...

mysql: [Warning] Using a password on the command line interface can be insecure.

ERROR 1118 (42000) at line 1434: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual.

You have to change some columns to TEXT or BLOBs "

 I have been searching on how and where to make these changes in imc or mysql and have no success. I have seen similar messages, but no hints.  This message tells me essentially nothing....  What script is running to find row 1434?  What row? Is this iMC?  Is this MySQL (sounds like) ?  iMC and MySQL are supposed to run together well, why are defaults of one not accepted by the other?  Like passwords, names, now an empty default DB...

 All I need is a clean install so I can do a restore of the linux version of MySQL db’s and get imc 7.3 on the Windows server 2016 w/MySQL 5.7 server . 

Any clues, hints, do's, do nots, etc... ????

Thanks

[NeilR]

IMC is not supported on MySQL 5.7 only on 5.5 or 5.6. there is documentation covering install of both on the HPE site. I'm running 5.5 but would suggest trying 5.6 as upgrading later seems a bit questionable. Either should work.

Hopefully you are virtualizing it - much easier to handle upgrades etc, and rolling back if they don't work.

[mschrein2]

Hello Bob,

first: please note again, that neither windows 2016 nor Mysql 5.7 is supported at the moment for IMC

second: I hope you do not want to restore a dbman backup taken from IMC 5 to IMC 7.3, this is not going to work

             you can only restore a dbman backup on the exact same version and installed components of IMC, where the dbman backup       was taken from (meaning: a backup taken from IMC 5.2 can only be restored on IMC 5.2)

third: the error message you are getting during the deployment is caused by your my.ini settings (have reproduced this)

please have a look at this document, which explains what my.ini settings must be used for IMC:

https://support.hpe.com/hpesc/public/home/documentHome?docId=emr_na-c04906886&document_type=138&language_code=1871440&sp4ts.oid=5180446

[mschrein2]

Hello Bob,

this error:

ERROR 1118 (42000) at line 1434: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual.

You have to change some columns to TEXT or BLOBs "

is caused by this my.ini settings:

[mysql)

default-character-set=utf8

[mysqld|

character-set-server=utf8

to solve this, you need to:

edit my.ini (mostly located in c:/ProgramData/MySQL/MySQL Server 5.7/my.ini (but you can double check under Services =>MySQL57 => properties

set

[mysql)

default-character-set=latin1

[mysqld|

character-set-server=latin1

save, restart mysql57

after that the IMC Deployment succeeded without a Problem:

Note: please also change the following in the my.ini, before you deploy IMC

Change the parameter values under [mysql] and [mysqld]. Table 2 describes the parameters in the my.ini file.
a. Under [mysql], change the value of the default-character-set parameter to match your operating system language. This example uses latin1. If you change the character after IMC has been deployed, you must reinstall IMC.
b. Under [mysqld], make the following changes:
 Addthe parameterlower_case_table_names=1.
 Change the value of the character-set-serverparameter to latin1.
 Change the value of the innodb_buffer_pool_sizeparameter to 512M.
 Change the value of the innodb_additional_mem_pool_sizeparameter to 16M.
 Change the value of the max_allowed_packetparameter to 200M.
 Change the value of the max_connectionsparameter to 400.

[parnassus]

Just an addition: as of now (it wasn't true until very recently, but from now on it is/will be true) HPE IMC 7.3 E0605 released in late May 2018 should supports MySQL 5.7. <-- tested on CentOS 7.5 (1804) Minimal (with GUI installed after first installation and not started by default) + MySQL 5.7 installed using dedicated Yum repositories (there are caveats since MySQL 5.7 is not equal to previous versions with regards to suggested options, some are deprecated and shouldn't be customized/added at all as suggested on deployments performed with MySQL 5.6 or older versions).

Also a detailed updated guide HPE IMC 7.3 E0605 + MySQL 5.7 on Linux (CentOS or RedHat) is still not available so - in my experience - installation was not so flawless as expected even if, in the end, it was successfull.