EOIO - Error

[Former Member]

Hi All,

We are testing JMS to IDOC Scenario,  getting error while testing data from RWB " Sequence already terminated".

http://host:port/MessagingSystem/monitor/sequenceStatus.jsp 

I was able to send test data earlier, i deleted one entry in sequence status monitor. So am getting this error.

Please suggest your ideas to solve this error,

Thanks,

Jeevitha N

[former_member182412 · Accepted solution]

Hi Jeevitha,

Did you terminate the sequence??

Regards,

Praveen.

[Former Member · Accepted solution]

Hi Praveen,

Yes, Mistakenly i terminated the sequence.

Now I am not able to send any message from RWB for testing..

Please help.

Thanks,

Jeevitha N

[Former Member · Accepted solution]

Hi All,

Please suggest how to solve this error.

Thanks,

Jeevitha N

[former_member182412 · Accepted solution]

Hi Jeevitha,

Check this sap note 2245118 - Sequence already terminated for EOIO, you need to manually update the table.

Cause


The EOIO sequence is already terminated.


If you check the "Sequence Status Monitor" at http://host:port/MessagingSystem/monitor/sequenceStatus.jsp, filter by status "TERMINATED",


you will get the sequence targeted for the EOIO queue.

Resolution


Please be aware that PI will not terminate any sequence by itself. Sequence termination can only be done by some user explicitly via the


trash button in Messaging System Monitoring tool: http://host:port/MessagingSystem/monitor/sequenceStatus.jsp


Since this action is irreversible(there is no option to reactivate the sequence again), you will have to update the sequence status in DB table.


Please carefully follow through the steps below. Any wrong update in the DB table can lead to inconsistencies which in turn will result in unexpected system behavior.


    Select the target sequence you found in the monitoring tool from table SAP<SID>DB.BC_MSG_SEQ_STAT, check and confirm it's indeed the one you want to reactivate.
    Update its status to "ACTIVE" by executing the following SQL statement:    


 UPDATE SAP<SID>DB.BC_MSG_SEQ_STAT SET STATUS='ACTIVE' WHERE STATUS='TERMINATED' AND SEQ_DEF = '<your target sequence>';


    Go to the monitoring tool again and use the link "Clear cluster wide sequences status cache" on top to clear the in-memory sequence status cache across server nodes.
    Try to restart the first failed message in the sequence in T-code : SXMB_MONI.
    If the message still fails with the same error, do a system restart to ensure that the cache is updated on each server node. Then do step 4 again.

Regards,

Praveen.