Issue 1:
In the past there were reported only two cases and apparently looks like Stat cannot insert data into PeopleSoft PSPROJECTDEFN and/or PSPROJECTITEM tables on Staging DB.
That can verified by login to Stage DB using SQL Plus, for example, then generate an insert INTO PSPROJECTDEFN then do a ROLLBACK.
For example:
Insert into PSPROJECTDEFN
(PROJECTNAME, VERSION, PROJECTDESCR, TGTSERVERNAME, TGTDBNAME,
TGTOPRID, TGTOPRACCT, COMPRELEASE, KEEPTGT, TGTORIENTATION,
COMPARETYPE, COMMITLIMIT, REPORTFILTER, MAINTPROJ, LASTUPDDTTM,
LASTUPDOPRID, RELEASELABEL, OBJECTOWNERID)
Values
('TEMP', 1, 'ORA', ' ', 'TEMP_DB', 'PS', ' ', ' ', 31, 0, 1, 50, 0, 0, SYSDATE, 'PS', ' ', ' ');
then ROLLBACK;
While trying the above insert, you should get an error too. However, it was considered more a warning than an error.
Issue 2:
Another customer, instead, reported the cause related to a bad PS Stage cloned. In this case, the staging database had been cloned from another database and a simple step had been missed by the DBA in the cloning process.
The dbowner record in the database had not been updated to reflect the name of the new database.
