This blog entry applies if you're building a new repository (docbase), with Oracle as the RDBMS and going through Documentum Server Configuration program on the Content Server. (CS vers 6.0 SP1) This install is for Windows servers but same basic ideas apply to UNIX/Linux. The db user (repository owner) must be able to:
- Connect to the database
- Create tables, views, and indexes in the database
- Insert records (rows) into the tables
- Drop tables, views, and indexes
This information is not new; however, it's often a problem connecting to the db. Here are some items to check:
a. make sure you have an Oracle client installed on the server. For install using Content Server version 6.0, SP1, the 10g_win32_client works.
Install as Administrator type. Not recommended to use Oracle "light" clients; I've had install problems with those.
b. once Oracle client is installed make sure you copy a tnsnames.ora file to the correct location. Typically this is
...\Oracle\product\10.1.0\Client_x\NETWORK\ADMIN
c. you may have multiple "Client_x" directories. Make sure you copy tnsnames.ora to the correct Client_x directory.
d. probably a good idea to verify that you can connect from Oracle SQL Plus. This small application will have been installed when you installed Oracle Client. Access SQL Plus via
Start Menu, Oracle Version x, Application Development. Run SQL Plus and make a connection, which verifies that from this server the repository owner can connect to Oracle.
e. through SQL Plus create a table. Here's a sample statement. At the SQL prompt enter:
create table TestTable(column1 varchar2(30));
f. next drop the table. This verifies Oracle user has rights to create and drop a table.
drop table TestTable;
Note of caution...sometimes tnsnames.ora becomes corrupt, because of stray characters or illegal entries. If this is the case you may want to reduce the tnsnames.ora file to only theconnection entry (string) that pertains. This may help to mitigate failures. This seems like common sense but usually tnsnames.ora files contain many entries for different connections and usually there is not a problem. If you get odd connection errors removing all but the single connection entry may help.
For further info:
1. EMC® Documentum® Content Server Version 6 Installation Guide. Available at EMC web site, support account required.
2. see Oracle support forums or similar & you'll read many, many problems people have with tnsnames.ora files: http://forums.oracle.com