Topic
  • 3 replies
  • Latest Post - ‏2013-09-25T17:41:03Z by joechen@us.ibm.com
mantovani
mantovani
8 Posts

Pinned topic DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DB2INST.APPSOFTWARE, DRIVER=3.63.123

‏2013-09-11T17:16:29Z |

Hi, I just installed MDM V10.1(default OOTB) on WAS 8.0.0.7 and DB2 v10.1.0.0 without any error during the installation in a Red Hat Enterprise Linux Client release 6.4. But when I run any transaction (like search party in DSUI) I get this wired error message:

Orb Version = IBM Java ORB build orb626ifx-20130530.00 (IX90121)
************* End Display Current Environment *************
[9/11/13 12:37:56:534 EDT] 0000002b SystemOut     O ERROR     - com.ibm.mdm.cache.common.CacheLoaderException: CacheLoader Exception in getCache: java.lang.RuntimeException: java.lang.Exception: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DB2INST.APPSOFTWARE, DRIVER=3.63.123
 

I'm attaching my full WAS logs(logs.zip) and my installation logs(InfoSphere_MDM_Server_InstallLog.log), so you can check analyze it.

  • mantovani
    mantovani
    8 Posts

    Re: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DB2INST.APPSOFTWARE, DRIVER=3.63.123

    ‏2013-09-11T17:48:39Z  

    Fixed, http://www-01.ibm.com/support/docview.wss?uid=swg21503879

  • mantovani
    mantovani
    8 Posts

    Re: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DB2INST.APPSOFTWARE, DRIVER=3.63.123

    ‏2013-09-12T01:39:54Z  

    This is not fixed, for some reason MDM is not creating APPSOFTWARE table. I don't know more what to do.

  • joechen@us.ibm.com
    6 Posts

    Re: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DB2INST.APPSOFTWARE, DRIVER=3.63.123

    ‏2013-09-25T17:41:03Z  

    This is not fixed, for some reason MDM is not creating APPSOFTWARE table. I don't know more what to do.

    if APPSOFTWARE db table was found missing or empty after your MDM Server v10.1 installation, the install was not successful.  Please check your installation logs to determine the failed install step(s) and reinstall after the necessary corrections.