the presence of a rising column value makes me wonder if it's decided that you've already gotten all of the data.
Yes i'm using db connect v2.
my data are something around 2008 until now
i dont understand very right this field timestamp input_timestamp_format i cant input the format like YYYY-MM-dd HH:mm:ss I need to put real date to this field be valid like this 2015/05/19 20:57:02
i try put like this input_timestamp_format = YYY/MM/dd HH:mm:ss but splunk db connect don't accept.
connection = SM9
description = Coleta
index = oracle_servicecenter
input_timestamp_column_name = OPEN_TIME
input_timestamp_column_number = 1
input_timestamp_format = 2015/05/19 20/:57:02
interval = 24 * * * *
max_rows = 1000000
mode = tail
output_timestamp_format = YYYY-MM-dd HH:mm:ss
query = select * from log_report_adm.v_sm_open_documents
source = /opt/splunk/var/log/splunk/rpc.log
sourcetype = coleta_oracle_incidentes
ui_query_catalog = NULL
ui_query_mode = advanced
tail_rising_column_name = IDENTIFICADOR
tail_rising_column_number = 5
ui_query_schema = SPLUNK_SMUBR
tail_follow_only = 1
I thought I had the answer thinking you were using dbconnect1 but now I can see you are definitely using dbconnect2.
One of the main thing to check is to be sure your data isn't older than 2000 days as there is a default limit in the app out of the box.
Note: Be aware that DB Connect abides by the MAX_DAYS_AGO setting in the Splunk Enterprise props.conf file. When set, MAX_DAYS_AGO defines the number of days in the past, from the current date, that a date is considered valid. This means that any imported records with timestamps before today's date minus MAX_DAYS_AGO will not be indexed. The default setting for MAX_DAYS_AGO is 2000 days, so if you use DB Connect to consume database data that is older than that, you should increase that value in props.conf.
Secondly and the most likely is your input timestamp format. See below
input_timestamp_format = <value>
* specify the format of input timestamp column, in JavaSimpleDateString format.