Dollar Universe can't launch the command in the uproc with oracle connection

Products

• CA Automic Dollar Universe

Issue/Introduction

Error Message :
in the universe.log 

###############
2014-10-14 08:55:07 |ERROR|X|IO |pid=16084.138862| o_Auth_ILocal_OWLS_Check_ | Error checking key /work/app/orsyp/orsyp_SC4/DUAS/CARRE4_SC4_PRO/data/exp/lo
cal/itmiz101_bs_oracle.key (255)
| 2014-10-14 08:55:07 |ERROR|X|IO |pid=16084.138862| o_Auth_ILocal_OWLS_Trt_Ke | o_Auth_ILocal_OWLS_Check_File returns error [-1]
###############  

Patch level detected:Dollar Universe 6.2.00
Product Version: Dollar.Universe 6.2.0

Description :Dollar Universe can't launch the command in the uproc with oracle connection

Cause

Cause type:
Configuration
Root Cause: Impossible to an "admin user" in that case univadm to do an uproc with oracle connection.
this user "admin "was not recognized by the Dollar Universe installation.

Environment

OS: All Unix
OS Version: Unix/Linux

Resolution

You have to do the installation with user root - As defined within the documentation of installation
Execute the command :
./uxrights -m assign -a root
With the node stopped
------------
If it’s a privileged installation, you can run the command :
./uxrights -m grant
This will give rights to the user of installation only.


[[email protected] bin]# ./uxrights -m assign -a root
DUAS environment loaded for Company EURPRD Node rabotest2.

#--------------------------------------------------
# Starting DUAS uxrights procedure.
# --------------------------------------------------

Checking if instance is stopped...
.
# ------------------------------------------------------------------------------------------------------
# DUAS instance ("EURPRD", "rabotest2") is stopped.
# ------------------------------------------------------------------------------------------------------
--> executing : chown -h root:0 /apps/du/600/EURPRD_rabotest2
...

#---------------------------------------------------------
# End of DUAS uxrights procedure with success.
# --------------------------------------------------------

Fix Status: No Fix
 

Additional Information

Workaround :
N/A