Trouble Ticket ID Out of Sequence Numbering Problem When Running on Oracle RAC Cluster Database with Multiple Nodes
(Doc ID 2862845.1)
Last updated on MAY 13, 2022
Applies to:Oracle Communications MetaSolv Solution - Version 6.3.1 and later
Information in this document applies to any platform.
Trouble Ticket ID sequence numbers are not being generated in consecutive order after implementing MetaSolv Solution to run on a Oracle RAC cluster database with multiple nodes. . The Ticket ID sequence numbers have jumps and are not in consecutive order. For example, a trouble ticket created now has a Ticket ID sequence number of '2022040400010' and a trouble ticket created 2 hour later has a Ticket ID sequence number of '2022040400005'. They were properly generated in consecutive order running with a non-RAC environment.
MetaSolv Solution running in an environment with 4 managed WebLogic servers and a Oracle RAC cluster database with 4 nodes.
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