Question

1
Replies
301
Views
AnimeshD6938 Member since 2015 32 posts
Accenture Services Pvt Ltd
Posted: 3 years ago
Last activity: 3 years 10 months ago
Closed

Issue while upgrade Pega Government Platform 7.16 to 7.21

hi,

We have a environment on PRPC7.1.9 with PGP7.16 running on WAS7.0.0.25. Now we upgraded that to PRPC7.2.1 with WAS8.5.5.8.

While upgrading the framework from PGP7.16 to 7.21 we are getting issue and not able to import the jar file. Please find the log below.

Also we didn't find any upgrade document for PGP7.21 framework in PDN.

current cursor size is 10000 and process 500. But still same issue.

Could anyone please suggest.

Caused by:

com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 1000 SQLState: 72000 Message: ORA-01000: maximum open cursors exceeded

ORA-06512: at "PRPCDATA.SPPR_SYS_RESERVEQUEUEITEM_B", line 152

ORA-01000: maximum open cursors exceeded

ORA-06512: at line 1

DatabaseException caused by prior exception: java.sql.SQLException: ORA-01000: maximum open cursors exceeded

ORA-06512: at "PRPCDATA.SPPR_SYS_RESERVEQUEUEITEM_B", line 152

ORA-01000: maximum open cursors exceeded

ORA-06512: at line 1

| SQL Code: 1000 | SQL State: 72000

From: (B796CB8DEC7B5177EF1ED191DE9691F4A)

SQL: {call PRPCDATA.sppr_sys_reservequeueitem_b ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) }

Caused by SQL Problems.

Problem #1, SQLState 72000, Error code 1000: java.sql.SQLException: ORA-01000: maximum open cursors exceeded

ORA-06512: at "PRPCDATA.SPPR_SYS_RESERVEQUEUEITEM_B", line 152

ORA-01000: maximum open cursors exceeded

ORA-06512: at line 1

at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:262)

at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:4844)

at com.pega.pegarules.data.internal.access.DBQueryExecutor.executeRDB(DBQueryExecutor.java:115)

at com.pega.pegarules.data.internal.access.DBQueryExecutor.executeRDB(DBQueryExecutor.java:66)

at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:5210)

at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:5190)

at com.pega.pegarules.session.internal.async.agent.QueueManagerImpl$QueueIteratorImpl.next(QueueManagerImpl.java:2008)

------------------

[10/20/16 8:20:04:086 EST] 0000005d SystemOut O 2016-10-20 08:20:03,462 [.PRPCWorkManager : 0] [ STANDARD] [ shared] [ PegaRULES:07.10] (ternal.util.SchemaImporterTool) ERROR Administrator@pega.com - Unable to make schema change because database name is null: code: <none> SQLState: <none> Message: <none>

com.pega.pegarules.pub.database.DatabaseException: Unable to make schema change because database name is null: code: <none> SQLState: <none> Message: <none>

From: (B934DCAA231A90076E89F6E96AD9A9E23)

at com.pega.pegarules.data.internal.access.DatabaseImpl.executeDBSchemaDDL(DatabaseImpl.java:5749)

[10/20/16 8:20:04:086 EST] 0000005d SystemOut O 2016-10-20 08:20:03,478 [.PRPCWorkManager : 0] [ STANDARD] [ shared] [ PegaRULES:07.10] (ernal.async.BatchRequestorTask) ERROR Administrator@pega.com - Batch activity "Rule-.PegaRULESMove_Zip_To_DB" threw:

com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError

at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.

***Updated by moderator: Lochan to move from PSC to Pega Upgrade Center***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn