Skip to Content
avatar image
Former Member

AK Duplicate catalog information

Hi,

I'am testing the MaxDB 7.6.05.09. After migrating a database from the

7.5.00.26, some stored proc doesn't execute and return an "AK Duplicate catalog information" error.

Here an extract of the diagnostic file :

2008-09-10 20:40:36 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 20:40:36 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 20:40:41 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 20:40:41 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 20:41:12 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 20:41:12 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 20:41:17 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 20:41:17 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 20:41:23 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 20:41:23 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 21:46:39 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 21:46:39 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 21:47:23 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 21:47:23 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 21:48:50 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 21:48:50 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 21:48:52 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 21:48:52 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 23:59:44 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 23:59:44 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-10 23:59:56 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-10 23:59:56 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-11 11:27:58 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-11 11:27:58 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-11 11:28:00 2405 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-11 11:28:00 2405 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

2008-09-11 14:37:47 2406 ERR 51105 AK CACHE FF0000020212002000C100020000000000000000

2008-09-11 14:37:47 2406 ERR 51080 SYSERROR -9206 AK Duplicate catalog information:F

Do you have a solution to correct this problem ?

(Have already tested to re upgrade system tables...)

greats !

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

7 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 15, 2008 at 12:41 PM

    Hallo,

    sorry for the late answer.

    Too much workload and bad luck caused the delay.

    But I got the backup. And with this we could reproduce the problem.

    So there is a good chance to find the bug and fix it.

    We will keep you informed if we will know more details.

    Elke

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 11, 2008 at 02:13 PM

    Hi Fabrice,

    does the problem persist, if you set the parameter OPTIMIZE_QUERY_REWRITE to NO ?

    You may also run a "CHECK CATALOG WITH UPDATE" to ensure catalog consistency.

    regards,

    Lars

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Lars,

      I changed the OPTIMIZE_QUERYREWRITE to NO (not permanent and on the running instance), the error was always the same

      Then i fixed NO to permanent, and stopped and started the database, tried the sp, nothing changed ;

      I reverted also the value back to OPERATOR.

      I ran the CHECK CATALOG WITH UPDATE under DBA user, and nothing changed too...

      The curious thing : i know what is the query in the sp responsible of this error. But when executing this query "alone" in SQL Studio, no problem.

      For information, this query is a dynamic query (text query that is then launched with the "execute" statement)

      Do you have an idea to solve this problem ?

  • avatar image
    Former Member
    Sep 12, 2008 at 07:49 AM

    Hallo,

    no idea, how to solve the problem, but an idea to (perhaps) get it:

    as you seem to be able to reproduce the problem, may we ask for a vtrace

    (default) and the vtrace should be stopped on err -9206.

    Both settings can be done in GUI-Tools.

    Or can you prepare a set of commands, including creation of corresponding tables,

    some data and the stored procedure in question and provide it?

    If you do not like to see it in public, a private communication could be opened for this

    special case.

    And with 7.5.xy no problem occured although nothing changed according to the DB?

    Elke

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 16, 2008 at 11:00 AM

    Hi,

    I tried to communicate on a private base to send vtrace, but the address known to the forum-master did not work. So we have to try it here.

    1. the ak-trace is not enough. Please select AKB when preparing the human-readable form.

    2. If you want to provide the vtrace, please try to send it (perhaps zip-ped)

    Elke

    Sorry for the delay because of the not-delivered mail

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Elke,

      i come back with a trace akb :

      ===== T88 ===== idnil ====================================3.702 page 4

      REQUEST: ascii, full_swap, 70600-ODB (1 segment, len: 160)

      (3.702 page 4)

      parse SEGMENT 1 (1 part, len: 160)

      internal, user_cmd

      commit_immediately

      command PART (1 argument, size: 36648)

      buf(101):

      63616C6C 2073705F 696D646F 5F676574 5F636F72 6265696C 6C655F69

      6E646963 280D3134 322C0D36 36312C0D 27272C0D 27272C0D 27272C0D

      27272C0D 27272C0D 2D312C0D 2D312C0D 322C0D3F 2C0D3F2C 0D3F2C0D

      3F2C0D3F 2C0D3F2C 0D3F2C0D 3F0D290D 0D

      'call sp_imdo_get_corbeille_indic(.142,.661,.'',.'',.'',.'',.''

      '',.-1,.-1,.2,.?,.?,.?,.?,.?,.?,.?,.?.)..'

      RECEIVE: ascii, full_swap, 70600-ODB (1 segment, len: 184)

      (5.3032 page 6)

      ok / RETURN SEGMENT 1 (2 parts, len: 184)

      pl_sql_execute_fc, sqlstate: '00000'

      shortinfo PART (8 arguments, size: 36648)

      1. pos: 1 io_len: 7 output fixed(10) optional

      2. pos: 8 io_len: 10 output fixed(15,2) optional

      3. pos: 18 io_len: 7 output fixed(10) optional

      4. pos: 25 io_len: 10 output fixed(15,2) optional

      5. pos: 35 io_len: 7 output fixed(10) optional

      6. pos: 42 io_len: 10 output fixed(15,2) optional

      7. pos: 52 io_len: 7 output fixed(10) optional

      8. pos: 59 io_len: 10 output fixed(15,2) optional

      parsid PART (1 argument, size: 36536)

      dialog_call, mess_type: delete

      buf(12):

      0038CE53 00003E02 12003C00

      REQUEST: ascii, full_swap, 70600-ODB (1 segment, len: 96)

      (5.3320 page 6)

      execute SEGMENT 1 (2 parts, len: 96)

      internal, user_cmd

      commit_immediately

      parsid PART (1 argument, size: 36648)

      dialog_call, mess_type: delete

      buf(12):

      0038CE53 00003E02 12003C00

      resultcount PART (1 argument, size: 36616)

      result_count: UNDEF

      REQUEST: ascii, full_swap, 70605-XCI (1 segment, len: 0)

      (5.3591 page 6)

      dbs SEGMENT 1 (1 part, len: 1760)

      internal, user_cmd

      scrollable on

      command PART (1 argument, size: 16296)

      buf(1700):

      ' SELECT Count(*), SUM(IMDO.IMDO_CA) FROM SA.IMPORT_DON'

      'NEE IMDO INNER JOIN SA.IMPORT_SOCIETE IMSO ON IMSO'

      • opmsg: AK CACHE FF00003E0212002000C100020000000000000000

      RECEIVE: ascii, full_swap, 70605-XCI (1 segment, len: 128)

      (8.7112 page 9)

      • -9206 / RETURN SEGMENT 1 (1 part, len: 128)

      select_fc, errpos: 1, sqlstate: 'S9206'

      errortext PART (1 argument, size: 16296)

      buf(71):

      'System error: AK Duplicate catalog information:FF00003E021200'

      '2000C10002'

      • End of the trace

      What i don't understand : there is an error when executing the stored procedure. The query that leads to an error is an dynamic sql query.

      In the sp, that is the first dynamic query executed.

      But when i execute this query alone, in SQL Studio for example, it does not produce error.

      And, when i execute this stored procedure under dmbcli, with a file that contains commands sql_connect xx,xx and sql execute call <the stored proc with parameters>, the stored proc don't produce error !!!

      Does it maybe have something to do with the "restore with initialisation" from the 7.5 backup file, with leads to the end of restoration to error ?

      Greats !

  • avatar image
    Former Member
    Sep 19, 2008 at 06:42 AM

    Hi,

    mhm, that is not what I wanted. As you already wrote: the statement / the call of this one dbproc alone does not result in that error. Therefore we do have to assume that some other statement / call before did not clean everything it should have done. And THAT (do not ask where it can be in your vtrace) we would like to see. If in case of special errors that info is left behind or if it would remain in every case or ...

    Therefore please provide the vtrace in its full length.

    Elke

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 24, 2008 at 01:48 PM

    Hi Fabrice,

    I am so sorry, but the vtrace did not help.

    It is not your fault, the used options are correct.

    But nevertheless we do not have the idea where the problem may

    result from (and why it succeeded in older releases but not in newer ones).

    Would it be possible to prepare a number of table definitions

    (or take them out of your system), few data, the stored procedure,

    and the call which (with the smaller dataset) will result in the problem

    if called for the second time and send it to us?

    Of course this data will handled confidently and thrown away as

    fast as possible.

    Or is it a small database of which you could provide a full backup and a step to step explanation how to reproduce the problem.

    Which operating system is used?

    The developers ask for this as otherwise it will be hard for both sides

    to check and find out the problem.

    And with the data/tables at hand, one can debug, check, ... much easier.

    Thank you in advance and sorry for the inconveniences.

    Elke

    BTW: I am not able to post directly to you.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 17, 2008 at 08:36 AM

    Hallo,

    fine bug you found with your use case. Now we know what happens and why this error occurs. We will fix it as soon as possible.

    To give you a chance of using your stored proc inclusive the dynamic join-select:

    add subtrans begin before your select and subtrans commit (or rollback) in the end of your stored proc. Both statements have to be static !!!

    The other chance would be to use static join-select instead of your dynamic one. But we assume that you have good reason to do it as you do it and therefore this is no opportunity for you.

    Good luck,

    Elke

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      ok ! bug found ; many thanks for the given solution while waiting for the next release !

      it works well with a sub transastion

      Greats !