Search found 7201 matches
- Tue Nov 06, 2001 1:37 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Paul We use this technique with all our jobs and it works fine. Check that you are interrogating the right REJECTCODE, the link to your OCI stage. Try setting the transaction size to 1 to see if makes any difference. Shouldnt. HTH >Hi Ray, > >I dont know what is going wrong here. I try to follow you...
- Tue Nov 06, 2001 1:27 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Yes, but what version of the OCI stage are you using? And what version is Paul using? -----Original Message----- From: kuan@clear.net.nz [mailto:kuan@clear.net.nz] Sent: Tuesday, 06 November 2001 12:37 To: datastage-users@oliver.com Subject: RE: Reporting on rows updated in database Paul We use this...
- Mon Nov 05, 2001 10:09 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Ive been griping about this for pushing two years now. You are right, that functionality works fine for the ODBC stage, but not at all for the OCI or OCI8 stages. Youve got absolutely no way to know if the database has rejected your row programatically. You can see the mess it makes in your log, but...
- Mon Nov 05, 2001 10:06 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Selective lookups
- Replies: 3
- Views: 959
What, no response from Phil Walker? Maybe he slept in this morning. This is one of Phils classic complaints or enhancement requests. Ascential .. when are we going to have constraints on reference links to determine whether or not the reference link is used? This would be very useful for performance...
- Mon Nov 05, 2001 9:42 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
I suspect that the OCI stages dont set the link variables properly (link variables were introduced after version 2.3 of the OCI stage was written). I would check this with Ascential support if I were you. It definitely works OK with ODBC stages. -----Original Message----- From: Paul Ko [mailto:PKO@c...
- Mon Nov 05, 2001 9:34 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Hi Ray, I dont know what is going wrong here. I try to follow your method but it does not seem to work. The REJECTCODE returns all "0" regardless of whether the database update is successful or not. My input data contains 3 rows, the first two records are supposed to return SQL 100 (meaning not foun...
- Mon Nov 05, 2001 7:25 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Merging data
- Replies: 1
- Views: 406
No, youve been misled. You have a primary input stream, everything else is a reference. You cannot reference a stream of data as suggested to you. Your situation is your desire to only do a reference on condition. Questions: 1. Is your reference lookup so detrimental to performance that it needs to ...
- Mon Nov 05, 2001 5:52 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Merging data
- Replies: 1
- Views: 406
Merging data
Hi to all. Im trying to merge data from two different transformer stages, the metadata in both stages is equal, and i would like to merge them without using any kind of files or database tables, is it possible? Tanks for your patient. _________________________________________________________________...
- Mon Nov 05, 2001 4:31 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Hash File Creation
- Replies: 21
- Views: 4025
The best think to do is to add this line to your dsenv file, then stop and start DS. umask=002 This will let you create all your new Hash files OR jobs with 775 permision which is read,write, and execute to owner and group and gives read and execute to others. Remember that this will not effect you ...
- Mon Nov 05, 2001 3:39 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Selective lookups
- Replies: 3
- Views: 959
Hello In your transform, in the derivation, you can do a condition like IF F Then F Else lookup regards Rui Soares Rui Soares NOVABASE - Data Quality - Mi Tlm : +351 . 96 347 0840 Mail : RUI.SOARES@NOVABASE.PT -----Original Message----- From: pedro santos [mailto:pedro_f_santos@hotmail.com] Sent: Se...
- Mon Nov 05, 2001 3:27 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Selective lookups
- Replies: 3
- Views: 959
Selective lookups
Hello to all Well ive got a question, that may bee of interest, im doing a lookup using an oracle 8i field, but only if that field takes the value A or B or C the lookup is made if the field takes the value F the lookup is not needed, one possible solution is to create a constraint in a transformer ...
- Mon Nov 05, 2001 7:17 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
I wish I could get DBMSCODE and SQLSTATE from the Basic macros. From the doco its only available from the C API. -----Original Message----- From: Paul Ko [mailto:PKO@clear.co.nz] Sent: Monday, 5 November 2001 1:45 PM To: datastage-users@oliver.com Subject: RE: Reporting on rows updated in database H...
- Mon Nov 05, 2001 5:48 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Assuming each row sent from DataStage is intended to update exactly one row in the target table (see David Barhams note), if REJECTEDCODE is zero the update was successful, otherwise it wasnt. Lets say your output link is called OutputLink. On another output link, lets call it FailLink, you can gene...
- Mon Nov 05, 2001 3:36 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Oracle OCI BL - Fault Type 11
- Replies: 0
- Views: 663
Oracle OCI BL - Fault Type 11
We are getting the following everytime we use the OCI Bulk Loader: Abnormal termination of stage OCIBL.CTransformerStage33 detected and this on reset: Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program DSD.StageRun at address 744. Dat...
- Mon Nov 05, 2001 2:44 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Hello, Refer to the email that Ray had said, how exactly can I use the active stage link variables to detect whether the row was rejected by the database or successful. Mind that there was no SQLCODE in the link variables. Currently, only the following values are in the output link variables: DBMSCO...