9i export issue with RBS

[thomgreen]

Thanks for the info. I read the AskTom site info on this subject and understand most of it. I am a little confused. Changes are not being applied to the db during the export. Does the consistent=y actually utilize RBS in order to assure a consistent point in time export. I do not know why it would since RBS holds the before image of actual changes.

I am going to take the advise and increase UNDO_RETENTION. Obviously if RBS is being used, which my errors indicate, than any table export greater than current setting of 900 seconds (15 minutes) would be in error. Once again, just confused as to WHY RBS is being used.

[Mr.Hanky]

Why not try consistent=n first?

[thomgreen]

My concern is that there is the possibility that data can change, if it does my export will be bad for key tables. It is not probable that my users will be on at that hour, but it is possible. I am trying to eliminate to margin for error.

If I correctly understand consistent=y that possibility exist.

[Mr.Hanky]

You are correct sir.

[thomgreen]

Would you happen to know the answer to my question about why RBS is used during export with consistent=y?

[marist89]

Consistent read. There are always changes going on.

[Mr.Hanky]

Originally posted by thomgreen
Would you happen to know the answer to my question about why RBS is used during export with consistent=y?

That is detailed in the first paragraph of my first response, which was copied from Oracle's website.

Did you get it to work?

MH

[thomgreen]

I will test it tonight when db activity is low to null. thanks.

[thomgreen]

I increased the UNDO_RETENTION parameter and I am still having the same problem. Any other suggestions? I would rather not take out the consistent=y. The export just stopped... Info from the log:

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. . exporting table AQ$_INTERNET_AGENTS 0 rows exported
. . exporting table AQ$_INTERNET_AGENT_PRIVS 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table AQ$_QUEUE_UPGRADE_TMP 4 rows exported
. . exporting table DEF$_AQCALL 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_AQERROR 0 rows exported
. . exporting table DEF$_CALLDEST 0 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_DEFAULTDEST 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_DESTINATION 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_ERROR 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_LOB 0 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_ORIGIN 0 rows exported
. . exporting table DEF$_PROPAGATOR 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_PUSHED_TRANSACTIONS 0 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table DEF$_TEMP$LOB

[Mr.Hanky]

For some reason I seem to remember having this issue in Unix. and I THINK it had to do with the EXPORT environmental variable but I do not remember.

Did you set NLS_LANG and EXPORT.