However, testing today - again without modification to the config file, i had a PX job max out all 8 procs and render the Server useless. We had to execute a hard reboot to recover. 4 gig of ram (out of 32) was used and swap space used was 0. The job had previously run successfully on the 4 way.
The job reads in 4 inputs from ORACLE, splits the data into peices, executes approximately 15 or so simultaneous lookups(both sparse and normal), then merges the data back together prior to writing to the target - a Data Set.
I have opened a ticket with IBM, but was hoping somone else had run into a similar problem. Is it a config file issue or some OS level setting that needs to be adjusted?
TIA
the config file used.
Code: Select all
{
node "node0"
{
fastname "etl00.xxxxx.org"
pools ""
resource disk "/usr/ETL/Flat-Files" {pools ""}
resource scratchdisk "/usr/ETL/Temp1" {pools ""}
}
node "node1"
{
fastname "etl00.xxxxx.org"
pools ""
resource disk "/usr/ETL/Flat-Files" {pools ""}
resource scratchdisk "/usr/ETL/Temp2" {pools ""}
resource ORACLE "node1" {pools ""}
}
node "node2"
{
fastname "etl00.xxxxx.org"
pools ""
resource disk "/usr/ETL/Flat-Files" {pools ""}
resource scratchdisk "/usr/ETL/Temp1" {pools ""}
resource ORACLE "node2" {pools ""}
}
node "node3"
{
fastname "etl00.xxxxx.org"
pools ""
resource disk "/usr/ETL/Flat-Files" {pools ""}
resource scratchdisk "/usr/ETL/Temp2" {pools ""}
}
}