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.

Troubleshooting: "No Schema Name specified in WebServer for access" for DB2 UDB

Updated on September 25, 2019


The issue documented here was reported for Process Commander V5.4 SP1 but pertains to all versions of Process Commander.

While using the Database Utilities application (prdbutil.war), you encounter the following error message when you attempt to complete the task Verify PegaRULES Process Commander Database Connection:

DB Schema Name: “No Schema Name specified in WebServer for access. Schema Name for Table access determined by DB Connect User's default in Database."

You are likely to encounter this error using DB2 Universal Database (UDB) in this scenario: The database user specified for the PegaRULES database has access to multiple schemas in the same database or in multiple databases. Consequently, the JDBC cannot determine which schema to connect to.



Suggested Approach

Choose an approach that meets your deployment needs:

  • Maintain one PegaRULES database with one schema for each installation of Process Commander.
  • Maintain multiple schemas with distinct names as described in the related topics.

Related Topics

Troubleshooting: Database-Saver-InsertUpdatefail error caused by multiple database schemas on a single instance of the PegaRULES database

Troubleshooting: "Obj-Save is trying to write to a non-existent column"

How to use fully-qualified table names in the PegaRULES database

  • Previous topic Troubleshooting: duplicate pzInsKeys error after setting up a copy of the pc_work table
  • Next topic Clipboard

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