DB2 Tablespace Management

HI All
Can anyone pls let us know how to perform Tablespace Management in DB2,like increasing tablespace and adding datafile..etc.
Can it be done in SAP through DB02 Tcode if so how to do it,???
also how to do it through DB2 from OS level.
Thanks in Advance
Infinite Team

Hi All
We noticed that BTABD was hundred percent and now database is not coming up and from operating system level if we login and try to increase the tablespace through sql command it says:
"DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030"
Not only that any command we execute it gives same error message and if we start sap it says Activate Database Failed, R3trans Connect Failed, Database start up failed
Pls help.
Thanks in Advance
Infinite Team

Similar Messages

Proactive Tablespace Management in a large environment

Hi, I was wondering how others in the community manage tablespaces proactively. In our situation we have thousands of oracle databases and are not using a primary DBA service model. We don't have DBA's looking at individual databases on a daily basis.
It often becomes a reactive measure to add space. Given the size of our environment tablespace management becomes a very tedious and time consuming action for us. Looking for way to minimize or automate this process.
I'm looking for a way to have a more "intelligent autoextend". With autoextend, the database engine won't take action until there is space pressure (ie. 99%). I'm looking for something when it crosses a defined thershold (ie. 85%).
To further add to the complexity we use shared storage (ASM) for many databases. There needs to be intelligence to check the available space first.
We are considering writing a custom script and using EM's Corrective Action to invoke the script based on the threshold. This will be a fairly significant development effort.
Is there anything from oracle "out of the box" that I should be considering?
How are others out there managing space in their large, complex oracle environments?
Ideas are much appreciated!

I'm looking for a way to have a more "intelligent autoextend". With autoextend, the database engine won't take action until there is space pressure (ie. 99%). I'm looking for something when it crosses a defined thershold (ie. 85%).What will be a benefit of such "intelligent autoextend"? What is a difference if a data file extended being 85% full versus 99% full?
From Application perspective there is no difference, it got the space for data in any case.
My ultimate goal is to not have DBA's add space entirely (or close to it)why the "out of box" autoextend does not work for you?
Just specify MAXSIZE according to your storage and DBA do not need to add space entirely. Until disk is full.
But. If you really do need some "intelligent autoextend" you (or your DBA) can write a PL/SQL script that can use any level of intelligence you put in its logic. It can forecast, extend datafiles, add datafiles, shrink them, even check disk space and send email about it.
Writing this script will be that "more exciting DBA task" ;)

Reading Images from DB2 content Manager

Has anybody have read images from IBM db2 content manager using oracel forms.
any links will be helpfu;
or any links to how to make windows API calls in forms 5.0.

OK, I found Greg's reply and that fixed it, once I played with it a bit.
"Cory McGinnis" <[email protected]> wrote:
>
I am displaying an html page from a <cm:select> but the images do not
display.
I have set up the dmsbase directory as per the samplePortal, and loaded
the content.
The HTML displays, but with errors for the images.
Here's the select from the portlet:
<cm:select contentHome="<%=ContentHelper.DEF_CONTENT_MANAGER_HOME%>"
query="type='page'"
id="textDocs"/>
<es:forEachInArray array="<%=textDocs%>" id="aTextDoc" type="com.bea.p13n.content.Content">
<p><cm:printDoc id="aTextDoc" failOnError="true" /></p>
</es:forEachInArray>

In Db2 tablespace problem

Hi,
We are using DB2 database.Here we enabled the Autoresize for tablespace.If tablespace enabled as autoresize means it should stay on 99%.In my case reaches 99.25%,100% some tablespace reachs.I checked the file system enough space is there.In this case how to increase the size of autoresize tablespace.
How to slove this problem...
Regards,
Kumar

Hello Kumar ,
this is usually not an Indicator for having an problem .
see
[DB2 : Automatic re-sizing of table spaces|http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0012277.html]
Tablespace extension is controlled by Parameters INCREASESIZE ,
(also MAXSIZE but this is usually not used in SAP Environments ) .
Depending on Increasesize , the tablespace is increased using this amount of storage .
If the tablespace reaches 100% filling grade , it is extended automatically (therefor "Auto"-resize ) . You just need to monitor freespace in the filesystems for the tablespaces to have enough space for enlarging the containers available .
Please recheck for the tablespaces displayed with 100% filling grade , whether there are still free pages using an tablespace snapshot
db2 get snapshot for tablespaces on <DBSID>
Best regards
dirk

Old db2 tablespace names in HR SP22 error log

Hi all,
We are applying HR support packages on a test box. This test instance is a copy of our production ERP instance. The copy was done using a backup/restore off the PRD database.
We get an error when applying SAPKE60020 because it is trying to create a table in a tablespace that does not exist. The tablespaces it is trying to access are of the pattern PRD#STABD, PRD#POOLD etc. PRD is copied to TST.
I have updated tables TADB6, TSDB6 and IADB6 and changed PRD to TST for all tablespaces. At the OS level if I run a "db2 list tablespaces" all the names show up as TST#<tablespacename>.
I am not sure why it is trying to access PRD#<tablespace>. Is there someplace else I need to make a change from the old name?
Thanks,
Kevin

Hi Kevin,
no I am running out of ideas. As Dirk mentioned the tablespace names are only maintained in tables TADB6, IADB6 and TSDB6. The SAP DDIC assembles CREATE TABLE statements for new tables using those table entries.
If you have changed all entries with the old SID in these tables and if you haven made sure that no old entries are buffered in the SAP table buffers ( $SYNC )
, the SAP DDIC should not generate CREATE TABLE statements for new tables containing the old tablespace names any more.
For existing tables that need to be converted the SAP DDIC reads out the current tablespace location from SYSCAT.TABLES and stores them into table DDSTORAGE before the table is dropped. For recreating the tables the DDIC then uses the DDSTORAGE entries. If no DDSTORAGE entries exist DDIC again falls back to TADB6, IADB6 and TSDB6.
If no table conversion is running table DDSTORAGE is usually empty.
Regards
Frank

Proactive Tablespace Management

hi,
In Oracle Database 10g, by default, all tablespaces have built-in alerts that notify you when the free space in the tablespace goes below a certain predetermined threshold level. Is it True?
How to check default threshholds at tablespace level in 10g

user1175505 wrote:
hi,
In Oracle Database 10g, by default, all tablespaces have built-in alerts that notify you when the free space in the tablespace goes below a certain predetermined threshold level. Is it True?
How to check default threshholds at tablespace level in 10gYou can use Enterprise Manager.
You better read the documentation here for the alerts regarding tablespaces:
http://www.comp.dit.ie/btierney/oracle11gdoc/server.111/b28310/schema001.htm
regards

Segment space for Manual tablespace management

Hi,
wanted to know if 10g segment advisor can advise on segments that exsists in a tablespaces that is set to manual extent management.
thanks,
Ven.

From the
Oracle® Database Administrator's Guide
10g Release 2 (10.2)
Part Number B14231-01
14 Managing Space for Schema Objects
Understanding Reclaimable Unused Space
You use the Segment Advisor to identify segments that would benefit from online segment shrink. Only segments in locally managed tablespaces with automatic segment space management (ASSM) are eligible. Other restrictions on segment type exist. For more information, see "Shrinking Database Segments Online".

System tablespace management in oracle 9i

Hi,
I would like to know whether system tablespace in oracle 9i by default is locally managed or dictionary managed

Hi,
I would like to know whether system tablespace in oracle 9i by default is locally managed or dictionary managed SYSTEM tablespace in 9i rdbms can ONLY be dictionary managed.

DB2 tablespace

Dear All,
May I know the proper way to increase a tablespace? Should change the tablespace from transaction DB02 from SAP login or I should update in the DB2 control center?
Currently, my system is generating some abap dumps which is caused by some tablespace is almost full.
Will also really appreciate it if someone can guide me to update the tablespace.
Regards,
John

If you are out of space in you tablespaces but not out of space in your sapdatas then you can either manually extend the size of the containers or setup Auto-resize.
There are various ways to setup Auto-resize.. I usually do a list tablespaces and pipe that to a file, then write an inline ksh to issue the alter TS statement while reading through the file.
If you are out of space in your sapdata's then you can either increase the lun size, if your san allows this, or add additional sapdata's and containers.
In adding addtional containers, my preferred method is to add another sapdata and go through rebalancing. keeping all new containers the same size as the old containers
Also be aware you can shrink tablespaces that have a large amount of free space and free up space in your sapdatas as well. Of course if your HWM is artifically high this requires more work.

Tablespace management with ASSM

Since ASSM is the default in 10g I was wondering how people are dealing with space management in their tablespaces? How do you know if you have enough space for the next extent of a table when you don't know how big the next extent is? Even if you did know the size of the next extent, how do you allow for the fact that the datafile for the tablespace is set to autoextend? And what if there isn't enough room on the disk for the tablespace to autoextend? What are you doing to deal with these questions?

We use ASSM for managing all of our tablespaces. Are you using the Database Control web page? On the Administration tab, you can specify how big you want each extent to be. For example, if you have a 10 Mg tablespace, and you set the tablespace size limit to 20 Mg you can then specify to grow in 1 Mg extents until you reach the limit. If you aren't using Database Control tool, respond and I will get you the command line syntax for managing your tablespaces.
What operating system is your database running on? Because you will need to monitor how much available disk space you have on your server, and how you do that depends on which OS you are running.

Tablespace management system and sysaux size.. a concern..

Hi mates,
I have the report of my tablespace as thus:
FILE_NAME TABLESPACE_NAME STA Total MB % Free Aext
/usr/lib/oracle/xe/oradata/XE/MD MDATE AVA 196.608 13.57 YES
ATE.dbf
/usr/lib/oracle/xe/oradata/XE/SL SLIPSTREAM AVA 327.680 17.54 YES
IPSTREAM.dbf
/usr/lib/oracle/xe/oradata/XE/sy SYSAUX AVA 542.720 1.77 YES
saux.dbf
/usr/lib/oracle/xe/oradata/XE/sy SYSTEM AVA 378.880 1.69 YES
stem.dbf
/usr/lib/oracle/xe/oradata/XE/TX TXCD AVA 131.072 99.46 YES
CD.dbf
/usr/lib/oracle/xe/oradata/XE/un UNDO AVA 1,048.576 90.92 NO
do
/usr/lib/oracle/xe/oradata/XE/us USERS AVA 102.400 98.38 YES
ers.dbf
Can you pls tell me if the size of the sysaux and system tablespace should be a concern as I have freespace of 1.69 and 1.77%.
Thanxxxx.
Kenny

A datafile may not be able to resize (file system full). And resizing it may cause file fragmentation of that file (on that file system).
I prefer to add a new file, e.g.
ALTER TABLESPACE <tablespace> ADD DATAFILE [<filename>] SIZE <size>
When using ASM, the filename is determined (per OFA standards) by ASM itself. No need for the DBA to concern him/herself with directory structures and filenames.
By the way, the topic of this forum is SQL and PL/SQL - not database administration. I suggest that in future you post questions like this to the Database forum instead.

Tablespace management

hi all,
i am a newbie, i newly installed oracle 10g in windows 2003 server, and i add a tablespace and given 4 GB size. my disk space is 90 GB. now how much i can increase the tablespace sizes of TSs\
SYSTEM
SYSAUX
USERS
TEMP
UNDOTBS
EXAMPLE
is this necessary to hold the EXAMPLE T.S, as it holds only 100 MB space (used 77 %)
pls suggest me in this regard.
thanks & Regards

785092 wrote:
hi all,
i am a newbie, i newly installed oracle 10g in windows 2003 server, and i add a tablespace and given 4 GB size. my disk space is 90 GB. now how much i can increase the tablespace sizes of TSs\
SYSTEM
SYSAUX
USERS
TEMP
UNDOTBS
EXAMPLE
You have all the 90GB to increase the size of your tablespaces. But do you need that?
Also don't worry about increasing the above permanent tablespaces, as they all are autoextensible.
is this necessary to hold the EXAMPLE T.S, as it holds only 100 MB space (used 77 %)It contains the sample schemas of the database.
regards

EHPI and DB2 DMS storage management

Hi Guys,
I am having a trouble with Enhancement package installer while applying enchancement packs to ABAP instances in DB2 environment. I am using DMS storage managementmethod in DB2 for tablespace management. While applying the enhancement pack1 for netweaver the installation tool asks for creation of new tables and I create the required tables spaces as I needed. The tool fails with insufficent space in tablespaces. However the tablesspaces are setup to grow when required not like assigned free space in a tablespace.The file system has total 16GB available and it only needs about 3GB. Since it can't see some required freespace available with in the tablespace it can't proceed.
1) Did any one face this issue. IF so how to overcome this issue.
2) Is there anyway we can bypass this check and cotinue with installation. In some steps we can jump with a password but there is no such thing to this step.
Your early reply is highly appreciated.
Regards
Srini

EHPI tool itself check how much space you needed in a tablespace. You have to add that space in tablespace then only you can proceedd otherwise it will always show the error...
thank sunny

Portal, Tablespace defragmentation and Locally Managed tablespaces

We are setting up a Big portal installation. We want to use seperate small, medium and large tablespaces for data, lobs and index as described in the de-fragmention start living white paper. We will also use locally managed tablespaces.
Has anybody set-up a portal installation like this. What where the large and medium data, index and lob segments ?
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by David Stoller ():
Anyone try using IFS in a Locally Managed Tablespace? Is it OK?<HR></BLOCKQUOTE>
Yes, we have all tablespaces managed locally. No problems with that.

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

DB2 Tablespace Management

Similar Messages

Maybe you are looking for