APT_CONFIG_FILE - Wrong Server Name

[durgaps]

I get the following error when I run a job. My project details are:

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?

[kumar_s]

Are you sure that you are using default.apt?
And are you not using any other file like, mellaswds01_11.apt?
Do a grep on the location /datastage/Ascential/DataStage/Configurations/ to check if any files have the value of fastname as MELLARWDS01?
What is the value of the command uname -n on the server?

[ray.wurlod]

Simple misspelling.
The host name is MELLARWDS01.
The fast name is MELLASWDS01.

[kumar_s]

You servername should be MELLARWDS01 and not mellaswds01.

[durgaps]

In fact I am using default.apt which has a symbolic link to mellaswds01_11.apt.

BTW, the issue is solved. The configuration file was using MELLARWDS01 as the head node before it was changed
by the admin to use MELLASWDS01. The DataStage engine had to be restarted(uv -admin -stop/-start) to make the
changes active.

I just need to know one thing,

why do we need to restart the engine for the changes to take effect.

Because when I ran the job(before the DS engine restart) it picked up the latest contents of the config file, as was evident from the log.

[kumar_s]

No, it was using MELLASWDS01 and pointing that the current host name is MELLARWDS01.

[ray.wurlod]

Probably time to mark the thread as resolved, then.