Cleaning up after a call to OCIAttrGet

Question

In the code below, I call OCIAttrGet to get a session handle from the Service
Context handle svchp. After I am done with the session handle in sh_ptr, I think
I should do something to clean it up as it looks like something gets allocated.
That being said, I don't think I should call OCIHandleFree on it as it ultimately
points to a handle that is the responsibility of the service context.
Should I do something else to clean this up?
Here is the code:
// Set an application context via OCI calls.
// Extract the session handle into sh_ptr.
OCISession *sh_ptr = 0;
ub4 sh_size;
sword OCIAttrGetStatus = OCIAttrGet ( svchp,
OCI_HTYPE_SVCCTX,
&sh_ptr,
&sh_size,
OCI_ATTR_SESSION,
errhp );
// Should I free sh_ptr with OCIHandleFree?? Boil on this. While ultimately,
// sh_ptr points to a session handle that exists and is owned by something else,
// something is allocated to hold that pointer.
// Using the session handle, set the responsibility variable to the value
// manager.
sword err = OCIAppCtxSet((void *) sh_ptr,(void *)"CLIENTCONTEXT",(ub4) 13,
(void *)"responsibility", 14,
(void *)"manager", 7, errhp, OCI_DEFAULT);
Thanks for any advice . . .
Karl

Answer 1

Hi Karl,
You need not bother about freeing the session handle(sh_ptr) which resides inside the service context handle. Infact one should not do it since the user handle is used internally. When you do OCISessionEnd (in case of non pooled session) the service context handle will be freed up which will also result in freeing up of all the dependent handles (user handle being one of them). In case of pooled sessions the service context handle will be freed up when the session pool is destroyed.
Thanks,
Sumit