Changes required to move pipeline software and utilities to new Production Oracle server, GLASTP, from shared server SLACPROD:

Since all pipeline utilities use the same perl connection module the required changes are minimal. In addition there are two configuration scripts that need to be modified to reflect the new server alias. This alias is always used in place of the server name which could change in the event of a server hot swap. The connection module generally uses the environment variable set by these configuration scripts unless passed a specific value during instantiation. Thus the only required change to PDBConnect.pm is to replace the default server alias that is used if no value is passed and the $TWO_TASK environment variable is null.

~glast/pdb_config/dpf_config_prod.csh

Update value of $TWO_TASK env var to reflect new server alias:

setenv TWO_TASK SLACPROD
setenv TWO_TASK GLASTP

~glast/pdb_config/dpf_config_prod.sh

Update value of $TWO_TASK env var to reflect new server alias:

export TWO_TASK=SLACPROD
export TWO_TASK=GLASTP

DPF/PDB/PDBConnect.pm

Update value of $TWO_TASK env var to reflect new server alias:

# If all else fails, assign a default
# Use production DB for backward compatibility with older code...
# we used to have only SLACPROD, so no parameters were passed.
$two_task = "SLACPROD" unless defined($two_task);
$two_task = "GLASTP" unless defined($two_task);