Invalid Database Trigger SMS.LCP_MAPPING_OVLP Found in Location Capability Application (LCP) After Upgrading Oracle Database from Version 9 to 10 (Doc ID 1321397.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 3.1.0 to 4.3.0 [Release 3.1.0 to 4.3]
Information in this document applies to any platform.
This problem applies to:

- LCP 1.0.1
- LCP 1.0.3.6
- LCP 1.0.4.0
- LCP 1.0.4.1
- LCP 1.0.4.2
- LCP 1.0.4.3

The fix is available in LCP 1.0.4.4.

Add ***Checked for relevance on 05-Feb-2013***

Symptoms

In SMS machine, the trigger was found in INVALID status.

#su - oracle
/home/oracle$ sqlplus / as sysdba

SQL> select OBJECT_NAME,OBJECT_TYPE,STATUS from DBA_OBJECTS where OBJECT_NAME = 'LCP_MAPPING_OVLP';

OBJECT_NAME                       OBJECT_TYPE         STATUS
--------------------------------- ------------------- -------
LCP_MAPPING_OVLP                  TRIGGER             INVALID


Recompile attempt doesn't help and show compilation errors.

SQL> alter TRIGGER SMF.LCP_MAPPING_OVLP compile;

Warning: Trigger altered with compilation errors.

"show errors" indicated what might be the problem is:

SQL> show errors;
Errors for TRIGGER SMF.LCP_MAPPING_OVLP:
4/27 PLS-00216: NUMBER precision constraint must be in range (1 .. 38)
5/25 PLS-00216: NUMBER precision constraint must be in range (1 .. 38)
SQL>

 

Note:
This trigger is created only on SMS machine, not on SLC or VWS.

Changes

Upgrade to Oracle Database 10 from version 9.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms