My Oracle Support Banner

Extending Capacity Limit Date Fails For Daily Capacity Records (Doc ID 747873.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Transportation Management - Version 5.5.05 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

OTM errors out when trying to extend expiration dates on capacity limit records setup with daily capacity.

In CU5 new functionality is delivered that allows to extend the expiration date on capacity limit records. This is supposed to work either by using the recurring capacity option or by using the daily capacity option.

It is only possible to extend the expiration dates on capacity limit records that are setup with recurring capacity. If the expiration date on capacity limit records is setup with daily capacity, OTM errors out when trying to extend the expiration dates. An error similar to this is thrown:

<DATE TIME> <VALUE> Error Exception Cannot insert the CAPACITY_USAGE record. LIMIT
must be set.
java.sql.SQLException: ORA-01400: cannot insert NULL into ("GLOGOWNER"."CAPACITY_USAGE"."LIMIT")

java.sql.SQLException: ORA-01400: cannot insert NULL into ("GLOGOWNER"."CAPACITY_USAGE"."LIMIT")

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:486)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:993)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3423)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:147)
at glog.util.jdbc.SqlUpdate.executeUpdate(SqlUpdate.java:133)
at glog.util.jdbc.SqlUpdate.resetArguments(SqlUpdate.java:111)
at glog.util.jdbc.SqlUpdate.execute(SqlUpdate.java:60)
at glog.util.remote.BeanManagedEntityBean.executeUpdate(BeanManagedEntityBean.java:793)
at glog.util.remote.BeanManagedEntityBean$1.execute(BeanManagedEntityBean.java:195)
at glog.util.remote.BeanManagedEntityBean.dbModify(BeanManagedEntityBean.java:1066)
at glog.util.remote.BeanManagedEntityBean.doCreate(BeanManagedEntityBean.java:191)
at glog.util.remote.BaseEntityBean$1.doIt(BaseEntityBean.java:455)
at glog.util.remote.BaseEntityBean.ejb(BaseEntityBean.java:798)
at glog.util.remote.BaseEntityBean.ejbCreator(BaseEntityBean.java:453)
at glog.ejb.capacity.db.CapacityUsageBeanDB.ejbCreate(CapacityUsageBeanDB.java:61)
at
glog.ejb.capacity.ejb_CapacityUsage_l50t1q_Impl.ejbCreate(ejb_CapacityUsage_l50t1q_Impl.java:235)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.O
bject;(Unknown Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at weblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.java:750)
at weblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityManager.java:721)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:249)
at
glog.ejb.capacity.ejb_CapacityUsage_l50t1q_HomeImpl.create(ejb_CapacityUsage_l50t1q_HomeImpl.java:12
3)
at
glog.business.capacity.CapacityUpdateSessionBean.expireCapacityLimitManually(CapacityUpdateSessionBe
an.java:107)
at
glog.business.capacity.CapacityUpdateSessionServerSideEJBWrapper.expireCapacityLimitManually(Capacit
yUpdateSessionServerSideEJBWrapper.java:72)
at
glog.business.capacity.CapacityUpdateSessionHome_64dyz3_EOImpl.expireCapacityLimitManually(CapacityU
pdateSessionHome_64dyz3_EOImpl.java:208)
at
glog.business.action.CapacityActionExecutor.expireCapacityLimitManually(CapacityActionExecutor.java:
410)
at
glog.business.action.CapacityActionExecutor.expireCapacityLimitsManually(CapacityActionExecutor.java
:308)
[ExecuteThread: '35' for q]

 

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


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