| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> DBMS_PIPE and the shared pool
We are having some issues here with using database pipes and having
the shared pool become fragmented. The way the code is setup is that
pipes get created every time the procedure is called and then removed after
they are done with it. Recently activity has increased in one of the areas
that these pipes are created.
We were thinking of changing the code to explicitly create the pipes but
not remove them until the user closes the application. One problem that we
foresee with this is that if a user's PC crashes this will remain in the
shared pool.
According to Oracle, pipes created in this method will remain there until
database is shutdown. It looks like even flushing the shared pool will not
help.
Does anyone have some guidelines based on past issues with using the DBMS_PIPE stuff that we could use to help us out? Changing to external procs is not really on option at the moment although its planned for later on.
 |
 |