Schema user locked

Hello everybody
My user schema keeps getting locked every time I unlocked it form sql developer it gets back to be locked.
I think that tomcat is trying to access it using wrong pswd. do you have any idea of the solution
where can I make sure that tomcat and apex has the password for this schema??
please help me

answered in another discussion

Similar Messages

How to find out what user locked account

We had production type schema account locked this morning. I checked profile which this user belongs and it has 3 times for Failed Login Attempts. My question is how to find out what user had 3 unsuccessful login attempts and lock this account.
Oracle version 8.1.7

Assuming that [auditing was enabled|http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/security.htm#sthref2916], the command
AUDIT CONNECT WHENEVER NOT SUCCESSFULThat will write audit records when there is an unsuccessful login. Depending on how you've configured auditing, those records will either be written to the SYS.AUD$ table, in which case you can query them through a few different views, or to a file on the operating system that you can grep.
Justin

LOCKS checking user locked and SQL that he is executing

Hello all,
I have this script that inserts into a table the user causing the lock and the users waiting for the lock to be released.
What I would like to add into this the script is the SQL string that the user causing the lock and the users waiting for the the lock to be released are executing.
Can you help me on this?
Script that I have now:
insert into dba.sessions_bloq
select sysdate "Data", w.sid "SID E", s1.username "User E", s1.osuser "OS User E", s1.machine "Maquina E", s1.program "Programa E", s1.logon_time "Logon E",
s.ksusenum "SID B", s2.username "User B", s2.osuser "OS User B", s2.machine "Maquina B", s2.program "Programa B", s2.logon_time "Logon B"
,decode(r.ksqrsidt,
''MR'', ''Media Recovery'',
''RT'', ''Redo Thread'',
''UN'', ''User Name'',
''TX'', ''Transaction'',
''TM'', ''DML'',
''UL'', ''PL/SQL User Lock'',
''DX'', ''Distributed Xaction'',
''CF'', ''Control File'',
''IS'', ''Instance State'',
''FS'', ''File Set'',
''IR'', ''Instance Recovery'',
''ST'', ''Disk Space Transaction'',
''TS'', ''Temp Segment'',
''IV'', ''Library Cache Invalidation'',
''LS'', ''Log Start or Switch'',
''RW'', ''Row Wait'',
''SQ'', ''Sequence Number'',
''TE'', ''Extend Table'',
''TT'', ''Temp Table'',
r.ksqrsidt) "Tipo Lock"
from gv$session_wait w, x$ksqrs r, gv$_lock l, x$ksuse s, gv$session s1, gv$session s2
where w.wait_Time = 0
and w.event = ''enqueue''
and r.ksqrsid1 = w.p2
and r.ksqrsid2 = w.p3
and r.ksqrsidt = chr(bitand(p1,-16777216)/16777215)||
chr(bitand(p1,16711680)/65535)
and l.block = 1
and l.saddr = s.addr
and l.raddr = r.addr
and s.inst_id = userenv(''Instance'')
and w.sid = s1.sid
and w.inst_id = s1.inst_id
and s.ksusenum = s2.sid
and s.inst_id = s2.inst_id;
Thanks in advance

You can link to:
gv$sql
gv$sqltext_with_newlines
but, if doing this in a trigger, also look at these:
http://www.psoug.org/reference/system_events.html

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.

Differences between Roles, Schemas, Users and Logins.

I need differences between Roles, Schemas, Users and Logins. Can anyone help me. Thanks in advance

Roles:
I think of creating roles in the database to group users of like
function. Roles are granted certain permissions in the database. You
should become familiar with the fixed database roles since these will be
utilized once you start creating users within the database. Also, once
you see the type of permissions that are granted to each role, is makes
more sense.
Schema: there can be several schemas in a database,
which will house different types of objects such as tables, indexes,
stored procedures, functions, etc. Users own schemas. Looking into
the AdventureWorks database illustrates this concept, with several
schemas like HR, Production, etc.
Login: Think about login as
gaining access to the SQL Server instance. If a user account is not
granted any permissions within the instance, you basically just were
able to unlock the door and enter the room, by creating a user you then
grant access to the database objects or principals, and can begin to
work with them.
Users: Users own schemas, and as such will be
able to manipulate the objects they own. Some of the manunipulations
are very permissive, such as creating tables, indexes, stored
procedures, functions, etc. These are developers and administrators.
Users
are created and granted permissions for application use, which will
have select, update, insert, and delete and execute permissions to a
finite set of objects in the schema, for which the application will need
to function properly.
In a client server database, as an
example, of the structure. Roles were defined which provides the
permissions to the database objects in the database, which only has one
schema 'dbo'. One SQL server login was created with the same username,
and dbo is the assigned default schema, and the roles assigned to that
username.
In the application, each specific user is given there own
"application" login which is mapped to the one defined sql server
login.
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/

How to check whether the particular schema(user) is having import privilege

Hi,i need to check whether a particular schema(user) is having privilege to import the data to target database within the same database(10 g)

Answer is in the documentation - which is pretty easy to look up -
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_import.htm#i1007024
http://docs.oracle.com/cd/E11882_01/server.112/e25513/statviews_5406.htm#REFRN26230
HTH
Srini

Configuration scenario currently being edited by user" & locked

HI all,
Appreciate your help on this object locks;
I was changing some configuration scenarios in integration Directory - suddanly lost the internet connection;
Now when i try to change it says "configuration scenario currently being edited by user" & locked
I appreciate if you help me to remove these lock objects
Thanks
Iver

Hi,
Go to administration -
Select appropriate option out of these - > repository/ Directory
now select LOCK OVERVIEW.
now you will get all the locked objects by any user.
Now focus on locked object which you want to realese
now press Button Release Lock .
Hurray !!! locks are released.
Hope this helps .....
regards
prabhat Sharma.

User lock failed.SU10

Dear experts,
I locked a mass users using SU10, one of the user locked and immediately prompted for pwd change.
USER1          31.01.2011     09:15:02     ADMIN           Lock Changed     0     Not locked     64     Administrator Lock               SU10
USER1          31.01.2011     09:16:56     USER1           Password Changed     Long Password 3          Long Password 4          KRNL
USER1          31.01.2011     09:16:56     USER1          Lock Changed     64     Administrator Lock     0     Not locked               KRNL
Please suggest why this is happening in my SAP ECC 6.00, Kernal:7.00.
Regards,
Siva.

USER1 31.01.2011 09:15:02 ADMIN Lock Changed 0 Not locked 64 Administrator Lock SU10
USER1 31.01.2011 09:16:56 USER1 Password Changed Long Password 3 Long Password 4 KRNL
USER1 31.01.2011 09:16:56 USER1 Lock Changed 64 Administrator Lock 0 Not locked KRNL
Above log is showing that only lock activity was happened from SU10 and after that User changed his password from other opened screen. Did you kick off that user from the system immediate after locking?
Regards,
Nick Loy

User Lock issue when processing IDOCS

Hi Folks,
We are pushing the data into SAP using IDOCS.During this process some IDOCS are getting failed due to User Lock on shipment header.Anyone here can share their experience in dealing with User Lock issues.
Thanks,
Kiran.

Kiran,
Only one can edit the document, it's standard fucntion. I think No note can resolve this. I can suggest you to run a back ground job very frequently ,which picks these status 51 IDOCs and reprocess. Report is :RBDMANi2
We can use Message class & error message number on selection screen, so that we can make sure that only those idocs which were failed due to Lock problem are taken by the job.
Reddy

User lock persists for killed process

Hi,
We have an app that acquires a user lock (using dbms_lock, release_on_commit FALSE).
We needed to kill a session but it remained in v$session (KILLED), even after killing the OS process. Fine, I know it will clear up eventually.
But the user lock (UL) persists. Does anyone know how it can be force-released?
Calling dbms_lock.release (using handle in v$lock) fails, even as user SYS, the error being that the user does not own the lock. But the owning session is killed so who can release it?
Eventually the session (and lock) disappers from v$session/v$lock but can the lock be removed before then, to avoid a DB bounce in an urgent case?
Thanks

If the process was truely KILLED and not MARKED FOR KILL then I do not know what could of happened. I cannot remember Oracle ever failing to release a user lock when the acquiring session was terminated. We use a fair number of UL; however, few of our processes have concurrent sessions that attempt to use the same UL. Mostly we just ensure that batch processes do not get submitted twice and that some on demand processes run single threaded or do not run if another customer has submitted the task.
HTH -- Mark D Powell --

How it is possible that an internet user locks an order???

Hi,
I have a problem. Some of the orders, when transfered to R/3 has a mapping error in SMW01. When I check the details I see that it gives an error "Transaction 300615856 is being processed by user 7003788553" message number CRM_ORDER013.
However here 7003788553 is an internet user who gave the order. So how it is possible that an Internet user locks the order.
I tried to simulate the error myself in quality system however never succeeded.
Any idea?
Best Regards

Hello
I would suggest you review notes 542924 and 490932.
Regards
Cormac

Sqlplus command to display all schema/user in database

Hi,
What sqlplus command can list out all schemas/users in database?
Ken

select username from dba_users;
will give you a list of the schema owners.
Are you looking for more detail than this?
Bob

Sounds stop playing when user locks screen on iOS with AIR 3.9 Beta

We built a simple application that should play sounds when in background and when the screen is locked.
Since we updated to the latest AIR 3.9 Beta SDK, all sounds stop playing when the user locks the screen on iOS.
The sounds resume when the screen is unlocked.
- it works on Android
- we use renderMode : cpu
- we use UIBackgroundModes : audio
- we use NativeApplication.nativeApplication.systemIdleMode=SystemIdleMode.KEEP_AWAKE;
- sounds play when the app is in background
- was working great with AIR 3.8 SDK
Any help would be greatly appreciated.
Thanks!

Thanks for reproting the issue, we have an internal already logged bug for this, which is under investigation at the moment.
-Nimit

How can I konw , Which computer name or IP Address make SAP User lock

Dear all,
I have one issues about SAP user lock,
Now I don't know which computer name or IP Address make user lock.
How can I check it or Can you tell me about the table that keep information about the ip address or computer name?
I can see the computer name when I use t-code al08 or sm04.
But I don't know the table that keep data from this t-code.
Pls suggest me for this issue.
Regards,
Pannee

In SM21
If you double click on the message "User XXXXX locked due to incorrect logon"
You'll see under details the name of the terminal
Terminal............ XXXXXXXXXXX
for IP address just ping the terminal.
Regards
Juan

User Locking out in LDAP

I guess it's common problem in LDAP. If the user locks out after 3 failed failed logins, The admin needs to be entered in NDS conslole and he need to be unlock after he gets a request from that user. But I couldn't find the property for single User. whatever you specify the parameter in User Lockout tab, it's valid for all the user.
i.e. if you uncheck the checkbox User lockout check box it's valid for all the users. How to unlock the particular user in NDS???
any help in this regard is really appreciable.
regards,
chandra

What version of WLS are you using? In the 6.0 beta, user lockout was one of
the new security features
added. This way, WLS could detect the failure and allow administrators to
detect password guessing
attempts.
If this is a previous release of WLS, you will need to check the NDS
documentation for how to unlock
a given user.
Paul Patrick
"chandra" <[email protected]> wrote in message
news:3a1e3d7d$[email protected]..
>
I guess it's common problem in LDAP. If the user locks out after 3 failedfailed logins, The admin needs to be entered in NDS conslole and he need to
be unlock after he gets a request from that user. But I couldn't find the
property for single User. whatever you specify the parameter in User Lockout
tab, it's valid for all the user.
>
i.e. if you uncheck the checkbox User lockout check box it's valid for allthe users. How to unlock the particular user in NDS???
>
any help in this regard is really appreciable.
regards,
chandra

Schema user locked

Similar Messages

Maybe you are looking for