Search found 7201 matches
- Tue Jan 07, 2003 11:56 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Calling KeyMgt* from routine
- Replies: 13
- Views: 3710
This may or may not be the case, however I was quoting the behaviour described in the Ascential documentation. Which states a return code from such a routine of non zero is considered failure and the job will abort. If this is not the case then it is probably a good idea to take this up with Ascenti...
- Tue Jan 07, 2003 11:48 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Calling KeyMgt* from routine
- Replies: 13
- Views: 3710
I agree, but if you want it to appear in the drop down list of routines then it should be. ----- Original Message ----- From: "Ray Wurlod" To: Sent: Monday, January 06, 2003 9:30 PM Subject: Re: Calling KeyMgt* from routine > That is not correct. The routine type must be before/after. You can store ...
- Tue Jan 07, 2003 10:02 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Datastage warning
- Replies: 4
- Views: 1652
Hi Leonid, SInce ur informix database was created without log, it doesnt support transcation. Just ignore that. Its ok. Br. Tommy -----Original Message----- From: lfrumke@sears.com [mailto:lfrumke@sears.com] Sent: Tuesday, January 07, 2003 5:20 AM To: datastage-users@oliver.com Subject: Datastage wa...
- Tue Jan 07, 2003 10:00 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Datastage warning
- Replies: 4
- Views: 1652
Hi Leonid, SInce ur informix database was created without log, it doesnt support transcation. Just ignore that. Its ok. Br. Tommy -----Original Message----- From: lfrumke@sears.com [mailto:lfrumke@sears.com] Sent: Tuesday, January 07, 2003 5:20 AM To: datastage-users@oliver.com Subject: Datastage wa...
- Tue Jan 07, 2003 8:02 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
Nulls and empty strings are the same to Oracle. The TO_DATE function will simply return null. Provided your database column does not have a NOT NULL constraint, that will be handled just fine. The advantage of an explicitly defined format is that there is no ambiguity. I have played around a bit usi...
- Tue Jan 07, 2003 6:56 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
My testing of the to_date function resulted in the following: select AAA || to_date(1/1/2002,dd/mm/yyyy) || BBB from dual AAA01-JAN-02BBB select AAA || to_date(,dd/mm/yyyy) || BBB from dual AAABBB select AAA || to_date( ,dd/mm/yyyy) || BBB from dual ORA-01847: day of month must be between 1 and last...
- Tue Jan 07, 2003 6:38 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Calling KeyMgt* from routine
- Replies: 13
- Views: 3710
Hi Ien, That was the problem, thank you all for the help. Im using the routine from a sequencer, it is setting one of my job-parameters, and i can actually make it use it in the next jobs ) It was the same problem that I was working on just before xmas. br Tom ---------------------------------------...
- Tue Jan 07, 2003 12:54 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
Yes that is true. But i wanted to avoid it because i dont know how generated query with to_date function would behave when there are nulls or empty strings. So i went ahead with user defined sql with no to_date() function in OCI Stage. I will handle empty strings and nulls in a routine. Is that appr...
- Tue Jan 07, 2003 12:35 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
With a generated query, using timestamp causes DataStage to generate the following: TO_DATE(your column,YYYY-MM-DD HH24:MI:SS) If you look at the generated SQL, you can see what it is doing. -----Original Message----- From: Shivprasad Rao [mailto:shiv_rao@hotmail.com] Sent: Tuesday, 7 January 2003 1...
- Tue Jan 07, 2003 12:32 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
Thanks David. What we found was change the target OCI column type to "TIMESTAMP" and allow the default oracle date format whichis "dd-mon-yy". The job runs fine. Thank you very much. Shiv >From: David Barham >Reply-To: >To: "datastage-users@oliver.com" >Subject: RE: OraOci9i Date Issue >Date: Tue, 7...
- Tue Jan 07, 2003 12:26 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
Oh, well... got interrupted and David beat me to it. This is documented in the DataStage Oracle Call Interface Plug-in pdf that ships with the product, btw. See the section on DATE Data Type Considerations and the Oracle Data Type Support section on Date Data Types. -craig "Shivprasad Rao" 01/06/200...
- Tue Jan 07, 2003 12:09 am
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
The best and safest way to handle Oracle dates in DataStage is to define the output in DataStage as TIMESTAMP rather than DATE. You then manipulate your input date string to match the format: YYYY-MM-DD HH24:MI:SS If the source is ODBC and also defined as timestamp, then you probably only have to tr...
- Mon Jan 06, 2003 11:59 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: OraOci9i Date Issue
- Replies: 7
- Views: 2160
OraOci9i Date Issue
Hey Guys, Im trying to load date strings from either a text file or an OBDC source to ORAOCI 9i target. I have mentioned my target column as date and source column as string, I tried all possibilities of Iconv() and Oconv() functions to convert string to date but none works, Only thing which work is...
- Mon Jan 06, 2003 9:44 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: bold free text field
- Replies: 8
- Views: 1251
Usually there is a character sequence for "start bold" and another for "stop bold". You need to determine - perhaps using a text editor - what these are. Then you can use the Ereplace() or Change() function (or Convert() if its a single character) to change these to "". ----- Original Message ----- ...
- Mon Jan 06, 2003 9:32 pm
- Forum: Archive of DataStage Users@Oliver.com
- Topic: Calling KeyMgt* from routine
- Replies: 13
- Views: 3710
That is not correct. The signal to stop is changing the ErrorCode argument to a non-zero value. It is unaffected by the return value of any subroutine or function invoked from the before/after subroutine unless you explicitly code to load that return value into the ErrorCode argument. ----- Original...