Check db2 client latency with db2 database

 Check db2 client latency with db2 database

If you wanted to check latency of db2 client hosted on Linux vs db2 database hosted on Mainframe , you will usually perform ping <db2 hosting host> from client server and that will give response time. 

However if you are not satisfied with response time and think it takes more time then it is probably because of multiple hops between db2 client server and db2 hosting database servers. Usually these servers gateway servers and configured in db2 catalog in nodes. 

How to test actual query response time.

Perform following steps from server where you have indirect/gateway server configured in db2 client catalog nodes.

1. Open the DB2 Command Window: Click Start, navigate to IBM Db2, and select "DB2 Command Window Administrator"
2. Create SQL File: Create a file named test.sql in a local directory (e.g., c:\temp\test.sql) containing your SQL statement (e.g., SELECT * FROM schema.table;).
3. Run db2batch:

db2batch -d DBNAME -f "c:\temp\test.sql" -a dbid/password -i complete

This will give following response with query result.

* Prepare Time is:       0.032398 seconds

* Execute Time is:       0.028289 seconds

* Fetch Time is:         0.000837 seconds

* Elapsed Time is:       0.061525 seconds (complete)

Now perform above steps from server where you have configured db2 hostname in catalog nodes. Whatever complete time difference you observe will be latency.

Reconfigure nodes appropriately for performance improvement.  Comment on blog if you looking for additional information. 

PeopleSoft Journal upload template giving error

 PeopleSoft Journal upload template giving error 

Following warning gets generated while performing transaction through PeopleSoft upload spreadsheet which do not allow to upload the data.

Solution -

1. Check the connection details , select any two sheets of spreadsheet ->right click and select unhide . This will show connection settings.

2. If url is HTTP based then contact your security team to allow unsecured traffic and disable encryption. This situation is has worked most of the cases however you can take security considerations before changes.

ERROR: Jolt client (ip address X.X.X.X) does not have proper application password. PeopleSoftTargetConnector - The appserver may be down. Check Appserver URL or Domain Password. (158

    ERROR: Jolt client (ip address X.X.X.X) does not have proper application password

Ping local node from Integration Gateway properties or directly from Integration Broker -> nodes.

Error observed in tuxlog file of PeopleSoft application server logs.

ERROR: Jolt client (ip address X.X.X.X) does not have proper application password. PeopleSoftTargetConnector - The appserver may be down.  Check Appserver URL or Domain Password. (158 

Even though configuration.properties domain password matching with app server domain password this error is occurring. 

Solutions --->

1. Remove and update domain password from psappsrv.cfg of app server domain and reconfigure App server domain. Test the local node. 

If still did not work

2. Remove domain password from Integration Gateway properties application server node details. Also remove it from psappsrv.cfg of app server domain and reconfigure App server domain. Test the local node.

2nd option fixed issue for me.