DS Designer Hangs during Job compilation

psluser · Post by **psluser** » Wed Jul 09, 2008 5:35 am

Hi,

Our DS Designer is hanging during compiling of jobs. Jobs were working fine till yesterday, but now whenever we try to compile a job it shows : "compilation in progress, please wait.." and then DS Designer hangs. This is happening from different clients connected to the same server.

We tried deleting &PH& folder contents, but no help.

Please suggest.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 09, 2008 5:50 am

Obvious question: what changed between yesterday and today? (Note: "nothing" is not the correct answer.)

sunayan_pal · Post by **sunayan_pal** » Wed Jul 09, 2008 6:07 am

Hi ,

Are you working on the test server.
if so then do one thing if u have the backup of that job. then delete the existing and import the job from the previous backup from the .dsx file.
in my case this export and import had resolve the issue.

psluser · Post by **psluser** » Wed Jul 09, 2008 7:29 am

We just noticed that we are able to compile the copy of old jobs. So, while compiling of old jobs hangs DS Designer, compiling of a copy of old jobs(without any modification) works fine!!

Any idea about this strange behavior.

ArndW · Post by **ArndW** » Wed Jul 09, 2008 11:24 am

Probably locks of some kind. If you have a small project and access to root/dsadm, then shutting down and restarting Datastage might be your quickest solution.

kcbland · Post by **kcbland** » Wed Jul 09, 2008 12:16 pm

Smells like permissions have changed. If the job object files are owned by others or groups you may have some sticky bit situations or someone changed group level permissions.

psluser · Post by **psluser** » Thu Jul 10, 2008 9:16 am

ArndW, shutting DS server down and restarting the machine also didn't help.

kcbland, we are using same windows local user to connect to DS. Ours is a small team and each user use the same username/pwd to connect to DS; since different developers are working on different jobs it has not caused any issues till now.

We are moving ahead by creating copies of old jobs but just wanted to identify the cause of such behavior.

Can it be linked to date changes on the server machine? We put the system date back by one month for a few hours to test some date/time functionality. And the issue cropped during the same day, though I can not say it occurred at the same instant.