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

Pega does not start after restoring a database backup

SA-19124

Summary



After a database backup is restored to the database, Pega fails to start. The backup was obtained from a replication server.


Error Messages



2015-12-07 16:48:25,276 [server-name] [ ] [ ] ( internal.access.DatabaseImpl) INFO - Database version: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
2015-12-07 16:48:25,276 [server-name] [ ] [ ] ( internal.access.DatabaseImpl) INFO - Driver: Oracle JDBC driver
2015-12-07 16:48:25,276 [server-name] [ ] [ ] ( internal.access.DatabaseImpl) INFO - Driver version: 11.2.0.4.0
2015-12-07 16:48:25,447 [server-name] [ ] [ ] (ternal.dictionary.ClassMapImpl) INFO - Reading the class group definitions
2015-12-07 16:48:25,564 [server-name] [ ] [ ] (ternal.dictionary.ClassMapImpl) INFO - Read 56 class group definitions
2015-12-07 16:48:25,564 [server-name] [ ] [ ] (ternal.dictionary.ClassMapImpl) INFO - Reading the class definitions
java.lang.ArrayIndexOutOfBoundsException: -2096602210
at com.pega.pegarules.data.internal.clipboard.directstream.ByteArrayUtil.compare(ByteArrayUtil.java:79)
<snip>
2015-12-07 16:48:36,535 [server-name] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: <server-name>
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:387)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1565)


Steps to Reproduce

1) Restore a database backup.
2) Start Pega application.


Root Cause



Issue is due to the corrupted record.

Resolution



Run the following query to identify the corrupted record:

select * from pr4_base where pxObjClass = 'Rule-Obj-Class'

The issue is resolved when the corrupted file is deleted.

 

Suggest Edit

Published January 30, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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