Oracle

Initialization parameters

When you use an Oracle database with IBM® SPSS® Collaboration and Deployment Services, the following parameters and configurations must be followed. Changes are made to the init.ora and spfile.ora parameter files.

Table 1. Oracle database Parameters
Parameter	Setting
OPEN_CURSORS	300
NLS_CHARACTERSET	AL32UTF8
NLS_NCHAR_CHARACTERSET	AL16UTF16
SESSIONS_PER USER	Equal to, or greater than, 100

Note: Set both NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET when you create the Oracle instance.

Tip: To address case sensitivity of user login values, use parameters such as NLS_LANG, NLS_COMP, or NLS_SORT for your Oracle instance. See the Oracle documentation to determine which parameter best addresses your needs.

Oracle XDB

For an Oracle database, Oracle XDB (XML database feature) must be installed. You can verify that by querying for schema (user account) XDB (SELECT * FROM ALL_USERS), or by verifying that RESOURCE_VIEW exists (DESCRIBE RESOURCE_VIEW). The Oracle principal that is used with IBM SPSS Collaboration and Deployment Services Repository must be granted the XDBADMIN role.

Errors when migrating data from 12c to 19c

When upgrading from 12c to 19c, note that the following nine user rule names in 12c no longer exist in 19c:

XS_RESOURCE
JAVA_DEPLOY
SPATIAL_WFS_ADMIN
WFS_USR_ROLE
SPATIAL_CSW_ADMIN
CSW_USR_ROLE
APEX_ADMINISTRATOR_ROLE
APEX_GRANTS_FOR_NEW_USERS_ROLE
DELETE_CATALOG_ROLE

If you used these roles in 12c, you'll see the following errors when importing data to 19c:

ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'XXX' does not exist
Failing sql is:
 GRANT "XXX" TO "%schemaName%" WITH ADMIN OPTION

Since some rule names have changed in 19c, your database administrator should ensure that corresponding new rule permissions are granted manually before performing the import. Doing this will prevent these errors from impacting your installation and use of IBM SPSS Collaboration and Deployment Services.