All Apps and Add-ons

com.microsoft.sqlserver.jdbc.SQLServerException: The index 1 is out of range

anitaroseline
New Member

i receive index 1 out of range error while i enter the below query.Please help .

SELECT [NUMBER]
      ,[OPEN]
      ,[CATEGORY]
      ,[SUBCATEGORY]
      ,[MODEL]
      ,[CURRENT_PHASE]
      ,[IMPACT]
      ,[STATUS]
      ,[PRIORITY]
      ,[APPROVAL_STATUS]
      ,[ALERT]
      ,[ALERT_NAMES]
      ,[PENDING_GROUPS]
      ,[REASON]
      ,[SUBMIT_DATE]
      ,[CLOSE_DATE]
      ,[CANCELLED_DATE]
      ,[REQUESTOR_NAME]
      ,[COORDINATOR_NAME]
      ,[COORDINATOR_DEPT]
      ,[ASSIGNED_TO]
      ,[PLANNED_START]
      ,[PLANNED_END]
      ,[REQUESTED_FOR]
      ,[COMPANY]
      ,[ALERT_STATUS]
      ,[SVC_OPTIONS]
      ,[FOLDER]
      ,[SLA_BREACH]
      ,[NEXT_BREACH]
      ,[SVCCARTID]
      ,[AGREEMENT_IDS]
      ,[ASSIGNED_GROUP]
      ,[CUST_VISIBLE]
      ,[CLOSURE_CODE]
      ,[DELIVERY_DATE]
      ,[CLOSED_BY]
      ,[GLOBAL_LEAD_TIME]
      ,[REQUESTED_DATE]
      ,[MODELNAME]
      ,[SYSMODTIME]
      ,[SYSMODUSER]
      ,[SYSMODCOUNT]
      ,[SEVERITY]
      ,[OPENED_BY]
      ,[AFFECTED_ITEM]
      ,[LOGICAL_NAME]
      ,[ESCALATED]
      ,[OWNER]
      ,[LABOR]
      ,[FOREIGN_ID]
      ,[OTRSREFERENCENUMBER]
      ,[LASTASSIGNMENTGROUP]
      ,[REFERENCE_ID]
      ,[TICKET_TYPE]
      ,[OTRSINTERFACE]
      ,[ATTACHDATA]
      ,[ATTACHFILENAME]
      ,[LANGUAGE]
      ,[FULFILMENT_DATEOLY]
      ,[REQUEST_SUBSTATUS]
      ,[INCIDENT_ID]
      ,[REQVIPUSER]
      ,[EUCDEVICETYPE]
      ,[OSTEREFERENCENUMBER]
      ,[KPF_ID]
      ,[BACKTOFULFILLDATE]
      ,[BACKTOFULFILL]
      ,[OLY_TTR]![alt text][1]
      ,[OLY_IO_OFFICER]
      ,[OLY_SALES_OFFICER]
      ,[OLY_COUNTRY]
      ,[OLY_ORIGIN]
      ,[OLY_FIELD_TECHNICIAN]
      ,[OLY_FIELD_TECHNICIAN1]
      ,[OLY_BACKTOFULFILL_LIST]
      ,[OLY_DEFAULT_SLA]
   ,[BRIEF_DESCRIPTION]
  FROM [servicemanager].[dbo].[REQUESTM1] where SYSMODTIME >= '2018-10-01 00:00:12.000' ORDER BY SYSMODTIME ASC
Tags (2)
0 Karma

sloshburch
Ultra Champion

I believe I've seen this issue occur when I've failed to incorporate the checkpoint for rising column into the SQL.
So you'll need to add to your where clause the checkpoint. If SYSMODTIME is your rising tail column then just make this the where clause:

where SYSMODTIME > ? AND SYSMODTIME >= '2018-10-01 00:00:12.000'

Keep the ORDER BY as is.

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...