Hi Peter,

"H�bschen, Peter" [mailto:[EMAIL PROTECTED] wrote:

> Subject: Bug in loadercli ???
>       
> I'm using SAPDB 7.4.3.25 on a Redhat 9 box and I'm stumbled 
> into a strange
> problem. So I don't know if this is a bug or I did something wrong.
> Here is my situation:
> My commandfile for loadercli is very simple (I'm using it for test
> purposes):
> dataextract for dataload  table tbl_staffelteil
>         outfile 'Anfrage2.control'
>         outfile 'Anfrage2.data'
> 
> I'm starting the loadercli through
> loadercli -d <mydb> -u pehu,<password> -b <commandfile>.
> 

<snipped strange and real table definition>

> After I found this strange behaviour I looked again and found 
> out that user
> pehu (member of usergroup ALLUSERS and <> DBA) has a table called
> TBL_STAFFELTEIL and that my DBA-Account has such a table 
> (it's an older
> version with a different primary key). So loadercli is going 
> to mix them
> together. Since I don't know if this is the desired execution from
> loadercli, I can't say it's a bug. But I would prefer, if I 
> have access to 2
> tables with identical names and I want to export them through 
> the loader,
> that I get an error like 'The tablename <X> is ambiguous. 
> Please use the
> complete name' or something like that.
> 
This can't be the desired behavior, can it? But I need another day to
reproduce it here (if ever ;-) ) because the newest development version
doesn't show this behavior.
In the meanwhile would you mind to check if your loader system table
TRANSFORMATIONMODEL is empty and if not delete all rows? That doesn't
any harm to your db! After that could you run again the DATAEXTRACT
statement and see if you get the same result? And of course I would
be really interested in the result.

Thx and sorry for any inconvenience.
Regards,
 Steffen
-- 
Steffen Schildberg
SAP DB Team
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to