Re: 02020: too many database links in use

From: Mark D Powell <Mark.Powell_at_eds.com>
Date: Sat, 22 Dec 2007 07:15:36 -0800 (PST)
Message-ID: <12d28d96-1851-4ce8-b2c3-f578543af39b@n20g2000hsh.googlegroups.com>

On Dec 22, 6:09 am, "Mario" <mario.jak..._at_zg.t-com.hr> wrote:
> > Some one suggested that we increase the following parameters in the
> > target database:-
>
> > mts_sessions,
> > sessions,
> > license_max_sessions
>
> > Their current values are :-
>
> > mts_sessions=550
> > sessions = 555
> > license_max_sessions = 0
>
> > Will increasing these values help and when we do this should we
> > increase any other Oracle configuration parameter also.?
>
> What about OPEN_LINKS parameter?

Besides looking at the right database parameter was your application designed to commit distributed queries? A distributed query is a transaction that takes two-phase commit resources on both ends. So a commit or rollback after a distributed select is necessary to release these resource allowing the connection to the remote db to be reused.

Why does it seem that a select over a db link requires a commit after execution?
http://www.jlcomp.demon.co.uk/faq/dblink_commit.html

HTH -- Mark D Powell -- Received on Sat Dec 22 2007 - 09:15:36 CST