DB Connect Rising Column type

[gilla]

Hi,

I have some problem.
My database table rising_column type is varchar2.
So tail monitoring is not working.
We cannot change column type and we have no number, date type of rising column.
How can I do ?

[Dan · Accepted solution]

Rising column can be any column type that is comparable. Technically, varchar2 is comparable (see here for details from Oracle). Although tail monitoring will function, it may not give you desired results.

It could be that your table just isn't a good candidate for tail input. You can consider the dump input instead. Or, you can add an auto-incrementing field to the table, which won't require developers to write any extra SQL for every INSERT (see here again for Oracle).

[gilla]

I'm really sorry about this situation.
Yes... DBX app is working correctly.
I have simple mistake of configuration.
And now everything is OK!!!
DBX App is very very nice App!!!
Thank you very much, Dan!!!

[Dan]

The string representation of time should be comparable in the right way. This should work.

One thing you will have to change is your output timestamp formatting, so that the events make it into Splunk in the right way. In your stanza in inputs.conf:

output.timestamp = 1
output.timestamp.column = USE_START_DTIME
output.timestamp.parse.format = yyyyMMddHHmmss


[gilla]

Thank you for your answer.
But my customer do not want to modify database table.
And table is very large size and quickly increasing, so dump input is not available.
Column name is USE_START_DTIME, type is varchar2(14).
and data is 20130123102132. It is timestamp, but DB Connect App recognize string format. State.xml is below :


20130121182208


And value key is not update. It means tail function is not working.

Anyway, thank you again, Dan!!!