Tuxedo calls procedure and Application Level Service Failure

Question

hello ,professors all!
My Tuxedo Service just call an procedure exists in oracle9i, i am sure that the procedure runs ok in oracle9i individually, when it was called by my tuxedo service , it is not ok by first time ,and runs out tp application level Service failure error .But strangely it is ok by second time！
who can explan it to me and show me a way to solve the difficult problem?
i spend a lot time wondering the answer!
Edited by: user9086437 on 2010-9-29 下午9:57

Answer 1

There are many possible reasons why a database procedure might fail the first time it is executed and succeed after that.
You should check the Tuxedo ULOG and Oracle database logs for any messages that may point to the problem.
If there is a LIBTUX_CAT:6205 or LIBTUX_CAT:6206 message in the userlog file then you need to add a tx_open() call to your server's tpsvrinit() or tpsvrthrinit() function.
If there is an OPENINFO string for the group where your server is running then you are using XA transaction management and should not be connecting to the database in your application code; if there is not an OPENINFO string for the group where your server is running then you need to connect to the database in your application.
If you set the environment variable
TMTRACE=*:ulog:dye
for the server where the failure is happening then Tuxedo will write a trace record of each Tuxedo call and each XA call to the ULOG file. This can be helpful in determining why the failure is happening on the first call, especially if Tuxedo is handling transaction management using XA.
I hope some of this is of help in debugging the problem.
Ed