Java Exceptions during installation of CPU 10/2005

From: Thorsten Jens <thojens_at_gmx.de>
Date: 30 Oct 2005 22:49:44 -0800
Message-ID: <1130741384.395425.150240@o13g2000cwo.googlegroups.com>

Hi,

during installation of CPU 10/2005 on 9.2.0.7 on Solaris 8 (64 bit), I get a couple of Java Excaptions:

[...]
Updating inventory...
sInstallTime = >2005.Aug.12 11:39:38 MEST< java.text.ParseException: Unparseable date: "2005.Aug.12 11:39:38 MEST"

        at java.text.DateFormat.parse(DateFormat.java:324)
        at
oracle.sysman.oii.oiii.OiiiCompsXMLHandler$OiiiInstallCompElementHandler.onStart(OiiiCompsXMLHandler.java:873)
        at
oracle.sysman.oix.oixs.OixsElementHandler.startElement(OixsElementHandler.java:140)
        at
oracle.sysman.oix.oixs.OixsDefaultHandler.startElement(OixsDefaultHandler.java:109)
        at
oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:180)
        at
oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1224)
        at
oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:311)
        at
oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:278)
        at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:185)
        at
oracle.sysman.oii.oiii.OiiiInstallXMLReader.readComps(OiiiInstallXMLReader.java:271)
        at
oracle.sysman.oii.oiii.OiiiInstallInventory.getCompOHListElement(OiiiInstallInventory.java:1402)
        at
oracle.sysman.oii.oiii.OiiiAreaInventory.getAllCompsVect(OiiiAreaInventory.java:1052)
        at opatch.UpdateInventory.update(UpdateInventory.java:571)
        at opatch.UpdateInventory.main(UpdateInventory.java:431)

sInstallTime = >2005.Oct.27 15:32:45 MEST< java.text.ParseException: Unparseable date: "2005.Oct.27 15:32:45 MEST"

        at java.text.DateFormat.parse(DateFormat.java:324)
        at
oracle.sysman.oii.oiii.OiiiCompsXMLHandler$OiiiInstallCompElementHandler.onStart(OiiiCompsXMLHandler.java:873)
        at
oracle.sysman.oii.oiii.OiiiCompsXMLHandler$OiiiInstallPatchSetElementHandler.onStart(OiiiCompsXMLHandler.java:1784)
        at
oracle.sysman.oix.oixs.OixsElementHandler.startElement(OixsElementHandler.java:140)
        at
oracle.sysman.oix.oixs.OixsDefaultHandler.startElement(OixsDefaultHandler.java:109)
        at
oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:180)
        at
oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1224)
        at
oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:311)
        at
oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:278)
        at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:185)
        at
oracle.sysman.oii.oiii.OiiiInstallXMLReader.readComps(OiiiInstallXMLReader.java:271)
        at
oracle.sysman.oii.oiii.OiiiInstallInventory.getCompOHListElement(OiiiInstallInventory.java:1402)
        at
oracle.sysman.oii.oiii.OiiiAreaInventory.getAllCompsVect(OiiiAreaInventory.java:1052)
        at opatch.UpdateInventory.update(UpdateInventory.java:571)
        at opatch.UpdateInventory.main(UpdateInventory.java:431)

[...]

And so on, with several dates. I ran checkinv.pl after the installation, and it showed no errors:

oracle_at_nswe29 ~/patches $ perl checkinv.pl

This utility will do the following:

Detect if your inventory and filemap are in good state or not.
If the inventory or filemap is in bad state, the utility will ask if you want to repair it.

We recommend you run this utility prior to applying any interim patch.

Press <enter> to continue.

Checking if environment variable ORACLE_HOME is set... Checking if ORACLE_HOME is valid...

Looking for /oracle/product/9.2.0/inventory...
Looking for /oracle/product/9.2.0/inventory/ContentsXML/comps.xml...
Looking for /oracle/product/9.2.0/inventory/filemap...

Creating temporary file
"/oracle/product/9.2.0/.patch_storage/checkinv_filemap_oneoff10-31-2005_7-22-17.txt" ...
Reading
"/oracle/product/9.2.0/.patch_storage/checkinv_filemap_oneoff10-31-2005_7-22-17.txt" Reading "/oracle/product/9.2.0/inventory/ContentsXML/comps.xml"

This is a list of patches detected using your comps.xml: [ 4567854 ]

This is a list of patches detected using your filemap: [ 4567854 ]

Your inventory is OK and doesn't have any dangling patches. You can now safely apply patches.

Has anybody ran into this before?

Thorsten Jens Received on Mon Oct 31 2005 - 00:49:44 CST