Question

6
Replies
239
Views
MANOJPDN Member since 2009 21 posts
Rulesware LLC
Posted: 4 years ago
Last activity: 4 years 7 months ago
Closed

PR_SY_TMP table getting created automatically and holding System-locks

After 718 MLU upgrade we are observing a table called  PR_SY_TEMP is getting created automatically  and is holding instances whose pxobjclass is System--Locks.

Did not find any documentation on this in uprgade guide or is it present in the DDLs generated from pega media. Please let us know what is this table used for, and if its automatic creation isfine?

TABLE STRUCTURE ( taken from Oracle SQL developer)

   ( "PXCREATEDATETIME" DATE,

  "PXCREATEOPNAME" VARCHAR2(128 BYTE),

  "PXCREATEOPERATOR" VARCHAR2(128 BYTE),

  "PXCREATESYSTEMID" VARCHAR2(32 BYTE),

  "PXEXPIREDATETIME" DATE,

  "PXINSNAME" VARCHAR2(128 BYTE),

  "PXLOCKHANDLE" VARCHAR2(255 BYTE),

  "PXOBJCLASS" VARCHAR2(96 BYTE),

  "PXOWNERID" VARCHAR2(255 BYTE),

  "PXSYSTEMNAME" VARCHAR2(64 BYTE),

  "PXSYSTEMNODE" VARCHAR2(64 BYTE),

  "PXUPDATEDATETIME" DATE,

  "PXUPDATEOPNAME" VARCHAR2(128 BYTE),

  "PXUPDATEOPERATOR" VARCHAR2(128 BYTE),

  "PXUPDATESYSTEMID" VARCHAR2(32 BYTE),

  "PXUSERHOST" VARCHAR2(64 BYTE),

  "PYLABEL" VARCHAR2(64 BYTE),

  "PZINSKEY" VARCHAR2(255 BYTE) NOT NULL ENABLE,

  "PXCOMMITDATETIME" DATE,

  "PXSAVEDATETIME" DATE

}

Does this have anything to do with Hazelcast, we have already disabled it in prconfig.xml

System Administration
Moderation Team has archived post
Share this page LinkedIn