When i try to view a dataset using Dataset Management Utility in Designer. I pointed to data file path which is mentioned in config file. I get following error messgage "This is not a valid dataset file or format is not currently supported."
How can i run Orchadmin from windows workstation ?
Dataset Management Utility Doesn't Work
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 299
- Joined: Wed Nov 13, 2002 5:38 pm
- Location: USA
The Data File Path in the config file? That is not correct. You need to point to the descriptor file. It is this file which will contain the config file paths to the resource disks for the dataset. The descriptor file will provide orchadmin ont he command line or the Dataset Management tool in Designer with the info needed to view the data, schema Config file, etc. The descriptor file is the filename and path that was defined in the dataset stage of the job that created the dataset.
throbinson:
When i pointed to header file i was able to view the data.
However i have following scenario:
In our jobs we are creating datasets on an external file server
(e.g. \\fileserver\dev\proj\work\test.ds) but in config file admin has pointed datasets path as below:
node "node1"
{
fastname "DSS01"
pools "" "node1" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
node "node2"
{
fastname "DSS01"
pools "" "node2" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
Should admin needs to change the config file and give fileserver path in config file?
When i pointed to header file i was able to view the data.
However i have following scenario:
In our jobs we are creating datasets on an external file server
(e.g. \\fileserver\dev\proj\work\test.ds) but in config file admin has pointed datasets path as below:
node "node1"
{
fastname "DSS01"
pools "" "node1" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
node "node2"
{
fastname "DSS01"
pools "" "node2" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
Should admin needs to change the config file and give fileserver path in config file?
throbinson:
When i pointed to header file i was able to view the data.
However i have following scenario:
In our jobs we are creating datasets on an external file server
(e.g. \\fileserver\dev\proj\work\test.ds) but in config file admin has pointed datasets path as below:
node "node1"
{
fastname "DSS01"
pools "" "node1" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
node "node2"
{
fastname "DSS01"
pools "" "node2" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
Should admin needs to change the config file and give fileserver path in config file?
When i pointed to header file i was able to view the data.
However i have following scenario:
In our jobs we are creating datasets on an external file server
(e.g. \\fileserver\dev\proj\work\test.ds) but in config file admin has pointed datasets path as below:
node "node1"
{
fastname "DSS01"
pools "" "node1" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
node "node2"
{
fastname "DSS01"
pools "" "node2" "DSS01"
resource disk "d:/DSS01/apps/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "d:/DSS01/apps/Ascential/DataStage/Scratch" { pools "" }
}
Should admin needs to change the config file and give fileserver path in config file?
-
- Charter Member
- Posts: 299
- Joined: Wed Nov 13, 2002 5:38 pm
- Location: USA
Yes. Where you want the data to go is the path you'll need to put into the resource disk path of the nodes of the Config File. You've got a 2 node SMP currently writing to the same place on both nodes. Assuming there is no contention when writing to the same actual physical disk, this shouldn't be a concern. But what if you are writing to the same disk in both nodes? Can you write to two diferent FileServer locations to get the max parallel performance? Another observation I would make is about where your FileServer is physically located. What's the network hop from DSS01 to it? Is it significant? This might impact your read/write performance from/to DSS01. Just some stuff to think about.
Question from question:
Can you write to two diferent FileServer locations to get the max parallel performance?
Can two locations be on a same server pointing to different folders ?
What are the best practices to follow when defining resource and scratch disk configuration in config file?
Should Descripter (header) must be local on datastage server and data files somewhere else?
Can you write to two diferent FileServer locations to get the max parallel performance?
Can two locations be on a same server pointing to different folders ?
What are the best practices to follow when defining resource and scratch disk configuration in config file?
Should Descripter (header) must be local on datastage server and data files somewhere else?
-
- Charter Member
- Posts: 299
- Joined: Wed Nov 13, 2002 5:38 pm
- Location: USA