Note: That some partial rollbacks will not be able to be read released if they do not start at the beginning of the transaction and/or has mismatch error. You will need to examine the problem queue manually with qview to determine the correct course of action
1. CHECK WHETHER OR NOT POST IS SKIPPING RECORDS FOR ROLLBACK by noting the "Post state" output from the "show post detail" command in sp_ctrl
Example:
sp_ctrl (HOST:port #> show post detail
Host : HOST
Source : o.SID Queue : NAME
Operations
Target Status Posted Since Total Backlog
---------- --------------- ---------- ------------------ ----------
----------
o.SID Running 3620062 08-Oct-06 17:40:55 46767364
46512983
Last operation posted:
Redo log: 180439 Log offset: 146206560
UPDATE of "TABLE_OWNER"."TABLE_NAME" at 10/09/06 15:18:05
Post state : Skip records for rollback
Activation Id : 35
Current transaction Id : 214
ID of blocking transaction : 0
Number of open transactions : 3
Number of messages read released : 49224383
Operations posted : 3620062
Transactions posted : 505
Insert operations : 617698
Update operations : 2862740
Delete operations : 138606
Key cache hit count : 429
SQL cache hit count : 0 %
============
2. If post "skipping records for rollback, do the following:
3. Stop post
sp_ctrl (HOST:port #> stop post
NOTE: If multiple named post queue, only stop the post that is skipping records for rollback
sp_ctrl (HOST:port #> stop post queue <name>
4. Verify that the post has "stopped by user", by issuing sp_ctrl> show. I
sp_ctrl (HOST:port #> show
NOTE: If post state "Stopping" do the following:
1. sp_ctrl (HOST:port #> shutdown force
2. Restart SharePlex ( ./sp_cop &)
5. Go to the proddir/bin directory
6. Run " qview -p"
NOTE: To run "qview -p", SharePlex must be running and post stopped. Also, if multiple post queue, the program will prompt whether to open each post queue. Say "n" (NO) to the post queues without rollback transactions and say "y" (YES) to open the post queue for which post is skipping records for rollback only.
Example ONLY opening to scan NAME-3 post queue:
Queue NAME-1+P+o.SOURCE-SID-o.TARGET-SID (y/n) <n>?
Queue NAME-2+P+o.SOURCE-SID-o.TARGET-SID (y/n) <n>?
Queue NAME-3+P+o.SOURCE-SID-o.TARGET-SID (y/n) <n>? y
Current queue NAME-3+P+o.SOURCE-SID-o.TARGET-SID user +PP+host+sp_opst+o.SOURCE-SID-o.TARGET-SID
Partial rollback detected in subqueue 328
Read release partial rollback subqueue 328, seq 106871627
Full rollback detected in subqueue 240
Read release full rollback subqueue 240, seq 106871627
7. When qview -p done, restart post and monitor that performance has increased.
sp_ctrl> start post
