My Oracle Support Banner

OSM Upgrade From 7.2.2.3.13 To 7.2.2.6.0 Failed With ORA-04013 (Doc ID 2080380.1)

Last updated on MAY 28, 2018

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 to 7.2.2 [Release 7.2]
Information in this document applies to any platform.

Symptoms

When upgrading OSM from version 7.2.2.3.13 to 7.2.2.6.0 the following error appears : DbManagerException: ORA-04013: number to CACHE must be less than one cycle ORA-06512: at line 14.
The issue is getting replicated only when the maximum of coord_set_id is greater than 1000000000 in om_order_flow_coordinator and inom_coord_node_instance tables in OSM database. This is an Active-Active RAC Oracle database with Partitioning ON but "auto_creation_partition" is disabled.

STEPS TO REPLICATE

1. Take OSM version  7.2.2.3.13

2. Make sure the OSM database schema has a maximum of coord_set_id greater than 1.000.000.000 in om_order_flow_coordinatorand in om_coord_node_instance. For example: max(coord_set_id) in om_order_flow_coordinator and in om_coord_node_instance is the same, let's say: 1000556338 .

3. Notice that last_number in om_order_flow_coordina_seq is 2002 last_number in om_order_flow_coordina_seq1 is greater than 1.000.000.000.

4. Upgrading from OSM 7.2.2.3.13 to OSM 7.2.2.6.0 requires to first run the following SQL statements on the OSM database schema:update om_$install$version set same_as = '7.2.0.10.21' where object_name ='om_jms_event';commit;

5. Upgrade to OSM 7.2.2.6.0. The error  ORA-04013: number to CACHE must be less than one cycle appears:

BUILD FAILED
/app/OSM72260GA/Database/dbinstall/install/instplb.xml:47:
oracle.communications.ordermanagement.install.db.plan.InstallActionException:
com.mslv.install.db.util.DbManagerException: ORA-04013: number to CACHE must
be less than one cycle
ORA-06512: at line 14
sql:
              declare
              v_max_coord_set_id integer;
              v_nextval          integer;
              v_increment        integer;
              begin
                  -- find the maximum value of the current coord_set_id, then
reset the om_order_flow_coordina_seq current value

                  select om_order_flow_coordina_seq.nextval into v_nextval
from dual;
                  select nvl( max(coord_set_id),v_nextval-1) into
v_max_coord_set_id from om_coord_node_instance;

                  if v_max_coord_set_id >= v_nextval then
                      v_increment := v_max_coord_set_id - v_nextval + 1;
                      execute immediate 'alter sequence
om_order_flow_coordina_seq increment by '|| v_increment;
                      select om_order_flow_coordina_seq.nextval into
v_nextval from dual;
                      execute immediate 'alter sequence
om_order_flow_coordina_seq increment by 1';
                  end if;
              end;
          Nested Exception: ORA-04013: number to CACHE must be less than one cycle
ORA-06512: at line 14
Nested Exception: java.sql.SQLException: ORA-04013: number to CACHE must be less than one cycle
ORA-06512: at line 14

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


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