Thanks, Mani. I have attached a workaround to DERBY-5371, which repairs
the database to the point that SYSCS_UTIL.SYSCS_CHECK_TABLE runs cleanly.
At this time I don't know how the SYSSTATEMENTS_INDEX2 index was
corrupted. Your service.properties looks fine to me. Perhaps there is
some bug along the upgrade trajectory you followed.
Thanks,
-Rick
On 8/5/11 7:40 AM, Mani Afschar Yazdi wrote:
sorry for the late reply, I did not receive any email. By chance I
found the bug entered in jira. The service.properties looks like this,
somethings wrong with it? I changed DB versions, as far as I remember
from 10.5 to 10.6 and than to 10.8, without modifying something here.
Might that be the cause?
#/var/derby/template
# ********************************************************************
# *** Diese Datei darf NICHT bearbeitet werden. ***
# *** BEIM ?NDERN DES DATEIINHALTS K?NNEN DATEN BESCH?DIGT WERDEN. ***
# ********************************************************************
#Thu May 06 18:56:08 CEST 2010
SysschemasIndex2Identifier=225
SyscolumnsIdentifier=144
SysconglomeratesIndex1Identifier=49
SysconglomeratesIdentifier=32
SyscolumnsIndex2Identifier=177
SysschemasIndex1Identifier=209
SysconglomeratesIndex3Identifier=81
SystablesIndex2Identifier=129
SyscolumnsIndex1Identifier=161
derby.serviceProtocol=org.apache.derby.database.Database
SysschemasIdentifier=192
derby.storage.propertiesId=16
SysconglomeratesIndex2Identifier=65
derby.serviceLocale=de_DE
SystablesIdentifier=96
SystablesIndex1Identifier=113
------------------------------------------------------------
This mail has been sent through netpilot.net webmail service
Spam protected by http://www.clean-mx.de by netpilot GmbH
------------------------------------------------------------
