Re: Database Link Resources

Why not just let the second database open more connections? Only 20 connections seems pretty small, but then of course, I don't know your application.

HTH,
Brian

Stu wrote:
>
> Hello All,
>
> We're working on a fairly complex situation here and I was hoping for
> a little outside knowlede on Database Links.
>
> We're connecting to one database using WebLogic. Within the
> application, we make a call to a stored procedure that is located
> within another database. This is done via the DBLink.
>
> What's happening is that we are running out of resources in the second
> DB.
>
> The first db (WebLogic) allows up to 130 connections, while the second
> only has the ability to allow up to 20. It seem that once the
> connection is made via the link, it is not released until the
> connection is closed to the MAIN DB. Since connection pooling is on
> there... Well, we're basically losing connectivit on the second pretty
> quickly.
>
> Weblogic, of course, says to access the DB's directly using JDBC, and
> NOT to use the link (not an option for us due to security reasons).
>
> Any other ideas out there??
>
> Thanks,
> Stu

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"