Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Database-NonexistentTable error in logs

SA-30018

Summary



The below error appears in the logs. There is no known effect on application processing.


Error Messages



(BIndexes.PegaAESRemote_.Action) ERROR - PegaAESRemote : Exception while fetching indexes for table name BRD_FW_PISPrdFW_Work, schema name DATA, db name PegaDATA
com.pega.pegarules.pub.database.fException: Database-NonexistentTable DATA.BRD_FW_PISPrdFW_Work PegaDATA
From: (BDF409BAB74E9CF2A1BD6D58E49E8883D)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.lookupColumnInfo(TableInformationMapImpl.java:651)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.lookupTableInfo(TableInformationMapImpl.java:500)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.get(TableInformationMapImpl.java:384)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.get(TableInformationMapImpl.java:346)
at com.pega.pegarules.data.internal.access.DatabaseTableImpl.isView(DatabaseTableImpl.java:446)
at com.pegarules.generated.activity.ra_action_pushdbindexes_8c63caf56bbf17baa0f39a6bc799a162.step9_circum0(ra_action_pushdbindexes_8c63caf56bbf17baa0f39a6bc799a162.java:942)
at com.pegarules.generated.activity.ra_action_pushdbindexes_8c63caf56bbf17baa0f39a6bc799a162.perform(ra_action_pushdbindexes_8c63caf56bbf17baa0f39a6bc799a162.java:221)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:945)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1259)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:901)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:670)
at com.pega.pegarules.session.internal.async.Agent.queueBatchActivityForAgent(Agent.java:1504)
at com.pega.pegarules.session.internal.async.Agent.queueBatchActivityForAgent(Agent.java:1293)
at com.pega.pegarules.session.internal.async.AgentQueue.run(AgentQueue.java:792)
at com.pega.pegarules.session.internal.async.Agent.runAgentTask(Agent.java:936)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:221)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:167)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:315)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)
at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:245)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:155)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask.run(AsyncTask.java:64)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(RunnableWrapper.java:71)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:271)
at java.security.AccessController.doPrivileged(AccessController.java:364)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at com.ibm.ws.asynchbeans.WLMABWorkItemImpl.run(WLMABWorkItemImpl.java:68)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)


Steps to Reproduce



Not Applicable 


Root Cause



This is indicative that there is a Data-Admin-DB-Table instance in the monitored node (which is pushing the DB indices to AES via the agent) which refers to the table DATA.BRD_FW_PISPrdFW_Work in PegaDATA schema but that table is not present in that schema.

Resolution



Look for Data-Admin-DB-Table instance and check why it is referring to a non-existent table and take appropriate action.

Published November 5, 2016 - Updated October 8, 2020

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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us