<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Databricks job runs failures Py4JJavaError: An error occurred while calling o404.sql. : java.uti in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-job-runs-failures-py4jjavaerror-an-error-occurred/m-p/130002#M48667</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/176142"&gt;@vishalv4476&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;The error is likely due to a corrupted Delta transaction log or files deleted manually/outside of Delta. Check the table history and verify that no user or automated process removed data files. If issues are found, restore the table to a previous working version, also changing retention settings will not recover already deleted files.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Aug 2025 11:25:23 GMT</pubDate>
    <dc:creator>SP_6721</dc:creator>
    <dc:date>2025-08-28T11:25:23Z</dc:date>
    <item>
      <title>Databricks job runs failures Py4JJavaError: An error occurred while calling o404.sql. : java.util.No</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-job-runs-failures-py4jjavaerror-an-error-occurred/m-p/129635#M48582</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;Hi ,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;We had a successful running pipeline but it started failing since 20th august , no change were published. Can you please guide me resolve this issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;I've tried increasing&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;delta.deletedFileRetentionDuration'&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;'interval 365 days' but it didn't helped.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Error logs:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Py4JJavaError&lt;/SPAN&gt;&lt;SPAN&gt;: An error occurred while calling o404.sql. : java.util.NoSuchElementException: None.get at scala.None$.get(Option.scala:529) at scala.None$.get(Option.scala:527) at com.databricks.sql.transaction.tahoe.commands.VacuumCommand$.$anonfun$gc$16(VacuumCommand.scala:569) at com.databricks.sql.util.ThreadLocalTagger.withTag(QueryTagger.scala:62) at com.databricks.sql.util.ThreadLocalTagger.withTag$(QueryTagger.scala:59) at com.databricks.sql.util.QueryTagger$.withTag(QueryTagger.scala:159) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.$anonfun$recordFrameProfileWithDmqTag$1(DeltaLogging.scala:382) at com.databricks.spark.util.FrameProfiler$.record(FrameProfiler.scala:94) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.recordFrameProfileWithDmqTag(DeltaLogging.scala:382) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.recordFrameProfileWithDmqTag$(DeltaLogging.scala:381) at com.databricks.sql.transaction.tahoe.commands.VacuumCommand$.recordFrameProfileWithDmqTag(VacuumCommand.scala:70) at com.databricks.sql.transaction.tahoe.commands.VacuumCommand$.$anonfun$gc$2(VacuumCommand.scala:351) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.withOperationTypeTag(DeltaLogging.scala:325) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.withOperationTypeTag$(DeltaLogging.scala:312) at com.databricks.sql.transaction.tahoe.commands.VacuumCommand$.withOperationTypeTag(VacuumCommand.scala:70) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.$anonfun$recordDeltaOperationInternal$2(DeltaLogging.scala:178) at com.databricks.spark.util.FrameProfiler$.record(FrameProfiler.scala:94) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.recordFrameProfile(DeltaLogging.scala:418) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.recordFrameProfile$(DeltaLogging.scala:416) at com.databricks.sql.transaction.tahoe.commands.VacuumCommand$.recordFrameProfile(VacuumCommand.scala:70) at com.databricks.sql.transaction.tahoe.metering.DeltaLogging.$anonfun$recordDeltaOperationInternal$1(DeltaLogging.scala:177) at com.databricks.logging.UsageLogging.$anonfun$recordOperation$1(UsageLogging.scala:528) at com.databricks.logging.UsageLogging.executeThunkAndCaptureResultTags$1(UsageLogging.scala:633) at com.databricks.logging.UsageLogging.$anonfun$recordOperationWithResultTags$4(UsageLogging.scala:656) at com.databricks.logging.AttributionContextTracing.$anonfun$withAttributionContext$1(AttributionContextTracing.scala:48)&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 14:59:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-job-runs-failures-py4jjavaerror-an-error-occurred/m-p/129635#M48582</guid>
      <dc:creator>vishalv4476</dc:creator>
      <dc:date>2025-08-25T14:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks job runs failures Py4JJavaError: An error occurred while calling o404.sql. : java.uti</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-job-runs-failures-py4jjavaerror-an-error-occurred/m-p/130002#M48667</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/176142"&gt;@vishalv4476&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;The error is likely due to a corrupted Delta transaction log or files deleted manually/outside of Delta. Check the table history and verify that no user or automated process removed data files. If issues are found, restore the table to a previous working version, also changing retention settings will not recover already deleted files.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 11:25:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-job-runs-failures-py4jjavaerror-an-error-occurred/m-p/130002#M48667</guid>
      <dc:creator>SP_6721</dc:creator>
      <dc:date>2025-08-28T11:25:23Z</dc:date>
    </item>
  </channel>
</rss>

