InterMedia Image Import & Shared Pool Problem

Question

Hi All
I have a SYS.ImagePkg.ImportImage stored procedure that its body described below:
(dest_nid number, filename varchar2, img_date varchar2) is
img_blob BLOB;
ctx raw(64) := null;
file_string varchar2(4) := 'file';
dir_string varchar2(8) := 'IMAGEDIR';
begin
delete from ImageTable where NID = dest_nid;
insert into ImageTable (NID, Image, ImageDate)
values (dest_nid, empty_blob(), img_date)
returning Image into img_blob;
ORDSYS.ORDImage.importFrom(ctx, img_blob,
file_string, dir_string, filename);
update ImageTable set image=img_blob where
NID=dest_nid;
commit;
end;
this stored procedure inserts an image into database. Also we have a VB
application that includes this code:
Set prm1 = cmd.CreateParameter("dest_nid", adNumeric, adParamInput)
Set prm2 = cmd.CreateParameter("filename", adVarChar, adParamInput, 14)
Set prm3 = cmd.CreateParameter("img_date", adVarChar, adParamInput, 8)
'-- Append parameters to command object
cmd.Parameters.Append prm1
cmd.Parameters.Append prm2
cmd.Parameters.Append prm3
For Each tFil In fld.Files
temp = Mid(fld.Path + "\", 7)
temp = RemoveCharacters(temp, "\")
nid = temp
crDate = Format(tFil.DateLastModified, "yyyy/MM/DD")
crDate = RemoveCharacters(crDate, "/")
cmd.CommandText = " call sys.ImagePkg.ImportImage(?, ?, ?) "
'-- Assign Parameter Values
cmd(0).Value = Val(nid)
cmd(1).Value = nid + ".jpg"
cmd(2).Value = crDate
cmd.Execute
Next
Automatic Shared Memory Management is Enabled and Shared pool size is 400M at startup. Also library cache size is 4M. But when we start application run, Insertion rate decreses from 45000 records per hour to 14000 records per hour after 44 hours and library cache size increases to 116M.
If continue running of application, approximatly after 5 days I recieve below error:
ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool","select /*+ rule */ bucket, e...","Typecheck heap","kgghteInit")
and application can not insert any record.
Please help me to solve this problem.

Answer 1

Also, I would like to pitch the use of the image type rather than use of a database blob.
The media types, such as ORDImage, are native server datatypes. These
datatypes allows the database, and media aware tools and applications to
understand that a column or table contains media. This is similar to the
way that the DATE datatype allows the understanding that a column contains
a date.
The media types include the most common meta-data, such as mimetype, that is
needed by media applications. Without this meta-data, an application must
decide where and how this meta-data is to be stored and retreived. Perhaps extra
columns or tables in the database, or an application header in the binary data.
It is possible to store media in simple BLOBs, but by doing this, we take the
understanding of what is in the database out of the database, and put it into
the your application realm. Media aware applications and tools, existing
and future, will not be able to work easily with the media. Only your
application, or a new application you write specifically without the
advantage of media aware programming wizards, will be able to work well with
your media.
Storing media data into a BLOB is like storing a date in a text column, you
lose the intrinsic knowlege of what the column represents with the adverse
effect of media aware applications, tools and wizards not being able to work
effectively with the column, if at all.