# Error encountered investigating table: Database-NonexistentTable

**URL:** <https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505>\
**Category:** General\
**Created:** [September 17, 2026, 6:23pm UTC](https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505 "2026-09-17T18:23:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SheelK87](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SheelK87](https://forums.pega.com/u/SheelK87)\
**Post date:** [September 17, 2026, 6:23pm UTC](https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505/1 "2026-09-17T18:23:59Z")

</div>

Hi,  
I am connecting to an external database, while mapping I am getting this error.  
Anyone has any idea or solution for this ?  
Note - When we are running from query in backend it is working fine.

 ![image](https://pega1.discourse-cdn.com/pega/original/3X/f/7/f70897c9e0297787c41277b495813100ed048451.png)

---

<div class="post-metadata">

**Author:** ![Sairohith](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/sairohith/32/23362_2.png) [@Sairohith](https://forums.pega.com/u/Sairohith)\
**Post date:** [September 18, 2026, 1:07am UTC](https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505/2 "2026-09-18T01:07:11Z")

</div>

The error is caused by Pega not recognizing the external database table correctly during class mapping.  
Use **lowercase letters for both the schema name and the table name** in the external database.  
Make sure the same lowercase schema and table names are selected in the Pega Database Table Class Mapping wizard.  
This is important because Pega’s table investigation can be case-sensitive even when the query works directly in the database.  
After updating the names, refresh the database connection and run the mapping again.  
This has resolved the same `Database-NonexistentTable` issue reported with external database mapping in Pega.

---

<div class="post-metadata">

**Author:** ![SheelK87](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SheelK87](https://forums.pega.com/u/SheelK87)\
**Post date:** [September 18, 2026, 6:58am UTC](https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505/3 "2026-09-18T06:58:28Z")

</div>

Thanks for your response, so we have to ask external database to update the table names ?

---

<div class="post-metadata">

**Author:** ![Sairohith](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/sairohith/32/23362_2.png) [@Sairohith](https://forums.pega.com/u/Sairohith)\
**Post date:** [September 18, 2026, 11:04am UTC](https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505/4 "2026-09-18T11:04:07Z")

</div>

Yes, if the external database is PostgreSQL and the table or schema was created with mixed or uppercase letters, ask the database team to use lowercase names.  
Pega has reported this `Database-NonexistentTable` issue when PostgreSQL table or schema names use uppercase characters.  
The schema name and table name should both be created in lowercase.  
After the database team updates the names, use those same lowercase names in the Pega external table mapping.  
Then refresh the connection and run the class mapping again.  
This should allow Pega to recognize the external table correctly.

---

<div class="post-metadata">

**Author:** ![SheelK87](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SheelK87](https://forums.pega.com/u/SheelK87)\
**Post date:** [September 18, 2026, 12:56pm UTC](https://forums.pega.com/t/error-encountered-investigating-table-database-nonexistenttable/13505/5 "2026-09-18T12:56:59Z")

</div>

After using lowercase name for table we are not getting error.  
But while pulling the records via obj browse we are getting error.

We are connecting to Pega supported PostgresDB.

 ![image](https://pega1.discourse-cdn.com/pega/original/3X/d/1/d19753c9bd48ef9acbe1e5212a9dea5617dd7944.png)