ORA-12519 and Shared
Oracle MOSC shares
information regarding ORA-12519
which can occur following a change
to MTS. What has commonly
happened here is that moving from a
dedicated server to a shared server
(MTS) ORA-12519 is thrown even
though you have correctly changed al
of the necessary parameters.
ORA-12519 and listener
configuration: ORA-12519 occurs here because the
listener has not been properly set to
the default port and the PMON automatic
listener registration fails with
ORA-12519. You may also notice
with this ORA-12519 error that the RDA
LOCAL_LISTENER reads NULL.
resolve ORA-12519, register the listener
manually after the MTS change if you
still wish to use non-default ports.
ORA-12519 and "processes"
Oracle DBA Forums, there is
information referring to ORA-12519.
Here, it is pointed out that ORA-12519
can be caused by low "processes" values,
which can be resolved by increasing he
DB parameter, "parallel_max_servers".
Also, ORA-12519 can be thrown because of
DB and client versions which do not