The Sequence {id=null} for Rule <BNRule:X> is Exhausted

(Doc ID 602783.1)

Last updated on JULY 07, 2017

Applies to:

Oracle Transportation Management - Version 4.0 to 6.2.0 [Release 4 to 6.2]
Information in this document applies to any platform.
***Checked for relevance on 27-Oct-2014***


Symptoms

-- Problem Statement:
The following error is being generated when a user tries to create a shipment.

2008-06-10 07:22:50.707 495667 Error Exception The sequence {id=null} for rule <BNRule:CLIENTX.SHIPMENT_XID.DEFAULT,SHIPMENT_XID.DEFAULT> is exhausted

at sun.reflect.GeneratedConstructorAccessor313.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at glog.util.exception.GLException.factory(GLException.java:413)
at glog.util.exception.GLException.factory(GLException.java:390)
at glog.server.bngenerator.BNSequence.increment(BNSequence.java:32)
at glog.server.bngenerator.picture.BNPictureSegment$Sequence.increment(BNPictureSegment.java:221)
at glog.server.bngenerator.picture.BNPictureGenerator.perform(BNPictureGenerator.java:56)
at glog.server.bngenerator.picture.BNPictureGenerator.perform(BNPictureGenerator.java:31)
at glog.server.bngenerator.BNEngine.generateWithBNSequence(BNEngine.java:259)
at glog.server.bngenerator.BNEngine.generate(BNEngine.java:81)
at glog.server.bngenerator.BNEngine.generate(BNEngine.java:56)
at glog.ejb.shipment.ShipmentBean.newPK(ShipmentBean.java:199)
at glog.ejb.shipment.db.ShipmentBeanDB.preCreate(ShipmentBeanDB.java:256)

-- Steps To Reproduce:
Once this error has occurred it can be re-created by trying to plan any order into a shipment.


-- Business Impact:
Unable to plan any orders into shipments.

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