APT_CONFIG_FILE - Wrong Server Name
Posted: Sun Feb 18, 2007 7:02 pm
I get the following error when I run a job. My project details are:
Project Name: METL_SIT_R1
Server Name: mellaswds01
The APT_CONFIG_FILE being used is as follows:
Any idea from where the new server name is being retrieved? Do i need to restart the DataStage engine?
Project Name: METL_SIT_R1
Server Name: mellaswds01
main_program: Fatal Error: An ORCHESTRATE program must be started on a node
in the configuration file. This program is running on MELLARWDS01
which is not in the configuration file: /datastage/Ascential/DataStage/Configurations/default.apt
The APT_CONFIG_FILE being used is as follows:
main_program: APT configuration file: /datastage/Ascential/DataStage/Configurations/default.apt
/* mellaswds01_11.apt - conductor, full, 2-node cluster */
{
node "node1"
{
fastname "mellaswds01"
pools "" "node1" "mellaswds01"
resource disk "/datastage/Datasets" {pools ""}
resource scratchdisk "/Scratch" {pools ""}
}
node "node2"
{
fastname "mellaswds01"
pools "" "node2" "mellaswds01"
resource disk "/datastage/Datasets" {pools ""}
resource scratchdisk "/Scratch" {pools ""}
}
node "node3"
{
fastname "mellaswds01"
pools "" "node3" "mellaswds01"
resource disk "/datastage/Datasets" {pools ""}
resource scratchdisk "/Scratch" {pools ""}
}
node "node4"
{
fastname "mellaswds01"
pools "" "node4" "mellaswds01"
resource disk "/datastage/Datasets" {pools ""}
resource scratchdisk "/Scratch" {pools ""}
}
}
Any idea from where the new server name is being retrieved? Do i need to restart the DataStage engine?