Record CustomPX_1 on file DS_STAGETYPES cannot be written

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Rubu
Premium Member
Premium Member
Posts: 82
Joined: Sun Feb 27, 2005 9:09 pm
Location: Bangalore

Record CustomPX_1 on file DS_STAGETYPES cannot be written

Post by Rubu »

Hi All

I am trying to create a Custome operator (CustomPX_1) in DS Manager. While Saving the detail it gives the following error.
Record CustomPX_1 on file DS_STAGETYPES cannot be written
Is there any issue with the access for my user ID. Do we need manager access for creating New Parallel Stages?
Regards
Palas
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You need read, write and execute permission to DS_STAGETYPES and read and write permission to the three files within it (DATA.30, OVER.30 and .Type30). Actually you don't need write permission to the .Type30 file.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Rubu
Premium Member
Premium Member
Posts: 82
Joined: Sun Feb 27, 2005 9:09 pm
Location: Bangalore

Post by Rubu »

It looks I have permission to write in DS_STAGETYPES. Following is the output of the ls command.
-rwxrwxr-x 1 dsadm dstage 26624 2008-05-05 14:15 DATA.30*
-rwxrwxr-x 1 dsadm dstage 10240 2008-04-24 12:22 OVER.30*
-rwxrwsr-x 1 dsadm dstage 0 2007-08-28 17:22 .Type30*
Can there be any other reason?

This is happening for all the projects in the same DS sever.
Regards
Palas
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Are you actually connecting as dsadm or as a member of the dstage group?

Is the file system full?

Is the DS_STAGETYPES hashed file corrupted (check with UVFIXFILE)?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply