Re: Trouble adding new dbspace

In article <5unq6d$fm7@news.informix.com>, Bill Glidden <glidden@informix.com> writes >Michael L. Gallagher (mgallagh@motown.lmco.com) wrote: >: I am having extreme diffculty adding a new dbspace to my environment here >(Solaris 2.5.1 and NIS+). I have setup Online Workgroup Server 7.20 on Solaris 2.5.1 and had the same problems you are having. Under Solaris 2.5.1 you will find that the raw device (E.g. /dev/rdsk/c0t1d0s0) must be mode 660, group informix user informix. However /dev/rdsk/c0t1d0s0 will be a link to ../../devices/sbus<somthing> i.e. /devices/sbus<something> this must also be mode 660, group informix user informix. Not only must permissions on the device you use for the chunk be correct but if it is a link the permissions on the thing the link points to must also be correct. First change the entry in /devices/sbus... then to change permissions on the link itself (/dev/rdsk/c0t1d0s0) use chmod -h and chgrp -h and chown -h. These change the permissions on the link itself rather than what it points to. >: onmonitor complains that informix is not the owner nor group of the files I >want to access (both >: cooked and raw). I have opened the permissions wide on both and it still >refuses. I thought it was >: a problem in how the raw device was set up, but I see that even a cooked file >cannot be added. Must >: I be root under NIS+ to do this? >: >It's not a matter of having permission to read/write the device. Informix >is looking for a specific permission (660) and specific ownership and >group (informix/informix by default). > >Change the permissions and ownership of your raw device as stated and >see if that helps. > >Also, check the group id of your oninit executable. oninit doesn't >really check to see if the owner/group of your chunk are informix/informix. >Rather it checks to see that the owner/group of your chunk match the >group id of the oninit executable. Since our installation process changes >the group id of oninit to informix, we document that your chunks must >have owner/group of informix. However, if your installation didn't go >quite right, or someone for some reason changed the group id, this could >be the problem as well. >(This was true at least in 7.1, can't state for sure about 7.2 or higher). -- David Williams