The issue here is that Pro*C (and PL/SQL) use the Oracle SQL parser to parse SQL that is embedded in Pro*C (or PL/SQL) code at compile time but then at execution time it gets sent to the TimesTen SQL engine for execution. Since the Oracle and TimesTen SQL dialects are currently not identical issues liek thsi can arise. Oracle database does not support / understand the SELECT FIRST n syntax used here so the compilation fails. The solution is to use dynamic SQL so that the SQL is not parsed at Pro*C compilation time but rather at Pro*C execution time.
My application is taking more time with Timesten than Oracle for SELECT (approx 350 microseconds) and UPDATE (370 microseconds). Its hould be in the range of 20 - 30 microseconds. Please let me know if I need to check for any specific TT parameter.
This is a bit like going to a doctor and saying 'I'm not feeling well, what might be the problem?'.
Please provide details, lots of details. Without details we cannot help. There are hundreds, maybe thousands of things that you could check but probably only a few of them are relevant...
Perhaps start with table schema, row count, indexes, are stats updated, what is the query plan, what does application code that processes the SELECT look like, is this direct mode or client server etc. etc.