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$OiiiIns tallCompElementHandler.onStart(OiiiCompsXMLHandler .java:873)
at
oracle.sysman.oix.oixs.OixsElementHandler.startEle ment(OixsElementHandler.java:140)
at
oracle.sysman.oix.oixs.OixsDefaultHandler.startEle ment(OixsDefaultHandler.java:109)
at
oracle.xml.parser.v2.XMLContentHandler.startElemen t(XMLContentHandler.java:180)
at
oracle.xml.parser.v2.NonValidatingParser.parseElem ent(NonValidatingParser.java:1224)
at
oracle.xml.parser.v2.NonValidatingParser.parseRoot Element(NonValidatingParser.java:311)
at
oracle.xml.parser.v2.NonValidatingParser.parseDocu ment(NonValidatingParser.java:278)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.jav a:185)
at
oracle.sysman.oii.oiii.OiiiInstallXMLReader.readCo mps(OiiiInstallXMLReader.java:271)
at
oracle.sysman.oii.oiii.OiiiInstallInventory.getCom pOHListElement(OiiiInstallInventory.java:1402)
at
oracle.sysman.oii.oiii.OiiiAreaInventory.getAllCom psVect(OiiiAreaInventory.java:1052)
at opatch.UpdateInventory.update(UpdateInventory.java :571)
at opatch.UpdateInventory.main(UpdateInventory.java:4 31)
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$OiiiIns tallCompElementHandler.onStart(OiiiCompsXMLHandler .java:873)
at
oracle.sysman.oii.oiii.OiiiCompsXMLHandler$OiiiIns tallPatchSetElementHandler.onStart(OiiiCompsXMLHan dler.java:1784)
at
oracle.sysman.oix.oixs.OixsElementHandler.startEle ment(OixsElementHandler.java:140)
at
oracle.sysman.oix.oixs.OixsDefaultHandler.startEle ment(OixsDefaultHandler.java:109)
at
oracle.xml.parser.v2.XMLContentHandler.startElemen t(XMLContentHandler.java:180)
at
oracle.xml.parser.v2.NonValidatingParser.parseElem ent(NonValidatingParser.java:1224)
at
oracle.xml.parser.v2.NonValidatingParser.parseRoot Element(NonValidatingParser.java:311)
at
oracle.xml.parser.v2.NonValidatingParser.parseDocu ment(NonValidatingParser.java:278)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.jav a:185)
at
oracle.sysman.oii.oiii.OiiiInstallXMLReader.readCo mps(OiiiInstallXMLReader.java:271)
at
oracle.sysman.oii.oiii.OiiiInstallInventory.getCom pOHListElement(OiiiInstallInventory.java:1402)
at
oracle.sysman.oii.oiii.OiiiAreaInventory.getAllCom psVect(OiiiAreaInventory.java:1052)
at opatch.UpdateInventory.update(UpdateInventory.java :571)
at opatch.UpdateInventory.main(UpdateInventory.java:4 31)
[...]
-------------------------------------------------------------------

And so on, with several dates. I ran checkinv.pl after the
installation, and it showed no errors:
-------------------------------------------------------------------
oracle@nswe29 ~/patches $ perl checkinv.pl


----------------------------------
This utility will do the following:
1) Detect if your inventory and filemap are in good state or not.
2) 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

Thorsten Jens <thojens@gmx.de> wrote:
> 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$OiiiIns tallCompElementHandler.onStart(OiiiCompsXMLHandler .java:873)

[...]

> Has anybody ran into this before?

I searched Metalink and it seems that somebody encountered the same error:
"The problem happens after applying 9.2.0.5 patchset
or after installing Oracle Universal Installer 10.1.0.2.0 on top of 9.2.0.4"

The bug number is 3558215.

Oracle said that they tried to reproduce the problem without success,
and the bug is set to status "Closed, Not a Bug".

Not much help, but maybe a reference...

Yours,
Laurenz Albe

Laurenz Albe wrote:
> Thorsten Jens <thojens@gmx.de> wrote:
> > 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$OiiiIns tallCompElementHandler.onStart(OiiiCompsXMLHandler .java:873)
>
> [...]
>
> > Has anybody ran into this before?
>
> I searched Metalink and it seems that somebody encountered the same error:
> "The problem happens after applying 9.2.0.5 patchset
> or after installing Oracle Universal Installer 10.1.0.2.0 on top of 9.2.0.4"
>
> The bug number is 3558215.

Hmm. I couldn't reproduce this on a different machine, either. Let's
see what the third instance says when I update it on Saturday.

Thorsten
--
Any broken formatting is brought to you by Google Groups.

Thorsten Jens wrote:
> Laurenz Albe wrote:
> > Thorsten Jens <thojens@gmx.de> wrote:
> > > 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$OiiiIns tallCompElementHandler.onStart(OiiiCompsXMLHandler .java:873)
> >
> > [...]
> >
> > > Has anybody ran into this before?
> >
> > I searched Metalink and it seems that somebody encountered the same error:
> > "The problem happens after applying 9.2.0.5 patchset
> > or after installing Oracle Universal Installer 10.1.0.2.0 on top of 9.2.0.4"
> >
> > The bug number is 3558215.
>
> Hmm. I couldn't reproduce this on a different machine, either. Let's
> see what the third instance says when I update it on Saturday.

Not reproducible.

Thorsten

Thorsten Jens <thojens@gmx.de> wrote:
>> > > 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$OiiiIns tallCompElementHandler.onStart(OiiiCompsXMLHandler .java:873)
>>
>> Hmm. I couldn't reproduce this on a different machine, either. Let's
>> see what the third instance says when I update it on Saturday.
>
> Not reproducible.

It looks to me like a date string is dug up from somewhere and parsed,
and sometimes an unparsable date is encountered.
Maybe if you install it on August 12 after a leap year, it will fail :^)

Yours,
Laurenz Albe