Introduction / FirstSpirit Server configuration / Database connection / Data source configuration / Oracle-specific parameters
Description of the Oracle-specific parameters
 |
A subsequent change of the parameter values "jdbc.MAXSTRINGLENGTH", "jdbc.oracle.CHARACTERSET" and "jdbc.property.oracle.jdbc.J2EE13Compliant" is not possible! If you change your FirstSpirit database schema, new columns would then potentially be created and content already edited would no longer be accessible. |
<database>.jdbc.oracle.CHARACTERSET (Oracle19cLayer only)
The database characterset has to be specified via this parameter. We recommend the following setting:
jdbc.oracle.CHARACTERSET=AL32UTF8
If AL32UTF8 is selected here, NLS_CHARACTERSET must also have this value. FirstSpirit then saves data as VARCHAR2. If the value here is UTF8 or AL16UTF16, NLS_NCHAR_CHARACTERSET should have the corresponding value. In this case FirstSpirit saves the data in the database as NVARCHAR2.
The choice of characterset influences the maximum lenght of contents that can be saved “natively” in a column. See section <database>.jdbc.MAXSTRINGLENGTH under Optional parameters for a comparison of UTF8, AL16UTF16, and AL32UTF8.
<database>.jdbc.oracle.TABLESPACE:
A tablespace must be specified via this parameter (required parameter),
e.g.
jdbc.oracle.TABLESPACE=USERS
<database>.jdbc.property.oracle.jdbc.J2EE13Compliant (Oracle19cLayer only)
The connection parameter jdbc.property.oracle.jdbc.J2EE13Compliant must be specified in the database layer so that it can be used by FirstSpirit.
jdbc.property.oracle.jdbc.J2EE13Compliant=true
In a later version, this connection parameter will be dropped and the behavior will correspond to the activated option. If the dms.jar is used, the option is automatically activated. Otherwise, the option must be specified explicitly upon connection establishment.