DSXchange

This is a topic for an orphaned message.

Your syntax is incorrect. You still need the target column name where you have the sequence.nextval, and it goes down where you have :1. -craig "Wilcy William" 07/24/2003 08:43 AM Please respond to To datastage-users@oliver.com cc Subject Re: RE: RE: Sequence generator This is the exact statement us...

I have used user defined SQL With regards, Wilcy On Thu, 24 Jul 2003 Ian Godsell wrote : >It needs to be in user defined SQL. > >-----Original Message----- > From: Wilcy William [mailto:wilcy@rediffmail.com] >Sent: 24 July 2003 01:20 >To: datastage-users@oliver.com >Subject: Re: RE: Sequence generat...

This is the exact statement used. INSERT INTO INT_ERROR_DETAILS (SEQ_ERROR_TABLE.nextval ,BUSINESS_UT_ID,APPLICATION_TY,JOB_NM,ERROR_CD,ERROR_DE,ERROR_SOURCE,ERROR_DATA,PROCESS_IN,CREATE_UI,CREATE_TS,UPDATE_UI,UPDATE_TS) VALUES (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,TO_DATE(:11, YYYY-MM-DD HH24:MI:SS),:12,...

It needs to be in user defined SQL. -----Original Message----- From: Wilcy William [mailto:wilcy@rediffmail.com] Sent: 24 July 2003 01:20 To: datastage-users@oliver.com Subject: Re: RE: Sequence generator I put the sequence in the OCI that I am using to insert and encountered the following Oracle er...

Wilcy Sure you can but you would have to update it every record and read it in one routine. This becomes the single threaded bottleneck. An Oracle sequence would be faster but it does basically the same thing. If you are not worried about gaps in the numbers then I thought about calling the routine ...

I put the sequence in the OCI that I am using to insert and encountered the following Oracle error. : ORA-02287: sequence number not allowed here With regards, Wilcy On Wed, 23 Jul 2003 Ian Godsell wrote : >I assume that you are using this as a lookup and need to use the >returned >value in more tha...

You CAN store it in a hashed file. Read dskcache.pdf (in the DataStage manuals) for information about sharing hashed files between jobs. ----- Original Message ----- From: "Wilcy William" Date: 24 Jul 2003 00:10:04 -0000 To: datastage-users@oliver.com Subject: Re: RE: Re: Re: Sequence generator > Al...

Can you post the exact custom INSERT statement you are using? -----Original Message----- From: Wilcy William [mailto:wilcy@rediffmail.com] Sent: Thursday, 24 July 2003 10:16 AM To: datastage-users@oliver.com Subject: Re: RE: Sequence generator I tried Point 5 and encounter the following error. : ORA...

I tried Point 5 and encounter the following error. : ORA-02287: sequence number not allowed here With regards, Wilcy On Wed, 23 Jul 2003 David Barham wrote : >1. What is the network speed between the DataStage server and the >Oracle >server? I have found that increasing the network speed from >100Mb...

All the jobs are running in parallel and all require the sequence number. So I cannot store it in a hash file. On Wed, 23 Jul 2003 Kim Duke wrote : >Wilcy > >You do not need to store it between runs. Just select max(Key) > from >TargetTable; into a hash file at the start of the job or in a job >befo...

This is a topic for an orphaned message.

Because youre likely to be using parallel streams to load the target, its probably a good idea to use the NEXTVAL method of a sequence, or SERIAL data type, in the target database. You might investigate the Column Generator stage, editing the column metadata to specify how to generate values for the...

This is a topic for an orphaned message.

Since you are likely to be loading the table in parallel, probably the best way is to use the Oracle constant SYSDATE. INSERT INTO table(C1,C2,C3,C4) VALUES (:1,:2,:3,SYSDATE); If necessary, qualify with TO_DATE function, though you should not need to do so because SYSDATE is defined as a DATE type....