E-UPG Alter Error: Unable to Retrieve Current DDL Space. Alter Processed Failed. (76,47)

An Alter process during the Tools Only Upgrade  failed with the following error:

ERROR:
————
SQL Build process began on 3/17/2004 at 4:06:26 PM for database ****.
Error: ACCESS_GRP_LANG – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: AE_SYNCGEN_AET – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: AELOCKMGR – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: AERUNCONTROL – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: AERUNCONTROLPC – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: AETEMPTBLMGR – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: APPMSGARCH_AET – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: APPR_HDR_LNG – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)
Error: APPR_RULE_HDR – Unable to retrieve current DDL space name.  Alter processed failed. (76,47)
Error: Fatal error in function BldAlter on call to function GetOldRecDefn.  Return code = 1. (76,6)

SOLUTION:
————–  
In the PSSTATUS table, the OWNERID column data was in lowercase. When the data got converted into upper case, the error got resolved and the Alter script ran without any issues.

Page Data is Inconsistent With Database

If the message ‘Page data is inconsistent with database’ appears while saving the page, please refer the following resolution in MOS (My Oracle Support).

E-AS: How to Trace “Page data is inconsistent with database” error? [ID 655907.1]

Step 1: Set the following in psappsrv.cfg

TracePPR=1
TracePPRMask=32767

Step 2: Go to the PIA and before logging on, add & trace=Y (uppercase) at the end of the web address and press the ‘Enter’ key in the keyboard. Check the first five SQL options and for PeopleCode the ‘List Program’ & ‘Each statement’ options.

Step 3: Log in to PIA and reproduce the error.

Step 4: Check the trace, especially the portion which contains the below information:
PSAPPSRV.28630    1-167605 11.00.03    0.001 Record RO_LINE_ATTR.ROW_LASTMANT_DTTM database value “2007-06-11-10.58.44.000000? page value “2007-06-11-10.05.30.000000?
The trace should clearly show the field that is producing the error as well as the values that are populated both on database side and on page side.

The most common reason to encounter this issue is:

When you use a view to select data into a scroll based on a table and no Auto select option is turned on. The number of columns in view and scroll area base table differs and the additional column in base table contains not null values. Auto update for scroll can be used to change the value of the field in a scroll and save it.

To resolve this issue, add same number of columns to view similar to the base table or if possible, make the same view as a base record for the scroll that is used for selection.

Another reason could be using SQLExec in SavePostChange to update the Base Table Record and therefore changing the value.

AWE – eMail Template SQL Object(s)

You must create SQL Object(s) if you wish to use binds values in your email notifications.

Below is an example of how a SQL object can be created to populate an email template:

SELECT A.TRANSACTION_NBR

,A.EMPLID

,B.NAME

,A.TRANS_DT

FROM PS_EXP_RPT_HDR A

,PS_PERSON_NAME B

WHERE A.EMPLID = B.EMPLID

AND A.LINEID =:2

In this example, the AWE will look to populate the %2 bind with TRANSACTION_NBR, the %3 bind with EMPLID, the %4 bind with NAME, and the %5 bind with TRANS_DT. Also note the “:1” bind in the where clause of the SQL Object. It is  mandatory requirement to have all of the keys from your header record (or line level record depending on the notification) bound into the where clause. The AWE uses the header record keys to retrieve the correct row from the SQL Object.

PeopleSoft – Remedy Integration

Client: Leading Healthcare Solutions Provider

Solution: PeopleSoft – Remedy Integration

The client was a leading Healthcare Insurance, Medicare and Medicaid Programs provider and they wanted to integrate their existing PeopleSoft system with the Remedy, IT service management suite, to synchronize and get single source of truth of their asset information. The Drivestream team studied the client’s complex business processes to understand the data flow between the Remedy and their PeopleSoft system and proposed an auto-trigger dual integration program, which would run as a part of night job. The team configured PeopleSoft integration broker to send and receive data from the Remedy system and also built a process to segregate the valid data in PeopleSoft that has to be sent across to the Remedy system. The systems were seamlessly integrated and the client was able to get a holistic view of their asset information.

Prompt Values Specified on Add Mode Search Record is not Enforced When Using ExcelToCI

While creating component interface, by default it will not enforce the prompt values specified on Add search record and will allow you to enter values even though they are not valid. This issue occurs when inserting new rows using ExcelToCI as it allows the user to enter invalid values without giving any error message.

To avoid this issue, open up the Add Mode Search Record for the component and go to Record field properties for the search fields and check the Search Edit check box.  This will enforce the use of valid values when adding a new row using component interface used in ExcelToCI. By default, Search Edit is not enabled.

Below is the description of this field in PeopleBooks.

Search Edit is enabled only if Search Key is selected. Selecting this option enforces the required property and table edits on the search page. It also enforces these edits under circumstances where the search page would normally be bypassed. With this option, the user no longer has the ability to perform partial searches on this field.

Below is the MOS (My Oracle Support) link related to this issue.

E-CI: Component Interface Does Not Validate Record Edits (Against Prompt table) When Using Create [ID 664377.1]

Does Row Level Security Work in ExcelToCI? (Doc ID 972241.1)

As per the above resolution, row level security is not enforced using ExcelToCI.

User is Unable to see Pagelet on a Home page

If a user is not able to see Pagelet on a Home page despite having access to it, then it indicates that the Webserver Pagelet cache is corrupt. The only way to overcome this issue is to restart the webserver. But if this problem occurs during the middle of a day, then the below steps can be followed to force the webserver Home page Pagelet cache refresh.

Add a new page to Home page tab as a required fix (PeopleTools –> Portal –> Structure and Content –> Portal Objects –> Home Page –> Tabs ->Home).

Go to the tab – ‘Content Tab’ and add the new Pagelet as required fix and select the column (usually the last column). Save it and re-login with the id of the user who is not able to see the Pagelet. After this step, the user should be able to see the missing Pagelet. Remove the newly added Pagelet, as it is no longer needed. The following sql can be used to determine which Pagelet that user has access to.

SELECT * FROM PSPRUHTABPGLT where oprid = ’7420060' ORDER BY portal_col_num,portal_row_num;

For further reference, please visit MOS (My Oracle Support) and see the following resolution.

E-PORTAL: What Are The Tables Used By Portal Technology? [ID 651342.1]

Tags: Pagelets, PeopleSoft, PeopleSoft Home page, PeopleSoft Pagelets, Portal

Application Engine Program: PSPAL::Abort: Unexpected Signal Received

When we create an Application Engine program which refers to a State Record, and migrate it to other environment without migrating the State Record, it will get migrated successfully. When we try to run this program on the Batch Server, the following error message will appear.

Record XYZ not defined (108,505)
1341: 1301685557: PSPAL::Abort: Unexpected signal received
1341: 1301685557: PSPAL::Abort: Location: /vob/peopletools/src/pspal/exception_sigaction.cpp:492: RecoverableSignalHandler
1341: 1301685557: PSPAL::Abort: Generating process state report to /xxx/xxx/scripts/LOGS/psae.1341/process_state.txt
1341: 1301685557: PSPAL::Abort: Terminating process now.

In Windows
2564: 1301686035: PSPAL::Abort: Unrecoverable exception received
2564: 1301686035: PSPAL::Abort: Location: E:\pt85010b-retail\peopletools\SRC\pspal\exception_winunhandled.cpp:577: PSPAL::UnhandledExceptionFilter::RecoverableExceptionFilter
2564: 1301686035: PSPAL::Abort: Abort diagnostics generation is currently disabled
2564: 1301686035: PSPAL::Abort: Terminating process now.
PeopleTools 8.50.10 – Application Engine

Record XYZ not defined (108,505)
Message Set Number: 108
Message Number: 505
Message Reason: Record XYZ not defined (108,505)

Solution

Copy the missing AET Record to the target database and its application engine program will work fine.