 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Locally-managed tablespaces (LMTS) in SAP</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/locally-managed-tablespaces-lmts-in-sap/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/locally-managed-tablespaces-lmts-in-sap/</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 12:39:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: croca</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/locally-managed-tablespaces-lmts-in-sap/#comment-85280</link>
		<dc:creator>croca</dc:creator>
		<pubDate>Mon, 13 Dec 2010 19:11:33 +0000</pubDate>
		<guid isPermaLink="false">#comment-85280</guid>
		<description><![CDATA[Hello Eduardo, I&#039;ve migrated an entire SAP system from dictionary managed TS to LMT (autoallocate). It took me 3 months to do that online. I used brtools. Basically, i created new locally tablespaces for tables and indexes and moved those objects to corresponding tablespaces. The only problem was after moving CDCLS table. We don&#039;t know exactly whap happened, users reported to have missing documents. It seems SAP stores header documents in table CDCLS and detailed documents are stored in another table. We opened a ticket in SapService, they helped us to delete corrupted rows. But we lost those information. That was the only issue with online reorganization. I&#039;ve working as Oracle DBA for 20 years, i&#039;m not an SAP expert. But i can tell you that from the point of view of oracle database, LMT with lead to improve space usage in database. Hope it helps. Regards.]]></description>
		<content:encoded><![CDATA[<p>Hello Eduardo, I&#8217;ve migrated an entire SAP system from dictionary managed TS to LMT (autoallocate). It took me 3 months to do that online. I used brtools. Basically, i created new locally tablespaces for tables and indexes and moved those objects to corresponding tablespaces. The only problem was after moving CDCLS table. We don&#8217;t know exactly whap happened, users reported to have missing documents. It seems SAP stores header documents in table CDCLS and detailed documents are stored in another table. We opened a ticket in SapService, they helped us to delete corrupted rows. But we lost those information. That was the only issue with online reorganization. I&#8217;ve working as Oracle DBA for 20 years, i&#8217;m not an SAP expert. But i can tell you that from the point of view of oracle database, LMT with lead to improve space usage in database. Hope it helps. Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abhishekthota</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/locally-managed-tablespaces-lmts-in-sap/#comment-42528</link>
		<dc:creator>abhishekthota</dc:creator>
		<pubDate>Mon, 12 Sep 2005 08:17:40 +0000</pubDate>
		<guid isPermaLink="false">#comment-42528</guid>
		<description><![CDATA[Hi
 Here reorganizing means, basically it is performing exports and imports of all the tables in that particular tablespace, while performing import, if it is DMTS you will face space related issues as SAP tables are very huge in size, where as most of the space related issues can be avoid when we use LMTS. This is the major reason behind in forcing towards to LMTS. DMTS is old technology and Oracle strongly supports to go with LMTS as LMTS is having so many advantages over DMTS. 
Few of the major advantages are gaining performance because of reduced hits on System Tablespace and reduced burden on Oracle DBA s.

Regards,
Abhishek
Senior Oracle DBA  
]]></description>
		<content:encoded><![CDATA[<p>Hi<br />
 Here reorganizing means, basically it is performing exports and imports of all the tables in that particular tablespace, while performing import, if it is DMTS you will face space related issues as SAP tables are very huge in size, where as most of the space related issues can be avoid when we use LMTS. This is the major reason behind in forcing towards to LMTS. DMTS is old technology and Oracle strongly supports to go with LMTS as LMTS is having so many advantages over DMTS.<br />
Few of the major advantages are gaining performance because of reduced hits on System Tablespace and reduced burden on Oracle DBA s.</p>
<p>Regards,<br />
Abhishek<br />
Senior Oracle DBA  </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 5/8 queries in 0.015 seconds using memcached
Object Caching 283/284 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-20 13:18:53 -->