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

[Elke Zietlow]

Hello,
 
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?
 
  Elke
SAP Labs Berlin
 
Sitz der Gesellschaft/Registered Office: Walldorf, Germany

Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo
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äftsgeheimnisse oder sonstige vertrauliche
Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist
Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der
E-Mail ausdrücklich 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. 

 


________________________________

	From: Beermann, Albert [mailto:A.Beermann@stripped] 
	Sent: Donnerstag, 26. Juli 2007 16:36
	To: maxdb@stripped
	Subject: [JUNK]SQL Problem after Hardware Change ?l
	
	
	Hello Everybody !
	 
	My application(MaxDB no SAP) connects via odbc to a SAP System with maxdb
database(7.5.00.44) and fires the following command:
	 
	DECLARE PUFFER CURSOR FOR WITH RECURSIVE TMPPUFFER 
	(LEVEL,stlnummer,stlbezeich,stlnr,postp,posnr,matnr,matbezeich,menge,meins,erskz,stlnrid)
 
	 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 
	 from stpo 
	 join mast ma2 on stpo.stlnr = ma2.stlnr and ma2.mandt = '900' 
	 join makt matextd on stpo.idnrk = matextd.matnr and matextd.mandt = '900' and
matextd.spras = 'D'
	 join makt stltextd on ma2.matnr = stltextd.matnr and stltextd.mandt = '900' and
stltextd.spras = 'D'
	 left join mast ma1 on stpo.idnrk = ma1.matnr and ma1.mandt = '900' 
	 where stpo.mandt = '900' and stpo.stlty = 'M' and stpo.stlnr = '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 
	 FROM TMPPUFFER,stpo 
	 join mast ma2 on stpo.stlnr = ma2.stlnr and ma2.mandt = '900' 
	 join makt matextd on stpo.idnrk = matextd.matnr and matextd.mandt = '900'  and
matextd.spras = 'D' 
	 join makt stltextd on ma2.matnr = stltextd.matnr and stltextd.mandt = '900' and
stltextd.spras = 'D'
	 left join mast ma1 on stpo.idnrk = ma1.matnr and ma1.mandt = '900' 
	 where stpo.mandt = '900' and stpo.stlty = 'M' and stpo.stlnr = TMPPUFFER.stlnrid) 
	 SELECT TMPPUFFER.* FROM TMPPUFFER 
	 order by level,stlnr,posnr
	 
	 
	For more than 6 month everything works as expected.
	I use the result cursor to update spezial tables in my system.
	 
	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
	

	 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
	 
	????????????????
	Any help welcomed
	 

	Best regards
	________________________________________

	

	Albert Beermann  
	Abteilungsleiter 
	Informationsverarbeitung 
	
	
	  Piepenbrock Service GmbH + Co. KG 
	  Hannoversche Str. 91-95 
	  49084 Osnabrück 
	  Tel: [phone] 
	  Fax: [phone] 
	  Mobil: +49 (0) 177/9400868 
	  E-Mail:A.Beermann@stripped 
	  www.piepenbrock.de 
	________________________________________
	
	Kommanditgesellschaft Sitz Osnabrück HRA 6519 AG Osnabrück phG: Piepenbrock
Service Verwaltungs- und Beteiligungsgesellschaft mbH HRB 19436 AG Osnabrück
Geschäftsführer: Arnulf Piepenbrock, Olaf Piepenbrock Paul Richter
St-Nr.FA:66/204/26100 Osnabrück-Stadt Ust.-ID-Nr.: DE 166472497 Sicherheitsnr
Bauabzugssteuer: 236620320479 
	

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