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.

PeopleTools 8.51 error while copying project through application designer- check copy options (62,30)

 PeopleTools 8.51 error while copying project through application designer

Definition Name RECNAME.FIELDNAME.FieldFormula not copied, check copy options (62,30)

While copying application designer projects to other database, if you receive an error like this:

Definition Name RECNAME.FIELDNAME.FieldFormula not copied, check copy options (62,30)

It means that you did not selected the language type Common  in your project copy options. This can happen if in the copy dialog, the user selects options and then selects a specific language (e.g. English).

Note this setting can continue to apply to a project even if another person is performing the copy. Behind the scenes this setting is stored in the PeopleTools table,PSPROJECTSEC

If it still did not work then select "Select All' If you are using multilingual database

Change Assistant unable to connect target database

Change Assistant unable to connect target database

While configuring change assistant with target database it is failing to query database and does not show any error message.

PeopleTools 8.60

Resolution 

Make sure you have updated tnsnames.ora with target database details in Oracle 19c client present in db folder of dpk and in oracle client. 

CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

After hitting PeopleSoft login page in browser getting following message

CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

-->

App Server logs does show following message

PSAPPSRV.7524 (4) [XX GetCertificate] - - - (1) (NET.502): PTWEBSERVER@HOSTNAME is an Invalid User ID, or you typed the wrong password.  User ID and Password are required and case-sensitive.  Make sure you're typing in the correct upper and lower case.  

Based on these issue is with PTWEBSERVER User .

1. User account PTWEBSERVER is locked, and if it is then unlock the PTWEBSERVER account :

UPDATE PSOPRDEFN SET ACCTLOCK=0 WHERE OPRID=’PTWEBSERVER’;

2. User password is not matching with encrypted value.

Navigate to 

$PS_CFG_HOME/webserv/<DOMAIN_NAME>/peoplesoft/applications/peoplesoft /PORTAL.war/WEB-INF/psftdocs/<DOMAIN_NAME>/configuration.properties

Look for parameter WebPassword

If you know existing password then use pscipher utility to check encrypted value of it and see if it matches with above WebPassword value. If not then reset it.

on command prompt type follow to get encrypted value

>pscipher password

Error in document delete process (262,2031)

 Elastic Search Indexing Application Engine process failure Error in document delete process (262,2031)

Search Indexing Process failure with following errors -

Message Log-

Error in document delete process (262,2031)

.log File -

Process XXX ABENDED at Step PTSF_GENFEED.INDXDATA.Step01 (PeopleCode) -- RC = 24 (108,524)

Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s

.Trc File-

Direct Transfer Parameters: URL= http://HOSTNAME/_bulk Handle Count=50 Process Instance = XXX SBO Name = INDEX NAME Max Error = 100 

Solution ---->

PeopleTools ->Search Framework ->Administration ->Search Options

Update Attachment handlers from default 50 to 20