Can anyone point us to some white papers, best practices or even DS documentation we may have missed that describes the best way to "port" a project with the least aggravation.
We probably did something wrong, but we were surprised that even an export and then import back to the original project folder created configuration problems that had to be addressed manually. We would appreciate any insight into what probably is a simple problem that displays our inexperience. Thanks!..
Dan Paolini
Export/Import/Moving Projects
Hi Dan.
If you have a few moments, check out the site www.tools4datastage.com . The folks there have built a Version Control product for DataStage whose most significant benefit is the deployment of entire "sets" of DataStage
application "pieces" amongst DS Servers.
Ascential supported this partners development of this product, and will soon be incorporating the product into DataStage directly as an Ascential offering.
Ernie
-----Original Message-----
From: Dan Paolini [mailto:daniel.paolini@oit.state.nj.us]
Sent: Monday, October 01, 2001 4:04 PM
To: datastage-users@oliver.com
Subject: Export/Import/Moving Projects
Can anyone point us to some white papers, best practices or even DS documentation we may have missed that describes the best way to "port" a project with the least aggravation.
We probably did something wrong, but we were surprised that even an export and then import back to the original project folder created configuration problems that had to be addressed manually. We would appreciate any insight into what probably is a simple problem that displays our inexperience. Thanks!..
Dan Paolini
If you have a few moments, check out the site www.tools4datastage.com . The folks there have built a Version Control product for DataStage whose most significant benefit is the deployment of entire "sets" of DataStage
application "pieces" amongst DS Servers.
Ascential supported this partners development of this product, and will soon be incorporating the product into DataStage directly as an Ascential offering.
Ernie
-----Original Message-----
From: Dan Paolini [mailto:daniel.paolini@oit.state.nj.us]
Sent: Monday, October 01, 2001 4:04 PM
To: datastage-users@oliver.com
Subject: Export/Import/Moving Projects
Can anyone point us to some white papers, best practices or even DS documentation we may have missed that describes the best way to "port" a project with the least aggravation.
We probably did something wrong, but we were surprised that even an export and then import back to the original project folder created configuration problems that had to be addressed manually. We would appreciate any insight into what probably is a simple problem that displays our inexperience. Thanks!..
Dan Paolini
Dan, youre going to have to be more specific.
Reimporting to the same project should never present a
problem, unless:
1. Permissions on a unix server has screwed you up.
If you guys dont have sticky bits set on project
directories, youre in different user groups and the
directory permissions arent playing nice. This could
be most of your problem.
2. Jobs were locked (either running or being
modified) at the time of your export or import.
Theres a bug in DS that if youre running an export
the jobs being exported will break at the point where
it hits a job that is locked (running or in Designer).
All of the remaining jobs in the alphatetically
sorted list are SKIPPED, giving you a partial export.
Ive got a bunch of stuff Ill send you, with a
DataStage Best Practices document you might want to
read that explains permissions, imports/exports, etc.
Good luck!
-Ken
--- Dan Paolini
wrote:
> Can anyone point us to some white papers, best
> practices or even DS
> documentation we may have missed that describes the
> best way to "port" a
> project with the least aggravation.
>
> We probably did something wrong, but we were
> surprised that even an
> export and then import back to the original project
> folder created
> configuration problems that had to be addressed
> manually. We would
> appreciate any insight into what probably is a
> simple problem that
> displays our inexperience. Thanks!..
>
> Dan Paolini
>
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com
Reimporting to the same project should never present a
problem, unless:
1. Permissions on a unix server has screwed you up.
If you guys dont have sticky bits set on project
directories, youre in different user groups and the
directory permissions arent playing nice. This could
be most of your problem.
2. Jobs were locked (either running or being
modified) at the time of your export or import.
Theres a bug in DS that if youre running an export
the jobs being exported will break at the point where
it hits a job that is locked (running or in Designer).
All of the remaining jobs in the alphatetically
sorted list are SKIPPED, giving you a partial export.
Ive got a bunch of stuff Ill send you, with a
DataStage Best Practices document you might want to
read that explains permissions, imports/exports, etc.
Good luck!
-Ken
--- Dan Paolini
wrote:
> Can anyone point us to some white papers, best
> practices or even DS
> documentation we may have missed that describes the
> best way to "port" a
> project with the least aggravation.
>
> We probably did something wrong, but we were
> surprised that even an
> export and then import back to the original project
> folder created
> configuration problems that had to be addressed
> manually. We would
> appreciate any insight into what probably is a
> simple problem that
> displays our inexperience. Thanks!..
>
> Dan Paolini
>
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com