Bug #8016 General error;-9404 POS(1) System error: AK System error: VAK724 1
Submitted: 19 Jan 2005 18:13 Modified: 5 May 2005 7:45
Reporter: Chris Wall Email Updates:
Status: No Feedback Impact on me:
None 
Category:MaxDB Severity:S2 (Serious)
Version:7.5.0.23 OS:Linux (Linux)
Assigned to: Assigned Account CPU Architecture:Any

[19 Jan 2005 18:13] Chris Wall
Description:
The execution of a select statment yeilds the following error.

General error;-9404 POS(1) System error: AK System error: VAK724 1

This problem does not occur in version 7.5.0.18
I found this problem with version 7.5.0.23
I haven't tested it on version 7.5.0.19

How to repeat:
select movement.* from movement ,movement_order where movement_order.order_id = '1005000' and movement.id = movement_order.movement_id and movement_order.company_id = 'TMS'

yields General error;-9404 POS(1) System error: AK System error: VAK724 1

If movement_order.* is added then the statement executes succesfully

select movement.*, movement_order.* from movement ,movement_order where movement_order.order_id = '1005000' and movement.id = movement_order.movement_id and movement_order.company_id = 'TMS'

The explain statement from the previous select statement.

LME  MOVEMENT_ORDER  X_MOO_ORDER_MOVE  RANGE CONDITION FOR INDEX                       69
                     ORDER_ID               (USED INDEX COLUMN)                
LME  MOVEMENT        ID                JOIN VIA KEY RANGE                             410
                                            NO TEMPORARY RESULTS CREATED       
                                            RESULT IS COPIED   , COSTVALUE IS           3

Removing the and movement_order.company_id = 'TMS' fixes the problem.

select movement.* from movement ,movement_order where movement_order.order_id = '1005000' and movement.id = movement_order.movement_id

LME  MOVEMENT_ORDER  X_MOO_ORDER_MOVE  RANGE CONDITION FOR INDEX                       69
                                       ONLY INDEX ACCESSED                     
                     ORDER_ID               (USED INDEX COLUMN)                
LME  MOVEMENT        ID                JOIN VIA KEY RANGE                             410
                                            NO TEMPORARY RESULTS CREATED       
                                            RESULT IS COPIED   , COSTVALUE IS           2

Changing movement_order.company_id <> '1' to a not equal to yeilds succesful execution yet incorrect data obviously.

select movement.* from movement ,movement_order where movement_order.order_id = '1005000' and movement.id = movement_order.movement_id and movement_order.company_id <> '1'

LME  MOVEMENT_ORDER  X_MOO_ORDER_MOVE  RANGE CONDITION FOR INDEX                       69
                                       ONLY INDEX ACCESSED                     
                     ORDER_ID               (USED INDEX COLUMN)                
LME  MOVEMENT        ID                JOIN VIA KEY RANGE                             410
                                            NO TEMPORARY RESULTS CREATED       
                                            RESULT IS COPIED   , COSTVALUE IS           2
[24 Jan 2005 14:59] Ulf Wendel
Welcome back Chris!

Chris, do I already have all the neccessary data (SQL schema + sample data) to reproduce the problem, is it contained in one of your previous bug reports? If not, please provide me with it so that I can verify the problem. Please use the "Files" tab to upload the schema and some sample data. 

Thanks & Best regards!
Ulf Wendel
[24 Jan 2005 20:11] Chris Wall
movement table data

Attachment: movement.unl (application/octet-stream, text), 1.51 KiB.

[24 Jan 2005 20:13] Chris Wall
movement order table data

Attachment: movement_order.unl (application/octet-stream, text), 5.81 KiB.

[24 Jan 2005 20:27] Chris Wall
Ulf it is good to hear from you!

I has version 18 stable and meeting all of my needs so the databse problems got put on the back burner.  I finally have some time to dedicated to helping you fix the problems.  Let me know if you need anything else.  Thanks a million!

I put the schema, and the data for both tables up under the files.  The don't know if the data is in the "best" format for you.  If you can't get to it let me know how you would like for me to extract it and give it to you.

I simplified the data as much as I could and still reproduce the problem.  As it turns out there has to be 102 entries or more in the movement_order table or the problem does not occur.  The data I provided has exactly 102 entries in the movement_order table and three in the movement table.  Below is a select statement that applies to the data that I provided.

select movement.* from movement ,movement_order where movement_order.order_id =
'1001808' and movement.id = movement_order.movement_id and
movement_order.company_id = 'TMS'
[25 Feb 2005 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[25 Feb 2005 10:07] Aleksey Kishkin
Sorry this bug report was wrongly closed as 'no feedback' despite the fact user posted required info. Reopened.
[5 Apr 2005 7:45] Ulf Wendel
Hi Chris,

I'm unfamiliar with the format of the data files you've provided. Could you give me a hint how to load the data?

Best regards,
Ulf
[5 May 2005 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".