I recently decided that I wanted to create a brand-new Documentum 6.6  environment for our companies development lab.  I decided to go all out and go  the 64-bit route.  Some of our clients are heading that way, so I figured I  would see if there were any issues.

 

The quick answer, yes.

 

That said, it wasn't anything that I couldn't get through after a bit of  research.  After searching the documentation and the forums, I broke down and  went to Powerlink.  Before I get analytical, let's talk about the issue.

Setting-Up the SQL Client

In the old days, pre-64-bit, you just had to install the client for SQL Server, configure ODBC, and you were off to the races.  Now you have to perform a few extra steps to add a tool and to help the Content Server's Server Configuration Program along.

 

  • Fully patch your SQL Server 2008.  Specifically, make sure that KB956717, Cumulative Update Package 1, is installed on your server.  You can short-circuit this just by installing Service Pack 1 which includes the fix.
  • Install the client tools for SQL Server 2008 on your Content Server as you normally would.
  • Download and install Microsoft SQL Server 2008 Command Line Utilities from  Microsoft, specifically the 32-bit version (because Content Server is still a 32-bit application).  The link provided by the Powerlink Note is for the Microsoft SQL Server 2008 Feature Pack, but you can download the install file that you need directly: X86  Package (SqlCmdLnUtils.msi) - 7234 KB.

  • Time to create the ODBC connection.  Do not use the one from "Administrative Tools" under the "Control Panel".  You need to use the 32-bit ODBC configuration tool.  That can be found here: "C:\Windows\SysWOW64\odbcad32.exe"  Your location may vary based upon your Windows installation path.
  • When creating the ODBC connection, use the "SQL Server" driver.  Do not use the new SQL Server 2008 (version 10.xxx) version that you will see.  I didn't try that one, but I've been using the other one for over a decade and it hasn't steered me wrong.

 

Support Note 107602 has some more details.  It was written for 6.5 sp2, but the solution still worked for me.

Observations

Nothing in this section will help you solve problems, but I have some things to share.  The first is that this appears to have been a failure of documentation.  I understand if the installer cannot use 64-bit components, but I shouldn't have to go to Powerlink to find the solution.  It should be easy to find in the Installation Guide and/or Release Notes.

 

Second, can we get a 64-bit compiled version of the Content Server?  That would rock and bypass this problem. Dare to dream.