Unable to parse an XML

Hi
I like to get Latitude and Longitude values from XML returned by Yahoo Geocoding.
I tried to use following piece of SQL but getting "Unsupported data type" error.
Any help?
select extract(XMLType('<?xml version="1.0"?> <ResultSet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:yahoo:maps" xsi:schemaLocation="urn:yahoo:maps http://api.local.yahoo.com/MapsService/V1/GeocodeResponse.xsd"><Result precision="zip"><Latitude>51.502232</Latitude><Longitude>-0.117800</Longitude><Address></Address><City>London, SE1 7PB</City><State>United Kingdom</State><Zip></Zip><Country>GB</Country></Result></ResultSet> ')
,'/ResultSet/Result/') Latitude from dualPS: I am executing this on Oracle Apex

I've rewritten it slightly:
with test as
select XMLType('<?xml version="1.0"?>
<ResultSet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:yahoo:maps" xsi:schemaLocation="urn:yahoo:maps http://api.local.yahoo.com/MapsService/V1/GeocodeResponse.xsd">
<Result precision="zip">
<Latitude>51.502232</Latitude><Longitude>-0.117800</Longitude>
<Address></Address><City>London, SE1 7PB</City><State>United Kingdom</State>
<Zip></Zip><Country>GB</Country>
</Result></ResultSet> ') Latitude from dual
select *
from xmltable (xmlnamespaces ('http://www.w3.org/2001/XMLSchema-instance' as "xsi"
                 ,default 'urn:yahoo:maps' )
                ,'/ResultSet/Result' passing (select latitude from test)
                  columns Latitude number path 'Latitude'
                        , Longitude number path 'Longitude'
                        , Address varchar2 (100) path 'Address'
                        , City varchar2 (100) path 'City'
                        , State varchar2 (100) path 'State'
                        , Zip varchar2 (100) path 'Zip'
                        , country varchar2(2) path 'Country'
                )

Similar Messages

Opatch error 'Unable to parse the xml file'

Hi there,
I am new to installing patches on Oarcle and I need to install patch 12375678 on my windows system, Oracle 11.2.0.2.
I have followed the instructions in the readme.txt file, but got this error and I have not come across anywhere on the web that explain how I could fix it.
Could you please advise?
Thanks
C:\>set oracle_home=C:\oracle\product\11.2.0\dbhome_1
C:\>echo %oracle_home%
C:\oracle\product\11.2.0\dbhome_1
C:\>cd C:\oracle\product\11.2.0\dbhome_1\inventory\oneoffs\12375678
C:\oracle\product\11.2.0\dbhome_1\inventory\oneoffs\12375678>opatch apply
Invoking OPatch 11.2.0.1.1
Oracle Interim Patch Installer version 11.2.0.1.1
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home : C:\oracle\product\11.2.0\dbhome_1
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.2.0.1.1
OUI version : 11.2.0.2.0
OUI location : C:\oracle\product\11.2.0\dbhome_1\oui
Log file location : C:\oracle\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch2
012-05-21_15-28-52PM.log
Patch history file: C:\oracle\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch_
history.txt
ApplySession applying interim patch '12375678' to OH 'C:\oracle\product\11.2.0\d
bhome_1'
Running prerequisite checks...
OPatch detected non-cluster Oracle Home from the inventory and will patch the lo
cal system only.
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '12375678' for restore. This might take a
while...
Backing up files affected by the patch '12375678' for rollback. This might take
a while...
Patching component oracle.rdbms, 11.2.0.2.0...
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\xml\xsl\kuexttbl.xsl"
Patching component oracle.rdbms.dbscripts, 11.2.0.2.0...
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\admin\prvtbpd.plb"
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\admin\prvtbpw.plb"
ApplySession adding interim patch '12375678' to inventory
Interim Patch metadata parsing failure... 'Unable to parse the xml file.'
ApplySession failed: ApplySession failed in system modification phase... 'Unable
to create patchObject'
OPatch will attempt to restore the system...
Restoring the Oracle Home...
OPatch was able to restore your system. Look at log file and timestamp of each f
ile to make sure your system is in the state prior to applying the patch.
OPatch failed with error code = 73

your actions.xml must not be able to be read.
open it in notepad yourself to see does it open, if so its not corrupt, if doesnt open download patch again.
More then likely will be fine so try locate the patch in a shorter home path, like c:\patches\12375678 and see does it install from there.
Only other thing I can think of is the main inventory.xml, usually c:\program files\oracle\inventory\inventory.xml
try notepad with that too.

CRM Designer Unable to parse CLD XML file

I am unable to use the CRM designer to load the CLD files from CRM. Each time I try, I get "Error retrieving and parsing XML file". I save the file locally and open using notepad and these are the contents:
0001
http://sethnn058.mynetwork.ds.BLAHBLAH.net:8000/sap/bc/bsp/sap/crm_bsp_bab_dis/bpserv.htm?sap-client=200&cmd=getScreen&lang=E&appl=CRMD_SALQ&blview=SLS_REP&event=ZBT_ADDITIONAL_R3&scrpos=4&scrvar=&creq=VAQK901374&wreq=VAQK901372&xchg_id=595A1E7995AC2E45BC1723BB1260BF66
http://sethnn058.mynetwork.ds.BLAHBLAH.net:8000/sap/bc/bsp/sap/crm_bsp_bab_dis/bpserv.htm?sap-client=200&cmd=saveScreen&lang=E&appl=CRMD_SALQ&blview=SLS_REP&event=ZBT_ADDITIONAL_R3&scrpos=4&scrvar=&creq=VAQK901374&wreq=VAQK901372&xchg_id=595A1E7995AC2E45BC1723BB1260BF66
http://sethnn058.mynetwork.ds.BLAHBLAH.net:8000/sap/bc/bsp/sap/crm_bsp_bab_dis/bpservexit.htm?sap-client=200&cmd=endSession&lang=E&appl=CRMD_SALQ&blview=SLS_REP&event=ZBT_ADDITIONAL_R3&scrpos=4&scrvar=&creq=VAQK901374&wreq=VAQK901372&xchg_id=595A1E7995AC2E45BC1723BB1260BF66
It's definitely not a XML file. What could the issue be??
Thanks!!

jtahlborn wrote:
My guess is that it is a namespace issue. The ShipmentOrder element has no namespace, but the Voyage element has the namespace "http://www.xyz.com//CDM/2009/v1.0".
Yes, indeed. The posted error message does say that *"":Voyage* is one of the possible expected types, which must mean a Voyage element in no namespace.

Unable to parse the xml file

I have a xml file with the xsd ,when i try to parse it using Xerces2-j i am getting an error msg like this
XML Document has Error:true cvc-complex-type.2.4.a: Invalid content was found starting with element 'Voyage'. One of '{"":Parties, "":Voyage, "":Carrier, "":Ports, "":Commodities}' is expected.
and mu xml file is
<?xml version = "1.0" encoding = "UTF-8"?>
     <ShipmentOrder
          AllocationNumber = "AL12345"
          CustomerReferenceNumber = "FORD123"
          OrderType = "NEW"
          ShipmentNumber = "USEDN12345"
          ShipmentType = "IMPORT">
     <Parties
          PartyName = "XYZ INC"
          PartyNumber = ""
          PartyType = "Shipper">
     <Address
          Address1 = "1234"
          Address2 = "Avenue Road"
          Address3 = ""
          City = "DETROIT"
          Country = "USA"
          State = "MI"
          ZIPCode = "098081"
          xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     <Contact
          ContactPerson = "John Smith"
          ContactPoint = "7324120987"
          ContactType = "Work Phone"
          xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     </Parties>
     <Voyage
          EndDate = ""
          FlagShipCountry = "INDIA"
          LlyodsCode = "12345467"
          StartDate = ""
          VesselCode = "PAZ"
          VesselName = "BLUESHIP"
          VoyageMode = "OCEAN"
          VoyageNumber = "NA2345-PAZ"
          xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     <Carrier CarrierName = "XYZ OCEAN CARRIER" SCAC = "XYZO" TaxID = "" xmlns = "http://www.xyz.com//CDM/2009/v1.0"/>
     <Ports
          Code = "USBAL"
          Name = "BALTIMORE"
          Terminal = "TERMINAL1"
          TerminalName = "DUNDALK"
          Type = "LOAD">
          <Berth
          Code = "USBAL1"
          Name = "ATLANTIC TERMINAL"
          PierNumber = "19"
          Type = "LOAD"/>
     </Ports>
     <Ports Code = "BEZEE"
          Name = "ZEEBRUGE"
     Terminal = "TERMINAL C"
     TerminalName = "MASTER STEO"
     Type = "DISCHARGE">
          <Berth Code = "BEZEE4"
     Name = "BELGIAN TERMINAL"
     PierNumber = "12"
     Type = "DISCHARGE"/>
     </Ports>
     <Commodities BarCode = "123456" CommodityClass = "AUTO" CommodityCode = "8703000" CommodityDescription = "FORD 4X4 PICKUP TRUCK" CommodityType = "CAR" LadingLineItem = "1" LadingQuantity = "1" MarksandNumbers = "123456">
          <Weight UnitOfMeasurement = "KGS" UnitOfWeight = "GROSS" Weight = "1234"/>
          <Measurement CubicDimensions = "8" Height = "1.65" Length = "5" UnitOfMeasurement = "FEET" Width = "3"/>
          <ManufacturerDeatils CommodityDescription = "FORD 4X4 PICKUP TRUCK" MakeCode = "FORD" ManufacturerName = "FORD MOTOR CO" ModelCode = "TAURUS" ModelType = "LX" ModelYear = "2009"/>
          <HazardousDetails CalssificationDescription = "12" ClassificationCode = "124" ClassificationCodeQualifier = "W" FlashpointTemperature = "23" FlashpointUnitOfMeasurement = "C" MarinePollutant = "Y" MaterialCode = "N" MaterialDescription = "N" MaterialsPage = "N" PackagingGroupCode = ""/>
          <EquipmentDetails EquipmentNumber = "1234" EquipmentType = "CONTAINER"/>
     </Commodities>
</ShipmentOrder>
can any one help me out with the problem

jtahlborn wrote:
My guess is that it is a namespace issue. The ShipmentOrder element has no namespace, but the Voyage element has the namespace "http://www.xyz.com//CDM/2009/v1.0".
Yes, indeed. The posted error message does say that *"":Voyage* is one of the possible expected types, which must mean a Voyage element in no namespace.

Unable to parse xml file

public class DOMEcho1 {
     static Document document;
     static String FILE_NAME = "slideSample01.xml";
     public static void main(String[] args) {
          DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
          Node node = null;
          try{
               DocumentBuilder builder = factory.newDocumentBuilder();
               document = builder.parse(new File(FILE_NAME));
               node = document.getParentNode();
          catch(SAXException e) {
          catch(ParserConfigurationException e) {
          catch(IOException e) {
}the XML file:
<?xml version='1.0' encoding='utf-8'?>

<slideshow
title="Sample Slide Show"
date="Date of publication"
author="Yours Truly"
>

<slide type="all">
<title>Wake up to WonderWidgets!</title>
</slide>

<slide type="all">
<title>Overview</title>
<item>Why <em>WonderWidgets</em> are great</item>
<item/>
<item>Who <em>buys</em> WonderWidgets</item>
</slide>
</slideshow>
I was unable to parse this xml file properly. When I called the method "getParentNode" it returns me a null value.
Anyone out there please guide me how to parse this xml file or advice me on the additional tasks I need to perform before I can start parsing.
Your advices will be greatly appreciated, thanks!

The documentation for getParent Node says:
All nodes, except Attr, Document, DocumentFragment, Entity, and Notation may have a parent.
I think what you want is getDocumentElement to get the root element (slideshow in your case).
Dave Patterson

Unable to display tree view; Error when parsing an XML document (Premature end of file.)

Hi folks,
I am using a cascaded mapping in my OM. I have a graphical mapping followed by the Java mapping. It is a flat file to IDOC mapping. Everything works fine in Dev but when I transport the same objects to QA, the Operation mapping though it doesn't fail in ESR testing tool, gives the following message and there is no output generated for the same payload which is successfully tested in DEV. Please advise on what could be the possible reasons.
Unable to display tree view; Error when parsing an XML document (Premature end of file.)

kalyan,
There seems to be an invalid xml payload which causes this error in ESR not generating the tree view. Please find the similar error screenshot and rectify the payload.
Mutti

ERROR ITMS-9000: "Unable to parse apple display options file: com.apple.ibooks.display-options.xml" at Book (MZItmspBookPackage)

Hi, I'm En32, now trying to publish my first iBooks (epub).
The package I created is always rejected to deliver with following error.
Does anyone who can provide me a solution ?
=== error ===
Package Summary:
1 package(s) were not uploaded because they had problems:
          /Users/En32/Music/iTunes Producer/Playlists/10000448204.itmsp - Error Messages:
                    Apple's web service operation was not successful
                    Unable to authenticate the package: 10000448204.itmsp
                    ERROR ITMS-9000: "Unable to parse apple display options file: com.apple.ibooks.display-options.xml" at Book (MZItmspBookPackage)
===
$ cat META-INF/com.apple.ibooks.display-options.xml
<?xml version=”1.0″ encoding=”UTF-8″?>
<display_options>
<platform name=”*”>
<option name=”fixed-layout”>true</option>
</platform>
</display_options>
===
Actually, I'd like to use fixed layout so I use com.apple.ibooks.display-options.xml.
This ePub file looks good because I can open it with my iPad - iBooks, however iTunes publisher always rejects this.
Any solutions ?

I was getting that error when I used OSX's default compress feature. I found a little utility called ePub Zip and used it to compress (zip) my ePubs and that did the trick. They then passed the validation. I got it here:
http://www.mobileread.com/forums/showthread.php?t=55681

Error message "Unable to parse opf file: container.xml"

The Message I get is
ERROR ITMS-9000: "Unable to parse opf file: container.xml" at Book (MZItmspBookPackage)
I have made the book in iBooks author- the previous version was fine, apple requested I "fix" it landscape mode. Since then... No Joy.

Yep, i just did it again. The entire scroll-bar widget, complete with formatted text, graphics, etc., pasted itself nicely in another book. Two different files, the same widget.
I use the scroll-bar widgets for most of my texts. (I have audio buttons on the side, and the scripts are within the widget, to the side). My only text is within widgets, and text boxes, naturally.
I am following your recommendation: cleaning files, etc. I am remaking the book anew. I need to convince the EPUB bot or whatever that my file looks and works nicely on all my devices. You would expect an error message when previewing the book: 'Hey Amigo, your file is flawed, stop working on it, and get back to the drawing board." Should be able to try again next Monday.

PO 7.4 RESTAdapter issue : Unable to parse XML message payload

Dear experts,
We are implementing the scenario Exposing a function module as Restful service with the PO RESTAdapter that's avaiable in PO 7.4 SP09 as described in the blog written by Ivo:
PI REST Adapter – Exposing a function module as RESTful service
When we test the scenario to processing messages the adapter reports the error message:
Error while sending message to module processor: senderChannel '589b39c9b91c3ae99040d9addc6a818b': Catching exception calling messaging system: Unable to parse XML message payload to extract operation for receiver determinationorg.xml.sax.SAXParseException: Premature end of file.
Anyone an idea or solution direction?
Thanks in advance.
Cheers, Luc

Hi YRV isa,
Issue solved by Ivo Kulms
"Either you use a Dummy Interface in the IFlow for the adapter or you have to specify on the Operation Determination Tab which XI Operation / Interface should be used. The table on the tab allows to specify different interface name depending on the internal variables. In the variable columns add for example the REST operation, by entering "operation", in the expression column "GET" or "POST" or "*" and in the operation/namespace columns the XI operation / interface you want to reference.
The variable "operation" has to be in curly brackets, so that it gets evaluated. So the entry should look like "{operation}" ( or like "{service}" if you want to map the XI operation by REST service name)"
Kind regards, Luc

CS3 - "Unable to locate or parse the XML source"

Hello,
When I try and attach a remote XML source to my XSL fragment,
Dreamweaver
CS3 tells me "Unable to locate or parse the XML source".
This happens irrespective of where the remote XML file is
located, and for
all the remote XML files that I have found and tested from a
myriad of
different sources - I always get the same response.
I can download any of these XML files and work with them
locally, which
Dreamweaver is quite happy to do, but that isn't appropriate
for an
application that needs to rely on an XML feed that is always
up to date!
From searching Google I can find numerous other queries of
this nature, but
no solutions! I am not sure if it is a Dreamweaver problem,
or related to
the type of web server I'm using or indeed to the corporate
firewall here.
For clarity, only Dreamweaver can't locate the remote XML
sources - pasted
into a browser they are all perfectly valid.
(Apologies for sort of cross posting, I have already asked
this question
slightly differently on macromedia.dreamweaver)
Cheers,
D.

Kelli, I know this is months late for you.. but I get the
same error.. I found if I downloaded the xml locally I was able to
set up my xsl page. After I got the page to look the way I wanted I
switch the source to the external URL.
If you have found a fix for the error please let me know,
other then that this way will work.

Unable to locate or parse the XML source (-1,-1)

Hello,
Why do I get this error when I'm trying to get the XML source
from
*.php ?
quote:
"Unable to locate or parse the XML source (-1,-1)"
The
*.php file has a recordset which I exported as XML based on
this
tutorial
I can see the XML of *php in the browser but can't get the
schema.
What am I missing?
Thank you

page.php
url
quote:
code:
<?php require_once('../Connections/example.php'); ?>
<?php
// Load the XML classes
require_once('../includes/XMLExport/XMLExport.php');
if (!function_exists("GetSQLValueString")) {
function GetSQLValueString($theValue, $theType,
$theDefinedValue = "", $theNotDefinedValue = "")
$theValue = get_magic_quotes_gpc() ? stripslashes($theValue)
: $theValue;
$theValue = function_exists("mysql_real_escape_string") ?
mysql_real_escape_string($theValue) :
mysql_escape_string($theValue);
switch ($theType) {
case "text":
$theValue = ($theValue != "") ? "'" . $theValue . "'" :
"NULL";
break;
case "long":
case "int":
$theValue = ($theValue != "") ? intval($theValue) : "NULL";
break;
case "double":
$theValue = ($theValue != "") ? "'" . doubleval($theValue) .
"'" : "NULL";
break;
case "date":
$theValue = ($theValue != "") ? "'" . $theValue . "'" :
"NULL";
break;
case "defined":
$theValue = ($theValue != "") ? $theDefinedValue :
$theNotDefinedValue;
break;
return $theValue;
mysql_select_db($database_example, $example);
$query_data = "SELECT * FROM example";
$data = mysql_query($query_data, $example) or
die(mysql_error());
$row_data = mysql_fetch_assoc($data);
$totalRows_data = mysql_num_rows($data);
// Begin XMLExport data
$xmlExportObj = new XMLExport();
$xmlExportObj->setRecordset($data);
$xmlExportObj->addColumn("Name", "Name");
$xmlExportObj->addColumn("Damage", "Damage");
$xmlExportObj->addColumn("Speed", "Speed");
$xmlExportObj->addColumn("Level", "Level");
$xmlExportObj->addColumn("Details", "Details");
$xmlExportObj->addColumn("Type", "Type");
$xmlExportObj->addColumn("Source", "Source");
$xmlExportObj->addColumn("Location", "Location");
$xmlExportObj->addColumn("Date", "Date");
$xmlExportObj->addColumn("Price", "Price");
$xmlExportObj->addColumn("Skill", "Skill");
$xmlExportObj->addColumn("Constitution", "Constitution");
$xmlExportObj->addColumn("Intelligence", "Intelligence");
$xmlExportObj->addColumn("Wisdom", "Wisdom");
$xmlExportObj->addColumn("Strength", "Strength");
$xmlExportObj->addColumn("Member", "Member");
$xmlExportObj->addColumn("Image", "Image");
$xmlExportObj->setMaxRecords("ALL");
$xmlExportObj->setDBEncoding("ISO-8859-1");
$xmlExportObj->setXMLEncoding("ISO-8859-1");
$xmlExportObj->setXMLFormat("NODES");
$xmlExportObj->setRootNode("Category");
$xmlExportObj->setRowNode("Type");
$xmlExportObj->Execute();
// End XMLExport data
?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "
http:// www.
w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http:// www . w3. org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
<title>example</title>
<link href="css.css" rel="stylesheet" type="text/css"
/>
</head>
<body>
</body>
</html>
<?php
mysql_free_result($data);
?>

Unable to Locate or Parse the XML source

I've just started playing around with Dreamweaver 8 and I'm
trying to pull in a RSS feed. I've followed the instructions in
Dreamweaver, but when I add my XML source (
http://rss.cnn.com/rss/cnn_law.rss)
I get an error message in the bindings area where the XML structure
should be displaying that says "Unable to locate or parse the XML
source". I'm somewhat familiar with XML and new to RSS feeds so I
have no idea what this means. Any help will be appreciated.

Kelli, I know this is months late for you.. but I get the
same error.. I found if I downloaded the xml locally I was able to
set up my xsl page. After I got the page to look the way I wanted I
switch the source to the external URL.
If you have found a fix for the error please let me know,
other then that this way will work.

L755-S5244 - W7 system repair disc could not be created... unable to parse... XML data. (0x800705B9)

After creating a backup image of my W7 Toshiba laptop OK, the last step was the option to create a system repair disc. However that returned the following error:
System repair disc could not be created
Windows was unable to parse the requested XML data.
(0x800705B9)
Note this is *not* the same as "system recovery discs"! I already have a set of those discs which work OK.. What I need is a system repair disc which allows booting into special recovery mode to repair W7, to restore a backup image, etc.
Note that my computer is working fine. I just need to be able to make a system repair disc in case there are future problems. There always are, eventually.
In googling this problem, there are many reports of this error but no clear solution. Some of the reported fixes refer to microsoft help/support/social/technet links which no longer exist. I tried one of those suggestions, SFC /SCANNOW, which didn't find any system file errors on my computer. So that's not the cause.
It may have something to do with the OEM W7 version which Toshiba puts on its laptops such as my L755-S5244(?). It's possible that Toshiba has intentionally or accidentally disabled the normal commands to make a system repair disc in W7. Does anybody know for sure?
Thanks.

I did a fair amount of goggling and reading, then... I tried 3 different downloadable boot disks from maximumpcguides.com, spirebyte, and mydigitallife.info. They all work exactly the same. When booting from one of those discs, there are 5 options offered. I had to make text notes (below) because there's no way to make screen images in repair mode.
1) Startup Repair - apparently works OK, at least it went through the process and found no errors. That's as it should be, because this computer is working fine! My only objective here is to find out what can be done someday when it malfunctions, as all computers do eventually..
2) System Restore - doesn't work
big red X: "To use System Restore, you must specify which Windows installation to restore. Restart this computer, select an operating system, and then select System Restore." That makes no sense because I only have one Windows installation! This is an important option. Is there any way to access it when Windows 7 won't start normally?
3) System Image Recovery - It found the image file I had created previously. But I didn't want to risk it on a properly functioning computer (no reason). So I don't know if it will actually work right... someday when I really need it.
4) Windows Memory Diagnostic - doesn't work
"Windows cannot check for memory problems. An error is preventing Windows from checking for memory problems during startup. To run the Windows Memory Diagnostic manually, boot the computer from the Windows installation disc, and then select Windows Memory Diagnostic from the Windows Boot Manager menu." However there is no such thing as a Windows installation disc on Toshiba OEM W7. Or is there? Also, I can get to Windows Boot Manager by pressing f8 during startup then select Repair Your Computer, but it won't do anything. Again, it requests the Windows installation disc, which I don't have. Then at the end of all the verbiage... "... Status 0xc000000e; Info: The boot selection failed because a required device is inaccessible." It would be nice to run a good memory diagnostic because I just upgraded from 4G to 8G RAM. Suggestions?
5) Command Prompt - apparently works OK, at least it listed the directory when I entered "dir".
I feel that chances would be better if I could somehow get this W7 Toshiba laptop to make its own system repair disc, which goes full circle back to my original query... Can it be fixed to avoid the parse XML data error?

JDOM parser fails to parse Huge Size Xml Files ??? Unable to Parse ???

Hi All,
When i transformed or parsed many XML Files of huge size...I am getting java.lang.OutOfMemory error for all the huge xml files. It is working fine for files which is of small size.
I've 2GB ram in my system. I have also set heapsize for the JVM.
-Xms512M -Xmx1800M (or) -Xms512M -Xmx1500M
I like to know what are the drawbacks of JDOM parser ?
What is the maximum size of the Xml which JDOM can parse ?
I've read a long time before that parsers have certain limitations. Can anybody tell me the limitations of the parses?
Please help. i'm currently using jdom.jar to parse the xml files.
Thanks,
J.Kathir

Hi All,
When i transformed or parsed many XML Files of huge
size...I am getting java.lang.OutOfMemory error for
all the huge xml files. It is working fine for files
which is of small size.Of course it is.
>
I've 2GB ram in my system. I have also set heapsize for the JVM.
-Xms512M -Xmx1800M (or) -Xms512M -Xmx1500MYou can't always get what you want. Your JVM is competing with all the other processes on your machine, including the OS, for RAM.
I like to know what are the drawbacks of JDOM parser ?You just discovered it: all DOM parsers create an in-memory representation of the entire document. A SAX parser does not.
What is the maximum size of the Xml which JDOM can parse ?The max amount of memory that you have available to you.
I've read a long time before that parsers have
certain limitations. Can anybody tell me the
limitations of the parses?See above.
Please help. i'm currently using jdom.jar to parse the xml files.You can try a SAX parser or a streaming parser. Maybe those can help.
%

MissingResourceException: Error parsing jdbcdrivers.xml

java.io.IOException: Unable to resolve input source.
Error: writeDomain() failed. Do dumpStack() to see details.
Problem invoking WLST - Traceback (innermost last):
File "D:\release\7420WLS\SCPO\weblogic\config\weblogic\setup\createManuWLSDomain.py", line 222, in ?
File "C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py", line 70, in writeDomain
com.bea.plateng.domain.script.jython.WLSTException: java.util.MissingResourceException: Error parsing jdbcdrivers.xml
at com.bea.plateng.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
at com.bea.plateng.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1373)
at com.bea.plateng.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:712)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:270)
at org.python.core.PyInstance.invoke(PyInstance.java:261)
at org.python.pycode._pyx5.writeDomain$14(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py:70)
at org.python.pycode._pyx5.call_function(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:267)
at org.python.core.PyFunction.__call__(PyFunction.java:172)
at org.python.pycode._pyx18.f$0(D:\release\7420WLS\SCPO\weblogic\config\weblogic\setup\createManuWLSDomain.py:222)
at org.python.pycode._pyx18.call_function(D:\release\7420WLS\SCPO\weblogic\config\weblogic\setup\createManuWLSDomain.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
at weblogic.management.scripting.WLST.main(WLST.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.WLST.main(WLST.java:29)
Caused by: java.util.MissingResourceException: Error parsing jdbcdrivers.xml
at com.bea.plateng.domain.jdbc.JDBCAspectHelper.getGenericJDBCDriverInfo(JDBCAspectHelper.java:850)
at com.bea.plateng.domain.jdbc.JDBCAspectHelper.getGenericJDBCDriverInfo(JDBCAspectHelper.java:223)
at com.bea.plateng.domain.aspect.XBeanJDBCConnectionPoolDriverNameConfigAspect.decompose(XBeanJDBCConnectionPoolDriverNameConfigAspect.java:56)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.setDelegate(AbstractConfigAspect.java:550)
at com.bea.plateng.domain.aspect.FilteredConfigAspect.setDelegate(FilteredConfigAspect.java:333)
at com.bea.plateng.domain.aspect.XBeanConfigAspectBuilder.createJDBCConnectionPoolSimpleAspect(XBeanConfigAspectBuilder.java:300)
at com.bea.plateng.domain.aspect.AbstractConfigAspectBuilder.createJDBCConnectionPoolSimpleAspects(AbstractConfigAspectBuilder.java:288)
at com.bea.plateng.domain.operation.config.ConfigJDBCConnectionPool.createInitialSimpleAspects(ConfigJDBCConnectionPool.java:115)
at com.bea.plateng.domain.operation.HTableEditOperation.createSimpleTableModel(HTableEditOperation.java:784)
at com.bea.plateng.domain.operation.HTableEditOperation.getSimpleTableModel(HTableEditOperation.java:348)
at com.bea.plateng.domain.operation.HTableEditOperation.initSimpleTableModel(HTableEditOperation.java:654)
at com.bea.plateng.domain.DomainChecker.isOperationValid(DomainChecker.java:726)
at com.bea.plateng.domain.DomainChecker.getInvalidSection(DomainChecker.java:168)
at com.bea.plateng.domain.GeneratorHelper.validateConfig(GeneratorHelper.java:257)
at com.bea.plateng.domain.GeneratorHelper.validateDomainCreation(GeneratorHelper.java:235)
at com.bea.plateng.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:580)
at com.bea.plateng.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:704)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:270)
at org.python.core.PyInstance.invoke(PyInstance.java:261)
at org.python.pycode._pyx5.writeDomain$14(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py:70)
at org.python.pycode._pyx5.call_function(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:267)
at org.python.core.PyFunction.__call__(PyFunction.java:172)
com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.jython.WLSTException: java.util.MissingResourceException: Error parsing jdbcdrivers.xml
The system cannot find the path specified.
0 file(s) copied.
Attempting to shutdown server ...
Checking JSP Precompilation ...
Thanks

java.io.IOException: Unable to resolve input source.
Error: writeDomain() failed. Do dumpStack() to see details.
Problem invoking WLST - Traceback (innermost last):
File "D:\release\7420WLS\SCPO\weblogic\config\weblogic\setup\createManuWLSDomain.py", line 222, in ?
File "C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py", line 70, in writeDomain
com.bea.plateng.domain.script.jython.WLSTException: java.util.MissingResourceException: Error parsing jdbcdrivers.xml
at com.bea.plateng.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
at com.bea.plateng.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1373)
at com.bea.plateng.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:712)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:270)
at org.python.core.PyInstance.invoke(PyInstance.java:261)
at org.python.pycode._pyx5.writeDomain$14(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py:70)
at org.python.pycode._pyx5.call_function(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:267)
at org.python.core.PyFunction.__call__(PyFunction.java:172)
at org.python.pycode._pyx18.f$0(D:\release\7420WLS\SCPO\weblogic\config\weblogic\setup\createManuWLSDomain.py:222)
at org.python.pycode._pyx18.call_function(D:\release\7420WLS\SCPO\weblogic\config\weblogic\setup\createManuWLSDomain.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
at weblogic.management.scripting.WLST.main(WLST.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.WLST.main(WLST.java:29)
Caused by: java.util.MissingResourceException: Error parsing jdbcdrivers.xml
at com.bea.plateng.domain.jdbc.JDBCAspectHelper.getGenericJDBCDriverInfo(JDBCAspectHelper.java:850)
at com.bea.plateng.domain.jdbc.JDBCAspectHelper.getGenericJDBCDriverInfo(JDBCAspectHelper.java:223)
at com.bea.plateng.domain.aspect.XBeanJDBCConnectionPoolDriverNameConfigAspect.decompose(XBeanJDBCConnectionPoolDriverNameConfigAspect.java:56)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.setDelegate(AbstractConfigAspect.java:550)
at com.bea.plateng.domain.aspect.FilteredConfigAspect.setDelegate(FilteredConfigAspect.java:333)
at com.bea.plateng.domain.aspect.XBeanConfigAspectBuilder.createJDBCConnectionPoolSimpleAspect(XBeanConfigAspectBuilder.java:300)
at com.bea.plateng.domain.aspect.AbstractConfigAspectBuilder.createJDBCConnectionPoolSimpleAspects(AbstractConfigAspectBuilder.java:288)
at com.bea.plateng.domain.operation.config.ConfigJDBCConnectionPool.createInitialSimpleAspects(ConfigJDBCConnectionPool.java:115)
at com.bea.plateng.domain.operation.HTableEditOperation.createSimpleTableModel(HTableEditOperation.java:784)
at com.bea.plateng.domain.operation.HTableEditOperation.getSimpleTableModel(HTableEditOperation.java:348)
at com.bea.plateng.domain.operation.HTableEditOperation.initSimpleTableModel(HTableEditOperation.java:654)
at com.bea.plateng.domain.DomainChecker.isOperationValid(DomainChecker.java:726)
at com.bea.plateng.domain.DomainChecker.getInvalidSection(DomainChecker.java:168)
at com.bea.plateng.domain.GeneratorHelper.validateConfig(GeneratorHelper.java:257)
at com.bea.plateng.domain.GeneratorHelper.validateDomainCreation(GeneratorHelper.java:235)
at com.bea.plateng.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:580)
at com.bea.plateng.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:704)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:270)
at org.python.core.PyInstance.invoke(PyInstance.java:261)
at org.python.pycode._pyx5.writeDomain$14(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py:70)
at org.python.pycode._pyx5.call_function(C:\Documents and Settings\j1007353\Local Settings\Temp\WLSTOfflineIni2466.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:267)
at org.python.core.PyFunction.__call__(PyFunction.java:172)
com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.jython.WLSTException: java.util.MissingResourceException: Error parsing jdbcdrivers.xml
The system cannot find the path specified.
0 file(s) copied.
Attempting to shutdown server ...
Checking JSP Precompilation ...
Thanks

Unable to parse an XML

Similar Messages

Maybe you are looking for