CA Spectrum OneClick Console Version 9.3.0.1.82 After hours of "fog" In-place upgrade from 9.2.0.04.24 to 09.02.03.H12 to 9.3 to 9.3.0.1.82 Hours spend on debugging of encoding settings, different approaches, multiple restores. "Thank the lord we run on Linux"
Lot to say, but in the end the cause of the issues are related to in my opinion a possible fault in the installation manual. Maybe specific to our situation, I don't know Manual says; Page 63 Migrate and Upgrade on Linux and Solaris 3. Preserve the existing SpectroSERVER database (see page 48). Important! When backing up the SpectroSERVER database for migration, include both the modeling catalog and the models. A catalog-only or models-only migration is not supported. On page 48, only a online backup is explained, which always include the catalog I have done multiple upgrade attempts, with manual and online backups, all fail at the ISO-8859-1 to UTF-8 encoding when installing IN-PLACE upgrade to 9.3. Not needed because we had UTF8, but no option to select All went smooth, as soon we did the IN-PLACE upgrade from 09.02.03.H12 to 9.3 with only a SS dbsave with models only, not the catalog. In contrary of the installation manual Quit important to make a dbsave after the migration, due to the change of DB consistency check in SS start Next step, get in contact with our global purchase department, because we had NOC license, and now startup says device limit. Will need another device based license key Regards Erwin. ( Tnx Alexander Garkusha to support in debug and analysing !!!) _____________________________________________ From: De Munter, Erwin Sent: Wednesday, March 05, 2014 4:13 PM To: 'spectrum' Cc: RG BE gitv Subject: RE2: [spectrum] upgrade v9.3 linux database conversion issue Colleague pointed me to https://communities.ca.com/ru/web/ca-ehealth-and-ca-spectrum-global-user-community/message-board/-/message_boards/message/107037218?&; With relevant information, and approach to import database with different version, into 9.3. first import and SS start successful, but now issue with corba naming service, to debug as next step _____________________________________________ From: De Munter, Erwin Sent: Wednesday, March 05, 2014 1:54 PM To: spectrum Cc: RG BE gitv Subject: [spectrum] upgrade v9.3 linux database conversion issue In 12 years of Spectrum mngnt, never had big issues with Spectrum installs or upgrade, until now Anyone facing this problem or has idea to solve ? 1) Linux Spectrum instance upgrade with in-place db conversion running version 9.2.0.04.24 to 09.02.03.H12 succeeded 2) Created new DB save from version 09.02.03.H12 for an in-place upgrade to 9.3.0 Based on the Install manual of 9.3 the prerequisites are Note: To upgrade from CA Spectrum 9.1 or an earlier version, you must be at CA Spectrum 9.2.0 or later before starting the upgrade to Release 9.2 H04. And then you can upgrade again, to Release 9.3. Previous in-place with DB conversion went smooth As far my knowledge 09.02.03.H12 is a higher version then 9.2 H04 ? ( 9.2 H04 is in my interpretation 9.2.0.4 ) ? 3) Upgrade process to 9.3.0 runs smooth, until the final end, in the post-install where the installation does a ISO-8859-1 to UTF-8 encoding conversion. Based on my knowledge our database was in UTF-8, but UTF cannot be selected from the installation GUI. Install manual says select ISO-8859-1 when no non-std encoding was used. OC, System local are all in UTF-8 . So I don't really understand why the installation process is doing the conversion. And why it fails every time. ( 4 attempts / rollback restores with detail respect of order and best practices in upgrade process ) POST- Installation log, where it fails Stamping database version into SpectroSERVER database Current database version is 9.3.0.0 Database version has been changed from 9.3.0.0 to 9.3.0.000 Backing up catalog to db_20140305,2.after.SSdb Converting SSdb to UTF-8 from ISO-8859-1 Install-Tools/postinst_engine: line 1335: 6520 Segmentation fault SSdbload -UpgradeFrom $SOURCE_ENCODING $DB_SAVE_PRE_CONVERSION > $LOGDIR/UpgradeFrom.$TIME 2>&1 ** Error during database conversion to utf8 from ISO-8859-1 If looking in the Pre-install phase, existing database seems to picked up like it should Renaming the dbsavefile.SSdb to dbsavefile.1030_0305.SSdb, because there is an existing SpectroSERVER database in /spectrum/SS. We will upgrade/update the existing SpectroSERVER database. ---------------------------------------------------------------------- Starting pre-installation Install module Install-Tools/IPRE/PreInstall.pl Any idea welcome --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
