Hello Eydie,

We had a similar problem, not with an Oracle agent but with an other adsm-api
based application. The way we resolved it was to change not the UID of the
servertask, but the UID of the client task. Try changing the rights of the
backup executable to owner root with the SUID set. The "rest" can almost always
be done with some extra group ( or adding dba as secondary group to the root
user ) and setting some SGID bits on log directories or your ADSM pipe .... (you
have to investigate ...).
By the way: using the SHM communication REALLY speeded up our application ( +
500 % or something like that ).

herfried




ecaren <ecaren AT PRODIGY DOT NET> on 24.08.99 00:27:34

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



 To:      ADSM-L AT VM.MARIST DOT EDU

 cc:



 Subject: SHAREDMEM









In our environment, ADSM 3.1, is started out of /etc/inittab using TCPIP as the
communications method.  I would like to enable sharedmem, since the client and
server reside on the same system.  However, the Oracle raw logical volume
backup, performed by the Oracle dba id, group dba, using adsmpipe, fails.  I
assume it is because the shared memory area is restricted to the root user.  I
read TechDOc #8152859, "Non-Root User Running the ADSM Server", but do not want
the Oracle id to start ADSM.  If I change the group id to "dba" with the
appropriate permissions for the files mentioned, will this resolve my problem?

Eydie Caren
ecaren AT prodigy DOT net
Tel:  (914)448-8378
Pager:  1(800)352-4731