DSXchange

Hi friends,

starting the agents

Sh DSAppWatcher.sh -start all
Which: no DSAppWatcher.sh in (/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/ Home / dsadm / bin)
EngMonApp: STARTING
ODBQueryApp: STARTING
ResMonApp: STARTING

Even when I start the datastage console, I get the error:

DSODB is started but DSAppWatcher is not running for the selected engine (TCIBM.CCSGR3000.LOCAL).


I run the command to test the applications, and it shows that everything is ok

Sh DSAppWatcher.sh -test
Which: no DSAppWatcher.sh in (/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/ Home / dsadm / bin)
DSODB is ON in the DSODBConfig.cfg file.
Link monitoring is OFF.
Use of job execution is ON.
Resource monitoring is ON.
Checking database connection:
Controller: com.ibm.db2.jcc.DB2Driver
Connection URL: jdbc: db2: //TCIBM.CCSGR3000.LOCAL: 50000 / xmeta
The database driver has been successfully loaded.
Successfully connected to the database.
Outline: DSODB
BD Schema Version Number: 2
Satisfactory test.


Any idea of this error?

How many engine tier machines do you have controlled by the one services tier? You need to make sure that the services are started on ALL of the engine tier machines.

Hello ray.wurlod, I only have a machine with a engine tier, additional I commented that, my platform / suite of infosphere is integrated in a server (app, repository, engine).

The first line of your message is of concern.
( Which: no DSAppWatcher.sh in (/usr/lib64 ... )

Which path are you running this from?

I'm getting the following from ibm/infosphere/InformationServer/Server/DSODB

./bin/DSAppWatcher.sh -test
DSODB is turned ON in the DSODBConfig.cfg file.
Link Monitoring is OFF.
Job Run Usage is ON.
Resource Monitoring is ON.
Checking Database Connection:
Driver: com.ibm.isf.jdbc.oracle.OracleDriver
Connection URL: jdbc:ibm:oracle://gf0zsxdb129e:1521;SID=INFINTE
Successfully loaded the database driver.
Successfully connected to the database.
Schema: dsodb
DB Schema version number: 2
Test Successful.

Hi,
I have the same problem. The problem happens since I changed the IP to the Engine Server. Could they solve it?
thanks

vatranos wrote:Hi,
I have the same problem. The problem happens since I changed the IP to the Engine Server. Could they solve it?
thanks

Welcome.
Please advise the version of InfoSphere Information Server that you are running, and the platform on which it is running. If these are not the same as the original poster, you don't "have the same problem".