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

Unable to find the schema name for the connection to OTHER



Pega admin had issues upgrading from Single schema to split schema.

Error Messages

[java] 2014-10-03 12:38:53,962 [                main] [          ] [                    ] (ernal.access.DataSourceManager) ERROR   - Unable to obtain DataSource for other
[java] Unable to complete import of Application Bundle.
[java] From: (unknown)
[java] at com.pega.pegarules.deploy.internal.archive.ApplicationBundle.doImport(

Root Cause

The problem here is that there exist custom database tables that are mapped to the PegaRULES database.

In PRPC 7.1, the database table will be mapped to PegaDATA, not PegaRULES.  
So admins must temporarily map the custom database tables that are currently mapped to PegaRULES to another database schema, hence a new database schema (e.g. "OTHER" schema) was created and modifed the Database table to point to OTHER instead of PegaRULES.
When running the Rules upgrade script (i.e. the above error was seen. This was due to, inside Database rule for OTHER, "How to connect” option "use JDBC Connection pool" was selected from the drop down.  The database had no datasource defined for this temporary OTHER database.


 In the Database rule for OTHER, select the "How to connect” dropdown option and "use JDBC URL listed below" was selected.  Test the connection.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

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