RE: [JUNK]SQL Problem after Hardware Change ?l

------_=_NextPart_001_01C7D04B.9F6C710C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,
=20
is this problem reproduceable or did it happen just once after (for =
example) a canceled command which did not clean correctly before =
finishing?
Do you use the same statistical values or do we have to assume that =
differences in join-sequence (and perhaps stopping in different steps =
because of no row found any further) may cause the difference in =
behaviour? Is any difference in explain (ok, I know, explain with =
recursive select is not very nice) to be seen?
Do you have a vtrace where the handling sequence can be seen and the =
'name' of the file found as duplicate and the statement which created =
it,
but did not drop it although this was expected to be done?
Is it possible to see that vtrace from creation of file until =
duplicate-error?
=20
  Elke
SAP Labs Berlin
=20
Sitz der Gesellschaft/Registered Office: Walldorf, Germany

Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai =
Agassi, L=E9o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, =
Peter Zencke

Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: =
Hasso Plattner

Registergericht/Commercial Register Mannheim No HRB 350269

Diese E-Mail kann Betriebs- oder Gesch=E4ftsgeheimnisse oder sonstige =
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail =
irrt=FCmlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, =
eine Vervielf=E4ltigung oder Weitergabe der E-Mail ausdr=FCcklich =
untersagt.

Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. =
Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or =
otherwise confidential information. If you have received this e-mail in =
error, you are hereby notified that any review, copying, or distribution =
of it is strictly prohibited. Please inform us immediately and destroy =
the original transmittal. Thank you for your cooperation.=20

=20


________________________________

	From: Beermann, Albert [mailto:[email protected]]=20
	Sent: Donnerstag, 26. Juli 2007 16:36
	To: [email protected]
	Subject: [JUNK]SQL Problem after Hardware Change ?l
=09
=09
	Hello Everybody !
	=20
	My application(MaxDB no SAP) connects via odbc to a SAP System with =
maxdb database(7.5.00.44) and fires the following command:
	=20
	DECLARE PUFFER CURSOR FOR WITH RECURSIVE TMPPUFFER=20
	=
(LEVEL,stlnummer,stlbezeich,stlnr,postp,posnr,matnr,matbezeich,menge,mein=
s,erskz,stlnrid) =20
	 AS (SELECT 1, ma2.matnr as stlnummer,stltextd.maktg as =
stlbezeich,stpo.stlnr,
	 stpo.postp,stpo.posnr,stpo.idnrk as matnr,matextd.maktg as =
matbezeich,stpo.menge,stpo.meins,stpo.erskz, ma1.stlnr as stlnrid=20
	 from stpo=20
	 join mast ma2 on stpo.stlnr =3D ma2.stlnr and ma2.mandt =3D '900'=20
	 join makt matextd on stpo.idnrk =3D matextd.matnr and matextd.mandt =
=3D '900' and matextd.spras =3D 'D'
	 join makt stltextd on ma2.matnr =3D stltextd.matnr and stltextd.mandt =
=3D '900' and stltextd.spras =3D 'D'
	 left join mast ma1 on stpo.idnrk =3D ma1.matnr and ma1.mandt =3D '900' =

	 where stpo.mandt =3D '900' and stpo.stlty =3D 'M' and stpo.stlnr =3D =
'00216214'
	 UNION ALL SELECT TMPPUFFER.LEVEL + 1, ma2.matnr as =
stlnummer,stltextd.maktg as stlbezeich, stpo.stlnr,
	 stpo.postp,stpo.posnr,stpo.idnrk as matnr,matextd.maktg as =
matbezeich,stpo.menge,stpo.meins,stpo.erskz,
	 ma1.stlnr as stlnrid=20
	 FROM TMPPUFFER,stpo=20
	 join mast ma2 on stpo.stlnr =3D ma2.stlnr and ma2.mandt =3D '900'=20
	 join makt matextd on stpo.idnrk =3D matextd.matnr and matextd.mandt =
=3D '900'  and matextd.spras =3D 'D'=20
	 join makt stltextd on ma2.matnr =3D stltextd.matnr and stltextd.mandt =
=3D '900' and stltextd.spras =3D 'D'
	 left join mast ma1 on stpo.idnrk =3D ma1.matnr and ma1.mandt =3D '900' =

	 where stpo.mandt =3D '900' and stpo.stlty =3D 'M' and stpo.stlnr =3D =
TMPPUFFER.stlnrid)=20
	 SELECT TMPPUFFER.* FROM TMPPUFFER=20
	 order by level,stlnr,posnr
	=20
	=20
	For more than 6 month everything works as expected.
	I use the result cursor to update spezial tables in my system.
	=20
	Now the SAP System was migrated from HP-UX on a PA-Risc Server to HP-UX =
on a Integrity Server. (Same MaxDB Version).
	SAP is running quick and fine, but my command stops with the following =
error
=09

	 1526
	Connectivity-Fehler: [SAP AG][SQLOD32 DLL][MaxDB] Base table or view =
already exists;-6000 POS(1) Duplicate table name
	[SAP AG][SQLOD32 DLL][MaxDB] Base table or view already exists;-6000 =
POS(1) Duplicate table name
	S0001
	-6000
	=20
	????????????????
	Any help welcomed
	=20

	Best regards
	________________________________________

=09

	Albert Beermann =20
	Abteilungsleiter=20
	Informationsverarbeitung=20
=09
=09
	  Piepenbrock Service GmbH + Co. KG=20
	  Hannoversche Str. 91-95=20
	  49084 Osnabr=FCck=20
	  Tel: +49 (0) 541/5841-868=20
	  Fax: +49 (0) 541/5841-869=20
	  Mobil: +49 (0) 177/9400868=20
	  E-Mail:[email protected]=20
	  www.piepenbrock.de=20
	________________________________________
=09
	Kommanditgesellschaft Sitz Osnabr=FCck HRA 6519 AG Osnabr=FCck phG: =
Piepenbrock Service Verwaltungs- und Beteiligungsgesellschaft mbH HRB =
19436 AG Osnabr=FCck Gesch=E4ftsf=FChrer: Arnulf Piepenbrock, Olaf =
Piepenbrock Paul Richter St-Nr.FA:66/204/26100 Osnabr=FCck-Stadt =
Ust.-ID-Nr.: DE 166472497 Sicherheitsnr Bauabzugssteuer: 236620320479=20
=09

	Diese eMail enth=E4lt vertrauliche und/oder rechtlich gesch=FCtzte =
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese =
eMail irrt=FCmlich erhalten haben, informieren Sie bitte sofort den =
Absender und vernichten diese eMail. Das unerlaubte Kopieren sowie die =
unbefugte Weitergabe dieser eMail ist nicht gestattet.

	=20

	=20


------_=_NextPart_001_01C7D04B.9F6C710C--