Unable to create a Dataset

arun_im4u · Post by **arun_im4u** » Sat Sep 05, 2009 10:29 pm

Hi

We have jobs failing in production because it is unable to create datasets based on the defined configuration file. We have a Datastage box and two DB2 boxes where the scratch space is defined. This is the first time we are running the jobs in this environment.

Below is the error.

/test/test.ds: Error when checking operator:
/test/test.ds has 20 partitions, but only 4 are
accessible from the nodes in the configuration file.
[datamgr/deleteop.C:165]

I checked for all the dataset directories defined in the config file exist with right permissions.

Any help to debug this issue would be great.

ray.wurlod · Post by **ray.wurlod** » Sun Sep 06, 2009 2:39 am

Given that the Data Set already exists, it must be accessed using a compatible configuration file (one that refers to the 20 nodes with which it was created). The orchadmin command has options to bypass this requirement but the Data Set stage does not (except in a grid environment in version 8.1) as far as I am aware.

arun_im4u · Post by **arun_im4u** » Tue Sep 08, 2009 11:12 am

Resolved.

The dataset was originally created using a different configuration file on different boxes where the scratch was defined. When we moved over to new boxes, the job tried to overwrite the existing dataset, but was unable to because of the mismatch in the config files.

I manually went and deleted the old files from all the nodes and then was able to run the job successfully. The admin is working on setting up orchadmin currently.

chulett · Post by **chulett** » Tue Sep 08, 2009 11:24 am

arun_im4u wrote:Resolved.

Excellent. Then please mark the post the same by using the big button at the top of the page.