ORA-00980 during import PegaNBAM_FW_0712.jar
During Next Best Action Marketing v7.12 we tried to import PegaNBAM_FW_0712.jar following the installation documentation but failed an exception via Import Wizard.
The exception is as below.APP_PEGA_EXT_DATA is the PegaNBAM external Data user.
There are problems applying changes to the database object:
MKT_INTERACTION_DETAIL SQL: CREATE VIEW APP_PEGA_EXT_DATA.MKT_INTERACTION_DETAIL AS SELECT ifr.pxFactId AS pxFactId, ifr.pySubjectId AS pySubjectId, CASE isr.pyOutcome WHEN 'Pending' THEN 1 ELSE 0 END AS Pending, CASE isr.pyOutcome WHEN 'Impression' THEN 1 ELSE 0 END AS Impression, CASE isr.pyOutcome WHEN 'Clicked' THEN 1 ELSE 0 END AS Clicked, CASE isr.pyOutcome WHEN 'Accepted' THEN 1 ELSE 0 END AS Accepted, isr.pyoutcome AS outcome, irc.pycategory AS pycategory FROM pr_data_ih_fact ifr LEFT OUTER JOIN pr_data_ih_dim_context irc ON (ifr.pzcontextid = irc.pzid) LEFT OUTER JOIN pr_data_ih_dim_outcome isr ON (ifr.pzoutcomeid = isr.pzid)
ERROR: Database-General Problem executing SQL to update database schema 980 42000 ORA-00980: synonym translation is no longer valid.
Steps to Reproduce
Tried to re-import PegaNBAM_FW_0712.jar from Pega7.1.7
The root cause of this problem is software use/operation error. During investigation it revailed that synonym import jar looking for doesn't exist. The creation of these SYNONYM is done via Install_PegaNBAM.sh/Install_PegaNBAM.bat depending upon your OS.Administrator observed error reported in log generated during running Install_PegaNBAM.bat.
Problem was resolved by performing manual configuration at database level such as re-creating the synonyms and granting the users with appropriate permissions.
Published January 31, 2016 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.