Kevin Yeandel’s Random Access Memory

After running the uninstaller clean up the schema. Useful in cases of migration when sysadmin’s password can’t be legally extracted from the Oracle dba and you need to crack on.

set heading off
set feedback off
spool dropobj_x.sql
select ‘drop ‘||object_type||’ ‘||object_name||’ ;’
from user_objects
where object_type <> ‘INDEX’
and object_type <> ‘DATABASE LINK’
and object_type <> ‘PACKAGE BODY’
and object_type <> ‘TRIGGER’
and object_type <> ‘LOB’
order by created;
spool off
set heading on
set feedback on

If you have to have your schema created for you by the hosting company then this is what is required.
Make sure to ask the developers if any triggers will be required as you may wish to add this at the same time.

Schema Parameters        (Tried, tested and in use)
GRANT ALTER SESSION TO xy_resource;
GRANT CREATE DATABASE LINK TO xy_resource;
GRANT CREATE INDEXTYPE TO xy_resource;
GRANT CREATE OPERATOR TO xy_resource;
GRANT CREATE PROCEDURE TO xy_resource;
GRANT CREATE PUBLIC SYNONYM TO xy_resource;
GRANT CREATE ROLE TO xy_resource;
GRANT CREATE SEQUENCE TO xy_resource;
GRANT CREATE SESSION TO xy_resource;
GRANT CREATE SYNONYM TO xy_resource;
GRANT CREATE TABLE TO xy_resource;
GRANT CREATE TYPE TO xy_resource;
GRANT CREATE VIEW TO xy_resource;
GRANT SELECT_CATALOG_ROLE TO xy_resource;

In the case that the service provider maintains the Oracle instance which you are to use and wishes to create the database in advance, they will need to create the database

SQL> CREATE TABLESPACE DM_TEST_02_docbase DATAFILE ‘/U02/ORADATA/DM1/dm_TEST_0220071018141334_db.dbf’ SIZE 250M REUSE;

Then
SQL> ALTER DATABASE DATAFILE ‘/U02/ORADATA/DM1/dm_TEST_0220071018141334_db.dbf’ AUTOEXTEND ON NEXT 10M MAXSIZE 2048M;

Then grant essential privs to the docbase owner (schema account) so that the installation can commence:

SQL>GRANT CREATE ANY VIEW,RESOURCE,UNLIMITED TABLESPACE to TEST_02 ;

Platform

In these notes I am using Documentum 6 on Windows XP Prof with Oracle 10. something.

It is of course far easier to break a system than to fix it. If you go changing the ip address on a system (See my thing on reconfiguring Solaris) or the hostname then it is likely some applications are going to kick up a stink about it.

Here’s my Documentum and Oracle trip-me-ups for various things. This is live content that I intend to manage as time goes on.

1. DOCBASE OWNER NOT FOUND (docbase log):

Easy to fix – though I am not actually using NT. In fact, Documentum 6 does’t even appear to want to run on anything less than XP (a few tried it on W2000 and discovered it wouldn’t install). This applies in both the Unix and Windows environments. Nobody could ever tell me why this user needs to be created and I’ve heard theories but none plausable enough to publish. In this case the name Kevin is an OS user, Kevin is also the name of the docbase (Oops, need to break the habit – even if Documentum won’t), it’s a REPOSITORY.So the fix is in Windows XP to open the Control Panel and add a user. In Unix ‘useradd’ will do this or you can use some fancy gui tool. The user doesn’t need a home dir or any further config, the Content Server stops complaining in the knowledge this user exists. Couple of things: 1. Seen systems running happily without the user except for a message at the top of the log and 2. I don’t even think I’ve set a password for this user in the past either. So.. answers on a postcard please.

If you go mucking about with host names then you need to plough through a number of files to make the content server run again…

2. server.ini

Usually found in $DOCUMENTUM/dba/config/<repository name>/server.ini
If you are on Windows you can use the Windows Server manager to locate it easily. the above unix path gives you a clue for the Windows environment.

If you renamed a system or removed it from the domain, the least you will have to do is change the docbroker projection target:

[DOCBROKER_PROJECTION_TARGET]
host = yoyo
port = 1489

Check the hostname is at least ping-able from the DOS prompt or shell. If it aint then fix it. I’m not going there – there are plenty of Google searches you can do to figure this out. One thing I will say is watch out for things like…

3. Firewall Warning

Norton Protection Center which has a hideously unfriendly and unintuitive UI and can be a right hinderance to a working system, blocking ports and all that, just watch out for it and turn it off if you run into problems (obviously not if you are directly connected to the the Tinterweb).

4. The Windows Registry – NASTY.

I don’t know about version 5.3 or before because I’ve not used Windows in the Documentum world since last century but I do know Documentum pumps stuff into the Windows registry. So even if you think you’ve been prudent with your files and see stuff appearing in the server log which didn’t aughta be there then you need to open regedt32.

HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\

Reveals a lot of interesting things.

I installed a Content Server and repository without reading the instructions simply because I wanted to break the install. Anyway, I decided to change the hostname and ip address then make the content server run (because that certainly broke the install). Well, I did this without editing the registry but had to go through \windows\system32\drivers\etc\hosts and update ip and hostname here as well as edit

C:\oracle\product\10.2.0\db_1\network\admin\listener.ora
C:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora

(You will have to find your own files, this is just my ‘out of the box’ personal config)

Just because you can connect to SQLPLUS and hack into the repository schema, doesn’t mean Documentum can do the same, so, you need to make sure to fix these files also.

5. dfc.properties

On your system you will find not 1 or 2 or even 3 dfc.properties files. On my system I found millions of them.

Some were in subdirs of c:\Documentum\bea9.2\domains\DctmDomain\upload\MethodServer\*…
…. and as the folderpath will tell you these have something to do with the java methodserver which, in D6, is no longer Tomcat and now a BEA thing.

There were others in my Webtop and DA deployments. anyway, keep as close an eye on these as you did with your dmcl.ini files. They are equally as important and configurable.

6. Oracle Connection Errors

Jumping back… SQLNET.log – which you will find in tnsnames.ora. If you have mucked up your connection sufficiently by tinkering around without writing stuff down then you may find this file will throw you a bone as to how to fix stuff.