Tuesday 12 November 2013

Memory allocation failed (SQLSTATE PS118), Cache write failed

PSAPPSRV LOG:
PSPAL: Abort: Unrecoverable exception
Memory allocation failed (SQLSTATE PS118)
CMgrImp::WriteCache : Cache write failed

Platform : AIX
Getting the following error messages in the APPSRV_MMDD.LOG log on PeopleTools 8.48+:

PSPAL: Abort: Unrecoverable exception
Memory allocation failed (SQLSTATE PS118)
CMgrImp::WriteCache : Cache write failed

Solution :

Check the output of 'ulimit -a' command while logged into your AIX system as the user that you use to boot the domain.

It may give you results like below, which are the older AIX defaults:

time(seconds) unlimited
file(blocks) 2097151
data(kbytes) 131072
stack(kbytes) 32768
memory(kbytes) 32768
coredump(blocks) 2097151
nofiles(descriptors) 2000

From the 'ulimit -a' output above, it the limitations are set too low for PeopleTools.

The out of memory problems are due to the low setting for the 'data' limit -
This should be set to unlimited.
Additionally, the 'nofiles' limit should be raised to at least 4000.

Increase these limits, logout, log back in, verify the limits,
as the user that will boot the application server domain,
have been raised by running 'ulimit -a', then restart the domain.

Note : this setting also helps if you are being thrown out of PIA multiple times & if you are getting below error in app logs
/vob/peopletools/src/pssys/crmget.cppSQL error. Stmt #: 1066 Error Position: 28 Return: 8007 - Insufficient memory available
You can also change the ulimit settings to unlimited except for codedump parameter.
After changing the limits you need to log out and back into your Unix account and restart the process scheduler.

Database Signon: Could not sign on to database HCMDEV with user PSAPPS. Return: 8097 - Oracle initialization error

Errors :Database Signon: Could not sign on to database HCMDEV with user PSAPPS.
Return: 8097 - Oracle initialization error

PSAPPSRV Fails to Boot - Return: 8097 - Oracle initialization error

Solution:
Case #1- Same error message. Tnsping was able to connect to the DB OK.
The application server user on the Unix box needs read accesss to all files under $ORACLE_HOME.Please make sure that.

Case #2 - if Appserver is on 32bit Windows & Oracle client installed is 11.2.
This Oracle client version was never certified for 32bit Windows OS.
Installing Oracle client 11.1 or lower resolves the problem.

Oracle Client 11.2 is certified for Windows 64bit OS only.

CMDGW_CAT:3250: ERROR: Cannot send config to GWADM group=GWTGROUP

TUXLOG:
GWADM.10104.1.0: 12-09-2010: Tuxedo Version 10.3.0.0, 64-bit
GWADM.10104.1.0: LIBTUX_CAT:262: INFO: Standard main starting
DMADM.10103.1.0: CMDGW_CAT:3250: ERROR: Cannot send config to GWADM group=GWTGROUP
GWADM.10104.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
tmboot.10102.1.-2: CMDTUX_CAT:825: ERROR: Process GWADM at g3u0181c failed with /T tperrno
(TPESVCFAIL - application level service failure)
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

Applicable to : PT 8.51 and later
App server domain is having an issue starting up & the TUXLOG file is showing the following errors:

GWADM.10104.1.0: 12-09-2010: Tuxedo Version 10.3.0.0, 64-bit
GWADM.10104.1.0: LIBTUX_CAT:262: INFO: Standard main starting
DMADM.10103.1.0: CMDGW_CAT:3250: ERROR: Cannot send config to GWADM group=GWTGROUP
GWADM.10104.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
tmboot.10102.1.-2: CMDTUX_CAT:825: ERROR: Process GWADM at g3u0181c failed with /T tperrno
(TPESVCFAIL - application level service failure)
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

Cause :
Upon checking the configuration template via PSADMIN.
The Domain Gateway was found out to be enabled = "YES"
which will cause the server to search for a remote server
to which this domain will send search requests.

Solution :

To resolve the issue, refer to the details below:

1. open PSADMIN
2. go to Configure this Domain
3. enter 12 to disable the Domain Gateway
4. enter 13 to configure the domain and save the changes made

After the changes, the Application Server domain booted without any problem

SQL Access Manager: SQL error. Stmt #: 2 Error Position: 0 Return: 12541 - ORA-12541: TNS:no listener

PSAPPSRV LOG:
GenMessageBox(200, 0, M): SQL Access Manager: SQL error. Stmt #: 2 Error Position: 0
Return: 12541 - ORA-12541: TNS:no listener
GenMessageBox(0, 0, M): Database Signon: Could not sign on to database FSYS with user PSAPPS.

Trying to boot application server domain or process scheduler receive errors like the following:
PSAPPSRV LOG
GenMessageBox(200, 0, M): SQL Access Manager: SQL error. Stmt #: 2 Error Position: 0
Return: 12541 - ORA-12541: TNS:no listener
GenMessageBox(0, 0, M): Database Signon: Could not sign on to database FSYS with user PSAPPS.

Solution :

ORA-12541: TNS:no listener means the Oracle database listener is not started.
Check to ensure this is started with the Oracle DBA.
(you can check listner service using lsnrctl on solaris)
Also make sure tnsnames.ora has correct entries.

Unable to start PSRENSRV

PSRENSRV process fails to start.

PSRENSRV_mmdd.LOG:
(FATAL) nsmain: configuration file empty or missing ns/servers section (162,2076)
(ERROR) Server failed to start

When you start the Application Server, the PSRENSRV process fails to start. The following error is logged to APPSRV_MMDD.log:
REN configuration file not found.

Also, the following error may be logged to PSRENSRV_mmdd.LOG
(FATAL) nsmain: configuration file empty or missing ns/servers section (162,2076)
(ERROR) Server failed to start

Steps
1. Start Application Server (with 'Event Notification' enabled)
2. Application Server fails to start with message:

exec PSRENSRV -A -- -C psappsrv.cfg -D TESTSERV -S PSRENSRV :
CMDTUX_CAT:1685: ERROR: Application initialization failure
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
Cause

The REN configuration file (psrenconfig.txt) is missing or corrupted.

Solution :

Follow these steps in order to correct problems with the REN configuration file
in your PeopleTools environment:

1. A default REN configuration file is delivered when PeopleTools is installed.
Whenever a new application server domain is created, it is populated with this file.
So we need to make sure the file exists, and is not corrupted, as follows:
a. Go to <PS_HOME>/appserv/ren.
b. Within this directory, there should be a file called psrenconfig.txt
c. If the file exists, make sure if it not corrupted, as follows:
-Open file and it should be readable (this is a text file).
-Verify that the last line is '#### END OF FILE #####'.
d. If file does not exist, or is corrupted, then get a new copy from your DEMO system.

2. Next, place a new copy of psrenconfig.txt into the application server domain
where you are getting the PSRENSRV error, as follows:
a. Copy psrenconfig.txt
From: <PS_HOME>/appserv/ren
To: <PS_CFG_HOME>/appserv/<DOMAIN_NAME>.
b. If you had made any customizations to the previous psrenconfig.txt file,
you'll need to remake the changes.

3. After making the above changes, restart the application server.

Could not connect to application server FNDEV. Make sure the PeopleTools authentication server (PSAUTH) is booted.

Application Designer in 3-tier mode getting below error message:
Could not connect to application server FNDEV.
Make sure the PeopleTools authentication server (PSAUTH) is booted.

While trying to logon to Application Designer in 3-tier mode getting below error message:
Could not connect to application server FNDEV.
Make sure the PeopleTools authentication server (PSAUTH) is booted.

Cause :
Not having the tuxedo folder under the <PSHOME> where
Application Designer is launched from will cause this issue.

Solution :

The tuxedo client needs to be under the <PSHOME> where you launch the executable for App Designer,

which is usually your file server.

The error is related to files missing on file server where Application Designer was started. Make sure the tuxedo folder exists under this <PSHOME>. Also,you must have the following four files installed -

PS_HOME/tuxedo/udataobj/Lic.txt, SysRegiiop.rdp, SysRegtgiop.rdp, System.rdp.

For PeopleTools 8.50 and higher the only files you will find under PS_HOME/tuxedo/udataobj are

SysRegiiop.rdp, and System.rdp, which is all that are needed.

Some users copy the <PSHOME> to their PC to have the executables local on their machine.

If you do this make sure you include the tuxedo folder and all files that reside under it.

You can also get this error if your Domain Connection Password in Configuration Manager

does not match the password for DomainConnectionPwd on your web server in the

configuration.properties file

Missing or invalid version of SQL library libpsora (200,0)

PSAPPSRV LOG:
PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
Database Signon: Could not sign on to database FTST with user PSAPPS.

On new install of PplTools 8.49,unable to boot the application server domain on AIX Unix system

Errors : PSAPPSRV LOG shows :
PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
Database Signon: Could not sign on to database HRMSDV with user PSAPPS.

StdErr shows :
open in libpscompat failed for 'libpsora.so':/oracle/10.2.0.3/lib32/libclntsh.so.9.0:file too short

Cause :

The cause of the problem is the incorrect size of Oracle library in use.

<xxxxxxxxxxx: test></oracle/10.2.0.3/lib32> ls -l /oracle/10.2.0.3/lib32/libclnt*
lrwxrwxrwx 1 oracle dba 85 Feb 11 10:56 /oracle/10.2.0.3/lib32/libclntsh.so -> libclntsh.so.10.1
-rwxrwxr-x 1 oracle dba 0 Feb 01 02:18 /oracle/10.2.0.3/lib32/libclntsh.so.10.1

Here, -rwxrwxr-x 1 oracle dba 0 Feb 01 02:18 /oracle/10.2.0.3/lib32/libclntsh.so.10.1
shows that the file everything is pointed to has 0 bytes

Solution :

1. Run the following as the UNIX account that boots the Application Server:

ls -l $ORACLE_HOME/lib32/libclnt*

Review the listing results to determine if the libclntsh soft links are accurate
and that the files/links returned have some size value.

2. Output should show files with a size greater than 0 bytes and not like below:

<xxxxxxxxx: test></oracle/10.2.0.3/lib32> ls -l /oracle/10.2.0.3/lib32/libclnt*
lrwxrwxr-- 1 oracle dba 85 Feb 11 10:56 /oracle/10.2.0.3/lib32/libclntsh.so -> libclntsh.so.10.1
-rwxrwxr-- 1 oracle dba 0 Feb 01 02:18 /oracle/10.2.0.3/lib32/libclntsh.so.10.1

3. If the Oracle client lib has a size of '0' then you will need to re-create it
using the Oracle DB delivered '$ORACLE_HOME/bin/genclntsh' script using the UNIX Oracle account.

4 . To resolve the issue install the 32 bit Oracle client on your application server machine
and setup your environment to only find the 32 bit libraries.
Make sure ORACLE_HOME, PATH, LD_LIBRARY_PATH are all configured to find 32 bit Oracle libraries.

JOLT_CAT:1079: ERROR: Error starting minimum number of handlers

TUXLOG:
JOLT_CAT:1079: ERROR: Error starting minimum number of handlers
LIBTUX_CAT:250: ERROR: tpsvrinit() failed

Trying to boot an application server domain, it fails to start. TuxLog shows the following messages

JOLT_CAT:1079: ERROR: Error starting minimum number of handlers
LIBTUX_CAT:250: ERROR: tpsvrinit() failed

Solution :
First make sure there is no port conflicts of your JSL and JSH ports. Use the command 'netstat -an' to see if a port is currently in use.

This error will occur when a JSL or JSH process is not able to capture it's assigned port. If multiple domains are running on the same box, make sure that the ports are not already being used by another process.

Friday 8 November 2013

Invalid Access ID or Password for Signon - see your security administrator.

Database Signon: Could not sign on to database HRMSPD with user PSAPPS orInvalid User ID or Password for SignOn; logon denied. Or Invalid Access ID or Password for Signon - see your security administrator.

Steps to check :

a) Check Connect ID and Connect Password Values are correct one.(default : people/peop1e)
Chech whether connect id was locked or not. We should be able to login with connectid/connectpass to database.
Connect ID login has SELECT privilege on SOPRDEFN,PSACCESSPRFL,PSSTATUS.

b) Make sure OPRID/password that is used to boot app server is correct. Make sure OPRID is not locked in PSOPRDEFN table.
Query: Select ACCTLOCK from PSOPRDEFN
The SymbolicID field in PSOPRDEFN & PSACCESSPRFL is same.

c) Make sure AccessID/Access password in PSACCESSPRFL are correct and the values are encrypted.
Make sure You are able to login to Database with Accessid/pass
Pls make sure sysadm(accessid for oracle) is not locked out or it's passwd is not expired

d) Analyse appsrv/tuxlog files.

Friday 1 November 2013

Error in XMLP reports: 'system-temp-dir' property is pointing to an invalid path

XML Publisher Global Engine settings are defined in the xdo.cfg file. The default xdo.cfg file is located in the $PSHOME/appserver directory, which is shared by all application server and process scheduler domains by default.

The default xdo.cfg file contains the following settings:

<config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/">
<properties>

<property name="xslt-xdoparser">true</property>
<property name="xslt-scalable">true</property>
<property name="system-temp-dir">CACHE</property>
<property name="system-cachepage-size">50</property>


<property name="pdf-compression">true</property>





</properties>
</config>

change the temp directory path. For example /psoft/FNTST/temp and bounce application and process scheduler servers.

Error 404—Not Found From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.5 404 Not Found

Error 404—Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
When we try to see the output PDF file of any report (Ex: sysaudit report) in ProcessMonitor, it is showing above error.
Solution: We get this error if report node was not configured properly. Configure the report node, verify PSOPTIONS, PS_CDM_DIST_NODE and PSGATEWAY tables and bounce the process scheduler server.

Unable to retrieve current DDL space name in DtaMover

After export of peoplesoft database using DataMover, one may get "Unable to retrieve current DDL space name" error while altering tables. For this check a few tools tables like PSSTATUS, PSACCESSPRFL etc. Some details may be lower case. eg . PSSTATUS . OWNERID column might have ownerid in lower case (sysadm).

In Oracle, if one checks DBA_TABLES.OWNER, sysadm would be in upper case.

Update PSSTATUS.OWNERID to upper case and you should be able to alter tables through Application Designer.

Error on Peoplesoft Login page: Invalid User Id or Password.

Case1: Only one user is unable to login

User account has been locked.

Case2: No one is able to login.

Password of PS user was locked or changed. If it was locked, unlock it from the back end.

UPDATE PSOPRDEFN SET ACCTLOCK=0 WHERE OPRID='PS';

If the password is changed, change the password from back end and change it in application server and process scheduler server and bounce them.

Error on peoplesoft Login page: Authorization Error -- Contact your Security Administrator

Showing some error and we are not able to login of peoplesoft

Error on peoplesoft login page: Authorization Error -- Contact your Security Administrator.

Case1: Clear your browser CACHE and try again.

Case2: This is due to, the Database is down. After DB is bringing up then we are able to login.

bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

In Login page it is showing following error:
bea.jolt.ApplicationException: TPESVCFAIL - application level service failure. But users are able to login.
Case1:
This happens due to PTWEBSERVER is locked.
Error in PIA Page: CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

Case 2:
This is due to, In valid WebProfile name entered in in web server configuration.properties file.
WebProfile= DEV OR TEST OR KIOSK OR PROD. If we give other than this it shows error. In Configuration propertied file D:\PT8.49\webserv\peoplesoft\applications\peoplesoft\PORTAL\WEB-INF\psftdocs\ps change webprofile= DEV OR TEST OR PROD OR KIOSK. THEN RESTART WEB SERVER, after message will not be displayed on PIA page.

Case 3:
This is due to mismatch PTWEBSERVER password I,e Password of PTWEBSERVER given in PSOPRDEFN table and password given in configuration.properties file are not same.
PIA Page PeopleTools->Security->UserProfiles->Ptwebserver
and in configuration.properties file I,e WebPassword=(In PIA and config file both pswd will be same and in ecrypted.
The default password of PTWEBSERVER is PTWEBSERVER.

Goto cmd prompt:
cmd>cd pshome\setup
cmd>Pscipher PTWEBSERVER

Then it will generate PTWEBSERVER encrypted password and copy pswd in configuration.properties file and PT->Security->UserProfiles->Ptwebserver.Then bounce the webserver after the message will not be displayed.

OR
In PIA go to PeopleTools--> IBGateways-->Gateway properties (hyperlink)-->Give user id and password At the end of the page we can find edit boxes to encrypt the password.

(You can also update the password in psoprdefn using SQL, then encrypt it with datamover.
In SQL: update psoprdefn set operpswd='XXX', encrypted=0 where oprid='PTWEBSERVER';

In datamover:
encrypt_password PTWEBSERVER;
commit;)
PTàSecurity-->User Profiles-->User Profiles
User Name: PTWEBSERVER.
Change the password.

after this we get the encrypted format of password. Copy it and paste it in config.Props file.

Error: 501 Not Implemented:

1. Getting frequent error 501 not implemented on the browser with IE7 and IE8.

2. Component page reset. Users are getting kicked out to first page or the search dialog box in the middle of a multi page transaction and losing the data they have entered.

3. Suddenly the page will become unresponsive and entire browser will freeze and will require restart of the browser.

All the 3 symptoms were annoying for the users and we eventually traced it to AJAX feature, that results in loss of POST data.

Turning off the AJAX setting resolved all 3 issues. Here is a way to turn off the AJAX

Go to PeopleTools –> Web Profile > Open the Web profile you use for e.g. DEV or PROD.

Go to Custom Properties and Add a Property AJAX of type Boolean and set its value to false. This will turn off the AJAX. To enable it again make it true or remove the row. Bounce all the Web servers using this web profile to make this setting take effect.

Though the above changes resolves the issue, this is not desirable and also may not be supported in future peopletools release. I have found this issue to be related to a bug in IE7 and IE8 when used with Windows XP OS. Fortunately microsoft includes the hotfix to resolve the issue, however registry change needs to be made to enable the hotfix. For more details, see this following KB :http://support.microsoft.com/kb/895954 - When you use Microsoft Internet Explorer or another ! program to perform a re-POST operation, only the header data is posted. See How to enable this hotfix section for registry changes.

Basically, the issue happens as IE sends the AJAX request in 2 tcp ip packets one for the header and one for the body. When network error happens, and ie tries to send the ajax request again, it fails to send the body. This causes PIA to loose the session state and we see the issues described above. The other browsers Firefox, Safari and Chrome do not send ajax request in multiple packets and this issue does not appear there.

Also see this article on further clarification on which registry key needs to be modified : http://www.geoffchappell.com/viewer.htm?doc=notes/windows/ie/featurecontrol.htm

According to this , you can specify the value in any one of the following location, in order of decreasing precedence.

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl

HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl

HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl

Please leave comments, if applying the above registry changes resolves the issue.

PeopleSoft has also published this resolution on My Oracle Support (MOS) - E-PIA: PeopleTools 8.50 and 8.51 - Intermittent "Error 501--Not implemented" Messages when Navigating to a Page Using IE7 or IE8 Browser. Doc ID : 1337266.1

Error & Posted: ora-03114 not connected to oracle

AE Process went Error and Posted. And log file shows above error.

PSAE process has been killed by oracle DBA. So it went error. Process Scheduler server has been bounced to resolve it.

CMDTUX_CAT:1685 & CMDTUX_CAT:827

CMDTUX_CAT:1685: ERROR: Application initialization failure tmboot:
CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

1) Authority/security not in place for the userid trying to boot the Application Server or Process Scheduler (when Maintained by Tuxedo)

Log on in 2-tier mode, go to Security Manager, and check that the ID being used to start the Application Server has the 'authority to boot the app server' box checked 'ON'.

2) Connectivity problems between the Application Server and the database.

CASE 1:
The problem was with the connectivity and this could be seen in the appsrv.log file. The Tuxedo-delivered services booted, but the PeopleSoft delivered services (psauth, psappsrv, etc) did not. It is the PS services that require the connectivity DLLs to the RDBMS. This can be fixed by specifically coding the AddToPath in Psadmin, instead of relying on the '.'

Check the environment variables set before going into Psadmin, especially the Ld Library Path.
Make sure psconfig.sh is run before going into psadmin.

CASE 2:
2) NT/2000 only. Make sure the PeopleSoft service and the Tuxedo IPC Helper are started with the same user id. Change the Logon As for the Service to be This Account. Make sure the account is a local account with local administrator privileges or a domain account with local administrator
privileges to this box. Use a regular userid id like TUXADM not the administrator account. TUXADM should have right to the report repository to be able to start the Distribution Agent.

CASE 3:
For one customer, the problem was due to password changes on the database (PS) or PIA. Once they reset the database password, the Application Server was able to start.

CASE 4:
For one customer on PeopleTools 7.5 and Sybase platform They received the error message above every time that they tried to boot up the App Server.
Found out that the user login into the system did not have have access to the /opt/Sybase/bin directory, and there was a missing /opt/Micro Focus COBOL.41 directory.
Once they gave the user right to the Sybase middle ware software, and installed the COBOL compiler, it worked and they were able to start up Application Server.

CASE 5:
2-tier log on also failed. The Oracle listener had not been started.

CASE 6:
Could not complete a TCP loopback as psoft (sqlplus VP1/VP1@dbname) but could as oracle.
Check for differences in environment settings and permissions of these two UNIX id's. This should fix the problem.

CASE 7: (Oracle Customers) :
Problem was with the tnsnames.ora file on the database server (or application server, as they have got logical 3-tier architecture). New domain database name was not updated in tnsnames.ora file. It started running once this file was updated.

CASE 8: (Oracle Customers)
The Application Server would hang without any error messages during PSAUTH start up. Tuxedo log file would just show "Standard main starting" and no errors either. The problem was with Oracle database archive logs. The archive log directory was full and the database had stopped all operations. Creating space in the archive log directory (or turning off archiving),
fixed the problem.

CASE 9:
Customer upgraded Oracle and get CMDTUX_CAT 1685 errors. The Application Server hangs while booting PSAPPSRV. The problem was resolved by doing Server transfer again and recompiling and relinking COBOL.

CASE 10 :
Customer didn't have sufficient space left on their Hard disk. Once they created some space they were able to boot the App Server.

CASE 11:
Customer upgraded to PT 7.58 and not able to start Application Server. Getting CMDTUX_CAT:1685: ERROR: Application initialization failure on the screen. APPSRV.LOG shows the following error :
PSAUTH.90 [05/17/00 18:08:51](1)

=== GenMessageBox ==
Title: Database Signon
Message: Invalid operator ID or password for database signon. (id=PS)
Style: 8208
Msg Set: 0
Msg #: 0
==

RESOLUTION:

Try to start the Application Server using another Operator Id. Make sure that the new Operator Id has permission to start Application Server by going into Security Manager. It should work.

If you still want to use the original Operator Id to start the Application Server then delete and recreate the Operator Id.

CASE 12:
Customer was booting up their domain and received the following:

exec JSL -A -- -d /dev/TCP -n //etsprode105:9140 -m 1 -M 1 -I 5 -c ANY -x 60

-T 60 -j 5000 -w JSH :
CMDTUX_CAT:1685: ERROR: Application initialization failure

RESOLUTION:
They were using a port number that was already being used, once they change the port number for JOLT, JSL started up OK.

CASE 13:
In the Install/Admin Guide for Oracle, for tools 7.5, Appendix A lists information on the Oracle bug

#617681 and the changes required for Hp UX 10.20 for Oracle 7.3.4 customers. Here the delivered clntsh.mk file is incorrect. The instructions ask the customer to login as the Oracle user and cd to $Oracle_Home/rdbms/lib. There, the clntsh.mk script needs to be editted as follows -- move the include of cobsqlintf.o to the front of the link list in the clntsh.mk script.

CASE 14:
ODBC configuration for SQL Server did not have peoplesoft database set as default in ODBC configuration

CASE 15:
Seen in PT 8.41 for Process Scheduler. The TNSNAMES.ORA file was using "IFILE=" clause to dereference a TNS file on the network.

Even though TNSPING and SQLPLUS could connect to the database, the Process Scheduler failed.

Create or copy the TNS file to the local machine, remove the IFILE clause.

CASE 16:
This Error can also be caused by an incorrect Node selection .

in pt 8.4x Navigate to : peopletools->process scheduler->servers->(select the distribution tab).

Click on the magnifying glass and select one of the available Nodes. Note* even though the Test box may contain a node name when you first navigate it may not be the correct one. available ones will be listed in the lookup listbox.

A referenced to an incorrect Node will also be references in the log of the service that errors out during the scheduler boot up.

bea.jolt.serviceexception.tpenoent-no entry found

There are three reasons for this error
1) The employee id and password are not correct
2) The employee PSOPRDEFN record is locked
3) Archive Log is full.

The application server machine has not enough capacity (processor and memory).
Corrupted cache on application server is the primary cause for this issue. Shutdown the Application Server Domain, Delete cache for your domain.
The problem was that the user profile you are trying to start the app server does not have enough permissions to start the app server. Check your demo environment and add extra roles to the user you are trying to start the appserver with.

PIA Error on Signon Page : bea.jolt.ServiceException: TPENOENT – no entry found

If you are getting the above message like above in sigon page with all OPRD ID’s then there is high probabilbity of PSDEFAULT tablespace is not able to extend or full. If you try to login in the Applciation Designer then you will get the below error message. Resolution for this is obvious,.i.e, to alter or extend the PSDEFAULT tablespace.
Error while loggin in Application Designer
File: D:\pt84917b-retail\peopletools\SRC\pssys\stmupd.cppSQL error. Stmt #: 2292 Error Position: 0 Return: 1653 – ORA-01653: unable to extend table SYSADM.PSACCESSLOG by 128 in tablespace PSDEFAULT Failed SQL stmt:INSERT INTO PSACCESSLOG (OPRID, LOGIPADDRESS, LOGINDTTM, LOGOUTDTTM) VALUES (:1, :2, TO_DATE(SUBSTR(:3, 0, 19),’YYYY-MM-DD-HH24.MI.SS’), TO_DATE(SUBSTR(:4, 0, 19),’YYYY-MM-DD-HH24.MI.SS’))

Change Assistant Error

Error in EMHub error log:
<Oct 12, 20012 3:03:13 PM EST> <Notice> <Stdout> <000000> <WARN [ACTIVE] ExecuteThread: ’0′ for queue: ‘weblogic.kernel.Default (self-tuning)’ EMF_CATEGORY – Unable to register peer com.peoplesoft.emf.peer:id=2 with the EMHub>

Error that PSAgent gives:
ERROR main EMF_CATEGORY – Error while connecting to ‘http://pserv01:8300/PSEMHUB /hub’.
ERROR main EMF_CATEGORY – Error: Internal Exception: – Error registering peer
ERROR main EMF_CATEGORY – Error while connecting to server – retrying attempt 1
The fix was to reset the GUI
Viewing:
select GUID from PSOPTIONS
Updating:
UPDATE PSOPTIONS SET GUID = ‘ ‘
Then, you need to restart the application server and the web server.

Strange errors in Application Designer

Errors:
1. When we try to save, we get error: “PSXXX_XXX has been updated by another user. (3,1)”
2. Unable to login into Application Designer in my system and able to login from different system.
3. Scroll or grid is not functioning properly or unable to save scroll or grid.

Solution: Clear the CACHE of Application Designer.
Clearing Cache of Application Designer:
First close the application designer and....

Go to Configuration Manager =>Click on "Purge Cache Directories"

Error: Invalid user/Password after installation of database.

After installation of DB using Datamover in BS mode, if we try to login to AppDesigner using PS/PS we get an error like Invalid user/Password. To solve this run grant.sql script.