Question
SINARMASMSIGLIFE
ID
Last activity: 12 Mar 2020 8:41 EDT
Cannot save Data-Admin-Operator-ID
Cannot save Data-Admin-Operator-ID instance to
database.com.pega.pegarules.pub.database.DatabaseException: Database-General Problem writing an
instance to the database 8103 72000 ORA-08103: object no longer exists DatabaseException caused by prior
exception: java.sql.SQLException: ORA-08103: object no longer exists | SQL Code: 8103 | SQL State: 72000
From: (HE341EB7C3EE03711E05D71871A8821E3:192.168.15.16) Caused by SQL Problems. Problem #1,
SQLState 72000, Error code 8103: java.sql.SQLException: ORA-08103: object no longer exists
hello, i got problem about instance Operator ID .
can anyone help about this problem ?
thanks
Coforge DPA
GB
Hi
How are you trying to save the instance?
Is it from activity or you are just saving the Operator id rule.
Regards
Bhavya
SINARMASMSIGLIFE
ID
Hi Bhavya,
i'm trying login from form login PEGA. ( i attach the screenshot ) and this happened suddenly without any changes
Hi Bhavya,
i'm trying login from form login PEGA. ( i attach the screenshot ) and this happened suddenly without any changes
Coforge DPA
GB
Hi
can you please reattach the screenshot, its not uploaded properly.
Regards
Bhavya
SINARMASMSIGLIFE
ID
here i attach the file
Pegasystems Inc.
US
Hi Ryan,
Are you using any custom authentication? Is it just an issue with your operator OR for all the operators?
Can you share the entire log stackTraces? I feel an SR would be more appropriate.
Let me know on the details.
SINARMASMSIGLIFE
ID
hi Harish,
no. i'm not using any custom authenctication, there is no change before.
that issue is appeared suddenly. this is part of the log
2020-03-09 09:53:19,524 [-] [ STANDARD] [ shared] [ PegaRULES:07.10] (.authentication.Authentication) ERROR - Cannot save Data-Admin-Operator-ID instance to database.com.pega.pegarules.pub.database.DatabaseException: Database-General Problem writing an instance to the database 8103 72000 ORA-08103: object no longer exists
DatabaseException caused by prior exception: java.sql.SQLException: ORA-08103: object no longer exists
| SQL Code: 8103 | SQL State: 72000
From: (HC1450F7319EAF7BEC0493DD30669C28B:192.168.14.210) Caused by SQL Problems. Problem #1, SQLState 72000, Error code 8103: java.sql.SQLException: ORA-08103: object no longer exists
com.pega.pegarules.pub.database.DatabaseException: Database-General Problem writing an instance to the database 8103 72000 ORA-08103: object no longer exists
DatabaseException caused by prior exception: java.sql.SQLException: ORA-08103: object no longer exists
| SQL Code: 8103 | SQL State: 72000
Pegasystems Inc.
US
Hi Ryan,
It is unclear what has caused the problem from the log message.
During standard login/log-off, engine does an update to Operator ID record, it seems the save is failed due to the above ORA-08103: object no longer exists error.
It would be best to consult Oracle DBA and seek suggestions as the causes for the above ORA error are not straight forward and somewhat out of scope.
Coforge DPA
GB
Hi
Can you try to trace it and see where exactly it is failing?You can trace the browser requestor session, that will give a bit more clarity.
Regards
Bhavya
Pegasystems Inc.
IN
Can you check with the DB team on their inputs on the Oracle Exception?
Capgemini Engineering
BE
Hello,
Have you tried with other operators and did you get same result or it went fine.
This would isolate issue on particular operator or on global login mechanism.
Could you please also check for your operator in pr_operators table?
Thank you
Regards
Anthony