Search found 134 matches

by jweir
Fri Dec 07, 2012 11:30 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Job hanging at CDC stage
Replies: 2
Views: 2411

I found the solution. Instead of sorting and partitioning on the inputs, I did an ORDER BY on the reference table select query on the CDC keys. After I did this, the job completed within a minute.

I will mark this as resolved.
by jweir
Fri Dec 07, 2012 11:17 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Job hanging at CDC stage
Replies: 2
Views: 2411

Job hanging at CDC stage

Hi all, I have a job that uses the CDC stage to check if the source records are insert, update or copy records. I am looking up to the target table that has about 6.8 million records. In the current run of the job, only one record is looking up to the 6.8 million. For some reason, it has been taking...
by jweir
Tue Nov 20, 2012 11:17 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Removing double quotes from a flat file
Replies: 5
Views: 3745

I have tried that, in combination of removing all the double quotes in the source file as well as the Convert function, and it is still padding the column in the job. I have looked in the source file and it does not have an extra space after the column.

Any thoughts?
by jweir
Tue Nov 20, 2012 10:53 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Removing double quotes from a flat file
Replies: 5
Views: 3745

Removing double quotes from a flat file

Hi all, I have a job that reads from a sequential file and loads into DB2 target table. The file is tab-delimited and is supposed to have no quotes around the fields. However, the file has been converted to tab delimited from an Excel file. So when one of the fields has a comma inside it, the tab de...
by jweir
Tue Oct 23, 2012 11:51 am
Forum: General
Topic: Sequencer was entered, but never exited
Replies: 7
Views: 3881

I found the solution. I believe one of you may have mentioned it in one of your posts, but I could not see it since I am not a premium member. I found that all of the Routine 2 Execute Command activities were not all true on the output link triggers. One of them was false, so when I set the sequence...
by jweir
Tue Oct 23, 2012 8:08 am
Forum: General
Topic: Sequencer was entered, but never exited
Replies: 7
Views: 3881

I have tested it both ways. When I set it to "All", none of the email notifications fire. When I have it set to "Any", only the first email notification activity fires.
by jweir
Tue Oct 23, 2012 7:53 am
Forum: General
Topic: Sequencer was entered, but never exited
Replies: 7
Views: 3881

Sequencer was entered, but never exited

All, I need help with my sequence job. I have a pattern in my sequence that looks like below: Routine 1 ---> Parallel Job ----> Routine 2 ----> Sequencer ----> Nested Condition ---> Email Notification Now the "Routine 1 ---> Parallel Job ----> Routine 2 ---->" part is duplicated 39 times a...
by jweir
Tue Aug 14, 2012 8:42 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

My problem has been magically fixed. I re-ran my job and it now pulls the rows I need. The only thing I did was cleared out my SELECT statement and made sure I copied and pasted my entire parameter. Here is my code that works. Let me know if someone spots something that is different from what I had ...
by jweir
Tue Aug 14, 2012 7:56 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

It definitely has to do with the parameter. I hardcoded the time and I was able to pull rows: WHERE USTIMESTAMP > convert(datetime,'1800-01-01 16:07:48') Do I have to do something unique when I am dealing with parameter set value files? Since I am selecting the time from a value file of a parameter ...
by jweir
Tue Aug 14, 2012 7:22 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

Here is my select statement that is generated by DataStage in the log. sql_SRC_APPRAISALFORMSECTION,0: Execute failed on statement SELECT HRORGANIZATION , APPRAISALFORM , APPRAISALFORMSECTION , CSTIMESTAMP , CSACTOR , USTIMESTAMP , USACTOR , CONVERT(int, DELETEFLAG) as DELETEFLAG , APPRAISALSECTION ...
by jweir
Tue Aug 14, 2012 7:05 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

Scratch my last post. Since it is in my WHERE clause, it has no place in my table definition. I got one of my test jobs mixed in with the final version.
by jweir
Tue Aug 14, 2012 6:57 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

I have tried what you have suggested. However, I get the following fatal error: ODBC function "SQLExecute" reported: SQLSTATE = 42000: Native Error Code = 102: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '#ps_AppraisalFormSection_DeltaDate.EXTRACT_T...
by jweir
Tue Aug 14, 2012 6:26 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

Thanks for getting back to me.

The value of the parameter at run-time is: 1800-01-01 16:07:48
by jweir
Mon Aug 13, 2012 4:30 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

Update. I have gotten rid of the first problem. I altered the odbc.ini file to include quoted identifiers. The line in the Director log is no longer there. However, my job still aborts due to the error: ODBC function "SQLExecute" reported: SQLSTATE = 22007: Native Error Code = 241: Msg = [...
by jweir
Mon Aug 13, 2012 3:42 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: driver does not support quoted identifiers in SQL statements
Replies: 13
Views: 26478

Here is the fatal error I receive when I do not try and convert the parameter to timestamp: ODBC function "SQLExecute" reported: SQLSTATE = 22007: Native Error Code = 241: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Driver][SQL Server]Conversion failed when converting date and/or time from...