Forum Discussion

MarcS's avatar
MarcS
Occasional Contributor
3 years ago
Solved

ADO: Connection to the database still exists, after calling connection.close (Oracle)

If I execute the following code snipped, the user for the ADO connection is still connected to the database in the background. I'm not able to delete the database scheme for this user, after closing ...
Desktop Testing
Script Tests
  • MarcS's avatar
    MarcS
    3 years ago

    Hi Alex,

    thank you for your reply.

    The hint with the garbage collection would fit with the following, which I've found out in the meantime.

    After a 2 minute wait, the connection is terminated. But the variable is only defined within the function.

     

    I was able to solve my problem first by using the user SYSTEM. This way I have no connection to the schema, which I first query and then possibly delete.

     

    It would be interesting to see what happens, If I could call the "collect function" of the garbage collection from TestComplete

     

    Regards MarcS

     

AlexKaras's avatar
AlexKaras
Champion Level 3

Hi,

 

The only idea that I have at the moment is that QryConnection variable is a public one (or was copied to a public one) and thus was not garbage collected which keeps connection on the database side to be not disposed of.

 

MarcS's avatar
MarcS
Occasional Contributor
3 years ago

Hi Alex,

thank you for your reply.

The hint with the garbage collection would fit with the following, which I've found out in the meantime.

After a 2 minute wait, the connection is terminated. But the variable is only defined within the function.

 

I was able to solve my problem first by using the user SYSTEM. This way I have no connection to the schema, which I first query and then possibly delete.

 

It would be interesting to see what happens, If I could call the "collect function" of the garbage collection from TestComplete

 

Regards MarcS

 

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    3 years ago

    Hi,

     

    Might it be that this is something in Oracle (or how TNS is configured) itself that keeps its internal connection object in a pool for this 2 minutes timeout? Can you check this idea with your Oracle administrators?

     

    • MarcS's avatar
      MarcS
      Occasional Contributor
      3 years ago

      Hi Alex, 

      when I connect to this user with a database tool and then close the connection, then it works correctly. So I assume it has nothing to do with the Oracle configuration, otherwise I would expect the same behavior with these tools. Maybe it has to do with ADO or TestComplete

       

      At the moment I have a good workaround, connecting with the system user.

      But thanks anyway for your support.

       

      Regards MarcS