cancel
Showing results for 
Search instead for 
Did you mean: 

Identity Management Dispatcher Cannot be Started

Former Member
0 Kudos

Dear SAP Experts,

I have problem with start dispatcher of identity management. When i click Start button, the status of dispatcher was not changed. The status still stopped.

Content of log file MxDispatcherPrelog_Prelog.log:

[28.07.2016 14:04:34-137] - INFO - Prelog - First prelog line

[28.07.2016 14:04:34-845] - INFO - Prelog - Initialization done

[28.07.2016 14:04:34-847] - INFO - Prelog - Full dispatcher identifier:idm@[hostname]/[ip address]:1469689474847:147606

[28.07.2016 14:04:34-847] - INFO - Prelog - Dispatcher identifier prefix:idm@[hostname]/[ip address]

[28.07.2016 14:04:34-858] - TRACE - Prelog - Executing: GET_DISPATCHER #FieldsToReturn:null #Params:[idm] #InClause:[idm] #OrderBy:null

[28.07.2016 14:04:34-860] - DEBUG - Prelog - STATEMENT PREPARED: SELECT * FROM MC_DISPATCHER  WHERE MACHINE=?  PARAMETERS: idm

[28.07.2016 14:04:34-870] - TRACE - Prelog - Succesfull execution: GET_DISPATCHER

[28.07.2016 14:04:34-870] - INFO - Prelog - No dispatchers with this name (idm) appear to be running! Cleaning all existing semaphores (starting with null)

[28.07.2016 14:04:34-874] - TRACE - Prelog - Calling   SP: MC_CLRX_OWN_SEMA #InputParams:[441, ]

[28.07.2016 14:04:34-874] - TRACE - Prelog - Preparing SP: MC_CLRX_OWN_SEMA

[28.07.2016 14:04:34-897] - TRACE - Prelog - Executing SP: MC_CLRX_OWN_SEMA

[28.07.2016 14:04:35-377] - ERROR - Prelog - Key:MC_CLRX_OWN_SEMA - SQL Exception: No authorized routine named "MC_CLRX_OWN_SEMA" of type "PROCEDURE" having compatible arguments was found.. SQLCODE=-440, SQLSTATE=42884, DRIVER=4.19.49

[28.07.2016 14:04:35-379] - FATAL - Prelog - Preparing dispatcher failed: No authorized routine named "MC_CLRX_OWN_SEMA" of type "PROCEDURE" having compatible arguments was found.. SQLCODE=-440, SQLSTATE=42884, DRIVER=4.19.49

The configuration IC Admin configuration

The connection string for <prefix>_admin: jdbc:db2://[hostname]:52222/ic_db!!!user=ic_admin;password=********;currentSchema=IC_OPER;currentFunctionPath=ic;maxStatements=100;retrieveMessagesFromServerOnGetMessage=true;

I still not sure for currentFunctionPatch value is correct or not. I put 'ic' for that value.

Please help to give me suggestion how to solve this error.

Thanks & best regards,

Husin

View Entire Topic
Former Member
0 Kudos

We have an environment that works on SQL. Part of the issue that i have seen when setting up the Dispatcher was the SQLJDBC driver should be compatible. Check if you had to specify any JDBC drivers when you configure the dispatcher and make sure the the JDBC driver is compatible.

Here are the steps i will follow to troubleshoot the issue.

1. go to dispatcherutil.bat and delete the existing dispatcher

2. create a new dispatcher

3. Check the appropriate JDBC driver and the location and map this in your configuration

4. Check JVMDLL and DSE Home Location

5. Connection String.. Database should be mxmc_db and user should be mxmc_admin and if there is a instance number for the server, do not specify the instance number

6.Update the dispatcher script with appropriate class path(In Service Scripts)

7.Restart the dispatcher.

Regards,

Harish

Former Member
0 Kudos

Dear Harish,

Thanks. It is not the JDBC Driver that caused the issue. It was Current Function path in connection string that was the issue.