<?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: SMO 3.1 - clone of read-only tablespaces in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SMO-3-1-clone-of-read-only-tablespaces/m-p/19174#M8682</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SMO3.1 doesn't support cloning of databases that contain read-only tablespaces.&lt;/P&gt;&lt;P&gt;There exists no workaround for this as of now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clone cannot be created if any of the tablespace is read-only.&lt;/P&gt;&lt;P&gt;If you still want to clone the db, you should make the tablespace as read-write, now take a backup and then clone it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Kanthan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Apr 2011 05:05:55 GMT</pubDate>
    <dc:creator>kanthan</dc:creator>
    <dc:date>2011-04-19T05:05:55Z</dc:date>
    <item>
      <title>SMO 3.1 - clone of read-only tablespaces</title>
      <link>https://community.netapp.com/t5/Data-Protection/SMO-3-1-clone-of-read-only-tablespaces/m-p/19169#M8681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;DIV id="_mcePaste"&gt;we want to use SMO 3.1 for cloning our read-only tablespaces.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;In the release notes of 3.1 there is one note:&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Note 5092: SnapManager for Oracle does not support the cloning of databases that contain read-only tablespaces. &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt; &lt;/DIV&gt;&lt;DIV&gt;Is there any workaround?&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt; &lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt; &lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Sebastian&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:56:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SMO-3-1-clone-of-read-only-tablespaces/m-p/19169#M8681</guid>
      <dc:creator>sfrechen</dc:creator>
      <dc:date>2025-06-05T06:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: SMO 3.1 - clone of read-only tablespaces</title>
      <link>https://community.netapp.com/t5/Data-Protection/SMO-3-1-clone-of-read-only-tablespaces/m-p/19174#M8682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SMO3.1 doesn't support cloning of databases that contain read-only tablespaces.&lt;/P&gt;&lt;P&gt;There exists no workaround for this as of now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clone cannot be created if any of the tablespace is read-only.&lt;/P&gt;&lt;P&gt;If you still want to clone the db, you should make the tablespace as read-write, now take a backup and then clone it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Kanthan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Apr 2011 05:05:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SMO-3-1-clone-of-read-only-tablespaces/m-p/19174#M8682</guid>
      <dc:creator>kanthan</dc:creator>
      <dc:date>2011-04-19T05:05:55Z</dc:date>
    </item>
  </channel>
</rss>

