Hi,
I've recently upgraded my environment to 9.01 on a W2K8 R2 cluster, and I've begun to notice some unusual behaviour.
We have an issue where a job seems to hang, yet the session drops out of the monitor context as if it has completed and is thus impossible to abort.
The sessions list in the Internal Database tab shows the job as running, however there are no corresponding BSM or CSM processes to be found on the CM's Task Manager.
The session logs of the affected jobs show no errors, they simply tail off, and the job itself doesn't time out after the usual interval.
The command omnistat only shows those sessions that are visible in Monitor.
Debug.log shows repeat entries of this message:
02/01/2015 13:29:34 RMA-NET.9060.4836 ["/ma/xma/rmanet.c $Rev: 41801 $ $Date:: 2014-03-26 16:29:59":161] A.09.00 b87
DbgStack: DbgFcnOut() and level already 0!
ExitFcn="MaProtocolCheck"
If anyone has seen this behaviour and has managed to get past it, I'd appreciate any advice they might have.
Thanks,
Bob
DP 9.01 on W2K8 Enterprise (with DPWIN_00711,712)
CM has 32GB/4*Quad-core CPU/10Gb Ethernet/4Gb SAN connectivity (3PAR storage)
