Shareplex, activate config, " Supplemental logging is not enabled"处理

有个测试环境，启动的时候报错：

sp_ctrl (xxxx:11111)> activate config xxxxxxx.cfg
   Supplemental logging is not enabled.
   SharePlex requires at least minimal supplemental logging to be enabled.
   Please enable supplemental logging and reactivate
sp_ctrl (xxxx:11111)>

 

处理如下：

1. shutdown (shareplex process)

2. run "ora_cleansp"

3. enable the supplemental log in database.

 

官方文档如下：

Solution SOL46293

 

Title

Supplemental logging enabled at objectlevel results in error "Supplemental logging is not enabled" whenactivating a config.

Problem Description

When activating a config, the followingerror appears:

sp_ctrl (snapblv:2300)> activate config SnapBlvToSnapStl
Supplemental logging is not enabled.
SharePlex requires at least minimal supplemental logging to be enabled.
Please enable supplemental logging and reactivate

Table level supplemental logging is enabled for the tables involved inreplication.

Cause

Supplemental logging is not enabled atdatabase level

Resolution

For certain combination of Shareplex andOracle versions you need to have at least minimum supplemental logging enabledat database level, and not at the object level. For example, if running Oracle10g on Shareplex 5.3 or up, you need to have minimum supplemental loggingenabled at database level. See Release Notes for the Shareplex version inquestion.Since supplemental logging was enabled for the objects beingreplicated (table level supplemental logging) this error occurred.

To resolve the issue, please shutdown Shareplex, clean up the existingenvironment by running ora_cleansp and then enable minimum supplemental logging(at database level) before activating the config again. See Admin Guide orRelease Notes for that Shareplex version for further details. The following isan excerpt from Admin Guide:

To turn on supplemental logging perform the following.


ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER SYSTEM SWITCH LOGFILE;

Additional Information

The following is the information ontable level supplemental logging available in Oracle's documentation.

Table Supplemental Logging
Table supplemental logging uses log groups to log supplemental information.There are two types of log groups:
A. Unconditional log groups - The before images of specified columns are loggedany time the table is updated, regardless of whether the update affected any ofthe specified columns. This is sometimes referred to as an ALWAYS log group.
B. Conditional log groups - The before images of all specified columns arelogged only if at least one of the columns in the log group is updated.

Unconditional Log Groups
To enable supplemental logging that uses unconditional log groups, use theALWAYS clause as shown in the following example:
SQL> ALTER TABLE scott.emp
2 ADD SUPPLEMENTAL LOG GROUP emp_parttime (empno, ename, deptno) ALWAYS;

This creates a log group named emp_parttime on scott.emp that consists of thecolumns empno, ename, and deptno. These columns will be logged every time anUPDATE statement is executed on scott.emp, regardless of whether or not theupdate affected them. If you wanted to have the entire row image logged anytime an update was made, you could create a log group that contained all thecolumns in the table.

Conditional Log Groups
To enable supplemental logging that uses conditional log groups, omit theALWAYS clause from your ALTER TABLE statement, as shown in the followingexample:
SQL> ALTER TABLE scott.emp
2 ADD SUPPLEMENTAL LOG GROUP emp_fulltime (empno, ename, deptno);

This creates a log group named emp_fulltime on scott.emp. Just like theprevious example, it consists of the columns empno, ename, and deptno. Butbecause the ALWAYS clause was omitted, before images of the columns will belogged only if at least one of the columns is updated.

Environment

·        Product:

Shareplex for Oracle~all

·        Attachments:

·        Client OS:

·        Server OS:

·        Database:

·        Application