HELP! After Restore of MAXDB 7.6.06.03 I get sql error duplicate secondary key

[christoph_schwerdtner2]

HELP! After Restore of MAXDB 7.6.06.03 I get sql error duplicate secondary key and the database can't go ONLINE.

I tried to restore a complete backup with initialization. When the restore is finished and I click on Restart the error comes up.

Is there a chance to fix that error? I dont have access to an older backup right now.

EDIT: The error log says this:

2014-05-27 05:36:54      0x308 ERR     5 Catalog  Catalog update failed,IFR_ERROR=250,DESCRIPTION=POS(1) Duplicate secondary key:INDEX001

2014-05-27 05:36:55                               ___ Stopping GMT 2014-05-27 03:36:55           7.6.06   Build 003-123-202-135

I also tried to switch AUTO_RECREATE_BAD_INDEXES from NO to YES but no difference. Any ideas?

[christoph_schwerdtner2]

The error seems to be an old one - I tried to use a backup from last week, error is the same. At this time this is the oldest backup.

I used the Initialize command to read the parameters of the new database from the backup medium.

The verbose database message log says this:

Thread  0x908 Task     69  2014-05-27 05:48:23     Admin      20039:  Kernel state: 'REDO LOG' finished

Thread  0x908 Task     69  2014-05-27 05:48:23     OBJECT     54000:  C:\Programme\sdb\QMED\pgm\liboms

Thread  0x908 Task     69  2014-05-27 05:48:23 ERR Catalog        5:  Catalog update failed,DESCRIPTION=POS(1) Duplicate secondary key:INDEX001,IFR_ERROR=250,_FILE=Catalog_AuthorizationObject.cpp,_LINE=1017

                                                                      DESCRIPTION:

                                                                      Catalog update failed

Thread  0x908 Task     69  2014-05-27 05:48:23     Admin          3:  Database state: OFFLINE

Thread  0x908 Task     69  2014-05-27 05:48:23     CONNECT    19651:  Connection released, T69

Thread  0x908 Task     69  2014-05-27 05:48:23     DBSTATE    19620:  Shutdown normal requested

Thread  0x1CC Task      3  2014-05-27 05:48:23     Trace      20000:  Start flush kernel trace

Thread  0x1D1 Task      -  2014-05-27 05:48:23     TASKING    19684:  Tracewriter termination timeout: 1200 sec

Thread  0x1CC Task      3  2014-05-27 05:48:23     VOLUMEIO   19617:  Single I/O attach, 'knltrace', UKT:1

Thread  0x1CC Task      3  2014-05-27 05:48:24     Trace      20001:  Stop flush kernel trace

Thread  0x1CC Task      3  2014-05-27 05:48:24     TASKING    19619:  Releasing tracewriter

Thread  0x1D1 Task      -  2014-05-27 05:48:24     VERSION    19600:  'Kernel    7.6.06   Build 003-123-202-135'

Thread  0x1D1 Task      -  2014-05-27 05:48:24     DBSTATE    19654:  SERVERDB 'QMED' has stopped