My Oracle Support Banner

Documaker SQL Database Collation (Doc ID 2686281.1)

Last updated on JULY 01, 2020

Applies to:

Oracle Documaker - Version 12.6 and later
Information in this document applies to any platform.

Symptoms

 Oracle recommended us to use the following database collation :
- Latin1_General_CS_AS_WS (Case-sensitive, accent-sensitive, kana-insensitive, width-sensitive)
instead of this one :
- SQL_Latin1_General_CP1_CI_AS (Case-insensitive, accent-sensitive, kana-insensitive, width-insensitive)

This change was required for us to be able to use accents in french words.

So we changed the database collation in one of our environment for “Latin1_General_CS_AS_WS”. Following this change, a lot of SQL errors occurred in Documaker services. Errors of this type :
******************************************************************************************************************************************************
####<May 13, 2020, 2:33:20,899 PM EDT> <Warning> <oracle.adf.controller.faces.lifecycle.Utils> <hostname> <dmkr_server_1_1> <[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'> <DFK3324> <> <c20b059a-eb47-433c-a712-edeb379a05ae-000000b1> <1589394800899> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <ADF: Adding the following JSF error message: Invalid object name 'jobsall'.
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'jobsall'.

Cause

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
Symptoms
Cause
Solution
References


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