Well, just as an addition: the dbms_file_transfer package isn't that
helpful in my case. The documents managed in my DMS addon are related
to objects in a facility management application. Physical file
structure is a bit complex, too. Copying won't be done between always
the same source and destination folder, thus I had to rewrite
directory objects for every file copy action.
Because - and it's getting not easier - copy action is required by a
trigger based event, I cannot rewrite directory objects. Accept from
wrapping them in an autonomous transaction which I do not really want
to do. Addionally the copy method of this function seems to rely on a
very specific file size (in multiples of 256 bit or so) and errors out
when not meeting this requirement. Died.
I tried triggering a scheduled job using DBMS_SCHEDULER package, but
this again has to be called in an autonomous transaction (due to
trigger based file action). When trying out, I found that calling
neither the OS method copy nor a batch file doing the same thing can
be supplied as a job action. Instead I have to call the batch file as
a parameter for cmd.exe. But then, I cannot pass parameters to the
batch file. At least, _I_ didn't manage to pass source and destination
path to the batch file.
Obviously, I will have to store files as blob in database directly
using a special tablespace.
Thank again for your help.
Claus.
>> Stay informed about: Accessing files copied by UTL_FILE.FCOPY