Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Upgrade the hq server database is ending up with ERROR message

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.2.0.5
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    Mysql 5.1.x on MacOSX
  • Case Links:
    none
  • Regression:
    No

Description

Anytime time the upgrade option is selected when running the installer and MySQL is on MacOSX the install fails.

1.Installed the AMS 2.0.0-SR04(cServer-6.0.20.B-GA-linux32.tgz) on Redhat 5 linux(32bit)with a new db on macosx(mysql Ver 14.14 Distrib 5.1.44, for apple-darwin10.2.0 (i386))
2.Tried to upgrade the installed to AMS to HQ(hyperic-hq-installer-noJRE-tc-server-2.0.0.M5.tar.gz) by selecting the upgrade option

After i run the setup.sh i am getting the following error message.

Choices:
1: Upgrade the HQ server database
2: Overwrite the HQ server database (ERASE all existing data)
3: Exit the installer
An HQ server database already exists at the JDBC connection URL.
What should be done with this database? [default '3']:
1
Loading install configuration...
Install configuration loaded.
Preparing to install...
Validating server install configuration...
Checking server webapp port...
Checking server secure webapp port...
Checking server JRMP port...
Checking server JNP port...
Checking database permissions...
Validating server DB configuration...
Installing the server...
Unpacking server to: /opt/rmadala/server-4.2.0.5-EE...
Creating server configuration files...
Copying binaries and libraries to server installation...
Copying server configuration file...
Copying server control file...
Copying server binaries...
Copying server db-upgrade files...
Copying server libs...
Setting up server database...
Upgrading database...
--------------------------------------------------------------------------------
An ERROR occurred, the installation cannot continue.
FATAL EXCEPTION at /opt/hyperic-hq-installer-noJRE-tc-
server-2.0.0.CI-39/installer-4.2.0.5-EE/data/setup.xml:434: : The
following error occurred while executing this line:
/opt/hyperic-hq-installer-noJRE-tc-server-2.0.0.CI-39/
installer-4.2.0.5-EE/data/setup.xml:440: The following error
occurred while executing this line:
/opt/hyperic-hq-installer-noJRE-tc-server-2.0.0.CI-39/
installer-4.2.0.5-EE/data/setup.xml:580: The following error
occurred while executing this line:
/opt/hyperic-hq-installer-noJRE-tc-server-2.0.0.CI-39/
installer-4.2.0.5-EE/data/setup-db-MySQL.xml:21: The following error
occurred while executing this line:
/opt/hyperic-hq-installer-noJRE-tc-server-2.0.0.CI-39/
installer-4.2.0.5-EE/data/setup-db-common.xml:95: The following
error occurred while executing this line:
/opt/hyperic-hq-installer-noJRE-tc-server-2.0.0.CI-39/
installer-4.2.0.5-EE/data/db-upgrade.xml:42: DBUpgrader: Error
running SchemaSpec: 3.131: Error running SchemaSpecTask:
org.hyperic.tools.ant.dbupgrade.SST_AlterColumn: Error retrieving pg
columntype from table, QRTZ_FIRED_TRIGGERS column, PRIORITY

Attaching hq-install.log.verbose for reference.

Activity

Hide
Radhika Madala added a comment -

When i run the following query i am getting the empty result set.

mysql> select table_name, column_name,data_type, column_type, character_maximum_length,
-> column_type, numeric_precision, numeric_scale
-> FROM information_schema.columns
-> WHERE lower(table_name) = 'qrtz_triggers'
-> AND lower(column_name) = 'priority';
Empty set (0.00 sec)

Show
Radhika Madala added a comment - When i run the following query i am getting the empty result set. mysql> select table_name, column_name,data_type, column_type, character_maximum_length, -> column_type, numeric_precision, numeric_scale -> FROM information_schema.columns -> WHERE lower(table_name) = 'qrtz_triggers' -> AND lower(column_name) = 'priority'; Empty set (0.00 sec)
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks ago