DSXchange

Hi Buzzy, How much volume of data did you used while performing these tests? We were having huge volume of data 15-16 million to start with. It took around 12 mins for datsstage job to write into seq file and then another 1-2 mins for COPY command to load into the tables, using 4 virtual node config...

Sure buzzy... this connector that you are using, is that provided by Vertica itself?..
Yeah, i also thought that extra I/O would cause the problem, but we did faced some issues while using ODBC connector to Vertica specially if you need to truncate the table before loading.
Do let me know your results

I was also using Vertica with Datastage 8.7 version, the way how we tackled the loads were to create a load ready sequential file in pipe delimited and then using Vertica's COPY utility command to load the data. Believe me ODBC can never give you that performance. You can try using this way and comp...

Got the root cause of this issue - The file schema that i loaded into the target sequential file stage was imported using a mainframe copybook (it had level nums, groups etc). I think some-how the column definitions were the culprit behind such junk display of data as the definition was for an ebcdi...

The input to the job is a sequential pipe delimited file, which i can read properly in UNIX prompt. So this rules out the possibility of having ebcdic data. Moreover the input consists of integer and decimal values and transformations are also simple, so i dount if any non-readable ascii character c...

I am using vim <file name> in unix. Normally for a ascii file, we can see the actual data. But here in this case i am seeing entire data as junk.. following is example 201210|^@Z|^@^@'^S|^@^@^@^\|^@^@^@~| |^@^@^@^@|^@^@^@^@| |^@^@^@^@| | |^@^@^@^A|^@^B|^@^@^@^@|^@^@^@^@|^@^@^@^@|^@^@^@^@|^@^@^@^@|^@...

Hi, I am facing an issue while creating a sequentail pipe delimited file using datstage job. My job design is like seq stg -> trfm -> seq stg Target is pipe delimited. Now the job runs fine without any warning, even when i view data from view data utility in seq stage, i can see it properly but when...

Hi All, We are planning to use ODBC connector stage for extraction and loading of the data from vertica database. We are using DS version 8.7. My concern is that we will be extracting huge volume of data ~270 Million rows with around 30-40 columns, so performance of jobs would take a lot of hit. Can...

Found the reason, why it was aborting. Its the issue of level number of those columns which were being added in transformer. Their level number was blank and the columns that were being taken from cff file had it as 02. Added the level number and job worked.

There is no OCCURS clause for the key column. In fact, there are only 2 columns in the file. Also, i tried reading the file in a separate job and wrote it to a dataset, and used the dataset for lookup. But again it gave the same fatal error. The key column is a char column. It might have some junk c...

Hi, I am getting following error in my job:- main_program: Syntax error: Error in "lookup" operator: Error in output redirection: Error in output parameters: Error in modify adapter: Error in binding: Could not find type: "subrec", line 330 I am doing a lookup in my job where the...

You can define the record type and record id constraint for '27' but while defining the output constraints, dont map the record id =27. In that way you can get rid of this warning.

Is there any document that have the details of how JobMonApp works, m trying to figure out if number of monitor sessions have any impact

Got the answer, we need to include escape char \ for every single qoute that we are passing in the value of parameter
eg var1 = \'A\',\'N\' so on...

Found a workaround using transformer and reducing some redundant requirements.