<?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 2.2, AIX 5.3, Oracle 10g -- SMO setup in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SMO-2-2-AIX-5-3-Oracle-10g-SMO-setup/m-p/23464#M5523</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Historically, SMO required databases to be laid out in a single filesystem per volume group manner.&amp;nbsp; With SMO 3.0, this is no longer the case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest taking a look at the SMO 3.0 Best Practices Guide to start:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://media.netapp.com/documents/tr-3761.pdf" target="_blank"&gt;http://media.netapp.com/documents/tr-3761.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifically, check out the sample database volume layouts in Appendix L as well as the section on "Fast Restores" (volume snap restore - which is also a new feature supported in SMO 3.0).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SMO 3.0 for AIX requires SnapDrive for Unix 4.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Jun 2009 19:38:14 GMT</pubDate>
    <dc:creator>jessick</dc:creator>
    <dc:date>2009-06-01T19:38:14Z</dc:date>
    <item>
      <title>SMO 2.2, AIX 5.3, Oracle 10g -- SMO setup</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SMO-2-2-AIX-5-3-Oracle-10g-SMO-setup/m-p/23459#M5521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've setup my database volumes/LUNs/logical volumes/filesystems in the following manner, in an attempt to get a SMO fast restore (w/SnapRestore) to work.  Alas, I have failed.  Here is the setup:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FilerB:  /vol/db_ora_data/lun2   hdisk5           fcs0     FCP           50g (53687091200)    GOOD&lt;/P&gt;&lt;P&gt;FilerB:  /vol/db_ora_data/lun1  hdisk4           fcs1     FCP           20g (21474836480)    GOOD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My Oracle data files all sit on hdisk5, my control files, redo logs, archive logs and temp spaces all sit on hdisk4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The SMO backup successfully snaps the data on hdisk5, but gives me the following error on the hdisk4 data&amp;amp;colon;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--SMO-11034 [ERROR]: LUN "NS5200B:/vol/db_ora_data/lun1" contains partitions corresponding to "/dev/hdisk4" and "/dev/hdisk4".  Cannot use multiple partitions on the same LUN - please reconfigure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This error leads me to believe I will need distinct NetApp volumes (and thus hdisks) for EACH filesystem that holds the archive logs, redo logs, control files and temp spaces.  This would be an additional eight volumes -- which leads to eight new hdisks and eight new AIX volume groups -- which is an administrative overhead I'd prefer to not have to do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there another way?  Am I mis-interpreting this error?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gerry Thome&lt;/P&gt;&lt;P&gt;CDW Corporation&lt;/P&gt;&lt;P&gt;gerry.thome@cdw.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:31:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SMO-2-2-AIX-5-3-Oracle-10g-SMO-setup/m-p/23459#M5521</guid>
      <dc:creator>thome</dc:creator>
      <dc:date>2025-06-05T07:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: SMO 2.2, AIX 5.3, Oracle 10g -- SMO setup</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SMO-2-2-AIX-5-3-Oracle-10g-SMO-setup/m-p/23464#M5523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Historically, SMO required databases to be laid out in a single filesystem per volume group manner.&amp;nbsp; With SMO 3.0, this is no longer the case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest taking a look at the SMO 3.0 Best Practices Guide to start:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://media.netapp.com/documents/tr-3761.pdf" target="_blank"&gt;http://media.netapp.com/documents/tr-3761.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifically, check out the sample database volume layouts in Appendix L as well as the section on "Fast Restores" (volume snap restore - which is also a new feature supported in SMO 3.0).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SMO 3.0 for AIX requires SnapDrive for Unix 4.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jun 2009 19:38:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SMO-2-2-AIX-5-3-Oracle-10g-SMO-setup/m-p/23464#M5523</guid>
      <dc:creator>jessick</dc:creator>
      <dc:date>2009-06-01T19:38:14Z</dc:date>
    </item>
  </channel>
</rss>

