Re: conventional path export with direct=y

I've noticed another clue.

The schema is loaded with several imports (after being freshly created with some objects loaded necessary for the application). The first import is a table import getting its data from a schema export of another schema. Subsequent tables are imported from table level imports created with the query option. Any missed objects are added from a full=y rows=n export (I'm not sure that that even does anything), and views and triggers are dropped and recreated.. As part of the load process most every table has its primary key updated, and the whole schema is analysed (so I don't think this is a delayed-block-cleanout issue, which of course would be really scary in dictionary tables).

The tables exported by the misbehaving direct schema export exactly match those of the first import.

The live load has successfully completed, and I did a direct mode schema export with no problems from the command line. Tonight, the script will run and tomorrow I'll know if there is still a problem. I did notice one privilege issue - the script runs under root, and root is in the dba group. I suggested changing that 5+ years and two generations of hardware ago [siiiiigggghhhh].

jg

--
@home.com is bogus.
"Hookers?  Tomorrow?  I thought we were doing the Guggenheim." -
Michael Crawford