Missing Source file in a job DI studio(9.1.3)

[venkatesh]

Hi Team,

Here i have a source file called A(CSV external file).

Created Job(abcd) and loaded my target table successfully based on external file as source.
and created one more job(abcd1) and used as same external file as a source run the job and job successfully run and loaded data into target table.

now the problem is if i open first job (abcd) the source file is missing.
Here my doubt is source file can't use more than a job. or
Is there any problem with installation. or
Is there any other problem.

How can i achieve this problem if i run both jobs and source file has to be available in both jobs.

[DanielSantos]

Very strange behavior...

I'm not aware that a file can only be shared on a single job/target table...
Unless there is some kind of file lock issue, but both jobs are acessing the file for read access, right?
On what kind of system is the workspace server running?

Which version of DIS are you running?

Greetings from Portugal.

Daniel Santos at www.cgd.pt

[venkatesh]

Hello Daniel,

Am using DIS version 3.4

Dont know what i have to do to resolve this issue.
There is no problem with lock issue because after completing first job then only am using for second.


Help would be a great

[deleted_user]

Hi,

I am encoutering the similar problem.

we have an extraction job that was running well last week and when we opened this job today the source files are missing. Just want to ask if you guys have a resolution for this?

Thank you.

Cheers!

JZ Message was edited by: JZ

[milts]

Hi,

Have you applied the latest hotfix for DI Studio?

Not sure if this solves the issue.

Regards,
Milton

[deleted_user]

Hi Milton,

Thanks for the reply.

Forgot to mention that we are using SAS9.2 and DI 4.2 with latest hotfix.

Cheers!

JZ

[LinusH]

We have encountered some problems linked with external files and partial promotion.
It seems that external files needs to be in same package file as the job.
Are you using change management (check-out/check-in)?
If so, it could be a similar problem (under the "hood").
Maybe it would be worth open a track to SAS tech support.

/Linus