SUMMARY:
In Strategy Universal 9.x and 10.x end users may receive a SQLFetch error after upgrading their database to Oracle 12c. This will be seen when the database has a character code page that does not match the code page of the data being entered. This issue has been classified as a defect in Strategy Universal 9.x and and 10.x The current action is to alter the character page of the database to match the code page of the data being entered.
SYMPTOM:
After upgrading to Oracle 12c, an end user finds that some reports now show either a SQLFetch error or do not return data.
CAUSE:
This issue is believed to be caused by data being placed into a database that does not contain a matching character code page. The data being placed in the database should comply or be formatted to comply with that of the character page of the database. It is believed in older versions of Oracle that the missing information relating to the character code points was filled in by the database allowing the driver to successfully return the data.
The driver itself should return an error relating to character conversions not the SQLFetch error. The lack of an error related to characters conversions has been classified as a defect in Strategy Universal 9.x and 10.x .
ACTION:
To resolve this issue, database administrators should alter the character page of the database to a character page that does not exclude characters that are being entered. A database administrator could also alter the ETL process to process the data into the correct format to match the character set of the database.
TROUBLESHOOTING STEPS:
In the event that altering your code page does not allow the issue to be resolved, it is recommended to contact Strategy Technical Support with the following information:
