Issue Converting Nonpartitioned Classes to Partitioned Classes (Doc ID 2795760.1)

Last updated on MAY 15, 2024

Applies to:

Symptoms

An user is working to upgrade Billing and Revenue Management (BRM) 7.5 to 12.3 using Oracle Golden Gate (OGG) to replicate the database (DB) objects from (7.5 + 12C) to (12.3 + 19c).

Currently, the server database has the initial load made by Oracle® GoldenGate (OGG) process to copy all the data from original production database server to “production_like” new server, i.e. the user has executed the upgrade procedure in “production_like” server to BRM 7.5 database copy, no errors reported during upgrade process.

Now, the user is creating the partitions to BRM 12.3 database by using partition_utils.pl as mentioned in below doc:
https://docs.oracle.com/cd/E16754_01/doc.75/e16719/adm_nonpart_to_part.htm#BRMSA974

But the partitioning was not successful, only /bill table was partitioned.

ERROR in the partition_utils.log:
-----------------------
SQL> INFO: Procedure add_partitions_init
PINPARTITION_ERROR_NO -20001
ORA-20001: Partitioning is not enabled for the given class
BEGIN PIN_PARTITION.add_partitions_init('<HOSTNAME>','pin', 'pin','/item','07012021',0,0,1,12,2,TRUE,TRUE,FALSE,1623799538); END; *
ERROR at line 1:
ORA-20001: Partitioning is not enabled for the given class
ORA-06512: at "PIN.PIN_PARTITION", line 1869
ORA-06512: at "PIN.PIN_PARTITION", line 85
ORA-06512: at "PIN.PIN_PARTITION", line 1709
ORA-06512: at line 1

Changes

As per BRM architecture, the relationship between database tables doesn't exist, this relationship is handled by the application. OGG requires a "key" to find the DB registers to be replicated. In this case, the way to inform the key to find the records is defining the supplemental log parameter into the tables.

The user is using poid_id0+rec_id as supplemental log key. Supplemental log parameter is created by OGG to perform above mentioned tasks. After this process, trandata was created from OGG side in order to let it know the table have supplemental log as below:

GGSCI> add trandata <custom_PIN>.*;
GGSCI> add trandata Prodi_pinprod01.*;

This is the overall process why the supplemental log is added.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.