Performance Techniques For Unicode Conversion of Single
Performance Techniques For Unicode Conversion of Single
3 Application servers
2 ITS servers
450 GB DB
24,000 users
who_is_sorting.sql
column tablespace format a10;
column osuser format a10;
column machine format a10;
column bytes format 999,999,999,990
break on tablespace skip 1
compute sum of bytes on tablespace
set linesize 180
sqlactive.sql
set pagesize 60
set linesize 130
set long 1000
column sql_text format A50 word_wrapped
Export/import_monitor_cmd.properties (Migration
Monitor)
Use mounted file system - nfs vs. ftp
Saves on space and no need to enable ftp (security risk)
Use explicit export order to force large packages earlier and get
them importing (and indexing) (OrderBy=<filename>)
ExportNumJobs=16 ( on an 8-CPU system)
It’s vital to have in-depth knowledge of your files and status for
restarting specific packages/phases
Public Web:
www.sap.com
www.sdn.sap.com
Q&A
Be kind to others.
Thank You !
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.