Java AS 700 Post install error

[Former Member]

I am getting an error after install of the java AS 700 when I am trying to run the JSPM. It's telling me it cannot locate the DBINFO.XML file.

I'm sure I've missed a step somewhere but I cant find any note or anything with DBINFO.XML in it.

The SDM, http etc are all running fine.

TIA,

M

[Former Member]

Hi Michael,

Please try to upgrade your JSPM to 5.0(atleast) or 6.0

using the SDM.

Otherwise try delpoying packages using SDM. Let us know

if JSPM upgrade works.

Regards,

Srikishan

[Former Member]

Hi,

I upgraded to 5.0 and still got the same error and then upgraded again using SDM to the 6.0 version of JSPM. The upgrades went fine but I still get the error message that is unable to find the DBINFO.XML in the JSPM\config folder (which actually doesnt exist). I have no idea what process actually creates this file. The rest of the stack appears to be operating normally.

Thanks for your help.

M.

[Former Member]

Mike,

I am not sure what step you missed. But, I was able to find the file, DBINFO.XML in the JSPM\config folder of my installation.

Here is the content of the file for your reference:

[code]

<b><?xml version="1.0"?>

<VariableHandler name="DBINFO">

<StringVariable name="DB/CODE">ORA<StringVariable>

<StringVariable name="DB/NAME">Oracle</StringVariable>

<StringVariable name="DB/VERS">10.1.0.4.0</StringVariable>

</VariableHandler>

<!-- $VL:MdxuQC$></b>

[/code]

Regards,

Teecheu Loh

[Former Member]

Hi Michael,

The JSPM uses the DMT tool to detect the DB info. The DB

information is stored in the file DBINFO.xml. Now the

problem you are facing might be due to a corrupt version

in the DB table or the JDBC driver.

This is a known error in JSPM 4.0, but was supposed to

be fixed in JSPM 5.0.

Note 855801 may help, if you are using MSSQL.

Regards

Srikishan

[Former Member]

SOLUTION:

Turns out that my %JAVA_HOME% variable was point to the JRE from the initial install. I never changed it to the JDK path.

I discovered this because the logs were telling me that that it didnt support the cp850 bin2. A quick search on that turned up a note explaining that this variable was pointing in the wrong place.

M.