I have a backup from a 220.127.116.1100-2 machine.
I prepared another machine and configured it the same as the original (IP's username/password, security password)
I am able to restore the backup and everything seems OK, but I can not do any upgrade anymore.
The upgrade starts correctly and then ends with this:
(10747) Fri Mar 18 12:46:01 EET 2011
Publisher: Starting installdb... /bin/su -l informix -s /bin/sh -c "source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; nice /usr/local/cm/bin/installdb -x /usr/local/cm/db/xml/xml"
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installdb Failure [-x] 1
(10747) Fri Mar 18 12:46:49 EET 2011
ERROR: Final installdb run unsuccessful
What could this be?
The original machine is an IBM, and the target machine is a HP, but that should not cause any problems I think.
What is happening is the following.
I have a backup from a customer running 18.104.22.16800-2
I installed in my lab the same version and then try to upgrade to 22.214.171.12400-12
When I install 126.96.36.19900-2 on my server, and then do an upgrade to 188.8.131.5200-12 everything works fine.
When I install 184.108.40.20600-2 on my server, restore the backup from customer (no errors) and then I try to upgrade it fails.
Before you can upgrade from 220.127.116.1100-2 to 18.104.22.16800-12 you have to install 'ciscocm.513e_upgrade.cop.sgn' because of a bug.
I can install 'ciscocm.513e_upgrade.cop.sgn' on my system running 22.214.171.12400-2 without error's
When I have restored the backup from customer and then I want to install 'ciscocm.513e_upgrade.cop.sgn' I receive the same error.
Untarring and a lot of things go well untill the staement mentioned in my first message.
I really would like to know why this is.
Looking in the DB log files I see this error:
/21/2011 11:04:02.782 installdb|-->DBXMLParser::initParser() |
03/21/2011 11:04:02.782 installdb|<--DBXMLParser::initParser() |
03/21/2011 11:04:02.783 installdb|-->DBXMLParser::parse() |
03/21/2011 11:04:02.836 installdb|-->DOMErrorReporter::fatalError |
03/21/2011 11:04:02.836 installdb| DOMErrorReporter::fatalError *ERROR* Fatal Error at file , line 0, column 0
message: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/usr/local/cm/db/xml/xml/c72xx_display_instance-t1_cas.xml|
03/21/2011 11:04:02.836 installdb|<--DOMErrorReporter::fatalError |
03/21/2011 11:04:02.836 installdb| DBXMLParser::parse() Errors occurred, no output available|
03/21/2011 11:04:02.836 installdb|<--DBXMLParser::parse() |
03/21/2011 11:04:02.836 installdb| CDBInstall::BuildDisplayInstanceRuleMap() *ERROR* getting error while parsing: /usr/local/cm/db/xml/xml/c72xx_display_instance-t1_cas.xml|
03/21/2011 11:04:02.839 installdb|<--CDBInstall::BuildDisplayInstanceRuleMap() |
03/21/2011 11:04:02.839 installdb| CDBInstall::InstallXML() after BuildDisplayInstanceRuleMap, rv is |
03/21/2011 11:04:02.839 installdb|<--CDBInstall::InstallXML() |
03/21/2011 11:04:02.839 installdb|-->CDBInstall::~CDBInstall() |
03/21/2011 11:04:02.839 installdb|<--CDBInstall::~CDBInstall() |
03/21/2011 11:04:02.839 installdb|<--xmlinstall |
03/21/2011 11:04:02.843 installdb|<--main |
03/21/2011 11:04:02.843 installdb|-->SDIControl::~SDIControl() |
03/21/2011 11:04:02.843 installdb|<--SDIControl::~SDIControl() |
03/21/2011 11:04:02.843 installdb|-->SDIControlBase::~SDIControlBase |
03/21/2011 11:04:02.843 installdb|<--SDIControlBase::TimerThread |
03/21/2011 11:04:02.843 installdb|<--SDIControlLayer::pollThread(30f0bb0) |
This is regardless if I install a Locale, or a firmware
What is this?
The issue was that on an older version of 5.x some files were there like (/usr/local/cm/db/xml/xml/c72xx_display_instance-t1_cas.xml)
When you install from scratch version 5.2.x these files are not there anymore.
When you then restore the data and want to do an upgrade you get conflicts.
With TAC we copied around 5 xml files from the old server to the new 5.2 server, and the upgrade went OK.
Meanwhile, good luck in finding a suitable devicepack for your dusty x.y(z) CUCM version.
I had this same error when attempting to install firmware cop files.