Case:
Microsoft Windows [版本 5.2.3790]
(C) 版權所有 1985-2003 Microsoft Corp.
C:\Documents and Settings\user1>lsnrctl
LSNRCTL for 32-bit Windows: Version 9.2.0.7.0 - Production on 27-8月 -2008 09:33
:43
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
歡迎來到LSNRCTL，請鍵入"help"以獲得信息。
LSNRCTL> status
正在連接到 (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
TNS-12541: TNS：無監聽器
TNS-12560: TNS: 協議適配器錯誤
TNS-00511: 無監聽器
32-bit Windows Error: 2: No such file or directory
正在連接到 (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.55)(PORT=1521)))
TNS-12538: TNS：沒有此協議適配器
TNS-12560: TNS: 協議適配器錯誤
TNS-00508: 無此類協議適配器
LSNRCTL> start
啓動tnslsnr：請稍候...
TNSLSNR for 32-bit Windows: Version 9.2.0.7.0 - Production
系統參數文件爲D:\oracle\ora92\network\admin\listener.ora
寫入D:\oracle\ora92\network\log\listener.log的日誌信息
監聽：(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
監聽該對象時出錯: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.55)(PORT=
1521)))
TNS-12538: TNS：沒有此協議適配器
TNS-12560: TNS: 協議適配器錯誤
TNS-00508: 無此類協議適配器
監聽程序未能啓動。請參閱上面的錯誤消息...
---------------------------
服務
---------------------------
在 本地計算機 無法啓動 OracleOraHome92TNSListener 服務。
錯誤 1067: 進程意外終止。
---------------------------
確定
---------------------------
==============================================================
ORA-12560: TNS: 協議適配器錯誤的解決方法
造成ORA-12560: TNS: 協議適配器錯誤的問題的原因有三個：
1.監聽服務沒有起起來。windows平臺個一如下操作：開始---程序---管理工具---服務，打開服務面板，啓動oraclehome92TNSlistener服務。
2.database instance沒有起起來。windows平臺如下操作：開始---程序---管理工具---服務，打開服務面板，啓動oracleserviceXXXX,XXXX就是你的database SID.
3.註冊表問題。regedit，然後進入HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0將該環境變量ORACLE_SID設置爲XXXX,XXXX就是你的database SID.或者右幾我的電腦，屬性--高級--環境變量---系統變量--新建，變量名=oracle_sid,變量值=XXXX,XXXX就是你的database SID.或者進入sqlplus前，在command line下輸set oracle_sid=XXXX,XXXX就是你的database SID.
經過以上步驟，就可以解決問題。
=======================================
TNS: 協議適配器錯誤的問題的原因有三個：
1.監聽服務沒有起起來。windows平臺個一如下操作：開始---程序---管理工具---服務，打開服務面板，啓動oraclehome92TNSlistener服務。
2.database instance沒有起起來。windows平臺如下操作：開始---程序---管理工具---服務，打開服務面板，啓動oracleserviceXXXX,XXXX就是你的database SID.
3.註冊表問題。regedit，然後進入HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0將該環境變量ORACLE_SID設置爲XXXX,XXXX就是你的database SID.或者右幾我的電腦，屬性--高級--環境變量---系統變量--新建，變量名=oracle_sid,變量值=XXXX,XXXX就是你的database SID.或者進入sqlplus前，在command line下輸set oracle_sid=XXXX,XXXX就是你的database SID.
經過以上步驟，就可以解決問題
1、ORA－12541：TNS：沒有監聽器
原因：沒有啓動監聽器或者監聽器損壞。如果是前者，使用命令net start OracleOraHome81TNSListener（名字可能有出入）即可；如果是後者，則使用“Net8Configuration
Assistant”工具嚮導之“監聽程序配置”增加一個監聽器即可（基本不用寫任何信息，一路OK。在添加之前可能需要把所有的監聽器先刪除！）
2、ORA－12500：TNS：監聽程序無法啓動專用服務器進程或ORA－12560：TNS：協議適配器錯誤
原因：ORACLE的數據庫服務沒有啓動。使用命令net start ORACLESERVICEORADB（ORADB爲數據庫名字）即可。如果仍沒有解決，請繼續向下看。
3、如果數據庫服務啓動失敗，則很有可能是其註冊表項值損壞，最好的做法是以下兩步：
1）ORADIM -DELETE -SID oradb 刪除數據庫服務項
2）ORADIM -NEW -SID oradb 新增數據庫服務項
注：這個過程中如果出錯，就重啓計算機！
4、ORA－12154：TNS：能解析服務名
原因：ORACLE的網絡服務名沒有正確配置。請使用“Net8 Configuration Assistant”工具嚮導之“本地網絡服務名配置”配置TNS即可。如果仍沒有解決，請繼續向下看。
5、ORA－1034 ：TNS：ORACLE不可用
原因：ORACLE的數據庫服務正確啓動，但是數據庫沒有打開！
使用命令：
1）svrmgrl 啓動服務管理器
2）connect internal 以internal身份登陸
3）startup 打開數據庫
6、ORA－12560：TNS：協議適配器錯誤（頑固性的）
原因：未知。
解決：必殺技－－打開“Windows任務管理器”，殺死ORACLE.exe及ORADIM.exe進程，書寫自己的
ora_startup.bat，執行之！
PS：
1、我的ora_startup.bat：
net start OracleOraHome81TNSListener
net start ORACLESERVICEORADB
svrmgrl 一般情況下不用，不過有時少不了它的，具體步驟見第5步。
2、我的ora_shutdown.bat：
net stop OracleOraHome81TNSListener
net stop ORACLESERVICEORADB
ORACLE_HOME=/u01/app/oracle/product/8.1.6
export ORACLE_HOME/ 包括Oracle軟件的目錄 /
LD_LIBRARY_PATH=/u01/app/oracle/product/8.1.6/lib;
export LD_LIBRARY_PATH
ORACLE_BASE=/u01/app/oracle
export ORACLE_BASE/ 包括Oracle軟件的目錄和管理軟件的目錄 /
ORACLE_SID=ORCL
export ORACLE_SID/ 缺省數據庫的標識 /
ORACLE_TERM=vt100
export ORACLE_TERM
ORA_NLS33=/u01/app/oracle/product/8.1.6/
ocommon/nls/admin/data
export ORA_NLS33 / 語言支持 /
PATH=$PATH: /u01/app/oracle/product/8.1.6/bin
export PATH
=============================================
ORA-12560 STARTING LISTENER ON NT - TROUBLESHOOTING
---------------------------------------------------
ORA-12560: TNS Protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors.For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation
is complete.
This is a high level error just reporting an error occurred in the actual transport layer. Look at the next error down the stack and process that.
1.- Starting Listener with TCP/IP Protocol
Problem:
You start the TNS Listener from command line and the TCP/IP address fails with a TNS-12560.
Solution:
Check if Microsoft Winsock Proxy(WSP) Client is enabled on the Windows NT Server, if that is the case then go to windows Control Panel, click WSP icon and select the disable Proxy Client option.
Explanation:
The Winsock application may fail to bind to a specific port on a Proxy Server computer when the Winsock is running Proxy Client.
2.- TNS-12560 TNS-512 Starting the listener.
Problem:
You try to start up the listener and receive the following error stack:
TNS-12542: TNS:address already in use
TNS-12560: TNS Protocol adapter error
TNS-00512: Address already in use
32-bit Windows Error: 48: Unknown error
Error: TNS 512
Text: Address already in use
--------------------------------------------
Cause: Specified listener address is already being used.
Action: Start your listener with an unused address.
Generally this problem may ocurr for a incorrect setting in the listener.ora. Some causes of this problems may be:
a.- Some defined address in the listeners.ora is been used. Make sure other listeners are not running. Either listener.log and screen output appear the address with problem.
b.- Just for 8i: in windows NT the algorithm to acquire
the address has change, please check the Note 69026.1: Oracle 8i and socket LISTEN operations.
Explanation:
The listener will try to acquire the address in exclusive mode, if this is been used then the process to get it will fail.
3.- Starting the listener the errors ORA-12203,ORA-12560, NL-462 or NL-427 may be raised.
Problem:
You try to start up the listener and receive the following errors
ORA-12203,ORA-12560, NL-462 or NL-427.
Solution:
Recreate the listener.ora file.
Explanation:
Some corruption in the listener.ora may get unable to the tnslsnr to work adequatly.
4.- Failed to start service, TNS-12560, TNS-00530 when create new listener services
Problem:
To recreate Oracle TNS listener service on Windows NT, you delete the service entry in registry. When using lsnrctl to start the listener, you get the following errors:
LSNRCTL> start
Starting tnslsnr: please wait...
Failed to start service, error 3.
TNS-00530: Protocol adapter error
The Listener service is not recreated and the Listener would not start.
You are using a valid listener.ora file and protocol adapters.
Solution:
After you delete the Listener service from registry, you have to reboot NT for it to take effect. Then you can use lsnrctl to start the Listener, which would re-create the listener service.
Explanation:
The Listener service is marked 'disabled', but it still exists after you delete the service from registry.
本文轉載自博客