Versions Compared

Old Version 3

changes.mady.by.user Cyril Wüthrich

Saved on

compared with

New Version Current

changes.mady.by.user Virginie BANNIER

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Informations

Page Properties


Public cible

Status
colourGreen
titleutilisateur



Explication

Le problème est dû à une rupture (même minime) de la connexion réseau (filaire ou Wifi).

Cela arrive en cas de microcoupures sur le réseau ou alors suite à un changement de carte réseau, par exemple lors d'un passage d'un réseau câblé à Wifi en cas de déconnexion d'une station d'accueil d'un laptop. Au fil du temps, ProConcept a rencontré plusieurs erreurs Oracle pour de multiples raisons.

Il n'est pas possible de fournir une solution clé en main, mais par contre cet article à pour but de donner des astuces pour résoudre les erreurs Oracles les plus rependues.

Dans tous les cas, une recherche du code d'erreur sur internet permet de comprendre ce qui cause l'erreur. De plus, des outils tels que Chat GPT sont capables de proposer des alternatives pour contourner certaines erreurs.



Ui expand
titleORA-01403

no data found

Cause

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.

Action

Terminate processing of the data.



Ui expand
titleORA-01427
single-row subquery returns more than one row

Cause

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.

Action

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


Ui expand
titleORA-01476

divisor is equal to zero

Cause

An expression attempted to divide by zero.

Action

Correct the expression, then retry the operation.

Chat GPT

Ce type d'erreur peut être corrigé par des outils tels que Chat GPT.

Image Added


Ui expand
titleORA-03114
not connected to ORACLE

Cause

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.

Action

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.


Ui expand
titleORA-03135
connection lost contact

Cause

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

Action

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


Ui expand
titleORA-12170
Cannot connect. timeout_type timeout of timeout for host_port. (CONNECTION_ID=connection_id)
  • timeout_type: The timeout type (i.e. TCP, OUTBOUND_CONNECT, RECEIVE).
  • timeout: The timeout value.
  • host_port: The host and port that could not be connected to.
  • connection_id: The connection ID.

Cause

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.

Action

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.


Ui expand
titleORA-20740
Numsubordinates assertion failure.

Cause

The database is not coherent. There is a child entry that is unknown to the parent entry and the numsubordinates attribute is absent in the parent entry.

Action

Rebuild the database, using db2ldif, then ldif2db.