DSXchange

Hi

"Enable partition reads" will work with partitioned databases in DB2 - if you have a single partition database you will not see a performance effect

regards
MT

Hi More detailed information will get you better answers! I guess - and I am very sure chulett as well - that you are talking about DB2. Load in DB2 has several options to ensure consistency in the database while it does not use SQL and standard logging to add the data. You have giut a so called Cop...

Hi sridinesh2009, first I wonder that your statement still works as the DB2 Connector usually wants ORCHESTRATE.column-name instead of "?". I have recommended to an create index for these situations a lot of times and I have no idea why this should not be possible - maybe not for you perso...

Hi,

as you write that you migrate from 7.5 so I recommend to set
DB2CODEPAGE 1208 as job parameter

Hi ok two more things you could do: - You said that you viewed the file - did you use DataStage View...? If so I stongly recommend to do it natively on the OS because DataStage View will already interpret the data. - I would also strongly recommend DB2 Connector stage if you work with DB2 Your datab...

Hi Dinesh, it is always a little hard to say where the stuff gets converted or lost - so it is not enough to look at the db2 stage where you load it. default NLS Map Name is UTF-8 in the target db2 bulk stage. Having UTF-8 for the database and as NLS in the DataStage job you could use the DB2CODEPAG...

Hi Abhishek, why are you not using the DB2 Connector - relly recommended when using DS8 as described! The db2nodes.cfg is only available in partitioned DB2 databases - so yes it might be a good idea to ask your Db2 admin. But again if you use the Db2 Connector you do not have to worry about the dbno...

Hi nishantrk DataStage uses the regular DB2 Load utility. I am a littl e surprised about the different durations you saw but DEL (Delimited ASCII) would always be my choice as ASC is only used when you get data in that format. Of cause differnt options can have a performance impact. Try to use API l...

Hi _chamak

you could write a database trigger "on update" of that column. Then you check if it is set to 'Y' within the trigger and run a user defined function.
That UDF could then execute a OS command which runs dsjob to start the DataStage sequence (or job).

Hi tbtcust 1208 is UTF-8 and this environment variable sets it for DB2. I would not say that it is always the solution, but in many cases it is. We have other jobs working well with Unicode extended attribute and it seems it "depends" on combinations used. Many things can only be found out...

Hi partha.natta


use the Parser step within the XML stage.
The PARSER defines how the XML looks like
and in the OUTPUT step you defines how many rows will be created.

Hi tbtcust, reading from a file into a DB2 UTF-8 database should be possible without warnings. Having UTF-8 for the database and as NLS in the DataStage job you could use the DB2CODEPAGE set to 1208. Make this a job parameter and do not user the extended unicode for the column and it will work witho...

Hi tbtcust Some columns are as small as 1 and as large as 80. The database code set is UTF-8. OK - but is the specified length in DataStage the same as in DB2? For example if you have a length of 10 in DataStage - try using 40 in DB2 ( as a single character could be stored in up to 4 bytes using UTF...

Hi tbtcust what is the column length in DataStage and in DB2? I suppose your database hast been created with UTF-8 and this means that a single character can be stored in 1,2,3 or even 4 bytes. Be aware that DB2 length specifications at the moment are in bytes (and not in characters). This can lead ...

Hi Raftsman


the "Statistics" option is only valid if the LOAD MODE is replace.
This is due to regular DB2 LOAD functionality.