it is passed...
Without problems. Simply, often I see here that write "thanks for the help, I solved all", and decisions is not written. Here and I on same so wrote. And so it is not a pity to me, use, can to someone it is valid helps.
On server side and the client in sqlnet.ora added here these lines:
In listener.ora and tnsnames.ora did not begin to add, because it should to restart that it would not be desirable. But it was possible and so to make, therefore it was restricted to the first variant.
Andrey, nevertheless to twist such parameters for all clients, not the right decision, it can cause time delays for tasks which periodically exchange only small, short packets, for example Forms. Especially, if they work on slow lines.
Plus, by transmission of the big data from the server on the client, arises an overload of buffers TCP of the client at which are not adjusted big that leads to network waitings at such operations.
The raising selected listener on other port and adjustment special TNS Alias, only for those connections which demand it would be more adequate decision, , nevertheless.
It is unique, you will need to think over, whether dynamic registration of services on it is necessary. Normally, it it is not required, for the auxiliary purposes as a rule are used static registration, but basically it too can be adjusted.
listener, thus it is possible not to touch the main at all, and operation with it remains same, as before.
In addition, two listener, allow to restrict connections from clients, for example at creation standby if to stop the main listener.
Minus in that it is necessary to supervise