1
|
Unable to open TTServer
key from registry
|
Windows platform only. TimesTen Server could not open HKEY_LOCAL_MACHINE\SOFTWARE\ TimesTen\TimesTen1122\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> (<fully
qualified domain name>);
IP Address: <IP address of
the client machine>;
Client PID: <process ID of
the client driver>; DSN:
<Server DSN>; UID: <Login
ID sent by client>; Total
connect time: <ddd
hh:mm:ss>; Total execution
time: <ddd hh:nmm:ss>
|
This message is informational only. Could be used to match the connects and disconnects by TimesTen Client application to/from a TimesTen Server. |
7
|
Unable to open the
ODBC.INI data sources
root
|
Windows platform only. 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. TimesTen Server could not read HKEY_LOCAL_MACHINE\SOFTWARE \TimesTen\TimesTen1122\Servers\logical_server\TCP_Port from registry. Make sure that you did not modify registry entries manually. |
9
|
Server is exiting. Could
not cd to <path>. OS
reports error(<error
code>): <error message>
|
This message is caused by the failure of the system call chdir. Make sure 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
|
TimesTen Server communicates with TimesTen Data Manager daemon. Make sure that TimesTen Data Manager daemon/service is running. |
11
|
Main Server cleaned up
all child processes and
exiting.
|
ServerProc thread of TimesTen Server accepts all connection requests from 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 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 succeded from
client: <client host name>
(<fully qualified domain
name>); IP Address: <IP
address of the client
machine>; Client PID:
<process ID of the client
driver>; DSN: <Server
DSN>; UID: <Login ID sent
by client>
|
This message is informational only. Could be used to match the Connects and Disconnects by TimesTen Client application to/from a TimesTen Server. |
17
|
Connect failed for
client: <client host name>
(<fully qualified domain
name>); IP Address: <IP
address of the client
machine>; Client PID:
<process ID of the client
driver>; DSN: <Server
DSN>; UID: <Login ID sent
by client>; SQL State:
<SQL state>; Error:
<error message from
Timesten Data Manager
driver>
|
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 Programmer's Reference and SDK Guide that is included with the ODBC SDK. |
18
|
Server is exiting. Failed
to create REQUEST
semaphore for IPC. Error
Code = <OS error code>
|
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 TimesTen Server is configured to allow shared memory segment as IPC. |
19
|
Server is exiting. Failed
to create RESPONSE
semaphore for IPC. Error
Code = <OS error code>
|
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 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 the 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 IPS
|
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 Code: <OS error code>
|
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 UNIX platforms the uname call failed. |
27
|
Server is exiting.
ttSetSockOptBool() failed.
Error Code: <OS error code>
|
Failed to set a socket option of boolean type. Contact customer support for assistance. |
32
|
Server is exiting.
socket() failed. Error
Code: <OS error code>
|
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 Code: <OS error code>
|
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 Code:
<OSerror code>
|
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
Code: <OS error code>
|
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's Version number>;
Host: <server host name>
(<fully qualified domain
name>); IP Address: <IP
address of the server
machine>; port: <port
number>, max connections:
<max connections allowed
to the server>
|
This message is informational only. |
37
|
Client version <client
message protocol version
number> is not supported,
the current server version
is <server message
protocol version number >.
Contact TimesTen support
for instructions on how to
download new versions of
TimesTen Client/Server.
|
There is a version mismatch between the TimesTen Client and TimesTen Server |
40
|
Server is exiting. Error
Code: <OS error code>. A
TimesTen Server is already
active on this port.
|
An attempt was made to start the TimesTen Server on a machine where the same release of 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
|
accept() failed. Error
Code: <OS error code>
|
This message is caused by the failure of the system call accept. Consult your system documentation to determine the cause of this error. |
58
|
Error creating or mapping
mapped file to communicate
with separate server
process. Error Code: <OS
error code>
|
The event logged just prior to this one has further details, if any. |
59
|
Error creating separate
server process. Error
Code: <OS error code>
|
Operating system error. Make a note of the system error number and then contact your system administrator. |
60
|
Error creating waitpid
thread. Error Code: <OS
error code>
|
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> Error Code:
<OS error code>
|
Contact customer support for assistance. |
62
|
Connection refused.
Server is processing a
configured maximum of
<number> connections
|
The TimesTen Server can handle a maximum of 9999 concurrent client connections. This message means that the maximum number of clients are currently connected. |
67
|
Failed to allocate
memory. File: <source_
file_name; line: <source_
line_number>; size: <size
of malloc that failed>
|
Note that sometimes the size is logged as zero if for some reason TimesTen Server cannot determine it at the time of logging. |
99
|
<Log Message>
|
Certain informational/error messages are logged with this event id. |
