Schema owner object permission

Does schema owner which is oracle user has all the object permissions for all the object under that schme eventhough all the objects are created on that shcmea with sys user?
Please advise
Thanks
Tina

I dont understand where exactly you are checking... i am able to check the objects created like that in my Tables list.

Similar Messages

SELECT on XML DB Table works for Schema owner, not for Schema user

Hi,
We are working on Oracle 10.2.0.3 under HP-UX.
We get ORA-01031: Insufficient Privileges when trying to execute Query
on Oracle XMLDB Table by Schema User
Here are detailed steps:
1) We have 2 users: CDROWNER (Schema Owner)
CDRJAVA (Schema User)
2) login as CDROWNER and execute following:
3) Register 2 XSDs (Common is used by CorridorRate)
Common.xsd:
<?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
     <xsd:complexType name="NamedCustomer_V1" xdb:SQLType="NAMED_CUSTOMER_T">
          <xsd:annotation>
               <xsd:documentation>Named customer for the quote</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SAP_IDS" type="SAPIDCollection_V1" minOccurs="0" xdb:SQLName="SAP_IDS">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="BookingConditions" type="xsd:string" minOccurs="0" xdb:SQLName="BOOKING_CONDITIONS"/>
               <xsd:element name="BLConditions" type="xsd:int" xdb:SQLName="BL_CONDITIONS"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="Attachment_V1" xdb:SQLType="ATTACHMENT_T">
          <xsd:annotation>
               <xsd:documentation>Quote attachment</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Url" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_URL"/>
               <xsd:element name="Text" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_TEXT"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="SentOfferingRecord_V1" xdb:SQLType="SENT_OFFERING_RECORD_T">
          <xsd:annotation>
               <xsd:documentation>Record of quote sending out to customer</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="TimeSent" type="xsd:string" minOccurs="0" xdb:SQLName="TIME_SENT"/>
               <xsd:element name="UserName" type="xsd:string" minOccurs="0" xdb:SQLName="USER_NAME"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="QuoteFormatSettings_V1" xdb:SQLType="QUOTE_FMT_SETTINGS_T">
          <xsd:annotation>
               <xsd:documentation>Quote format setting specification</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="TemplateName" type="xsd:string" minOccurs="0" xdb:SQLName="TEMPLATE_NAME">
                    <xsd:annotation>
                         <xsd:documentation>predefined format template</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="OptionalContentIDs" type="StringWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="OPTIONAL_CONTENTS" xdb:SQLCollType="OPTIONAL_CONTENT_V">
                    <xsd:annotation>
                         <xsd:documentation>optional contents</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="StandardRemarkIDs" type="IDWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="STANDARD_REMARKS" xdb:SQLCollType="STANDARD_REMARK_V">
                    <xsd:annotation>
                         <xsd:documentation>standard remarks specified by each region/office</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="StandardDisclaimerID" type="ID_LongNumeric_V1" minOccurs="0" xdb:SQLName="STANDARD_DISCLAIMER">
                    <xsd:annotation>
                         <xsd:documentation>standard disclaimer specified by each region/office</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ShowSurcharges" type="ShowSurchargeType_V1" xdb:SQLName="SHOW_SURCHARGES">
                    <xsd:annotation>
                         <xsd:documentation>specifies how surcharges are shown in the offering document, can be show prepaid only, collect only or all</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="SurchargeCode_V1">
          <xsd:restriction base="xsd:string"/>
     </xsd:simpleType>
     <xsd:simpleType name="ShowSurchargeType_V1">
          <xsd:annotation>
               <xsd:documentation>Indicator for quote to show prepaid, collect or all surcharges</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="Prepaid"/>
               <xsd:enumeration value="Collect"/>
               <xsd:enumeration value="All"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="StandardRemarkAndDisclaimer_V1" xdb:SQLType="STD_REMARK_AND_DISCLAIMER_T">
          <xsd:annotation>
               <xsd:documentation>Region specific standard remark and disclaimer</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Id" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_ID"/>
               <xsd:element name="Region" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_REGION"/>
               <xsd:element name="IsRemark" type="xsd:boolean" xdb:SQLName="IS_REMARK"/>
          </xsd:sequence>
     </xsd:complexType>
     
     
     
     
     
     <xsd:complexType name="GeoIDCollection_V1" xdb:SQLType="GEO_ID_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="IDWrappers" type="IDWrapper_V1" maxOccurs="unbounded" xdb:SQLName="GEO_ID_WRAPPERS" xdb:SQLCollType="GEO_ID_WRAPPER_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="IDWrapper_V1" xdb:SQLType="ID_WRAPPER_T">
          <xsd:sequence>
               <xsd:element name="Value" type="ID_LongNumeric_V1" xdb:SQLName="ID_VAL"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="OfficeCodeCollection_V1" xdb:SQLType="OFFICE_CODE_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="OFFICE_CODE_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="SAPIDCollection_V1" xdb:SQLType="SAP_ID_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SAP_ID_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="ServiceLoopCodeCollection_V1" xdb:SQLType="SERVICE_LOOP_CODE_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SERVICE_LOOP_CODE_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="IncludedHSCodeCollection_V1" xdb:SQLType="INCLUDED_HS_CODE_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="INCLUDED_HS_CODE_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="StringWrapper_V1" xdb:SQLType="STRING_WRAPPER_T">
          <xsd:sequence>
               <xsd:element name="Value" xdb:SQLName="STR_VAL">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="256"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="GuidelineRateReference_V1">
          <xsd:annotation>
               <xsd:documentation>Represents a guideline rate containing an ocean rate and up to 4 inland/port arbitrary add-on rates</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="OutboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>The first outbound inland rate. If present, the location of this rate is always the point of receipt. Otherwise the point of receipt is (one of) the Trunk origin(s). The over location must match with either OB2 Location or Trunk Origin (if OB2 is not present)</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="OutboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>An optional outbound inland rate. If present, the location must match with the over location of OB1 and the over location of this rate must match with the origin of the Trunk.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="BaseRateID" type="ID_LongNumeric_V1">
                    <xsd:annotation>
                         <xsd:documentation>The BaseRate = trunk / ocean rate.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="InboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>The inbound rate connecting to the destination of the trunk. If there is only one inbound rate (IB2 is not present), then this rate will have the final destination. </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="InboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>A second inbound rate which connects to the first inbound rate to arrive at a final destination.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:simpleType name="AgreementID_V1">
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="AgreementStatus_V1">
          <xsd:annotation>
               <xsd:documentation>Agreement Status, like filed, approve, terminated, amend</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
               <xsd:enumeration value="File"/>
               <xsd:enumeration value="Filed"/>
               <xsd:enumeration value="Approve"/>
               <xsd:enumeration value="Terminated"/>
               <xsd:enumeration value="New"/>
               <xsd:enumeration value="Incomplete"/>
               <xsd:enumeration value="Amend"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="AgreementType_V1">
          <xsd:annotation>
               <xsd:documentation>Agreement type, like CSO, SC, AB</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
               <xsd:enumeration value="CSO">
                    <xsd:annotation>
                         <xsd:documentation>Customized Service Offering</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="RA">
                    <xsd:annotation>
                         <xsd:documentation>Rate Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="SVC">
                    <xsd:annotation>
                         <xsd:documentation>Service Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="SUR">
                    <xsd:annotation>
                         <xsd:documentation>Surcharge Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="SC">
                    <xsd:annotation>
                         <xsd:documentation>Service Contract</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="TSO">
                    <xsd:annotation>
                         <xsd:documentation>Territorial Customized Service Offering</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="TSA">
                    <xsd:annotation>
                         <xsd:documentation>Territorial Service Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="AB">
                    <xsd:annotation>
                         <xsd:documentation>Agreement Builder</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="TradeTerm_V1">
          <xsd:annotation>
               <xsd:documentation>Trade term</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="10"/>
               <xsd:enumeration value="FOB"/>
               <xsd:enumeration value="CIF"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="ABDateTime_V1">
          <xsd:restriction base="xsd:dateTime"/>
     </xsd:simpleType>
     
     <xsd:complexType name="PersonName_V1" xdb:SQLType="PERSON_NAME_T">
          <xsd:sequence>
               <xsd:element name="FirstName" minOccurs="0" xdb:SQLName="FIRST_NAME">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string"/>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LastName" minOccurs="0" xdb:SQLName="LAST_NAME">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string"/>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="EmailAddress_V1" xdb:SQLType="EMAIL_ADDRESS_T">
          <xsd:sequence>
               <xsd:annotation>
                    <xsd:documentation>
                    A common Type for EmailAddress.
                    </xsd:documentation>
               </xsd:annotation>
               <xsd:element name="EmailID" type="xsd:string" xdb:SQLName="EMAIL_ID"/>
               <xsd:element name="EmailType" type="EmailType_V1" default="Unspecified" xdb:SQLName="EMAIL_TYPE"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="EmailType_V1">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="Home"/>
               <xsd:enumeration value="Work"/>
               <xsd:enumeration value="Unspecified"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="PhoneNumberType_V1">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
                    Type refers to the contact number type associated to the contact number.
                    May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="BusinessPhone"/>
               <xsd:enumeration value="HomePhone"/>
               <xsd:enumeration value="BusinessFax"/>
               <xsd:enumeration value="HomeFax"/>
               <xsd:enumeration value="MobilePhone"/>
               <xsd:enumeration value="Pager"/>
               <xsd:enumeration value="Telex"/>
               <xsd:enumeration value="Unspecified"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:complexType name="PhoneNumber_V1" xdb:SQLType="PHONE_NUMBER_T">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
                    PhoneNumber is a common type that defines generic structure of a phone number object.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="CountryCode" type="xsd:string" minOccurs="0" xdb:SQLName="COUNTRY_CODE">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              CountryCode holds on the country code value.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="AreaCode" type="xsd:string" minOccurs="0" xdb:SQLName="AREA_CODE">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              AreaCode holds on the area code value.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Number" type="xsd:string" xdb:SQLName="PHONE_NUMBER">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              Number holds on the number value.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Extension" type="xsd:string" minOccurs="0" xdb:SQLName="PHONE_EXTN">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              Extension holds on the phone number extension, if applicable
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Type" type="PhoneNumberType_V1" default="Unspecified" xdb:SQLName="PHONE_NUM_TYPE">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              Type refers to the contact number type associated to the contact number.
                              May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified
                              Default value is Unspecified.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="ContactInformation_V1" xdb:SQLType="CONTACT_INFORMATION_T">
          <xsd:sequence>
               <xsd:element name="Name" type="PersonName_V1" minOccurs="0" xdb:SQLName="CONTACT_NAME"/>
               <xsd:element name="EmailAddresses" type="EmailAddress_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="EMAIL_ADDRESSES" xdb:SQLCollType="EMAIL_ADDRESS_V"/>
               <xsd:element name="PhoneNumbers" type="PhoneNumber_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="PHONE_NUMBERS" xdb:SQLCollType="PHONE_NUMBER_V"/>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:simpleType name="CardinalDirectionName_V1">
          <xsd:annotation>
               <xsd:documentation>A list of voyage name direction.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="North"/>
               <xsd:enumeration value="South"/>
               <xsd:enumeration value="East"/>
               <xsd:enumeration value="West"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="ID_LongNumeric_V1">
          <xsd:annotation>
               <xsd:documentation>Represents Identifier using long as the restriction - with max - 15 digits</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:long"/>
     </xsd:simpleType>
     
     <xsd:simpleType name="ServiceLoopCode_V1">
          <xsd:annotation>
               <xsd:documentation>A simple type that holds on to the service loop code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="4"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="CurrencyCode_V1">
          <xsd:annotation>
               <xsd:documentation>A 3 digit currency code string (like USD)</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:length value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="TariffCode_V1">
          <xsd:annotation>
               <xsd:documentation>tariff code that uniquely identify a tariff</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:length value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="Global_UUID_V1">
          <xsd:annotation>
               <xsd:documentation>This is to represent the largest UUID format in the domain. Max. length is 36.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="36"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="UUID_V1">
          <xsd:annotation>
               <xsd:documentation>A system generated uuid in string format. Max. length is 20.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="Global_UUID_V1">
               <xsd:maxLength value="20"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="CustomerContactRoleType_V1">
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
               <xsd:enumeration value="Accounting"/>
               <xsd:enumeration value="Booking"/>
               <xsd:enumeration value="Booking_CS"/>
               <xsd:enumeration value="Documentation"/>
               <xsd:enumeration value="General"/>
               <xsd:enumeration value="Operations"/>
               <xsd:enumeration value="Pricing"/>
               <xsd:enumeration value="Sales"/>
               <xsd:enumeration value="Sales_SMM"/>
               <xsd:enumeration value="Warehouse"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="TradeCode_V1">
          <xsd:annotation>
               <xsd:documentation>A simple type that holds on to the trade code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="ShipmentBoundCode_V1">
          <xsd:annotation>
               <xsd:documentation>A list of shipment bound code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="IB"/>
               <xsd:enumeration value="OB"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="CustomerContactSpecification_V1" xdb:SQLType="CUST_CONTACT_SPEC_T">
          <xsd:sequence>
               <xsd:element name="ContactSpecUUID" type="UUID_V1" xdb:SQLName="CONTACT_SPEC_UUID"/>
               <xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
               <xsd:element name="Role" type="CustomerContactRoleType_V1" xdb:SQLName="CONTACT_ROLE"/>
               <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="CUST_SAP_ID"/>
               <xsd:element name="TradeCode" type="TradeCode_V1" minOccurs="0" xdb:SQLName="TRADE_CODE"/>
               <xsd:element name="TradeLaneCode" type="TradeLaneCode_V1" minOccurs="0" xdb:SQLName="TRADE_LANE_CODE"/>
               <xsd:element name="ServiceLoopCode" type="ServiceLoopCode_V1" minOccurs="0" xdb:SQLName="SERVICE_LOOP_CODE"/>
               <xsd:element name="ShipmentBoundCode" type="ShipmentBoundCode_V1" minOccurs="0" xdb:SQLName="SHIPMENT_BOUND_CODE"/>
               <xsd:element name="CommodityGroupCode" type="AlphaCode_V1" minOccurs="0" xdb:SQLName="COMMODITY_GROUP_CODE"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="CustomerContact_V1" xdb:SQLType="CUSTOMER_CONTACT_T">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
               This defines a contact for a Customer. A customer contact is someone to whom an OOCL sales representative communicates regarding business transactions between OOCL and the Customer.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
               <xsd:element name="ContactInformation" type="ContactInformation_V1" xdb:SQLName="CONTACT_INFORMATION"/>
               <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID"/>
               <xsd:element name="Title" minOccurs="0" xdb:SQLName="TITLE">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="35"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="JobTitle" minOccurs="0" xdb:SQLName="JOB_TITLE">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="35"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Department" minOccurs="0" xdb:SQLName="DEPARTMENT">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="35"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Specifications" type="CustomerContactSpecification_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="CUST_CONTACT_SPECS" xdb:SQLCollType="CUST_CONTACT_SPEC_V"/>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:simpleType name="TradeLaneCode_V1">
          <xsd:annotation>
               <xsd:documentation>A simple type that holds on to the trade lane code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="CompanyName_V1">
          <xsd:annotation>
               <xsd:documentation>Name of a Company
This is used to denote the information about an organization which may not be a Customer</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="105"/>
               <xsd:minLength value="1"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:complexType name="CorridorBaseRate_V1" xdb:SQLType="CORRIDOR_BASE_RATE_T">
          <xsd:annotation>
               <xsd:documentation>Corridor base rate specifications</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Amount" type="xsd:decimal" minOccurs="0" xdb:SQLName="BASE_RATE_AMOUNT">
                    <xsd:annotation>
                         <xsd:documentation>charge amount</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Currency" type="CurrencyCode_V1" minOccurs="0" xdb:SQLName="BASE_RATE_CURRENCY">
                    <xsd:annotation>
                         <xsd:documentation>charge currency code</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="OfferType" minOccurs="0" xdb:SQLName="OFFER_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>offer type: either OOCL offered or customer requested</xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="4"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="IsSOC" type="xsd:boolean" minOccurs="0" xdb:SQLName="IS_SOC">
                    <xsd:annotation>
                         <xsd:documentation>indicator for shipper owned container</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="EffectiveFrom" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_FROM" xdb:SQLType="TIMESTAMP">
                    <xsd:annotation>
                         <xsd:documentation>effectime start time of the rate</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="EffectiveTo" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_TO" xdb:SQLType="TIMESTAMP">
                    <xsd:annotation>
                         <xsd:documentation>effectime end time of the rate</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="TransitTime" type="xsd:string" minOccurs="0" xdb:SQLName="TRANSIT_TIME">
                    <xsd:annotation>
                         <xsd:documentation>transit time of shipment that the rate offered</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="SAP_ID_V1">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
               SAP ID is the unique identifier for a given Customer in reference to SAP Application.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="10"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="ABShippingParty_V1" xdb:SQLType="AB_SHIPPING_PARTY_T">
          <xsd:annotation>
               <xsd:documentation>Customer's roles in a shipment, like shipper, consignee, etc</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="CustomerHolder" type="CustomerHolder_V1" xdb:SQLName="CUSTOMER_HOLDER"/>
               <xsd:element name="ShippingRoleGroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="SHIPPING_ROLE_GROUP_ID"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="CustomerHolder_V1" xdb:SQLType="CUSTOMER_HOLDER_T">
          <xsd:annotation>
               <xsd:documentation>A place holder where a new customer was created or modified in agreement builder</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID">
                    <xsd:annotation>
                         <xsd:documentation>Customer SapID if it is an existing customer</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Name" type="CompanyName_V1" minOccurs="0" xdb:SQLName="COMPANY_NAME">
                    <xsd:annotation>
                         <xsd:documentation>New customer name that is created during agreement builder creation(customer does not exist in NewCPF)</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ModifiedContacts" type="CustomerContact_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="MODIFIED_CONTACTS" xdb:SQLCollType="MODIFIED_CONTACT_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="ShippingPartyRoleGroup_V1" xdb:SQLType="SHIPPING_PARTY_ROLE_GROUP_T">
          <xsd:annotation>
               <xsd:documentation>All customer's shipping role in an agreement</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="GroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="GROUP_ID"/>
               <xsd:element name="IsShipper" type="xsd:boolean" xdb:SQLName="IS_SHIPPER"/>
               <xsd:element name="IsConsignee" type="xsd:boolean" xdb:SQLName="IS_CONSIGNEE"/>
               <xsd:element name="IsForwarder" type="xsd:boolean" xdb:SQLName="IS_FORWARDER"/>
               <xsd:element name="IsControlParty" type="xsd:boolean" xdb:SQLName="IS_CONTROL_PARTY"/>
               <xsd:element name="IsSignatureParty" type="xsd:boolean" xdb:SQLName="IS_SIGNATURE_PARTY"/>
               <xsd:element name="IsNotifyParty" type="xsd:boolean" xdb:SQLName="IS_NOTIFY_PARTY"/>
               <xsd:element name="IsAssociate" type="xsd:boolean" xdb:SQLName="IS_ASSOCIATE"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="AlphaCode_V1">
          <xsd:annotation>
               <xsd:documentation>Code of a CommodityReportGroup. The Business Community refers to this 3 digit code as the AlphaCode
               </xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="CargoNatureCode_V1">
          <xsd:annotation>
               <xsd:documentation>The classification code of cargo for special stowage arrangement</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="2"/>
               <xsd:enumeration value="AW">
                    <xsd:annotation>
                         <xsd:documentation>Awkward</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="DG">
                    <xsd:annotation>
                         <xsd:documentation>Dangerous</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="GC">
                    <xsd:annotation>
                         <xsd:documentation>GeneralCargo</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="RF">
                    <xsd:annotation>
                         <xsd:documentation>Reefer</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="ID_Integer_V1">
          <xsd:annotation>
               <xsd:documentation>Represents Identifier using Integer as the restriction.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:int"/>
     </xsd:simpleType>
     <xsd:complexType name="CorridorVolume_V1" xdb:SQLType="CORRIDOR_VOLUME_T">
          <xsd:annotation>
               <xsd:documentation>Corridor volumns associated with corridor base rate</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="ID" type="xsd:int" xdb:SQLName="IDNUM">
                    <xsd:annotation>
                         <xsd:documentation>A numeric identifier which identifies a CorridorVolume only in the context of a Quote/Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
                    <xsd:annotation>
                         <xsd:documentation>corridor rate volume specification</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="VolumePatterns" type="VolumePattern_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="VOLUME_PATTERNS" xdb:SQLCollType="VOLUME_PATTERN_V">
                    <xsd:annotation>
                         <xsd:documentation>detailed volume sepecification</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Basis" type="xsd:string" minOccurs="0" xdb:SQLName="BASIS"/>
               <xsd:element name="IsConditionOfRate" type="xsd:boolean" xdb:SQLName="IS_CONDITION_OF_RATE">
                    <xsd:annotation>
                         <xsd:documentation>indicate if the volume sepecification is a condition of the corridor rate</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="IsShared" type="xsd:boolean" xdb:SQLName="IS_SHARED">
                    <xsd:annotation>
                         <xsd:documentation>Indicates if the volume group is shared by more than one corridor rate. When true, sizetype should be null</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="IsForEntireAgreement" type="xsd:boolean" xdb:SQLName="IS_FOR_AGREEMENT"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="VolumePattern_V1" xdb:SQLType="VOLUME_PATTERN_T">
          <xsd:annotation>
               <xsd:documentation>Agreement volume pattern</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
                    <xsd:annotation>
                         <xsd:documentation>volume amount</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Period" type="xsd:string" minOccurs="0" xdb:SQLName="PERIOD">
                    <xsd:annotation>
                         <xsd:documentation>time period for the volume</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="ShipmentVolume_V1" xdb:SQLType="SHIPMENT_VOLUME_T">
          <xsd:annotation>
               <xsd:documentation>A measurement for shipment volume</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Unit" type="xsd:string" minOccurs="0" xdb:SQLName="UNIT"/>
               <xsd:element name="Value" type="xsd:decimal" minOccurs="0" xdb:SQLName="VALUE"/>
          </xsd:sequence>
     </xsd:complexType>
     
</xsd:schema>
CorridorRate.xsd
<?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
     <xsd:include schemaLocation="AB_Common_V1_XMLDB.xsd"/>
     <xsd:element name="CorridorRate" type="CorridorRate_V1" nillable="true" xdb:SQLName="CORRIDOR_RATE"/>
     
     <xsd:simpleType name="DeliveryMode_V1">
          <xsd:annotation>
               <xsd:documentation>2 char string representing the delivery mode associated with the rate. YY for example is a Container Yard to Container Yard move, whereas DD is a door to door move.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="2"/>
               <xsd:minLength value="2"/>
               <xsd:enumeration value="YY"/>
               <xsd:enumeration value="YD"/>
               <xsd:enumeration value="DY"/>
               <xsd:enumeration value="DD"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="PaymentTerm_V1">
          <xsd:annotation>
               <xsd:documentation>Payment term, either prepaid or collect</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="10"/>
               <xsd:enumeration value="Prepaid"/>
               <xsd:enumeration value="Collect"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:complexType name="CorridorMetric_V1" xdb:SQLType="CORRIDOR_METRIC_T">
          <xsd:annotation>
               <xsd:documentation>Corridor metrics associated with corridor base rate</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="VolumeSRG" type="xsd:string" minOccurs="0" xdb:SQLName="VOLUME_SRG">
                    <xsd:annotation>
                         <xsd:documentation>guideline volume</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="AgreementSRG" type="xsd:string" minOccurs="0" xdb:SQLName="AGREEMENT_SRG">
                    <xsd:annotation>
                         <xsd:documentation>ageeement volume</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ContributionNRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_NRPO">
                    <xsd:annotation>
                         <xsd:documentation>contribution matrix NRPO</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ContributionRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_RPO">
                    <xsd:annotation>
                         <xsd:documentation>contribution matrix RPO</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="AverageRate" type="xsd:string" minOccurs="0" xdb:SQLName="AVERAGE_RATE">

Thanks so much for your response - Prefixing the call to the table within the package, with the schema owner does indeed solve the problem. Since this is a Production issue, i have implemented this fix in my customer's database.
However, I would still like this issue permanently resolved. The next time we send out updated package code, this will happen again (unless we then fix it again). I'd still like info from anyone on what exactly must be done to allow the call within the package to work without specifically pre-fixing the table's schema owner. It shouldn't be needed... The DB link is connecting via the same schema on database B that owns the table in question.
pre-fixing the schema owner is something we don't do in our sql statements, and this has worked fine for many of our cusomer's environments. We're only seeing this issue on one environment.

To access PD Repository, why do we have to connect to the schema owner?

Hi
we use Oracle for PD repository. In order to connect to the repository, we create odbc connection to the repository schema owner. The question is, can we create a application schema user and provide read/write privileges to the repository and then create odbc connection to this application schema instead of repository schema?
thanks

Hi Krishna,
We create odbc connection to the repository schema owner. The question is, can we create a application schema user and provide read/write privileges to the repository and then create odbc connection to this application schema instead of repository schema? Yes
I suggest that you use the proxy rather than a direct connection. Search this topic in this forum.
If you decide to keep your idea here's how :
REPOSITORY_SCHEMA (OWNER SCHEMA):
GRANT SELECT, INSERT, UPDATE, DELETE ON EACH <PD TABLES> TO <APPLICATION_SCHEMA>
(PD tables usually begin by PM%, actually PD does not use VIEW, SEQUENCE objects)
On Application Schema : Create as many synonyms as there's table to go to the schema owner
Example : CREATE SYNONYM PMTEMP FOR <OWNER_SCHEMA.PMTEMP>
Ask to your Oracle DBA. It can do, he know how do.
Warning : When you do an update of PD you will have to check if the privileges are gone,if SAP has added new tables, etc.
I do not think it's a good idea to follow this path
Note : Your evaluation of my answer would be appreciated. Please mark the answer as "Helpful” or “Correct” if this is the case. Also If you consider that I have answered mark the discussion as “Answered,” so that other members can find the answer more easily. Before posting a new question members search SCN to see if it’s already been asked / answered. That’s the fastest way to get information.

Locking Schema Owner account in oracle

Hi
One of the oracle security policy recommendations is to lock the owning schema in the database. To overcome this issue I suggested to the developer that I can create a new access account with permissions to select ,insert,delete and update data on owning schema. But the developer is insisting that instead of creating that new account, should transfer the objects of the schema owner account to a new account and unlock the schema owner account this way he does not have to make changes to the application on his side...this did not make sense to me ,can some one please shed some light on this?

>
sorry , I meant that when we lock the schema owner ,connecting to the database with that account is denied. What I suggested is to create an access account with SUID priviliges on owning schema data. But the developer insists that I create a new account transfer the objects/data from schema owner to this new account and then unlock the schema owner account. This way he will not have to make changes on the application side,I was not entirely sure how it will benefit him by doing so
>
You still haven't stated what the actual issue is you are trying to address.
From the first post is seemed that your question was 'How can we implement the Oracle security recommendation to lock the application account without actually locking the application account'?
And your proposed solution is to create another account with exactly the same privileges as the schema owner and use that account instead.
That doesn't implement the recommendation. That is an attempt to circumvent the recommendation.
My advice is that if you don't want to actually implement Oracle's recommendation then don't implement it.
And if you do want to implement the recommendation then do so. But none of the options you are suggesting implement it they only circumvent it.
>
One of the oracle security policy recommendations is to lock the owning schema in the database
>
What is the citation for this statement? What reason was given for the recommendation?
One primary reason for using application users (rather than schema users) is to exert positive control over the functionality and data that the application has access to.
A schema owner has access to all objects owned by the schema. Applications typically don't need all of those privileges. A schema owner can create new objects and modify existing objects; applications seldom need to be able to do that.
Within a stored procedure a schema owner still has access to all of the schemas objects but other users/applications only have access granted directly to them and do not have access to objects granted only thru roles.
To properly implement the recommendation you need to create an application user and grant that user the roles and direct grants that are needed for the functionality and data that needs to be accessed. The result is two users: one has full access to the schema objects and the other has limited access. Application code should use the limited user credentials.
What you call the users is up to you. If you want to switch roles and make your current user the limited user and create a new user for the objects and move them all to the new schema go ahead.
But that is a lot of work and validation for you to have to do. The only change a developer should have to make to use a different user is to change the connection information. That should be very simple to do and if it is not it needs to be changed to make it simple.
Based only on the information you have provided it sounds like the developer is just lazy and wants you to have to do all of the work. So the developer needs to make their case as to why they can't just change connection settings and then management can make a decision about which method should be used.
Your work should be to create a new application account that specifically is NOT simply an account superuser but is only granted, either directly or via roles, the specific privileges that the application actually needs. My guess would be that no one actually knows or has documented what privileges are really needed so they just want them all.
The best contribution you could make for security is to resist the super user approach and actuallly push for documentation of the privileges needed and then implement those.
Management and auditors must ALWAYS be able to control and determine who is actually using their data.
I would suggest that you create a new user account account

Schema owner with DDL privileges only

Hi,
Oracle 11.2.0.2
What is the easiest way of creating a schema owner that can own all the schema objects (tables, viws, procedures etc) WITHOUT being able to see the data in tables. In short can do DDL without being able to DQ or DML.
Thanks

905989 wrote:
Hi,
Oracle 11.2.0.2
What is the easiest way of creating a schema owner that can own all the schema objects (tables, viws, procedures etc) WITHOUT being able to see the data in tables. In short can do DDL without being able to DQ or DML.
Thanks
do not do as below
GRANT CREATE SESSION TO SCHEMA_OWNER;
If SCHEMA_OWNER can not log into the DB, then they can not do DML or SELECT.

How to restrict a schema owner from granting privileges to other users.

How can we restrict a schema owner from granting privileges to other users on his objects (e.g. tables). Lets say we have user called XYZ and he has tables in his schema TAB1, TAB2 an TAB3. How can we restrict user XYZ from granting privileges on TAB1, TAB2 and TAB3 to other users in the database. Is it possible in Oracle 10g R2? Any indirect or direct way to achieve this? Please help on this.
Thanks,
Manohar

Whenever someone is trying to prevent an object owner from doing something, that's generally a sign of a deeper problem. In a production database, the object owner shouldn't generally have CREATE SESSION privileges, so the user shouldn't be able to log in, which would prevent the user from issuing any grants.
As a general rule, you cannot stop an object owner from granting privileges on the objects it owns. You can work around this by creating a database-level DDL trigger that throws an exception if the user issuing the statement is XYZ and the DDL is a GRANT. But long term, you probably want to get to the root of the problem.
Justin
Edited by: Justin Cave on Nov 6, 2008 9:52 PM
Enrique beat me to it.

Win Server 2003 DC repair the Schema owner

Hello,
I prepare a new server on Win 2012 R2 64b to add to our DC, with 2 Win Server 2003 R2 32b.
At the begin, I view the configuration of the actuel DC / W2003, but I see some trouble :
- Dcdiag
        Warning: CN=NTDS Settings\0ADEL:d96382dc-30df-44f2-9044-82acedf258b7,CN=SUSLAB,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vzad,DC=lab,DC=fr,DC=at,DC=com is the Schema Owner, but is deleted.
- netdom query fsmo
Schema owner                susl.vzad.lab.fr.at.com
Domain role owner           pluto.vzad.lab.fr.at.com
PDC role                           pluto.vzad.lab.fr.at.com
RID pool manager            pluto.vzad.lab.fr.at.com
Infrastructure owner        pluto.vzad.lab.fr.at.com
The command completed successfully.
I think "Schema owner" must be the same as "Domain role owner", your idea ?
Is it possible to undelete the line see with Dcdiag with Ntdsutil ??
Regards, Stef

Warning: CN=NTDS Settings\0ADEL:d96382dc-30df-44f2-9044-82acedf258b7,CN=SUSLAB,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vzad,DC=lab,DC=fr,DC=at,DC=com
is the Schema Owner, but is deleted.
That means that you have an object that was removed and that was not properly cleaned. Is the server SUSLAB still existing? If not then simply proceed with a metadata cleanup and seize the Schema Master FSMO role to another DC.
Metadata cleanup: https://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx
Seizing FSMO roles: https://support.microsoft.com/kb/255504?wa=wsignin1.0
If the server still exist then I would recommend demoting and promoting it again.
For the Best Practices when assigning FSMO roles, you can refer to them here: http://www.windowsdevcenter.com/pub/a/windows/2004/06/15/fsmo.html
"Rule 3: For simpler management, the Schema Master and Domain Naming Master can be on the same machine, which should also be a GC."
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Db_owner Schema owner

I wanted to delete a user (no longer with the company) from a database. The delete failed indicating that the user owned a schema.... I found his AD account (no longer in our system) was the schema owner of the "db_owner" schema.
(I plan to alter the owner to "db_owner" and then delete his account from the DB but am unsure of the consequences of this.)
Any idea how this could have happened or why there would even be a need for it to happen for that schema?
TIA,
edm2
P.S. sql 2008

Hello ,
TAKE OWNERSHIP permission on the entity. If the new owner is not the user that is executing this statement, also requires either, 1) IMPERSONATE permission on the new owner if it is a user or login; or 2) if the new owner is a role, membership in the role,
or ALTER permission on the role; or 3) if the new owner is an application role, ALTER permission on the application role details on:
Transfer ownership
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

Determine Schema Owner

I have a user I'm trying to remove, but it's the owner of some objects. I'm assuming it's the schema owner and thus I'll need to assign the schema to a different user, but I'm not sure how to query the schema owners. Thanks in advance!

select * from dba_obejects where owner=<username>; yu will get the objects it ownes, you can take export and import into new user.. then drop old one.
--Girish

Including Schema owner when generating DDL scripts

Designer 9.0.4.6
How do i set the option to include the schema owner prefix in the DDL scripts being generate ("generate server model from database") in design editor?

Generating from the DB Admin tab does not prefix the objects I am generating with the schema name. There isn't a generator preference (that I've found at least) to accomplish this. Has anyone been able to generate database objects prefixed with the schema name?
Thanks,
Wayne

Changind schema owner dbo to SIDadm

Hi All,
After a homogeneous system copy, the schema owner is dbo.
I´d like it to be SIDadm.
Refering to note 551915, the script user_change.sql had been ran on SQL2005, but dbo schema user is coexisting with SIDadm.
Can anyone be a help on this?
Thanks!
Edited by: Saleki Siavauch on Aug 22, 2008 10:03 AM

Saleki Siavauch wrote:
> Hi All,
>
> After a homogeneous system copy, the schema owner is dbo.
> I´d like it to be SIDadm.
>
> Refering to note 551915, the script user_change.sql had been ran on SQL2005, but dbo schema user is coexisting with SIDadm.
>
> Can anyone be a help on this?
>
> Thanks!
>
> Edited by: Saleki Siavauch on Aug 22, 2008 10:03 AM
I hope you backed up your database.
I think what had happened is, you changed the user and profile parameter from schema "dbo" to "SIDadm" and started the SAP instance right? Because your database now contain objects with same name belonging to the two different schemas.
You need do:
1. Restore your database.
2. Shut down SAP.
3. If you are running 4.7 or older: Run sp_sapdroproc
4. Run the script to change dbo to SIDadm.
5. Start SAP.

SCHEMA/DATABASE 내에 새로운 OBJECT 가 생성될때 자동으로 권한을 부여받는 방법

제품 : ORACLE SERVER
작성날짜 : 2002-11-05
SCHEMA/DATABASE 내에 새로운 OBJECT 가 생성될때 자동으로 권한을 부여받는 방법
=====================================================
PURPOSE
schema 나 database 내에 새로운 table 이 생성될 때 application role 에
object privilege 를 grant 하는 operation 을 자동으로 하는 방법에 대해
소개한다.
이 방법은 procedural object, view 와 같은 object type 에도 확장 적용할
수 있으며 database 내의 application object 의 보안을 관리하는 모든
DBA 에게 필요한 자료이다.
Explanation
CREATE 같은 DDL 문과 관련된 trigger 를 fire 시킬 수 있는 user event
를 사용한다.
- DDL trigger 는 database 나 schema 와 관련될 수 있다.
- SCHEMA triger 는 특정 user 에 대해 각 event 에 대해서 fire 된다.
- DATABASE trigger 는 모든 user 에 대해 각 event 에 대해 fire 된다.
Example
SCOTT schema 에 table 이 생성될 때마다, SELECT, INSERT, UPDATE,
DELETE privilege 를 role R1 에 grant 할 필요가 있는 예를 살펴보자.
( 참고로, 다음은 oracle 9i 에서 role R1 이 있다는 전제하에 test 한다.)
1. sys user 에서 새로 생성되는 table 이름을 저장할 table 을 생성한다.
생성된 table 을 특정 schema 또는 PUBLIC 으로 모든 권한을 부여한다.
SQL> connect / as sysdba
Connected.
SQL> drop table event_table;
Table dropped.
SQL> create table event_table
(ora_dict_obj_owner varchar2(30), ora_dict_obj_name varchar2(30));
Table created.
SQL> grant all on sys.event_table to scott;
Grant succeeded.
2. procedure 를 생성한다.
위의 1.에서 생성한 table 로 부터 table name 을 retrieve 하여
role R1 에 table name 의 권한을 부여하고 row 를 삭제한다.
SQL> create or replace PROCEDURE grant_proc AS
own VARCHAR2(30);
nam VARCHAR2(30);
v_cur INTEGER;
cursor pkgs is
select ora_dict_obj_owner, ora_dict_obj_name
from SYS.event_table;
BEGIN
open pkgs;
loop
fetch pkgs into own, nam;
exit when pkgs%notfound;
v_cur := dbms_sql.open_cursor;
dbms_sql.parse(v_cur,
'grant SELECT, INSERT, UPDATE, DELETE on '||own||'.
'||nam|| ' to R1', dbms_sql.native);
dbms_sql.close_cursor(v_cur);
commit;
delete from sys.event_table;
commit;
end loop;
end;
Procedure created.
3. role R1 에 권한을 부여하는 procedure 를 call 하는 job 을 submit
하는 procedure 를 생성한다.
SQL> create or replace procedure grant_job(procname varchar2) as
jobid number := 0;
procnm varchar2(30);
begin
ProcNm := 'Begin '||ProcName||'; End;';
dbms_job.submit(jobid, procnm);
commit;
end;
Procedure created.
4. trigger 를 생성한다.
이 trigger 는 CREATE 문 이후에 fire 되며 위의 1.에서 생성된
table 에 생성된 table 의 이름이 insert 된다.
그리고 role R1 에 object 권한을 부여하는 procedure 를 call 하는
job 을 submit 하는 procedure 를 call 한다.
SQL> CREATE or REPLACE TRIGGER role_update
AFTER CREATE on scott.schema
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
IF( ora_sysevent='CREATE' and ora_dict_obj_type = 'TABLE') THEN
insert into sys.event_table values
(ora_dict_obj_owner, ora_dict_obj_name);
grant_job('grant_proc');
END IF;
END;
Trigger created.
5. 다음의 작업으로 확인해 볼 수 있다.
SQL> connect scott/tiger
Connected.
SQL> create table test_trig (c number);
Table created.
SQL> create table test_trig2 (c number);
Table created.
SQL> select * from sys.event_table;
ORA_DICT_OBJ_OWNER ORA_DICT_OBJ_NAME
SCOTT TEST_TRIG
SCOTT TEST_TRIG2
-> 위에서 새로 생성된 table 의 이름들이 insert 되어 있다.
SQL> connect / as sysdba
Connected.
SQL> select * from dba_tab_privs where grantee='R1';
no rows selected
-> job 이 아직 실행되지 않았을 것이다.
SQL> select * from user_jobs;
JOB LOG_USER PRIV_USER
SCHEMA_USER LAST_DATE LAST_SEC THIS_DATE THIS_SEC NEXT_DATE
NEXT_SEC TOTAL_TIME B
INTERVAL
FAILURES
WHAT
NLS_ENV
MISC_ENV INSTANCE
39 SCOTT SYS
SYS 13-SEP-02
11:43:46 0 N
null
Begin grant_proc; End;
NLS_LANGUAGE='AMERICAN' NLS_TERRITORY='AMERICA' NLS_CURRENCY='$' NLS_ISO_CURRENC
Y='AMERICA' NLS_NUMERIC_CHARACTERS='.,' NLS_DATE_FORMAT='DD-MON-RR' NLS_DATE_LAN
GUAGE='AMERICAN' NLS_SORT='BINARY'
0102000000000000 0
-> job 이 실행되는 동안 기다린다.
다시 event_table 을 select 해 본다.
SQL> select * from sys.event_table;
no rows selected
SQL> select * from dba_tab_privs where grantee='R1';
GRANTEE OWNER TABLE_NAME GRANTOR PRIVILEGE GRA HIE
R1 SCOTT TEST_TRIG SCOTT INSERT NO NO
R1 SCOTT TEST_TRIG SCOTT SELECT NO NO
R1 SCOTT TEST_TRIG SCOTT UPDATE NO NO
R1 SCOTT TEST_TRIG SCOTT DELETE NO NO
R1 SCOTT TEST_TRIG2 SCOTT INSERT NO NO
R1 SCOTT TEST_TRIG2 SCOTT SELECT NO NO
R1 SCOTT TEST_TRIG2 SCOTT UPDATE NO NO
R1 SCOTT TEST_TRIG2 SCOTT DELETE NO NO
8 rows selected.
job 이 실행된 후 event_table 은 비워 있고
role R1 은 새로 생성된 2개의 table 에 대한 권한을 받았을 것이다.
SQL> select * from user_jobs;
no rows selected
단, 위에서 설명된 것에 따르면 SCHEMA trigger 는 현재 user 의
schema 에서만 fire 되므로 DBA 가 해당 schema 아래에 table 을 생성한다면 이는 작동되지 않을 것이다.
SQL> connect system/manager
Connected.
SQL> create table SCOTT.TEST_TRIG3 (c number);
Table created.
SQL> select * from dba_tab_privs
where grantee='R1' and table_name='TEST_TRIG3';
no rows selected
scott.schema 대신에 DATABASE 에 같은 trigger 를 생성한다면
schema 내에 생성된 table 은 누가 생성했던지 role R1 은 object 권한을
적절하게 부여 받을 것이다.
Reference Documents
<Note:210693.1>
Oracle9i Application Developer's Guide - Fundamentals
Chapter Working With System Events - Event Attribute Functions
Oracle8i SQL Reference - SQL Statements - CREATE TRIGGER
Oracle8i SQL Reference - SQL Statements - CREATE PROCEDURE

Who is a Schema owner

Happy New Year folks!!
I have a couple questions regarding 'Schemas'.
1) Whos called a schema owner? I thought if schema is a bundle of objects created by a user; the user I guess should be called the owner of that particular schema. Am I correct? Or are there any particular database priviledges that need to be explicitly given to a user to make it a schema owner?
2) If I have granted CONNECT; RESOURCE and CTXAPP roles to a user what priviledges will the user inherit in 9i and 10g?

Thanks everyone, very useful comments. I just tried something out and there looks something thats either not correct.I thought I should be able to create that table in the last bit. So why can't I ?
SQL> connect system/password@ora10g
Connected.
SQL> GRANT CREATE SESSION to TEST1;
Grant succeeded.
SQL> grant resource to test1;
Grant succeeded.
SQL> grant connect to test1;
Grant succeeded.
Connect Test1@ora10g
SQL> select * from role_sys_privs;
ROLE PRIVILEGE ADM
CONNECT CREATE VIEW NO
CONNECT CREATE TABLE NO
CONNECT ALTER SESSION NO
CONNECT CREATE CLUSTER NO
CONNECT CREATE SESSION NO
CONNECT CREATE SYNONYM NO
CONNECT CREATE SEQUENCE NO
CONNECT CREATE DATABASE LINK NO
RESOURCE CREATE TYPE NO
RESOURCE CREATE TABLE NO
RESOURCE CREATE CLUSTER NO
RESOURCE CREATE TRIGGER NO
RESOURCE CREATE OPERATOR NO
RESOURCE CREATE SEQUENCE NO
RESOURCE CREATE INDEXTYPE NO
RESOURCE CREATE PROCEDURE NO
SQL> select * from role_role_privs;
no rows selected
SQL> select * from role_tab_privs;
no rows selected
SQL> create table t(name varchar2(10));
create table t(name varchar2(10))
ERROR at line 1:
ORA-01031: insufficient privileges

Prefixing the schema owner to the table name

I have entity objects in my JClient app that were created from tables owned by USER1. When I connect to my JClient app as USER2 the DML fails because the table names are not prefixed by the table owner (USER1). I don't want to use public synonyms and I don't want to customize my view objects just to prefix the table names with the table owner. How could I prefix all of the table names with the table/schema owner by default?

We have been using another approach. We change the "current schema" at the db session level. This avoids having to define public synonyms and having to fully qualify names. It also allows us to have the same application schema defined multiple times in a db instance, which is useful for testing.
While our real code is bit more complicated, basically we implement the afterConnect() and prepareSession() methods on an appication module with a call to our utility method:
protected void afterConnect() {
super.afterConnect();
setupSession('hr');
protected void setupSession(String currentSchema) {
try {
log.debug("Setting current schema to: " + currentSchema +
" via: call alter session set current schema " + currentSchema);
Statement stmt =
getDBTransaction().createStatement(DBTransaction.DEFAULT);
stmt.execute("alter session set current_schema=" + currentSchema);
stmt.close();
} catch (SQLException e) {
if (e.getErrorCode() == 1435) {
log.info("Couldn't set the current_schema to " + currentSchema +
" because it doesn't exist in the target db.");
} else {
log.error("Error setting current_schema in DB context!", e);
} catch (Exception e) {
log.error("Error setting current_schema in DB context!", e);
}

Schema owner for ECC 5.0 IDES

Hi,
When I am trying to start ECC 5.0, the work processes are dying below is the error.
OS: Windows, DB: Oracle.
Now I'm connected to ORACLE
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c    10114]
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=0493EFF4,usrhp=07FC1E64)
C Now I'm disconnected from ORACLE
C Try to connect with default password
C Connecting as SAPR3/<pwd>@CC5 on connection 0 ...
C Starting user session (con_hdl=0,svchp=0493EFF4,srvhp=07FB9234,usrhp=07FC1E64)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
[dboci.c      3721]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c    9750]
B ***LOG BY2=> sql error 1017   performing CON [dbsh#1 @ 1200] [dbsh    1200 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#1 @ 1200] [dbsh    1200 ]
B ***LOG BY2=> sql error 1017   performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1270]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   9377]
Based on these errors I have looked at Notes: 400241, 50088.
The problem is, even though schema owner is listed as SAPSID, why is SAPR3 being used to connect to Oracle.
I have tried creating the users using note 50088, but to no avail.
I have tried creating the users with schema owner as SAPSID. Above is the error message that I get.
When trying to create the users with owner as SAPR3, I get the below error,
ERROR at line 1:
ORA-00959: tablespace 'PSAPUSER1D' does not exist
ORA-06512: at line 114
Regards,
Vishi

Hi,
I have tried suggestions from you all of you, Thank you.
However the problem still persists. I am quite unable to figure out, why it is showing SAPR3 in wp trace.
Below are the error details from dev_w0 log, trans.log
dev_w0:
Logon as OPS$-user to get SAPR3's password
C Connecting as /@CC5 on connection 0 ...
C Attaching to DB Server CC5 (con_hdl=0,svchp=0493EFF4,svrhp=07FB9234)
C Starting user session (con_hdl=0,svchp=0493EFF4,srvhp=07FB9234,usrhp=07FC1E64)
C Now I'm connected to ORACLE
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c    10114]
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=0493EFF4,usrhp=07FC1E64)
C Now I'm disconnected from ORACLE
C Try to connect with default password
C Connecting as SAPR3/<pwd>@CC5 on connection 0 ...
C Starting user session (con_hdl=0,svchp=0493EFF4,srvhp=07FB9234,usrhp=07FC1E64)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
[dboci.c      3721]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c    9750]
B ***LOG BY2=> sql error 1017   performing CON [dbsh#1 @ 1200] [dbsh    1200 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#1 @ 1200] [dbsh    1200 ]
B ***LOG BY2=> sql error 1017   performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1270]
M in_ThErrHandle: 1
Trans.log"
4 ETW000 [dev trc     ,00000] Thu Nov 24 23:48:32 2011                           80178 0.132260
4 ETW000 [dev trc     ,00000] Assigning server context 02C0982C to service context 02C08C24
4 ETW000                                                                              57 0.132317
4 ETW000 [dev trc     ,00000] Allocating user session handle                        47 0.132364
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=02C08C24,srvhp=02C0982C,usrhp=02C123F4)
4 ETW000                                                                             165 0.132529
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000                                                                            6620 0.139149
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000                                                                              31 0.139180
4 ETW000 [dev trc     ,00000] Try to connect with default password                  73 0.139253
4 ETW000 [dev trc     ,00000] Connecting as SAPCC5/<pwd>@CC5 on connection 0 ...
4 ETW000                                                                              27 0.139280
4 ETW000 [dev trc     ,00000] Assigning username to user session 02C123F4           19 0.139299
4 ETW000 [dev trc     ,00000] Assigning password to user session 02C123F4           28 0.139327
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=02C08C24,srvhp=02C0982C,usrhp=02C123F4)
4 ETW000                                                                              31 0.139358
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000                                                                            7326 0.146684
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000                                                                              31 0.146715
4 ETW000 [dblink      ,00419] ***LOG BY2=>sql error 1017   performing CON [dblink#1 @ 419]
4 ETW000                                                                             141 0.146856
4 ETW000 [dblink      ,00419] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#1 @ 419]
4 ETW000                                                                              27 0.146883
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'CC5'"
Should I go back looking at Note: 400241.
Regards,
Vishnu

Schema owner object permission

Similar Messages

Maybe you are looking for