Layout of Tablespace in Database in an SAP System


The SAP systems before 6.1 had the following tablespace layout:

SYSTEM - (Oracle Dictionary)
PSAPTEMP - (Standard tablespace for sort operations)
PSAPROLL - (Standard tablespace for rollback segments)
PSAPBTABD/I - (Standard tablespace for frequently changed data)
PSAPSTABD/I - (Standard tablespace for rarely changed data)
PSAPPOOLD/I - (Standard tablespace for SAP pool tables)
PSAPPROTD/I - (Standard tablespace for log information)
PSAPLOADD/I - (Standard tablespace for SAP loads (executables))
PSAPSOURCED/I - (Standard tablespace for SAP sources (ABAP))
PSAPDOCUD/I - (Standard tablespace for documentation tables)
PSAPCLUD/I - (Standard tablespace for SAP cluster data)
PSAPDDICD/I - (Standard tablespace for the SAP data dictionary)
PSAPUSER1D/I - (Standard tablespace for data customers)
PSAPEL<REL>D/I - (Standard tablespace for release load programs)
PSAPES<REL>D/I - (Standard tablespace for release source programs)

This layout was based on logical division of the type of data that the tables would save. Due to this layout, one could distribute them over several disks to optimize disk I/O access.

The newer SAP installation come with the following tablespace layout:

SYSTEM (tablespace for the Oracle dictionary)
SYSAUX (additional tablespace as of Oracle database 10g)
PSAPTEMP (default tablespace for database sort operations)
PSAPUNDO/PSAPROLL (default tablespace for segment undo/rollback)
PSAP<SCHEMA_ID> (default tablespace for all SAP objects of the ABAP stack)
PSAP<SCHEMA_ID>DB (default tablespace for all SAP objects of the Java stack)
PSAP<SCHEMA_ID>USR (default tablespace for all customer objects)
PSAP<SCHEMA_ID><REL> (default tablespace for release-dependent data)
PSAP<SCHEMA_ID<NAME> (Additional tablespace for example, for large tables)

The new layout lets you install MCOD systems and eases databse administration. This set up is based on the improvements made in disk management and storage systems over the years.

When you upgrade an SAP system (prior to 6.1, with classic tablespace layout) to release 6.1 or older, the layout is not changed. You can change it manually using BR Tools. Checkout SAP Notes 646681 and 541538.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more