Topic
5 replies Latest Post - ‏2012-12-14T18:05:07Z by SystemAdmin
JUW
JUW
3 Posts
ACCEPTED ANSWER

Pinned topic SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724,

‏2012-07-12T21:22:25Z |
Configuring library server with CM8.4.3.200 on AIX with DB2 9.7.4 64-bit, encountering follow exception.

Have anyone seen this error? please help, Thanks!!

2012-07-12 13:55:02 cmcfgls: TRACE -> Using connect string SCHEMA=icmadmin;DBAUTH=SERVER;REPTYPE=DB2;JDBCURL=jdbc:db2://9.30.142.3:50002/icmnlsdb;JDBCDRIVER=com.ibm.db2.jcc.DB2Driver
com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724, SQLERRMC=ICMLOGON;SQL120712135408101;.../sqllib/function/ICMNLSSP;ICM_logon;5, DRIVER=3.63.81
at com.ibm.db2.jcc.am.fd.a(fd.java:679)
at com.ibm.db2.jcc.am.fd.a(fd.java:60)
at com.ibm.db2.jcc.am.fd.a(fd.java:127)
at com.ibm.db2.jcc.am.yn.b(yn.java:2317)
at com.ibm.db2.jcc.am.yn.c(yn.java:2300)
at com.ibm.db2.jcc.t4.cb.l(cb.java:370)
at com.ibm.db2.jcc.t4.cb.f(cb.java:98)
at com.ibm.db2.jcc.t4.q.e(q.java:81)
at com.ibm.db2.jcc.t4.sb.k(sb.java:160)
at com.ibm.db2.jcc.am.yn.jb(yn.java:2266)
at com.ibm.db2.jcc.am.zn.b(zn.java:4319)
at com.ibm.db2.jcc.am.CallableStatement.fc(CallableStatement.java:113)
at com.ibm.db2.jcc.am.CallableStatement.execute(CallableStatement.java:96)
at com.ibm.mm.sdk.internal.sql.db2.PDB2CallableStatementICM.execute(PDB2CallableStatementICM.java:130)
at com.ibm.mm.sdk.internal.PSpParmICM.callSP(PSpParmICM.java:1021)
at com.ibm.mm.sdk.server.DKDatastoreICM.logon(DKDatastoreICM.java:2570)
at com.ibm.mm.sdk.server.DKDatastoreICM.connect(DKDatastoreICM.java:2311)
at com.ibm.cm.dbutil.ICMLSDBUtilities.buildCompTypes(ICMLSDBUtilities.java:72)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureCM(ICMConfigureLSDB.java:2268)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureLSDB(ICMConfigureLSDB.java:2212)
at com.ibm.cm.dbutil.ICMConfigureLSDB.start(ICMConfigureLSDB.java:3555)
at com.ibm.cm.dbutil.cmcfgdbu.startSilentMode(cmcfgdbu.java:226)
at com.ibm.cm.dbutil.cmcfgdbu.startConfig(cmcfgdbu.java:376)
at com.ibm.cm.dbutil.cmcfgdbu.main(cmcfgdbu.java:514)
com.ibm.cm.dbutil.ICMDBUtilsException: Fail to build component types
at com.ibm.cm.dbutil.ICMLSDBUtilities.buildCompTypes(ICMLSDBUtilities.java:94)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureCM(ICMConfigureLSDB.java:2268)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureLSDB(ICMConfigureLSDB.java:2212)
at com.ibm.cm.dbutil.ICMConfigureLSDB.start(ICMConfigureLSDB.java:3555)
at com.ibm.cm.dbutil.cmcfgdbu.startSilentMode(cmcfgdbu.java:226)
at com.ibm.cm.dbutil.cmcfgdbu.startConfig(cmcfgdbu.java:376)
at com.ibm.cm.dbutil.cmcfgdbu.main(cmcfgdbu.java:514)
2012-07-12 13:55:08.087 Return code is already set to 126 in CSO. Skipping update...
2012-07-12 13:55:08.087 DEBUG:: ====================== Configuration state information ======================
Return code: 126
Message code: DBU02126E
Message: Failed to build component types.
Exception: Fail to build component types
Exception stack trace:
com.ibm.cm.dbutil.ICMDBUtilsException: Fail to build component types
at com.ibm.cm.dbutil.ICMLSDBUtilities.buildCompTypes(ICMLSDBUtilities.java:94)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureCM(ICMConfigureLSDB.java:2268)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureLSDB(ICMConfigureLSDB.java:2212)
at com.ibm.cm.dbutil.ICMConfigureLSDB.start(ICMConfigureLSDB.java:3555)
at com.ibm.cm.dbutil.cmcfgdbu.startSilentMode(cmcfgdbu.java:226)
at com.ibm.cm.dbutil.cmcfgdbu.startConfig(cmcfgdbu.java:376)
at com.ibm.cm.dbutil.cmcfgdbu.main(cmcfgdbu.java:514)

=============================================================================
2012-07-12 13:55:08.088 DBCONFIG:: lsrte configuration finished at "2012-07-12 13:55:08 -0700" and took 3 minutes and 30.35 seconds to complete.
2012-07-12 13:55:08.113 DEBUG:: Writing ConfigState to: /opt/IBM/db2cmv8/log/install/ConfigState.obj
2012-07-12 13:55:08.131 DEBUG:: It is false that the current user is root or administrator.
2012-07-12 13:55:08.131 DEBUG:: Configuration state updated successfully in file /opt/IBM/db2cmv8/log/install/ConfigState.obj.
2012-07-12 13:55:08.131 ConfigService.writeConfigState(): Information in CSO file "/opt/IBM/db2cmv8/log/install/ConfigState.obj":
====================== Configuration state information ======================
Exit code: 126
Return code: 126
Message code: DBU02126E
Message: Failed to build component types.
Exception: Fail to build component types
Exception stack trace:
com.ibm.cm.dbutil.ICMDBUtilsException: Fail to build component types
at com.ibm.cm.dbutil.ICMLSDBUtilities.buildCompTypes(ICMLSDBUtilities.java:94)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureCM(ICMConfigureLSDB.java:2268)
at com.ibm.cm.dbutil.ICMConfigureLSDB.configureLSDB(ICMConfigureLSDB.java:2212)
at com.ibm.cm.dbutil.ICMConfigureLSDB.start(ICMConfigureLSDB.java:3555)
at com.ibm.cm.dbutil.cmcfgdbu.startSilentMode(cmcfgdbu.java:226)
at com.ibm.cm.dbutil.cmcfgdbu.startConfig(cmcfgdbu.java:376)
at com.ibm.cm.dbutil.cmcfgdbu.main(cmcfgdbu.java:514)
Updated on 2012-12-14T18:05:07Z at 2012-12-14T18:05:07Z by SystemAdmin
  • JKMorrow
    JKMorrow
    44 Posts
    ACCEPTED ANSWER

    Re: SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724,

    ‏2012-07-12T21:41:46Z  in response to JUW
    The stored procedure ICMLOGON is not found. It may STOPPED or in STOPABND status.
    • JUW
      JUW
      3 Posts
      ACCEPTED ANSWER

      Re: SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724,

      ‏2012-07-12T22:38:43Z  in response to JKMorrow
      Hi JKMorrow,

      Thanks for the reply!

      I did see ICMLOGON procedure completed successfully. Would you please explain a little more? I have posted cmconfig.log for your reference. It's blocking me to install CM843 on AIX box. :-( Thank you!

      2012-07-12 14:20:16 cmcfgls: TRACE -> create procedure ICMLOGON
      2012-07-12 14:20:16 cmcfgls: TRACE -> (
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lRC INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lReason INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lExtRC INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lExtReason INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> InOut sTraceLevel SMALLINT,
      2012-07-12 14:20:16 cmcfgls: TRACE -> In lReserved1 INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> InOut szUserInfo VARCHAR(254),
      2012-07-12 14:20:16 cmcfgls: TRACE -> InOut szUserToken CHAR(32),
      2012-07-12 14:20:16 cmcfgls: TRACE -> InOut lReserved INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> InOut szLanguageCode CHAR(3),
      2012-07-12 14:20:16 cmcfgls: TRACE -> InOut szUserID VARCHAR(32),
      2012-07-12 14:20:16 cmcfgls: TRACE -> In szPassword CHAR(48) FOR BIT DATA,
      2012-07-12 14:20:16 cmcfgls: TRACE -> In szNewPassword CHAR(48) FOR BIT DATA,
      2012-07-12 14:20:16 cmcfgls: TRACE -> In szApplication VARCHAR(32670),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szUserName VARCHAR(128),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lUserPrivSetCode INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lGrantPrivSetCode INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lDfltItemACLCode INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out sDfltRMCode SMALLINT,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out sDfltSMSCollection SMALLINT,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szUserPrivSetName VARCHAR(32),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szGrantPrivSetName VARCHAR(32),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szDfltACLName VARCHAR(32),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szDfltRMName VARCHAR(128),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szDfltSMSCollectio VARCHAR(44),
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out sSystemFlag SMALLINT,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lMaxResultSetSize INTEGER,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out szPlatform SMALLINT,
      2012-07-12 14:20:16 cmcfgls: TRACE -> Out lUserDomainID INTEGER
      2012-07-12 14:20:16 cmcfgls: TRACE -> )
      2012-07-12 14:20:16 cmcfgls: TRACE -> DYNAMIC RESULT SETS 2
      2012-07-12 14:20:16 cmcfgls: TRACE -> LANGUAGE C
      2012-07-12 14:20:16 cmcfgls: TRACE -> PARAMETER STYLE DB2SQL
      2012-07-12 14:20:16 cmcfgls: TRACE -> NO DBINFO
      2012-07-12 14:20:16 cmcfgls: TRACE -> FENCED
      2012-07-12 14:20:16 cmcfgls: TRACE -> PROGRAM TYPE SUB
      2012-07-12 14:20:16 cmcfgls: TRACE -> EXTERNAL NAME 'ICMNLSSP!ICM_logon'
      2012-07-12 14:20:16 cmcfgls: TRACE -> DB20000I The SQL command completed successfully.
  • MikeAA
    MikeAA
    36 Posts
    ACCEPTED ANSWER

    Re: SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724,

    ‏2012-07-13T00:58:34Z  in response to JUW
    If I understand this error correctly

    2012-07-12 13:55:02 cmcfgls: TRACE -> Using connect string SCHEMA=icmadmin;DBAUTH=SERVER;REPTYPE=DB2;JDBCURL=jdbc:db2://9.30.142.3:50002/icmnlsdb;JDBCDRIVER=com.ibm.db2.jcc.DB2Driver
    com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724, SQLERRMC=ICMLOGON;SQL120712135408101;.../sqllib/function/ICMNLSSP;ICM_logon;5, DRIVER=3.63.81

    I think the reason code is '5' The DB2 infocenter entry for sqlcode=-444 reason 5 suggests there is insufficient memory. Link: http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql.doc%2Fdoc%2Fmsql00444n.html
    • JUW
      JUW
      3 Posts
      ACCEPTED ANSWER

      Re: SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724,

      ‏2012-07-13T17:16:58Z  in response to MikeAA
      Hi MikeAA,

      Thanks for the information,

      My AIX box is quite powerful (listed below), I guess insufficient memory might not be the issue, however the 2nd point in the link you sent that made me to check the db2diag.log.

      Processor Version: PV_4_2
      Number Of Processors: 10
      Processor Clock Speed: 1904 MHz
      CPU Type: 64-bit
      Kernel Type: 64-bit
      LPAR Info: 1 ArAnderson
      Memory Size: 74752 MB
      Good Memory Size: 74752 MB

      How come "shr_64.o" and "shr.o" are not found in archive that caused ICMNLSSP couldn't be loaded?

      ========== db2diag.log =======
      2012-07-13-09.49.23.686155-420 E1245706A795 LEVEL: Error (OS)
      PID : 5046598 TID : 1 PROC : db2fmp (4210) 0
      INSTANCE: db2inst1 NODE : 000
      EDUID : 1 EDUNAME: db2fmp (4210) 0
      FUNCTION: DB2 UDB, oper system services, sqloAIXLoadModuleTryShr, probe:130
      CALLED : OS, -, dlopen
      OSERR : ENOEXEC (8) "Cannot run a file that does not have a valid format."
      MESSAGE : Attempt to load specified library failed.
      DATA #1 : Library name or path, 41 bytes
      /edisco/db2inst1/sqllib/function/ICMNLSSP
      DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
      2
      DATA #3 : String, 148 bytes
      0509-022 Cannot load module /edisco/db2inst1/sqllib/function/ICMNLSSP.
      0509-026 System error: Cannot run a file that does not have a valid format.

      2012-07-13-09.49.23.706303-420 E1246502A823 LEVEL: Error (OS)
      PID : 5046598 TID : 1 PROC : db2fmp (4210) 0
      INSTANCE: db2inst1 NODE : 000
      EDUID : 1 EDUNAME: db2fmp (4210) 0
      FUNCTION: DB2 UDB, oper system services, sqloAIXLoadModuleTryShr, probe:140
      CALLED : OS, -, dlopen
      OSERR : ENOEXEC (8) "Cannot run a file that does not have a valid format."
      MESSAGE : Attempt to load specified library augmented with object name failed.
      DATA #1 : Library name or path, 51 bytes
      /edisco/db2inst1/sqllib/function/ICMNLSSP(shr_64.o)
      DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
      262146
      DATA #3 : String, 134 bytes
      0509-022 Cannot load module /edisco/db2inst1/sqllib/function/ICMNLSSP(shr_64.o).
      • 0509-152 Member shr_64.o is not found in archive*

      2012-07-13-09.49.25.494907-420 E1247326C799 LEVEL: Error (OS)
      PID : 3080198 TID : 1 PROC : db2fmp32 (4210) 0
      INSTANCE: db2inst1 NODE : 000
      EDUID : 1 EDUNAME: db2fmp32 (4210) 0
      FUNCTION: DB2 UDB, oper system services, sqloAIXLoadModuleTryShr, probe:130
      CALLED : OS, -, dlopen
      OSERR : ENOEXEC (8) "Cannot run a file that does not have a valid format."
      MESSAGE : Attempt to load specified library failed.
      DATA #1 : Library name or path, 41 bytes
      /edisco/db2inst1/sqllib/function/ICMNLSSP
      DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
      2
      DATA #3 : String, 148 bytes
      0509-022 Cannot load module /edisco/db2inst1/sqllib/function/ICMNLSSP.
      0509-026 System error: Cannot run a file that does not have a valid format.

      2012-07-13-09.49.25.539557-420 E1248126C818 LEVEL: Error (OS)
      PID : 3080198 TID : 1 PROC : db2fmp32 (4210) 0
      INSTANCE: db2inst1 NODE : 000
      EDUID : 1 EDUNAME: db2fmp32 (4210) 0
      FUNCTION: DB2 UDB, oper system services, sqloAIXLoadModuleTryShr, probe:140
      CALLED : OS, -, dlopen
      OSERR : ENOEXEC (8) "Cannot run a file that does not have a valid format."
      MESSAGE : Attempt to load specified library augmented with object name failed.
      DATA #1 : Library name or path, 48 bytes
      /edisco/db2inst1/sqllib/function/ICMNLSSP(shr.o)
      DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
      262146
      DATA #3 : String, 128 bytes
      0509-022 Cannot load module /edisco/db2inst1/sqllib/function/ICMNLSSP(shr.o).
      • 0509-152 Member shr.o is not found in archive*

      2012-07-13-09.49.25.851203-420 E1248945A471 LEVEL: Event
      PID : 4260172 TID : 4210 PROC : db2sysc 0
      INSTANCE: db2inst1 NODE : 000 DB : ICMNLSDB
      APPHDL : 0-262 APPID: 9.30.142.3.34024.120713165203
      AUTHID : ICMADMIN
      EDUID : 4210 EDUNAME: db2agent (idle) 0
      FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::TermDbConnect, probe:2000
      STOP : DATABASE: ICMNLSDB : DEACTIVATED: NO
      • SystemAdmin
        SystemAdmin
        228 Posts
        ACCEPTED ANSWER

        Re: SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-444, SQLSTATE=42724,

        ‏2012-12-14T18:05:07Z  in response to JUW
        Hi Guys,
        Have you were able to resolve this above issue?
        Im having exactly the same thing with CM 8.4.2 & DB2 9.7