ttDaemonLog

Description

TimesTen uses a TimesTen daemon (referred to as the TimesTen Data Manager Service on Windows) and other background processes, known as subdaemons and agents, to manage access to the either the "user" or "error" log.

By default, TimesTen messages are stored in:

• A user error log that contains information you may need to see. Generally, these messages contain information on actions you may need to take.

• A support log containing everything in the user error log plus information of use by TimesTen Customer Support.

The ttDaemonLog utility allows you to control the type of events that are written to and fetched from the TimesTen user and error logs.

There are two versions of the ttDaemonLog utility:

• ttDaemonLog for Windows

• ttDaemonLog for UNIX

Required privilege

This utility requires the instance administrator privilege.

---

ttDaemonLog for Windows

On Windows, TimesTen user and error log messages are written to the Windows Application Event Log. The ttDaemonLog utility controls which events are written to and fetched from the log and displayed to stdout.

Syntax

ttDaemonLog {-h | -help | -?}
ttDaemonLog {-V | -version}
ttdaemonlog [-show type] [-b | -r | -s] [-f] [-maxlines]
[-loglevel level [DSN | [-connstr] connStr]]
[-[no]logcomponent component [DSN | [-connstr] connStr]]
[-logreset] [-msg messagestring] [-setquiet | -setverbose]
[-n computer]

Options

ttDaemonLog has the options:

Examples

By default, the ttDaemonLog utility logs messages and errors from all of the TimesTen components. You can narrow the scope of what is written to the log by setting the -nologcomponent option. The -nologcomponent option can be applied to selected data stores or all data stores.

For example, to prevent messages and errors related to replication for all data stores from being written to the log, enter:

ttDaemonLog -nologcomponent replication

To prevent messages and errors related to replication for the masterdsn data store from being written to the log, enter:

ttDaemonLog -nologcomponent replication masterdsn

If, you want to prevent both replication and IMDB Cache errors and messages from being written, enter:

ttDaemonLog -nologcomponent replication
ttDaemonLog -nologcomponent oracleconnect

If, after setting a -nologcomponent option, you want to re-enable writing errors for a component, you can use the -logcomponent option. For example, if after preventing both replication and IMDB Cache errors from being logged, as shown in the example above, you want to re-enable logging of replication errors, enter:

ttDaemonLog -logcomponent replication

To re-enable logging for all TimesTen components, you can use the -logreset option:

ttDaemonLog -logreset

To display all of the output from the TimesTen daemon and server on your local machine, use:

ttDaemonLog

To display the log output from the host machine named, backup1, use:

ttDaemonLog -n backup1

To write the log output to the file C:\TimesTen\logout\log1, use:

ttDaemonLog -file C:\TimesTen\logout\log1

The TimesTen Server generates a message each time an application connects to or disconnects from a client DSN if these messages were specified to be generated during installation. To display just the server log messages, use:

ttDaemonLog -show server

To display just the replication agent messages, use:

ttDaemonLog -show replication

To display just the cache agent messages, use:

ttDaemonLog -show ora

To display all messages from the TimesTen processes, use:

ttDaemonLog -show all

To restore logging to its default "verbose" level, use the -setverbose option:

ttDaemonLog -setverbose

Notes

While primarily intended for use by TimesTen customer support, this information may be useful to system administrators and developers.

This utility is supported only where the TimesTen Data Manager is installed.

To permanently set or disable verbose logging, you must change the options in the ttendaemon.options file. See "Modifying informational messages" in the "Working with the Oracle TimesTen Data Manager Daemon" chapter of Oracle TimesTen In-Memory Database Operations Guide.

---

ttDaemonLog for UNIX

Description

On UNIX, ttDaemonLog fetches all TimesTen events from the file generated by syslogd(1). It displays all events to stdout.

The TimesTen daemon (timestend) records its event log via syslog(2). The eventual disposition of the log information depends on the configuration of your /etc/syslog.conf file, which you can customize to log or ignore messages selectively. Messages can be logged into various files depending on the configuration of the file. These files can grow to be quite large. You should prune them periodically to conserve disk space.

Syntax

ttDaemonLog {-h | -help | -?}
ttDaemonLog {-V | -version}
ttDaemonLog [-show type] [-b | -r | -s] [-f] [-integer] [-file filename] [-facility name] [-loglevel level [DSN | [-connstr] connStr]] [-[no]logcomponent component [DSN | [-connstr] connStr]] [-logreset] [-msg string] [-setquiet | -setverbose]

Options

ttDaemonLog has the options:

Examples

With the exception of the example with the -n option, all of the examples shown under "ttDaemonLog for Windows" also apply to the UNIX version of ttDaemonLog. The following examples, show the use of some of the UNIX-specific options.

To write the log output to the file /var/adm/syslog/syslog.log, use:

ttDaemonLog -file /var/adm/syslog/syslog.log

To direct logging to the local7 facility, use.

ttDaemonLog -facility local7

Notes

While primarily intended for use by TimesTen customer support, this information may be useful to system administrators and developers.

This utility is supported only where the TimesTen Data Manager is installed.

To permanently set or disable verbose logging, you must change the options in the ttendaemon.options file. See "Modifying informational messages" in the "Working with the Oracle TimesTen Data Manager Daemon" chapter of Oracle TimesTen In-Memory Database Operations Guide.

For information about configuring syslog, See "Modifying informational messages" in the "Working with the Oracle TimesTen Data Manager Daemon" chapter of Oracle TimesTen In-Memory Database Operations Guide.