Limitations with interMedia with ORDSYS.ORDImage.process()?

Question

Hello,
We are currently writing an Apex application that will allow our users to upload pictures to the database. We have been using interMedia to manipulate them as we want to create thumbnails etc. We have one picture that just won't scale down at all. We are using blobs to store the images on the database. We are using the command:
ORDSYS.ORDImage.process(l_thumb, 'maxscale=160 160');
and as I say most of the images are scaling but some are not. The image details is by using ORDSYS.ORDImage.getProperties:
MIME Type: image/jpeg
Width: 3292
Height: 3279
File Format: JFIF
Content Format: 24BITRGB
Compression Format: JPEG
Content Length/Size: 3634347 (bytes)
As I say when I try and do the process command it makes no difference as the thumbnail properties are the same as the original properties.
If so is there anyway around this?
Thanks,
Paul.

Answer 1

Hi there.
We are trying to do this in PL/SQL and was wondering if it did write anything to a exception table?
Here is the code that we use:
declare
l_page blob;
l_web blob;
l_thumb blob;
L_TEMP_BLOB BLOB;
TEMP_ID INTEGER;
AMOUNT INTEGER;
l_mime VARCHAR2(250);
begin
IF (:P2_FILE_NAME is not null)
THEN
SELECT blob_content a, mime_type
INTO L_TEMP_BLOB, l_mime
FROM HTMLDB_APPLICATION_FILES
WHERE NAME = :P2_FILE_NAME;
INSERT INTO PL_IMG_DATA(img_data_id, title, location, img_date, grid_ref, orig_img_loc, description, staff_number,unit_id, mime_type, file_name)
VALUES (PL_IMG_DATA_SEQ.nextval, :P2_TITLE, :P2_LOCATION, :P2_DATE, upper(:P2_GRID_REF), :P2_ORIGINAL_LOCATION, :P2_DESCRIPTION, :P2_STAFF_NUMBER, :P2_MAN_UNIT, l_mime, :P2_FILE_NAME)
RETURN img_data_id into TEMP_ID;
COMMIT;
UPDATE PL_IMG_DATA SET THUMBNAIL = EMPTY_BLOB(), WEB_IMG = EMPTY_BLOB(), PAGE_IMG = EMPTY_BLOB()
WHERE IMG_DATA_ID = TEMP_ID;
COMMIT;
SELECT THUMBNAIL, WEB_IMG, PAGE_IMG
INTO l_thumb, l_web, l_page
FROM PL_IMG_DATA
WHERE IMG_DATA_ID = TEMP_ID
FOR UPDATE;
amount := dbms_lob.getlength(L_TEMP_BLOB);
DBMS_LOB.copy(l_thumb, L_TEMP_BLOB, AMOUNT, 1, 1);
DBMS_LOB.copy(l_WEB, L_TEMP_BLOB, AMOUNT, 1, 1);
DBMS_LOB.copy(l_PAGE, L_TEMP_BLOB, AMOUNT, 1, 1);
ORDSYS.ORDImage.process(l_thumb, 'maxscale=160 160');
ORDSYS.ORDImage.process(l_web, 'maxscale=320 320');
ORDSYS.ORDImage.process(l_page, 'maxscale=640 640');
UPDATE PL_IMG_DATA SET THUMBNAIL =L_THUMB, WEB_IMG = L_WEB, PAGE_IMG = L_PAGE
WHERE IMG_DATA_ID = TEMP_ID;
COMMIT;
DELETE FROM HTMLDB_APPLICATION_FILES
WHERE NAME = :P2_FILE_NAME;
END IF;
END;
As we say it seem to work for images that are a certain size but anything that is roughly over 3,500 KB it doesn't scale it down.
We were wondering if the this is a version problem as we are currently on Oracle 9.2.0.8.0?
We did manage to scale it down when we used a TIFF but then the application didn't display it so we converted the scaled down image back to a jpeg. This seems a bit mad to do right enough,