Topic
  • 5 replies
  • Latest Post - ‏2011-04-28T20:48:00Z by SystemAdmin
SystemAdmin
SystemAdmin
33 Posts

Pinned topic An internal error occurred during: "Deploy Change Commands".

‏2011-04-26T05:52:41Z |
  • Database Administrator 2.2.3 and Development Studio 2.2.1
  • OS is Win7-64 with a local instance of DB2 Express C 9.7.2

I receive this error when trying to run administration tasks such as taking a backup or configuring maintenance:

eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr7-20091214_49398 (JIT enabled, AOT enabled)
J9VM - 20091214_049398
JIT - r9_20091123_13891
GC - 20091111_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product com.ibm.datastudio.administrator.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86 -product com.ibm.datastudio.administrator.product.ide
Error
Mon Apr 25 22:37:38 PDT 2011
An internal error occurred during: "Deploy Change Commands".

java.lang.UnsatisfiedLinkError: db2dasjutil (.\db2dasjutil.dll is not a valid Win32 application. )
at java.lang.ClassLoader.loadLibraryWithPath(Unknown Source)
at java.lang.ClassLoader.loadLibraryWithClassLoader(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.ibm.db2.das.core.DasMessageIdentifier.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(Unknown Source)
at com.ibm.db2.das.core.DasService.<init>(Unknown Source)
at com.ibm.db2.das.core.DasCmd.<init>(Unknown Source)
at com.ibm.db2.das.core.DasDB2Cmd.<init>(Unknown Source)
at com.ibm.datatools.das.db2.luw.DASRemoteExecutor.initializeTarget(Unknown Source)
at com.ibm.datatools.das.db2.luw.HybridRemoteExecutor.initializeTarget(Unknown Source)
at com.ibm.dbtools.common.util.executor.RemoteCmdExecutor.<init>(Unknown Source)
at com.ibm.dbtools.common.util.executor.RemoteExecManager.<init>(Unknown Source)
at com.ibm.dbtools.common.ConnectionService.getRemoteExecManager(Unknown Source)
at com.ibm.datatools.changecmd.db2.DB2CmdChangeCommand.execute(Unknown Source)
at com.ibm.datatools.changecmd.db2.luw.ui.internal.deploy.DeployChangeListJob$UiExecuteChgListVisitor.visit(Unknown Source)
at com.ibm.datatools.changecmd.db2.luw.ui.internal.deploy.DeployChangeListJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

Thanks.
Jeff
Updated on 2011-04-28T20:48:00Z at 2011-04-28T20:48:00Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    33 Posts

    Re: An internal error occurred during: "Deploy Change Commands".

    ‏2011-04-26T15:11:18Z  
    Can you send me the output of db2level? I think you might have a bit width issue going on.
  • SystemAdmin
    SystemAdmin
    33 Posts

    Re: An internal error occurred during: "Deploy Change Commands".

    ‏2011-04-26T17:54:52Z  
    Can you send me the output of db2level? I think you might have a bit width issue going on.
    Thanks. Here it is.

    DB21085I Instance "DB2" uses "64" bits and DB2 code release "SQL09072" with
    level identifier "08030107".
    Informational tokens are "DB2 v9.7.200.358", "s100514", "IP23084", and Fix Pack
    "2".
    Product is installed at "C:\PROGRA~1\IBM\SQLLIB" with DB2 Copy Name "DB2COPY1".
  • SystemAdmin
    SystemAdmin
    33 Posts

    Re: An internal error occurred during: "Deploy Change Commands".

    ‏2011-04-27T19:15:18Z  
    Thanks. Here it is.

    DB21085I Instance "DB2" uses "64" bits and DB2 code release "SQL09072" with
    level identifier "08030107".
    Informational tokens are "DB2 v9.7.200.358", "s100514", "IP23084", and Fix Pack
    "2".
    Product is installed at "C:\PROGRA~1\IBM\SQLLIB" with DB2 Copy Name "DB2COPY1".
    The problem is happening because ODS is 32 bit while your environment is 64 bit. Is your ODA and DB2 Server installed on the same box? There are a few things we can try, once we know how your environment is setup.

    -Vinod
  • SystemAdmin
    SystemAdmin
    33 Posts

    Re: An internal error occurred during: "Deploy Change Commands".

    ‏2011-04-27T19:47:01Z  
    This issue has been resolved in DB2 FP4 and up. The problem was that the 32 bit DAS libraries were not being bundled with the 64 bit server. This caused problems when connecting from 32 bit ODA.

    -Vinod
  • SystemAdmin
    SystemAdmin
    33 Posts

    Re: An internal error occurred during: "Deploy Change Commands".

    ‏2011-04-28T20:48:00Z  
    This issue has been resolved in DB2 FP4 and up. The problem was that the 32 bit DAS libraries were not being bundled with the 64 bit server. This caused problems when connecting from 32 bit ODA.

    -Vinod
    Thanks Vinod. Applying FP4 resolved the problem.