My Oracle Support Banner

How to Resolve "unknown JDBC types for property" and "Table ... does not exist in a table space accessible by the data source" Errors (Doc ID 1476429.1)

Last updated on JUNE 15, 2022

Applies to:

Oracle Commerce Platform - Version 2006.3 and later
Oracle Commerce Merchandising - Version 2006.3 and later
Information in this document applies to any platform.

Goal

Errors and warnings may be logged at startup as SQL repositorities initialize reporting that database tables or columns do not exist even though the tables and columns are properly defined in the database. The SQL repository accesses the database metadata at startup to determine the JDBC type of each property in the repository template which enables the repository to use the appropriate JDBC type in creating SQL queries. It validates the repository definition XML to ensure the following things are present in the configured datasource:

If the table is not found in the default schema or the schema defined by the metaDataSchemaPattern table attribute or the metaDataSchemaPattern property of the repository, the following error will be reported:

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Verify That Tables and Columns Exist
 Check Table Ownership
 Set metaDataSchemaPattern Property on the Repository
 Set metaDataSchemaPattern Attribute on Table Tag
 Set metaDataSynonymTableName Attribute if Using Synonyms
 Specify SQL Types to Bypass Metadata Check
 Set the sql-type Attribute for All Item Properties
 Set the safeSQLTypes Property on the Repository
 Switching Data Source Considerations
 In Case of  CustomProductCatalog-ver
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.