DSXchange

The database itself probably supports a structure called a SEQUENCE that you can invoke to generate the numbers, usually via a property called something like NEXTVAL.

Yes, your segment files are minimally sized (128KB each). Therefore that's not the problem. Data are moved to/from data sets in units of not less than 32KB, so you should be seeing very few I/O operations.

Time to involve your official support provider, methinks.

Not at the moment. Currently on 8.5 with DB2.

Just before the break I installed an 11.3.1 system (with FP2) using SQL Server as the repository database. But there's nothing there to export yet.

No, that's just a weird result. Can you reproduce it? How big are the Data Set segment files?

The search is only ever within the project from which the export is being performed. Objects in other projects cannot participate in dependency relationships with objects in the current project.

Are you using any unbounded string data types (Char or VarChar)?

Johnny0638 wrote:How to import data files in parallel?

Specify the multiple readers per node property.

Johnny0638 wrote:We run the DS job in osh script , which Environment Variables can change the size of Restrict Memory Buffer ?

The global memory for tsort operators is set by environment variable APT_TSORT_STRESS_BLOCKSIZE. Note that this sets the memory allocated for all tsort operators.

I think that, in this case, it's the question that was resolved, and that the answer is "no". Newer versions of classes invoked by osh may well have arguments that do not exist in earlier versions.

The root cause is getting the list of dependent items. There is no smart way to do this because there is no a priori knowledge of the items you have selected for export. Therefore, for each of those items, the exporter has to search (relevant object types) in the entire project repository.

Possible ideas:
1. generate an XML export then generate an XSD from that using any of the available tools
2. search your machine for file names matching *.xsd

rajnishjain88 wrote:I have to develop a parallel job (without chaining it together with a sequence job)

Resist stupid requirements!

If the best solution uses a sequence, use a sequence.

The Exception Handler has its own activity variables, one of which identifies the name of the activity that triggered it. Use a Nested Condition activity in the exception handling stream to test that value.

Thank you for posting the solution.

I have been able to reproduce this error and narrowed the cause down to a column name that began with an underscore.