Alexei Novakov wrote: > I trying out latest MaxDB version 7.5.0.26 and ran > into a problem with extremely simple query: > > select T1.ENTITY_ID, T2.ENTITY_DOWN_FK > from ENTITY_E T1, RELATIONSHIP_R T2 > where T1.ENTITY_ID = 3640722049958068233 > and T2.TYPE_FK = 201104 > and 3640722049958068233 = T2.ENTITY_UP_FK > order by T2.ORDER_R, 1, 2 > > It results: "[-9111]: System error: Move error" I > guess this is some kind of internal error. It supposed > to return 3 records in result set. It starts working > OK if I remove and of listed columns in "ORDER BY" > clause (for instance "order by T2.ORDER_R, 1" works > fine). It also works fine if I add T2.ORDER_R into > select. > > Any ideas?
Hi, you are right it's an internal error and there is more information in the knldiag or knldiag.err about the problem. Please send one of those file to the list. Kind regards Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
