Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Issue: Must delete temporary files (V4.2SP3 and SQL Server)

Updated on September 13, 2021


When using a Microsoft SQL Server relational database, temporary files are created and stored in the Windows TEMP directory every time Process Commander is initialized. Eventually, these may cause initialization to fail.

Update : This issue does not occur with V4.2SP4 and later releases. The workaround presented here applies to V4.2SP3 and earlier releases.

The workaround is to clear out these files from the TEMP directory regularly, to be sure there is enough space for Process Commander's start-up temporary files.



Suggested Approach

When Process Commander uses a Microsoft SQL Server relational database, it creates temporary files in the TEMP directory every time Process Commander is initialized. For example, starting the Process Commander server creates ten of these files.

java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error setting up static cursor cache.
   at Source)
   at Source)
   at Source)
   at Source)
   at Source)
   at<init>(Unknown Source)
   at Source)
   at Source)
   at Source)
   at Source)
   at com.pega.pegarules.engine.database.DatabaseTableMap.lookupTableInfo(
   at com.pega.pegarules.engine.database.DatabaseTableMap.get(
   at com.pega.pegarules.engine.database.ClassMap.init(
   at com.pega.pegarules.engine.database.DatabaseImpl.<init>(
   at com.pega.pegarules.engine.context.PRThreadImpl.<init>(
   at com.pega.pegarules.engine.context.PRRequestorImpl.getThread(
   at com.pega.pegarules.engine.context.PRRequestorImpl.setRulesetsAndRoles(
   at com.pega.pegarules.engine.context.PRRequestorImpl.initializeRequestor(
   at com.pega.pegarules.engine.context.PRRequestorImpl.<init>(
   at com.pega.pegarules.engine.context.PRNodeImpl.createRequestor(
   at com.pega.pegarules.engine.context.PREnvironment.initialize(
   at com.pega.pegarules.engine.context.PREnvironment.getInstance(
   at com.pega.pegarules.engine.context.PREnvironment.getInstance(
   at com.pega.pegarules.web.PRStartup.init(
   at javax.servlet.GenericServlet.init(
   at org.apache.catalina.core.StandardWrapper.loadServlet(
   at org.apache.catalina.core.StandardWrapper.load(
   at org.apache.catalina.core.StandardContext.loadOnStartup(
   at org.apache.catalina.core.StandardContext.start(
   at org.apache.catalina.core.ContainerBase.start(
   at org.apache.catalina.core.StandardHost.start(
   at org.apache.catalina.core.ContainerBase.start(
   at org.apache.catalina.core.StandardEngine.start(
   at org.apache.catalina.core.StandardService.start(
   at org.apache.catalina.core.StandardServer.start(
   at org.apache.catalina.startup.Catalina.start(
   at org.apache.catalina.startup.Catalina.execute(
   at org.apache.catalina.startup.Catalina.process(
   at java.lang.reflect.Method.invoke(Native Method)
   at org.apache.catalina.startup.Bootstrap.main(


  • Previous topic Issue: Cannot use SQL keywords as database column names
  • Next topic Issue: Must restart application server after database server restart


Pega Platform 7.1.1 - 8.3.1 System/Cloud Ops Administrator System Administration Low-Code App Development

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us