PSADMIN.7615 (0) (0) Begin boot attempt on domain DMOHRMS9
And the stderr file more stderrĭlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory Within Oracle 11gR2 64-bit, there is no 32-bit libraries (as I described here), so we can try the symbolic link as above, but it will not work ln -s libclntsh.so.11.1 libclntsh.so.9.0Įxec PSWATCHSRV -A -ID 111990 -C psappsrv.cfg -D DMOHRMS9 -S PSWATCHSRV : Server Id = 0 Group Id = orion2.phoenix-nga Machine = orion2.phoenix-nga: shutdown succeededġ process stopped. Shutting down all admin and server processes in /apps/psoft/hrms9/appserv/prcs/DMOHRMS9/PSTUXCFG Here a test case with Peopletools 8.49.20 working with Oracle 11.2.0.1 64-bit on Linux OEL 5.3 64-bit.Įxec PSMSTPRC -A -C psprcs.cfg -CD DMOHRMS9 -PS PSUNX -A start -S PSMSTPRC : The Oracle is a 64-bit, but we can use the lib32 libraries ln -s /apps/oracle/product/11.1.0/lib32/libclntsh.so.11.1 libclntsh.so.9.0 And restart the AppServer works fine : PSADMIN.8321 (0) (0) End boot attempt on domain DMOHRMS9ĭo you wish to see the error messages in the TUXLOG.040410 file? (y/n) : We can check the stderr file from the domain we are trying to start more stderrĭlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory As suggested in the certification matrix on My Oracle Support, a symbolic link must be created to workaround this. PSAPPSRV.8363 (0) (0) Server failed to start PSAPPSRV.8363 (0) (1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database DMOHRMS9 with user PS. PSAPPSRV.8363 (0) (1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0) PSAPPSRV.8363 (0) (0) Cache Directory being used: /apps/psoft/hrms9/appserv/DMOHRMS9/CACHE/PSAPPSRV_1/ PSAPPSRV.8363 (0) (0) PeopleTools Release 8.49.20 (Linux) starting PSWATCHSRV.8362 (0) Checking process status every 120 seconds PSADMIN.8321 (0) (0) Begin boot attempt on domain DMOHRMS9
Check the TUXEDO log for details.ĭo you wish to see the error messages in the APPSRV.LOG file? (y/n) :y Tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered initiating user error handlerīoot attempt encountered errors!.
PEOPLESOFT REPORT NODE TYPE PC
Oracle: setuid setgid ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not menu - domain: DMOHRMS9ġ) Pub/Sub Servers : Yes 15) DBNAME :Ģ) Quick Server : No 16) DBTYPE :ĥ) Jolt Relay : No 19) DomainID :Ħ) WSL : Yes 20) AddToPATH :ħ) PC Debugger : No 21) ConnectID :Ĩ) Event Notification: No 22) ConnectPswd:ġ0) Perf Collator : No 24) WSL Port :ġ1) Analytic Servers : No 25) JSL Port :ġ2) Domains Gateway : No 26) JRAD Port :Įxec PSWATCHSRV -A -ID 114790 -C psappsrv.cfg -D DMOHRMS9 -S PSWATCHSRV :Įxec PSAPPSRV -sICQuery -sSqlQuery:SqlRequest -C psappsrv.cfg -D DMOHRMS9 -S PSAPPSRV :ĬMDTUX_CAT:1685: ERROR: Application initialization failure The test below is being with AppServer, but this is exactly the same with Process file oracle Here a test case with Peopletools 8.49.20 working with Oracle 11.1.0.7 64-bit on Linux OEL 5.3 64-bit. Here we can distinguished two cases, before Oracle 11gR2 and from 11gR2. Whatever the wordsize of the OS the Peopletools are running on, it must use the Oracle 32bit libraries. => Peopletools 8.50.xx : 64bit only is certified (regardless the OS, Unix, Linux and Windows) Only one certification path with Peopletools 8.50 : => From Peopletools 8.49.14+ : Linux 64bit is also certified => Before Peopletools 8.49.14 : Linux 32bit only is certified I don't have any troubleshoot tests cases, but I assume it must be easy to be respectful of this constraint. Depending of your Peopletools version, this could be very different, from a certification point of view as well as from a working point of view.Īnd this two points are not exclusive to the process scheduler, but are also valid for AppServer, that's why tests below could also contain example with AppServer as well as Prcs. The first two components to check are the OS wordsize and the database client version (32 or 64 bit). Note I said "must work", and not the other way around, if a combination is not certified, it does not necessarily mean it does not work, but at least if it is certified it must work. The certification matrix assure that the combination of component must work. It might appear basic advice, but it is very often forgotten.
When debugging process scheduler (or AppServer), we need to be sure about the certification matrix.