CNFIG.APT

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
king999
Participant
Posts: 7
Joined: Thu Sep 29, 2005 3:46 pm

CNFIG.APT

Post by king999 »

hi
iam trying to work on a standalone system and trying to compile a simple parallel job my config .apt and error are below
can i run parallel job on my system which is 3ghz and 512 ram and has server and client on it
:?




{
node "node1"
{
fastname "KING"
pools ""
resource disk "C:/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "" }
}
}

:? ##I TFCN 000001 12:03:36(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved


##I TOSH 000002 12:03:36(001) <main_program> orchgeneral: loaded
##I TOSH 000002 12:03:36(002) <main_program> orchsort: loaded
##I TOSH 000002 12:03:36(003) <main_program> orchstats: loaded
##W TCOS 000049 12:03:36(004) <main_program> Parameter specified but not used in flow: DSProjectMapName
##I TFSC 000001 12:03:36(009) <main_program> APT configuration file: C:/Ascential/DataStage/Configurations/default.apt
##W TFPM 000147
**** Startup error on node1 connecting with conductor on VAMSHI with cookie 1128711816.987000.eb0: unable to connect to port 10000 on conductor; socket = 3, Connection timed out retries left: 3
>##E TFPM 000152 12:04:07(000) <main_program> Accept timed out retries = 4
>##E TFPM 000141 Timeout in step setup on node node1
>##E TFPM 000152 12:04:37(000) <main_program> Accept timed out retries = 3
>##E TFPM 000153 12:04:37(001) <main_program> The section leader on VAMSHI died
>##E TFPM 000356 12:04:37(002) <main_program>
>
>**** Parallel startup failed ****
>
>This is usually due to a configuration error, such as
>not having the Orchestrate install directory properly
>mounted on all nodes, rsh permissions not correctly
>set (via /etc/hosts.equiv or .rhosts), or running from
>a directory that is not mounted on all nodes. Look for
>error messages in the preceding output.
>
>
##I TFPM 000177 12:04:37(003) <main_program> Step started on node VAMSHI; it uses 1 nodes.
The program running the step is /C=/Ascential/DataStage/PXEngine/bin/osh.exe.

##I TFPM 000178 12:04:37(004) <main_program> The ORCHESTRATE startup program in /C=/Ascential/DataStage/PXEngine/etc/standalone.sh is being used.

##I TFPM 000181 12:04:37(005) <main_program> A startup script is not being used.

##I TFPM 000183 12:04:37(006) <main_program> The TCP port being used for startup is 10000; the associated socket number is 3.

##I TFPM 000184 12:04:37(007) <main_program>
Node status:


##I TFPM 000185 12:04:37(008) <main_program> VAMSHI -
##I TFPM 000187 12:04:37(009) <main_program> rsh issued, no response received


>##E TFPM 000247 12:04:37(010) <main_program> Unable to contact one or more Section Leaders.
>Probable configuration problem; contact Orchestrate system administrator.
>
>##E TFSR 000011 12:04:37(011) <main_program> Step execution finished with status = FAILED.
##I TCOS 000026 12:04:37(012) <main_program> Startup Time 1:01 Production Run Time 0:00
track_star
Participant
Posts: 60
Joined: Sat Jan 24, 2004 12:52 pm
Location: Mount Carmel, IL

Post by track_star »

It looks like there are some discrepancies between your fastname and the host name the the conductor is running on. Check to make sure you can resolve "KING" from a command line (try pinging it), and/or check the output from uname -n.

As for your first question, I wouldn't suggest it. The framework takes up quite a bit more memory than what you have available. I have 1GB on my laptop, and it seems to work fine on relatively small jobs. The manuals suggest 2GB per CPU, but that's usually only necessary when you are performing large sorts or lookups.
Post Reply