STORAGE parameter in CREATE TABLESPACE

Hello all,
Env: 10gR2
I have the export of a schema of around 70Gb from 9i. I need to Import it to 10g.
This will be used only for 'SELECT', there wont be any DML once i import the data.
There are tables of size upto 20Gb.
What would be the best STORAGE parameters that i should be using along with the CREATE TABLESPACE if my db block size is 8k?
TIA,
JJ

If you are using locally managed tablespace then it is not required to specify storage parameters like initial, next and pctincrease. It is better to create LMT with uniform extent size. For the table with 20GB data create a seperate tablespace with uniform extent size as 1024MB. All tables of size more than 1GB can be allocated to this TS. For tabes of size between 100MB and 1GB create seperate tablespace of extent size 100MB. For all other tables create another TS with extent size 10M.
If you are using dictionary managed tablespace then calculate the size of tables and first create empty tables with the necessary initial and next value. Then import data with the option IGNORE=Y.
Mohan
http://www.myoracleguide.com

Similar Messages

Storage parameter for Temp tablespace

Hi all,
Greetings of the day...
DB version is 10.2.0.4 ..Size of db is 550gb and in that temp tablespace is 40gb... daily and frequently we used to unable to extent temp segments...Saw the storage parameters of temp segments it has only 'EXTENT MANAGEMENT LOCAL UNIFORM SIZE 16777216'
Please suggest as how to define storage parameters for temp tablespace...Am able to find the query which uses temp segments...Just needed to know abt the storage parameters for it..
thanks,
baskar.l

CREATE TEMPORARY TABLESPACE TEMP TEMPFILE
'/u02/TSTLOG/temp01.dbf' SIZE 15360M AUTOEXTEND ON NEXT 100M MAXSIZE 32767M
TABLESPACE GROUP ''
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
Hope this will work.
Regards
Asif Kabir

Default Storage versus Uniform size at creating Tablespace

anybody can explain if those two concepts mean same? in my practice, i need to dump all data from 9i to 10g database, in 9i a tablespace created by :
CREATE TABLESPACE DATA_TS
DATAFILE '/opt/oracle/u01/data_04.dbf' SIZE 11M AUTOEXTEND ON NEXT 1024K MAXSIZE UNLIMITED
EXTENT MANAGEMENT DICTIONARY
LOGGING
DEFAULT STORAGE(INITIAL 112K
NEXT 112K
MINEXTENTS 1
MAXEXTENTS 1017
PCTINCREASE 0)
ONLINE
PERMANENT
SEGMENT SPACE MANAGEMENT MANUAL
so in 10g I created tblsp like:
CREATE TABLESPACE DATA_TS
DATAFILE '/opt/oracle/u10/data_04.dbf' SIZE 11M AUTOEXTEND ON NEXT 1024K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 112K
LOGGING
ONLINE
SEGMENT SPACE MANAGEMENT MANUAL
are they same?

Hi,
Two concepts are not same.
Check this link:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/tspaces.htm
Starting with Oracle9i, the default for extent management when creating a tablespace is locally managed. However, you can explicitly specify that you want to create a dictionary-managed tablespace. For dictionary-managed tablespaces, Oracle updates the appropriate tables in the data dictionary whenever an extent is allocated, or freed for reuse.

Alter the tablespace storage parameter

Hi,
I want to alter the tablespace storage parameter from 1024 to 200 KB. Can anyone please provide me what is the procedure? Its very urgent.
Suman

SQL> select tablespace_name, EXTENT_MANAGEMENT, ALLOCATION_TYPE, SEGMENT_SPACE_M
ANAGEMENT from dba_tablespaces;
Output of the sql
TABLESPACE_NAME                EXTENT_MAN ALLOCATIO SEGMEN
SYSTEM                         DICTIONARY USER      MANUAL
PSAPR3E                        LOCAL      SYSTEM    MANUAL
PSAPR3E620                     LOCAL      SYSTEM    MANUAL
PSAPR3EUSR                     LOCAL      SYSTEM    MANUAL
PSAPTEMP                       LOCAL      UNIFORM   MANUAL
PSAPTF60D                      LOCAL      SYSTEM    MANUAL
PSAPUNDO                       LOCAL      SYSTEM    MANUAL
SYSAUX                         LOCAL      SYSTEM    AUTO
<u><b>PSAPR3E700                     LOCAL      UNIFORM   AUTO</b></u>
Message was edited by:
        Amit Jain

Default storage for locally managed tablespaces

the documentation says you cannot have a default storage parameter for locally managed tablespaces. Does this mean that we cannot specify
INITIAL
NEXT
PCTINCREASE
MINEXTENTS
MAXEXTENTS for such tablespaces, or is there another way we can, without using default storage?
thanks

I amnot sure where you read that part that the default storage clause can't be given.Please see here,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#sthref1149
From the doc,
Creating a Locally Managed Tablespace
If the CREATE TABLESPACE statement includes a DEFAULT storage clause, then the database considers the following:
If you specified the MINIMUM EXTENT clause, the database evaluates whether the values of MINIMUM EXTENT, INITIAL, and NEXT are equal and the value of PCTINCREASE is 0. If so, the database creates a locally managed uniform tablespace with extent size = INITIAL. If the MINIMUM EXTENT, INITIAL, and NEXT parameters are not equal, or if PCTINCREASE is not 0, the database ignores any extent storage parameters you may specify and creates a locally managed, autoallocated tablespace.
If you did not specify MINIMUM EXTENT clause, the database evaluates only whether the storage values of INITIAL and NEXT are equal and PCTINCREASE is 0. If so, the tablespace is locally managed and uniform. Otherwise, the tablespace is locally managed and autoallocated.
HTH
Aman....

Error in creating tablespace

Machine has the following configuration,
Oracle 10g 10.2.0
Solaris 10
Sparc v9-64 bit
I have mounted NAS(Network attached Storage) device on solaris using NFS file system. The device has been mounted using sharity software.
The problem is that when i execute the following command in sqlplus,
create tablespace test datafile '/storage/test.dbf' size 1m autoextend on
(/storage is the mount point for NAS device)
then i get the following error message
ORA-01119: error in creating database file '/storage/test.dbf'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options.
Additional Information:2

this is the document
http://download-uk.oracle.com/docs/cd/B19306_01/install.102/b15660/app_nas.htm#BCFEAHIC
and this will help either
10gR2 "database backup" to nfs mounted dir results in ORA-27054 NFS error

Not able to Create TABLESPACE PSAPROLL|PSAPUNDO    with 728 MB

Hi Experts,
               When i an trying to upgrade PI 7.0 to pi 7.1 with EHP1 in checks roadmap in abap it throws error like
ERROR> Insufficient free space in the database as follows:
Create TABLESPACE PSAPROLL|PSAPUNDO    with 728 MB
INFO> To adjust the size of your tablespaces, you may use the commands
      in file '/oracle/stage/upg/abap/log/ORATBSXT.LST' using the 'brspace' utility.
      Please copy the file before making changes, as it may be
      overwritten in subsequent upgrade phases.
In the location
'/oracle/stage/upg/abap/log/ORATBSXT.LST
These are examples for brspace commands to extend/create the required
tablespaces. You can adapt them according to your own needs.
Add option '-c force' to call the commands in batch mode.
Change option '-autoextend' to 'yes' and set '-maxsize' and '-incrsize'
to create autoextensible segments.
brspace -function tscreate -tablespace PSAPROLL|PSAPUNDO -owner SAPSR3 -size 728 -autoe
xtend no
info while creating : PSAPUNDO: Command not found.
with the help of this above command i am not able to create the tablespace.
My Existing tabelspaces are
PSAPSR3
PSAPSR3700
PSAPSR3DB
PSAPSR3USR
PSAPTEMP
PSAPUNDO1
SYSAUX
SYSTEM
Plz help me on this ASAP.
Thanks,
Hari

Your real problem is that PSAPUNDO does not exist. For an unknown reason you are using PSAPUNDO1. so, you must fix this:
shutdown your DB.
rename tablespace PSAPUNDO1 to PSAPUNDO. this can be done with:
brspace -c force -f tsalter -a rename -t PSAPUNDO1 -n PSAPUNDO
you will also need to change parameter undo_tablespace to PSAPUNDO
if using initSID.ora, change this manually. or else, do this:
alter system set undo_tablespace=PSAPUNDO scope=both;
you might need to restart your database.
good luck.

Create tablespace issue

Hi;
I wanna learn one thing...
I have oracle ebs r11i wiht 10gr2 db, and its prod instance...
Issue is like this:
I have one tablespace lets us call it XXX and it has datafile like xx1.dbf,xx2.dbf..... I want to delete those dbf becouse their each size is 40 GB, and i want to create 2 new datafile which is each 10Gb.
Would you give me steps and command how i can do that?
Thanks

tablespace - XXX
datafile - xx1.dbf,xx2.dbf.....
you want to delete those dbf becouse their each size is 40 GB, and i want to create 2 new datafile which is each 10Gb.
1) If you want to delete 40 GB dbf's, you will loose data.
2) If you really do not want those data, you can go ahead by dropping and creating DBF with 10 GB.
steps and command how i can do that?
I have give below sample commands, go through it thoroughly and go ahead.
Best of Luck.
=================================================================
CREATING TABLESPACES
====================
CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 100M
AUTOEXTEND ON NEXT 5M MAXSIZE 200M;
Locally Managed Tablespaces
===========================
CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 500M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K;
Dictionary Managed Tablespaces
==============================
CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 500M
EXTENT MANAGEMENT DICTIONARY DEFAULT STORAGE ( initial 1M NEXT 1M );
Undo Tablespace
===============
CREATE UNDO TABLESPACE undo1 DATAFILE '/u01/oradata/undo101.dbf' SIZE 40M;
Enabling Automatic Extension of Data Files
==========================================
ALTER DATABASE DATAFILE '/u01/oradata/userdata02.dbf' SIZE 200M AUTOEXTEND ON NEXT 10M MAXSIZE 500M;
SAMPLES
=======
SQL> CREATE TABLESPACE data01
2 DATAFILE '$HOME/ORADATA/u04/data01.dbf' SIZE 2M
3 EXTENT MANAGEMENT DICTIONARY;
Tablespace created.
SQL> CREATE TABLESPACE data02
2 DATAFILE '$HOME/ORADATA/u03/data02.dbf' SIZE 1M
3 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 100K;
Tablespace created.
SQL> CREATE TABLESPACE indx01
2 DATAFILE '$HOME/ORADATA/u02/indx01.dbf' SIZE 1M
3 AUTOEXTEND ON NEXT 500K MAXSIZE 2M
4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 4K;
Tablespace created.
SQL> CREATE TABLESPACE ronly
2 DATAFILE '$HOME/ORADATA/u01/ronly01.dbf' SIZE 1M;
Tablespace created.
TO QUERY ALL TABLESPACES
========================
SELECT * FROM v$tablespace;
ALTER TABLESPACE
================
ALTER DATABASE DATAFILE '$HOME/ORADATA/u03/data02.dbf' RESIZE 1500K;

Create tablespace with extend, etc.

Hi guys,
I am typing the following commands bellow: (ORACLE_HOME and ORACLE_SID is set up correctly).
#sqlplus sys/<sys-password> as sysdba ==> worked very well, of course !
SQL> create tablespace imm datafile $ORACLE_HOME/oradata/$ORACLE_SID/imm01.dbf size 100M autoextend on next 100M;
ERROR at line 1:
ORA-01034: ORACLE not available
I have the below scripts set up correctly. Any one know how can I solve this problem ?!
Any help is appreciate !
# dbstart
SQL*Plus: Release 9.2.0.1.0 - Production on Fri Apr 7 16:46:24 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORACLE instance started.
Total System Global Area 672223892 bytes
Fixed Size 455316 bytes
Variable Size 268435456 bytes
Database Buffers 402653184 bytes
Redo Buffers 679936 bytes
Database mounted.
Database opened.
SQL> Disconnected from Oracle9i Release 9.2.0.1.0 - Production
JServer Release 9.2.0.1.0 - Production
Database "immdb" warm started.
# lsnrctl start
LSNRCTL for Solaris: Version 9.2.0.1.0 - Production on 07-APR-2006 16:46:46
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Starting /apps/oracle/OraHome//bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 9.2.0.1.0 - Production
System parameter file is /apps/oracle/OraHome/network/admin/listener.ora
Log messages written to /apps/oracle/OraHome/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=gama2)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Solaris: Version 9.2.0.1.0 - Production
Start Date 07-APR-2006 16:46:46
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File /apps/oracle/OraHome/network/admin/listener.ora
Listener Log File /apps/oracle/OraHome/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=gama2)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "immdb.gama2" has 1 instance(s).
Instance "immdb", status UNKNOWN, has 1 handler(s) for this service...
Service "oradb.gama2" has 1 instance(s).
Instance "oradb", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Cheers,
Murilo

Can i perhaps add Operating system environment variable to DATAFILE value somehow? I don't want to create tablespace with full file path, starting from drive name and ending with file name.You can use variables in dbca when you create a database (I already can hear you say you don't want that)
You can also use Oracle Managed Files for the entire database ( I already can hear you say you don't want that)
You can not use relative paths, which begs the question why you don't want to use an absolute path, assuming you seldomly create a tablespace.
I don't want to see posts like yours with unjustified 'complaints', yet I do respond to it.
Sybrand Bakker
Senior Oracle DBA

How to create tablespace HRAPP

Hi everyone,
@Nicolas ; @Hakan Biroglu
My system: Windows Server 2003 32-bit ; Oracle DB 10.1.0.2.0 ; PT 8.52 ; PeopleSoft Human Capital Management and Campus Solutions 9.0 - Revision 5 ;
During Data Mover script I recieve the following error :
Importing AAP_ETHNIC_PMPT
Creating Table AAP_ETHNIC_PMPT
- SQL Error. Error Position: 108 Return: 959 - ORA-00959: tablespace 'HRAPP' does not exist
CREATE TABLE PS_AAP_ETHNIC_PMPT (ETHNIC_GROUP VARCHAR2(1) NOT NULL, DESCR VARCHAR2(30) NOT NULL) TABLESPACE HRAPP STORAGE (INITIAL 40000 NEXT 100000 MAXEXTENTS UNLIMITED PCTINCREASE 0) PCTFREE 10 PCTUSED 80
Error: Unable to process create statement for AAP_ETHNIC_PMPT
Ended: Tue Aug 21 16:19:06 2012
Unsuccessful completion
How can I fix this error,please help ?

Tablespace HRAPP should have been created when you ran hcddl.sql.
CREATE TABLESPACE HRAPP DATAFILE '<drive>:\oradata\<SID>\hrapp.dbf' SIZE 350M
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
SEGMENT SPACE MANAGEMENT AUTO
Make sure all the tablespaces defined in the file hcddl.sql are created!
Judging by your other thread you have choosen to create a PeopleTools system database, without an application (HCM).
Now you want to run the dms to create HCM tables???
If you want to create an HCM database you need to run hcddl.sql.
Edited by: Hakan Biroglu on Aug 21, 2012 4:38 PM

Create tablespace using RAW device

Hi,
When you create the tablespace using RAW device, you no need to specify the size parameter in the sql. It works in Solaris but not in Linux.
I dont know why, can anyone experience this issue before? please let me know
Thanks
Veera

My advice for you would be to always include SIZE parameter when you create tablespace, redo log file on raw device.
Best Regards
Krystian Zieja / mob

Creating tablespace and databasefiles

I am creating a tablespace with sets of database files within it with the following option
I get the following error:
CREATE SMALLFILE TABLESPACE "CLAIMS_NEW"
DATAFILE
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW1.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW2.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW3.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW4.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW5.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW6.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW7.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW8.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW9.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW10.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW11.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW12.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW13.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW14.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M,
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\QAIDM2\CLAIMS_NEW15.DBF' SIZE 4096M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE 4096M
NOLOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
Error:
Error at Command Line:1 Column:0
Error report:
SQL Error: ORA-00059: maximum number of DB_FILES exceeded
00059. 00000 - "maximum number of DB_FILES exceeded"
*Cause: The value of the DB_FILES initialization parameter was exceeded.
*Action: Increase the value of the DB_FILES parameter and warm start.
I am not sure how to rectify this error ? Do I have to reduce number of database files ?
Please advise
Thanks
Jay

Cause of The Problem
You have reached the limit of DB_FILES parameter. Before entering into solution part let's have an idea about DB_FILES and MAXDATAFILES parameter.
The DB_FILES parameter limits the maximum number of datafile can exist in oracle database. We can't change this parameter dynamically. We have to change it spfile by using ALTER SYSTEM .... SCOPE=SPFILE or in the pfile.
And the MAXDATAFILES parameter you can find with the CREATE DATABASE command or in CREATE CONTROLFILE command. It is also a limitation of maximum number of datafiles can be in the datafile. But starting from oracle 8 this hard limit parameter can be easily expanded up to DB_FILES parameter. So, if you attempt to add a new file whose number is greater than MAXDATAFILES, but less than or equal to DB_FILES, the MAXDATAFILES parameter of the control file will expand automatically to accommodate more files.
So, if you are after oracle 8i then we should just forget about MAXDATAFILES parameter. We should rather think about DB_FILES parameter.
Solution of The Problem
If you use pfile to startup the database then edit pfile and add/modify the DB_FILES parameter to a greater value so that it can accommodate higher number of datafiles. Then start the database using that pfile.
If you use spfile to startup the database then issue,
SQL> alter system set db_files=300 scope=spfile;
System altered.
Then start your database and either create tablespace or add datafile to an existing tablespace. Hopefully it will work.source:-
http://arjudba.blogspot.com/2008/08/maxdatafiles-dbfiles-parameters-and-ora.html
also refer,
http://laurentschneider.com/wordpress/2006/01/change-maxdatafiles-malogfiles-maxinstances-maxlogmembers-without-downtime.html

The OPTIMAL storage parameter in the rollback segment

Hi,
in metalink note Subject: ORA-01555 "Snapshot too old" in Very Large Databases (if using Rollback Segments)
Doc ID: 45895.1
I see :
Solution 1d:
    Don't use the OPTIMAL storage parameter in the rollback segment. but how not to use the OPTIMAL storage parameter in the rollback segment ?
Thank you.

If you are using undo_management=AUTO (in 9i or higher) then there is no "OPTIMAL" setting.
"OPTIMAL" is when using Manual Undo Management with Rollback Segments created by the DBA.
If you are using Manual Undo Management, check your Rollback Segments. The Optimal size would be visible in V$ROLLSTAT.
select a.segment_name a, b.xacts b, b.waits c, b.shrinks e, b.wraps f,
      b.extends g, b.rssize/1024/1024 h, b.optsize/1024/1024 i,
      b.hwmsize/1024/1024 j, b.aveactive/1024/1024 k , b.status l
-- from v$rollname a, v$rollstat b
from dba_rollback_segs a, v$rollstat b
where a.segment_id = b.usn(+)
and b.status in ('ONLINE', 'PENDING OFFLINE','FULL')
order by a.segment_name
/To unset the Optimal setting you can run
alter rollback segment SEGMENT_NAME storage (optimal NULL);Note that if you unset OPTIMAL, then your Rollback Segments will remain at very large sizes if and when they grow running large transactions ("OPTIMAL" is the pre-9i method for Oracle to automatically shrink Rollback Segments). You can manually SHRINK or DROP and CREATE Rollback Segments then.

PSAPTEMP default storage (Parameter settings)

Hi there,
I am trying to increase INITIAL and NEXT values for default setting of PSAPTEMP. Using sapdba version 9, under Tablespace, when I select the INITIAL and change value, the value gets reset to default 1024K. How can I extend these values. Do I need to drop and recreate or can I do it online.
Regards,
Jeet

Dear Jeet,
first of all: don't use sapdba anymore.
It's not developed anymore and the recommendated tool is now br*tools.
See note
12741 - Current versions of SAPDBA and BR*Tools
for details
Concerning your question:
When you've got a locally managed temp. tablespace (as it is recommended) then the INITIAL and NEXT values should be identical and the allocation type for the tablespace should be UNIFORM.
The exact value for this parmeters depends on the sort_area-size used in the database.
The formula looks like this:
( N * sort_area_size ) + 2 * db_block_size
db_block_size is 8K in SAP systems and the N depends on the size of your PSAPTEMP (tempsize):
N = 1 : tempsize <= 2 GB
N = 3 : 2 GB < tempsize <= 6 GB
N = 5 : 6 GB < tempsize <= 10 GB
N = 10 : 10 GB < tempsize
All this - in more detail - can be found in these notes:
164925 - Storage parameter of tablespace PSAPTEMP
659946 - FAQ: Temporary tablespaces
Hope that helps.
Best regards, Lars

Retrieving LOB Storage Parameter through jdbc

Is there a way to retrieve the lob column's initial and next storage parameter through jdbc?
I need to replicate a table in one database to another database and with tables containing lobs(clobs,blobs),
I need to get the storage parameter values for creating a "Create Table" script on the other database.
tnx

In records.jsp change your line that reads:
out.print("<a href =vdetails.jsp>" + plantno);Change it to:
out.print("<a href =vdetails.jsp?plantno=" + plantno + ">" + plantno);Then you can change your line in vdetails.jsp:
String pla=request.getParameter("something");to
String pla=request.getParameter("plantno");That should be enough to get you started.
You should investigate either the use of a bean or even a custom tag to remove these scriplets from your JSP.

STORAGE parameter in CREATE TABLESPACE

Similar Messages

Maybe you are looking for