Creating the Collaborate system table database or schema

Note: The Collaborate system database must use UTF-8 character encoding. If you do not use UTF-8, you can encounter a problem when you copy certain characters from a Microsoft™ Word document into Collaborate. In an Oracle database, certain characters display as ? when you copy them from Word to a Collaborate field. For DB2®, this issue causes a problem when you view objects. To fix the problem, you must go into the database and remove the problem characters.

Table 1. Guidelines for creating databases or schemas

This two-columned table provides information about the database vendor in one column, and the guidelines that must be followed while you create the database or schema in the second column.

Database vendor	Guidelines
Oracle	Enable the auto commit feature for the environment open. See the Oracle documentation for instructions.
DB2	Set the database page size to at least 16K, or 32K if you need to support Unicode. See the DB2 documentation for instructions.
SQL Server	Use either the SQL Server authentication, or both the SQL Server and Windows™ authentication, because Platform requires SQL Server authentication. If necessary, change the database configuration so that your database authentication includes SQL Server. Also, be sure that TCP/IP is enabled in your SQL Server.
MariaDB	To support Unicode, set the appropriate database collation while creating databases or schemas.

Note: If you plan to enable locales that use multi-byte characters, such as Chinese, Korean, and Japanese, ensure that the database is created to support them.

Note: When you create your databases, you should use the same code page for all of your databases. You cannot change this code page once it is set. If you did not create your databases to use the same code page, you must use only the characters supported in the code page. For example, if you create a zone in global offers that does not use a character in the profile database code page, the global offer does not work.

Note: Database names in Unica Collaborate must follow the naming convention for ordinary identifiers (also known as "non-quoted identifiers or regular identifiers) for the brand of SQL used (DB2, Oracle, SQL Server, MariaDB and so on). Refer to your database provider documentation for specific details. Typically, alphabetic letters, numbers, and underscores are allowed by all flavors of SQL. Hyphens and other characters not permitted in ordinary identifiers will likely cause SQL exceptions.

• http://docs.oracle.com/cd/E11882_01/server.112/e41084/sql_elements008.htm#SQLRF51129
• https://msdn.microsoft.com/en-us/library/ms175874.aspx