Oracle 184.108.40.206.0 on Windows 2012 Std:
expdp '/ as sysdba' full=y directory=exp dumpfile=... logfile=... flashback_time=systimestamp
ORA-39001: invalid argument value ORA-39150: bad flashback time ORA-01841: (full) year must be between -4713 and +9999, and not be 0 ORA-01877: string is too long for internal buffer
consistent=y which AFAIK is a backwards compatible way to say the same exact thing also fails with the same errors. Removing those options completely, with no other changes, makes it work.
Still, I would like to take a consistent backup in addition to RMAN, which yes I do have configured and working. There are various workarounds suggested on the web. For example using
to_timestamp but none of them seem to be working.
My questions are:
- Is this a known bug?
- Are there any settings that could cause this behavior like system locale?
- I am using a slightly modified version of this script and I swear just yesterday it worked fine. I don't recall changing anything, today it doesn't work. Any ideas?
- Is there a reliable workaround? I am thinking of using
flashback_scninstead but that will require a separate query beforehand.
Doubling down on the weirdness here. Each day:
- 00:00-11:59 - errors as above
- 12:00-23:59 - everything works fine
I ran the script repeatedly yesterday evening using
flashback_time=systimestamp - no errors. Today 7:45am getting errors again from the same script, without modifications.