The following articles mainly introduce several faster methods to diagnose common Oracle problems. The following describes the specific solution of Oracle troubleshooting methods, I hope it will be helpful for your future study. The following is a detailed description of the article. I hope you can learn from it.
1 TNS-12154 Error or ORA-12154
Feature: SQL * NET does not find a connection string or Alias
Cause) The TNSNAMES. ORA file is not found. The default path of this file is:
- Windows 95/98 client
- SQL*Net 2.x - ORAWIN95NETWORKADMIN
- Net8 - ORAWIN95NET80admin
- Net8i - OracleORA81NETWORKADMIN
- Windows NT client
- SQL*Net 2.x - ORANTNETWORKADMIN
- Net8 - ORANTNET80ADMIN
- Net8i - OracleORA81NETWORKADMIN
- UNIX Client
- $Oracle_HOME/NETWORK/ADMIN
- or /etc
- or /var/opt/Oracle
Set TNS_ADMIN on the client
Set TNS_ADMIN. TNS_ADMIN to point to the location of the TNSNAMES. ORA file in the Registry HKEY_LOCAL_MACHINESoftwareOracle.
Measure: Check the file location according to the preceding instructions.
Cause 2: 2) the cause of common Oracle problems is that the content format in the TNSNAMES. ORA file is incorrect.
Measure: Check the file format. The standard format is as follows:
- DEV1.WORLD =
- (DESCRIPTION = (ADDRESS_LIST =
- (ADDRESS = (PROTOCOL = TCP) (Host = 145.45.78.56) (Port = 1521) ) )
- (CONNECT_DATA = (SID = ORCL) ) )
Cause 3: (3) TNSNAMES. ORA is inconsistent with SQLNET. ORA
Measure: The SQLNET. ORA format is as follows:
- TRACE_LEVEL_CLIENT = OFF
- SQLNET.AUTHENTICATION_SERVICES = (NONE)
- NAMES.DIRECTORY_PATH = (TNSNAMES)
- AUTOMATIC_IPC = OFF
Because there is no NAMES. DEFAULT_DOMAIN = world, the DEV1.WORLD connection string cannot be connected. You can add
- DEV1 =
- (DESCRIPTION = (ADDRESS_LIST =
- (ADDRESS = (PROTOCOL = TCP) (Host = 145.45.78.56) (Port = 1521) ) )
- (CONNECT_DATA = (SID = ORCL) ) )
In this case, you can connect.
2 NL-00462 Error or ORA-00462
Feature: The Listener cannot be started.
Cause: the content of the LISTENER. ORA file is incorrect, such as mismatched brackets, incorrect parameter names, and redundant spaces.
Measure: re-edit the file.
3 NL-00405 Error or ORA-00405
Feature: The LISTENER. ORA file is not readable or cannot be found.
Cause: the content of the LISTENER. ORA file is incorrect, such as mismatched brackets, incorrect parameter names, and redundant spaces.
Measure: Make sure that the file location is $ Oracle_HOME/network/admin in the default directory, or set the environment variable TNS_ADMIN to point to the location of the file.
4 TNS-01155 Error or ORA-01155
Feature: The SID_LIST_LISTENER variable value in the LISTENER. ORA file is incorrect.
Cause: the content of the LISTENER. ORA file is incorrect. The value of SID_LIST_LISTENER variable is incorrect.
Measure: Make sure that the values in the file are correct. There is a sample file in the $ Oracle_HOME/network/admin/samples Directory for your reference.
5 TNS-12537, TNS-12560, TNS-00507 Error
Feature: An invalid protocol adapter is referenced in the LISTENER. ORA file.
Cause: the value of the PROCOTOL variable in the LISTENER. ORA file is incorrect.
Measure: Make sure that the values in the file are correct. Generally, the TCP protocol is used. The sample file is in the $ Oracle_HOME/network/admin/samples Directory for your reference. Use adapters tnslsnr to check protocol programs
6 TNS-12203 Error
Feature: cannot be connected to the target
Cause: whether the listener is started; whether the alias is configured
Measure: Check whether the listener is started, such as lsnrctl status; check the alias configuration of TNSNAMES. ORA.
7 TNS-12533 Error
Feature: cannot be connected to the target
Cause: Invalid address parameter,
Measure: Check the ADDRESS parameter of TNSNAMES. ORA. The above content is an introduction to the Oracle FAQ diagnosis method. I hope you can gain some benefits.