List of Log Entries

Event ID	Message	Description
1	Unable to open TTServer key from registry	Windows platform only. TimesTen server could not open HKEY_LOCAL_MACHINE\SOFTWARE\ TimesTen\TimesTen221\TTServer key from registry. Your TimesTen installation may be corrupted. Contact customer support for assistance.
2	TimesTen Server is stopping	This message is informational only.
3	Socket send() failed. Error_message	This message is caused by the failure of the system call send. Consult your system documentation to determine the cause of this error.
4	Server is exiting. Unable to create server context object (CSrvCtx)	An internal error occurred.Make a note of any information necessary to reproduce the error and then contact customer support for assistance.
5	Socket recv() failed. Error_message	This message is caused by the failure of the system call recv. Consult your system documentation to determine the cause of this error.
6	Disconnecting client: Client_host_name (domain_name); IP Address: client_IP; Client PID: client_PID; DSN: server_DSN; UID: client_UID; Total connect time: ddd hh:mi:ss; Total execution time: ddd hh:mi:ss	This message is informational only. Could be used to match the connects and disconnects by a TimesTen client application to/from a TimesTen server.
7	Unable to open the ODBC.INI data sources root	Windows platform only. The TimesTen server could not open HKEY_LOCAL_MACHINE\SOFTWARE \ODBC\ODBC.INI\ODBC Data Sources key from registry. Contact customer support for assistance.
8	Unable to read (numeric) port number from registry; using default port	Windows platform only. The TimesTen server could not read HKEY_LOCAL_MACHINE\SOFTWARE \TimesTen\TimesTen221\Servers\logical_server\TCP_Port from registry. Ensure that you did not modify registry entries manually.
9	Server is exiting. Could not cd to path. OS reports error(error_number): error_message	This message is caused by the failure of the system call chdir. Ensure that you have installed TimesTen properly and the directory exists. Consult your system documentation to determine the cause of this error.
10	Server is exiting. Could not connect to TimesTen daemon. Check to make sure that the TimesTen daemon/service is running	The TimesTen server communicates with TimesTen Data Manager daemon. Ensure that TimesTen Data Manager daemon/service is running.
11	Main Server cleaned up all child processes and exiting.	ServerProc thread of the TimesTen server accepts all connection requests from a TimesTen client. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error.
12	Server is exiting. Failed to create shared memory segment for IPC. Error_message	This message is caused by the failure to create a shared memory segment for IPC. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.
13	Server is exiting. Failed to attach to shared memory segment for IPC. Error_message	This message is caused by the failure to attach to a shared memory segment for IPC. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.
14	Server is exiting. Failed to create semaphore for IPC. Error_message	This message is caused by the failure of a semaphore creation. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only when the TimesTen server is configured to allow shared memory segment as IPC.
15	Client application terminated. Terminating corresponding TimesTen child server process	This message implies that the TimesTen server has lost a TCP/IP socket connection to the TimesTen client ODBC driver (and hence the application) before the application closed the ODBC connection properly. This can happen only if the client application (or the thread that had the ODBC connection) exited without closing the ODBC connection. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.
16	Connect succeeded from client: client_host_name(client_domain_name); IP Address: client_IP; Client PID: client_PID; DSN: server_DSN; UID: client_UID	This message is informational only. Could be used to match the connects and disconnects by a TimesTen client application to/from a TimesTen server.
17	Connect failed for client: client_host_name(client_domain_name); IP Address: client_IP; Client PID: client_PID; DSN: server_DSN; UID: client_UID; SQL State: SQL_state; Error: error_message	This error is generated if SQLDriverConnect fails. The runtime error returned by the driver may indicate the cause of the error. The corrective action depends on the runtime error. For details, refer to the Microsoft ODBC API Reference at https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/odbc-api-reference.
18	Server is exiting. Failed to create REQUEST semaphore for IPC. Error_message	TimesTen uses a pair of semaphores called REQUEST and RESPONSE to implement shared memory segment as IPC. This message is caused by the failure of a REQUEST semaphore creation. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only when the TimesTen server is configured to allow shared memory segment as IPC.
19	Server is exiting. Failed to create RESPONSE semaphore for IPC. Error_message	TimesTen uses a pair of semaphores called REQUEST and RESPONSE to implement shared memory segment as IPC. This message is caused by the failure of a RESPONSE semaphore creation. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only when the TimesTen server is configured to allow shared memory segment as IPC.
20	Shared memory segment for IPC exhausted the configured maximum. File: source_file_name; line: line_number; size: requested_size	There is not enough space left in the configured shared memory segment for IPC. Please refer to Managing the Size of the Shared Memory Segment in Oracle TimesTen In-Memory Database Operations Guide to configure this properly. This message generated only for a connection that uses a shared memory segment as the IPC mechanism.
21	Server is exiting. Failed to open shared memory segment for IPC. Error_message	This message is caused by the failure to create a shared memory segment for IPC. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.
25	Server is exiting. Socket initialization failed. Error_message	Windows platforms only. Call to WSAStartup failed. Consult your system documentation to determine the cause of this error.
26	Server is exiting. gethostname() failed. Error_message	On Linux or UNIX platforms the uname call failed.
27	Server is exiting. ttSetSockOptBool() failed. Error_message	Failed to set a socket option of boolean type. Contact customer support for assistance.
32	Server is exiting. socket() failed. Error_message	This message is caused by the failure of the system call socket. Consult your system documentation to determine the cause of this error.
33	Server is exiting. gethostbyname() failed. Error_message	This message is sent if the system call gethostbyname fails. Consult your system documentation to determine the cause of this error.
34	Server is exiting. bind() failed. Error_message	This message is caused by the failure of the system call bind. Consult your system documentation to determine the cause of this error.
35	Server is exiting. listen() failed. Error_message	This message is caused by a failure of the system call listen. Consult your system documentation to determine the cause of this error.
36	Successful TimesTen Server startup. Version: server_version_number; Host: server_host_name (server_domain_name); IP Address: server_IP; port: port_number, max connections: max_connections_allowed	This message is informational only.
37	Client protocol version client_version is not supported by this server, which uses version server_version. Attempting to renegotiate protocol level.	There is a version mismatch between the TimesTen client and TimesTen server.
40	Server is exiting. Error_message. A TimesTen Server is already active on this port	An attempt was made to start the TimesTen server on a system where the same release of the TimesTen server is already running with the same port number. Each version of the TimesTen server of the same release must have a unique port number.
50	Socket accept() failed. Error_message	This message is caused by the failure of the system call accept. Consult your system documentation to determine the cause of this error.
57	Error creating a mutex to communicate with separate server process. Error_message	The communication setup between the main and child servers could not be set up properly. Contact customer support for assistance.
58	Error creating or mapping mapped file to communicate with separate server process. Error_message	The event logged just prior to this one has further details, if any.
59	Error creating separate server process. Error_message	Operating system error. Make a note of the system error number and then contact your system administrator.
60	Error creating waitpid thread. Error_message	Operating system error. Make a note of the system error number and then contact your system administrator.
61	Internal error in TimesTen Server. File: source_file_name; line: line_number	Contact customer support for assistance.
62	Connection refused. Server is processing a configured maximum of number connections	This message means that the maximum number of clients are currently connected. See System Limits and Defaults in Oracle TimesTen In-Memory Database Reference.
67	Failed to allocate memory. File: source_file_name; line: line_number; size: failed_malloc_size	Note that sometimes the size is logged as zero if for some reason the TimesTen server cannot determine it at the time of logging.
68	Failed to read request from client. Closing connection without reply.	The server connection to a client application failed. Common causes are: - The client application exited without invoking the SQLDisconnect function. - The waiting time specified in the TTC_Timeout attribute for the client application was exceeded. See Management of TimesTen Database Connections in Oracle TimesTen In-Memory Database C Developer's Guide and TTC_Timeout in Oracle TimesTen In-Memory Database Reference.
69	Child server died due to SEGV signal error_message	A SQL request caused a thread stack overflow. Try increasing the value for the ServerStackSize attribute. See ServerStackSize in Oracle TimesTen In-Memory Database Reference.
70	Invalid value specified_value for attribute: should be in range min_value to max_value. Using used_value	The specified value for the specified attribute is invalid. The message identifies the valid range for the specified attribute value.
71	Connect received from client: client_host_name (client_domain_name); IP address: client_IP; Client PID: client_PID; DSN: server_DSN; UID: client_UID	This message is informational only.
99	Log_message	Certain informational/error messages are logged with this event id.