Hi Simon: I'm back with ORA-28575 again :(

Question

If you recall from some previous posts, you were (are) helping us with Extproc issues.
My case is bizarre. I do not have a listener.ora nor a tnsnames file on my machine - Oracle 8.1.6/linux. I think during the install - a different setup was used that bypasses these files for net9 communications. - Still a mystery. Yet, we had a BC4J app running for a while using intermedia and all was OK. Overnight - we are getting the infamous ORA-28575/06512 error again when trying to insert images into the db.
Here is our lsnrctl status response
[oracle@atechora dbs]$ lsnrctl status
LSNRCTL for Linux: Version 8.1.6.0.0 - Production on 21-APR-2001 07:13:43
(c) Copyright 1998, 1999, Oracle Corporation. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 8.1.6.0.0 - Production
Start Date 21-APR-2001 06:29:47
Uptime 0 days 0 hr. 43 min. 55 sec
Trace Level off
Security OFF
SNMP OFF
Listener Log File /usr/local/oracle/u01/product/8.1.6/network/log/listener.log
Services Summary...
atech1 has 3 service handler(s)
Question: Where do I start applying the help you've provided in other posts when I don't have these files?
Thanks,
Chris

Answer 1

Hi Chris,
Sorry for not getting back to you, I've been busy "9i'ing" it. Glad to hear you've got it resolved though.
Just to clear up some stuff and ask a question or two:
First, its not really "interMedia writes" that is the issue. Its interMedia's use of the ExtProc functionality to call out to external procedures to perform image processing. Its always possible to write interMedia data. The issue comes with image processing such as calls to ORDImage.setProperties() [which only reads image data] and ORDImage.process() [which reads, modifies and writes image data], which are handled externally using ExtProc. Note that a "standard" BC4J app, using the built-in interMedia support in 3.2, should work even if ExtProcs aren't working, because there's a try-block around the call to OrdImage.setProperties() with a catch-block that simply writes the browser-supplied MIME type to the object. Of course, if you've built your own app, then that might be different.
As for the problem; yes, unfortunately, there is a bug using the Multi-Threaded Server feature with ExtProc, in that MTS breaks ExtProcs. I believe this has been fixed in 8.1.7, and may also have been fixed in an 8.1.6 patch set.
You mention that "First, unlike all reference information I've seen on Technet, the client side of your intermedia app doesn't need to reference the extproc listener - but the server side does." I hope I haven't mislead you here. You are absolutely correct, ExtProcs are server-side functionality. If you can point me at the offending information, I'll try to see about getting it fixed.
Once again, glad to hear its working again.
Regards,
Simon
null