DSXchange

Can you also output the value for KeyMgtGetNextValue('YourKey'), perhaps separately? My initial guess is that you are not using the same keyname value.

No list is kept, just one value; namely that of next value to use. I'm not where I can check the filename, but if you open the KeyMgtGetNextValue() routine you will see the code that tells you which record in which file is used to store that value.

Can you simplify the issue, write a job with a row generator generating a ustring, then converting it is a string column in a transform stage and writing it to a peek stage. Is the error similar? If no string type conversion occurs does it compile correctly?

The same problem, the Oracle settings need to be set in your shell script as well.

You probably need to correct your dsenv file. Read the ORACLE chapter in the IBM Information Server Planning, Installation, and Configuration Guide to get the details of what additions you need to make to the dsenv file.

I would prefer to use table and column names without embedded blanks, but if you do custom SQL in your job and use double-quotes around the column names with blanks that should solve your problem.

Can you do a "db2 connect to DATVT000 user YourUser" from the command line?

It sounds like you have embedded spaces as Ray surmised. You will need to quote them in order to have DataStage use them correctly.

But do the other jobs access ORACLE? It sounds like a dsenv file problem that needs to be corrected by adding the Oracle libraries, paths and environment variables. When you run the job, the ENV settings are displayed. IS "ORACLE_HOME" set there?

That could be the cause. You need to execute the following: CREATE ROLE DSXE; GRANT SELECT on sys.dba_extents to DSXE; GRANT SELECT on sys.dba_data_files to DSXE; GRANT SELECT on sys.dba_tab_partitions to GRANT SELECT on sys.dba_tab_subpartitions GRANT SELECT on sys.dba_objects to DSXE; GRANT SELECT...

How are you migrating jobs? If you are doing a .dsx or .xml job export from the original to the new project and are importing them through the designer job import button then you should not be seeing any errors during the import process. I know that there is an easier way, but I can't think of it or...

There is no reason to post duplicate threads. The active one can be found here

If you migrate from AIX to Linux you would need to change your licensing with IBM. IBM certainly still supports Version 7.5 and will do so for some time. Most scripts should run on both environments, although some might require slight syntactical changes. DataStage jobs that don't use such things as...

Hello pxraja, could you give an example of the data and also post your table's DDL?

Hello zulfi123786 and welcome to DSXChange. The manuals are (c) Copyrighted material belonging to IBM and, while they ship free of charge with the product, we cannot distribute them. Unless they can be found on the IBM site you will have to contact your distributor or IBM directly for a copy. Every ...