does a previous version of the filename you use in the export exists? If so, the newly created export file takes some attributes of the 'old' file and the export may fail. This happened to me some time ago and it took me some time to find out why.
these are software programming errors, most likley in the Oracle code. The program counter in both cases is within P0 space, the user program space. If you have a process running the same image, you could use SDA> SHOW PROC/IMA to find out, which code is loaded at that address range.
To collect more information, in case this happens again, you could activate process dumps before running these images:
$ SET PROC/DUMP
then run the image. Or - if it's a detached process and you can influence the RUN command, add a /DUMP.
In case of an improperly handled condition, a process dump would be generated in the default directory and called imagename.DMP. You can analyze such a dump with ANAL/PROCESS.
If you've collected a process dump and have a service contract with Oracle (assuming that V7.3 is still a supported version), you could log a call. Unfortunately, process dump analysis on OpenVMS V7.1-2 process dumps is - in most cases - bound to the system, where the process dump has happenend.
Consider to obtain and install the most recent available patches for Oracle.
I like Martin's explanation. This is a relatively recent change to the C-RTL (for a ntopic talking ancient stuff like Oracle V7.3 and VMS 7.1). To inherit certian file attribute which then later may bite you, and may bite an existing program like exp.
That said, I also agree with Volker (That's a no-brainer.. he is always right about VMS thingies :-): "these are software programming errors, most likley in the Oracle code."
Specially crash #2. Check out that 'target PC' and 'param'... The HEX address actually reads "BAD". So some code (EXP? VMS?anticipated it could get in trouble there!
May we assume that the basic setup has been running succesfully for years and years, exporting (as backup?) frequently? What changed? - DB size? - Disk space? - OS upgrade/patch? - Hardware (cpus, mem, io) - Was there an ORA-006xx error reported? - Was there a .TRC file generated - Is it related to a specific TABLE/USER?
Even if nothing changed you'll need to capture a bunch of this before raising a call to Oracle. Of course they might just laugh when you mention 7.3.. and VMS :-(.
