DSXchange

You cannot write records to a datasets which have bigger length than the blocksize of the dataset which is by default 128K. You can change that though by setting APT_PHYSICAL_DATASET_BLOCK_SIZE.

You mention that these jobs are running in production fine. I am assuming that your problem is in other environment. Are the database tablespaces the same in that environment as they are in prod? When DB2 executes load it does some locking at tablespace level.

If you were to reimport the Database meta data, you will find that for Char and Varchar columns, the length will be a multiple of the byte length ( depending upon the value set in the DataBase ). The soulution is to multiply the length values in the database metadat by appropriate factor ( eg. 4 tim...

The issue is the configuration of the SQLServer database. You need to set it up to support multi-byte characters - UTF-8, UTF-16, or UTF-32 are possible options. If the DB is set up for US-English you will have problems.

I believe that you must install the multi-client manager that comew with version 8

Is the table partitioned or copied on each DB2 node?

Check the configuration file you are using to see if it is referencing multiple nodes.

What other tasks are going on - on the server while you were running today?

Did someone change the configuration file your job is using?

Do other ID's work connecting to DataStage server?

You may also need to add the db2 configuration parameters into the .profile file of the etl user ( i.e. the user you sign on to DataStage with) Make sure your libpath is set correctly. Also you can verify the connectivity by trying to run db2 connect to "Database" from the unix command line.

How many "root" levels will you have in your hierarchy ( in your example 1 )?

You could partition your data based upon values of the "root" level and then run subsets in parallel.

Gazelle


Is the DB2 database on the same machine as DataStage or is it on a different machine?

you need the windows xp path.

See post:

viewtopic.php?t=97965

One of the things that will cause this message is if you get a network timeout..

This can occur if you leave a DataStage client connected and go out for lunch

yes you can have two key colums in lookup.

1) make sure the column definitions are the same for the source and hash file.

2) try If ( IsNull(lkReferenceLookup.column_1) or IsNull(lkReferenceLookup.column_2)) as the constraint for the failed lookup stream.

Another option is to create a temporary table with the two columns in it.

Change the existing job to truncate then load into the table.

Then use an after SQL function to issue an insert into the target table using a not exists in the where clause.