ORA-06508 and the Shared Pool sizing 2005-06-29 - By Robyn
Hello everyone,
We've run into a new issue and I'm curious as to how 'normal' this might be.
We have a new/upgraded application in test. User testing was scheduled to
start yesterday but one trigger was failing. This trigger calls a procedure
owned by another user and had worked in the past. It is an 'after update'
trigger and the procedure populates a status table, but resulted in
ORA-06508 (See ORA-06508.ora-code.com): PL/SQL: could not find program unit being called.
The developers worked through all the stuff they knew to check (permissions,
full identificiation of the objects, etc) to no avail. The procedure and
trigger appeared to be valid, but compiling the trigger caused the procedure
to go invalid. Procedure could be recompiled but the trigger still didn't
work.
I searched at Metalink and found several documents referrencing this error
for various Oracle applications, while the docs specific to the database all
mentioned the same stuff that had already been tried.
The Oracle applications docs stated that the shared pool was too small and
needed to be increased. Seemed odd to me since the error mentioned not
finding a program unit, but these were the only docs that referenced
receiving just this error. In every other case, there was a related error
message was mentioned.
So, I shutdown the database, increase the shared pool by 128M (or 33%) and
the procedure worked. However a later attempt to recompile again broke the
procedure. This time the database was restarted without an increase in the
shared pool and again, the procedure worked.
We're going to test a few things later when the users get off the system,
but this seems really odd. The database is on HP-UX not WinDoze, so I should
not have to play the restart game to fix a problem. Has anyone seem a
similar problem? I am planning to open a TAR if it repeats but I can't test
again until tonight.
TIA ... Robyn
Hello everyone,<br>
<br>
We've run into a new issue and I'm curious as to how 'normal' this
might be. We have a new/upgraded application in test. User
testing was scheduled to start yesterday but one trigger was
failing. This trigger calls a procedure owned by another user and
had worked in the past. It is an 'after update' trigger and the
procedure populates a status table, but resulted in ORA-06508 (See ORA-06508.ora-code.com):
PL/SQL: could not find program unit being called.<br>
<br>
The developers worked through all the stuff they knew to check
(permissions, full identificiation of the objects, etc) to no
avail. The procedure and trigger appeared to be valid, but
compiling the trigger caused the procedure to go invalid.
Procedure could be recompiled but the trigger still didn't work. <br>
<br>
I searched at Metalink and found several documents referrencing this
error for various Oracle applications, while the docs specific to the
database all mentioned the same stuff that had already been tried.<br>
<br>
The Oracle applications docs stated that the shared pool was too small
and needed to be increased. Seemed odd to me since the error
mentioned not finding a program unit, but these were the only docs that
referenced receiving just this error. In every other case, there
was a related error message was mentioned.<br>
<br>
So, I shutdown the database, increase the shared pool by 128M (or 33%)
and the procedure worked. However a later attempt to recompile
again broke the procedure. This time the database was restarted
without an increase in the shared pool and again, the procedure worked.<br>
<br>
We're going to test a few things later when the users get off the
system, but this seems really odd. The database is on HP-UX not
WinDoze, so I should not have to play the restart game to fix a
problem. Has anyone seem a similar problem? I am planning
to open a TAR if it repeats but I can't test again until tonight.<br>
<br>
TIA ... Robyn<br>
|
|
