RDB methods are failing with table or View doesnt exists wheras OBJ rules are working without any issues
We have an application hosted on Pega 7.3.1 with Oracle 11g Data base . We did a Data Base only upgrade to Oracle cloud 12 CR2 where the whole Data and rules Schemas were exported and imported directly into cloud 12Cr2.
Post that , we are able to launch the application and all other transactions are working but RDB methods are failing with the below errors
"There was a problem getting a list: code: 942 SQLState: 42000 Message: ORA-00942: table or view does not exist"
We are using RDB rules for few of the tables under the PegaData Schema to browse/ Save /Delete. we were told by DBA that those tables exists on PegaDATA schema.
i suspect its an issue with grants but DBA confirmed PEGADATA has required access on those tables.
Is there anyway we can resolve this issue.
Attaching the log trace below.
Error in RDB-Delete com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 942 SQLState: 42000 Message: ORA-00942: table or view does not exist
Proximus
BE
It's a typical synonym error.
Easy test: connect directly to the DB with the same user as the one of your application.
select * from yourTable: should fail
select * from yourSchema.yourTable: should work
Regards
Anthony
Lloyds
GB
Hi Antony,
I tried to run the query directly on DB but both the below queries are running without any issues
select * from yourTable
select * from yourSchema.yourTable:
Proximus
BE
You're connected with the same user as your application?
Then you could check the code to make sure that your code is not calling the DB in Rule Schema while table is defined in Data schema.
Your application user should btw have access to both schema.
If the code calls Rules.yourTable and Syn is defined on PegaData then it will not work.
Since the 2 SQL works, at first sight, all is OK at DB level. So the call is made differently in the DB.
It also happens that a table is created in both schema for any (usually incorrect) reason, but the synonym should be defined to the good one in the correct schema.
then select * from yourTable will work, select * from DATA.yourTable will also work yet your app code calls RULES.yourTable or opposite way DATA/RULES.
Luxoft
SG
Hi,
Can you compare the sql that ran in the backend with Obj method with the sql of RDB method and see if they align as you expected.
Also, as you are connecting to internal DB, check in the sqls whether database schema is used correctly or not along with the table/view name.
Sometimes, case-sensitiveness of the table/view names may also impact.
Please try these and let the forum know if this works or the solution if you find any.