Home » Windows

Category Archives: Windows

Oracle 11g Extended Statistics for SAP Tables

Extended Statistics is an attempt to fix one of the flaws in CBO–values of different columns are not correlated.

Let us take an example of two columns in a table. One of the column contain department code and the other contains employee name. Let us assume that there are 10 departments and 3000 employees in our example. In a real life scenario, all the employees do not belong to all the departments, but CBO assumes that is the case and hence it assumes that there are 3000*10 = 30000 combinations of employee name and department code that exist. In reality, it can be between 3000 and 30000 (assuming employee belongs to at least one department and can clock for multiple departments).

DB2 Optimized for SAP – Set it and forget it

You may have read that the last release of DB2 (8.2.2) was specifically Optimized for SAP. What exactly does that mean? Well in this and the next few postings I’ll describe exactly what new features were in 8.2.2 and how, if you are using SAP (and even if you are not), you can take advantage of these new features.

The first is what I like to call the One SAP Knob.
If you administer an SAP database then you likely know that there are a number of settings SAP strongly recommends that you set. This is not a big issue when you initially get started but as new versions of DB2 and/or SAP come out it can be a burden to read through all the release notes to find out what new registry variables should be set and/or what changes to existing registry variables should be made. Well if you are on 8.2.2 your life has just gotten easier. You can turn the SAP Knob to the ON position and forget about it. What do I mean? Well there is a new registry variable in DB2 8.2.2 called DB2_WORKLOAD. If you run


this will automatically set a number of registry variables based on what IBM and SAP have determined to be the optimal settings. Think of this as a parent setting which takes care of all the children registry variables underneath it. If a future fixpack of DB2 or release of SAP has new or more optimal (if that’s even correct grammar) registry settings, DB2 will automatically adjust them as long as the DB2_WORKLOAD setting is set to SAP. If you want to see what registry variables are controlled by the DB2_WORKLOAD variable, you can run

db2set -gd DB2_WORKLOAD=SAP

and you will see a list of 17 registry variables and their settings, specifically designed in cooperation with SAP to tune DB2 optimally for an SAP workload.

How to do remote client copy ( SCC8 ) & How to do client transport( SCC9 )

Hope the below information helps.
HOW to do remote client copy ( SCC8 )
1. create the new client in the target system via tcode SCC4
2. log on to the traget client of the traget system with the user SAP* and password PASS
3. for the planned copy run, you must define the RFC connection between the R3 systems as the source client, if this has not already been
4. you should also protect the source client of the source system against changes during the copy. To do this, log on to the source system and
lock the source client : In scc4 (
change mode ), choose the option ” Currently locked Due to client Copy ”
5. you can start the copy in the target system. Execute tcode SCC9
6. using the profile, choose the data to be copied
7. choose the RFC connection. The source system and client are chosen automatically for the RFC connection
8. before the actual copy, test the RFC connection using the RFC system check. In addition to testing the connection, the R3 system releases
are checked.
9. start the copy in background ( in test mode )
10. check the status of the copy procedure from the target system. You can do this at any time by choosing Client Administration..tcode SCC3
11. start the copy in background ( in final mode )
12. check the status of the copy procedure…SCC3
NOTE : with a remote client copy, only the table data is moved, not the table definitions. If user-specific, client-dependent tables were created in
the source client, they are not automatically copied to the target client, and an error may be caused. It is the responsibility of the user to create
the necessary tables in the target client manually via SE11.
HOW to do client transport : ( SCC9 )
prerequisites : the source and target system must have the same R3 release. The R3 system can not checked the R3 release since there is no
connection between the
systems established.
1. create the target client in the target system via tcode SCC4
2. log on the source client in the source system with a user with transport authorization ( Not SAP* or DDIC )
3. using the client maintenance tool ( SCC4 ), lock the source client against changes
4. go to the client transport menu by choosing Tools > Administration > Administration > Client Transport > Client Export or transaction SCC9.
When you confirm your
selection, you are notified of which transport requests were created for this task.
KO – Client-independent
KT – client-dependent
KX – texts
5. check the logs created for the copy run via SCC3
To import the transports created into another R3 system :
1. copy the required files to the corresponding subdirectory of the local transport directory of the target system
2. on the operating system level, from the subdirectory bin of the local transport directory of the target system, execute the commands :
tp addtobuffer <request> <target system> client=<client>
tp import <request> <target system> client=<client>
3. the remaining file with the text elements requires different procedure. Log on to the target client of the target system and access the client
administration tool by selecting
Tools > Administration > Client Administration > Client Admin. Choose client Transport > Post-process Import. Select the request
<SID>KT<number of the request> and
execute it online or in background. This procedure copies and generates the client-dependent text elements.

New SAPGUI 7.30 for Windows has been released !!

SAP GUI for Windows 7.30 is the successor to SAP GUI for Windows 7.20 which will be out of of support as of 9th of April 2013. With the new release SAP GUI for Windows was carefully improved to provide the end-user with an interface where information is presented in a logical and easy-to-understand way. Several visual and usability improvements have been implemented to help users organize and complete their daily work quickly and efficiently.


The new SAP GUI for Windows 7.30 was shipped on 26th of June 2012 and introduces the following useful enhancements:

  • Corbu Design: A new SAP GUI design is available: The Corbu Design. This design comes with a reduced contrast when compared to SAP Signature Design and improves the integration of SAP GUI into other SAP components like NWBC which also offer Corbu Designs.
  • Signature Color Themes: New color themes can be applied system and client specific: Users are enabled to easily select different Signature color themes for test, development or productive systems and clients etc. This leads to a clear overview over the system landscape.
  • Branding Area: A company specific logo (corporate branding, product branding) can be embedded into the top right corner of the SAP screen. This new branding area will help administrators to generate additional corporate communication and corporate identity. It can be used in SAP Signature Design and in Corbu Design.
  • Floating Docking Containers: Docking containers can be positioned individually by end users. Dragging the container with the mouse to north, west, east or south positions helps adjusting the screen layout for individual needs.
  • Personalized TAB Order: Users can define their own TAB order within SAP screens. The new TAB order allows users to jump to the next screen element of interest. Screen elements not included in the TAB order can still be accessed by mouse clicks.
  • System Comments in SAP Logon: In SAP Logon users can add system specific notes or information. This new edit area will help users to manage and comment the system landscape.
  • SNC indication icon in the status bar: A small icon in the SAP GUI status bar indicates whether the connection between SAP GUI and application server is secured (SNC is activated) or not.

An up-to-date list of new features is available in SAP note 1670678.

See below for an image explaining some of the new, exciting features of release 7.30!


Lifecycle information:

  • Delivery: 26th of June 2012 (“Productive Release” & “Default Release”)
  • End of maintenance: 15th of July 2015 (end of support for Microsoft Visual Studio 2010)
  • Please note that SAP GUI for Windows 7.20 will be out of maintenance as of 09th of April 2012 – therefore we recommend to start planning your upgrade to release 7.30 soon after the delivery of the new release.

More detailed information on the lifecycle of SAP GUI can be found in SAP note 147519.


Supported platforms:

  • Windows XP / 2003 Server
  • Windows Vista (only “Business”, “Ultimate” and “Enterprise” editions) / Windows 2008 Server
  • Windows 7 (only “Business”, “Ultimate” and “Enterprise” editions) / Windows 2008 R2 Server
  • Windows 8: Under evaluation (planned to be supported as of SAP GUI for Windows 7.30)

More detailed information on the platforms supported by SAP GUI can be found in SAP note 66971.

Various other pieces of information related to SAP GUI can be found on the SAP GUI Homepage in SAP SCN.

Download link : http://service.sap.com/swdc – Installation and Upgrades – Browse our Download Catalog – SAP Frontend Components – SAPGUI For Windows – SAPGUI For Windows 7.30 core – Installation

Screenshot :

Oracle 9i : Some of limitation on Oracle 9i

Physical Database Limits

Item Type of Limit Limit Value
Database Block Size Minimum 2048 bytes; must be a multiple of operating system physical block size
Maximum Operating system dependent; never more than 32 KB
Database Blocks Minimum in initial extent of a segment. 2 blocks
Maximum per datafile Platform dependent; typically 222-1 blocks
Controlfiles Number of control files 1 minimum; 2 or more (on separate devices) strongly recommended
Size of a control file Dependent on operating system and database creation options; maximum of 20,000 x (database block size)
Database files Maximum per tablespace Operating system dependent; usually 1022
Maximum per database 65533

May be less on some operating systems

Limited also by size of database blocks and by the DB_FILES initialization parameter for a particular instance

Database extents Maximum 4 GB, regardless of the maximum file size allowed by the operating system
Database file size Maximum Operating system dependent. Limited by maximum operating system file size; typically 222 or 4M blocks
MAXEXTENTS Default value Derived from tablespace default storage or DB_BLOCK_SIZE initialization parameter
Maximum Unlimited
Redo Log Files Maximum number of logfiles Limited by value of MAXLOGFILES parameter in the CREATE DATABASE statement

Control file can be resized to allow more entries; ultimately an operating system limit

Maximum number of logfiles per group Unlimited
Redo Log File Size Minimum size 50 KB
Maximum size Operating system limit; typically 2 GB
Tablespaces Maximum number per database 64 K

Number of tablespaces cannot exceed the number of database files, as each tablespace must include at least one file


source (http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch43.htm#287916)

Oracle 9i : Max size of datafiles

Data files are not exactly unlimited in size, so the term “Unlimited” refers to the ceiling your datafile is able to reach, and it depends on the Oracle Block Size. To find the absolute maximum file size multiply block size by 4194303. This is the actual maximum size. You may want to read the Metalink Note:112011.1.

A datafile cannot be oversized, otherwise it could get corrupted. Let’s say if your database is 8k blocks that means that one file can not exceed approximately 34GB (34,359,730,176 bytes) without having database corruption.

Sizing datafiles is a matter of manageability, it depends on your storage, the amount of space allocated in a single managed storage unit.

128G is the maximum datafile size in 10g, but considering the maximum number of datafiles a Database can have, it can make a database to potentially size 8E (exabytes = 8,388,608 T).

The maximum data file size is calculated by:
Maximum datafile size = db_block_size * maximum number of blocks

The maximum amount of data in an Oracle database is calculated by:
Maximum database size = maximum datafile size * maximum number of datafile

The maximum number of datafiles in Oracle9i and Oracle 10g Database is 65,536. However, the maximum number of blocks in a data file increase from 4,194,304 (4 million) blocks to 4,294,967,296 (4 billion) blocks.

The maximum amount of data for a 32K block size database is eight petabytes (8,192 Terabytes) in Oracle9i.

Maximum database size is 8Pb in Oracle9i & 10g (Small file Tablespaces).

Block Sz   Max Datafile Sz (Gb)   Max DB Sz (Tb)

2,048 8 512 4,096 16 1,024 8,192 32 2,048 16,384 64 4,096 32,768 128 8,192

The maximum database size is 8Eb in Oracle 10g (Big file tablespaces).

Block Sz   Max Datafile Sz (Gb)   Max DB Sz (Tb)

2,048 8,192 524,264 4,096 16,384 1,048,528 8,192 32,768 2,097,056 16,384 65,536 4,194,112 32,768 131,072 8,388,224