1.1.1

Table Of Contents
EnablesTrace flag
Client-side connection open and close stack traces.TraceClientConn
Client-side, basic timing logging.TraceClientStatement
Client-side wall clock timing.TraceClientStatementMillis
Detailed index logging.TraceIndex
Logging for JAR installation, replace, and remove events.TraceJars
Detailed logging for transaction events and operations, including
commit and rollback.
TraceTran
Locking and unlocking information for all internal locks.TraceLock_*
Logging for all DataDictionary and table locks that are acquired or
released.
TraceLock_DD
If you are asked to set a trace ag in a SQLFire member for debugging purposes, do so using the
sqlfire.debug.true system property when you start a server or locator. For example, this command sets
both the QueryDistribution and TraceIndex ags:
sqlf server start -J-Dsqlfire.debug.true=QueryDistribution,TraceIndex
For applications that use the JDBC peer driver, set trace-related ags in the sqlre.debug.true system property
before the application connects to the SQLFire cluster. For example, this code sets traces for index and query
distribution and then connects using the peer driver:
Properties props = new Properties();
props.put("sqlfire.debug.true", "TraceIndex,QueryDistribution");
System.setProperties(props);
Java.sql.Connection conn =
java.sql.DriverManager.getConnection("jdbc:sqlfire:");
Client-side trace ags write additional information to the client log le, which is congured using the log-le
property.
If you need to set a trace ag in a running system, use the SYS.SET_TRACE_FLAG system procedure. The
procedure sets the trace ag in all members of the distributed system, including locators. You must execute the
procedure as a system user. For example:
sqlf> call sys.set_trace_flag('traceindex', 'true');
Statement executed.
263
Configuring and Using SQLFire Log Files