Regarding Maintain DB Storage Parameters

hai
we have data in Oracle data tables.
I heard that while creating chracteristics , i need to give 'MAintain DB Storage Parameters' in "Extra" on menu bar.
Can anyone explain why we need to give 'Maintain DB Storage PArameters' here and what is advatage and its funcationality pls
i ll assign the points
bye
rizwan

You have to maintain Data Class and Size Category. These things are basically used for Database settings as below.
As it is in my experience we don't fill anything in this option.
Data Class
With the data type, you determine, on a logical level, in which physical area of the database (of the TABLESPACE with ORACLE) your table is stored. With the correct choice of data type, your table is automatically assigned to the correct area when creating on the database.
The most important data types (apart from the system data) are:
APPL0    Master data
APPL1    Transaction data
APPL2    Organization and customizing data
With Master data, you are dealing with data that is often accessed read, but that is rarely activated. Transaction data is data that is often actualized. Organization and customizing data is data that is entered when setting the system, and is later rarely changed.
There are two additional data types USR and USR1 that the customers can use. These are intended for customer-own developments. The tables assigned to these data types are stored in a tablespace for customer developments.
Note:Please note that the data type only has an influence on storing the table for the database systems ORACLE and INFORMIX.
If this field is empty, then the value is respectively transferred from the table that is already saved. If the characteristic is new, meaning no saved tables yet exist, then data type APPL0 is used as default.
Size Category
Determining the expected space requirement of a table on the database.
You can choose category 0 to 4 for your table. With this, a certain fixed size for a storage of the database is assigned to a category. When creating a table, an blank space is reserved on the database for this; If it later needs more space, then the storage space is added correspondingly to the category chosen here.
Use F4 on the field Size category to see the number of data records, that can be maintained with the individual categories for your table without any complications arising (for example, for required reorganisations because the maximum space to be reserved for the table , due to the maintained size category, was overwritten).
If this field is empty, then the value is respectively transferred from the saved table that already exists. If the characteristic is new, meaning no saved tables yet exist, then category 0 is used as default.
Regs
Gopi.

Similar Messages

Regarding assigning Maintain DB-Storage Parameters

hai
i fotgot to assing the 'Maintain DB-Storage Parameters' for Transfer Structure.I already activated the TR.Then this option 'Maintain DB-Storage Parameters' is disabled.
So how can i enable that option for assing the DB-storage parameters.
pls tell me
i ll assing the points
bye
rizwan

hi Rizwan,
you may want take a look
http://help.sap.com/saphelp_nw2004s/helpdata/en/a7/214538821ae027e10000009b38f8cf/frameset.htm
hope this helps.

Maintain DB storage parameter

Hello,
is anyone familiar with the option for DSOs, Cubes etc. to maintain DB storage parameters?
I would be interested in the impact oof adjusting this option? What is technically happening, when changing these settings?
Thank You!
Goliad

HI,
The main reason for separating the table spaces is easy monitoring as u know which data is lying where moreover there are several other benefits also like u can take backup at individual table space level. This helps in trouble shooting also.
The separation of table spaces is database depended.
Regards
Ravish

Oracle Table Storage Parameters - a nice reading

bold Gony's reading excercise for 07/09/2009 bold -
The below is from the web source http://www.praetoriate.com/t_%20tuning_storage_parameters.htm. Very good material.The notes refers to figures and diagrams which cannot be seen below. But the text below is ver useful.
Let’s begin this chapter by introducing the relationship between object storage parameters and performance. Poor object performance within Oracle is experienced in several areas:
Slow inserts Insert operations run slowly and have excessive I/O. This happens when blocks on the freelist only have room for a few rows before Oracle is forced to grab another free block.
Slow selects Select statements have excessive I/O because of chained rows. This occurs when rows “chain” and fragment onto several data blocks, causing additional I/O to fetch the blocks.
Slow updates Update statements run very slowly with double the amount of I/O. This happens when update operations expand a VARCHAR or BLOB column and Oracle is forced to chain the row contents onto additional data blocks.
Slow deletes Large delete statements can run slowly and cause segment header contention. This happens when rows are deleted and Oracle must relink the data block onto the freelist for the table.
As we see, the storage parameters for Oracle tables and indexes can have an important effect on the performance of the database. Let’s begin our discussion of object tuning by reviewing the common storage parameters that affect Oracle performance.
The pctfree Storage Parameter
The purpose of pctfree is to tell Oracle when to remove a block from the object’s freelist. Since the Oracle default is pctfree=10, blocks remain on the freelist while they are less than 90 percent full. As shown in Figure 10-5, once an insert makes the block grow beyond 90 percent full, it is removed from the freelist, leaving 10 percent of the block for row expansion. Furthermore, the data block will remain off the freelist even after the space drops below 90 percent. Only after subsequent delete operations cause the space to fall below the pctused threshold of 40 percent will Oracle put the block back onto the freelist.
Figure 10-83: The pctfree threshold
The pctused Storage Parameter
The pctused parameter tells Oracle when to add a previously full block onto the freelist. As rows are deleted from a table, the database blocks become eligible to accept new rows. This happens when the amount of space in a database block falls below pctused, and a freelist relink operation is triggered, as shown in Figure 10-6.
Figure 10-84: The pctused threshold
For example, with pctused=60, all database blocks that have less than 60 percent will be on the freelist, as well as other blocks that dropped below pctused and have not yet grown to pctfree. Once a block deletes a row and becomes less than 60 percent full, the block goes back on the freelist. When rows are deleted, data blocks become available when a block’s free space drops below the value of pctused for the table, and Oracle relinks the data block onto the freelist chain. As the table has rows inserted into it, it will grow until the space on the block exceeds the threshold pctfree, at which time the block is unlinked from the freelist.
The freelists Storage Parameter
The freelists parameter tells Oracle how many segment header blocks to create for a table or index. Multiple freelists are used to prevent segment header contention when several tasks compete to INSERT, UPDATE, or DELETE from the table. The freelists parameter should be set to the maximum number of concurrent update operations.
Prior to Oracle8i, you must reorganize the table to change the freelists storage parameter. In Oracle8i, you can dynamically add freelists to any table or index with the alter table command. In Oracle8i, adding a freelist reserves a new block in the table to hold the control structures. To use this feature, you must set the compatible parameter to 8.1.6 or greater.
The freelist groups Storage Parameter for OPS
The freelist groups parameter is used in Oracle Parallel Server (Real Application Clusters). When multiple instances access a table, separate freelist groups are allocated in the segment header. The freelist groups parameter should be set the number of instances that access the table. For details on segment internals with multiple freelist groups, see Chapter 13.
NOTE: The variables are called pctfree and pctused in the create table and alter table syntax, but they are called PCT_FREE and PCT_USED in the dba_tables view in the Oracle dictionary. The programmer responsible for this mix-up was promoted to senior vice president in recognition of his contribution to the complexity of the Oracle software.
Summary of Storage Parameter Rules
The following rules govern the settings for the storage parameters freelists, freelist groups, pctfree, and pctused. As you know, the value of pctused and pctfree can easily be changed at any time with the alter table command, and the observant DBA should be able to develop a methodology for deciding the optimal settings for these parameters. For now, accept these rules, and we will be discussing them in detail later in this chapter.
There is a direct trade-off between effective space utilization and high performance, and the table storage parameters control this trade-off:
For efficient space reuse A high value for pctused will effectively reuse space on data blocks, but at the expense of additional I/O. A high pctused means that relatively full blocks are placed on the freelist. Hence, these blocks will be able to accept only a few rows before becoming full again, leading to more I/O.
For high performance A low value for pctused means that Oracle will not place a data block onto the freelist until it is nearly empty. The block will be able to accept many rows until it becomes full, thereby reducing I/O at insert time. Remember that it is always faster for Oracle to extend into new blocks than to reuse existing blocks. It takes fewer resources for Oracle to extend a table than to manage freelists.
While we will go into the justification for these rules later in this chapter, let’s review the general guidelines for setting of object storage parameters:
Always set pctused to allow enough room to accept a new row. We never want to have a free block that does not have enough room to accept a row. If we do, this will cause a slowdown since Oracle will attempt to read five “dead” free blocks before extending the table to get an empty block.
The presence of chained rows in a table means that pctfree is too low or that db_block_size is too small. In most cases within Oracle, RAW and LONG RAW columns make huge rows that exceed the maximum block size for Oracle, making chained rows unavoidable.
If a table has simultaneous insert SQL processes, it needs to have simultaneous delete processes. Running a single purge job will place all of the free blocks on only one freelist, and none of the other freelists will contain any free blocks from the purge.
The freelist parameter should be set to the high-water mark of updates to a table. For example, if the customer table has up to 20 end users performing insert operations at any time, the customer table should have freelists=20.
The freelist groups parameter should be set the number of Real Application Clusters instances (Oracle Parallel Server in Oracle8i) that access the table.

sb92075 wrote:
goni ,
Please let go of 20th century & join the rest or the world in the 21st century.
Information presented is obsoleted & can be ignored when using ASSM & ASSM is default with V10 & V11I said the same over here for the exactly same thread, not sure what the heck OP is upto?
Oracle Table Storage Parameters - a nice reading
regards
Aman....

Maintained the storage location in MRPview2

Hi,
Though I have maintained storage location in MRP view2, while reversing the document from m.type 103 to 105 system is asking storage location in GR, then entered the storage location in GR, even though system is not allowing to post the GR because system is giving error message saying that inbound delivery storage location can not be changed to here.
We don not want to maintain the storage location in PO and Inbound delivery
We are creating inbound delivery in VL31N against the PO, after that posting the GR with m.type 103 once that is complete then will reverse the document from m.type 103 to 105 while reversing the document we are facing the above said problems.
Appreciate for your effective action.

Hi,
You have two queries:
1.You entered your required storage location in material master ,MRP2 screen to have Default storage location for external procurement, so that when you enter plant while creating the PO, this SL will be written automatically.This storage location nothing to with GR, during GR you need to enter your storage location.
2.While reversing the document you are facing the problems.
The movement types 103 is used for Goods receipt for purchase order into GR blocked stock & 105 is used for Release from GR blocked stock for purchase order.
But as you are reversing the document use 104 movement type instead of 105.
Regards,
Biju K

(PCTFREE, PCTUSED) and Storage parameters

HI,
I am confused about (PCTFREE, PCTUSED) and Storage parameters(initial, next, pctincrease etc.)
As far as i have read PCTFREE and PCTUSED are used to control free and used space in a datablock and also these parameters related to Manual segment space management in Locally managed tablespace(i.e we need to manually set and tune these parameters). Whether these parameter are used in Dictionary managed tablespace or not?
Also, Storage parameters(intital, next, PCTUSED etc) are used in Dictionary managed tablespace. But in locally managed tablespaces how they are set as i have read we need not set these in locally managed tablespaces.
So, can you explain me about differences of these parameters with regard to Locally and Dictionary managed tablespaces in Oracle 9i and 10g platform on RHEL.

Hi,
Locally Managed Tablespace :-
A tablespace that can manage extent allocation by itself is called locally managed tablespace.
Using the bitmap in each datafile to keep track of the freed or used status of blocks in that datafile.
Each bit in the bitmap corresponds to a block or a group of blocks.
When an extent is allocated or freed for reuse, Oracle changes the bitmap values to show the new status of the blocks.
These changes do not generate rollback information because they do not update tables in the data dictionary.
Now remember, storage parameters
NEXT,
PCTINCREASE,
MINEXTENTS,
MAXEXTENTS, and
DEFAULT STORAGE are not valid for extents that are managed locally
Extents allocated in LMT :-
LMT have extent sizes either UNIFORM or variable extent sizes
For UNIFORM extents you can specify an extent size. The default size is 1MB.
and for AUTOALLOCATE extents you can specify the size of the initial extent and Oracle determines the optimal size of the additional extents, with a minimum extent size of 64KB
Example :-
Extent of uniform size
CREATE TABLESPACE test
DATAFILE 'tet.dbf'
EXTENT MANAGEMENT LOCAL
UNIFORM SIZE 256K;
Specifying Segment Space Management in Locally Managed Tablespaces
When you create a locally managed tablespace using the CREATE TABLESPACE statement, the SEGMENT SPACE MANAGEMENT clause allows you to specify how free and used space within a segment is to be managed.
MANUAL (MSSM) :- refers to oracle use free lists for managing free space within segments
because of the need to specify and tune the PCTUSED, FREELISTS, and FREELISTS GROUPS storage parameters for schema objects created in the tablespace
AUTO :-
Oracle use bitmaps to manage the free space within segments- automatic segment-space management
(ASSM)
Example :-
CREATE TABLESPACE lmtbsb DATAFILE '/u02/oracle/data/lmtbsb01.dbf' SIZE 50M
EXTENT MANAGEMENT LOCAL - LMT
SEGMENT SPACE MANAGEMENT AUTO; - ASSM
- DMT :-
Example :-
CREATE TABLESPACE tbsb
DATAFILE '/u02/oracle/data/tbsa01.dbf' SIZE 50M
EXTENT MANAGEMENT DICTIONARY -- specified how to manag the extent in DB
DEFAULT STORAGE (
INITIAL 50K
NEXT 50K
MINEXTENTS 2
MAXEXTENTS 50
PCTINCREASE 0); -- you have specified how extents in memory should increase
In the above example you have created dmt and specified the storage parameter for Extents, that is
how they much allocated as data get inserted in to the segments(tables) .
refer : http://www.mpi-inf.mpg.de/departments/d5/teaching/ss05/is05/oracle/server.920/a96521/tspaces.htm#636
- Pavan Kumar N
Oracle 9i/10g - OCP
http://oracleinternals.blogspot.com/

Create table with storage parameters in a locally managed tablespace

Hi,
Can we create object with storage parameters in a locally managed tablespace.
CREATE TABLE my_hash_table_6 (
name VARCHAR2(30),
value VARCHAR2(4000) )
STORAGE (
INITIAL 1M
NEXT 512K
PCTINCREASE 0
MINEXTENTS 2
MAXEXTENTS UNLIMITED )
users default tablespace is locallly managed.
Then this table's extent management will be managed as per the tablespace or as the storage parameters which
were specified at the time of table creation.

Why don't you try it yourself ?
TEST@db102 > select * from dba_tablespaces
2 where TABLESPACE_NAME='USERS';
TABLESPACE_NAME                BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
MAX_EXTENTS PCT_INCREASE MIN_EXTLEN STATUS    CONTENTS LOGGING   FOR EXTENT_MAN
ALLOCATIO PLU SEGMEN DEF_TAB_ RETENTION   BIG
USERS                                8192          65536                       1
2147483645                   65536 ONLINE    PERMANENT LOGGING   NO LOCAL
SYSTEM    NO AUTO   DISABLED NOT APPLY   NO
TEST@db102 > CREATE TABLE my_hash_table_6 (
2 name VARCHAR2(30),
3 value VARCHAR2(4000) )
4 STORAGE (
5 INITIAL 1M
6 NEXT 512K
7 PCTINCREASE 0
8 MINEXTENTS 2
9* MAXEXTENTS UNLIMITED )
TEST@db102 > /
Table created.
TEST@db102 > select * from user_segments
2 where segment_name='MY_HASH_TABLE_6';
SEGMENT_NAME
PARTITION_NAME                 SEGMENT_TYPE       TABLESPACE_NAME
     BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS BUFFER_
MY_HASH_TABLE_6
                               TABLE              USERS
   2097152        256          2        1572864                       1
2147483645                                         DEFAULT
TEST@db102 >

IMP - EXP and storage parameters

Hi All,
I am planning to import few tables from one database to another database using our good old import-export (even when I am on 10g).
Tables which I am importing do not exist in the target database. So, when I create them from the export dump, I think they will be created "with the same storage parameters (i.e. initial extent, next etc etc) as the source database". If I want import tables to take up the storage parameters of the target database/tablespace instead of the source, what is the way ??
Thanks in advance

Sabdar is right. Pre-defining the objects using the desired storage clause is the best way to do this.
If using locally managed tablespaces in the target database the tablespace parameters will override the next extent and pct_increase information on import but the initial extent setting will influence how many extents are allocated.
I suggest in either case: dictionary or locally managed target tablespaces that the export be made using compress=n. This will give you the best control over how much space the objects take on import.
HTH -- Mark D Powell --

Specifying storage parameters for indexes

Hi
Could be I'm blind or something, but....
When I create an index in SQL Dev: How do I specify storage parameters (e.g. tablespace) for that index?
:-)Roald

In the truth a visual way does not exist to make this.
Just with the command line, in the SQL Worksheet, as example below.
create index your_index on your_table (
index_column ASC
) tablespace your_tablespace
Bigger details on the parameters of storage can be gotten in link:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5010.htm#i2062403

Require Configuration Details regarding JDBC Sender Adapter Parameters

Hi All,
I have a scenario in which I need to read around 2 million records from an SQL Server table and process.
Since the data content is very huge, I have decided to split the data and execute.
So, in the select statement of my SQL Server Query, I used Select top(2000) from table name with my where condition.
In the update statenment, I used update tablename set my required values from (my select query written above).
QOS -> EOIO
I have given the queuename as my tablename
Poll Interval is "120" seconds.
My idea is to process 2000 records at a time.
When I am executing this interface through RWB, I am getting an error in update statement saying
The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Unable to start a nested transaction for OLE DB provider "SQLNCLI" for linked server (serverdetails). A nested transaction was required because the XACT_ABORT option was set to OFF.'. For details, contact your database server vendor."
I have also tried in advanced tab the name of the variable as XACT_ABORT and its value as "ON", but to no avail.
Please let me know if I have missed anything. Do I need to set any additional parameters in the advanced tab of JDBC sender communication channel?
Any help is highly appreciated.
Regards
Kiran.

HI Kiran
Fist of all suggestion is to increase the polling time. It may not process 2000 records in 120 second and you will poll again.
Paste your query to check if there is a problem
Also do check with SAP Note 831162 to verify if there is something you are doing wrong.
Thanks
Gaurav

Advise needed in regard to iCloud storage 5GB

Can anyone please advise me in regard to the iCloud storage of 5GB:
I have 2 devices using iCloud: iPad and iPhone.
iCloud has said to me it is almost full and I really am not sure why? I have deleted all music from the 2 devices, hoping this would free up a lot of space. But this did not seem to improve the space level very much.
I have on the devices: No music. A few apps. Alot of podcasts. No videos. 40 photos. Not many documents.
I have looked at the backups for the devices: iphone: 2.3GB and iPad 2.1GB. So, this explains to me what is causing the 'full' limit almost being reached.
So, I still would like to take my music with me when I travel. At the moment, in order to do this I have cancelled using iCloud on my iPad. But was this the right thing to do? Should I only have one device using iCloud?
Any advise would be appreciated. Thank you

Removing music from your devices won't remove it from iCloud. The music stays there in case you want to download it again.

Regarding maintaining session in flex

Hello,
I am developing a flex application which is using jsp for database connectivity. I am using HTTP request for connecting to jsp page and passing and retrieving parameters. Now I wanted to ask how can I maintain session in flex so that I can know which client has logged into the system and on the basis of that can assign privileges to the client. Is it possible in flex and how?Reply needed urgently.
Thanks in advance.

Hi a.bhavika,
There is not specifically any session management in Flex as it runs everything on the client side if at all you want to mainatain you can maintain it on the server side. ...and I think for your case I dont think you need any session managemenet as at the time of login only you can identify which user has logged in to the syetem and based on the user logged in you can load all the previleges of that particular user in the Flex application.
Check out the links below for your understanding...
http://www.forta.com/blog/index.cfm/2006/9/24/flex-and-session-state-management
http://www.assembla.com/wiki/show/romoz/Session_Management_in_Flex
Thanks,
Bhasker

Regard an error "Storage type & notsuitable as interface (SU mgmt is active

Hi All,
I am trying to do the inventory clearing in both warehouse and Inventory management using the transactions LI20 and LI21 after counting the inventory. But whenever I am trying to do the writeoff's I am facing with an error "Storage type & not suitable as an interface (SU management is active)"
I couldnt able to figure out the main cause for this error. Your valuable suggestions would be highly appreciated.
Regards,
Shane

Hi Jürgen L,
My objective is to do physical inventory and of ther are any differences then write them........in this sytem Both Grants and fund management is involved?
I am getting this message while I am doing LI21. And you have suggested that, the difference storage type SU managed. which is a 999 storage type. and this is not SU managed.
I would also like to ask regarding the clearing of differences in warehouse and Inventory mangement. I am using the mvmt types 711 and 712, But what account documents will get generated. I am thinking there will be no account documents that will get generated. Adding to this I am getting "Account 6701 requires an assignment to a CO object with Message no. KI235". If we do this assignment to this CO object......... doesnt the transaction go and hit the balance sheet account.
I am lil baffled with this whole process. If you could give me your valuable information, that will help me a lot.
Shane.

REGARDING MAINTAINING CODITION TAB IN SERVICE PUR. ORDER

Dear cons
In service p.o I entered service item in service tab . I didnot maintain condition tab in service P.o.But I saw condition type is available in condition tab automatically. what is the setting for this or it is happen by default in service P.O. pl. help me in this regard.
nrk

hi,
Check here:
SPRO >> MM > External serivce management >> Maintain conditions for services...here check for your settings...
Hope it helps..
Regards
Priyanka.P
Anything else revert back...

Regarding MI data storage in handheld device

Hi,
How does the file I/O manage the data on handheld when it becomes huge after continous usage and mulitple synchronizations.
I guess that MI currently creates a folder for every login and stores the data from WAS in the form .dat files.
As the handheld device has limited memory how is the memory management done.
Is it okay to delete the previous folders to reduce the memory storage.
Regards
Raja Sekhar

Hi Raja,
you should never delete any of the data that is stored in the MI persistence API by hand/with your own code. That will most likely break your MI installation.
I would always recommend to use DB2e instead of file I/O, especially if you have a large amount of data on a PDA. It is faster and you can turn on encryption.
Best Regards, alex
alexander ilg
http://www.juniverse.org

Regarding Maintain DB Storage Parameters

Similar Messages

Maybe you are looking for