Search found 91 matches
- Mon Sep 10, 2007 5:17 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error in routine- not in VOC
- Replies: 13
- Views: 6244
Leomauer, Earlier I tried without CHAR(254) only. But it was giving error: AfterJob (1): The sql statement is sqlplus<<endofsql -S aaa@bbb/cc11 INSERT INTO APPS.XYZ(SERVER_NM,PROJ_NM,JOB_NM,JOB_STATUS,START_DT) VALUES(pa12,Test,JobNamesFromSequence,0,2007-09-10 03:59:23); exit; endofsql AfterJob (1)...
- Fri Sep 07, 2007 7:16 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error in routine- not in VOC
- Replies: 13
- Views: 6244
- Fri Sep 07, 2007 6:27 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error in routine- not in VOC
- Replies: 13
- Views: 6244
- Fri Sep 07, 2007 3:21 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error in routine- not in VOC
- Replies: 13
- Views: 6244
Sorry. By mistake I missed copying that statement here.
I used the above DSExecute statement. I have used "UNIX" only Ray.
Regards,
ssunda.
Code: Select all
Call DSExecute('UNIX',SQLSTMT,Output,SystemRetValue)
Regards,
ssunda.
- Thu Sep 06, 2007 5:56 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error in routine- not in VOC
- Replies: 13
- Views: 6244
Error in routine- not in VOC
Hi All, The routine is trying to insert data into an oracle table. And Iam using DSExecute with sqlplus to insert data. The code is as follows: SQLSTMT = "sqlplus<<endofsql -S abc@dddd/xxx":Char(254):" INSERT INTO APPs.LOGDATA(SERVER_NM,PROJ_NM,JOB_NM,START_DT)" SQLSTMT := "...
- Tue Sep 04, 2007 9:00 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error when accessing DS_JOBS table from DSExecute command
- Replies: 3
- Views: 1380
- Tue Sep 04, 2007 8:29 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error when accessing DS_JOBS table from DSExecute command
- Replies: 3
- Views: 1380
Error when accessing DS_JOBS table from DSExecute command
Hi All, My requirement is to fetch the job names involved in a particular sequence. I used the following query in Datastage administrator and it successfully returned the jobnames of a sequence. SELECT EVAL "TRANS('DS_JOBOBJECTS','J\':@RECORD<5>:'\ROOT',31,'X')" AS JOBS FMT '35L' FROM DS_J...
- Tue Jul 17, 2007 4:01 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Preserving blanks when using Oracle(LOAD Option)
- Replies: 8
- Views: 3350
- Mon Jul 16, 2007 11:47 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Preserving blanks when using Oracle(LOAD Option)
- Replies: 8
- Views: 3350
Arnd, In one of the sql loader documents, I found the following statement: Although VARCHAR fields also contain character data, these fields are never trimmed. A VARCHAR field includes all whitespace that is part of the field in the datafile. That means, the blanks should have been inserted as blank...
- Mon Jul 16, 2007 11:16 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Preserving blanks when using Oracle(LOAD Option)
- Replies: 8
- Views: 3350
I have imported the metadata for table using Load->Import->Plug-in Metadata Definitions I tried fixing it, by changing the column definition from varchar(3) to varchar(1) manually in the oracle stage. It is still giving the same error-ORA-12899. When I dont use the env variable (APT_ORACLE_PRESERVE_...
- Mon Jul 16, 2007 4:06 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Preserving blanks when using Oracle(LOAD Option)
- Replies: 8
- Views: 3350
Preserving blanks when using Oracle(LOAD Option)
Hi All, I went through the posts related to preserving blank spaces(adding env variables APT_ORACLE_PRESERVE_BLANKS) and tried them out. But still my job is getting aborted. I have blanks in some of the character fields coming from input file and want to store them as blanks instead of NULL in oracl...
- Sun Jul 15, 2007 10:55 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Formatted length of fields & record<declared length-W
- Replies: 18
- Views: 3238
The following are the properties set on Sequential file stage. Record type =implicit. Field defaults->delimiter=none General->Character set=EBCDIC Data format=binary Decimal->Allow all zeroes=yes I have neither used Record delimiter nor Final Delimiter. Dint use Record Length Property also. But I tr...
- Fri Jul 13, 2007 3:34 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Formatted length of fields & record<declared length-W
- Replies: 18
- Views: 3238
- Fri Jul 13, 2007 3:05 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Formatted length of fields & record<declared length-W
- Replies: 18
- Views: 3238
Arnd, I have 6 similar jobs and all them are having this warning(with diff record lengths) when using 'LOAD' option. I checked the control file created in /opt/etl/scratch directory in unix. The record length calculated by sql loader is 272. table definition in the control file is as follows: Column...
- Fri Jul 13, 2007 2:39 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Formatted length of fields & record<declared length-W
- Replies: 18
- Views: 3238