From: Date: June 7 2005 11:06am
Subject: RE: [-9111]: System error: Move error
List-Archive: http://lists.mysql.com/maxdb/25511
Message-Id: <235EE6AC8AE9264CBF763FC6749E27010249335D@dewdfe22.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Alexei Novakov wrote:

> --- "Becker, Holger" <holger.becker@stripped> wrote:
>=20
> > Alexei Novakov wrote:
> >=20
> > > I trying out latest MaxDB version 7.5.0.26 and ran
> > > into a problem with extremely simple query:
> > >=20
> > > select T1.ENTITY_ID, T2.ENTITY_DOWN_FK
> > > from ENTITY_E T1, RELATIONSHIP_R T2
> > > where T1.ENTITY_ID =3D 3640722049958068233
> > > and T2.TYPE_FK =3D 201104
> > > and 3640722049958068233 =3D T2.ENTITY_UP_FK
> > > order by T2.ORDER_R, 1, 2
> > >=20
> > > 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.
> > >=20
> > > Any ideas?
> >=20
> > Hi,
> >=20
> > you are right it's an internal error and there is
> > more=20
> > information in the knldiag or knldiag.err about the
> > problem.
> >=20
> > Please send one of those file to the list.
> >=20
> > Kind regards
> > Holger
> >=20
>=20
> Hi,
>=20
> Yes I found corresponding message in the knldiag.err.
> Here it is:
>=20
> 2005-06-04 13:13:23      0x67C ERR 11012 MOVECODE Bad
> parameter: limit source 80 destination 80, source
> [0X7E687858]+49, destination [0X7E687858]+0, 12 bytes
> 2005-06-04 13:13:23      0x67C ERR 51080 SYSERROR
> -9111 Move error
> 2005-06-04 13:13:23      0x67C ERR 11012 MOVECODE +
> 2005-06-04 13:13:23.640 MOVECODE ERROR 11014
> 2005-06-04 13:13:23      0x67C ERR 11012 MOVECODE - =20
> Module Join_JoinOperator.cpp call index 3
> 2005-06-04 13:13:23      0x67C ERR 11012 MOVECODE Bad
> parameter: limit source 80 destination 80, source
> [0X7E687858]+49, destination [0X7E687858]+0, 12 bytes

Hi,

I was able to reproduce the bug and we'll fix it with one of=20
the next builds. For detailed information about target release see
http://www.sapdb.org/webpts?wptsdetail=3Dyes&ErrorType=3D0&ErrorID=3D1136=
011.

Thanks for reporting this bug.

Kind regards=20
Holger