Before implementing MTS, there are several questions you need to answer:
What protocols do you want to support?
How many dispatchers do you want to have?
How many shared server processes do you want Oracle to initially create whenever you start the instance?
What is the maximum number of shared server processes that you want to allow?
Do you still need to provide for some dedicated server connections?
How are you going to handle the extra memory demands of MTS?
The last item, regarding memory, can sneak up on you. When dedicated server connections are used, session-specific memory is contained in the memory area of each dedicated server process. With MTS, session-specific memory ends up in either the shared pool or the large pool (see Section 18.104.22.168 earlier in this chapter for details). When you implement MTS, you may need to increase your pool sizes to accommodate the extra demand for memory.
The question of which protocols to support doesn’t require a lot of discussion. You can decide this based on the protocols in use at your site. It’s worth pointing out that you do not need to implement MTS for every protocol that you use. If you are supporting 500 TCP/IP users and only 5 SPX users, you may find that there’s no real benefit to be gained by moving those 5 SPX users to MTS. The big gain would probably come from moving those 500 TCP/IP users to MTS.
Another thing to think about here is whether or not you are supporting Common Object Request ...