Re: SIMULATING DISTRIBUTED TRANSACTION FAILURE

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<atq756$a6m$1$8300dec7_at_news.demon.co.uk>...
> The last time I did this was in Oracle 7.
> I think I used events 10271 to 10276 - the
> last digit matches the N in the comment
> ora-2pc-crash-test-N, I think.
>
> Things may have changed since then, but
> I remember I had to kill RECO somehow
> to do this - otherwise it kicked in so fast
> that I never had time to see the side-effects
> of the 2PC failing.
>
> --
> Regards
>
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
> Coming soon a new one-day tutorial:
> Cost Based Optimisation
> (see http://www.jlcomp.demon.co.uk/tutorial.html )
>
> Next Seminar dates:
> (see http://www.jlcomp.demon.co.uk/seminar.html )
>
> ____England______January 21/23
>
> The Co-operative Oracle Users' FAQ
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>
 

> Brit Pop wrote in message
> <189eb8c37353ba33c4dd88d3ca9d902d.117233_at_mygate.mailgate.org>...
> >Hi all,
> >
> >has anybody ever simulated a distributed transaction failure?
> >
> >I would like to make some test, and in order to have the views
> >DBA_2PC_PENDING and DBA_2PC_NEIGHBORS populated, I've been
> suggested
> >to use the statement COMMIT COMMENT 'ORA-2PC-CRASH-TEST-n' , where
> >n=1,2, etc.
> >
> >However, this method doesn't seem widely documented.
> >
> >Any comment about?
> >
> >Thanks,
> >
> >BritPop
> >

If you have metalink access see Simulating a distributed transaction failure #421656.999 and Commit comment 'ORA-2PC-CRASH-TEST-n' document #365507.999

HTH -- Mark D Powell -- Received on Wed Dec 18 2002 - 16:11:02 CST