The IBM® Records Manager engine requires your database management system to process XA transactions.
If you created a new Oracle database using the DBCA templates shipped with IBM Records Manager or DB2 Content Manager, XA has already been enabled on the new database and you do not have to enable it again. If you plan to co-locate your IBM Records Manager and DB2 Content Manager library server databases, XA must be enabled on the DB2 Content Manager library server database.
SQL Server databases require you to enable XA transactions.
>set ORACLE_SID=icmnlsdb >sqlplus "/ as sysdba" sql>create spfile from pfile sql>shutdown immediate sql>startup sql>ALTER SYSTEM SET JAVA_POOL_SIZE=120M scope=spfile; sql>ALTER SYSTEM SET SHARED_POOL_SIZE=240M scope=spfile; sql>create pfile from spfile; sql>shutdown immediate; sql>startup; sql>@C:\oracle\ora10g\javavm\install\initjvm.sql; sql>@C:\oracle\ora10g\javavm\install\initxa.sql; sql>grant select,insert,update,delete on DBA_PENDING_TRANSACTIONS to icmadmin; sql>grant select,insert,update,delete on DBA_PENDING_TRANSACTIONS to system; sql>shutdown immediate; sql>startup; sql>exit;
For SQL Server databases, XA transactions are not enabled by default when you install a new SQL Server. To enable XA transactions, install the IBM-branded DataDirect Technologies Connect JDBC driver, release 3.4. To obtain the driver, download ConnectJDBC34-JTA.zip from ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm.
Before you begin, read these two documents:
Follow these steps to install the driver on the computer where the SQL Server database server is installed: