Native XML Database

Does anyone know if DSP will ever ship with a native XML database? It makes sense to me, given the XQuery strategy, that a native XML database would make sense for storing data that is not in an external system.

Can you elaborate a little on what you would like to do?
Currently you can use XQuery and SDO to store and query data in a database. It shouldn't matter if it is a true XML database or Oracle, or something else.
- Mike

Similar Messages

  • Is Oracle XML DB a native xml database?

    Hi!
    XML DB provides native data type XMLTYPE, and it can provide traditional storage for xml. So is it a enabled xml database or a native one??
    Cheers

    It is an XML enabled relational database (XMLType OR storage) but has also native XML database capabilities in the form of binary XML (XMLType Binary XML storage)

  • About this XML database

    Today I have found these definitions:
    1.Native XML Database (NXD):
    a) Defines a (logical) model for an XML document -- as opposed to the data in that document -- and stores and retrieves documents according to that model. At a minimum, the model must include elements, attributes, PCDATA, and document order. Examples of such models are the XPath data model, the XML Infoset, and the models implied by the DOM and the events in SAX 1.0.
    b) Has an XML document as its fundamental unit of (logical) storage, just as a relational database has a row in a table as its fundamental unit of (logical) storage.
    c) Is not required to have any particular underlying physical storage model. For example, it can be built on a relational, hierarchical, or object-oriented database, or use a proprietary storage format such as indexed, compressed files.
    2.XML Enabled Database (XEDB) - A database that has an added XML mapping layer provided either by the database vendor or a third party. This mapping layer manages the storage and retrieval of XML data. Data that is mapped into the database is mapped into application specific formats and the original XML meta-data and structure may be lost. Data retrieved as XML is NOT guaranteed to have originated in XML form. Data manipulation may occur via either XML specific technologies(e.g. XPath, XSL-T, DOM or SAX) or other database technologies(e.g. SQL). The fundamental unit of storage in an XEDB is implementation dependent. The XML solutions from Oracle and Microsoft as well as many third party tools fall into this category.
    3.Hybrid XML Database (HXD) - A database that can be treated as either a Native XML Database or as an XML Enabled Database depending on the requirements of the application. An example of this would be Ozone.
    Which of them would you put XML DB in?

    If we consider the duality of the XMLType (store XML documents in CLOB's and structured storage with XML Schemas), could we say that it is an hybrid XML database?
    Native->CLOB's
    Enabled->structured storage
    I suppose this cuestion is a bit subjective, but I would like to know your opinions.
    Thanks in advance!

  • How to use native XML driver in CR XI 2 (to avoid "Database Logon Failed")?

    Hello,
    I have a simple scenario:
    The Java Part:
    -Our Java application creates a pair of files: one XML and one XSD.
    -Both files are uploaded to an ASP.NET page along with a report (RPT file - based on the same XSD and some generated XML using the native XML driver) for rendering a PDF.
    The ASP.NET(VB) Part:
    -Reads and stores 3 files (XML, XSD and RPT) to temporary files.
    -Loads the report
    -Updates connection attributes ("Local Schema File" and "Local XML File") to point to those temporary files.
    -Exports the report to a PDF which is returned to the Java part.
    What are the correct steps to accomplish this? I keep on getting "Database logon failed." exceptions.
    My code looks like this:
    Dim doc As ReportDocument = New ReportDocument
    doc.Load(rptPath)
    Dim attr As DbConnectionAttributes
    attr = New DbConnectionAttributes()
    attr.Collection.Set("Local Schema File", xsdPath)
    attr.Collection.Set("Local XML File", xmlPath)
    Dim conn As IConnectionInfo
    conn = doc.DataSourceConnections.Item(0)
    conn.Attributes.Collection.LookupNameValuePair("QE_LogonProperties").Value = attr
    conn.Attributes.Collection.LookupNameValuePair("QE_ServerDescription").Value = xmlPath & " " & xsdPath
    conn.Attributes.Collection.LookupNameValuePair("QE_SQLDB").Value = False
    doc.ExportToHttpResponse(ExportFormatType.PortableDocFormat, Response, False, "")
    Thank you for any help,
    David
    (Crystal Reports XI Rel 2. SP4, .NET assembly 11.5.3700)

    Hi,
    When you get a database logon prompt like this it normally means the dataset you're creating at runtime does not match the schema that the report was designed with.
    The simplest thing to do is write out the dataset to XML with Schema after you fill the dataset. Once you've written out the dataset you can go back to the report in Crystal Reports itself and try to point the report to the XML file directly. If you get any errors this confirms that the dataset does not match what the report is expecting.
    Try it, address any differences, and you should be all set.
    Sincerely,
    Amit

  • XML database query through Java

    Hi all.
    I am collecting information about a little application i am trying to build:
    I have an XML database with records divided in a lot of subdirectory (with three or four .xml files);
    directories' names are defined by date in format "yyyymmdd",
    the file within are "date_something.xml":
    what is the best way to access it by a web app or a java class to search all the dirs adn print results in a readable way (aka not in cmd) ? I need first to define a period of time to search and then some attribute or node to print referred to some element.
    I was guessing to use xpath, anyway I ve tryed JSP but it is too difficult and the query i have to do are really simple to build a full servlet.
    I am learning xalan through servlet and I think in future this will be my choice but now i need to collect the data by queries without any automation, just to have results for researching and paper writing.
    The main problem I found is to search a full series of directory, with transformations i can find out stuff from a single file, but how to do it for a system of directories?
    Any suggestion or link to resource would be good also.

    lm00 wrote:
    ProjectMoon wrote:
    By XML database do you mean an actual XML native database, or just a bunch of XML files in a directory structure? If it is an actual XML native database, you should probably use the XML:DB API. If they are just flat files you will need to probably make something that is able to navigate through your directory structure to the documents you want. Once you have that, you can then use XQuery or XPath to get information from those documents.The data is a bunch of directories named by date in format "yyyymmdd", inside each of these there are three or four files .xml
    All files have data definitions and schemas but i dont think they are a 'database'. What do u mean "something to navigate through"? A class? Suppose I would like to do it as a webapp what should i have to do?
    Yes, I basically meant a class. Before querying the XML file you need something that will retrieve its location. If it's by date you could probably concoct something that takes a Date object and returns a set of File objects. Internally it would traverse the directory trees and find the proper XML file(s).
    >>
    If you have a LOT of XML documents I honestly recommend something like the eXist XML Native Database, or another XND. I have been playing with them lately and they are very useful.in this case what i have to do? Take the data and put it into a database by this tool? And then I should acces it by a JSP? There is a program using Xpath instead?Well, yes. You would put the files in the XND. Although I don't know if that's useful or not in your situation. It all depends. I also think you're a bit confused as to what JSPs and XPath are...
    JSPs are just Java Server Pages, which get dynamically compiled into servlets. If you are following the MVC pattern for servlets/JSP (which you should), JSPs represent your views while servlets are the controllers. The model would be your XML data in this case. XPath is a way to get at that data. If it was in an XND, you could just throw an XQuery/XPath expression at the database and it would give you back XML documents/fragments representing the results of your query. You don't have to make your own system to find the XML documents. Of course, you do have to learn how to use an XND.
    Perhaps you should separate what you are trying to do. You have two problems: 1) how to get the XML data you need. 2) How to present it. You should separate those two completely and learn how to do both before attempting to put it together.
    Edited by: ProjectMoon on Oct 21, 2009 12:05 PM

  • Special Character Restrictions for Native XML Driver

    Hi,
    I have found the following special character restrictions in the documentation:
    "Because they are handled specially by the Native XML driver, do not use the following special characters to define element types and attributes in your XML schema:u201C.u201D, u201C/u201D, u201C\u201D, u201C:u201D u201C@u201D."
    After checking the createad XML-Files in our projects that we will use for CR4E there is often a  u201C.u201D in the definition. Because this is delivered from third-party, we wish that the  u201C.u201D  will be enabled.
    In the moment we create the XSD-Files from the XML-File with XML2XSD.
    It is possible in the future?
    Best Regards
    Arnold Meier

    The changes aren't in XI Release 2, but in 2008.
    Do you still have Nha's XML data?  I edited Document_Policy, Policy_AllCoverages, Policy_Beneficiary to Document.Policy, Policy.AllCoverages, Policy.Beneficiary, then use the following code in CR4E 2.0:
    reportClientDocument reportClientDocument;
    ConnectionInfo connectionInfo;
    PropertyBag propertyBag;
    * Connect to the Java Print Engine and create a new document.
    reportClientDocument = new ReportClientDocument();
    reportClientDocument.setReportAppServer(ReportClientDocument.inprocConnectionString);
    reportClientDocument.newDocument();
    * Define connection to the XML and XSD files.
    propertyBag = new PropertyBag();
    propertyBag.put("Local XML File", "C:\\Documents and Settings\\tueda\\Desktop\\nha.xml");
    propertyBag.put("Local Schema File", "C:\\Documents and Settings\\tueda\\Desktop\\nha.xsd");
    propertyBag.put("Convert Multivalue to Table", Boolean.FALSE);
    propertyBag.put("Database DLL", "crdb_xml.dll");
    connectionInfo = new ConnectionInfo();
    connectionInfo.setAttributes(propertyBag);
    * Specify the dataset in the XML as a Table, and add to the report.
    Table table = new Table();
    table.setConnectionInfo(connectionInfo);
    table.setName("Document.Policy/Policy.Beneficiary");
    table.setAlias("Document_Policy/Policy_Beneficiary");
    reportClientDocument.getDatabaseController().addTable(table, null);
    * Save report to file C:\local_xml.rpt
    reportClientDocument.saveAs("nha_local_xml.rpt", "C:\\", ReportSaveAsOptions._overwriteExisting);
    reportClientDocument.close();
    Sincerely,
    Ted Ueda

  • Importing native xml in to semi structured storage

    hello,
    how store the a bibliographic data in the native xml and import or export that data into to the semi structured storage. What are the ways we query the xml database.
    Eagerly waiting for the reply
    Cheers
    Akhil
    Thank you in advance

    Based on a small extension demo-ed in : http://www.liberidu.com/blog/?p=1053 (demo script demo06.sql)
    -- If you can select it you can insert it...
    -- drop table OGH_xml_store purge;
    create table OGH_xml_store of xmltype
    xmltype store as binary xml
    commit;
    exec get_dir_list( 'G:\OGH\xmlstore' );
    set time on timing on
    insert into OGH_xml_store
    select XMLTYPE(bfilename('OGH_USE_CASE',dl.filename),NLS_CHARSET_ID('AL32UTF8')) AS "XML"
    from   dir_list dl
    where  dl.filename like '%.xml';
    set time off timing off
    commit;
    select count(*) from OGH_xml_store;
    prompt pause
    pause
    clear screen
    -- If you can select it you can create resources and files
    set time on timing on
    commit;
    exec get_dir_list( 'G:\OGH\xmlstore' );
    select count(*) from dir_list where filename like '%.xml';
    set serveroutput on size 10000
    DECLARE
      XMLdoc       XMLType;
      res          BOOLEAN;
      v_foldername varchar2(4000) := '/public/OGH/';
      cursor c1
      is
      select dl.filename                                                                  FNAME
      ,      XMLTYPE(bfilename('OGH_USE_CASE',dl.filename),NLS_CHARSET_ID('AL32UTF8')) XMLCONTENT
      from   dir_list dl
      where  dl.filename like '%.xml'
      and rownum <= 100;
    BEGIN
    -- Create XDB repository Folder
    if (dbms_xdb.existsResource(v_foldername))
    then
           dbms_xdb.deleteResource(v_foldername,dbms_xdb.DELETE_RECURSIVE_FORCE);
    end if;
    res:=DBMS_XDB.createFolder(v_foldername);
    -- Create XML files in the XDB Repository
    for r1 in c1
    loop
       if (DBMS_XDB.CREATERESOURCE(v_foldername||r1.fname, r1.xmlcontent))
       then
          dbms_output.put_line(v_foldername||r1.fname);
          null;
       else
          dbms_output.put_line('Loop Exception :'||sqlerrm);
       end if;
    end loop;
    EXCEPTION WHEN OTHERS THEN
      dbms_output.put_line('Others Exception: '||sqlerrm);
    END;
    set time off timing off
    commit;
    prompt pause
    pause
    clear screen
    -- FTP and HTTP
    clear screen
    prompt
    prompt *** FTP - Demo ***
    prompt
    prompt pause
    pause
    host ftp
    -- open localhost 2100
    -- user OGH OGH
    -- cd public
    -- cd OGH
    -- ls
    -- bye
    clear screen
    prompt
    prompt *** Microsoft Internet Explorer - Demo ***
    prompt
    prompt pause
    pause
    host "C:\Program Files\Internet Explorer\IEXPLORE.EXE" http://OGH:OGH@localhost:8080/public/OGH/
    prompt pause
    pause
    -- Accessing the XDB Repository content via Resource View
    -- Selecting content from a resource via XBDUriType
    clear screen
    prompt set long 300
    set long 300
    prompt Relative Path - (path)
    SELECT path(1) as filename
    FROM RESOURCE_VIEW
    WHERE under_path(RES, '/public/OGH', 1) = 1
    and rownum <= 10
    prompt pause
    pause
    clear screen
    prompt Absolute Path - (any_path)
    select xdburitype(any_path).getClob() as xml
    FROM RESOURCE_VIEW
    WHERE under_path(RES, '/public/OGH', 1) = 1
    and rownum <= 1;
    prompt pause
    pause

  • Xml data into non-xml database.. solution anyone?

    Hi,
    My current project requires me to store the client's data on our servers. We're using Oracle9i. Daily, I will download the client's data for that day and load it into our database. My problem is that the data file is not a flat file so I can't use sql*loader to load the data. Instead, the data file is an xml file. What is the best way to load xml data into a non-xml database? Are there any tools similar to sql*Loader that will load xml data into non-xml database? Is it the best solution for the client to give me an XML dump of their data to load into our database, or should I request a flat file? My last resort would be to write some sort of a script to parse the xml data into a flat file, and then run it through sql*loader. Is this the best solution? One thing to note is that these files could be very large.
    Thanks in advance.
    -PV

    I assume that just putting the XML file into an
    extremely large VARCHAR field is not what you want.
    Instead, you want to extract data elements from the
    XML and write them to columns in a table in your
    database. Right?Yes. Your assumption is correct.
    It sounds like you already have a script that loads a
    flat file into your database. In that case I would
    write an XSL transformation that converts the client's
    XML into a correctly-formatted flat file.Thank you. I'll look into that. Other suggestions are welcome.

  • XML Database Development with JDeveloper?

    Hello, folks:
    I am trying to create XML database through JDeveloper.
    Database: Oracle 10g
    IDE: JDeveloper 11.1.2.2.0
    JDBC Driver: Oracle ojdbc6.jar
    I connect successfully to the database through JDeveloper. There I see many folders listed, e.g. Tables, Views, Indexes, XML Schemas, XML DB Repository, and others. My problem is that when I try to save a large schema file (that I already validated on my local machine) that is roughly more than 300 lines, then JDeveloper is unable to save the file. It saves only very small files that are about 100 lines or less. The error message simply is: "Unable to save XML Schema blah.filename@local (Error saving XML Schema).
    I tried to do it in Oracle SQL Developer too, but got the same error. Can someone please help me understand this problem and how to fix it? Do I need to specify some settings in JDeveloper or SQL Developer? Thanks a lot in advance.
    Asif

    Please raise your question to the forum dedicated to JDeveloper 11:
    JDeveloper and OC4J 11g Technology Preview
    Regards,
    Didier.

  • How to create simple XML database in oracle 11g

    Hi,
    what are the steps to followed to create a simeple custormer XML database.
    Like storing .xml file into XMLType, writing simple xml schema.....like that
    how to register the .xsd
    how to insert the xml data
    how to querying the the data base with xquery
    Thanks in Advance

    Have a look a the FAQ on the main page of this XMLDB forum. That's a good source to start (besides the XMLDB Developer Guide manual).

  • XML Database in Apps Databases

    Hi,
    What is the use of XML database in Apps Databases...it has XML Schema...etc etc..what purpose is that...

    If you are using XMLTYPE in stored procedures,
    views, functions, columns or tables you need the XDB
    feature in order for the base XMLTYPE to have
    complete functionality of it's member functions.
    This means if you were directed to remove XDB for
    some other reason you must follow the steps to put
    it back in if you want to use the XMLTYPE. You will
    also require it if you are using any of the standard
    pl/sql apis such as DBMS_XMLDOM and DBMS_XMLQUERY
    to name a couple.Yes, this is from the first note. If you check the other one, you would also find that Oracle XML Database has to be installed correctly (Oracle 10g Release 2 and above) in order to have a successful interMedia installation. For getting more details about "Oracle interMedia", check the the same note (Question 1).

  • XML database not loading

    I have a xml database that has some information which is loaded into a drop down menu on my form. While I am in Live Cycle Designer and use the pdf preview, the dropdowns populate correctly and show what is in the database but when I open up the form in Adobe Reader, the dropdown show null. How can I remedy this problem?

    You can use the importXFA() method to import data via scripting.
    this.importXFAData("../MyFormData.xml");
    Note: This script cannot be run directly from a button in your form.
    You'll have to call it from a privileged context like the console window or a folder level script.

  • Component XML database is in INVALID state, while quering dba_registry,

    How to make the component XML valid

    Did You performed recently any upgrade?
    Was upgrade sucessfull? No errors?
    Please reffer to metalink note 243554.1 - How to Deinstall and Reinstall XML Database (XDB).
    If You are using XDB, then You will have to reinstall it.

  • Xml database error

    Create a table employee having (dept_id : number, employee_spec : XMLType).
    The employee_spec is a schema with
    attributes emp id, name, email, acc_no, managerEmail, dateOf Joning.
    Insert 10 tuples into employee table.Fire the following queries on XML database.
    a) Retrieve the names of employee.
    b) Retrieve the acc_no of employees.
    c) Retrieve the names,acc_no, email of employees.
    d) Update the 3rd record from the table and display the name of an employee.
    e) Delete 4 th record from the table.
    SQL> connect hr/tiger@bom4;
    Connected.
    SQL> create table employee
    2 (
    3 dept_id number(8),
    4 employee_spec sys.xmltype
    5 );
    Table created.
    SQL>
    SQL> INSERT INTO employee VALUES
    2 (
    3 100,
    4 xmltype(
    5 '<employees>
    6 <emp id="1">
    7 <name>abhijeet gole</name>
    8 <email>[email protected]</email>
    9 <acc_no>111</acc_no>
    10 <dateOfJoining>1994-11-16</dateOfJoining>
    11 </emp>
    12 </employees>'))
    13 ;
    xmltype(
    ERROR at line 4:
    ORA-00904: invalid column name
    SQL> INSERT INTO employee VALUES
    2 (
    3 100,
    4 sys.XMLTYPE( '<employees>
    5 <emp id="1">
    6 <name>abhijeet gole</name>
    7 <email>[email protected]</email>
    8 <acc_no>111</acc_no>
    9 <dateOfJoining>1994-11-16</dateOfJoining>
    10 </emp>
    11 </employees>'))
    12 ;
    sys.XMLTYPE( '<employees>
    ERROR at line 4:
    ORA-22876: this user-defined type is not allowed or it cannot be used in this
    context

    Yep, works fine on 10.2...
    SQL> ed
    Wrote file afiedt.buf
      1  create table employee
      2  (
      3  dept_id number(8),
      4  employee_spec xmltype
      5* )
    SQL> /
    Table created.
    SQL> ed
    Wrote file afiedt.buf
      1  INSERT INTO employee VALUES
      2  (
      3  100,
      4  xmltype(
      5  '<employees>
      6  <emp id="1">
      7  <name>abhijeet gole</name>
      8  <email>[email protected]</email>
      9  <acc_no>111</acc_no>
    10  <dateOfJoining>1994-11-16</dateOfJoining>
    11  </emp>
    12* </employees>'))
    SQL> /
    1 row created.
    SQL>What version of SQL*Plus are you using? Ensure that it's up to date with the database version.

  • XML DATABASE INSTALLATION

    i am installing xml database on live server with following step:-
    created tablespace
    create tablespace XDB datafile '/umsdata03/umsdb/datafile/ums_data_xdb01.dbf' size 1G;
    executing script
    @?/rdbms/admin/catqm.sql xdb123 XDB UMS_AUTOALLOC_TEMP
    but the script follow with error:-
    and pls suggest how to deal with port issue of xml installation
    SQL> create tablespace XDB datafile '/umsdata03/umsdb/datafile/ums_data_xdb01.dbf' size 1G;
    Tablespace created.
    SQL> SQL>
    SQL>
    SQL>
    SQL> @?/rdbms/admin/catqm.sql xdb123 XDB UMS_AUTOALLOC_TEMP
    CREATE TABLE sys.xdb_installation_tab (
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    CREATE TABLE sys.dropped_xdb_instll_tab (
    ERROR at line 1:
    ORA-00955: name is already used by an existing object
    DROP ON DATABASE
    ERROR at line 3:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-20000: Trigger xdb_installation_trigger does not support object creation of
    type TRIGGER
    ORA-06512: at line 32
    Trigger created.
    System altered.
    System altered.
    System altered.
    System altered.
    old 23: where tablespace_name = upper('&res_tbs');
    new 23: where tablespace_name = upper('XDB');
    old 29: where tablespace_name = upper('&temp_tbs');
    new 29: where tablespace_name = upper('UMS_AUTOALLOC_TEMP');
    old 47: raise_application_error(-20001, 'Compressed tablespace &res_tbs' ||
    new 47: raise_application_error(-20001, 'Compressed tablespace XDB' ||
    old 51: '&temp_tbs cannot be used');
    new 51: 'UMS_AUTOALLOC_TEMP cannot be used');
    PL/SQL procedure successfully completed.
    old 1: create user xdb identified by &xdb_pass account lock password expire
    new 1: create user xdb identified by xdb123 account lock password expire
    old 2: default tablespace &res_tbs temporary tablespace &temp_tbs
    new 2: default tablespace XDB temporary tablespace UMS_AUTOALLOC_TEMP
    User created.
    PL/SQL procedure successfully completed.
    old 1: create user anonymous identified by values 'anonymous' default tablespace &res_tbs
    new 1: create user anonymous identified by values 'anonymous' default tablespace XDB
    create user anonymous identified by values 'anonymous' default tablespace XDB
    ERROR at line 1:
    ORA-01920: user name 'ANONYMOUS' conflicts with another user or role name
    Grant succeeded.
    User altered.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    CREATE role xdbadmin
    ERROR at line 1:
    ORA-01921: role name 'XDBADMIN' conflicts with another user or role name
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Session altered.
    Table created.
    Table created.
    Index created.
    Type created.
    Table created.
    Index created.
    Type created.
    Type created.
    Type created.
    Synonym created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Table created.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Index created.
    Index created.
    Index created.
    Table analyzed.
    Sequence created.
    Sequence created.
    Grant succeeded.
    Library created.
    Function created.
    Package created.
    No errors.
    Package body created.
    No errors.
    Procedure created.
    Function created.
    Grant succeeded.
    Grant succeeded.
    PL/SQL procedure successfully completed.
    Type created.
    Type created.
    Type created.
    Type created.
    Type created.
    Grant succeeded.
    Type created.
    Grant succeeded.
    Table created.
    Table altered.
    Table altered.
    Index created.
    Table created.
    Index created.
    Index created.
    Index created.
    Package created.
    No errors.
    Package body created.
    No errors.
    PL/SQL procedure successfully completed.
    Session altered.
    Package created.
    No errors.
    Synonym created.
    Grant succeeded.
    Package created.
    Synonym created.
    Grant succeeded.
    No errors.
    Type created.
    No errors.
    Grant succeeded.
    Package created.
    No errors.
    Synonym created.
    Grant succeeded.
    No errors.
    drop type xdb.xdbpi_im
    ERROR at line 1:
    ORA-04043: object XDBPI_IM does not exist
    drop table xdb.xdb$path_index_params
    ERROR at line 1:
    ORA-00942: table or view does not exist
    Library created.
    Table created.
    Package created.
    Grant succeeded.
    No errors.
    Type created.
    No errors.
    Type body created.
    No errors.
    Grant succeeded.
    Package created.
    Package body created.
    Package created.
    No errors.
    Grant succeeded.
    Package created.
    Synonym created.
    No errors.
    Grant succeeded.
    Library created.
    Procedure created.
    No errors.
    Grant succeeded.
    Function created.
    No errors.
    Grant succeeded.
    Warning: Package Body created with compilation errors.
    No errors.
    Grant succeeded.
    No errors.
    Trigger created.
    No errors.
    Package body created.
    Package created.
    No errors.
    Synonym created.
    Synonym created.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    No errors.
    Package created.
    No errors.
    Synonym created.
    Synonym created.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    No errors.
    Package created.
    No errors.
    Package created.
    Synonym created.
    Synonym created.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    No errors.
    Grant succeeded.
    Library created.
    Package body created.
    No errors.
    Library created.
    Warning: Package Body created with compilation errors.
    No errors.
    Synonym created.
    Grant succeeded.
    No errors.
    Library created.
    Warning: Package Body created with compilation errors.
    No errors.
    Warning: Package Body created with compilation errors.
    Synonym created.
    Grant succeeded.
    No errors.
    Grant succeeded.
    Library created.
    Function created.
    Grant succeeded.
    Synonym created.
    Procedure created.
    No errors.
    Grant succeeded.
    Grant succeeded.
    Function created.
    No errors.
    Grant succeeded.
    Function created.
    Grant succeeded.
    Grant succeeded.
    Package body created.
    No errors.
    Warning: Package Body created with compilation errors.
    No errors.
    Synonym created.
    Grant succeeded.
    No errors.
    PL/SQL procedure successfully completed.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    1 row created.
    Commit complete.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Index created.
    Package created.
    No errors.
    Grant succeeded.
    Package body created.
    Package body created.
    No errors.
    Procedure created.
    No errors.
    Procedure created.
    No errors.
    drop view xdb.xdb$resource_view
    ERROR at line 1:
    ORA-00942: table or view does not exist
    drop view xdb.xdb$rv
    ERROR at line 1:
    ORA-00942: table or view does not exist
    PL/SQL procedure successfully completed.
    drop indextype xdb.xdbhi_idxtyp force
    ERROR at line 1:
    ORA-29833: indextype does not exist
    drop operator xdb.path force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.depth force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.abspath force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.under_path force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop operator xdb.equals_path force
    ERROR at line 1:
    ORA-29807: specified operator does not exist
    drop package xdb.xdb_ancop
    ERROR at line 1:
    ORA-04043: object XDB_ANCOP does not exist
    drop package xdb.xdb_funcimpl
    ERROR at line 1:
    ORA-04043: object XDB_FUNCIMPL does not exist
    drop type xdb.xdbhi_im
    ERROR at line 1:
    ORA-04043: object XDBHI_IM does not exist
    drop type xdb.path_array
    ERROR at line 1:
    ORA-04043: object PATH_ARRAY does not exist
    Library created.
    Library created.
    Type created.
    Type created.
    No errors.
    Grant succeeded.
    Grant succeeded.
    Type created.
    No errors.
    Type body created.
    No errors.
    Grant succeeded.
    Package created.
    No errors.
    Grant succeeded.
    Package created.
    No errors.
    Grant succeeded.
    Type altered.
    Operator created.
    Operator created.
    Grant succeeded.
    Grant succeeded.
    Synonym created.
    Synonym created.
    Operator created.
    Operator created.
    Operator created.
    Grant succeeded.
    Synonym created.
    Grant succeeded.
    Synonym created.
    Grant succeeded.
    Synonym created.
    Indextype created.
    Grant succeeded.
    Index created.
    View created.
    No errors.
    Synonym created.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Grant succeeded.
    Package created.
    No errors.
    Synonym created.
    Grant succeeded.
    Trigger created.
    No errors.
    Package body created.
    No errors.
    Function created.
    No errors.
    Grant succeeded.
    Synonym created.
    Function created.
    No errors.
    Package body created.
    No errors.
    Package body created.
    No errors.
    Package body created.
    No errors.
    Package body created.
    BEGIN
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "XDB.DBMS_XDBZ0"
    ORA-06512: at "XDB.DBMS_XDBZ", line 7
    ORA-06512: at line 2
    declare
    ERROR at line 1:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
    ORA-06512: at "XDB.XDB$PATCHUPSCHEMA", line 98
    ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
    ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14
    ORA-06512: at line 143
    BEGIN
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "XDB.DBMS_XDBZ0"
    ORA-06512: at "XDB.DBMS_XDBZ", line 14
    ORA-06512: at line 2
    DECLARE
    ERROR at line 1:
    ORA-31114: XDB configuration has been deleted or is corrupted
    ORA-06512: at "XDB.DBMS_XDB", line 73
    ORA-06512: at line 96
    declare
    ERROR at line 1:
    ORA-01403: no data found
    ORA-06512: at line 5
    Commit complete.
    call xdb.dbms_xdbz0.initXDBSecurity()
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    BEGIN
    ERROR at line 1:
    ORA-04063: package body "XDB.DBMS_XDBZ0" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "XDB.DBMS_XDBZ0"
    ORA-06512: at "XDB.DBMS_XDBZ", line 7
    ORA-06512: at line 2
    Commit complete.
    grant all on XDB.XDB$ACL to public
    ERROR at line 1:
    ORA-00942: table or view does not exist
    Commit complete.
    declare
    ERROR at line 1:
    ORA-31000: Resource 'http://xmlns.oracle.com/xdb/acl.xsd' is not an XDB schema
    document
    ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
    ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14
    ORA-06512: at line 63
    declare
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    No errors.
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    No errors.
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    No errors.
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:
    ORA-03114: not connected to ORACLE
    ERROR:

    Refer MOS note 243554.1 for reinstallation of XDB.

Maybe you are looking for