Table space increasees in db2

Dear team ,
we are using ecc6+db2  found the problem in db02 table spaces dms/sms table spaces are reached 95% like BTABD ,BTABI
etc tables please advice the steps how to increase the table spaces in db2.
regards
suresh

Suresh,
The following should help you. BTW is your DB not Automatic storage managed?
http://help.sap.com/saphelp_sm40/helpdata/en/3d/da4d3c9bc34800e10000000a114084/content.htm
A simple googling can always help
Regards,
Venkat

Similar Messages

  • Table space not getting cleaned after using free method (permanent delete)

    Hi ,
    We are using the free method of the LIB OBJ, to permanently delete the objects. As per documentation, the ContentGarbageCollectionAgent will be cleaning the database which runs in a scheduled mode. But the log of that ContentGargabageCollectionAsgent shows, all zero for objects without reference, objects cleared,etc. I.e the table space remains the same before and after deleteing all the contents in the cmsdk database. But the agent is running as per the schedule but just comes out doing nothing.
    Can anbody put some light on this issue.
    thanks
    Raj.

    Hi Matt,
    Thanks for replying. It's been a very long time waiting for you ;)
    ---"Are you running the 9.2.0.1, 9.2.0.2, or 9.2.0.3 version of the Database?"
    we are using 9.2.0.1
    ---"If you installed the CM SDK schema in the "users" tablespace ......."
    Yes we are using USERS tablespace for our Development.
    I ran the query. The result is:
    SYSTEM MANUAL NOT AFFECTED
    USERS MANUAL NOT AFFECTED
    CTXSYS_DATA MANUAL NOT AFFECTED
    CMSDK1_DATA MANUAL NOT AFFECTED
    (USERS belongs to develpoment cmsdk schema. And CMSDK1 for Prod CMSDK schema)
    From the results I see only "Manual", but still I don't see the tablespace size being coming down. Both table space sizes (USER and CMSDK1) always grows higher and higher.
    Also to let you know, We use ORACLE EM Console (Standalone) application to see the oracle databse information online. Will there be any thing to do with the tool we use to see the table space sizes. We make sure we always refresh it before making a note.
    So is there anything else I can see. Once I saw the ContentGarbageCollection agent to free 1025 objects and deleted 0 objects. But I don't see any change in the table space size. I am little confused b/w freed and deleted.
    thanks once again for your response Matt.
    -Raj.

  • What is difference between table space and shchema

    what is difference between table space and shchema ?

    784633 wrote:
    so each user has it own space of tables - schema ?yes, but let's clarify a bit ....
    The "schema" is the collection of all objects owned by a particular user. So if user SCOTT creates two tables, EMP and DEPT, and a view EMP_RPT, and a procedure GET_MY_EMP, those objects (tables, views, procedures) collectively make up the SCOTT schema.
    Those objects will be physically stored in a tablespace.
    A tablespace is a named collection of data files. So tablespace USERS will be made up of one or more data files. A specific datafile can belong to one and only one tablespace. If a tablespace has more than one data file, oracle will manage those files as a collection invisible to the application - much like the OS or disk subsystem handles striping across multiple physical disks.
    A specific object in the SCOTT schema can exist in only one tablespace, but not all objects of the schema have to be in the same tablespace. Likewise a tablespace can contain objects from multiple schemas.
    and can one user to access tables of other users?As others have said - FRED can access tables belonging to SCOTT as long has SCOTT has granted that access to FRED.

  • Space in bytes used by a single index in given table space

    Hi All,
    How can i find a table space used by index in bytes
    Eg:
    suppose i have a table space USERS and i have a table say customer . one index defined on table customer called CUSTOMER_UQ and mapped to table to table space USERS . How can i find the bytes used by object CUSTOMER_UQ in table space USERS.
    Thanks

    The used space in Karthik's example is the number of bytes actually used by entries in the index, not the amount of space allocated to the index itself.
    To find out how much space in disk is allocated to the index you can use (as the owner of the index) something like:
    SELECT bytes FROM user_segments
    WHERE segment_name = <index name>You could also use all_segments or dba_segments if you have access as another user, but you would also need to specify the owner name.
    John

  • Error in "Checking Availabe Space for the DB2 UDB for Unix..." phase

    Hello,
    We are in the middle of an Upgrade proyect from R/3 4.6C (kernet 4.6D EXT) to ECC 6.0.
    As a first step we are doing an Heterogenous System Copy to migrate from servers with HP-UX B11.11/Informix 9.4 to servers with AIX 5.3/DB2 UDB 8.
    We already did the database import with no errors. When we are installing R3 4.6C in the target server we are getting u201CMemory Fault (coredump)u201D error in the u201CChecking Availabe Space for the DB2 UDB for Unix, Windows Tablespacesu201D phase.
    Any advice will be appreciated.
    Best Regards
    Francisco

    Hello Paul,
    There is no db2diag.log. We are in the first steps of the installation.
    Operating System logs just shows an ABNORMALY TERMINATION OF SOTWARE error.
    This is the CEDBMIG.log
    INFO 2010-08-04 10:12:00 CommandFileController SyFileCopy:150
        Copying source file CEDBMIG.R3S to target file CEDBMIG.R3S.30 ...
    INFO 2010-08-04 10:12:01 Main
        Preparation successfully completed.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:23 CDSERVERMIG_IND_DB6 InternalColdKeyCheck:0
        The CD KERNEL will not be copied.
    INFO 2010-08-04 10:12:23 CDSERVERMIG_IND_DB6 InternalColdKeyCheck:0
        The CD RDBMS will not be copied.
    INFO 2010-08-04 10:12:23 CDSERVERMIG_IND_DB6 InternalColdKeyCheck:0
        The CD EXPORT1 will not be copied.
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyCoprocessCreate:300
        Creating coprocess /usr/sbin/lsattr -El sys0 -a realmem  ...
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyRamSizeGet:100
        The process lsattr puts out:
         realmem 8388608 Amount of usable physical memory in Kbytes False
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyRamSizeGet:700
        Physical RAM size is 8192 MB.
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:100
        Retrieving swap space size ...
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyCoprocessCreate:300
        Creating coprocess /usr/sbin/lsps -s  ...
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:150
        The process lsps puts out:
         Total Paging Space   Percent Used
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:150
        The process lsps puts out:
               8192MB               1%
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:500
        Currently activated swap space is 8192 MB.
    INFO 2010-08-04 10:12:31 CENTRDBINSTANCE_IND_DB6 InternalWarmKeyCheck:0
        The installation phase is starting now. Please look in the log
        file for further information about current actions.
    INFO 2010-08-04 10:12:31
        Requesting Installation Details
    INFO 2010-08-04 10:12:31
        Reading and Checking DB2 UDB for UNIX, Windows Specific Keys
    INFO 2010-08-04 10:12:31
        Select the DB2 Storage Management.
    INFO 2010-08-04 10:12:31
        Choose the number of storage paths for DB2's Automatic Storage
        Management.
    INFO 2010-08-04 10:12:31 CDSERVERMIG_IND_DB6 InternalWarmKeyCheck:0
        The CD KERNEL will not be copied.
    INFO 2010-08-04 10:12:31 CDSERVERMIG_IND_DB6 InternalWarmKeyCheck:0
        The CD RDBMS will not be copied.
    INFO 2010-08-04 10:12:31 CDSERVERMIG_IND_DB6 InternalWarmKeyCheck:0
        The CD EXPORT1 will not be copied.
    INFO 2010-08-04 10:12:31
        Requesting Information on CD-ROMs
    INFO 2010-08-04 10:12:31
        Calculating RAM Distribution
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Dispatcher
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Gateway Service
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Secure Gateway Service
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Message Server
    INFO 2010-08-04 10:12:31
        Creating the SAP Administration Group sapsys
    INFO 2010-08-04 10:12:32
        Creating the Database Administration Group db<dbsid>adm
    INFO 2010-08-04 10:12:32
        Creating the Group db<dbsid>ctl
    INFO 2010-08-04 10:12:32
        Creating the Group db<dbsid>mnt
    INFO 2010-08-04 10:12:32
        Creating the SAP connect user
    INFO 2010-08-04 10:12:32
        Setting Password of the SAP connect user
    INFO 2010-08-04 10:12:32
        Creating the db2<sapsid> User
    INFO 2010-08-04 10:12:32
        Setting the User Password
    INFO 2010-08-04 10:12:32
        Creating the SAP System Administrator
    INFO 2010-08-04 10:12:32
        Setting Password for for the SAP System Administrator
    INFO 2010-08-04 10:12:32
        Creating Directories
    INFO 2010-08-04 10:12:32
        Creating Symbolic Links
    INFO 2010-08-04 10:12:32
        Getting Minimal Size of the Database
    INFO 2010-08-04 10:12:32
        Changing DB2 UDB for UNIX, Windows Tablespace Data
    INFO 2010-08-04 10:12:32
        Checking if Required Directories Exist
    INFO 2010-08-04 10:12:32
        Checking Available Space for the SAP Instance
    INFO 2010-08-04 10:12:32
        Checking Available Space for the DB2 UDB for UNIX, Windows
        Tablespaces
    This is the CEDBMIG.R3S log
    120_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.CSH
    130_SOURCE=@DB_HOME@/.cshrc
    130_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.CSH
    200_SOURCE=@DB_HOME@/.profile
    200_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.SH
    210_SOURCE=@DB_HOME@/.profile
    210_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.SH
    [Z_OSUSERSIDADMENVIRONMENT_IND_DB6]
    100_GROUP=sapsys
    100_OWNER=@LOWER_SAPSYSTEMNAME@adm
    100_PERMISSION=0644
    100_SOURCE=@HOME@/.login
    100_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.CSH
    110_SOURCE=@HOME@/.login
    110_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.CSH
    120_GROUP=sapsys
    120_OWNER=@LOWER_SAPSYSTEMNAME@adm
    120_PERMISSION=0644
    120_SOURCE=@HOME@/.cshrc
    120_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.CSH
    130_SOURCE=@HOME@/.cshrc
    130_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.CSH
    200_SOURCE=@HOME@/.profile
    200_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.SH
    210_SOURCE=@HOME@/.profile
    210_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.SH
    [Z_R3DIRECTORIES_IND_IND]
    101_PATH=@SAPDIR@
    101_PERMISSION=0775
    101_SET_FILE_ATTRIBUTES=YES
    101_USERGROUP=sapsys
    101_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    102_PATH=@SAPDIR@/tmp
    103_PATH=@SAPDIR@/trans
    104_PATH=@SAPDIR@/trans/tmp
    104_SET_FILE_ATTRIBUTES=NO
    105_PATH=@SAPDIR@/trans/EPS
    106_PATH=@SAPDIR@/trans/EPS/in
    107_PATH=@SAPDIR@/trans/EPS/out
    108_PATH=@SAPDIR@/trans/EPS/log
    109_PATH=@SAPDIR@/trans/bin
    110_PATH=@SAPDIR@/trans/buffer
    111_PATH=@SAPDIR@/trans/cofiles
    112_PATH=@SAPDIR@/trans/data
    113_PATH=@SAPDIR@/trans/etc
    114_PATH=@SAPDIR@/trans/log
    115_PATH=@SAPDIR@/trans/sapnames
    120_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    120_PERMISSION=0751
    120_SET_FILE_ATTRIBUTES=YES
    121_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS
    121_PERMISSION=0755
    122_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe
    123_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe/opt
    124_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/gen
    125_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/gen/opt
    126_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/gen/dbg
    127_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/src
    128_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@
    129_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/data
    130_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/log
    131_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/work
    131_PERMISSION=0775
    132_PATH=@SAPMOUNT@
    140_PATH=@SAPMOUNTEXE@
    141_PATH=@SAPMOUNTPROFILE@
    141_PERMISSION=0755
    142_PATH=@SAPMOUNTGLOBAL@
    142_PERMISSION=0700
    150_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/sec
    160_PATH=@STARTDIRECTORY@
    160_PERMISSION=0777
    [Z_R3DIRPERMISSIONS_IND_IND]
    101_CHANGE_ON_NFS=NO
    101_PATH=@SAPMOUNT@
    101_PERMISSION=0755
    101_TRAVERSE=
    101_USERGROUP=sapsys
    101_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    102_CHANGE_ON_NFS=NO
    102_PATH=@SAPMOUNTEXE@
    102_PERMISSION=0755
    102_TRAVERSE=
    102_USERGROUP=sapsys
    102_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    103_CHANGE_ON_NFS=NO
    103_PATH=@SAPMOUNTGLOBAL@
    103_PERMISSION=0710
    103_TRAVERSE=
    103_USERGROUP=db@LOWER_DB_SID@adm
    103_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    104_CHANGE_ON_NFS=NO
    104_PATH=@SAPMOUNTPROFILE@
    104_PERMISSION=0755
    104_TRAVERSE=
    104_USERGROUP=sapsys
    104_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    105_CHANGE_ON_NFS=NO
    105_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    105_PERMISSION=0755
    105_TRAVERSE=
    105_USERGROUP=sapsys
    105_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    120_CHANGE_ON_NFS=NO
    120_PATH=@HOME@
    120_PERMISSION=0700
    120_TRAVERSE=
    120_USERGROUP=sapsys
    120_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    121_CHANGE_ON_NFS=NO
    121_PATH=@HOME@
    121_PERMISSION=0777
    121_TRAVERSE=FILES
    121_USERGROUP=sapsys
    121_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    130_CHANGE_ON_NFS=NO
    130_PATH=@STARTDIRECTORY@
    130_PERMISSION=0777
    130_TRAVERSE=
    130_USERGROUP=sapsys
    130_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    140_CHANGE_ON_NFS=YES
    140_PATH=@SAPDIR@/trans
    140_PERMISSION=0775
    140_TRAVERSE=
    140_USERGROUP=sapsys
    140_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    141_CHANGE_ON_NFS=YES
    141_PATH=@SAPDIR@/trans/bin
    141_PERMISSION=0775
    141_TRAVERSE=
    141_USERGROUP=sapsys
    141_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    [Z_R3FILEPERMISSIONS_IND_IND]
    101_CHANGE_ON_NFS=NO
    101_PATH=@SAPMOUNTEXE@
    101_PERMISSION=0755
    101_TRAVERSE=SUBDIRECTORIES
    101_USERGROUP=sapsys
    101_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    102_CHANGE_ON_NFS=NO
    102_PATH=@SAPMOUNTEXE@
    102_PERMISSION=0755
    102_TRAVERSE=FILES
    102_USERGROUP=sapsys
    102_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    103_CHANGE_ON_NFS=NO
    103_PATH=@SAPMOUNTGLOBAL@
    103_PERMISSION=0700
    103_USERGROUP=sapsys
    103_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    104_CHANGE_ON_NFS=NO
    104_PATH=@SAPMOUNTPROFILE@
    104_PERMISSION=0755
    104_TRAVERSE=SUBDIRECTORIES
    104_USERGROUP=sapsys
    104_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    105_CHANGE_ON_NFS=NO
    105_PATH=@SAPMOUNTPROFILE@
    105_PERMISSION=0755
    105_TRAVERSE=FILES
    105_USERGROUP=sapsys
    105_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    106_CHANGE_ON_NFS=NO
    106_PATH=@SAPMOUNTEXE@/saposcol
    106_PERMISSION=04755
    106_USERGROUP=sapsys
    106_USERNAME=root
    112_CHANGE_ON_NFS=NO
    112_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    112_PERMISSION=0751
    112_TRAVERSE=SUBDIRECTORIES
    112_USERGROUP=sapsys
    112_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    113_CHANGE_ON_NFS=NO
    113_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    113_PERMISSION=0751
    113_TRAVERSE=FILES
    113_USERGROUP=sapsys
    113_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    114_CHANGE_ON_NFS=NO
    114_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS
    114_PERMISSION=0755
    114_TRAVERSE=SUBDIRECTORIES
    114_USERGROUP=sapsys
    114_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    115_CHANGE_ON_NFS=NO
    115_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS
    115_PERMISSION=0755
    115_TRAVERSE=FILES
    115_USERGROUP=sapsys
    115_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    116_CHANGE_ON_NFS=NO
    116_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@
    116_PERMISSION=0755
    116_TRAVERSE=SUBDIRECTORIES
    116_USERGROUP=sapsys
    116_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    117_CHANGE_ON_NFS=NO
    117_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@
    117_PERMISSION=0755
    117_TRAVERSE=FILES
    117_USERGROUP=sapsys
    117_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    118_CHANGE_ON_NFS=NO
    118_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/work
    118_PERMISSION=0775
    118_USERGROUP=sapsys
    118_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    120_CHANGE_ON_NFS=NO
    120_PATH=@HOME@
    120_PERMISSION=0700
    120_USERGROUP=sapsys
    120_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    121_CHANGE_ON_NFS=NO
    121_PATH=@HOME@
    121_PERMISSION=0700
    121_TRAVERSE=FILES
    121_USERGROUP=sapsys
    121_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    [Z_R3LINKS_IND_IND]
    101_LINKCONTENT=@SAPMOUNTEXE@
    101_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe/dbg
    102_LINKCONTENT=dbg
    102_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe/run
    103_LINKCONTENT=@SAPMOUNTGLOBAL@
    103_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/global
    104_LINKCONTENT=@SAPMOUNTPROFILE@
    104_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/profile
    [Z_SAPDATAPATH]
    S1=/db2/@SAPSYSTEMNAME@/sapdata1
    S2=/db2/@SAPSYSTEMNAME@/sapdata2
    S3=/db2/@SAPSYSTEMNAME@/sapdata3
    S4=/db2/@SAPSYSTEMNAME@/sapdata4
    S5=/db2/@SAPSYSTEMNAME@/sapdata5
    S6=/db2/@SAPSYSTEMNAME@/sapdata6
    SAPDATAT=/db2/@SAPSYSTEMNAME@/sapdatat
    As you can see there is not an error message, the installation simply stops when the try to check the space available for tablespaces.
    Regards

  • BRtools table space creation error

    hi,
    Iam trying to create new table space in my R/3 system. When i went to brtools - space management sytem throwing error owner failed.I tried with all users to login like ( <SID>adm,administrator etc ...)even then same problem.Could you please suggest how to create table space with what login id
    Error:
    Main options for creation of tablespace in database WA6
    1 - Tablespace name (tablespace) ......... [PSAPECDATA]
    2 - Tablespace contents (contents) ....... [data]
    3 - Segment space management (space) ..... [auto]
    4 - SAP owner of tablespace (owner) ...... [EC5ADM]
    5 - Data type in tablespace (data) ....... [both]
    6 # Joined index/table tablespace (join) . []
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help
    BR0662I Enter your choice:
    c
    BR0280I BRSPACE time stamp: 2006-06-14 21.08.45
    BR0663I Your choice: 'c'
    BR0259I Program execution will be continued...
    BR0824E Owner EC5ADM not found in database or not SAP owner
    BR0691E Checking input value for 'owner' failed
    BR0669I Cannot continue due to previous warnings or errors - you can go back to
    repeat the last action
    BR0280I BRSPACE time stamp: 2006-06-14 21.08.45
    BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:
    Please suggest.
    - Cheers

    Login as ora<sid> and run brtools. Tablespace owner will be SAP<SID> or SAPR3 depends upon your version.
    Thanks
    Prince

  • Table space not reduce after delete in oracle 11G

    Hi Team,
    I have a DB 11.1.0.7 on unix.
    I have execute delete tables on tablespace, but this not reduce.
    Thanks

    935299 wrote:
    What segment space management type is defined for the tablespace in question?
    MANUAL
    Then you should check out the documentation some more.
    But even if you shrink the table segement what is that going to do for the data file size?
    I don't undertand you.
    ThanksYour thread is titled "Table space not reduce after delete in oracle 11G" which implies to me that you are interested in reducing the size of a tablespace (which really means reducing the size of the underlying datafile(s)).
    So, if you shrink the size of the sys.aud$ table, will that cause the datafile(s) to become smaller? Will it accomplish your goal? What else, if anything, needs to happen?

  • Table space not reduce after delete in oracle 10g

    Hi..
    Based on my system, i have found that my oracle table space did not reduce after the deletion query. Why ?.. Could somebody help me. As your info, I am using oracle 10g.
    Thank you,
    Baharin

    After Delete the table space will not be set free. high water mark will not be reset. to regain the space you need to recognize the objects from which you deleted the data. This can be done in many ways.
    1) Move the objects.
    Alter table temp move --> optionally tablespace clause can be used. After this you need to rebuild table indexes.
    2) With 10g table can be shrinked or reorganize to free the space.
    alter table mytable enable row movement;
    alter table mytable shrink space;
    3) Export/Import
    export the objects and drop and recreate with import.

  • How to restart after table space error

    Hi,
    While loading a big file ( 360 MB)  with the File -> XI-<ABAP prodxy from source, we got the table space error in middle of load. Due to Content conversion split for 20K we normally get many messages per load.
    In this case after basis increased the disk space, how do i restart the process so that it start from where it is left. I checked Moni and there is no Que. I checked RWB for adapter also and there is no message with error. I also checked integration and all possible places..
    The Alert that came in for failure has a message ID. I checked and found that message ID has been processed successfully. Still the count of records at the source does not match with target and lot of records are missing.
    Is there any way to re run the process from where it was left.
    Thanks

    Hi,
    Check following:
    - RWB->Message monitoring->Adapter engine (not integration server)
    -Check for follwing status:
    "Holding", "Waiting" "To be delivering" "Error" your message should be here any of above status.
    Note: in RWB message monitoring select "Adapter engine"
    Regards,
    Gourav
    reward points if it helps you

  • Temp Tables space problem with ORA-01114 and  ORA-27072:

    RDBMS :Oracle:9.2.0
    OS: Linux AS3
    Storage: SAND arrray (RAID 5)
    Problem on exeuting dml statement
    SQL> select * from myview ;
    select * from myview
    ERROR at line 1:
    ORA-01114: IO error writing block to file 201 (block # 3977)
    ORA-27072: skgfdisp: I/O error
    Linux Error: 28: No space left on device
    Additional information: 3976
    ORA-01114: IO error writing block to file 201 (block # 3977)
    ORA-27072: skgfdisp: I/O error
    Linux Error: 28: No space left on device
    Additional information: 3976
    With Regards
    Joy

    Hello joy,
    So, still looking for solution. I suggest you a sloution and it works well only if as you mentioned (in your previous post) that file causing error is temp file. So, get rid of this better you create new temporary table space and drop old one and then delete the old files manually.
    But this will work only for Temp Tablespace not for normal tablespaces and datafiles. Prepare new temporary tablespace at different location from the previous one, try to make it on different disk beacuse it may be due to corruption of physical medium too.
    Try this. If it works... you are through... otherwise i have no other options...
    Please update.....

  • Information about table spaces.

    Hi!
    I have a requirement to   create a Bex by which I can display the  list of table spaces available and status of  those  table spaces like memory free, Used. Though we can get this information from  DB02  I need to generate a  report and  broadcast that to users.
    Can anyone help me in telling me the table name  where you can get the list of table spaces  and infomation or any function module which lists the  table spaces name and  status of them. 
    Regards
    Venkat

    Hello,
    Could you please share more information about this? We need to do the same thing. How did you create your generic datasource? what table/Function module did you used?
    Thank you
    Ramona

  • Table space and recollection of released space after client deletion

    Dear All,
    I have two questions:
    1.Can any1 tell me how to determine the fastest growing table and how to reorganize table space.
    2. Is there any way by which we can recollect the space released:say after client deletion. I had deleted one client two  weeks back and when I saw the SAP/user drive I fow free space available remains the same.
    I searched but found no relevant clue.
    regards,
    Ashutosh

    1.- You can see the largest table report in ST04 (as far as i remember)...
    2.- You can reorganize your db using brtools - brspace...
    Read,
    http://help.sap.com/saphelp_erp2004/helpdata/en/32/0d0c888839164ba4245b3ff7969c59/frameset.htm
    Regards
    Juan

  • Table space need to be increased in every week..

    Dear Experts,
    We are facing a new problem .
    The problem is like , Last 6 months back we had done the Hard-ware migration. After
    migration we need to increase the table space in every 10 days.   But before migration , the table
    space was getting ing increased in every 45 days.
    In this way , we dont have much space left with us..
    I am not able to analyse the issue ...
    Please suggest .. What to check and necessary action ...
    Thanks,
    Sanjana

    Hi,
    Thank you for the response. Yes , the hord-ware migration is not linked with this issue. But this is happening after migration . So I was thinking , if any setting might have changed or something like that .
    Deleting all the redundant data in system means , it should run regaularly. And Now new developments have gone to production.
    And the data loads are carrying almost same amount of data. Only 2 changes, Material Master was coming on DELTA , Now its Coming on FULL Load.  Rest all loads are same as before migration.
    Kindly suggest.
    Thanks,
    Sanjana

  • How to Access Table Space Map in Oracle 10g OEM

    How and from where to Access Table Space Map in Oracle 10g OEM ??
    Thanks

    Hi,
    first of all, the online help system of grid control is outstanding. Just click on Help in the upper right corner and enter "Tablespace Extent Map" in the search form.
    Result:
    Show Tablespace Contents Page
    Each Oracle database is divided into one or more logical units called tablespaces. You can use Oracle Enterprise Manager to manage these tablespaces and create or modify the parameters for the tablespaces. Use the Tablespace property sheet to set general and storage information for the specified tablespace.
    Use the Show Tablespace Contents page to display the list of tablespace segments that comprise the existing tablespace. You can display Tablespace Extents by choosing Show Tablespace Extent Map at the bottom of the page. An extent is a logical unit of database storage space allocation made up of a number of contiguous data blocks. One or more extents in turn make up a segment. When the existing space in a segment is completely used, Oracle allocates a new extent for the segment.
    You can view segment extents by clicking on the link in the Extents column to display the Extents in Segments page.
    You can display the Show Tablespace Contents page by choosing Show Tablespace Contents from the command drop down list on the Tablespace property page, the Tablespace View page, or the Tablespace search results page.
    Note: Developers could only display the tablespace map to a maximum hard coded number of 30,000 extents. Tablespaces are often larger than that. If a tablespace is larger than 30,000 extents, the portion over that is displayed as Unmapped. To avoid exceeding the memory capacity of the tablespace map and to display the map without unmapped extents, use a search criteria displaying results of less than 30K extents.
    For an overview of tablespaces, see the "Overview of Tablespaces " chapter of the Oracle Database Concepts Guide.
    For more information about managing tablespaces, see the " Managing Tablespaces" chapter of the Oracle Database Administrators Guide.
    For more information about managing datafiles, see the " Managing Datafiles and Tempfiles" chapter of the Oracle Database Administrator's Guide.

  • Access Table Space Map in Oracle 10g EM

    From where can I access Access Table Space Map in Oracle 10g EM?
    Thanks

    From where can I access Access Table Space Map in Oracle 10g EM?
    Thanks

Maybe you are looking for