Symptom
SQL0104N An unexpected token "ORDER" was found following "TINENAME = ? ) AS T2". Expected tokens may include: "<join_type_without_spec> JOIN <join_operand". SQLSTATE=42601
C *** ERROR in prepareStatement[dbdb6.c, 15581] CON = 1 (BEGIN)
C &+ dsql_db6_open( SQLExtendedPrepare ): [IBM][CLI Driver][DB2/AIX64] SQL0104N An unexpected token "ORDER" was found
C &+ following "TINENAME = ? ) AS T2". Expected tokens may include: "<join_type_without_spec> JOIN <join_operand". S
C &+ QLSTATE=42601
C &+
C &+ SELECT TIMESTAMP FROM ( SELECT CURRENT TIMESTAMP - 48 HOURS AS TIMESTAMP FROM SYSIBM.SYSDUMMY1 ) AS T
C &+ 1 UNION ( SELECT ALTER_TIME AS TIMESTAMP FROM SYSIBM.SYSDUMMY1, SYSCAT.ROUTINES
C &+ WHERE ROUTINESCHEMA = ? AND ROUTINENAME = ? ) AS T2 ORDER BY TIMESTAMP DESC FETCH FIRST 1 ROWS ONLY
C &+ cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=18, read_only=0
C &+
C &+ ABAP location info 'CL_SQL_STATEMENT==============CP', 468
C &+ SAP user '<sap_user>', transaction code 'DBACOCKPIT'
The solution is only valid if you find the exact statement as above.
this SQL0104N is slightly different (ORDER token compared to VALUES token) from SQL0104N in SAP KBA 2508138 - DB6: SQL0104N error in SAP system log
Read more...
Environment
upgraded from DB2 9.7 . . . to . . . DB2 10.5 FP8
version 71 of SAP NOTE 1456402 - DB6: DBA Cockpit Corrections for SAP Basis 7.02/7.30/7.31/7.40 to SOLMAN and managed systems
Product
Keywords
KBA , BC-DB-DB6-CCM , CCMS/Database Monitors , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.