Cleo Clarify users upgrading to JDE Oracle 12c database might want to research the necessity of moving to V2.

Currently in V1 there have been cases where a Database Adapter Select, of any JDE table, caused the following error in the Cleo Clarify Auditor.

2018-10-18 11:57:18,280 [DEBUG] - JDBC Resource Adapter got a result set containing 34 columns.
SZDOCO - NUMBER (2)
SZKCOO - NCHAR (-15)
SZDCTO - NCHAR (-15)
SZLNID - NUMBER (2)
SZDOC - NUMBER (2)
SZDCT - NCHAR (-15)
SZMCU - NCHAR (-15)
SZITM - NUMBER (2)
SZLITM - NCHAR (-15)
SZAITM - NCHAR (-15)
SZDSC1 - NCHAR (-15)
SZUORG - NUMBER (2)
SZSHAN - NUMBER (2)
SZAN8 - NUMBER (2)
SZALPH - NCHAR (-15)
SZFRTH - NCHAR (-15)
SZCRCD - NCHAR (-15)

[DEBUG] - JDBC Resource Adapter is FINALLY attempting to close the JDBC Connection.
Error executing adapter : Unsupported SQL column type: -15 in column 2
java.lang.IllegalArgumentException: Unsupported SQL column type: -15 in column 2
Error executing adapter - 2
java.lang.ArrayIndexOutOfBoundsException: 2

The ‘simple’ solution was to move rulesets, sqlAccess, database adapter, business processes, and RDO objects to Version 2 of Cleo Clarify.