Oracle Application Server 10.1.3.4, Руководство пользователя

Страница: 92 / 170

Resolving Communication Errors
7-6 Oracle Application Server Adapters for IMS/DB User's Guide
Resolving Communication Errors
When Oracle Studio disconnects from the IBM z/OS computer, the computer is
displayed in Oracle Studio with an X in a red circle. If this situation occurs, try to
access the computer later.
The following table describes the various scenarios that may exist when Oracle
Application Server disconnects from the IBM z/OS computer.
To troubleshoot client/server communication problems, you need to be familiar with
the following:
■
Daemon configuration settings
■
Oracle Connect security
■
TCP/IP subsystem. Oracle Application Server Adapter for IMS/DB uses TPC/IP
for internal intercomputer communications.
■
System details, such as the account name and password of the administrator
account, the IP address of the computers involved and whether a portmapper is
being used.
Resolving Specific Errors
The following error messages relate to errors received from Oracle Connect.
C007: Server initialization failed.
Cause: The daemon failed to start its network service.
Action: Check the processes being run on the system to see whether another
daemon or program is using the port specified in the oc4j-ra-xml file for the
adapter.
Action: Check the TCP/IP subsystem on the current computer by trying to ping it
or run FTP or Telnet to or from it.
Table 7–4 Scenarios When a Client Is Disconnected
Scenario
Idle (Not Processing a Client
Request)
Processing a Client Request
Explicit Disconnect
(client explicitly
closes connection
or client program
terminates)
The server is immediately notified of
the disconnect and either becomes
available for use by another client or
terminates (if it is not reusable). The server does not know that the client has
disconnected and continues processing. When
processing completes, the server tries to reply to
the client and immediately gets an error that the
connection was lost. The server either becomes
available for use by another client or terminates (if
it is not reusable).
Abrupt Disconnect
(client closed
without proper
shutdown or client
system hanged
and
communication
disconnected)
The server does not know that the
client has disconnected and remains
in the idle state.
After timing out based on whichever
comes first of the value for the client
idle timeout daemon workspace
parameter or the TCP/IP
KEEPALIVE
parameter, the server is notified of the
disconnect and either becomes
available for use by another client or
terminates (if it is not reusable).
The server does not know that the client has
disconnected and continues processing. When
processing completes, the server tries to reply to
the client. After an interval (typically several
minutes, depending on the TCP/IP configuration),
during which the TCP/IP subsystem retries
sending the message to the client, the server
assumes that the client has terminated and notifies
the server that the connection has been closed. The
server either becomes available for use by another
client or terminates (if it is not reusable).