After upgrade to Applications Manager 9.3.2, awrun fails intermittently with No role access error
search cancel

After upgrade to Applications Manager 9.3.2, awrun fails intermittently with No role access error

book

Article ID: 203435

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

After upgrading to 9.3.2, awrun, may intermittently fails with a "no role access" error message even if the correct permission are in place or if the DBA User Group is assigned.

Error will look similar to the following error messages:

13:46:58.142 ASM1: .AgentSocketManager$_A: doRun 0 1825 null null java.sql.SQLException: ORA-20025: No role access to "Agent as "<AGENT_NAME>" rtype=N edit=N my_dba=N my useq=*-5-6 user_seq_to_check: -6
.2
13:46:58.142 ASM1: .AgentSocketManager$_A: doRun done 0 1825 null null java.sql.SQLException: ORA-20025: No
13:46:58.142 awserverWorker2: TRN:313: .AgentSocketManager: sendRequest: java.sql.SQLException
13:46:58.142 awserverWorker2: TRN:313: AwE-5501
13:46:58.142 awserverWorker2: TRN:313: SQL Error: 0
13:46:58.143 awserverWorker2: TRN:313: .AxOptions: NoErrorMsgProperties=false
ErrorMsg: AwE-5501 Error executing AwServer statement (6/7/20, 1:46 PM)
Details: 37 API_GEN FUNCTION 10000 0 23 exec_fn_in exec_fn_out
[so_login, bigline]
[result]

java.sql.SQLException: ORA-20025: No role access to "Agent as "<AGENT_NAME>" rtype=N edit=N my_dba=N my useq=*-5-6 user_seq_to_check: -6.2 user_seq_to_check: -9-11 all user_seq: 1: 2: 3: 4: awop: "
ORA-06512: at "APPWORX.AW5", line 116
ORA-06512: at "APPWORX.AWAPI2", line 4346
ORA-06512: at "APPWORX.AWAPI2", line 477
ORA-06512: at "APPWORX.AWAPI2", line 2921
ORA-06512: at "APPWORX.AWAPI2", line 3513
ORA-06512: at "APPWORX.AWAPI2", line 4018
ORA-06512: at "APPWORX.AWOP_API", line 732
ORA-06512: at "APPWORX.AW5", line 107
ORA-06512: at "APPWORX.AW5", line 54
ORA-06512: at line 1
ORA-06512: at "APPWORX.AWDYN", line 19
ORA-06512: at line 1

Environment

Release : 9.3.2

Component : APPLICATIONS MANAGER

Resolution

This issue is still being investigated for a permanent fix.

Workaround:

Add the following line into the awenv.ini file under the [default] section, save, and restart Agent:
DirectDBConnection=Y