On every wrong login to 2-tier application, lcount in user$ table in oracle is updated by 2. If I use 3-tier application using Tuxedo then lcount is increased by 2 more than it was in 2-tier.
Can anyone help me in understanding the behavior of Tuxedo with respect to updation of lcount in user$ table? How does Tuxedo processing impacts lcount of user$ table? Or do I need to check my application code, which might be guiding this behavior?
Tuxedo doesn't directly affect any database tables. In fact, Tuxedo doesn't know what a database or database table is!
What may be happening is if you are using XA transactions and you have an error in the OPENINFO string, when a Tuxedo server tries to participate in an XA transaction with the database, it makes XA calls to the database with the OPENINFO string. Those calls are done in addition to any database calls the Tuxedo server application code does. Does your application use XA transactions, i.e., do you have an OPENINFO string associated with the group of Tuxedo servers and the appropriate TMS built for the resource manager?
Oracle Tuxedo Chief Architect