I am using Oracle Objects for Ole in an MFC application. It is
supposed to run 7-24 querying the DB for work to do.

When running, I have found that there are handles leaking. I have been
able to replicate the problem with the following stripped down code.

OStartup();
ODatabase oDb;

#define CONNECT xxxxxx
#define ID xxxxxx
#define PWD xxxxxx

while(1)
{
oDb.Open(CONNECT, ID, PWD);

oDb.Close();

Sleep(5000);
}

OShutdown();

return;

It seems that the Close function does not free 2 handles. This leads
to an increase in the number of handes by 2 for each time through the
loop.

Objects for Ole Version: 9.2.0.4

Any suggestions?
Brad

On 18 Nov 2005 09:40:17 -0800, njbrad@verizon.net wrote:

>Objects for Ole Version: 9.2.0.4
>
>Any suggestions?
>Brad


What is your pressing business need you can't use the dbms_job
mechanism for 7 x 24? You aren't stating you have a standalone client
PC hitting the database 7 x 24, do you? That would be likely very
inefficient.

--
Sybrand Bakker, Senior Oracle DBA

Sybrand Bakker wrote:
> On 18 Nov 2005 09:40:17 -0800, njbrad@verizon.net wrote:
>
> >Objects for Ole Version: 9.2.0.4
> >
> >Any suggestions?
> >Brad
>
>
> What is your pressing business need you can't use the dbms_job
> mechanism for 7 x 24? You aren't stating you have a standalone client
> PC hitting the database 7 x 24, do you? That would be likely very
> inefficient.
>
> --
> Sybrand Bakker, Senior Oracle DBA

First to reply to your questions:
I have a process that sits on a seperate server that formats and
delivers reports on a scheduled basis. The schedules are stored in
data tables. The program queries the database every minute to look for
more work to do.

Second, what I've discovered:
Each time a connection is opened in OO4O the connection information is
read from TNSNAMES.ora. If I fill in the complete information (as
found in TNSNAMES.ora) instead of a connection name, the extra handles
are not created.

It might be a bug in OO4O or in TNS, but for now I have somewhat of a
work-around.

Brad