|
Oracle |
|
Supported Oracle Versions Collaborator supports Oracle 11gR2, 12c, 18c and 19c. Note: Oracle database is only supported in Collaborator Enterprise. For a complete list of differences between Collaborator editions, please see the comparison page. Oracle's extended support for the Oracle 11g database will end on 31st of December 2020 and Collaborator will no longer be able to support it.
Install and Configure Database Create a database for Collaborator. It is recommended that you also create a username/password pair just for Collaborator and give this account full access to the database and no access to other databases. Install the CTX_DDL PL/SQL package on your DB server and grant the EXECUTE privileges on CTX_DDL to your Oracle user of Collaborator Server. This package allows use of the Oracle Text component instead of regular expression query for full-text searches from the Web Client. By default, Oracle databases search based on regular expressions. If the default settings do not suit your requirements, you can change them on the Oracle side or through Collaborator admin UI. Once done, restart your Collaborator server to complete its upgrade. When installing Collaborator on a server, the installation wizard will prompt for the Oracle server host name, TCP/IP port (default is 1521), database service name (not the SID!), user name, password and path to JDBC driver. The installer will not report any connectivity errors. Warning: The database service name is not the same thing as the SID! This change was made by Oracle in version 9iR2. When you first visit the web page for Collaborator, it will detect that you have a new database and will create all tables, indexes, and views for you automatically, or give you an appropriate error message if there is a connectivity problem. Connectivity problems should be resolved by re-running the installer. Oracle Limitations
-Duser.country=US -Duser.language=en
Troubleshooting We use the Oracle JDBC driver to connect to your Oracle database. The driver has a few undocumented behaviors that may come as a surprise. There are threads on Oracle's tech support forums about this. Most of the problems arise in the GLOBAL_DBNAME field in your SID_DESC entry from your listener.ora file. A typical entry might look like this: (SID_DESC = (GLOBAL_DBNAME = mysid.mydomain.com) (ORACLE_HOME = /appl/oracle1/product/10.2.0.1) (SID_NAME = mysid) )
Most other Oracle-based programs use the SID_NAME field to identify the database, but the JDBC driver uses GLOBAL_DBNAME. This would cause a connection error in the example above. Also note that the database service name is not the same thing as the SID. This change was made by Oracle in version 9iR2. The installer asks for the database service name, not the SID. The database service name is also sometimes referred to as "TNS alias" or "connect descriptor". Typically, this means you should use the GLOBAL_DBNAME in the installer (that is, mysid.mydomain.com) and not just the SID (that is, mysid). |
|
© 2003-2025 SmartBear Software. All rights reserved. |