NFS Mount - How Can I grant read/write acess to a specific user?

This is on a Sun Solaris 10 system.

/etc/exports doesn't exist.

When I try and mount as oracle I get the following error:
nfs mount: insufficient privileges

if the /etc/exports file does not exits then there are no exports.
Please read up on the following;
http://www.linuxdocs.org/HOWTOs/NFS-HOWTO/interop.html

the layout of the linux & sunos version are the same.

if the root account is used to mount then the root user will enter the remote system as nobody. (this is a safety precaution).
See man 5 exports for details.

The issue is that the user ids for the "oracle" user is different on each server. I noticed this when I created my mount on the remote server. Is there anyway to get around this issue?

BTW, on Solaris 10, shares are defined in /etc/dfs/dfstab, not /etc/exports.  It does the same thing, but the implementation is quite different.

On Linux, you can use a trick to map *any* connecting user to the uid you want (anon flag), but that's pretty dangerous and undesirable.

Follow noci's advice (although I'd add the -h flag to chown so linked-to files can't get screwed up) to change the uid and gid on the *mounting* server, along with the relevant entries in /etc/passwd & /etc/group.

For example, the server were you've set up the shares, the 'oracle' user has a uid & gid of 1010.  On the new/mounting server, user 'oracle' has a uid & gid of 1040, you need to switch over everything to uid/gid 1010:

find /data/oracle -user 1040 -exec chown -h 1010 '{}' \;
find /data/oracle -group 1040 -exec chgrp -h 1010 '{}' \;
find /tmp -user 1040 -exec chown -h 1010 '{}' \;
find /tmp -group 1040 -exec chgrp -h 1010 '{}' \;
find /var/tmp -user 1040 -exec chown -h 1010 '{}' \;
find /var/tmp -group 1040 -exec chgrp -h 1010 '{}' \;
vi /etc/passwd   (change the two "1040"s in user oracle's line to "1010")
vi /etc/group     (change the one occurrence of "1040" in group oracle's line to "1010")

Kill any processes user 'oracle' may be running on the new/mounting server (reboot if possible - not necessary, but if you don't know what's going on on your system, its the best thing to do).

If you change all this on the new/mounting server, you shouldn't need to make any changes on the original/sharing server to the oracle tables.

NOTE - if the uid/gid of oracle is already being used on the new server (in my example, uid/gid 1010 is already used, let's say be user "bob"), then you'll most like have to change *that* user's files and system files (in /etc) to an unused uid before you do all this.  Otherwise, user "bob" might be able to access all of the oracle data.