<?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 Hello, in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138477#M16995</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;In Wadud's case it might be the case that the result db came to a "bad" state after the machine crash when the result was opened in VTune. You can try to refinalize the result either using UI button on "Analysis target", "Analysis type"&amp;nbsp;or "Collection Log" tabs. In CL the command is the following:&lt;/P&gt;

&lt;P&gt;&amp;gt;amplxe-cl -finalize -r &amp;lt;result_path&amp;gt;&lt;/P&gt;

&lt;P&gt;Cannot comment much on Richard's case - if&amp;nbsp;one of&amp;nbsp;results to compare was not opened in another tab or in another&amp;nbsp;VTune GUI instance this is unexpected.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;BTW general comment - the result directory should have WRITE access for a user so if the collection was done under root by some reason and somebody wants to look at the result under user - they will have the same message about db is locked even if there is read access in the result folder if write permissions are not granted specially. I think we can improve the message on this.&lt;/P&gt;

&lt;P&gt;Thanks &amp;amp; Regards, Dmitry&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Mar 2018 09:04:44 GMT</pubDate>
    <dc:creator>Dmitry_P_Intel1</dc:creator>
    <dc:date>2018-03-02T09:04:44Z</dc:date>
    <item>
      <title>VTune SQLite database is locked</title>
      <link>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138475#M16993</link>
      <description>&lt;P&gt;Hi everyone, my desktop machine crashed whilst VTune was open. When I try to open an analysis after the reboot, it says:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;The path sqlite-db is locked. Suggestion: verify that you have enough permissions to access the path and make sure your result is not already in another tab or another instance of the project. &lt;/PRE&gt;

&lt;P&gt;Any help will be greatly appreciated.&lt;/P&gt;

&lt;P&gt;Wadud.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2018 14:05:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138475#M16993</guid>
      <dc:creator>Wadud_M_</dc:creator>
      <dc:date>2018-02-13T14:05:25Z</dc:date>
    </item>
    <item>
      <title>Similar issue while comparing</title>
      <link>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138476#M16994</link>
      <description>&lt;P&gt;Similar issue while comparing two runs I got the message below.&amp;nbsp; ls -Ral &amp;lt;the sqlite path&amp;gt; revealed nothing actionable. I suspect I had the result open in another tab.&lt;/P&gt;

&lt;P&gt;I closed VTune and reopened it and things seem to get better.&lt;/P&gt;

&lt;DIV&gt;&lt;SPAN style="font-size: 13.008px;"&gt;Intel VTune Amplifier 2018 cannot open the result&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;

&lt;DIV&gt;&lt;SPAN style="font-size: 13.008px;"&gt;&amp;nbsp; &amp;nbsp; Mon 26 Feb 2018 10:57:11 AM EST&amp;nbsp; The path /home/rlh/intel/amplxe/projects/genGarbage/r018ah/sqlite-db is locked. Suggestion: Verify that you have enough permissions to access the path and make sure your result is not already opened in another tab or another instance of the product.&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 26 Feb 2018 16:09:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138476#M16994</guid>
      <dc:creator>Richard_H_1</dc:creator>
      <dc:date>2018-02-26T16:09:02Z</dc:date>
    </item>
    <item>
      <title>Hello,</title>
      <link>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138477#M16995</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;In Wadud's case it might be the case that the result db came to a "bad" state after the machine crash when the result was opened in VTune. You can try to refinalize the result either using UI button on "Analysis target", "Analysis type"&amp;nbsp;or "Collection Log" tabs. In CL the command is the following:&lt;/P&gt;

&lt;P&gt;&amp;gt;amplxe-cl -finalize -r &amp;lt;result_path&amp;gt;&lt;/P&gt;

&lt;P&gt;Cannot comment much on Richard's case - if&amp;nbsp;one of&amp;nbsp;results to compare was not opened in another tab or in another&amp;nbsp;VTune GUI instance this is unexpected.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;BTW general comment - the result directory should have WRITE access for a user so if the collection was done under root by some reason and somebody wants to look at the result under user - they will have the same message about db is locked even if there is read access in the result folder if write permissions are not granted specially. I think we can improve the message on this.&lt;/P&gt;

&lt;P&gt;Thanks &amp;amp; Regards, Dmitry&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Mar 2018 09:04:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/VTune-SQLite-database-is-locked/m-p/1138477#M16995</guid>
      <dc:creator>Dmitry_P_Intel1</dc:creator>
      <dc:date>2018-03-02T09:04:44Z</dc:date>
    </item>
  </channel>
</rss>

