Oracle Application Server 10.1.3.4 User Manual page 150

Workspaces
Table 8–11 (Cont.) General Tab Components
Field
Specific log file
format
Trace options
Query governing
restrictions
Max number of rows
in a table that can be
read
Max number of rows
allowed in a table
before scan is rejected
C-10 Oracle Application Server Adapters for IMS/DB User's Guide
Description
Defines the name and location of the server log file if you
want the data written to a file instead of SYSOUT for the
server process. The parameter must specify the name and
the high level qualifier.
The following tokens can appear in the log file template
and will be replaced accordingly:
%A: workspace name
■
%D: date (yymmdd)
■
%I: instance number of the given workspace server
■
%L: server account's login directory
■
%P: server's process ID
■
%T: time (hhmmss)
■
%U: server's account name (username)
■
Specifies the type of tracing to be performed. The
following tracing options are available:
No timeout: Select this to disable the standard RPC
■
timeouts, setting them to a long duration
(approximately an hour) to facilitate debugging.
Call trace: Selecct this to generate a message in the
■
server log file for each RPC function called. This is
useful for troubleshooting the server.
RPC trace: Select this to enable debugging messages
■
on the server.
Sockets: Select this to generate a message in the
■
server log file for each socket operation. This is useful
for troubleshooting client/server communication -
providing a detailed trace of every client/server
communication.
Extended RPC trace: Select this to generate a verbose
■
message in the server log file for each low-level RPC
function called. This is useful for troubleshooting the
server.
System trace: Select this to generate operating
■
system-specific tracing.
Timing: Select this to generate a timestamp for every
■
entry to the server log file.
Select the maximum number of table rows that are read in
a query. When the number of rows read from a table
exceeds the number stated the query returns an error.
Select the maximum number of table rows that can be
scanned. This parameter has different behavior for query
optimization and execution.
For query optimization, the value set is compared to
■
the table cardinality. If the cardinality is greater than
the value, the scan strategy is ignored as a possible
strategy (unless it is the only available strategy).
For query execution, a scan is limited to the value set.
■
When the number of rows scanned exceeds the
number entered, the query returns an error.