Job Monioring fails in designer
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 21
- Joined: Wed Aug 29, 2007 1:33 am
- Location: Bangalore
- Contact:
Job Monioring fails in designer
Hi,
On execution the job succeeds with status as OK. The data inserted is also fine. But in the designer, While executing, no information on the number of rows inserted is displayed. there is one warning in the director log,
Main_Program:Failed to initialize job monitoring. Monitor information will not be generated.
Can anyone help?
Thanks in advance.
On execution the job succeeds with status as OK. The data inserted is also fine. But in the designer, While executing, no information on the number of rows inserted is displayed. there is one warning in the director log,
Main_Program:Failed to initialize job monitoring. Monitor information will not be generated.
Can anyone help?
Thanks in advance.
Rudresh Eswarappa
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can help yourself. Find out why the job monitor is not starting by trying to start it and capturing any output, especially from stderr, and inspecting the same.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 28
- Joined: Sat May 03, 2008 3:57 am
- Location: chennai
We have this problem. Sometime, the JOBMON process ceases to run and must be restarted. It is still unknown why it stops but to quickly resolve the issue, I get the network admin to run a restart on the process and the problem is resolved. Before asking for a restart, check friend.kak solution to see if the monitor is set.
Jim Stewart
We are having same problem?Raftsman wrote:We have this problem. Sometime, the JOBMON process ceases to run and must be restarted. It is still unknown why it stops but to quickly resolve the issue, I get the network admin to run a restart on the process and the problem is resolved. Before asking for a restart, check friend.kak solution to see if the monitor is set.
Does anyone know how to to start job montor on windows?
TIA
-
- Premium Member
- Posts: 37
- Joined: Mon Dec 08, 2008 4:02 am
- Location: Milton Keynes, UK
Does anyone know how to to start job montor on windows?
One way is to run "jobmoninit start" from the PXEngine\java directory. In a command window, type something like:
Code: Select all
set APT_ORCHHOME=c:\ ... <wherever> \PXEngine
Code: Select all
set APT_ORCHHOME=C:\IBM\InformationServer\Server\PXEngine
Code: Select all
cd C:\IBM\InformationServer\Server\PXEngine\java
sh jobmoninit start
Another JobMonApp which was not started from C:\IBM\InformationServer\Server\PXEngine
is using ports in C:\IBM\InformationServer\Server\PXEngine/etc/jobmon_ports.
Modify jobmon_ports file to select unused ports and run jobmoninit start again.
I think that means it's already started - can't see any specific command to check if its running. If in doubt you could try:
Code: Select all
sh jobmoninit stop
sh jobmoninit start
Thanks for quick help.LenGreenwood wrote:Does anyone know how to to start job montor on windows?
One way is to run "jobmoninit start" from the PXEngine\java directory. In a command window, type something like:
e.g.Code: Select all
set APT_ORCHHOME=c:\ ... <wherever> \PXEngine
Followed by:Code: Select all
set APT_ORCHHOME=C:\IBM\InformationServer\Server\PXEngine
You may get a message such as:Code: Select all
cd C:\IBM\InformationServer\Server\PXEngine\java sh jobmoninit start
Another JobMonApp which was not started from C:\IBM\InformationServer\Server\PXEngine
is using ports in C:\IBM\InformationServer\Server\PXEngine/etc/jobmon_ports.
Modify jobmon_ports file to select unused ports and run jobmoninit start again.
I think that means it's already started - can't see any specific command to check if its running. If in doubt you could try:
Code: Select all
sh jobmoninit stop sh jobmoninit start
It worked.