Support Article
Error while inserting columns
SA-33944
Summary
Whenever user is trying to insert two column pyFirstName and pyLastName, user is getting error on login screen.
Error Messages
Cannot save Data-Admin-Operator-ID instance to database.com.pega.pegarules.pub.database.DatabaseException: ORA-00904: "PYFIRSTNAME": invalid identifier DatabaseException caused by prior exception: java.sql.BatchUpdateException: ORA-00904: "PYFIRSTNAME": invalid identifier | SQL Code: 904 | SQL State: 42000 DatabaseException caused by prior exception: java.sql.SQLSyntaxErrorException: ORA-00904: "PYFIRSTNAME": invalid identifier | SQL Code: 904 | SQL State: 42000 From: (H9063DB791D5A89FDF9605B761001ECE3:XX.XXX.XX.XXX) SQL: MERGE INTO PEGADATA.pr_operators t USING (SELECT ? "pzInsKey" , CURRENT_TIMESTAMP"pxCommitDateTime" , ? "CostLocation" , ? "CostLocationUnit" , ? "pxCreateDateTime" , ? "pxCreateOperator" , ? "pxCreateOpName" , ? "pxCreateSystemID" , ? "pxInsName" , ? "pxObjClass" , ? "pxSaveDateTime" , ? "pxUpdateDateTime" , ? "pxUpdateOperator" , ? "pxUpdateOpName" , ? "pxUpdateSystemID" , ? "pyAccessGroup" , ? "pyAllowRuleCheckOut" , ? "pyCalendar" , ? "pyCountry" , ? "pyDefaultTimeZone" , ? "pyDepartment" , ? "_pyAddresses_Email__pyEmailAdd" , ? "pyExtension" , ? "pyImageFileName" , ? "pyLabel" , ? "pyLastSignon" , ? "pyLicenseType" , ? "pyOpAvailable" , ? "pyOrganization" , ? "pyOrgDivision" , ? "pyOrgUnit" , ? "pyOwner" , ? "pyPosition" , ? "pyReportTo" , ? "pyRuleSetName" , ? "pySubstituteOperator" , ? "pyUserIdentifier" , ? "pyUserName" , ? "pyWorkGroup" , ? "pzHasOperatorLocked" , ? "SIPLinkID" , ? "EMAILFORFOLLOWEDITEM" , ? "pyFirstName" , ? "pyLastName" , ? "pzPVStream" FROM dual) inputs ON (t.pzInsKey = inputs."pzInsKey") WHEN MATCHED THEN UPDATE SET "COSTLOCATION" = inputs."CostLocation" , "COSTLOCATIONUNIT" = inputs."CostLocationUnit" , "PXCREATEDATETIME" = inputs."pxCreateDateTime" , "PXCREATEOPERATOR" = inputs."pxCreateOperator" , "PXCREATEOPNAME" = inp
Steps to Reproduce
Add pyFirstName and pyLastName columns into pr_operators table.
Root Cause
Pega expects the database table's column names to be in upper case.
Resolution
Keeping the names of the columns as PYFIRSTNAME, PYLASTNAME instead of pyFirstName, pyLastName respectively resolves the issue.
Published March 15, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.