<?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: oracle tablespace in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860222#M821244</link>
    <description>Locally managed tablespaces are preferred.&lt;BR /&gt;&lt;BR /&gt;There are a lot of advantages in using locally managed tablespaces in the concept of space management.&lt;BR /&gt;&lt;BR /&gt;Like tablespace fragmentation,cohelesing or extent management are seen fine  in the locally maanaged tablespace.&lt;BR /&gt;&lt;BR /&gt;//*&lt;BR /&gt;&lt;BR /&gt;Improved concurrency and speed of space operations, as space allocations and deallocations predominantly modify locally managed resources (bitmaps stored in header files) rather than requiring centrally managed resources such as enqueues. &lt;BR /&gt;&lt;BR /&gt;Improved performance, because recursive operations that are sometimes required during dictionary-managed space allocation are eliminated. &lt;BR /&gt;&lt;BR /&gt;Readable standby databases are allowed, as locally managed temporary tablespaces (used for sorts, etc.) are locally managed and thus do not generate any rollback or redo. &lt;BR /&gt;&lt;BR /&gt;Simplified space allocation--when the AUTOALLOCATE clause is specified, appropriate extent size is automatically selected. &lt;BR /&gt;&lt;BR /&gt;Reduced user reliance on the data dictionary because necessary information is stored in file headers and bitmap blocks. &lt;BR /&gt;*//&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have attached a document which lists out some advantages.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Sat, 14 Dec 2002 06:11:31 GMT</pubDate>
    <dc:creator>T G Manikandan</dc:creator>
    <dc:date>2002-12-14T06:11:31Z</dc:date>
    <item>
      <title>oracle tablespace</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860217#M821239</link>
      <description>Hi,&lt;BR /&gt;I would like to see if a tablespace is data dictionary managed or locally managed. How can I do? Is better to create the data dictionary or locally managed one?&lt;BR /&gt;Thank you</description>
      <pubDate>Mon, 09 Dec 2002 15:07:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860217#M821239</guid>
      <dc:creator>HPADM</dc:creator>
      <dc:date>2002-12-09T15:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: oracle tablespace</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860218#M821240</link>
      <description>select EXTENT_MANAGEMENT from dba_tablespaces where tablespace_name = 'your_tablepsace_name';&lt;BR /&gt;&lt;BR /&gt;Oracle recommend using locally managed tablespaces at 9i.</description>
      <pubDate>Mon, 09 Dec 2002 16:11:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860218#M821240</guid>
      <dc:creator>Ian Lochray</dc:creator>
      <dc:date>2002-12-09T16:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: oracle tablespace</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860219#M821241</link>
      <description>Thank you very much Ian. &lt;BR /&gt;</description>
      <pubDate>Mon, 09 Dec 2002 16:22:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860219#M821241</guid>
      <dc:creator>HPADM</dc:creator>
      <dc:date>2002-12-09T16:22:24Z</dc:date>
    </item>
    <item>
      <title>Re: oracle tablespace</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860220#M821242</link>
      <description>In 9i "locally managed" is even the default!&lt;BR /&gt;Peter</description>
      <pubDate>Tue, 10 Dec 2002 09:07:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860220#M821242</guid>
      <dc:creator>Peter van Rijn_1</dc:creator>
      <dc:date>2002-12-10T09:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: oracle tablespace</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860221#M821243</link>
      <description>Locally managed tablespaces are preferred.&lt;BR /&gt;&lt;BR /&gt;There are a lot of advantages in using locally managed tablespaces in the concept of space management.&lt;BR /&gt;&lt;BR /&gt;Like tablespace fragmentation,cohelesing or extent management are seen fine  in the locally maanaged tablespace.&lt;BR /&gt;&lt;BR /&gt;//*&lt;BR /&gt;&lt;BR /&gt;Improved concurrency and speed of space operations, as space allocations and deallocations predominantly modify locally managed resources (bitmaps stored in header files) rather than requiring centrally managed resources such as enqueues. &lt;BR /&gt;&lt;BR /&gt;Improved performance, because recursive operations that are sometimes required during dictionary-managed space allocation are eliminated. &lt;BR /&gt;&lt;BR /&gt;Readable standby databases are allowed, as locally managed temporary tablespaces (used for sorts, etc.) are locally managed and thus do not generate any rollback or redo. &lt;BR /&gt;&lt;BR /&gt;Simplified space allocation--when the AUTOALLOCATE clause is specified, appropriate extent size is automatically selected. &lt;BR /&gt;&lt;BR /&gt;Reduced user reliance on the data dictionary because necessary information is stored in file headers and bitmap blocks. &lt;BR /&gt;*//&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have attached a document which lists out some advantages.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Sat, 14 Dec 2002 06:10:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860221#M821243</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-12-14T06:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: oracle tablespace</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860222#M821244</link>
      <description>Locally managed tablespaces are preferred.&lt;BR /&gt;&lt;BR /&gt;There are a lot of advantages in using locally managed tablespaces in the concept of space management.&lt;BR /&gt;&lt;BR /&gt;Like tablespace fragmentation,cohelesing or extent management are seen fine  in the locally maanaged tablespace.&lt;BR /&gt;&lt;BR /&gt;//*&lt;BR /&gt;&lt;BR /&gt;Improved concurrency and speed of space operations, as space allocations and deallocations predominantly modify locally managed resources (bitmaps stored in header files) rather than requiring centrally managed resources such as enqueues. &lt;BR /&gt;&lt;BR /&gt;Improved performance, because recursive operations that are sometimes required during dictionary-managed space allocation are eliminated. &lt;BR /&gt;&lt;BR /&gt;Readable standby databases are allowed, as locally managed temporary tablespaces (used for sorts, etc.) are locally managed and thus do not generate any rollback or redo. &lt;BR /&gt;&lt;BR /&gt;Simplified space allocation--when the AUTOALLOCATE clause is specified, appropriate extent size is automatically selected. &lt;BR /&gt;&lt;BR /&gt;Reduced user reliance on the data dictionary because necessary information is stored in file headers and bitmap blocks. &lt;BR /&gt;*//&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have attached a document which lists out some advantages.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Sat, 14 Dec 2002 06:11:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-tablespace/m-p/2860222#M821244</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-12-14T06:11:31Z</dc:date>
    </item>
  </channel>
</rss>

