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.........

Similar Messages

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

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.

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.........

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

Change DB storage parameter of existing info providers

Hello,
for better database monitoring reasons, it seems to be quite helpful to use the option change DB storage parameters for several infoproviders (some DSOs and Cubes) in the menu.
Now I found out, that it is only possible to use this option while creating new infoproviders. Is there also an option to change DB storage parameters of existing infoproviders?
With SE13 it is possible to change these parameters for the used tables e.g. active data of the DSO etc. But for me it that there might be a problem to change settings of generated tables.
Is there any other way to change the db storage parameters?
Thank You!
Goliad001

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

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

St22-storage parameter dump

Hi all,
We are continuously facing abap dump STORAGE_PARAMETERS_WRONG_SET.
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 972175952 bytes from the operating
system with 'malloc' when the operating system reported after a
further memory request that there was no more memory space
available.
Set the system profile parameters
-abap/heap_area_dia und
-abap/heap_area_nondia
to 972175952 maximum. For security, reduce the value by 10.000.000
Now shall i go ahead and change the parameter values and let me know the recommended
parameter values for my prod server as no issue arise in future.
Our System environment:
46C,oracle 10.2.0.2.0,win2003_64bit
Thanks in advance,
Kutty

Hi all,
And if i increase the parameter then from where it will take memory, is it from physical RAM memory or disc space?
And in RZ10 there is no
-abap/heap_area_dia
-abap/heap_area_nondia
Shall create and set the value. and pls correctly specify the value to set in both parameter.
available physical memory-12572236
free space - 4052444Kb
Kutty.
Edited by: prathapkutty on Aug 4, 2011 1:38 PM

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

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

Using Data Pump Storage Parameter option

I am creating database replica of our production environment - the db name don't have to be the same.
My option is to use Oracle data pump to move the data from source database to target database.
I performed the same schenerio for our Windows 2003 evnironment with no problem.
Doing the same for Linux, I am getting tablespace creation error as you can see below:
Lix
Linux-x86_64 Error: 2: No such file or directory Failing sql is: CREATE TABLESPACE "INQUIRY" DATAFILE '/oraappl/pca/vprod/vproddata/inquiry01.dbf' SIZE 629145600 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO ORA-39083: Object type TABLESPACE failed to create with error: ORA-01119: error in creating database file '/oraappl/pca/vprod/vproddata/medical01.dbf' ORA-27040: file create error, unable to create file
My question is do we have to create the tablespaces or data pump should use the default tablespace location already being used by the new database?

Hi Richard,
I am working creating my extra database using duplicate command as you suggested.
I got everything up until I got this error:
channel ORA_AUX_DISK_1: reading from backup piece /oraappl/pca/backups/weekly/vproddata/rman/VPR ackupset/2013_08_27/o1_mf_nnndf_TAG20130827T083750_91s7dz0r_.bkp ORA-19870: error reading backup piece /oraappl/pca/backups/weekly/vproddata/rman/VPROD/backupset 3_08_27/o1_mf_nnndf_TAG20130827T083750_91s7dz0r_.bkp ORA-19505: failed to identify file "/oraappl/pca/backups/weekly/vproddata/rman/VPROD/backupset/2 08_27/o1_mf_nnndf_TAG20130827T083750_91s7dz0r_.bkp" ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory
It is defaulting to the recovery location of the production database, instead of the auxiliary db.
My next option was to catalog the backup files, even that is not working. Any suggestion?

DB Storage parameter in DSO

Similar Messages

Maybe you are looking for