Parameters in schema(pe01)?

how do we access the parameters passed to the custom functions or custom rules like par1,par2,par3,par4 (ie embedded in the schema) at run time in the program?
regards
gunjan

PIT : Process Input Table...
Par1        nnnn        Personnel calculation rule
Par2        GEN         Generic access of personnel calculation rule (process any wagetype)
Par3         NOAB       Employee subgroup grouping personnel calculationfrom table employee group/employee subgroup (T503)
                                 without payroll type (Process for any EE sub-group groupings)...You can use if you have not
                                  differentiated employee subgroup groupings in a customer personnel calculation rule...
Plz go through it : [http://saphrexpert.blogspot.com/2008/09/schemas-and-personnel-calculation-rules.html]
Mohan

Similar Messages

Reg: Parameters In schema

Hi all,
In schema parameter 1 is for function, 2 is for gen, 4 is for noab. here my doubt is what is parameter 3 and what is the use of gen ,PIT gen with noab where these effect in process of log.let me know if any one knows
Thanks
Mrudula

PIT : Process Input Table...
Par1        nnnn        Personnel calculation rule
Par2        GEN         Generic access of personnel calculation rule (process any wagetype)
Par3         NOAB       Employee subgroup grouping personnel calculationfrom table employee group/employee subgroup (T503)
                                 without payroll type (Process for any EE sub-group groupings)...You can use if you have not
                                  differentiated employee subgroup groupings in a customer personnel calculation rule...
Plz go through it : [http://saphrexpert.blogspot.com/2008/09/schemas-and-personnel-calculation-rules.html]
Mohan

Removing schema prefix from DDL statements

When I do a change via sql developer, such as adding/dropping a field or table, etc... I need to send the change as a SQL script to my DBA (so it could be sent with our next upgrade to customers, etc).
But, the changes are always prefixed by the schema owner. How can I remove this? For example, if I add a field called: B to table: A, which is under schema O, the sql will look like this:
alter table O.A add (B);
I don't want the "O." to be in there by default. IMO, it is "stupid" for SQL Developer to do this.
My connection profile is to login as user "O".
I do see an option:
Preferences, Database, ObjectViewer Parameters: Show Schema
I un-check this box, because it does make one thing better: it makes it if I goto the "SQL" tab of a table i'm looking at, the sql to create the table won't have the schema prefix, which I think is the "correct" behaviour.
Is there anyway to "turn off schema prefix" for my "alters" ?

On the connections tab...
I expand TAbles
I highlight the table i want to add to.
I click Actions
I click Columns, Add
I proceed with entering the column via the GUI.
There's a tab called "SQL" that writes the SQL for whatever i'm doing. I want to be able to take this sql and send to my DBA, but I don't want it to be prefixed by the schema owner.

JDE Adapter Service Node parameter schema tabs are not visible

I have created a configuration for JDE Adapter & it is able to connect to JDE. But when i expand the service node, expect details tab nothing else is visible. I am not able to see Parameters Request Schema Response schema tabs.
Do i need to setup some classpath or some setup require in JDE server for this.
Thanks

I have the same problem.
Generate the wrappers :
The result are one package com.jdedwards.application.interop.jdejava_chrm with the java files and one JDEJAVA_CHRM.xml file.
I copy all to my repository directory /oracle/product/OracleAS1012/rep_test/
But on Application Explorer a see the services but can't see the tabs, i try to generate web-service but i receive an error "schema is missing for the component".
Did you had find the soluction ?
Thanks
Eliseu Cartaxo
http://www.itds.pt
Message was edited by:
[email protected]

(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/

ORA-00972: identifier is too long

Hi All,
I get the error ORA-00972: identifier is too long during installation of NW2004s SR2 Java system with DI. This error is seen on the step Perform post load activites. i have made the changes as suggested by SAP note: 314671. But the error still persists. Can anyone suggest what further more should be done here?
Oracle is unable to delete : OPS$<14 letter host name>\SAPSERVICESR3 and hence the error.
the output from ora_sql_results.log
=============================================================
2008-04-28, 19:04:56 SAPINST ORACLE start logging for
@@SAPDBA_ADDITIONAL.SQL
exit;
Output of SQL executing program:
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Apr 28 19:04:56 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Connected.
old   3:   :sSchemaUser := upper('&&1');
new   3:   :sSchemaUser := upper('SAPSR3DB');
old 19:   if upper('&&2') = 'NT' then
new 19:   if upper('NT') = 'NT' then
old 21:     :sDomain := upper('&&3');
new 21:     :sDomain := upper('[14 letter Host Name]\SIDadm');
old 32:   elsif upper('&&2') = 'UNIX' then
new 32:   elsif upper('NT') = 'UNIX' then
old 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('&&2'));
new 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('NT'));
using following Parameters:
. Schema User:                  SAPSR3DB
. Parametervalue os_authent_prefix:   OPS$
. OPS$SIDADM:                      OPS$[14 letter Host Name]\SIDADM
. SAP SID:                      SR3
. DB SID:                      SID
. R/3 Service User:                 OPS$[14 letter Host Name]\SAPSERVICESR3
. Computer or Domain:                 [14 letter Host Name]\SIDADM
old 119:   if upper('&&4') = 'SYN' then
new 119:   if upper('SYN') = 'SYN' then
old 137:   if upper('&&4') = 'SYN' then
new 137:   if upper('SYN') = 'SYN' then
create synonym: SAP_SDBAH SAPSR3DB.SDBAH
create synonym: SAP_SDBAH SAPSR3DB.SDBAD
unable to delete user: OPS$[14 letter Host Name]\SAPSERVICESR3
begin
ERROR at line 1:
ORA-00972: identifier is too long
ORA-06512: at line 46
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SAPINST: End of output of SQL executing program C:\oracle\product\10.2.0\db_1/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2008-04-28, 19:04:56 SAPINST ORACLE stop logging
Thanks in advance,
Arun E V

Hi Markus/Stefan,
Thanks for the quick answer. I know i am using a unsupported version, but that should not be a problem here. Though i have not run the installer from the script, still the DB is a successful installation and i have used it like this a few times.
Stefan, I have seen the note and made the required modification but still the issue persists. Is there anything more that i need to do apart from what is mentioned in the note?
The trouble is we are not in a position to change the host name as suggested and would prefer to continue with the same name.
Thanks,
Arun E V

JCO.Server appends null character to string

I am a complete SAP and JCO newbie so I'll try making as much since as I can, given the fact that I'm not familiar with SAP terminology and technology. I've been lent as a developer to another group which needs a legacy application rewritten. The application processes a RFC and decrypts the RFC encrypted payload and returns it along with a status code.
I have made progress - I'm able to register my server with the SAP runtime and using the SAP GUI application and the help of a SAP developer, I'm able to make an RFC call to my application. I'm able to read the parameters sent from SAP and write parameters back.
The problem is that one of the parameters I'm writing back (java.lang.String) appears to have and extra character on SAP side. On the GUI it appears as a '#' (pound) sign. The SAP developer told me the string is terminated with a null character which I know is a C/C++ thing but not a Java thing. I don't think it is a Unicode issue. The Java server is not running in Unicode mode and any attempt to set the jco.server.unicode property (I may have forgotten the exact name) to a value of 1 causes the RFC to fail.
I think the issue is likely to be the manner in which I defined the function parameters or the manner in which I write them. The following are code snippets:
Defining the function:
JCO.MetaData metadata = new JCO.MetaData(Constants.FUNCTION_DECRYPT);
metadata.addInfo(Constants.PARAMETER_SCHEME,      JCO.TYPE_INT,    255,   0, 0, JCO.IMPORT_PARAMETER, null);
metadata.addInfo(Constants.PARAMETER_ENCRYPTED,   JCO.TYPE_STRING, 255,   0, 0, JCO.IMPORT_PARAMETER, null);
metadata.addInfo(Constants.PARAMETER_DECRYPTED,   JCO.TYPE_STRING, 255,   0, 0, JCO.EXPORT_PARAMETER, null);
metadata.addInfo(Constants.PARAMETER_RETURN_CODE, JCO.TYPE_INT,    255,   0, 0, JCO.EXPORT_PARAMETER, null);
Server request handling code:
protected void handleRequest(JCO.Function function)
                // Obtaining import/export parameter lists.
                JCO.ParameterList input = function.getImportParameterList();
                JCO.ParameterList output = function.getExportParameterList();
                // Getting scheme and encrypted text parameters.
                int scheme       = input.getInt(Constants.PARAMETER_SCHEME);
                String encrypted = input.getString(Constants.PARAMETER_ENCRYPTED);
                // Decoding base 64 string.
                byte[] bytes = Base64.decode(encrypted);
                // Obtaining cipher by scheme and decrypting the text.
                AppCipher cipher = ApplicationConfiguration.getDecryptor(scheme);
                if(cipher == null)
                                logger.error("Unable to get cipher due to an unknown encryption scheme: " + scheme);
                else
                                byte[] decrypted = cipher.decrypt(bytes);
                                String plainText = new String(decrypted);
                                // Setting decrypted value information and return code.
                                output.setValue(plainText, Constants.PARAMETER_DECRYPTED);
                                output.setValue(Constants.RETURN_CODE_SUCCESS, Constants.PARAMETER_RETURN_CODE);

I seem to have made progress. If I define the parameter type as JCO.TYPE_CHAR instead of JCO.TYPE_STRING, it works:
metadata.addInfo(Constants.PARAMETER_DECRYPTED,   JCO.TYPE_CHAR,   255,   0, 0, JCO.EXPORT_PARAMETER, null);
That is the only change I made. I'm still setting the parameter value as java.lang.String. I hope this won't cause issues elsewhere. I was also able to change the field definition and set it as a byte array. However, that had the problem of having to define the exact length of the byte array in the field metadata otherwise the remaining bytes would appear as null bytes on SAP side.

Trying (and failing) to read XML multi-dimensional data array

i.e.
<mpp:Vehicle>
<mpp:Vehicle_Rgtrn_Ref>?</mpp:Vehicle_Rgtrn_Ref>
<mpp:Vehicle_Model_Code>?</mpp:Vehicle_Model_Code>
<mpp:DrivingRestrictionCode>?</mpp:DrivingRestrictionCode>
<mpp:Object_Mnfct_Year>?</mpp:Object_Mnfct_Year>
<mpp:Building_Number_const>1</mpp:Building_Number_const>
<mpp:Building_Name>The Slums</mpp:Building_Name>
<mpp:Sub_Building_Name>Flat 1</mpp:Sub_Building_Name>
<mpp:Postcode_Area_Ref>???? ???</mpp:Postcode_Area_Ref>
<mpp:Covers>
    <mpp:Cover>?</mpp:Cover>
    <mpp:Cover>?</mpp:Cover>
    <mpp:Cover>?</mpp:Cover>
</mpp:Covers>
</mpp:Vehicle>
<mpp:Vehicle>........
I'm currently trying to create a web service to read a SOAP message containing such XML. When reading the message, EDQ converts the singleton nodes in each Vehicle node group to a stringarray but only provides the last Cover node in each Vehicle in a stringarray. I'm not in control of the XML structure so trying to get the supplier to concatenate each vehicles covers into a delimited list within a single node may be a battle.
Anybody else ever encountered this? Is it possible or am I flogging a dead horse trying to achieve this.
Thanks in advance.
Jon

Hi Richard,
Thank you for your suggestion to my colleague Jon regarding -multi in option. As he said, w
hat we currently get when we have a SOAP message containing <Covers><Cover>A</Cover><Cover>B</Cover><Cover>C</Cover></Covers> is an EDQ stringarray containing the value {C}.
I've tried your suggestion
and ran the wsdlizer with the -multi in option but the wsdlizer fails with the following error:
H:\Workspaces\svn\edqTrunk\EDQ\WebServices\WSDL>java -jar wsdlizer.jar -o lv-mpp-query-request-ws.jar -multi in MPP_Query_Request_Service.wsdl
INFO: 10-Sep-2013 13:24:07: wsimport succeeded
Problem encountered during annotation processing;
see stacktrace below for more information.
com.datanomic.director.webservices.apt.ScannerException: multi-record request element must contain single nested list
com.datanomic.director.webservices.apt.Scanner$Processor$Servicer.makeDef(Scanner.java:747)
etc.
SEVERE: 10-Sep-2013 13:24:07: APT scan failed
Unfortunately, the error message is not very helpful to me. Do you know what it is whingeing about? I've also tried running the wsdlizer on our old wsdl files, i.e. before we introduced the parent tag <Covers> around <Cover>, but this failed with the same result when running with the -multi in option
The wsdl file, with most of the XML tags removed for clarity and brevity, looks like this:
<wsdl:definitions xmlns:schema="http://xxxx/MppService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://xxxx/MppService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="LV" targetNamespace="http://xxxx/MppService">
   <wsdl:types>
      <xsd:schema xmlns="http://xxxx/MppService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xxxx/MppService">
         <xsd:element name="request">
            <xsd:complexType>
               <xsd:sequence>
                  <xsd:element minOccurs="1" name="CorrelationUID" type="xsd:string"/>
                  <xsd:element minOccurs="1" name="RequestorName" type="xsd:string"/>
                  <xsd:element minOccurs="1" name="Brands" type="brandType"/>
                  <xsd:element minOccurs="1" name="Parties" type="partiesType"/>
                  <xsd:element minOccurs="1" name="InsuredObjects" type="insuredObjectsType"/>
               </xsd:sequence>
            </xsd:complexType>
         </xsd:element>
         <xsd:element name="response">
            <xsd:complexType>
               <xsd:sequence>
                  <xsd:element name="CorrelationUID" type="xsd:string"/>
                  <xsd:element name="MPPResponseUID" type="xsd:string"/>
                  <xsd:element maxOccurs="unbounded" minOccurs="1" name="Brand" type="schema:brandsType"/>
               </xsd:sequence>
            </xsd:complexType>
         </xsd:element>
         <xsd:complexType name="brandsType">
            <xsd:sequence>
               <xsd:element name="BrandCode" type="xsd:string"/>
               <xsd:element name="ResponseMPD">
                  <xsd:complexType>
                     <xsd:sequence>
                        <xsd:element minOccurs="0" name="FunctionAvailable" type="xsd:string"/>
                        <xsd:element minOccurs="0" name="MessageCode" type="xsd:string"/>
                     </xsd:sequence>
                  </xsd:complexType>
               </xsd:element>
               <xsd:element name="ResponseCI">
                  <xsd:complexType>
                     <xsd:sequence>
                        <xsd:element minOccurs="0" name="FunctionAvailable" type="xsd:string"/>
                        <xsd:element minOccurs="0" name="MessageCode" type="xsd:string"/>
                     </xsd:sequence>
                  </xsd:complexType>
               </xsd:element>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="brandType">
            <xsd:sequence>
               <xsd:element maxOccurs="2" minOccurs="1" name="BrandCode" type="xsd:string"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="partiesType">
            <xsd:sequence>
               <xsd:element maxOccurs="unbounded" minOccurs="1" name="Party" type="schema:partyType"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="partyType">
            <xsd:sequence>
               <xsd:element minOccurs="0" name="PartyUID" type="xsd:string"/>
               <xsd:element minOccurs="1" name="RoleCode" type="xsd:string"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="insuredObjectsType">
            <xsd:sequence>
               <xsd:element maxOccurs="1" minOccurs="0" name="Properties" type="schema:propertiesType"/>
               <xsd:element maxOccurs="1" minOccurs="0" name="Vehicles" type="schema:vehiclesType"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="propertiesType">
            <xsd:sequence>
               <xsd:element maxOccurs="unbounded" minOccurs="0" name="Property" type="schema:propertyType"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="vehiclesType">
            <xsd:sequence>
               <xsd:element maxOccurs="unbounded" minOccurs="0" name="Vehicle" type="schema:vehicleType"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="propertyType">
            <xsd:sequence>
               <xsd:element minOccurs="0" name="BuildingNumber" type="xsd:string"/>
               <xsd:element minOccurs="0" name="BuildingName" type="xsd:string"/>
               <xsd:element maxOccurs="1" minOccurs="0" name="Covers" type="schema:coversType"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="coversType">
            <xsd:sequence>
               <xsd:element minOccurs="1" name="Cover" type="xsd:string"/>
            </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="vehicleType">
            <xsd:sequence>
               <xsd:element minOccurs="0" name="VehicleRegistrationMark" type="xsd:string"/>
               <xsd:element minOccurs="1" name="ABIBrokernetCode" type="xsd:string"/>
            </xsd:sequence>
         </xsd:complexType>
      </xsd:schema>
   </wsdl:types>
   <wsdl:message name="request">
      <wsdl:part name="parameters" element="schema:request"/>
   </wsdl:message>
   <wsdl:message name="response">
      <wsdl:part name="parameters" element="schema:response"/>
   </wsdl:message>
   <wsdl:portType name="LVEI">
      <wsdl:documentation>Operations</wsdl:documentation>
      <wsdl:operation name="process">
         <wsdl:documentation>Process a query request</wsdl:documentation>
         <wsdl:input message="schema:request"/>
         <wsdl:output message="schema:response"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="LVBinding" type="tns:LVEI">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="process">
         <soap:operation soapAction="http://xxxx/MppService"/>
         <wsdl:input>
            <soap:body use="encoded"/>
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="LV-MPPQRS-v01">
      <wsdl:port name="LVEndpoint" binding="tns:LVBinding">
         <soap:address location="https://xxxx/LV-MPPQRS-v01"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>
A colleague created the wsdl, it's been checked a number of times but no one can find anything dodgy that might account for the wsdlizer error we're getting. So we're a bit lost now, the data coming in to our EDQ process is incomplete, which makes further development of out EDQ processes somewhat challenging.
Any help would be greatly received. Also happy to send any more information you may require.
Jules

Error in portal installation

Hi all,
I'm getting the following errors while installing Portal 7.0 with AS Java(NW2004s SR1).
ERROR 2008-04-20 10:40:00
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: Executable E:\oracle\TNS\102/bin/sqlplus returns 972..<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
ERROR 2008-04-20 10:40:00
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2008-04-20 10:40:00
FCO-00011 The step runSapdbaAdditionalSql with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_ORA|ind|ind|ind|ind|0|0|runSapdbaAdditionalSql was executed with status ERROR .
Please help me to resolve these problems.
Thanks in advance,
Ganpati Jha

Hi all,
Here, I'm pasting the complete log,
2008-04-20, 11:42:26 SAPINST ORACLE start logging for
@@SAPDBA_ADDITIONAL.SQL
exit;
Output of SQL executing program:
SQL*Plus: Release 10.2.0.2.0 - Production on Sun Apr 20 11:42:26 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Connected.
old   3:   :sSchemaUser := upper('&&1');
new   3:   :sSchemaUser := upper('SAPSR3DB');
old 19:   if upper('&&2') = 'NT' then
new 19:   if upper('NT') = 'NT' then
old 21:     :sDomain := upper('&&3');
new 21:     :sDomain := upper('administrator\tnsadm');
old 32:   elsif upper('&&2') = 'UNIX' then
new 32:   elsif upper('NT') = 'UNIX' then
old 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('&&2'));
new 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('NT'));
using following Parameters:
. Schema User:                  SAPSR3DB
. Parametervalue os_authent_prefix:   OPS$
. OPS$SIDADM:                      OPS$ADMINISTRATOR\TNSADM
. SAP SID:                      SR3
. DB SID:                      TNS
. R/3 Service User:                 OPS$ADMINISTRATOR\SAPSERVICESR3
. Computer or Domain:                 ADMINISTRATOR\TNSADM
old 119:   if upper('&&4') = 'SYN' then
new 119:   if upper('NOSYN') = 'SYN' then
old 137:   if upper('&&4') = 'SYN' then
new 137:   if upper('NOSYN') = 'SYN' then
unable to delete user: OPS$ADMINISTRATOR\SAPSERVICESR3
begin
ERROR at line 1:
ORA-00972: identifier is too long
ORA-06512: at line 46
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SAPINST: End of output of SQL executing program E:\oracle\TNS\102/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2008-04-20, 11:42:26 SAPINST ORACLE stop logging
If anybody is having any idea on this, then please help me out to resolve this problem.
Thanks in advance,
Ganpati Jha

Corporate Online Training For Oracle DBA @ Suninfosysinc Software Solutions

SUN INFOSYS SOFTWARE SOLUTIONS
Sun Infosys is a leading software solutions provider based out of Highland Park , New Jersey and serving clients across North America . Sun Infosys' dedicated information technology professionals are committed to meeting your company's information technology needs. Our allegiance to this goal and our high quality service guarantees our client's success.
Sun Infosys empowers the exchange, execution and integration of software consultancy projects with a strong edge for human resource management. By building strategic alliances with world-class companies, Sun Infosys serves a plethora of multinational businesses.
ORACLE 10g DBA COURSE CONTENTS
●     Introduction
●     Course Objectives
●     Suggested Schedule
●     Lesson Objectives
●     Oracle Products and Services
●     Oracle Database g: Stands for Grid
●     Oracle Database Architecture
●     Database Structures
●     Oracle Memory Structures
●     Process Structures
●     Oracle Instance Management
●     Server Process and Database Buffer Cache
●     Physical Database Structure
●     Tablespaces and Data Files
●     SYSTEM and SYSAUX Tablespaces
●     Segments, Extents, and Blocks
●     Logical and Physical Database Structures
●     Course Examples: The HR Schema
●     Database Architecture: Summary of Structural Components
●     Installing the Oracle Database Software
●     Tasks of an Oracle Database Administrator
●     Tools Used to Administer an Oracle Database
●     Installation: System Requirements
●     Checking the System Requirements
●     Optimal Flexible Architecture (OFA)
●     Using Optimal Flexible Architecture
●     Setting Environment Variables
●     Oracle Universal Installer (OUI)
●     Installing the Oracle Software
●     Database Configuration Options
●     Executing Configuration Scripts
●     Completing Your Installation
●     Advanced Installation Options
●     Installation Option: Silent Mode
●     Practice Overview: Installing the Oracle Software
●     Creating an Oracle Database
●     Planning the Database
●     Databases: Examples
●     Database Configuration Assistant (DBCA)
●     Using the DBCA to Create a Database
●     Password Management
●     Creating a Database Design Template
●     Using the DBCA to Delete a Database
●     Summary
●     Practice Overview: Using the DBCA
●     Managing the Oracle Instance
●     Management Framework
●     Starting and Stopping Database Control
●     Oracle Enterprise Manager
●     Accessing Oracle Enterprise Manager Database Home Page
●     Using SQL*Plus and iSQL*Plus to Access Your Database
●     Using iSQL*Plus
●     Setting Up iSQL*Plus for SYSDBA and SYSOPER Access
●     Using SQL*Plus
●     Calling SQL*Plus from a Shell Script
●     Calling a SQL Script from SQL*Plus
●     Initialization Parameter Files
●     Simplified Initialization Parameters
●     Database Startup and Shutdown
●     Starting Up an Oracle Database Instance
●     Starting Up an Oracle Database Instance: NOMOUNT
●     Starting Up an Oracle Database Instance: MOUNT
●     Starting Up an Oracle Database Instance: OPEN
●     Shutting Down an Oracle Database Instance
●     Shutdown Modes
●     SHUTDOWN Options
●     Using SQL*Plus to Start Up and Shut Down
●     Viewing the Alert Log
●     Viewing the Alert History
●     Dynamic Performance Views
●     Dynamic Performance Views: Usage Examples
●     Dynamic Performance Views: Considerations
●     Summary
●     Practice Overview: Managing the Oracle Instance
●     Managing Database Storage Structures
●     Storage Structures
●     How Table Data Is Stored
●     Anatomy of a Database Block
●     Tablespaces and Data Files
●     Oracle Managed Files (OMF)
●     Space Management in Tablespaces
●     Exploring the Storage Structure
●     Creating a New Tablespace
●     Storage for Locally Managed Tablespaces
●     Tablespaces in the Preconfigured Database
●     Altering a Tablespace
●     Actions with Tablespaces
●     Dropping Tablespaces
●     Viewing Tablespace Information
●     Gathering Storage Information
●     Viewing Tablespace Contents
●     Enlarging the Database
●     What Is Automatic Storage Management?
●     ASM: Key Features and Benefits
●     ASM: Concepts
●     Summary
●     Practice Overview: Managing Database Storage Structures
●     Administering User Security
●     Database User Accounts
●     Predefined Accounts: SYS and SYSTEM
●     Creating a User
●     Authenticating Users
●     Administrator Authentication
●     Unlocking a User Account and Resetting the Password
●     Privileges
●     System Privileges
●     Object Privileges
●     Revoking System Privileges with ADMIN OPTION
●     Revoking Object Privileges with GRANT OPTION
●     Benefits of Roles
●     Assigning Privileges to Roles and Roles to Users
●     Predefined Roles
●     Creating a Role
●     Secure Roles
●     Assigning Roles to Users
●     Profiles and Users
●     Implementing Password Security Features
●     Creating a Password Profile
●     Supplied Password Verification Function: VERIFY_FUNCTION
●     Viewing and Modifying Initialization Parameters
●     Managing Schema Objects
●     What Is a Schema?
●     Accessing Schema Objects
●     Naming Database Objects
●     Specifying Data Types in Tables
●     Creating and Modifying Tables
●     Understanding Data Integrity
●     Defining Constraints
●     Constraint Violations
●     Constraint States
●     Constraint Checking
●     Creating Constraints with SQL: Examples
●     Viewing the Columns in a Table
●     Viewing the Contents of a Table
●     Actions with Tables
●     Dropping a Table
●     Truncating a Table
●     Indexes
●     Types of Indexes
●     BTree Index
●     Bitmap Indexes
●     Index Options
●     Creating Indexes
●     What Is a View?
●     Creating Views
●     Sequences
●     Creating a Sequence
●     Using a Sequence
●     Temporary Tables
●     Temporary Tables: Considerations
●     Data Dictionary: Overview
●     Data Dictionary Views
●     Data Dictionary: Usage Examples
●     Summary
●     Practice Overview: Administering Schema Objects
Managing Data and Concurrency
●     Performance Management
●     Performance Monitoring
●     Performance Monitoring: Top Sessions
●     Performance Monitoring: Top Services
●     SQL Tuning Advisor: Overview
●     SQL Tuning Advisor Options and Recommendations
●     Using the SQL Tuning Advisor
●     Using the SQL Tuning Advisor: Example
●     SQL Tuning Advisor: SQL Statistics
●     SQL Tuning Advisor: Identifying Duplicate SQL
●     Using the SQL Access Advisor
●     Managing Memory Components
●     Enabling Automatic Shared Memory Management (ASMM)
●     Manually Setting Shared Memory Management
●     Using the Memory Advisor
●     Dynamic Performance Statistics
●     Troubleshooting and Tuning Views
●     Invalid and Unusable Objects
●     Summary
●     Practice Overview: Monitoring and Improving Performance
●     Backup and Recovery Concepts
●     Part of Your Job
●     Categories of Failures
●     Statement Failure
●     User Process Failure
●     Network Failure
●     User Error
●     Instance Failure
●     Background Processes and Recovery: Checkpoint (CKPT)
●     Background Processes and Recovery: Redo Log Files and LogWriter
●     Background Processes and Recovery: Archiver (ARCn)
●     Instance Recovery
●     Phases of Instance Recovery
●     Tuning Instance Recovery
●     Using the MTTR Advisor
●     Media Failure
●     Configuring for Recoverability
●     Control Files
●     Redo Log Files
●     Multiplexing the Redo Log
●     Archive Log Files
●     Archive Log File: Naming and Destinations
●     ARCHIVELOG Mode
●     Summary
Practice Overview: Configuring for Recoverability
○     Performing Database Backups
○     Backup Solutions: Overview
○     Oracle Secure Backup
○     User Managed Backup
○     Terminology
○     Recovery Manager (RMAN)
○     Configuring Backup Settings
Sun Infosys Software Solutions Offering Courses:
     Oracle 10g / 11g DBA
     SQL , PL/SQL
     Linux Administration
     Oracle OCA DBA
     Unix/Linux + Shell Scripting
Phone: +001-732-675-7911 (U.S.A)
E-mail : [email protected]
Website: www.suninfosysinc.com

I'll remember that company name to ensure that I neither use it nor recommend it.
John.

Authorization based on Item Name

I have a requirement to allow a user administrator to define which menu tabs & pages are available to each user group. So... I can't hard code the authorization scheme at design time for each item.
I've setup a form and table where the admin can link items to groups based on the item name. I can write a parameterized Authorization Scheme query to see if the item is available to the user's group - IF.. I can pass the item name as a variable.
How can I make the item name available to the Authorization Scheme as a variable in a parameterized query? Or, can you think of another way to meet the spec?
thanks,
Mark

I'm an eternal optimist (with a poor memory... ;o )
I wish there were more/better/documented hooks intoI agree but this specific case is not about documentation, the product currently just doesn't support what you are looking for.
The Apex team does seem to acknowledge that this would be a "desirable enhancement" as evidenced by Scott's comment in that thread
We do have plans to externalize authorization controls to facilitate this kind of thing, it's just a question of resources for us

Question: 9i- 10g

Hi all,
What does anyone know or have an opinion regarding 10g's ability with Virtual Private Databases/Row level security and Unix based servers providing client-server forms and reports services to browser based windows and unix clients?
My organisation has been stuck in Forms 6 land because of heavy limitations of Forms 9's ability to handle row level security in this situation and I was curious to know if anyone has upgraded to 10g and resolved any issues in that regards.
Thanks all.

This is another article:
TECHNOLOGY: Security
Keeping Information Private with VPD
By Arup Nanda
Oracle's row-level security gives users their own virtual private databases.
Ensuring appropriate information privacy is a pressing concern for many businesses today, given privacy legislation such as the United States' HIPAA (Health Insurance Portability and Accountability Act), Gramm-Leach-Bliley Act, Sarbanes-Oxley Act, and the EU's Safe Harbour Law. Other privacy mandates, such as Visa's Cardholder Information Security Program (CISP), also require businesses to ensure that access to information is tightly controlled.
Oracle has always included the ability to grant (or deny) users access to database objects, but these privileges are defined at the object levelfor an entire table, not for specific rows in that table. Although that approach is sufficient for many applications, any application touching on financial, health, or other kinds of personal information usually requires more-discrete controls over access and authorization.
Oracle's row-level security (RLS) feature, introduced in Oracle8i, provides fine-grained access controlfine-grained means at the individual row level. Rather than opening up an entire table to any individual user who has any privileges on the table, row-level security restricts access to specific rows in a table. The result is that any individual user sees a completely different set of dataonly the data that person is authorized to seeso the overall capabilities are sometimes referred to as Oracle's virtual private database, or VPD, feature.
Using Oracle's VPD capabilities not only ensures that companies can build secure databases to adhere to privacy policies but also provides a more manageable approach to application development, because although the VPD-based policies restrict access to the database tables, they can be easily changed when necessary, without requiring modifications to application code.
For example, say a bank's account managers (AMs) provide personal customer support to high-net-worth account holders. AMs use a custom banking application to help them check their customers' balances, deposit or withdraw funds, and decide on loan requirements, for example. At one time, the bank's policy was to allow all AMs to access all account holder information, but that policy was recently changed. Now, AMs are assigned to a particular set of customers, and they need to be able to access information pertaining only to those customers. The policy change needs to be reflected in the application, which currently shows all customer information to each AM, not just information on the customers to whom each particular AM is assigned.
To make the application comply with the new privacy policy, the bank has three choices:
Modify the application code to include a predicate (a WHERE clause) for all SQL statements. This option doesn't ensure privacy policy enforcement outside the application, however, and if there are other changes in the future, the code will once again have to be modified, so this is not a good approach in the long term.
Leave the application intact, creating views with the necessary predicates and creating synonyms with the same name as the table names for these views. This option is better from the perspective of application changes and security, but it can be difficult to administer, because of the potentially large number of views to track and manage.
Create a VPD for each of the AMs by creating policy functions that generate dynamic predicates, which can then be applied across all objects, regardless of how they are accessed, by setting up policies with the row-level-security built-in package (DBMS_RLS).
This last option offers the best security without administrative overhead and ensures complete privacy of informationall the account managers see a different view of the table, according to their own credentials.
This article shows you how to set up a VPD security model. It goes through the process by using the foregoing bank scenario to create policy functions, define policies, and then test results. (Note that the tables are not completely defined, to keep the example simple.)
Basic Setup for the Example Application
Briefly, here are the basic assumptions about the example bank application:
A BANK schema owns two key tables that make up the applicationa CUSTOMERS table:
Name Null? Type
CUST_ID NOT NULL NUMBER
CUST_NAME NOT NULL VARCHAR2(20)
and an ACCOUNTS table:
Name Null? Type
ACCT_NO NOT NULL NUMBER
CUST_ID NOT NULL NUMBER
BALANCE NUMBER(15,2)
Listing 1 comprises the SQL script for creating and populating these two basic example tables.
User SECMAN (security manager) owns an ACCESS_POLICY table that identifies the AMs and their respective customer accounts:
Name Null? Type
AM_NAME NOT NULL VARCHAR2(20)
CUST_ID NOT NULL NUMBER
ACCESS_TYPE NOT NULL CHAR(1)
The AM_NAME column stores the user ID of the account manager; CUST_ID identifies the customer; and ACCESS_TYPE defines the specific access entitlementS (SELECT), I (INSERT), D (DELETE), or U (UPDATE). Some example records from the ACCESS_POLICY table follow:
AM_NAME CUST_ID ACCESS_TYPE
SCOTT 123 S
SCOTT 123 I
SCOTT 123 D
SCOTT 123 U
SCOTT 456 S
SCOTT 789 S
LARA 456 I
LARA 456 D
LARA 456 U
LARA 456 S
As you can see, SCOTT, the AM for customer 123, has all privilegesS, I, D, and Uas does LARA for customer 456. Also, because SCOTT can confirm account balances for one customer of LARA, he has S privileges on customer 456.
Step 1. Create a Policy Function
The bank's access rules (contained in the ACCESS_POLICY table) must be applied somehow, dynamically, whenever an AM tries to look into customer account information. The first step is to create a policy function that returns the appropriate predicate to be applied to the table. As with the ACCESS_POLICY table, the policy functions are created and controlled by user SECMAN, for security purposes. It's best to keep privacy rules separate from the tables to which they apply.
Let's examine the policy function, get_sel_cust_idshown in Listing 2 in detail:
Accepts exactly two parameters: the schema name (p_schema in varchar2) and the table name (p_table in varchar2)
Returns one value only, a stringreturn varchar2 as l_retstr varchar2(2000);comprising the predicate that will be appended to every query on the table
Uses a cursor routinefor cust_ rec into get the list of values, because each user may have several cust_ids listed in the table
Returns a constructed stringl_retstrto be used as a predicate whenever any user attempts to access the underlying table
The function returns the predicate where cust_id in with the appended list of customer accounts (cust_id), separated by commas, that the user (am_name = USER) is allowed to see.
Note that before entering the loop that builds the list of cust_ids for the user, the code in Listing 2 checks to see if the user is the table owner BANK, in which case the function returns a NULL predicate, as follows:
if (p_schema = user) then
1_retstr := null;
After building this function, you want to make sure it returns the appropriate predicate, by testing some sample data. Connect to the database as SECMAN, and insert some records into the ACCESS_POLICY table, giving SECMAN read privileges on a few sample accounts, as follows:
insert into access_policy values ('SECMAN',123,'S');
insert into access_policy values ('SECMAN',456,'S');
insert into access_policy values ('SECMAN',789,'S');
Now execute the function:
select get_sel_cust_id
('BANK','CUSTOMERS') from dual;
The function returns a string that will be applied as a predicate, as shown in the following sample output:
GET_SEL_CUST_ID('BANK','CUSTOMERS')
CUST_ID IN (123,456,789)
You need to create similar functions for the other types of access. For simplicity's sake, create a single function for all the other access typesUPDATE, DELETE, INSERTas shown in Listing 3. However, note that for a real-world application, each type of access should have its own individual function defined, to ensure appropriate privacy.
The policy function in Listing 3 is nearly identical to the policy function in Listing 2, except that the predicate is further qualified by use of the information from the ACCESS_CONTROL table:
and access_type in ('I', 'U', 'D')
Creating a policy function is just the first step. You now need to ensure that the function will be used, by defining the policy that should control its use in your system.
Step 2. Define a Policy
Policies are defined with the DBMS_RLS package, which is Oracle-supplied. Be aware that the policies themselves are not database objects owned by any user (schema); they are logical constructs. Any user who has the execute privilege on the DBMS_RLS package can modify or drop a policy created by another user. Privileges to DBMS_RLS should be judiciously controlled and granted with caution.
In the following example, user SECMAN is granted execute privileges (by SYS) on the DBMS_RLS package:
grant execute on dbms_rls to secman;
Listing 4 creates a policy named CUST_SEL_POLICY on the table CUSTOMERS of schema BANK. This policy applies the predicate returned by the function GET_SEL_CUST_ID (which is shown in Listing 2) owned by schema SECMAN to all SELECT statements on the table.
Similarly, you place another policy on the table for other access types, as shown in Listing 5. This policy applies to inserts, updates, and deletes in the CUSTOMERS table.
It is almost identical to the SELECT policy, except that this policy includes a check that ensures that the policy will remain compliant even after an update:
update_check => TRUE
Data cannot be added to the table unless it adheres to the policy.
Step 3. Test the Setup
Now that the building blocks are in place, let's see how they work. Connecting as user BANK and issuing a simple select * from customers; query displays the following:
CUST_ID CUST_NAME
123 Jay Kulkarni
456 Wim Patel
These two records are the full contents of the CUSTOMERS table, and both records are shown because BANK owns the table, so the predicate clause is NULLthat is, no predicate is applied. However, when user LARA makes the same query, she sees the following:
select * from customers;
CUST_ID CUST_NAME
456 WIM PATEL
LARA sees only CUST_ID 456, not 123, because that is the row she is authorized to see, as determined by the ACCESS_ POLICY table. Note that the query has no WHERE clause but that the selection from the table is automatically filtered to show only the authorized rows.
If user SCOTT makes the same query, his results are different from the results for LARA: select * from customers;
CUST_ID CUST_NAME
123 Jay Kulkarni
456 Wim Patel
User SCOTT sees both rows, because he is authorized to do so, as shown in the ACCESS_POLICY table. When user LARA issues the query, the policy function get_sel_cust_id returns the predicate where cust_id in (456). Lara's original query select * from customers is rewritten as
select * from
(select * from customers)
where cust_id in (456)
The predicate is automatically appended to the user's original query. The same thing happens when the user updates the table:
SQL> update bank.customers
2 set cust_name = 'PAT TERRY';
1 row updated.
Note that in this example, only one row is updated, even though there are actually two rows in the underlying table. The policy (CUST_IUD_POLICY) appends the predicate where cust_id in (456) to the update statement. Similarly, while the table is being deleted, only the rows for which the user is authorized are deleted.
Attempting to insert a row containing data for which the user is not authorized results in an error message. For example, in this query, LARA is attempting to add a record to the CUSTOMER table for an account not under her purview: Next Steps
READ more about
VPD Oracle9i Supplied PL/SQL Packages and Types Reference
Oracle Privacy Security Auditing
SQL> insert into bank.customers
2 values (789,'KIM PARK');
insert into bank.customers
ERROR at line 1:
ORA-28115: policy with check option
violation
According to the ACCESS_POLICY table, Scott has SELECT privileges on account 789no other privileges for any other AM are listed in the table.
Using policies in conjunction with functions ensures authorized access to specific records of a table. The rules are applied regardless of how the table is accessed, whether through an application or directly through an ad hoc query tool, such as SQL*Plus. Users see only rows for which they have been authorized.
Policies can be applied to multiple tables, and a single policy function can be used by any number of policies. Listing 6 shows a policy on an ACCOUNTS table that uses the get_sel_cust_id function initially created for use with the CUSTOMERS table.
Arup Nanda ([email protected]) is the chief database architect at Proligence Solutions ( Printer View
http://otn.oracle.com/oramag/oracle/04-mar/o24tech_security.html
Joel Pérez
http://otn.oracle.com/experts

How to install & Configure Work Flow for OWB

Hi All,
I have installed companion products and now to configure work flow, what schema name should I have to give.
Can anybody tell me please.
Thanks,
Siva

Hi Siva,
If you are going to use workflow only for OWB , then what ever you have done is enough .
Using the Companion CD launch the UI and from the installation options Choose the following option "Oracle Database 10g Companion Product” Installation Type (Install into new Home)
This option will install the HTTP-Server
This option will create the default DAD for workflow
1 In the Middle Tier Configuration screen enter the required parameters
Workflow Schema: Schema Name
DB Host: DB Hostname
Port Number: DB Port on Host
Oracle SID: Database SID
2. Enter the Password for your oracle Workflow Database Account
3. This installation should have created the default DAD "/pls/wf" for you. It is required to restart the HTTP Server using the commands
$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/opmn/bin/opmnctl startall
Where ORACLE_HOME is the HTTP Server home
4. Now you can access the Workflow Home Page
Thanks,
Sutirtha

To check fact and dim table sizes in RSRV

Hi guys,
i hve access to only RSRV on prod so how do i check the fact and dim table ratios what is the test that i have to use to find....
Thanks,
Your help will be greatly appreciated

Hi,
I guess you can try the following options available in RSRV ->All Elementary texts -> Database ->
Database Statistics for an InfoCube and Its Aggregates
Database Information about InfoProvider Tables
Databank Parameters of *-Schema Tables for InfoCube
Check this help link:
[http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm]
hope this helps U...
Regards,
NR

PCTFREE and PCTUSED

hai !!!
I want to improve insertion and retriving performance of a table !'
* Could i achieve this by changing PCTFREE and PCTUSED values ?
* If so, what values do i need to put ?
- my table contains lakhs of records.
- involves continuos insertion of records.
- Updation is a rare.
- iam using Oracle 10g, data_block_size=8kb, OS : windows-7
* What about change in block size ?
- Do i need to increase it ? or decrease it ?

Not required to specify it if Segment Space Management is AUTO.
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 lets you specify how free and used space within a segment is to be managed. You can choose either manual or automatic segment-space management.
MANUAL: Manual segment-space management uses free lists to manage free space within segments. Free lists are lists of data blocks that have space available for inserting rows. With this form of segment-space management, you must specify and tune the PCTUSED, FREELISTS, and FREELIST GROUPS storage parameters for schema objects created in the tablespace. MANUAL is the default.
AUTO: Automatic segment-space management uses bitmaps to manage the free space within segments. The bitmap describes the status of each data block within a segment with respect to the amount of space in the block available for inserting rows. As more or less space becomes available in a data block, its new state is reflected in the bitmap. These bitmaps allow the database to manage free space automatically.
You can specify automatic segment-space management only for permanent, locally managed tablespaces. Automatic segment-space management is a simpler and more efficient way of managing space within a segment. It completely eliminates any need to specify and tune the PCTUSED, FREELISTS, and FREELIST GROUPS storage parameters for schema objects created in the tablespace. If you specify these attributes, the database ignores them.
can i set PCTFREE and PCTUSED in LMT
http://docs.oracle.com/cd/B12037_01/server.101/b10739/tspaces.htm
Thanks
Kuljeet Pal Singh

Parameters in schema(pe01)?

Similar Messages

Maybe you are looking for