In this case, you don't have to set USE_SHARED_SOCKETS = TRUE. (is this statement correct?)
2. If the Oracle server is not on a multithreaded OS, then there is no additional requirement besides keep port 1521 open on firewall and configure firewall to only accept predefined IP addresses for the clients.
Not quite. On Unix you have the same problems as with Win OS if your database is set up in MTS mode! Also in this configuration you must fix the dispatcher's port in your init.ora to "fix" the port.
I will read the docs you send me for sure --- I feel I learn something new from this forum everyday and thanks for all your (and other people) contribution to this forum.
Maybe this question will be answered in the doc, but can I check with you that if the Oracle server is running in dedicated mode, do we still need to 'fix' the port for it? Or it will always use port 1521 even after initial handshaking?
Originally posted by elaine3839 Maybe this question will be answered in the doc, but can I check with you that if the Oracle server is running in dedicated mode, do we still need to 'fix' the port for it? Or it will always use port 1521 even after initial handshaking?
On Unix, AFAIK the conversation will remain on the same port (e.g. 1521) if database is not in the MTS mode. On NT on the other hand, regardless if the database is in MTS or dedicated mode, only the initial request will go through that port, after that the database will choose another port through which the actual database session conversation will take place.
If your database is not in MTS mode, then talking about "fixing" the port is irrelevant, as setting that permanent port in the init.ora implies MTS mode! If you wan't to fix the port you must set MTS_DISPATCHERS parameter in the init.ora, and as soon as you have that parameter set you are in MTS mode .
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?