B2B Integration

Sterling B2B Integration

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to discussions
Expand all | Collapse all

check for Sterling Integrator product got use database sequence which need to reset to avoid hitting db table sequence limit

  • 1.  check for Sterling Integrator product got use database sequence which need to reset to avoid hitting db table sequence limit

    Posted Tue February 25, 2025 02:04 AM

    Hi Team, 

    In sterling Integrator, we can observe that the size of the sequence ID is keep growing and it is not reducing and we can see the cycle is set to N (which means auto-reset is not enabled). Our Management is asking what happens if the sequence hit the maximum size limit and what action to when it nears maximum limit. 

     (To my knowledge- IBM Sterling does not automatically reset any sequence ID if it reaches maximum limit. also reset the limit will lead to data integrity issues.)

    How to avoid  the database sequence ID reaches maximum limit? below is the table. 

    SEQNAME NEXTCACHEFIRSTVALUE MAXVALUE CYCLE
    SQL200203155056670 4761 999999999. N
    SQL200203155107180 1 999999999. N
    SQL200203155107620 1 999999999. N
    SQL200203155112490 1 999999999. N
    SQL200203155114340 3641 999999999. N
    SQL200203155116730 29090401 999999999. N
    SQL200203155119090 36165861 999999999. N
    SQL200203155123680 1 999999999. N
    SQL200203155128230 1 999999999. N
    SQL200203155145520 171216861 999999999. N
    SQL200203155152310 561 999999999. N
    SQL200203155206980 41 999999999. N
    SQL200203155218240 1001 999999999. N
    SQL200203155221110 1 999999999. N
    SQL200203155224830 1 999999999. N
    SQL200203155225150 321 999999999. N
    SQL200203155229960 1 999999999. N
    SQL200203162208060 1 999999999. N
    SQL200203162208160 1 999999999. N
    SQL200203162208360 1501 999999999. N
    SQL200203162209340 1 999999999. N
    SQL200203162210080 289181 999999999. N
    SQL200203162214150 1 999999999. N
    SQL200203162214220 1 999999999. N

    I tried Purging of the Business logs, but the sequence ID size limit does not changed.. 

    Please advise- how to identify which component of Sterling Integrator is using these Sequence ID ?

    Please advise- on performance measures to avoid the sequence ID to hit the maximum limit?

    Thank you in advance



    ------------------------------
    ABUL HASAN SHADHALI
    ------------------------------


  • 2.  RE: check for Sterling Integrator product got use database sequence which need to reset to avoid hitting db table sequence limit

    Posted Wed February 26, 2025 01:50 AM

    Good day,

    Have you asked this of support?



    ------------------------------
    Sincerely,
    Clayton Snyman
    ------------------------------

    Original Message


  • 3.  RE: check for Sterling Integrator product got use database sequence which need to reset to avoid hitting db table sequence limit

    Posted Wed February 26, 2025 04:01 AM

    hi

    first, internal database is always a black box for IBM.

    Second, your support should help you on these subject, they have somes tools/knowledge for it.

    For the BP sequence ID, from memory, the value is rotating back to first values when you reach to the max limits. 

    Your purge should have purged all referenced to precedent'suses of the oldest ID by this point.

    For UID table, they intented to grow without maintenance.

    For other sequence, ask your support.

    Conclusion, your IBM support should have your answer.

    Best regard.



    ------------------------------
    Vincent Lahousse
    ------------------------------

    Original Message