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"?>
<!-- edited with XMLSpy v2008 sp1 (http://www.altova.com) by Kent Williamson (OOCL (USA) INC) -->
<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>
     <!-- END Jianming Original XSD -->
     <!-- -->
     <!-- All Simple/Complex Types defined below have been copied from External XSD Files -->
     <!-- -->
     <!-- Complex Wrapper types are needed since 10.2 Oracle XMLDB does not support indexing unbounded simple types -->
     <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>
     <!-- Below copied from tnm.agreementbuilder:GuidelineRateReference_V1.xsd -->
     <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>
     <!-- Below copied from tnm:AgreementID_V1.xsd -->
     <xsd:simpleType name="AgreementID_V1">
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
          </xsd:restriction>
     </xsd:simpleType>
     <!-- Below copied from tnm:AgreementStatus_V1.xsd -->
     <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>
     <!-- Below copied from tnm:AgreementType_V1.xsd -->
     <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>
     <!-- Below copied from tnm:TradeTerm_V1.xsd -->
     <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>
     <!-- MODIFIED ABDateTime_V1 to be a simpleType of xsd:dateTime for DB storage -->
     <xsd:simpleType name="ABDateTime_V1">
          <xsd:restriction base="xsd:dateTime"/>
     </xsd:simpleType>
     <!-- Below copied from common:PersonName_V1.xsd -->
     <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>
     <!-- Below copied from common:EmailAddress_V1.xsd -->
     <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>
     <!-- Below copied from common:PhoneNumberType_V1.xsd.xsd -->
     <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>
     <!-- Below copied from common:PhoneNumber_V1.xsd -->
     <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>
     <!-- Below copied from common:ContactInformation_V1.xsd -->
     <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>
     <!-- Below copied from common:CardinalDirection_V1.xsd -->
     <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>
     <!-- Below copied from common:CommonRestrictions_V1.xsd -->
     <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>
     <!-- Below copied from common:ServiceLoopCode_V1.xsd -->
     <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>
     <!-- Below copied from common:Currency_V1.xsd -->
     <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>
     <!-- Below copied from tnm:TariffCode_V1.xsd -->
     <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>
     <!-- Below copied from tnm:TradeLaneCode_V1.xsd -->
     <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>
     <!-- Below copied from CorridorBaseRate_V1.xsd -->
     <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>
     <!-- END Simple/Complex Types copied from External XSD Files -->
</xsd:schema>
CorridorRate.xsd
<?xml version="1.0" encoding="utf-8"?>
<!-- edited with XMLSpy v2007 rel. 3 (http://www.altova.com) by Auroprem Kandaswami (OOCL (USA) INC) -->
<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"/>
     <!-- Below copied from common:DeliveryMode_V1.xsd -->
     <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>
     <!-- Below copied from PaymentTerm_V1.xsd -->
     <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>
     <!-- Below copied from CorridorMetric_V1.xsd -->
     <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.

Similar Messages

  • Table of Contents page numbers works for PDF but not for other formats

    Hi,
    I followed exactly was indicated here regarding creation of TOC.
    http://docs.oracle.com/cd/E10415_01/doc/bi.1013/e12187/T421739T481157.htm
    The page numbers generated correctly for PDF but not for RTF, HTML and XLS.
    (HTML and XLS are understandably not paginated in nature but why not in RTF?)
    Tried to make the simplest example work, with 2 headings each on a separate page. Doesn't work on either MSWord 2003 or 2007.
    What am I doing wrong?
    Regards,
    Jarell
    Edited by: Jarell on Jan 11, 2012 8:08 PM

    Hi Kavipriya,
    What is your email address? I have attached a file in Oracle Metalink, under SR 3-5172030861. named test_toc.rtf
    You may use any xml because the template does not use any dynamic binding of values.
    The template is basically 2 pages, the TOC in the 1st page. First TOC item (Heading 1) is in Page 1, and Second TOC item is in Page 2.
    So the end result should be (PDF result from BI Publisher):
    First TOC Item .................. 1
    Second TOC Item ............. 2
    But for RTF it outputs:
    First TOC Item .................. 0
    Second TOC Item ............. 0
    And after doing Print Preview (once or twice)
    First TOC Item .................. Error in Bookmark
    Second TOC Item ............. Error in Bookmark
    Hope this is detailed enough to illustrate the problem.
    Edited by: Jarell on Jan 17, 2012 10:24 PM

  • How can I add a new Template to My Templates in Pages? I've read most of the discussions on the subject but it doesn't work for me. By the time I reach the Templates folder, I only see templates for Numbers and not for Pages. Need help, please.  Thanks

    How can I add a new Template to My Templates in Pages? I've read most of the discussions on the subject but it doesn't work for me. By the time I reach the Templates folder, I only see templates for Numbers and not for Pages. Need help, please.  Thanks

    Si vous avez utilisé la commande Save As Template depuis Pages, il y a forcément un dossier
    iWork > Pages
    contenant Templates > My Templates
    comme il y a un dossier
    iWork > Numbers
    contenant Templates > My Templates
    Depuis le Finder, tapez cmd + f
    puis configurez la recherche comme sur cette recopie d'écran.
    puis lancez la recherche.
    Ainsi, vous allez trouver vos modèles personnalisés dans leur dossier.
    Chez moi, il y en a une kyrielle en dehors des dossiers standards parce que je renomme wxcvb.template quasiment tous mes documents Pages et wxcvb.nmbtemplate à peu près tous mes documents Numbers.
    Ainsi, quand je travaille sur un document, je ne suis pas ralenti par Autosave.
    Désolé mais je ne répondrai plus avant demain.
    Pour moi il est temps de dormir.
    Yvan KOENIG (VALLAURIS, France)  mercredi 23 janvier 2011 22:39:28
    iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
    My iDisk is : <http://public.me.com/koenigyvan>
    Please : Search for questions similar to your own before submitting them to the community

  • Password works for login but not for the Adobe CC Desktop application

    Password works for login but not for the Adobe CC Desktop application

    Please refer to http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html
    ou can try deleting OPM.DB from steps below and try again.
    Mac OS: You can locate the OPM.db file in the \User\\Library\Application Support\Adobe\OOBE folder. To access the hidden user Library folder, see Access hidden user library files | Mac OS 10.7 Lion. - http://helpx.adobe.com/x-productkb/global/access-hidden-user-library-f iles.html
    Windows: You can locate the OPM.db file in the :\Users\\AppData\Local\Adobe\OOBE folder.  To view the hidden AppData folder, see Show hidden files, folders, filename extensions | Windows XP, Vista, Windows 7. -http://helpx.adobe.com/x-productkb/global/show-hidden-files-folders-ex tensions.html
    3) update to the latest version of the Creative Cloud app.
    Also we would like few more details:
    When has this issue started occurring, was this after installation of any specific adobe product.
    On which platform are you seeing this.
    Also we would like to know if after above steps this issue occurs ever again in future.
    You can refer to http://forums.adobe.com/thread/1239510
    Regards,
    Rajshree

  • Creative SB0410 digital out only works for dd/dts, not for stereo or web videos...

    Creative SB0410 digital out only works for dd/dts, not for stereo or web videos...
    Hi all,
    Need some suggestions here.
    I have an old Creative sb0410 7.1 channel card and after reading few long threads, I am able to output dd/dts via 3.5mm to rca connector.
    However, the problem is I only hear sound if the video has dd or dts sound. When I play normal MP3 or youtube videos, there is no sound.
    Is there a way to configure the digital out so it sends all sound to the receiver whether it's dd or dts or regular stereo?
    Thanks

    As a workaround, I used another 3.5mm stereo to RCA adapter on stereo LR output of sound card and hooked to a different input in my receiver.
    Problem, is I have to switch input in receiver for non DTS/DD sounds.
    It's disappointing that my upscaling dvd player sends all sound signals via coax but this card does not.
    Isn't it supposed to send all sound signals via coax regardless whether it is DTS/DD or normal stereo/mono etc?

  • TS3274 Getting sound for music, but not for game apps.  Checked settings and sound is on.  Any suggestions.

    My volume controls work and getting sound for music but not for game apps.  I did check settings and sound is turned on under notifications and in the app.  Any help would be appreciated

    Have you got notifications muted ? Only notifications (including games) get muted, so the Music and Videos apps, and headphones, still get sound.
    Depending on what you've got Settings > General > Use Side Switch To set to (mute or rotation lock), then you can mute notifications by the switch on the right hand side of the iPad above the volume switch, or via control centre : swipe up from the bottom edge of the screen and it's the right-most of the 5 icons in the middle of it (if the icon is white then it's 'on', tap it to turn it grey and 'off'). The function that isn't controlled via the side switch is controlled via control centre instead : http://support.apple.com/kb/HT4085

  • How can I view the number of tunes in the Library? The number shows for Playlists but not for the total Library.

    How can I view the number of tunes in the Library? The number shows for Playlists but not for the total Library.

    Hello,
    I apologize for submitting this question.  Soon after I posted it I saw a similar question that had my answer..
    Again, my bad for not looking first.
    Ron Morris

  • I talked to your guys yesterday about installing correct version of Lightroom 5 which I legally owned, and your guy provided me a download link (different from Creative cloud account), but somehow it was for Windows version not for Mac version. I would ve

    I talked to your guys yesterday about installing correct version of Lightroom 5 which I legally owned, and your guy provided me a download link (different from Creative cloud account), but somehow it was for Windows version not for Mac version. I would very much like to download a Mac version, so please send my correct web link. By the way my s. number for Lightroom 5 up is [removed], and I also have s.number for 4 up and 3 full.

    The latest non-CC version of LR 5 is 5.7.1 and download links are available on the Adobe Updates page:
    http://www.adobe.com/downloads/updates/
    Both Mac and Win links are there.
    If you are asking for a LR 5 CC link, which wouldn't require a serial number, please be more clear about that.

  • POS system reports daily totals for each store, not for each cashier

    Hi!
    We are implementing SAP Retail (ERP 6.0 EHP4 stack 3), SAP PI (Netweaver PI 7.1 SP 8) and SAP BW (NetWeaver 7.0 ehp1 stack 4, incl BI content 704, SP 3 ) for a client. Their POS system is a 3rd party system, i.e. not SAP POS.
    This issue concerns the fact that the POS system reports daily totals for each store, not for each cashier.
    At my client, the daily settlements are done for each cashier. At the end of day, we will get cash drawers counted with sum of each tender (cash and checks) at the end of day. In addition, the POS system will send sum of each tender, sum of all sales and sum of different finance transactions made each day. However, this u201Ctotals messageu201D is not sent separately for each workstation, or for each cashier, but rather for each store. So we only gets the totals per store.
    Questions:
    i)     Are the tasks available for comparing totals to the aggregates for POS transaction able to handle u201Cstore-only figuresu201D?
    ii)     If not, how can we adapt the tasks so they can handle u201Cstore-only figuresu201D?
    iii)     Can we trigger outbound tasks sending WPUUMS and WPUTAB using outbound dispatcher automatically, or must we run this as a manual task of an employee, after checking that all stores have delivered their totals?
    iv)     The u201Cstore-only figuresu201D does not include cashier statistics. Do we need the u201Ccashier statisticsu201D as total figures, or can we just populate the BAPI for each POS transaction with data, in order to populate BW infocubes for cashier statistics?
    Thanks for any advice !
    Best regards,
    Oeystein Emhjellen

    Hi Kees ...
    Your profile indicates you are running Leopard v10.5.8
    You need to upgrade to Snow Leopard V10.6 in order to use the App Store. This is an "upgrade", not an "update".
    Make sure your Mac meets Snow Leopard's requirements here.
    You must have the minimum of v10.6.6 installed in order to access the App Store.
    You can purchase Snow Leopard here > Mac OS X 10.6 Snow Leopard - Apple Store

  • IN REPETATIVE AREA ATTER 9 RECORDS, LOWER BORDER  FOR 10 RECORD NOT FOR ALL

    LOWER BORDER  FOR 10 RECORD NOT FOR ALL RECORDS  (remaining 9 records)
    please clarify as much as possible

    hi Uday
    you have to tell the subject shart & sweet and give the message according to the subject elaborate and clearly.
    then which area do you want to see ?
    regards

  • WHY FREE ITUNES PRODUCTS ARE AVAILABLE ONLY FOR USA AND NOT FOR OTHER USERS OUTSIDE USA

    I am so impressed wit the welcome page saying "Join the conversation. Share tips and solutions with fellow Apple product users from all around the world."
    Apple mentioned for their products users around the world but many of their free itunes products are available only for USA and not for the users from the other side of the globe?
    Is this Apple a fair and customer oriented company or full of bias and Only money oriented company.
    If apple could not make thier other FREE stuffs available outside US territory then better for thsi company to just sell their products in USA. its just so disgusting...  If we need a certain apps (FREE APPS) available only for US based users.
    If you think US users and other country users are paying the same prices for their iPad 3G/4G WIFI 64GB and iPhone 3G/4G 64 GB like hat I did having the 2 gadgets altogether but my investment ends to disgusting as the apple company cound not treat people equal then.....  I want to return all this **** stuffs

    iTunes for Different Countries
    iTunes Store: Which types of items can I buy in my country?

  • DROP TABLE works through SSMS but not via T-SQL Query

    Hello All,
    I am trying to drop a number of tables (1,000+) in a particular database by scripting the actions in T-SQL. When I run the query I get error 3701 on every table which points to a permissions issue. However, I am able to delete tables one by one using
    the tree-view in the SSMS Object Explorer. 
    1. I have tried starting query sessions with both the DBO of the database and the SA account to no avail. (Both had the sysadmin role when I tried.)
    2. Both the DBO account and the SA account are able to drop tables using SSMS Object Explorer.
    Do I need a specific GRANT of permissions to use T-SQL versus SSMS or am I missing something even more fundamental?
    TIA, Simon
    <code>
    DECLARE @Company VARCHAR(max), 
    @ID VARCHAR(max), 
    @NAME VARCHAR(max), 
    @TABLE_CATALOG VARCHAR(max),
    @NAV_DATABASE VARCHAR(max),
    @TABLE_NAME VARCHAR(max), 
    @STATEMENT VARCHAR(max),
    @OBJECT_NAME VARCHAR(max),
    @OBJECT_NAME_BARE VARCHAR(max),
    @OBJECT_TYPE VARCHAR(max);
    SET @TABLE_CATALOG = 'NAV_PENTA_TEST_GAAP';
    SET @NAV_DATABASE = @TABLE_CATALOG
    IF @TABLE_CATALOG <> DB_NAME() 
    BEGIN
    DECLARE @ERRORMSG VARCHAR(max);
    SET @ERRORMSG =  'You are not in the correct database. You specified ' + @TABLE_CATALOG + ' but you are currently in a session for ' + db_name();
    RAISERROR(@ERRORMSG, 18, 1);
    RETURN;
    END;
    -- To hold the object names (tables) from Navision
    CREATE TABLE #NavisionObjects
    [CompanyName]
    VARCHAR(max),
    [ID] VARCHAR(max),
    [Name]
    VARCHAR(max),
    [TABLE_NAME]
    VARCHAR(max)
    -- To hold the object names (tables) from SQL only
    CREATE TABLE #NavisionSQLObjects
    [TABLE_NAME]
    VARCHAR(max)
    -- Holds the list of dependent objects
    CREATE TABLE #DependentObjects
    [name] VARCHAR(max),
    [type] VARCHAR(max)   
    WITH T AS (
    SELECT [Company Name],[ID],[Name],[Company Name]+'$'+[Name] AS TABLE_NAME 
    FROM [Object]   
    WHERE [Name] like '%IT IS%' AND [Company Name]>''
    UNION ALL
    SELECT [Company Name],[ID],[Name],[Name] AS TABLE_NAME 
    FROM [Object]   
    WHERE [Name] like '%IT IS%' AND [Company Name] IN ('',' ')
    INSERT INTO #NavisionObjects SELECT [Company Name],[ID],[Name],[TABLE_NAME] FROM T;
    UPDATE #NavisionObjects SET TABLE_NAME = TABLE_NAME+ID WHERE ID LIKE '1%';
    INSERT INTO #NavisionSQLObjects 
    SELECT TABLE_NAME from INFORMATION_SCHEMA.TABLES 
    WHERE TABLE_CATALOG = @TABLE_CATALOG AND TABLE_NAME LIKE '%IT IS%' AND TABLE_TYPE='BASE TABLE';
    --SELECT * FROM #NavisionObjects where CompanyName like 'E15%' order by TABLE_NAME;
    --SELECT * FROM #NavisionSQLObjects where TABLE_NAME like 'E15%' order by TABLE_NAME;
    DECLARE cTables CURSOR FOR SELECT A.CompanyName,A.ID,A.[TABLE_NAME] FROM #NavisionObjects A
    INNER JOIN #NavisionObjects B ON B.[TABLE_NAME]=A.[TABLE_NAME]
    OPEN cTables;
    FETCH NEXT FROM cTables INTO @Company,@ID,@TABLE_NAME;
    WHILE (@@FETCH_STATUS = 0)
    BEGIN
    PRINT 'Storing dependencies for [' + @TABLE_NAME + ']';
    BEGIN TRY
    INSERT INTO #DependentObjects 
    EXEC sp_depends @TABLE_NAME;
    END TRY
    BEGIN CATCH
    PRINT 'Could not get dependencies for table [' + @TABLE_NAME + ']';
    END CATCH
    FETCH NEXT FROM cTables INTO @Company,@ID,@TABLE_NAME;
    END
    CLOSE cTables;
    Drop dependent objects first so that table drops are less likely to fail. 
    DECLARE cdo CURSOR FOR SELECT [Name],[Type] FROM #DependentObjects;
    OPEN cdo;
    FETCH NEXT FROM cdo INTO @OBJECT_NAME, @OBJECT_TYPE;
    WHILE (@@FETCH_STATUS = 0)
    BEGIN
    BEGIN TRY
    SET @OBJECT_NAME_BARE = 
    CASE 
    WHEN CHARINDEX('dbo',@OBJECT_NAME) = 1
    THEN RIGHT(@OBJECT_NAME,LEN(@OBJECT_NAME)-4)
    ELSE @OBJECT_NAME
    END;
    SET @STATEMENT = 'DROP ' + @OBJECT_TYPE + ' [' + @OBJECT_NAME_BARE + ']';
    PRINT @STATEMENT;
    EXEC sys.sp_sqlexec @STATEMENT;
    END TRY
    BEGIN CATCH
    PRINT 'Could not DROP object [' + @OBJECT_NAME + '] of type ' + @OBJECT_TYPE + ', SQL Error ' + CAST(@@ERROR AS VARCHAR(max));
    END CATCH
    FETCH NEXT FROM cdo INTO @OBJECT_NAME, @OBJECT_TYPE;
    END
    CLOSE cdo;
    DEALLOCATE cdo;
    OPEN cTables;
    FETCH NEXT FROM cTables INTO @Company,@ID,@TABLE_NAME;
    WHILE (@@FETCH_STATUS = 0)
    BEGIN
    PRINT 'Removing [' + @TABLE_NAME + ']' ;
    BEGIN TRY
    SET @STATEMENT = 'TRUNCATE TABLE dbo.[' + @TABLE_NAME + ']';
    PRINT @STATEMENT;
    EXEC sys.sp_sqlexec @STATEMENT;
    END TRY
    BEGIN CATCH
    PRINT 'Could not truncate table [' + @TABLE_NAME + ']';
    END CATCH
    BEGIN TRY
    SET @STATEMENT = 'DROP TABLE dbo.[' + @TABLE_NAME + ']';
    PRINT @STATEMENT;
    EXEC sys.sp_sqlexec @STATEMENT;
    BEGIN TRY
    SET @STATEMENT = 'DELETE FROM [Object] WHERE [Company Name] = ' + CHAR(39) + @Company + CHAR(39) + ' AND [ID] = ' + CHAR(39) + @ID + CHAR(39) + ' AND [TABLE_NAME] = ' + CHAR(39) +
    @TABLE_NAME + CHAR(39) ;
    EXEC sys.sp_sqlexec @STATEMENT;
    print @STATEMENT;
    END TRY
    BEGIN CATCH
    PRINT 'Could not Delete Object [' + @TABLE_NAME + '], from Object table, SQL Error ' + CAST(@@ERROR AS VARCHAR(max));
    END CATCH
    END TRY
    BEGIN CATCH
    PRINT 'Could not DROP table [' + @TABLE_NAME + '], SQL Error ' + CAST(@@ERROR AS VARCHAR(max));
    END CATCH
    FETCH NEXT FROM cTables INTO @Company,@ID,@TABLE_NAME;
    END
    CLOSE cTables;
    DEALLOCATE cTables;
    DROP TABLE #DependentObjects;
    DROP TABLE #NavisionObjects;
    DROP Table #NavisionSQLObjects;
    </code>

    3701 = ...does not exist or you don't have permission.
    Most of the time it means the former. So there are probably some problems in your DROP TABLE statements. Since there is a whole lot about Navision in the script, I decline from trying to figure out what. But I encourage you to study the PRINT statements.
    I think that it would be a good idea to include the schema name, in cases these tables are not in dbo after all.
    Note: rather than writing:
       SET @STATEMENT = 'DROP ' + @OBJECT_TYPE + ' [' + @OBJECT_NAME_BARE + ']';
    write:
       SET @STATEMENT = 'DROP ' + @OBJECT_TYPE + quotename(@OBJECT_NAME_BARE)
    Somewhat briefer. And it works also when the object name includes a right bracket.
    sp_sqlexec is undocumented, use sp_executesql instead.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Spry Table works in Firefox but not IE

    I have a Spry table working just fine in Firefox in a site
    I'm developing:
    http://www.abenaki.com/newsite/schedule.html,
    but in IE 6 and 7 it first shows the table, unpopulated, and then
    disappears altogether. I'm new to Spry and XML... have I done
    something wrong? Any light anyone could shed would be hugely
    appreciated! Thank you!!
    The XML looks like this:
    <?xml version="1.0" encoding="utf-8"?>
    <courses>
    <course id="1">
    <name>New! Introduction to Social Assistance and Case
    Management</name>
    <location>Winnipeg</location>
    <startdate>10 21 2008</startdate>
    <duration>4 days</duration>
    <price>$1695</price>
    <desc>This course covers the setup, daily and periodic
    procedures for Abenaki’s Social Assistance and Case
    Management Module.Topics to be covered include: organization
    profile setup, rate maintenance, security, vendor and client
    maintenance, cheque production in Sage Accpac, cheque production in
    the Social Assistance module, reports, case planning, month and
    year end processing.</desc>
    </course>
    <course id="2">
    <name>Introduction to Safe Water Infrastructure
    Management System</name>
    <location>Moncton</location>
    <startdate>10 28 2008</startdate>
    <duration>2 days</duration>
    <price>$1295</price>
    <desc>No description available at this
    time.</desc>
    </course>
    <course id="3">
    <name>Introduction to Housing Inspection and Management
    System</name>
    <location>Moncton</location>
    <startdate>10 30 2008</startdate>
    <duration>1 day</duration>
    <price>$495</price>
    <desc>This introductory level course covers all of the
    steps involved in the data entry and report generation for housing
    units in the community. Topics to be covered include: rating the
    condition and estimated cost to repair of the interior, exterior,
    amenities, fire and health hazard items. Students will learn how to
    generate reports to identify housing units in need of minor or
    major repairs and those units that are potential fire and/or health
    hazard.</desc>
    </course>
    <course id="4">
    <name>New! Post Secondary Education and Student
    Tracking</name>
    <location>Winnipeg</location>
    <startdate>11 12 2008</startdate>
    <duration>3 days</duration>
    <price>$1595</price>
    <desc>No description available at this
    time.</desc>
    </course>
    <course id="5">
    <name>New! Introduction to Social Assistance and Case
    Management</name>
    <location>Edmonton</location>
    <startdate>11 18 2008</startdate>
    <duration>4 days</duration>
    <price>$1695</price>
    <desc>This course covers the setup, daily and periodic
    procedures for Abenaki’s Social Assistance and Case
    Management Module.Topics to be covered include: organization
    profile setup, rate maintenance, security, vendor and client
    maintenance, cheque production in Sage Accpac, cheque production in
    the Social Assistance module, reports, case planning, month and
    year end processing.</desc>
    </course>
    <course id="6">
    <name>Introduction to Safe Water Infrastructure
    Management System</name>
    <location>Edmonton</location>
    <startdate>11 18 2008</startdate>
    <duration>2 days</duration>
    <price>$1295</price>
    <desc>No description available at this
    time.</desc>
    </course>
    <course id="7">
    <name>Introduction to Housing Inspection and Management
    System</name>
    <location>Edmonton</location>
    <startdate>11 20 2008</startdate>
    <duration>1 day</duration>
    <price>$495</price>
    <desc>This introductory level course covers all of the
    steps involved in the data entry and report generation for housing
    units in the community. Topics to be covered include: rating the
    condition and estimated cost to repair of the interior, exterior,
    amenities, fire and health hazard items. Students will learn how to
    generate reports to identify housing units in need of minor or
    major repairs and those units that are potential fire and/or health
    hazard.</desc>
    </course>
    <course id="8">
    <name>Sage Accpac ERP 5.5 Refresher</name>
    <location>Moncton</location>
    <startdate>01 20 2009</startdate>
    <duration>4 days</duration>
    <price>$1695</price>
    <desc>No description available at this
    time.</desc>
    </course>
    <course id="9">
    <name>Sage Accpac ERP 5.5 General Ledger and Accounts
    Payable</name>
    <location>Winnipeg</location>
    <startdate>01 20 2009</startdate>
    <duration>4 days</duration>
    <price>$1695</price>
    <desc>No description available at this
    time.</desc>
    </course>
    </courses>
    Abenaki Course
    Schedule

    The reason its not working its because its "crashing" at the
    sort function in IE, I have no clue why.
    To be more specific,, this part of the SpryData.js
    if (this.unfilteredData)
    this.unfilteredData.sort(sortfunc);
    if (this.filterFunc)
    this.filter(this.filterFunc, true);
    else
    /*this->*/ this.data.sort(sortfunc);
    Maby try to delete the setColumnType for your startdate, to
    see if that helps. Because your startdate is not a "valid" date
    string. (i think)

  • Built app with subpanels works for me, but not for him

    Using labview 8.6 I have successfully built several revisions of an app that has multiple subpanels.  It has successfully executed on several different hosts.   However, with the most recent version I received a report that it launches, but the sub-panels do not load.  Of course, WFM (works for me) -- the sub-panels are compiled into the app and they load just fine for me.  The other user is using the free 8.6 LabView runtime.  Again, previous app revisions have worked fine, and I don't know what is different about this build that could affect loading of the subpanels.
    On my PC I renamed the path to the source files just in case the built app was picking up some missing file directly from the original VI directory.  Still works for me.  I even monitored it with FileMon (sysinternals.com) and confirmed that it never tried to open any other file (which further confirms that all the sub-panels are successfully incorporated into the built application).
    The only other significant difference is that the app is designed for 1280x1024 screen and the other user is running on a 1024x768 laptop.  But how could that affect loading the sub-VIs?
    Does anyone have any idea what would cause a built application with subpanels to work fine on one host but not display the sub-panels on another host?
    Thanks and Best Regards,
    J.

    How are you getting the software on the other computer? Did you build an installer?
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • ISync works for iCal but not for Address Book

    Another lost soul. Can anybody suggest where I should start looking for the problem.
    I've just successfully modified my iSync so that it sees my brand new Nokia 6300. I have got the phone and my iMac to sync my calendar, but absolutely zero activity on the contacts front.
    Looking at the message on my Nokia, the Synchronisation Info message records changes to the Calendar but makes no mention of the Contacts. It is as if I've switched off the requirement to sync these somewhere.
    Any ideas for where to look?
    Frances

    I followed the instructions on http://kaspers.freeflux.net/blog/archive/2007/04/13/how-to-isync-a-nokia-6300.ht ml , including simply replacing my MetaClasses.plist with his. The site blog shows this worked for lots of people, but not for me
    Over the years I have found these Apple Discussion lists a very useful source of help, but I don't think I have ever come across a list with so many frantic pleas for help as this! ISync is a wonderful Idea, but it seems that it is far from plain sailing to implement.

Maybe you are looking for