Simon, why do I get an OrdImage.setProperties() exception ORA-22288

Question

Hi Simon;
I've debugged a problem with the ImageExample to the point where I'm convinced one cannot call setProperties indirectly as the example code shows. SetProperties can only be called during a load - for example imgObj.LoadFromFile
The example from OTN sample code shows a sample method:
public void setPropertiesExample(OracleConnection con)
try
int index = 0;
Statement s = con.createStatement();
OracleResultSet rs =
(OracleResultSet)s.executeQuery("select * from ordimagetab where id = 5 for update");
while(rs.next())
index = rs.getInt(1);
OrdImage imgObj = (OrdImage) rs.getCustomDatum(2, OrdImage.getFactory());
imgObj.setProperties();
System.out.println("set Properties called");
if(imgObj.checkProperties())
System.out.println("checkProperties called");
System.out.println("setProperties successful");
System.out.println("checkProperties successful");
System.out.println("successful");
else
System.out.println("checkProperties called");
System.out.println("setProperties not successful");
System.out.println("checkProperties successful");
OraclePreparedStatement stmt1 =
(OraclePreparedStatement) con.prepareCall("update ordimagetab set image = ? where id = " + index);
stmt1.setCustomDatum(1,imgObj);
stmt1.execute();
stmt1.close() ;
rs.close();
s.close();
catch(Exception e)
System.out.println("exception raised " + e);
}No matter how many times I set this example or create something similar I get this error when I do something like:
ImageExample ie = new ImageExample();
con = ie.connect();
ie.setPropertiesExample(con);
exception raised java.sql.SQLException: ORA-22288: file or LOB operation FILEOPEN failed
No such file or directory
ORA-06512: at "ORDSYS.ORDIMG_PKG", line 418
ORA-06512: at "ORDSYS.ORDIMAGE", line 25
ORA-06512: at line 2
I noticed the only way to avoid this problem is to load the image immediately prior to the setproperties call...like:
OrdImage imgObj = (OrdImage) rs.getCustomDatum(2, OrdImage.getFactory());
imgObj.loadDataFromFile("imgdemo.dat");
imgObj.setProperties();
imgObj.getDataInFile("fileexample.dat");Here I get setproperties to work, but I need to change a lot of code to load images in this form...
I am using the constructors provided and the functions you provided some time back - so I do not believe initialization is the issue here. Any ideas what might be wrong here??

Answer 1

Hi Chris,
There are a number of configuration and/or setup problems that can
cause this error. But first, it might be worth describing at a higher
level what is going on here.
By default an interMedia object can store or 'reference' data in one
of 3 ways:
- local: the data is stored locally in the BLOB, the local flag is
set to 1 to indicate this.
- FILE: the source type is set to FILE, which indicates the data is
stored in a directory of which the server is aware and to
which the user/schema has been granted access. The source
location specifies the database server directory name, which
will be upper case unless you created a mixed-case name with
the CREATE DIRECTORY command. The source name specifies the
file name, which is case sensitive on Unix platforms.
- HTTP: the source type is set to HTTP, which indicates the data is
accessed via a web server. The source location is the domain,
port and path and the source name is the item name.
If you instantiate an ORDIMAGE object using something like:
CREATE OR REPLACE DIRECTORY MY_IMAGE_DIR AS 'c:\myphotos';
INSERT INTO MY_IMAGES VALUES
( 1, ORDSYS.ORDIMAGE.INIT( 'FILE', 'MY_IMAGE_DIR', 'photo1.jpg' );then the setProperties method is going to try to open photo1.jpg in
the directory known to the database as MY_IMAGE_DIR. This can fail
with "ORA-22288: file or LOB operation FILEOPEN failed; No such file
or directory" for a number of reasons:
[list]
[*]The directory MY_IMAGE_DIR was never created using CREATE DIRECTORY
[*]The user was not granted read access to MY_IMAGE_DIR
[*]The directory c:\myphotos doesn't exist
[*]The file photo1.jpg doesn't exist in c:\myphotos
[list]
Bear in mind that, essentially, everything is happening at the server,
all the client is doing is causing the setProperties method of the
ORDIMAGE type to be invoked at the server, which reads the image file,
which must be accessible to the server. Assuming everything to be OK,
then the properties will be read from the image and stored in the
object. Of course, since BFILEs are writable, you can't operate on
this image to scale, crop or convert it, for example.
However, in your case, you're hitting one of the problems listed above.
Bear in mind, there are others. For example, although you might be able
to access an image on a shared network drive of some sort, doesn't mean
to say that the database server can do so. This is a common problem on
NT. When logged in as you, you might be able to mount a network drive
and access an image file on that drive. However, that access is being
performed with your NT credentials and access rights. The database server
doesn't have the same credentials and access rights and in all likelyhood
will NOT be able to access the same file. Of course, the same situation
can occur in Unix land with NFS.
Contrast all that with what happens when a client application calls
loadDataFromFile. In this case, the client is reading image data from
a file that is local to the client (which could easily be on a
different machine than the server) and writing that image data
directly into the database as the contents of the BLOB. Therefore,
assuming the image format is recognized, setProperties is going to
succeed because the data is in the database, not external to it.
To sum up: setProperties can be called on an image when stored as a FILE.
However, the database server has to be able to access the file and the
directory in which it is stored. The reason it works when you call
loadDataFromFile is that the data is written to the BLOB in the database,
so the database has access.
Hope that makes sense,
Simon
null