Insufficient free space in the database during upgrademodule General checks

Question

we are upgrading SAP R/3 Enterprise 470 110 to ECC6 on Oracle/Windows.
During PREPARE module: General checks the file CHECKS.LOG show the following information:
   #====================================================#
Requests and information for module General checks #
   #====================================================#
INFO> The following values may be preliminary because of
      free space consumption during productive operation and
      additional free space requests derived in a later stage.
      Conversions of modified tables can require additional space.
      Please use the largest free space request printed,
      which are the values at the very end of this file.
ERROR> Insufficient free space in the database as follows:
Create TABLESPACE PSAPDIMD             with 102 MB
Create TABLESPACE PSAPDIMI             with 102 MB
Create TABLESPACE PSAPODSD             with 112 MB
Create TABLESPACE PSAPODSI             with 112 MB
Create TABLESPACE PSAPFACTD            with 102 MB
Create TABLESPACE PSAPFACTI            with 102 MB
INFO> To adjust the size of your tablespaces, you may use the commands
      in file 'C:\usr\sap\put\log\ORATBSXT.LST' using the 'brspace' utility.
      Please copy the file before making changes, as it may be
      overwritten in subsequent upgrade phases.
INFO> During the upgrade, the new SAP kernel
      will be installed. All files and subdirectories
      in directory C:\usr\sap\CTD\SYS\exe\run which are not used
      in Release 700 will be removed.
      The files from "dbclient.lst" in the kernel directory are kept.
      Files and subdirectories can be protected from deletion
      if they appear in a file "protect.lst" in the same directory
      (each protected name in a separate line).
      For security reasons, directory C:\usr\sap\CTD\SYS\exe\run
      should be saved in a backup.
INFO> You already installed kernel extensions.
      Please unpack the archive(s)
      RFC.CAR
      after the upgrade has finished.
      You can find these archives on the CD "Presentation".
      Do  n o t  unpack the archives now, the software
      is only compatible with the new SAP kernel.
INFO> It is possible to upgrade the frontend software before
      you start SAPup!
   #===========================================================#
PREPARE module General checks finished with status failed #
   #===========================================================#
#====================================================
Execution of all selected PREPARE modules finished.
#====================================================
Now, we have the new tablespace layout and as says the upgrade general note: Note 819655 - Add. info.: Upgrade to SAP NW 2004s ABAP ORACLE we do not have to create tablespaces as saied in PREPARE; so I have adjusted tables DDART,    TAORA, IAORA: with the entry
DDIM     STD     Dimension Tables in BW
DFACT     STD     Facts Table in BW
DODS     STD     ODS Tables in BW
Then J have repeated the module: GENERAL CHECK but in the file CHECKS.LOG I noted always the same error.
Any HELPS?????
Edited by: Raffaele Pezone on Dec 1, 2009 4:25 PM
Edited by: Raffaele Pezone on Dec 1, 2009 4:34 PM

Answer 1

As mentioned in sap note: Note 541542 - Upgrade phase INIT_CNTRANS: Container inconsistency
we don't have standard layout:
Standard layout: TABART: TAORA-TABSPACE, IAORA-TABSPACE
SSDEF:  PSAPES<rel>D,   PSAPES<rel>I
SSEXC:  PSAPES<rel>D,   PSAPES<rel>I
SLDEF:  PSAPEL<rel>D,   PSAPEL<rel>I
SLEXC:  PSAPEL<rel>D,   PSAPEL<rel>I
APPL0:  PSAPSTABD,      PSAPSTABI
USER :  PSAPUSER1D,     PSAPUSER1I
<...>:  PSAP<.....>D,   PSAP<.....>I
but
MCOD Layout (new layout)
SSDEF:  PSAP<sid><rel>, PSAP<sid><rel>
SSEXC:  PSAP<sid><rel>, PSAP<sid><rel>
SLDEF:  PSAP<sid><rel>, PSAP<sid><rel>
SLEXC:  PSAP<sid><rel>, PSAP<sid><rel>
APPL0:  PSAP<sid>USR,   PSAP<sid>USR
USER :  PSAP<sid>USR,   PSAP<sid>USR
<...>:  PSAP<sid>, PSAP<sid>
but we don't use Multiple component in one Database. We have only one instance in one DB.
in fact we have following tablespaces:
PSAPSID   
PSAPSID620
PSAPSID700
PSAPSIDUSR
PSAPTEMP  
PSAPUNDO  
SYSAUX    
SYSTEM
I have just created PSAPSID700 as  PREPARE says.