LIBTUX_CAT:681: ERROR: Failure to create message queue

Issue: 

While starting Application Server or Process Scheduler for very first time, Boot process fails while starting JSH or WSL  server processes.

In my case i am with PT 851 and HRMS 9.1.

 

Tuxedo Log:($PS_HOME/appserv/<DOMAIN>/LOGS/TUXEDO****)

100837.psapp.com!JSH.22674.1236849872.-2: LIBTUX_CAT:681: ERROR: Failure to create message queue
100837.psapp.com!JSH.22674.1236849872.-2: JOLT_CAT:1088: “ERROR: tpinit() failed, tperrno = 7”
100837.psapp.com!JSL.22671.285207664.0: JOLT_CAT:1079: “ERROR: Error starting mininum number of handlers”
100837.psapp.com!JSL.22671.285207664.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
100837.psapp.com!tmboot.22651.318214464.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
100837.psapp.com!WSL.22669.1231995104.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
100837.psapp.com!WSL.22669.1231995104.0: WSNAT_CAT:1197: INFO: Exiting system
100843.psapp.com!BBL.22648.4133522528.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
100846.psapp.com!PSADMIN.22115: End boot attempt on domain TESTHR

 

Solution:

As a root user add or modify with below kernal value in  sysctl.conf file from /etc location. After adding below value run ‘sysctl -p’ command as root user.

kernel.msgmni = 1024

Try to boot the domain with changed value. Hope this should resolve. 

How to Change SYSADM(Access) Password in PeopleSoft

1 Login into database as super user(SYS), and change the password of SYSADM user at DB leavel.

SQL> Alter user SYSADM identified by <new_password>;

SQL> select * from SYSADM.PSACCESSPRFL; — (Here you will get the information of Symbolic ID)

 

2.Login to Data Mover in bootstrap(SYSADM) mode with newely changed password and run the following command:

CHANGE_ACCESS_PASSWORD <Symbolic ID> <new_password>;
ENCRYPT_PASSWORD *;

This command will change the SYSADM password, and that will update the PSACCESSPRFL table as well and will encrypt the entry (ACCESSID and ACCESSPSWD).

File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 – ORA-01017: invalid username/password; logon denied

Issue:

 When you are trying to boot the application server for the first time after a fresh installation, Boot attempt freeze while starting PSAPPSERV server process. And same error is reflected in Application designer when you are trying to login with oper id (PS).

 

In my case i am with Peopletools 851 and HRMS 9.1

 

Error Message in Application designer:

File: SQL Access ManagerSQL error. Stmt #: 2  Error Position: 0  Return: 404 – ORA-01017: invalid username/password; logon denied

 

Error Message in Application server logs($PS_HOME/appserv/<DOMMAIN>/LOGS/PSAPPSRV******)

 

PSAPPSRV.24496 (0) [06/08/14 07:02:05](0) Cache Directory being used: /home/psoft/pt851/appserv/HRTEST/CACHE/PSAPPSRV_1/
PSAPPSRV.24496 (0) [06/08/14 07:02:05](3) File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 – ORA-01017: invalid username/password; logon denied
PSAPPSRV.24496 (0) [06/08/14 07:02:05](1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 – ORA-01017: invalid username/password; logon denied
PSAPPSRV.24496 (0) [06/08/14 07:02:05](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database HRTEST with user PS.
PSAPPSRV.24496 (0) [06/08/14 07:02:05](0) Server failed to start

 

Solution:

Change the Access password(SYSADM). This will help you.

How to run setspace.sqr in command line on linux

Setspace.sqr  :-

Script to populate or synchronize Tablespace information with the system catalog.

export PS_HOME=/psoft/pshome/pT851
export REPNAME=/psoft/pshome/pT851/sqr/setspace.sqr
export DB=SYSADM/SYSADM@TEST
export SQR=$PS_HOME/bin/sqr/ORA/bin/sqr
$SQR $REPNAME $DB -I$PS_HOME/sqr/ -F/tmp/ -ZIF$PS_HOME/sqr/pssqr.ini

 

This step populates all Tablespace information in the PSRECTBLSPC table. 

The values stored in the DDLSPACENAME field are updated with current values found in the system catalog for tables already defined in your database. If you modified Tablespace names from the PeopleSoft-delivered names, this step makes those same changes in the PeopleSoft record definition.