Deleting records through a view from datastage version 4.2

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Deleting records through a view from datastage version 4.2

Post by admin »

Hi,
I am having datastage version 4.1 on development and vers
ion 4.2 on production.I have a job which deletes the records from a view which is based on 2 tables.The job is working fine on Version 4.1 ie it is deleting the records from the view.The same job if I execute it on version 4.2 it is not deleting the records from the view.There is no error also. Can anybody help me in knowing the reason?

Regds
Tina.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

You havent mentioned what sort of stage you are using to access the view? Is it ORAOCI8?

If it is be aware that by default, DataStage 4.1 comes with ORAOCI8 version 2.3, where as DataStage 4.1 comes with ORAOCI8 version 3. There are some significant differences (and bugs) between these, especially in relation to bind variables on lookups and deletes.

Mostly these give errors but I have suspicions about one instance where it does not. However, I need more information before I can comment on your situation.

Cheers,

David

-----Original Message-----
From: derick j JOSE [mailto:datastage@rediffmail.com]
Sent: Wednesday, 10 October 2001 3:28 PM
To: datastage-users@oliver.com
Subject: Deleting records through a view from datastage version 4.2


Hi,
I am having datastage version 4.1 on development and vers
ion 4.2 on production.I have a job which deletes the records from a view which is based on 2 tables.The job is working fine on Version 4.1 ie it is deleting the records from the view.The same job if I execute it on version 4.2 it is not deleting the records from the view.There is no error also. Can anybody help me in knowing the reason?

Regds
Tina.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

Hi,
Thanks for the fast reply.The stage ORAOCI8 ver 3.0

Regds
Tina.

On Wed, 10 Oct 2001 David Barham wrote :
> You havent mentioned what sort of stage you are using
> to access the view?
> Is it ORAOCI8?
>
> If it is be aware that by default, DataStage 4.1 comes
> with ORAOCI8 version
> 2.3, where as DataStage 4.1 comes with ORAOCI8 version
> 3. There are some
> significant differences (and bugs) between these,
> especially in relation to
> bind variables on lookups and deletes.
>
> Mostly these give errors but I have suspicions about
> one instance where it
> does not. However, I need more information before I
> can comment on your
> situation.
>
> Cheers,
>
> David
>
> -----Original Message-----
> From: derick j JOSE [mailto:datastage@rediffmail.com]
> Sent: Wednesday, 10 October 2001 3:28 PM
> To: datastage-users@oliver.com
> Subject: Deleting records through a view from datastage
> version 4.2
>
>
> Hi,
> I am having datastage version 4.1 on development and
> vers
> ion 4.2 on production.I have a job which deletes the
> records from a view
> which is based on 2 tables.The job is working fine on
> Version 4.1 ie it is
> deleting the records from the view.The same job if I
> execute it on version
> 4.2 it is not deleting the records from the view.There
> is no error also.
> Can anybody help me in knowing the reason?
>
> Regds
> Tina.
>
>
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

In version 3, Ascential changed the way bind variables are labelled for lookups and deletes. In version 2.3 and earlier, the bind variables were numbered relative to the key columns. In version 3, they are numbered relative to all columns. Unfortunately, the changes were not fully implemented necessitating a bug fix.

OK, a few things to do or try.

1. Get the latest patch of the ORAOCI8 version 3 plugin (its a little messy to install, but basically just copy the files in and restart the services on the server - I dont suggest you de-register or re-register the plugin). There are also some new DLLs for the client. 2. Alternatively, deinstall version 3 and go back to version 2.3. Ascential have suggested this to some customers. I havent resorted to this yet as my problems have generally been solved with the following suggestion. 3. However, the first thing I would try (as it is the easiest) is: for all lookups and deletes, make sure the key columns are the first columns.


There are a few other gotchas but well leave those for when you find them.

-----Original Message-----
From: derick j JOSE [mailto:datastage@rediffmail.com]
Sent: Wednesday, 10 October 2001 4:24 PM
To: datastage-users@oliver.com
Subject: Re: RE: Deleting records through a view from datastage version 4.2


Hi,
Thanks for the fast reply.The stage ORAOCI8 ver 3.0

Regds
Tina.

On Wed, 10 Oct 2001 David Barham wrote :
> You havent mentioned what sort of stage you are using
> to access the view?
> Is it ORAOCI8?
>
> If it is be aware that by default, DataStage 4.1 comes
> with ORAOCI8 version
> 2.3, where as DataStage 4.1 comes with ORAOCI8 version
> 3. There are some
> significant differences (and bugs) between these,
> especially in relation to
> bind variables on lookups and deletes.
>
> Mostly these give errors but I have suspicions about
> one instance where it
> does not. However, I need more information before I
> can comment on your
> situation.
>
> Cheers,
>
> David
>
> -----Original Message-----
> From: derick j JOSE [mailto:datastage@rediffmail.com]
> Sent: Wednesday, 10 October 2001 3:28 PM
> To: datastage-users@oliver.com
> Subject: Deleting records through a view from datastage version 4.2
>
>
> Hi,
> I am having datastage version 4.1 on development and
> vers
> ion 4.2 on production.I have a job which deletes the
> records from a view
> which is based on 2 tables.The job is working fine on
> Version 4.1 ie it is
> deleting the records from the view.The same job if I
> execute it on version
> 4.2 it is not deleting the records from the view.There
> is no error also.
> Can anybody help me in knowing the reason?
>
> Regds
> Tina.
>
>
Locked