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

Similar Messages

DB Storage parameter in DSO

FOR DSO in BI 7.0
I wish to declare
DB Storage parameter (Active Records) data type            : DODS
DB Storage parameter (Active Records): size category     : 1
DB Storage parameter (Activation Queue): data type        : DODS
DB Storage parameter (Activation Queue): size category : 1          1
Can anyone help me out how i can do this.

Hi........
Check this :
http://help.sap.com/saphelp_nw04s/helpdata/en/a7/214538821ae027e10000009b38f8cf/frameset.htm
Re: Regarding Maintain DB Storage Parameters
Hope this helps......
Regards,
Debjani.........

DB Storage parameter (Active Records): data type

Hi i wish to declare DB Storage parameter (Active Records) data type as as DODS but iam unable to navigate to that options. can some one help me out.

Hi........
Check this :
http://help.sap.com/saphelp_nw04s/helpdata/en/a7/214538821ae027e10000009b38f8cf/frameset.htm
Re: Regarding Maintain DB Storage Parameters
Hope this helps......
Regards,
Debjani.........

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

Maintain settlement rule - parameter

Dear all ,
I Create new maintenance order type in system and creat a manual order through iw31 . but when we want realease the order system open one window name ''Maintain settlement rule - parameter''and asking for settelement profile.
please help me where i can maintain settlement rule in SPRO for system autometic settlement at the time of realease.
Raghav

Hi RS,
Go to -" spro>>>>>PM & CS>>>>>>>>Maintenance and service processing>>>>>>>Maintenance and service orders>>>>>Functions and settings for order types>>>>>>Settlement rule: Define time and creation of distribution rule
Execute
then
put "mandatory for release" and main order will be a settlement receiver" in settlement rule time and Distribution rule sub order field with corresponding to your order type.
After completing this configuration your settlement rule will automatically create for order
Thanks & Regards,
Rahul Pawar

How to DB Storage PArameter for DSO

Hi,
I want to change DB storage parameter - Data Type and Size Category for DSO. How to go about it or i need to have a ABAP program to do the same? Presently it is
DATA Type DODS and Size Category 6 but i need to change both of these. Changing option is grayed out. Please suggest me some way out !

Hi
Do u have data in the DSO?
You can change DB Storage and other settings only when the DSO is empty
Please check
Empty out your DSO and change the settings
Cheers

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

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.

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
PSAPR3E700 LOCAL UNIFORM AUTO
Message was edited by:
 Amit Jain

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 - PCTFREE & PCTUSED

My question is regarding storage parameter PCTFREE and PCTUSED. I have little bit confusion to determine PCTUSED calculation.
Suppose we set PCTFREE 20% and PCTUSED 50%. Initially, a block is empty, an INSERT fill free space 30% and after this UPDATE fill 20% reserved PCTFREE space.
My question is, the block will be available for new INSERT.
Thank

asif.maqbool wrote:
Thanks Aman for sending links. I read and understood. But I'd like to know the block availability. Do we consider filled PCTFREE space to calculate PCTUSED space?Are you sure that you read the link?
The block's availability is based on the PCTUSED marker (only in the Manual Segment Space Management). PCTFREE is going to be a reserved space for the subsequent updates.
This diagram should clear the concept.
http://docs.oracle.com/cd/E11882_01/server.112/e25789/logical.htm#BABHHIDA
My understanding is PCTUSED percentage only for new insert and the block is available until PCTUSED to reach specified percentage doesn't matter PCTFREE filled or not. A PCTFREE percentage is a separate space allocation in the block that we do not consider for PCTUSED space. If we set 20% PCTFREE and 50% PCTUSED so, we will use the over all 70% of a block space 20% for UPDATE and 50% for new INSERT.Wrong! Please read and re-read the given links.
I'd appreciate if you or anyone to correct my concept if there is something wrong.Though its not going to be of much use right now as you are not clear with the basic concepts , this link should help in knowing the idea behind calculation required to set the parameters(only for MSSM) ,
http://asktom.oracle.com/pls/asktom/f?p=100:11:::::P11_QUESTION_ID:733825532206
Aman....

Storage Parameter Settings for Cube

Hi , Thank alot for such a wonderful suggestions, We have 25 millions of records going to cube so for high load performance on cube Can you check and help me Data Base Storage Parameter Settings. can you tell if
Fact Table
1. Data Class for fact tables is DFACT or should i change to any other
2. Size 4 >150 MB or should i change to any other
Dimension Table
1. Data Class DDIM or should i change to any other
2. Size 0 <500 K or should i change to any other
Help me with this.
Thanks
Poonam Roy

Hi,
I don't think that we need to some extra settings at cube , if want to go with Acceletor.
I am not able give good info on it,because I have not yet worked on it. But if you spend some time to go through all the mentioed links,Definately You would not have any doubts on it.
Also refer the help link:
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/48c0417951d117e10000000a155106/frameset.htm
If you donot have chance to use acceletors, then I suggest you think about Data marts (no of cubes with same structures and with ssame datasource) which holds physically have different range of data.And then use a Multi provider upon it.
And also use Cache methodology for the reports built on these cubes.And use precalculattion to heat up the cache.
Also check the 1025307 note.
With rgds,
Anil Kumar Sharma .P
Message was edited by:
Anil Kumar Sharma
Message was edited by:
Anil Kumar Sharma

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.

Error: Maintain EDI-outbound parameter for partner MSG09

Hi Gurus,
I have encountered an error message while I am trying to trigger an output in Purchase order, this should in turn create a Sales Order automatically in our process.
I knew that for this we need to maintain the partner profile in WE20.
But still I am facing the same problem as explained above.
Can any one tell me where exactly we assign the EDI Message type to the Purchase order output type in IMG. (Please specify the IMG PATH for this)
Can this setting will help in solving this problem ?
Please advise how to get rid of this.
Thanks in advance.
Regards,
Venkat

Go to WE20 - Vendor.
After you click the Vendor, you can see the Message type on the right.
Enter into the message type - Message Control.
You have to enter the Application (EF) , Message type (output type from the PO ) and the Process code.
The error code because of the missing data in the Message Control.

Maintain DB storage parameter

Similar Messages

Maybe you are looking for