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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Developer Spotlight with Eduard Lekanne

From Network Engineer to Building Agentic AI for Splunk Eduard Lekanne has been architecting technology ...

From Data Landing to Insight

Search Across More of Your Data Ecosystem The data you need may live in Splunk, high-volume machine data, ...

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...