You tried one of the following:

1. You executed a SELECT INTO statement and no rows were returned.
2. You referenced an uninitialized row in a table.
3. You read past the end of file with the UTL_FILE package.

Terminate processing of the data.

The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row.

Use ANY, ALL, IN, or NOT IN to specify which values to compare or reword the query so only one row is retrieved.

The connection between the Client and Server process did not exist. This is likely the result of an earlier ORA-03113 error. The cause may be that the database instance experienced a maintenance or unplanned outage, or that the Server process had a fatal error, or that the network connection was interrupted.

Check the alert log of the database instance to see if a planned or unplanned outage occurred. Check the alert log to see if a process termination (ORA-07445, kill, or ORA-00600) occurred. Check for network problems and review the SQL*Net setup. After the problem is identified and resolved, retry the operation.

1. Server unexpectedly terminated or was forced to terminate.
2. Server timed out the connection.

1. Check if the server session was terminated.
2. Check if the timeout parameters are set properly in sqlnet.ora.

The connection request could not be completed within the allotted time interval. This may be a result of network or system delays, or it may indicate a denial of service attack on the database server.

The message indicates whether there was a transmission control protocol (TCP) connect timeout, an Outbound connect timeout, or a Receive timeout.

• If the error occurred in your application, then:

• Set CONNECT_TIMEOUT or TRANSPORT_CONNECT_TIMEOUT to a larger value if they are used in an Easy Connect or tnsnames.ora connection string. Or, set one or all of the parameters SQLNET.OUTBOUND_CONNECT_TIMEOUT, SQLNET.RECV_TIMEOUT, or TCP.CONNECT_TIMEOUT in the client sqlnet.ora file to a larger value. The connection string parameters have higher precedence than the corresponding sqlnet.ora parameters.

• In languages that support programmatic driver settings, adjust the settings equivalent to the previously mentioned timeouts. For example, with JDBC, adjust oracle.net.OUTBOUND_CONNECT_TIMEOUT, oracle.net.CONNECT_TIMEOUT, or use setLoginTimeout(). With Python python-oracledb, adjust the TcpConnectTimeout parameter when calling connect() or create_pool().

• If the error occurred in the database alert log file, then set one or both of the parameters, SQLNET.INBOUND_CONNECT_TIMEOUT or SQLNET.RECV_TIMEOUT, in the database sqlnet.ora file to a larger value.

• If a malicious client is suspected, then use the database alert log to identify the source address and then restrict access.

• Use the CONNECTION_ID value to track this connection attempt in trace files for further diagnosis.

Rebuild the database, using db2ldif, then ldif2db.