Error message to compile a routine

chulett · Post by **chulett** » Tue Dec 23, 2003 7:39 am

Maria - it sounds like you have a permissions problem. Have you ensured that your groups and permissions are setup properly to support multiple users? For example, you need to uncomment the "umask" entry in your .rc startup script, typically called 'S99ds.rc' at this release, but its name and location can vary (slightly) with the version of UNIX. Also what group does your userid belong to? Hopefully the same primary group that your Administrator (dsadm) user was setup with.

I have a nice little document Ascential wrote on setting up DataStage for a multi-user environment, which I'd be glad to forward to you (or perhaps post it here), it details what needs done so you won't have problems like you are having.

raju_chvr · Post by **raju_chvr** » Tue Dec 23, 2003 7:53 am

Can you actually post it here if possible Craig. Even I need something like that as we are having plans to move our Server from Windows to UNIX.

hgalusha · Post by **hgalusha** » Tue Dec 23, 2003 2:33 pm

Specifically, the compiled object code will be in your project home (s/b $dshome/../<project_name>) in a file called DSU.BP.O - check the permissions on this file in particular and therein may lie your answer.

As in the earlier post, setting up the umask in the ds.rc is important to get the permissions correct from the start.

Hope this helps.

vsi · Post by **vsi** » Wed Sep 20, 2006 1:21 pm

Hi,

I am sick and tired of Datastage Repository Interface Error. It always comes now and then.

Only way I know is to delete the job/routine, import it again and try.

Most of the times it doesnt work. I am using admin account so no permission issues I guess.

a) I have bunch of routines, just now recently changed the name of one of the routines. Since then none of the routines get compiled and I get the error

DataStage Repository Interface

Code: Select all

Unable to Open File DSU_BP

I went in datastage directory and checked to find the permission and they were

Code: Select all

drwxrwxr-x

b) I am unable to delete a job from the project because of the error below

Code: Select all

Cannot Open File RT_BP676.O

I went in the datastage directory to check for permissions and RT_BP676 doesnt exist at all.

How do I solve these problems. Apart from re-importing (as it is mostly failing)

is there anything like a restart on a PC

ray.wurlod · Post by **ray.wurlod** » Wed Sep 20, 2006 3:20 pm

Have you thought that RT_BP676.O may not exist because you do not have permission to create it?

Are you in the group associated with the project directory? If not, the permissions string you posted indicate that you can not change the contents of the project directory.

vsi · Post by **vsi** » Mon Sep 25, 2006 6:19 am

Have you thought that RT_BP676.O may not exist because you do not have permission to create it?

I was wondering why datastage is looking for a file which doesn't exists. What should be done in this scenario. The file isnt in the project directory and datastage says Unable to open RT_BP676.O

Are you in the group associated with the project directory? If not, the permissions string you posted indicate that you can not change the contents of the project directory

Yes, I am in the group associated with the project directory.

Code: Select all

Unable to Open File DSU_BP

How do I over the above error, its not allowing me to write any routine.[/quote]

Will rebuilding repository index help in anyway??

kumar_s · Post by **kumar_s** » Mon Sep 25, 2006 6:28 am

It is a file which Datastage will insert the runtime informations. IF the file doesnt present, DataStage will create one, according to the Routine number.
If you were sure that, all you routines were not responding recently, check in other projects with the same user id/ diffrent user id.
You can give a try with Reindexing as well. If the problem persist with other projects with the same user, you may need to go through the permission settings of that user once again.

vsi · Post by **vsi** » Mon Sep 25, 2006 6:38 am

By routines, not working, I meant they are not getting compiled. When the jobs are run, they are able to call the routines.

I checked with other projects and the routines are getting compiled very well. Only this project is giving trouble. Not only with routine, but also the jobs. Some of the jobs.

I have just rebuild repository indexes, but doesn't work

kumar_s · Post by **kumar_s** » Mon Sep 25, 2006 6:47 am

Alright, before proceeding further, take a back of the whole project. Do a unix backup as well.
Try to import some of the jobs in other project and check, if that work.
If that works, you can try to to a COUNT on the project hash files to ensure that, they were in accsseble state without any error. Else you may need to try to FIX the UV FILE.

vsi · Post by **vsi** » Mon Sep 25, 2006 7:09 am

Alright, before proceeding further, take a back of the whole project. Do a unix backup as well.

By Unix Backup, do u mean physical copy of entire project directory contents?

Try to import some of the jobs in other project and check, if that work.

It works in other project, when i import

If that works, you can try to to a COUNT on the project hash files to ensure that, they were in accsseble state without any error. Else you may need to try to FIX the UV FILE.

a How can I do the Count on the project hash files and how can I check whether they are in accessible state???
b) How can I fix the UV File???

Mike · Post by **Mike** » Mon Sep 25, 2006 7:50 am

Hi vsi,

It sounds like you have some residual project corruption due to filling up your project directory (a prior thread of yours). Ken advised you to create a new project at that time. You should heed that advice now.

Mike

vsi · Post by **vsi** » Mon Sep 25, 2006 8:04 am

Yes I am doing that right now :D.

But as well want to have old project name. For time being I will continue to work on a new project, then later on try to retain the old name, by removing the old project.

Thanks

kumar_s · Post by **kumar_s** » Mon Sep 25, 2006 7:28 pm

vsi wrote:Yes I am doing that right now :D.

But as well want to have old project name. For time being I will continue to work on a new project, then later on try to retain the old name, by removing the old project.

Thanks

You got the safest approach. :D