-
PeopleSoft Troubleshooting, Tips and FAQs
-
PeopleSoft Error Messages
The following are some error message that may appear when you are using PeopleSoft. Here are some explanations and work arounds.
Your PeopleSoft Connection has expired.
For security purposes, your PeopleSoft system logs you out of your application after 60 consecutive minutes of inactivity. Activity means that you are logged into the application, and actively navigating within the system or entering and saving data within the application. Prior to your session timeout, the system provides a warning that your browser session is about to expire. You can continue with your current session by clicking the OK button in the warning message. If you do not respond within two minutes, the session ends and the expired connection page opens.
To return to your application, click the Sign in to PeopleSoft link. The Sign In page appears, and you can once again sign in to your application. Note: Entering data without saving may not be recognized by the application as activity. Also, all unsaved data if/when you are timed-out is lost and unrecoverable.
If logging back in does not correct the problem, the problem may be caused by the browser you are using. Try again with a different browser.
SQL error. Stmt #: 5682 Error Position: 84 Return: 997 – ORA-00997: illegal use of LONG datatype…
OR
Error in running query because of SQL Error, Code=932, Message=ORA-00932: inconsistent datatypes: expected – got CLOB (50,380)
When working with Query: If you have a long Text field (like a Comments field) in your query results, and you use the DISTINCT option on the query or you are grouping by the long text field, you will receive one of the above Oracle errors.
(From PeopleBooks) In Oracle databases, PeopleSoft LongCharacter fields use the CLOB datatype when their length definition exceeds 1333. Since CLOBS and other binary datatypes are not valid columns for all operators, all queries including columns with LongCharacter field length definition that exceeds 1333 should not include the DISTINCT operator.
Work Arounds:
- To work around this, remove the DISTINCT if applicable.
- If you want to attempt to retain the DISTINCT:
- You can create an Expression that will add a new Character field to substitute for the Text field.
- First determine how many characters there are in the field with an Expression: MAX(LENGTH(A.SAMPLEFIELD))
- Then use the TO_CHAR function in an Expression to add a new character field with the maximum number of characters.
- Be sure to check Use as Field
- Once you’ve created the Expression, remove the Text field from the query.
- Examples:
- (TO_CHAR(SUBSTR(A.SAMPLEFIELD,55,950)))
- TO_CHAR(A.COMM_COMMENTS)
The resource you are trying to schedule is currently in use. Try your save again. If after 3 attempts you still cannot save, contact your system administrator.
(From PeopleBooks) For organizations that schedule classes with facility conflict checking activated, the resource queue table is a useful feature that prevents users from double booking facilities. When a user begins the class scheduling process, the system inserts a row in the resource queue table (via a COBOL program). This row signifies that someone within the organization is currently scheduling facilities. If another user attempts to reserve a facility, the system will present them with a message that resources are currently being allocated to another process and they must wait.
For example, “The resource you are trying to schedule is currently in use. Try your save again. If after 3 attempts you still cannot save, contact your system administrator.”
When the scheduling process completes, the row is removed from the Resource Queue table.
On occasion, system-wide or local client workstation errors may cause the row to remain in the table, thereby preventing the scheduling of classes. The Resource Queue Cleanup page was designed with this in mind. It is a powerful page, to be used by individuals at the system administrator level. The system administrator can simply click the Unlock Resource button on the Resource Queue Cleanup page, confirm their selection on the secondary page, and free up the resource.
Clearing the Resource Queue
- Access the Resource Queue Cleanup page.
- Unlock Resource
- Click to unlock the resource.