DSXchange

Is it all the message you get? Are you sure that there is no change after the first run and the second? Is CLCL_ID a field or a name of the stage? Will it allow you to do a force compile?

So how can i avoid first five rows to sourch while importing

You can use . Also note that it does not works on all flavors of unix.

Have you setup the DNS entry for Datastage for those database. Update uvodbc.config and .odbc.ini which is under $dshome. The same can also be found under the respective project folder. First try to do tnsping from the datastage server to the database to verify the tnsnames.ora has been updated corr...

You cannot extract from BO universe, but can try with its repository.

Why not the Universe and Unidata stage?

If its about deciding filename on runtime, then YES, its possible on many ways.

And the OLETYPE for Jobs are 'CJobDefn'.
So if you change your query as following you can get the result.

Hi Abhi, The output for LIST DICT or LIST ITEM and SELECT will be different. Select will give the list of data available in the Hashed table. LIST DICT will give the data dictionary(Metadata) for the table. You can use LIST DS_JOBOBJECTS to get the similar result of SELECT * FROM DS_JOBOBJECTS. Simi...

So its simple 'FROM' 'WHERE' statement misplace.

Change it to LIST DICT DS_JOBOBJECTS. (No dot'.' next to LIST)

The general reason can be many. Majorly Unique constraints violation, metadata mismatch or condition based rejects.

Check the permission of the file 'uat_edw.MAINT_USERS_SECR.bad' using ls -lat. And make sure the file exist in the correct format as expected.
Check the owner of the file. Check if the file can be deleted using dsadm.
Just curious to know, if its production, shouldn't it be prod_edw.....

The Usual exciting show from Ray and Craig!!!
Ray on 16K and Craig on 8K. Ray still maintains his benchmarks with Craig.
Nothing gonna stop them.

Perhaps you can try to reinstall the plugings using dspackinst in $DSHOME/bin.

2nd method may not pull out the precise result as the data and the indices been updated/inserted by ETL process. Due to the same reason, the performace might even get affected as the data gets loaded as the local index gets updated (based on the partitioning key).