Known Issue Oracle Database

Overview

The use of an Oracle Database as the database for the FMR is permitted. There is an article here about setting up the database and installing the appropriate JDBC Driver. However, in all versions of FMR before version 11.19.5 there is a potential issue with using an Oracle database. Database tables are automatically created by FMR but in versions before 11.19.4 these tables may be created with particular columns too short to accommodate the information needed to be stored. This has been addressed in subsequent FMR releases, but simply upgrading to a new release will not address this issue.

The Issue

The table below details database tables created by the FMR where specific

Table Name	Column	Definition prior to 11.19.5	Definition after 11.19.15
registry_settings	value	varchar2(255)	varchar2(2048)
registry_environment	value	varchar2(255)	varchar2(4000)
registry_environment	url	varchar2(255)	varchar2(2048)
registry_roles_mapping	urn	varchar2(100)	varchar2(255)
kafka_connection_settings	urn	varchar2(255)	varchar2(2048)

Table Name

The codebase of FMR uses the Hibernate library to generate tables automatically in your database. Hibernate, by design, does not modify existing table definitions. This means that any database tables created in a prior release of FMR may be affected.

TODO - how does it manifest itself

How to determine if you are affected

Using the database tool of your choice, view the tables listed above and check the column structure. If this does not match that as expected, please follow the instructions in the next section.

Methods to Address

Using the database tool of your choice, access the database and locate the following tables. Note they may already contain content so it is important not to lose any data. Modify the following tables

 ALTER TABLE t1 MODIFY col1 VARCHAR2(1000);
 ALTER TABLE t1 MODIFY col1 VARCHAR2(1000);
 ALTER TABLE t1 MODIFY col1 VARCHAR2(1000);
 ALTER TABLE t1 MODIFY col1 VARCHAR2(1000);