How to manually remove large rollbacks from poster ? (4320589)

When a user knows they have a large rollback sitting in the post and poster is spending time processing it.

How to intervene and remove huge rollbacks instead of waiting for poster to process them ?

There could be variety of reasons why huge rollbacks gets into replication. Some of them are :

1. Due to failed large source applications jobs.
2. User error.
3. Failed application upgrade.

There are 2 types of rollback transactions. Full and Partial Rollback transactions.

Full rollback transaction is a transaction where forward and backward operation match with no net new changes by end of transaction.

Partial Rollback transaction : Partial rollback transaction is a transaction where forward operations are higher than backward operations, which will result in net new changes by the end of transaction.

qview is an utility that is used by Quest Support when investigating or intervening with issues related to SharePlex queues.

Using qview utility users can manually intervene to remove full rollbacks.

“qview –p” is an option of qview where qview scans a transaction at the beginning of all subqueues and remove them if there are any full rollbacks.

As “qview –p” only looks at the beginning of each sub queue, it is recommend to repeat “qview –p” until you see  “qview -p did not read release any rollbacks” at the prompt.

“qview –p” is fairely safe to use as it only removes full rollbacks which doesn’t needs to be poster on target.

NOTE : qview –p doesn’t help with partial rollback transactions and partial rollback transactions are best handled by poster as it can involve complex logic and please do not use qview utility without Quest Supports recommendation and instructions.

Example :

sp_ctrl (10:8729)> qstatus

  Name:  alvsupl14 (o.ORA11GR2-o.ORA11GR2) (Post queue)

    Number of messages:        615 (Age        46 min; Size          5 mb)

    Backlog (messages):        615 (Age        43 min)

[syam@alvsupl14 config]$ qview -i

qview> sque p

Queue name:  alvsupl14+P+o.ORA11GR2-o.ORA11GR2

    Subqueue 8:   102 msgs     46:56 mins

    Subqueue 2:   69 msgs     44:11 mins

    Subqueue 7:   125 msgs     42:47 mins

    Subqueue 3:   91 msgs     10:22 mins

    Subqueue 6:   96 msgs     1:27 mins

    Subqueue 4:   66 msgs     1:18 mins

    Subqueue 5:   66 msgs     1:18 mins      

[syam@alvsupl14 config]$ qview -p

Current queue alvsupl14+P+o.ORA11GR2-o.ORA11GR2         user +PP+alvsupl14+sp_opst_mt+o.ORA11GR2-o.ORA11GR2

Read release full rollback subqueue 8, seq 432

Read release full rollback subqueue 7, seq 5648

[syam@alvsupl14 config]$ qview -p

Current queue alvsupl14+P+o.ORA11GR2-o.ORA11GR2         user +PP+alvsupl14+sp_opst_mt+o.ORA11GR2-o.ORA11GR2

qview -p did not read release any rollbacks

qview> sque p

Queue name:  alvsupl14+P+o.ORA11GR2-o.ORA11GR2

    Subqueue 8:   100 msgs     12:5 mins

    Subqueue 2:   69 msgs     46:26 mins

    Subqueue 7:   118 msgs     12:51 mins

    Subqueue 3:   91 msgs     12:37 mins

    Subqueue 6:   96 msgs     3:42 mins

    Subqueue 4:   66 msgs     3:33 mins

    Subqueue 5:   66 msgs     3:33 mins

sp_ctrl (10:8729)> qstatus

  Name:  alvsupl14 (o.ORA11GR2-o.ORA11GR2) (Post queue)

    Number of messages:        606 (Age        43 min; Size          5 mb)

    Backlog (messages):        606 (Age         9 min)