Unix dispatcher not responsive

[Former Member]

Hello IDM Gurus,

Needed your assistance with an issue we're currently facing; We have set up a dispatcher within a UNIX server of ours using scripts generated through our MMC; we placed them on the UNIX server started the dispatcher and it apparently seems to be running fine (it even tested fine going into the job loop); but, when we start running actual jobs that are attached to the new dispatcher absolutely nothing happens; no errors and the jobs don't run; it's acting as though the job is disabled (even though they ARE enabled) or the dispatcher isn't even running (even though it is).

Any ideas/suggestions on how this could possibly be fixed? Are we overlooking anything obvious?

I would appreciate any help with the issue! Thanks in advance!

Best regards,

Sandeep

[mvoros · Accepted solution]

Have you tried to follow [this document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00e7da17-26a1-2c10-c5a7-b9886cbc2a14?quicklink=index&overridelayout=true] by SAP?

Cheers

[Former Member · Accepted solution]

Yes Martin, that is the same document we used to set up the Unix dispatcher; we went through it again step by step thinking we missed something but couldn't find anything wrong.

Cheers!

Sandeep

[Former Member · Accepted solution]

Hi Martin,

I was checking further here with the network team and they think that this might be a issue with the desktop on which MMC is installed not being allowed to send a request through to the UNIX server which resides behind a firewall.

They want to know what ports does the MMC use to send jobs back to dispatcher on UNIX so that they can try allowing access for those ports only.

Can you help us with this information please ? Thanks a lot in advance!

Cheers!

Sandeep

[mvoros · Accepted solution]

Hi Sandeep,

MMC and dispatchers do not communicate directly.Communication is done via database. MMC and dispatcher connect to DB via JDBC connection, get some data, do something and then write back result. So check if dispatcher can connect to DB.

Cheers

[former_member2987 · Accepted solution]

Sandeep,

What output do you get if you run the dispatcher in "test" mode?

Matt

[Former Member · Accepted solution]

Hi Martin / Matt,

Thanks so much for you timely responses/suggestions! Sorry for the delayed response from my end; When testing the dispatcher in UNIX, it seems to connect to the DB successfully; I get the following output:

[24.08.2011 14:36:37-720] - MxDispatcher:Reading prop files
[24.08.2011 14:36:37-720] - MxDispatcher:Loading driver: oracle.jdbc.driver.OracleDriver
[24.08.2011 14:36:37-889] - MxDispatcher:Creating connection to : jdbc:oracle:thin:mxmc_rt/**********@dev:1521:IDM
[24.08.2011 14:36:39-025] - MxDispatcher:Reading main MxDispatcher configuration ...
[24.08.2011 14:36:39-079] - MxDispatcher:Starting dispatcher: MC-unixtest
[24.08.2011 14:36:39-083] - MxDispatcher:Started thread:MC-unixtest
[24.08.2011 14:36:39-083] - MxDispatcher:Executing 'getWaitingjobs'
[24.08.2011 14:36:39-091] - MxDispatcher:Started thread:MC-if-unixtest
[24.08.2011 14:36:39-092] - MxDispatcher:Executing clear old semas from IFCheck
[24.08.2011 14:36:39-096] - MxDispatcher:Executing set sema from IFCheck
[24.08.2011 14:36:39-096] - MxDispatcher:Policy type is :0
[24.08.2011 14:36:39-101] - MxDispatcher:Executing 'listSuitableTasks'
[24.08.2011 14:36:39-101] - MxDispatcher:[Evaluations] - trying to list tasks
[24.08.2011 14:36:39-111] - MxDispatcher:No tasks found ... nothing to do
[24.08.2011 14:36:39-111] - MxDispatcher:[Evaluations] - none
[24.08.2011 14:36:39-112] - MxDispatcher:Executing clear sema (44) from IFCheck
[24.08.2011 14:36:39-304] - MxDispatcher:Nothing to do. Sleeping ...
[24.08.2011 14:36:39-641] - MxDispatcher:[Executions ]  - none:
[24.08.2011 14:36:44-312] - MxDispatcher:Executing clear old semas from IFCheck
[24.08.2011 14:36:44-317] - MxDispatcher:Executing set sema from IFCheck
[24.08.2011 14:36:44-318] - MxDispatcher:Policy type is :0
[24.08.2011 14:36:44-321] - MxDispatcher:Executing 'listSuitableTasks'
[24.08.2011 14:36:44-321] - MxDispatcher:[Evaluations] - trying to list tasks
[24.08.2011 14:36:44-329] - MxDispatcher:No tasks found ... nothing to do
[24.08.2011 14:36:44-329] - MxDispatcher:[Evaluations] - none
[24.08.2011 14:36:44-329] - MxDispatcher:Executing clear sema (44) from IFCheck
[24.08.2011 14:36:44-369] - MxDispatcher:Nothing to do. Sleeping ...
[24.08.2011 14:36:44-692] - MxDispatcher:Executing 'getWaitingjobs'
[24.08.2011 14:36:44-707] - MxDispatcher:[Executions ]  - none:
[24.08.2011 14:36:49-372] - MxDispatcher:Executing clear old semas from IFCheck
[24.08.2011 14:36:49-377] - MxDispatcher:Executing set sema from IFCheck
[24.08.2011 14:36:49-377] - MxDispatcher:Policy type is :0
[24.08.2011 14:36:49-381] - MxDispatcher:Executing 'listSuitableTasks'
[24.08.2011 14:36:49-381] - MxDispatcher:[Evaluations] - trying to list tasks
[24.08.2011 14:36:49-388] - MxDispatcher:No tasks found ... nothing to do
[24.08.2011 14:36:49-389] - MxDispatcher:[Evaluations] - none
[24.08.2011 14:36:49-389] - MxDispatcher:Executing clear sema (44) from IFCheck
[24.08.2011 14:36:49-427] - MxDispatcher:Nothing to do. Sleeping ...

Still a little puzzling seeing that it connects to the DB successfully; we are currently looking into possible port issues also.

Any ideas?

Cheers!

Sandeep

[mvoros · Accepted solution]

Maybe stupid question but are you sure that you are connecting to proper DB? Development vs. production? Maybe you can try to check logs on DB server if it gets any connection from this host and maybe temporary increase log level to see what queries are executed.

Cheers