Search found 7201 matches
- Tue Oct 30, 2001 11:35 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Classifying Telephone numbers in a lookup
- Replies: 6
- Views: 1034
Thank you David i will try that. >From: "David Barham" >Reply-To: >To: >Subject: RE: Classifying Telephone numbers in a lookup >Date: Tue, 30 Oct 2001 21:14:09 +1000 > >Can do! > > >* Make sure the DataStage definition of the prefix on the lookup is >long enough to hold the entire telephone number. ...
- Tue Oct 30, 2001 11:14 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Classifying Telephone numbers in a lookup
- Replies: 6
- Views: 1034
Can do! * Make sure the DataStage definition of the prefix on the lookup is long enough to hold the entire telephone number. * Pass the entire telephone number to the lookup in the key column "prefix" * Write a user defined query for the lookup something like: select prefix, prefix_code from table_n...
- Tue Oct 30, 2001 10:54 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Classifying Telephone numbers in a lookup
- Replies: 6
- Views: 1034
Well my database is oracle-8i and ive got the result of a extraction that has a column named telephone and has values like 219999999, 91111111111, 112, 0800234234234, 112123456789, ... and my table which has the prefix and the code has two columns: prefix_code: 0001, 0002, 1230, ... prefix: 21, 0800...
- Tue Oct 30, 2001 10:39 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Classifying Telephone numbers in a lookup
- Replies: 6
- Views: 1034
What kind of database is your lookup stored in? Is it a relational database or a hash file? Can you give more detail about what your lookup table looks like and what you are trying to get from it? -----Original Message----- From: pedro santos [mailto:pedro_f_santos@hotmail.com] Sent: Tuesday, 30 Oct...
- Tue Oct 30, 2001 10:20 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Classifying Telephone numbers in a lookup
- Replies: 6
- Views: 1034
Classifying Telephone numbers in a lookup
Hello to all. Ive got a problem, i wonder if any one can be of assistance, id be really grateful. Im trying to classify a list of telephone numbers, according to a cod thats stored in a table with the list of all telephone prefix, my problem is that not all prefixes have the same length so ive got t...
- Tue Oct 30, 2001 6:01 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
But even a simple UPDATE can update more than one row if the key columns are not the primary key (which is a legitimate thing to do). To really achieve this from DataStage, it would have to ask the database how many rows were actually updated for each row passed to the passive stage and then record/...
- Tue Oct 30, 2001 5:29 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
If you use the output link variables on the active stage (Transformer?) that is driving the output link, you can detect whether the row was rejected by the database or successful. This could be used in conjunction with the row count on the output link to maintain statistics on another output link. N...
- Tue Oct 30, 2001 4:46 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Admin of Source tables used in a datastage project
- Replies: 0
- Views: 480
Admin of Source tables used in a datastage project
We a trying to come to terms with administration of the source table extracts via odbc A common request to our Administrator is: A table on the source system is either being dropped on having columns dropped/modified Our administrator is required to identify any impact to the datastage project. To d...
- Tue Oct 30, 2001 12:10 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Create a transform that creates a value indicitive of the load eg. the date, and load that value into a new column in the target table, then query the table for that value. Regards Adam Peter Oates on 30/10/2001 10:03:32 AM Please respond to To: "datastage-users@oliver.com" cc: Subject: Reporting on...
- Mon Oct 29, 2001 11:40 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Ray, This may not always correlate with the actual rows inserted/updated on the database table. eg. 10 rows out from the active stage but only 7 rows get updated because the other 3 dont exist in the database table. I have tried to enter sql like select @@rowcount into the AfterSQL properties of the...
- Mon Oct 29, 2001 11:24 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Its in the logged event for the active stage finishing (use DSGetLog... functions) and its available by asking the output link (use DSGetLinkInfo) for its row count. -----Original Message----- From: Peter Oates [mailto:Peter.Oates@macquarie.com] Sent: Tuesday, 30 October 2001 10:04 To: datastage-use...
- Mon Oct 29, 2001 11:03 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Reporting on rows updated in database
- Replies: 16
- Views: 2563
Reporting on rows updated in database
Is there a way to report on the actual rows updated in the database load stage.
Im using the Sybase OC and BCP plugin.
regards,
Peter
Im using the Sybase OC and BCP plugin.
regards,
Peter
- Mon Oct 29, 2001 3:08 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Subject: rejected_code isuue
- Replies: 1
- Views: 337
Subject: rejected_code isuue
This is a topic for an orphaned message.
- Mon Oct 29, 2001 3:08 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Subject: rejected_code isuue
- Replies: 1
- Views: 337
Xiong, If your constraint that is used to write to the output file uses the primary key column(s) form the lookup tables, then there will be no rejects records, because the odbc lookup stage will only select the records that match your select criteria in you stream input link. Keep in mind only reco...
- Mon Oct 29, 2001 1:11 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Update existing rows / warnings
- Replies: 1
- Views: 336
I think I have a solution - I will try it now. I will use the target table as a lookup as well when reading the source table, so that I can create a constraint that will only process matching records. This should work. Dirk -----Original Message----- From: Dirk Moolman [mailto:dirkm@reach.co.za] Sen...