Troubleshooting IBM InfoSphere Change Data Capture Redo Log specific issues should help address common problems before calling IBM® support and save you time. IBM provides the Service Request (SR) problem submission tool to electronically submit and manage service requests on the Web. In all cases, provide a clear description of the problem, including step by step details of the things you’ve already tried in an effort to resolve the problem
Replication will fail to start
Diagnosing the problem
Run the following command: show parameter log_parallelism;
NAME TYPE VALUE
Oracle 9i: log_parallelism integer N
Oracle 10g: _log_parallelism_max integer N
NOTE: In Oracle 10g, the above command might not return anything, meaning that the _log_parallelism_max internal parameter was not set by the database administrator. You should run the following command as sysdba since the tables require special permissions.
select x.ksppinm name, y.ksppstvl value from x$ksppi x , x$ksppcv y where x.indx = y.indx and x.ksppinm = '_log_parallelism_max'
The result would look like this: _log_parallelism_max N
If the value of N is 1, log parallelism is disabled; and n > 1 means that is enabled
Resolving the problem
In Oracle 9i, RAC environments and Transformation Server for Oracle versions prior to 6.0 SP2, Log Parallelism must be disabled by following this procedure:
- 1)Shutdown the database instance.
- 2)Run the following command to disable log parallelism:
SQL> alter system set log_parallelism=1 scope=spfile;
SQL> alter system set "_log_parallelism_max"=1 scope=spfile;
- 3)Restart the database instance.
- 4)Check if the parameter was set correctly by running the command from diagnosing the problem.
- If this a RAC environment then run steps 1 through 4 for each database instance (node) in RAC.
Transformation Server For Oracle