On 9/3/2010 9:44 AM, Michael Seibold wrote:
> Hi DJ,
>
> I will dig into this deeper next week together with our DB guru. Your hint
> about indices ...
>
> backup db
> drop database
> install -dis
> backup db
> restore only data from first backup
>
> ... there are quite a few foreign key constraint error messages and the
> tables / indices are not the same as before. The database is quite "old",
> having seen several OpenNMS version from about 1.5.90. Somewhere during the
> different upgrades there must have been problems creating new indices. I will
> write you as soon as I know more, maybe this is an issue of the upgrade
> process.
If you find a procedure that works for this, please post it if you don't
mind. I have a system running a 1.7.7 version where the db update to
1.8.x doesn't work. I wouldn't mind losing the event/outage history but
I want to at least keep the node numbering intact for the links to the
jrbs and and ksc definitions.
--
Les Mikesell
[email protected]
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
