ORA-19201: Datatype not supported when validating XML against an XSD

Hello.
Info: using Oracle 10.2.0.1.0, Java components are installed.
I've created an XML view using ora:view, which is validated against a registered XSD. This view is created successfully.
But when I SELECT * from this view, it gives ORA-19201 - Datatype not supported.
Can't understand why. I've matched the XML to the XSD, and the datatypes all look fine to me. I've referred to the XSD using the XMLFORMAT.CREATEFORMAT option. When I use the same option to specify "NO_SCHEMA", it returns the correct XML, but we need to validate it against the XSD.
I'm thinking one of two things has happened here:
1. I've made a mistake with either my registration, or how I've used XMLFORMAT to refer to the XSD.
2. There's a bug in Oracle.
My money's on 1. Can anyone help?
Thanks,
Ray.

Hello Geoff, I didn't want to send any code until I knew someone was willing to look at it (there's a lot of it).
Here is the XSD:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--W3C Schema generated by XMLSpy v2006 rel. 3 sp1 (http://www.altova.com)-->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
     <xs:element name="TransInfo">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="PIE_ERROR" type="PIE_ERRORType" minOccurs="0"/>
                    <xs:element name="Transaction" type="TransactionType" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="PIE_ERRORType">
          <xs:sequence>
               <xs:element ref="ERROR_CODE"/>
               <xs:element ref="DESCRIPTION"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="ERROR_CODE">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="0001"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="DESCRIPTION">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="LEAD NUMBER 12345 IS INVALID"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="TransactionType">
          <xs:sequence>
               <xs:element ref="TRANSACTION_NUMBER"/>
               <xs:element ref="TRANSACTION_STATUS"/>
<xs:element ref="CONTACT_ID"/>
               <xs:element ref="INVOICE_NUMBER"/>
               <xs:element ref="CHANNEL"/>
               <xs:element ref="CSA"/>
               <xs:element ref="OPEN_DATETIME"/>
               <xs:element ref="CLOSED_DATETIME"/>
               <xs:element name="Orderline" type="OrderlineType" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="TRANSACTION_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="3455229"/>
                    <xs:enumeration value="3455230"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TRANSACTION_STATUS">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="C"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CONTACT_ID">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="111"/>
                    <xs:enumeration value="222"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="INVOICE_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="123456789"/>
                    <xs:enumeration value="987654321"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CHANNEL">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Test 1"/>
                    <xs:enumeration value="Test 2"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CSA">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="SEARLEA"/>
                    <xs:enumeration value="SILVAJ"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="OPEN_DATETIME">
          <xs:simpleType>
               <xs:restriction base="xs:dateTime">
                    <xs:enumeration value="2001-10-26T20:32:52"/>
                    <xs:enumeration value="2004-12-06T10:23:25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CLOSED_DATETIME">
          <xs:simpleType>
               <xs:restriction base="xs:dateTime">
                    <xs:enumeration value="2001-10-26T21:32:52"/>
                    <xs:enumeration value="2004-12-06T10:23:25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="OrderlineType">
          <xs:sequence>
               <xs:element ref="ORDER_QTY"/>
               <xs:element ref="RETAIL_AMT"/>
               <xs:element ref="SALE_AMT"/>
               <xs:element ref="PRODUCT_DESCR"/>
               <xs:element ref="PART"/>
               <xs:element ref="IMEI"/>
               <xs:element name="BankDetails" type="BankDetailsType"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="ORDER_QTY">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="1"/>
                    <xs:enumeration value="3"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="RETAIL_AMT">
          <xs:simpleType>
               <xs:restriction base="xs:decimal">
                    <xs:enumeration value="45.67"/>
                    <xs:enumeration value="54.76"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="SALE_AMT">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="45.67"/>
                    <xs:enumeration value="54.76"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PRODUCT_DESCR">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Product test 2"/>
                    <xs:enumeration value="Vodafone Nokia 6230 Pack"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PART">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="6806"/>
                    <xs:enumeration value="8606"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="IMEI">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="099000000000001"/>
                    <xs:enumeration value="09900078900001"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="BankDetailsType">
          <xs:sequence>
               <xs:element ref="BANK_NAME"/>
               <xs:element ref="ACCOUNT_NAME"/>
               <xs:element ref="ACCOUNT_NUMBER"/>
               <xs:element ref="SORT_CODE"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="BANK_NAME">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="HSBC"/>
                    <xs:enumeration value="LLOYDS"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="ACCOUNT_NAME">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="MR A SEARLE"/>
                    <xs:enumeration value="MR J SILVA"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="ACCOUNT_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="87698789"/>
                    <xs:enumeration value="89769082"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="SORT_CODE">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="100928"/>
                    <xs:enumeration value="123346"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
</xs:schema>
I then registered this XSD using DBMS_XMLSCHEMA.REGISTER, calling it test_1.xsd. It is visble in USER_XML_SCHEMAS.
Here are the 15 views used to drive the XML:
SQL> desc v_pie_branch
Name Null? Type
BRANCH NOT NULL NUMBER(4)
SQL> desc v_pie_branch_feature
Name Null? Type
BRANCH_FEATURE NOT NULL NUMBER(10)
BRANCH NUMBER(4)
FEATURE_TYPE VARCHAR2(10)
CHANNEL VARCHAR2(40)
SQL> desc v_pie_transaction
Name Null? Type
TRANSACTION_NUMBER NOT NULL NUMBER(10)
BRANCH NUMBER(4)
EMPLOYEE_TRANS VARCHAR2(12)
CONTACT NUMBER(8)
OPEN_DAT DATE
OPEN_TIM DATE
TRANSACTION_STATUS VARCHAR2(1)
TRANS_TYPE VARCHAR2(1)
CLOSED_DAT DATE
CLOSED_TIM DATE
INVOICE_NUMBER NUMBER(10)
INVOICE_DAT DATE
CSA VARCHAR2(12)
CREATED_ON DATE
AMENDED_BY VARCHAR2(12)
AMENDED_ON DATE
OPEN_DATETIME VARCHAR2(19)
CLOSED_DATETIME VARCHAR2(19)
SQL> desc v_pie_bank_detail
Name Null? Type
BANK_DETAIL NOT NULL NUMBER(12)
BANKCODE VARCHAR2(40)
SORTCODE VARCHAR2(40)
BANK_NAME VARCHAR2(60)
SQL> desc v_pie_account_detail
Name Null? Type
ACCOUNT_DETAIL NOT NULL NUMBER(12)
BANK_DETAIL NUMBER(12)
ACCOUNT_NUMBER VARCHAR2(40)
SORT_CODE VARCHAR2(40)
ACCOUNT_NAME VARCHAR2(40)
BANKCODE VARCHAR2(40)
SQL> desc v_pie_account_link
Name Null? Type
ACCOUNT_LINK NOT NULL NUMBER(12)
CONTACT NUMBER(12)
ACCOUNT_DETAIL NUMBER(12)
ACC_LINK_TYP NUMBER(12)
BNK_SINCE DATE
AC_DET VARCHAR2(40)
SQL> desc v_pie_compesn
Name Null? Type
COMPESN NOT NULL NUMBER(10)
CONTACT NUMBER(8)
IMEI VARCHAR2(25)
SQL> desc v_pie_contact
Name Null? Type
CONTACT_ID NOT NULL NUMBER(8)
CONTACT_TYP VARCHAR2(1)
COMPANY NUMBER(10)
BRANCH NUMBER(4)
DEAD_FLG VARCHAR2(1)
FORENAME VARCHAR2(20)
TITLE VARCHAR2(5)
MID_INITIAL VARCHAR2(1)
GENDER VARCHAR2(1)
FRAUD_FLG VARCHAR2(1)
SQL> desc v_pie_servcon
Name Null? Type
SERVCON NOT NULL NUMBER(10)
CONTRACT NUMBER(10)
CONNECTION_CURR NUMBER(10)
CONTACT NUMBER(8)
SQL> desc v_pie_tpplan_compline
Name Null? Type
TPPLAN_COMPLINE NOT NULL NUMBER(10)
SERVCON NUMBER(10)
PPLAN NUMBER(10)
SQL> desc v_pie_tpplan_comp_detail
Name Null? Type
TPPLAN_COMPLINE NOT NULL NUMBER(10)
RULE_DETAIL_NO NOT NULL VARCHAR2(5)
RULE_DETAIL_LINE NOT NULL NUMBER(2)
U_VERSION VARCHAR2(1)
OPTION VARCHAR2(40)
OPT_STRING VARCHAR2(40)
SQL> desc v_pie_tpplan
Name Null? Type
SERVCON NOT NULL NUMBER(10)
PPLAN NOT NULL NUMBER(10)
U_VERSION VARCHAR2(1)
SQL> desc v_pie_connection
Name Null? Type
CONNECTION NOT NULL NUMBER(10)
CONTACT NUMBER(8)
ADDRESSNO NUMBER(5)
TRANSACTION NUMBER(10)
TPRODLINE NUMBER(10)
CONTRACT NUMBER(10)
SERVCON NUMBER(10)
SQL> desc v_pie_tprodline
Name Null? Type
TRANSACTION NOT NULL NUMBER(10)
TPRODLINE NOT NULL NUMBER(10)
CONTACT NUMBER(8)
PRODUCT NUMBER(10)
ORDER_QTY NUMBER(12)
RETAIL_AMT NUMBER
SALE_AMT NUMBER
SQL> desc v_pie_product
Name Null? Type
PRODUCT NOT NULL NUMBER(10)
PART VARCHAR2(20)
PRODUCT_DESCR VARCHAR2(40)
This is the code to create an XML view, validating against the schema:
create OR REPLACE VIEW v_xml_validate AS
SELECT SYS_XMLAGG(XMLQuery('
<PIE_ERROR>
<ERROR_CODE>"0001"</ERROR_CODE>
<DESCRIPTION>"There was an error with this customer"</DESCRIPTION>
</PIE_ERROR>,
<Transaction>
{for $t in ora:view("V_PIE_TRANSACTION")/ROW
    ,$ct in ora:view("V_PIE_CONTACT")/ROW
    ,$b in ora:view("V_PIE_BRANCH")/ROW
    ,$bf in ora:view("V_PIE_BRANCH_FEATURE")/ROW
where $t/CONTACT = $ct/CONTACT_ID
and   $t/BRANCH = $b/BRANCH
and   $b/BRANCH = $bf/BRANCH
return ($t/TRANSACTION_NUMBER
        ,$t/TRANSACTION_STATUS
        ,$ct/CONTACT_ID
        ,$t/INVOICE_NUMBER
        ,$bf/CHANNEL
        ,$t/CSA
        ,$t/OPEN_DATETIME
        ,$t/CLOSED_DATETIME
        ,<Orderline>
              {for $tpl in ora:view("V_PIE_TPRODLINE")/ROW
                  ,$pr  in ora:view("V_PIE_PRODUCT")/ROW
                  ,$cmpesn  in ora:view("V_PIE_COMPESN")/ROW
               where $tpl/TRANSACTION eq $t/TRANSACTION_NUMBER
               and   $tpl/PRODUCT eq $pr/PRODUCT
               and   $ct/CONTACT_ID eq $cmpesn/CONTACT
               return ($tpl/ORDER_QTY
                      ,$tpl/RETAIL_AMT
                      ,$tpl/SALE_AMT
                      ,$pr/PRODUCT_DESCR
                      ,$pr/PART
                      ,$cmpesn/IMEI
                      ,<BankDetails>
                           {for $conn in ora:view("V_PIE_CONNECTION")/ROW
                            for $scon in ora:view("V_PIE_SERVCON")/ROW
                            for $tpp in ora:view("V_PIE_TPPLAN")/ROW
                            for $tppc in ora:view("V_PIE_TPPLAN_COMPLINE")/ROW
                            for $tppcd in ora:view("V_PIE_TPPLAN_COMP_DETAIL")/ROW
                            for $al in ora:view("V_PIE_ACCOUNT_LINK")/ROW
                            for $ad in ora:view("V_PIE_ACCOUNT_DETAIL")/ROW
                            for $bd in ora:view("V_PIE_BANK_DETAIL")/ROW
                            where $conn/CONTACT eq $ct/CONTACT_ID
                            and   $scon/CONTACT eq $conn/CONTACT
                            and   $tpp/SERVCON eq $scon/SERVCON
                            and   $tppc/SERVCON eq $tpp/SERVCON
                            and   $tppc/PPLAN eq $tpp/PPLAN
                            and   $tppcd/TPPLAN_COMPLINE eq $tppc/TPPLAN_COMPLINE
                            and   $al/AC_DET eq $tppcd/OPT_STRING
                            and   $ad/ACCOUNT_DETAIL eq $al/ACCOUNT_DETAIL
                            and   $bd/BANK_DETAIL eq $ad/BANK_DETAIL
                            return ($bd/BANK_NAME
                                   ,$ad/ACCOUNT_NAME
                                   ,$ad/ACCOUNT_NUMBER
                                   ,$ad/SORT_CODE
</BankDetails>
</Orderline>
</Transaction>'
RETURNING CONTENT),
XMLFORMAT.CREATEFORMAT('TransInfo','USE_GIVEN_SCHEMA','test_1.xsd', 'http://xmlns.cpw.co.uk/CPW/EPOS/Order/RetrieveTransaction/RetrieveTransaction', NULL, NULL)) AS xml_string FROM DUAL;
The view is created with no errors. Selecting * from it, however, gives:
ORA-19201 - Datatype not supported
Marrying the XML to the XSD shows nothing obviously wrong.
Thanks,
Ray.

Similar Messages

  • When validating XML against XSD DateTime not getting recognised

    In the XSD the element is defined as
    <xs:element name="CreateDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
    <xs:element name="CreateUser" type="xs:string" nillable="true" minOccurs="0"/>
    <xs:element name="ModifyDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
    in the XML
    <CreateDate>1995-04-19 14:37:43</CreateDate>
    <CreateUser>JDC</CreateUser>
    <ModifyDate>2010-09-21 14:37:43</ModifyDate>
    When i validate it
    its throwing me error.
    ORA-30992 error occured at xpath
    ORA-01861 leteral does not match format string.
    But when i remove the Time part then it is not throwing error.
    <CreateDate>1995-04-19</CreateDate>
    <CreateUser>JDC</CreateUser>
    <ModifyDate>2010-09-21</ModifyDate>
    Help me out.

    Your date/time value is formatted incorrectly.
    See http://www.w3.org/TR/xmlschema-2/#dateTime
    The ·lexical space· of dateTime consists of finite-length sequences of characters of the form: '-'? yyyy '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zzzzzz)?, whereSo you are missing the T between the date and time.
    I will agree that the error message is not too helpful. How are you validating it and what version of Oracle (4 digits)?

  • XML Publisher does not create a valid XML file when I try to 'generate '

    I am working through an Oracle document that walks you through creating an XML Pub report. I am using HCM 8.9, Tools 8.49.15 and it has XML Pub installed and I have the Microsoft plug-in installed
    I have created a query and have downloaded an rtf template and now am on a page where you enter your data source and then click ‘Generate’ for the sample data file. I did it and it created ‘PERSONAL_DATA_PAY.XML’ which is created from a PS Query. However if I click on ‘PERSONAL_DATA_PAY.XML’ it generates a blocky text file that is not an XML file and I can’t go any further.
    Do you know why it’s not generating a valid XML file when I click on 'generate'?
    Thanks
    Allen H. Cunningham
    Data Base Administrator - Oracle/PeopleSoft
    Sonoma State University

    On the right click on HD under video quality to filter it. 

  • Unable to load the package as XML because of package does not have a valid XML format

    I have SSIS package and I would like to let SQL Server Agent Job to run it.
    However I get Unable to load the package as XML because of package does not have a valid XML format
    What could be wrong?
    Kenny_I

    Hi Kenny,
    What's the version of your SSIS? Please refer to the following methods to solve this issue:
    Hard code the path of SQL Server 2008's DTEXEC while calling the SSIS package as shown below:
    C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEXEC.exe /F "D:\MyFolder\MyPackage.dtsx"
    Rename the old exe in the 2005 path to a different name (Example:- C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTEXEC_Old.exe)
    Go to PATH environmental variable and edit it in such a way that "C:\Program Files\Microsoft SQL Server\100\DTS\Binn" path appears well before the "C:\Program Files\Microsoft SQL Server\90\DTS\Binn" path.
    For more detail information, please refer to the blog below:
    Failed to open package file due to error 0x80070020. The process cannot access the file because it is being used by another process. This happens when loading a package and the file cannot be opened or loaded correctly into the XML document:
    http://blogs.msdn.com/b/ramoji/archive/2009/08/28/failed-to-open-package-file-due-to-error-0x80070020-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process-this-happens-when-loading-a-package-and-the-file-cannot-be-opened-or-loaded-correctly-into-the.aspx
    A similar thread about this topic for your reference:
    http://social.technet.microsoft.com/Forums/en-US/b2987df5-8c9b-4797-bdce-b9ec308731f6/i-am-getting-error-when-running-ssis-package-using-sql-server-agent-error-description-is-unable-to?forum=sqlintegrationservices
    If you have any feedback on our support, please click
    here.
    Elvis Long
    TechNet Community Support

  • XML Publisher question - Not generating a valid XML file

    I am working through an Oracle document that walks you through creating an XML Pub report. I am using HCM 8.9, Tools 8.49.15 and it has XML Pub installed and I have the Microsoft plug-in installed
    I have created a query and have downloaded an rtf template and now am on a page where you enter your data source and then click ‘Generate’ for the sample data file. I did it and it created ‘PERSONAL_DATA_PAY.XML’ which is created from a PS Query. However if I click on ‘PERSONAL_DATA_PAY.XML’ it generates a blocky text file that is not an XML file and I can’t go any further.
    Do you know why it’s not generating a valid XML file when I click on 'generate'?
    Thanks
    Allen H. Cunningham
    Data Base Administrator - Oracle/PeopleSoft
    Sonoma State University

    You mean to say that you create a new data source by specifying Data Source Type as 'PS Query' and Data Source ID as your query name, you are not able to generate a valid XML file (by clicking on Generate link).
    did you cross check your query by running it?
    On field change of Generate link, PeopleSoft uses PSXP_RPTDEFNMANAGER and PSXP_XMLGEN app packagaes and query objects to create the file
    It should work if you query is valid..

  • HTTP response does not contain a valid XML root tag

    I am running into an error in my trace portion of my XML when executing my application. The error is  "HTTP response does not contain a valid XML root tag". The HTTP request is successful with message 200 so it seems to be accepted by the Integration Engine. I looked for other posts on this error and only found one and it didn't show the resolution. Any help would be appreciated.

    Hello
    Check these notes (do you use a split mapping?):
    1) 1515230     XI mapping: "Root tag missing" in split mapping
    2)  1640553     XI mapping: Split mapping: error Missing_Interface
    Regards
    Mark

  • "charging is not supported" when using the cable that came with ipod

    I get an error message that "charging is not supported" when plugged in using the only cable that came with my ipod touch. My ipod will charge for 5 minutes then when I check on it, I notice this error on screen and the ipod has stopped charging.  I'm using the same charging method I have always used since I owned this ipod which has been over 2 years now and this only started happening recently. I believe this started when I upgraded to 5.0.1.

    - Look at both partsof the 30 pin dock connector.  Log for bent. mising or corroded contacts of orther abnormalities. The cable could be bad.  Try a new one.
    - Try a reset. Nothings is lost.
    Reset iPod touch:  Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.

  • IPod Nano 7th Gen says "Unsupported. Accessory is not supported" when trying to charge / sync

    iPod Nano 7th Gen says "Unsupported. Accessory is not supported" when trying to charge / sync with official apple lightening cable.
    It worked for almost a year then suddenly began to say that. My computer [windows], lightening cable and my power brick [all apple official] are all the same as they were when it was working. The iPod is almost a year old now, and has worked perfectly up until about a week ago.
    I have tried resetting the iPod, plugging it into different charging sources but it keeps saying "Unsupported. Accessory is not supported"
    Does anyone have any ideas on how to fix it?
    Thanks.

    Your iPod Nano firmware and iTunes updated to the current versions? 
    It is very difficult to offer troubleshooting suggestions when the "os version" you are using is unknown as each os has their own troubleshooting solutions. 

  • I have a vizio led 26" but displays not support when I connect to my MacBook pro

    I have a vizio led 26" but displays not support when I connect to my MacBook pro

    Hello, Benlot.
    You may find this article helpful in troubleshooting the external display issue.
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/ht1573
    Cheers,
    Jason H.

  • Tv not supported when connecting HDMI to ipad 30 pin connector running ios 8

    tv not supported when connecting HDMI to ipad-2 30 pin connector running ios 8.  Was working fine with ios 7.

    Hello,
    I need to conect it to either a mouse or an OLED display to transfer the content I was going to use thee standard charging USB to a port splitter and sending it from there but I wanted to check before I did something stupid.
    Thanks.
    James

  • Keep getting accessory not supported when charging in romania.  I have a converter for wall and a att USB cord

    Keepgettimg accessory not supported when charging in romania. I have all the correct connections. ie wall converter, USB cord etc.

    If you know the IP address of the printer, then you can check if there is a working path between the Mac and printer. This can be done using Network Utility or a web browser.
    If you open Network Utility and select the Ping tab, you can enter the IP address of the Kodak and then press the Ping button. If there is a working connection then you should get a reply to each packet sent.
    With the web browser, many devices have a built-in web server so you can type the IP address of the printer into the browser and if there is a working connection then you will open the printers web page.
    So, are you able to confirm you have a working connection between the Mac and printer?

  • Why charger saying not supported when it is a genuine apple charger

    Why charger saying not supported when it is a genuine apple charger

    Do you mean the AC wall adapter or the cable when you say "charger"? Neither is a charger; the charger is built into the phone. You need to do some basic troubleshooting. First, try a different cable with the same AC adapter. Then try a different USB source such as the USB port on your computer. If you get the same message after both tests the problem lies in the phone. The most common cause of this message is dirt, moisture or pocket lint in the lightning connector on the bottom of the phone. Inspect it with a bright light and clean it with a plastic or wood toothpick. If none of these steps resolve the problem take the phone, cable and adapter to an Apple store for diagnosis. Make an appointment first: http://concierge.apple.com/reservation/us/en/techsupport/
    Note: You should register the iPhone on Apple's website first, if it isn't already registered: https://supportprofile.apple.com/. This will speed up the appointment process.

  • Does XDB supports validating xml against multiple schemas?

    The XMLType has some methods for validating an xml documents against a schema, e.g., SCHEMAVALIDATE, etc.. does XDB support validating xml against multiple schemas (Just like what JAXP or Xerces have done)? Or what's the current situation about this issue? thanks.

    did you try using the import schema element instead of the include elemnt?

  • MetaData operations are not supported when

    Dear Experts
    I am facing below error when trying to run my add-on in Windows  Server 2008 R2 and SQL Server 2008 service pack 2.
    Error: MetaData operations are not supported when a user transaction is active
    It runs fine in Sql Server 2005.
    Kindly tell me a solution to sort this out.
    Regards
    Shibin

    Can we see your code, it looks to me like the error is quite descriptive - its saying you can't do any metadata operation (creating/updating user fields, user tables using userfieldsMD or usertablesMD objects) while in a transaction.
    Previous SDK examples have shown that you can do it, but they it is not possible - it may be that SQL 2008 has a tighter control over this. (Did you also do a B1 upgrade, or just change SQL version?)
    Are you running a transaction?

  • My July 2009 iMac with OSX Mavericks "iMac is not supported" when I tried to perform bluetooth with my iPhone 5. What is the problem. thanks

    My July 2009 iMac with OSX Mavericks "iMac is not supported" when I tried to perform bluetooth with my iPhone 5. What is the problem. thanks

    Bluetooth is only supported for tethering.
    Barry

Maybe you are looking for