My Oracle Support Banner

When Adding Service Providers to a Match Pay Rule I Get this Error: java.sql.SQLException: ORA-12899: value too large for column (Doc ID 946498.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 6.0
This problem can occur on any platform.

Symptoms

-- Problem Statement:

On 6.0 in Production:
When attempting to Create a Match Rule with many Service Providers, if the number of characters of the list of all the Service Providers is greater than 1024 the following error occurs:

ERROR
java.sql.SQLException: ORA-12899: value too large for column
"GLOGOWNER"."SAVED_QUERY_VALUES"."QUERY_VALUE" (actual: 1275, maximum: 1024)

-- Steps To Reproduce:

1 - Log onto an OTM 6.0 system.

2 - Navigate to: Contract and Rate Management > Service Provider Management > New.

3 - Create many service Providers, for example:

12345678910_1
12345678910_2
12345678910_3
12345678910_4
12345678910_5
12345678910_6
12345678910_7
12345678910_8
12345678910_9
12345678910_10
12345678910_11
12345678910_12
12345678910_13
12345678910_14
12345678910_15
12345678910_16

4 - Navigate to: Financials > Payment Rule Management > Match Rule > NEW

5 - Create a new Rule:
ID: 12345678910_1
Source Location Rule: Ticked
Consolidation Rule: BOTH
Shipment Refnum Qual ID: ACCOUNT_CODE

6 - Add each of the Service Providers created above to the Match Rule.

7 - Click on 'Finished'.

8 - The following Error and Stack Trace is shown:


Errors
Create Another Modify Another

Error

Create Error:

glog.webserver.update.ValidateException: insert into saved_query_values
(saved_query_gid,query_value,domain_name) values (?,?,?); [LEE.12345678910_1, true
LEE.12345678910_2 LEE.12345678910_2 ..., LEE] java.sql.SQLException: ORA-12899: value too large
for column "GLOGOWNER"."SAVED_QUERY_VALUES"."QUERY_VALUE" (actual: 1275, maximum: 1024)


Stack Trace
Create Error:
glog.webserver.update.ValidateException: insert into saved_query_values
(saved_query_gid,query_value,domain_name) values (?,?,?); [LEE.12345678910

true

LEE.12345678910_1
LEE.12345678910_2
..., LEE]
java.sql.SQLException: ORA-12899: value too large for column
"GLOGOWNER"."SAVED_QUERY_VALUES"."QUERY_VALUE" (actual: 1275, maximum: 1024)



glog.webserver.update.ValidateException: insert into saved_query_values
(saved_query_gid,query_value,domain_name) values (?,?,?); [LEE.12345678910,

true

LEE.12345678910_1
LEE.12345678910_2
..., LEE]
java.sql.SQLException: ORA-12899: value too large for column
"GLOGOWNER"."SAVED_QUERY_VALUES"."QUERY_VALUE" (actual: 1275, maximum: 1024)


at glog.server.query.matchrule.MatchRuleHandler.validate(MatchRuleHandler.java:80)
at glog.webserver.update.GenericContainerXMLUpdate.create(GenericContainerXMLUpdate.java:375)
at glog.webserver.update.GenericContainerXMLUpdate.process(GenericContainerXMLUpdate.java:82)
at glog.server.xmlupdate.XMLUpdateSessionBean.updateAndTrack(XMLUpdateSessionBean.java:244)
at
glog.server.xmlupdate.XMLUpdateSessionServerSideEJBWrapper.updateAndTrack(XMLUpdateSessionServerSide
EJBWrapper.java:344)
at
glog.server.xmlupdate.XMLUpdateSessionHome_x72wrp_EOImpl.updateAndTrack(XMLUpdateSessionHome_x72wrp_
EOImpl.java:68)
at glog.server.xmlupdate.XMLUpdateSessionHome_x72wrp_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:439)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:61)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:983)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

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
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

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