KB-1111 "No matching tables found!" error thrown after verifying entity mappings even though the tables exist

Elly Meng — Tue, 17 Oct 2023 17:24:58 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 10/17/2023 5:24:58 PM

Symptoms

Creating a data store and verifying the entity mappings fails with error message No matching tables found! after confirming that the tables do exist in the database table or view.

Cause

The schema defined in the XSD is lowercased by Appian when verifying entity mappings. This creates a mismatch in casing between the data store and the entity mappings. This issue affects all Oracle datasources and SQL Server datasources that have case sensitive collation configured.

Action

There are two solutions to this issue:

Lowercase the schema name in the database and add the schema attribute to the XSD.
Create a synonym with the exact name and case as the entity. For example if the entity is named MYENTITY the steps are:
```
DROP SYNONYM XXXXX.MYENTITY;
DROP PUBLIC SYNONYM MYENTITY; 
```
As the Appian database user:
```
CREATE OR REPLACE SYNONYM MYENTITY FOR XXXXXX.MYENTITY;
```
This will ensure that the datasource validation succeeds however querying this datasource would fail. In Oracle for example, the error is:
```
ORA-00942: table or view does not exist 
```
This is typically addressed by ensuring that the XSD entity has the appropriate annotation that maps to the above synonym. For example:
```
@Table(name="MYENTITY")
```

Workaround

For Oracle databases, use an alias for the schema that is lowercase.

For SQL Server databases, configure case insensitive collation.

Affected Versions

This article applies to all versions of Appian using Oracle or SQL Server datasources.

Last Reviewed: February 2017

Tags: sql server, database, infrastructure, oracle

KB-1111 "No matching tables found!" error thrown after verifying entity mappings even though the tables exist

Parmida Borhani — Mon, 30 Jul 2018 03:53:47 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:53:47 AM

Symptoms

Creating a data store and verifying the entity mappings fails with error message No matching tables found! after confirming that the tables do exist in the database table or view.

Cause

Action

There are two solutions to this issue:

Lowercase the schema name in the database and add the schema attribute to the XSD.
Create a synonym with the exact name and case as the entity. For example if the entity is named MYENTITY the steps are:
```
DROP SYNONYM XXXXX.MYENTITY;
DROP PUBLIC SYNONYM MYENTITY; 
```
As the Appian database user:
```
CREATE OR REPLACE SYNONYM MYENTITY FOR XXXXXX.MYENTITY;
```
This will ensure that the datasource validation succeeds however querying this datasource would fail. In Oracle for example, the error is:
```
ORA-00942: table or view does not exist 
```
This is typically addressed by ensuring that the XSD entity has the appropriate annotation that maps to the above synonym. For example:
```
@Table(name="MYENTITY")
```

Workaround

For Oracle databases, use an alias for the schema that is lowercase.

For SQL Server databases, configure case insensitive collation.

Affected Versions

This article applies to all versions of Appian using Oracle or SQL Server datasources.

Last Reviewed: February 2017

Tags: sql server, database, infrastructure, oracle

KB-1111 "No matching tables found!" error thrown after verifying entity mappings even though the tables exist

Nick Vigilante — Fri, 24 Feb 2017 13:11:21 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 1:11:21 PM

Symptoms

Creating a data store and verifying the entity mappings fails with error message No matching tables found! after confirming that the tables do exist in the database table or view.

Cause

Action

There are two solutions to this issue:

Lowercase the schema name in the database and add the schema attribute to the XSD.
Create a synonym with the exact name and case as the entity. For example if the entity is named MYENTITY the steps are:
```
DROP SYNONYM XXXXX.MYENTITY;
DROP PUBLIC SYNONYM MYENTITY; 
```
As the Appian database user:
```
CREATE OR REPLACE SYNONYM MYENTITY FOR XXXXXX.MYENTITY;
```
This will ensure that the datasource validation succeeds however querying this datasource would fail. In Oracle for example, the error is:
```
ORA-00942: table or view does not exist 
```
This is typically addressed by ensuring that the XSD entity has the appropriate annotation that maps to the above synonym. For example:
```
@Table(name="MYENTITY")
```

Workaround

For Oracle databases, use an alias for the schema that is lowercase.

For SQL Server databases, configure case insensitive collation.

Affected Versions

This article applies to all versions of Appian using Oracle or SQL Server datasources.

Last Reviewed: February 2017

Tags: sql server, database, oracle