DSXchange

How about creating a dummy column with a truncated & trimmed value from the LongVarChar into your target VarChar(315) in your SELECT statement directly? This would work for both Server and Parallel jobs. I have used Trim function for that perticular column in my x'former stage between source DB...

Can you disable the constraints or create a test dummy table in the same schema without the constraints and do a comparison run - this will help localize the cause of the slow load.

Also, can you use the bulk loader (if you are doing pure INSERTS) or are you doing upserts?

Yes, it does I'm not at a PC with a DataStage installation, or even the documentation, right now so any statements I make should be cross checked for syntax and other errors. The format is quite simple, something like: record ( {columnName}:{DataType}; ... ) The DataTypes...

You can't just import the Excel meta-metadata. But if you can import a PX Schema it would save you writing a macro to create the DDL to load into the database of your choice and from there to load into the DataStage repository. So, does your manager show capability for loading schemas?

How about creating a dummy column with a truncated & trimmed value from the LongVarChar into your target VarChar(315) in your SELECT statement directly? This would work for both Server and Parallel jobs.

Does your metadata import in your manager contain a tab to import a px schema? If so, you could reformat your spreadsheet in a macro to make a PX schema file and load that into your DS installation. I think it will show up even on non-px installs.

DataStage will use the directory path pointed to for your project and look for a VOC file in that location. You will see this message if your UNIX userid does not have access to that directory or VOC file {this is the most common reason for this error in a running environment}. Can you attach to any...

DataStage will only pad if it needs to. If your CHAR column is defined as length 4 and your database is a CHAR(4) column then the settings for padding won't apply. You will need to do this at the source, or at the point in your job where you are going from a char(3) to a char(4) column type. Where i...

Hello Aravind, you seem to have 2 requirements: 1. Converting a sequential stream into formatted XML. Look at the documentation and help for information on XML. 2. writing the XML to MQ Series. Look at the documentation and help for information on MQ Series. Both XML and MQ Series have specific .pdf...

ravij, I'm sorry about leaving the "plz" comment in there! I put it in and then decided that I was just in a bad mood and it wasn't that important, so I cut the sentence out but then I must have refreshed the screen or done something to put it back in. Now that it "escaped" I'll leave it out, since ...

Ray - that's pretty cool; it's not that I don't believe you but I had to try it out for myself and darned if you weren't right. I guess I'm just too old-fashioned and these modern, new-fangled additions just confuse me So a bad write will occur if the key (or any part of it, if you have a multiple-c...

Can you set your $APT_STRING_PADCHAR to " " for this job?

In the Pad Char box put just ONE space

DataStage can and does read NLS character, but you need to know what is happening with regards to implicit and explicit conversions of character values. So far this thread has been geared towards getting you to find out what is happening and where it is happening, but as you've solved the problem ot...

ravij, we all have full keyboards here and don't need to text message, especially those of us like myself and yourself who don't speak English as a native language - so please don't use "plz" but spell it out. The VOC file is a core internal file in the DataStage engine and is not documented as part...