Building Package Timeout
Posted: Tue Feb 03, 2015 10:23 am
I'm using IS Server Manager to build a package for later sending to a prod environment. After defining a package, randomly when I build I get a timeout exception.
Also I don't know if this is related to my timeouts, sometimes when a package is sent to my prod environment (using the istools.sh utility to import the package from the command line) when the jobs go to run datastage says it's not in a runnable state. No matter how many times the package is redeployed and is proven to be runnable in dev, the only thing that I can do to get it to run in prod is to compile.
I realize all this is very obscure and is hard to know what is going on when you can't see my environment config. I'm just throwing this out there hoping that maybe someone can share their insights setting up a dev/prod workflow and how they had to configure their environment.
Also I don't know if this is related to my timeouts, sometimes when a package is sent to my prod environment (using the istools.sh utility to import the package from the command line) when the jobs go to run datastage says it's not in a runnable state. No matter how many times the package is redeployed and is proven to be runnable in dev, the only thing that I can do to get it to run in prod is to compile.
I realize all this is very obscure and is hard to know what is going on when you can't see my environment config. I'm just throwing this out there hoping that maybe someone can share their insights setting up a dev/prod workflow and how they had to configure their environment.