Support Article
Invalid object pr_base error during startup after Pega 7 upgrade
Summary
User applications were migrated from PRPC 5.5 SP1 to Pega 7.1.8, and during the server startup, user was getting "Invalid object pr_base" errors.Error Messages
2015-12-21 15:21:42,964 [ server.startup : 2] [ ] [ ] ( etier.engine.EngineStartup) ERROR - Reason:
com.pega.pegarules.pub.database.DatabaseException: Database-General Problem getting connection to read database definitions 208 S0002 Invalid object name 'pr_base'.
From: (unknown)
SQL: select pzPVStream from pr_base where pxObjClass = 'Data-Admin-DB-Name'
Caused by SQL Problems.
Problem #1, SQLState S0002, Error code 208: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr_base'.
at com.pega.pegarules.engine.database.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:148)
at com.pega.pegarules.engine.database.ConnectionManager.rebuildDBNameDefinitions(ConnectionManager.java:2227)
at com.pega.pegarules.engine.database.ConnectionManager.<init>(ConnectionManager.java:500)
at com.pega.pegarules.engine.database.ConnectionManager.getInstance(ConnectionManager.java:620)
at com.pega.pegarules.etier.engine.EngineStartup.initEngine(EngineStartup.java:406)
at com.pega.pegarules.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:136)
at com.pega.pegarules.etier.impl.EngineImpl.doStartup(EngineImpl.java:109)
at com.pega.pegarules.engine.context.EngineImpl.startEngineImpl(EngineImpl.java:221)
at com.pega.pegarules.engine.context.EngineImpl.startEngine(EngineImpl.java:106)
at com.pega.pegarules.engine.context.EngineImpl.startEngine(EngineImpl.java:87)
at com.pega.pegarules.engine.database.ParUtils.initEngineForVfs(ParUtils.java:160)
at com.pega.pegarules.servlet.InitializeServlet.init(InitializeServlet.java:72)
...
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:112)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:951)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by:
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr_base'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454)
...
... 39 moreSteps to Reproduce
Migrate from PRPC 5.5 SP1 to Pega 7.1.8.
Infrastructure setup:
- WebSphere 7
- SQL Server 2008 R2
- AIX
Root Cause
There were prdbutil and prupdmgr applications deployed on the same server which were compatible with PRPC 5.5 SP1.
After upgrade to Pega 7.1.8, these applications were not un-installed from the server, due to which user were getting the following error trace in the log:
2015-12-21 14:45:53,119 [ torada10] [ ] [ ] ( etier.engine.EngineStartup) INFO - OS: AIX, version: 6.1
2015-12-21 14:45:53,119 [ torada10] [ ] [ ] ( etier.engine.EngineStartup) INFO - Architecture: ppc64
2015-12-21 14:45:53,119 [ torada10] [ ] [ ] ( etier.engine.EngineStartup) INFO - PegaRULES Enterprise Tier 5.5 (SP1 General Availability)
2015-12-21 14:45:53,119 [ torada10] [ ] [ ] ( etier.engine.EngineStartup) INFO - v55_relcand_0068: Fri May 22, 2009 4:01:34 PM EDT
Resolution
Un-deploy prdbutil and prupdmgr applications of PRPC 5.5 SP1, and restart the JVM to resolve the issue.
Published January 31, 2016 - 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.