<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FLASHBACK_TIME on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/flashback_time/</link><description>Recent content in FLASHBACK_TIME on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Fri, 10 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/flashback_time/index.xml" rel="self" type="application/rss+xml"/><item><title>Run a Consistent Export with expdp FLASHBACK_TIME</title><link>https://www.oraclescripts.com/post/oracle-expdp-flashback-time-systimestamp/</link><pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/oracle-expdp-flashback-time-systimestamp/</guid><description>
&lt;h2 id="run-a-consistent-export-with-expdp-flashback_time"&gt;Run a Consistent Export with expdp FLASHBACK_TIME&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;A Data Pump export that reads one table at 02:00 and the next at 02:15 is not a consistent snapshot — it is a photograph taken in pieces over time. For schemas where rows in one table reference rows in another, that time spread means the export can capture parent rows whose child records were not yet committed, or child records whose parents were deleted during the export window. The dump file looks intact until the import runs and foreign key constraints reveal the mismatch, or an ETL pipeline reports orphaned surrogate keys.&lt;/p&gt;</description></item></channel></rss>