Oracle 監聽器日誌解析(續)
/////////////////////////////////////////////////////
監聽start後監聽日誌記錄資訊如下:
Tue Feb 06 13:03:06 2018
System parameter file is /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/wang/listener/alert/log.xml
Trace information written to /u01/app/oracle/diag/tnslsnr/wang/listener/trace/ora_5682_140618561201984.trc
Trace level is currently 0
Started with pid=5682
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=wang)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
WARNING: Subscription for node down event still pending
06-FEB-2018 13:03:06 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=wang)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647552)) * status * 0
Tue Feb 06 13:03:48 2018
06-FEB-2018 13:03:48 * service_register * DBdb * 0
Tue Feb 06 13:04:36 2018
06-FEB-2018 13:04:36 * service_update * DBdb * 0
Tue Feb 06 13:05:45 2018
06-FEB-2018 13:05:45 * service_update * DBdb * 0
Tue Feb 06 13:06:15 2018
06-FEB-2018 13:06:15 * service_update * DBdb * 0
Tue Feb 06 13:13:13 2018
06-FEB-2018 13:13:13 * service_update * DBdb * 0
Tue Feb 06 13:19:48 2018
WARNING: Subscription for node down event still pending
06-FEB-2018 13:19:48 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=wang)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647552)) * status * 0
Tue Feb 06 13:23:13 2018
06-FEB-2018 13:23:13 * service_update * DBdb * 0
//////////////////////////////////////////////////////////
透過plsql建立連線:如下是日誌資訊:
Tue Feb 06 13:23:41 2018
06-FEB-2018 13:23:41 * (CONNECT_DATA=(SERVICE_NAME=DBdb)(CID=(PROGRAM=E:\????\PLSQL_Developer8.0??????\plsqldev.exe)(HOST=SC-201707102126)(USER=Administrator))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.1)(PORT=53088)) * establish * DBdb * 0
06-FEB-2018 13:23:41 * (CONNECT_DATA=(SERVICE_NAME=DBdb)(CID=(PROGRAM=E:\????\PLSQL_Developer8.0??????\plsqldev.exe)(HOST=SC-201707102126)(USER=Administrator))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.1)(PORT=53089)) * establish * DBdb * 0
06-FEB-2018 13:23:43 * service_update * DBdb * 0
06-FEB-2018 13:23:46 * service_update * DBdb * 0
///////////////////////////////////////////////////
客戶端tns資訊
DBDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.12)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = DBdb)
)
)
監聽start後監聽日誌記錄資訊如下:
Tue Feb 06 13:03:06 2018
System parameter file is /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/wang/listener/alert/log.xml
Trace information written to /u01/app/oracle/diag/tnslsnr/wang/listener/trace/ora_5682_140618561201984.trc
Trace level is currently 0
Started with pid=5682
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=wang)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
WARNING: Subscription for node down event still pending
06-FEB-2018 13:03:06 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=wang)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647552)) * status * 0
Tue Feb 06 13:03:48 2018
06-FEB-2018 13:03:48 * service_register * DBdb * 0
Tue Feb 06 13:04:36 2018
06-FEB-2018 13:04:36 * service_update * DBdb * 0
Tue Feb 06 13:05:45 2018
06-FEB-2018 13:05:45 * service_update * DBdb * 0
Tue Feb 06 13:06:15 2018
06-FEB-2018 13:06:15 * service_update * DBdb * 0
Tue Feb 06 13:13:13 2018
06-FEB-2018 13:13:13 * service_update * DBdb * 0
Tue Feb 06 13:19:48 2018
WARNING: Subscription for node down event still pending
06-FEB-2018 13:19:48 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=wang)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647552)) * status * 0
Tue Feb 06 13:23:13 2018
06-FEB-2018 13:23:13 * service_update * DBdb * 0
//////////////////////////////////////////////////////////
透過plsql建立連線:如下是日誌資訊:
Tue Feb 06 13:23:41 2018
06-FEB-2018 13:23:41 * (CONNECT_DATA=(SERVICE_NAME=DBdb)(CID=(PROGRAM=E:\????\PLSQL_Developer8.0??????\plsqldev.exe)(HOST=SC-201707102126)(USER=Administrator))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.1)(PORT=53088)) * establish * DBdb * 0
06-FEB-2018 13:23:41 * (CONNECT_DATA=(SERVICE_NAME=DBdb)(CID=(PROGRAM=E:\????\PLSQL_Developer8.0??????\plsqldev.exe)(HOST=SC-201707102126)(USER=Administrator))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.1)(PORT=53089)) * establish * DBdb * 0
06-FEB-2018 13:23:43 * service_update * DBdb * 0
06-FEB-2018 13:23:46 * service_update * DBdb * 0
///////////////////////////////////////////////////
客戶端tns資訊
DBDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.12)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = DBdb)
)
)
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/31397003/viewspace-2151393/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle 監聽器日誌解析Oracle
- Oracle 監聽器日誌配置與管理Oracle
- oracle清理監聽日誌Oracle
- Oracle之外部表監聽日誌Oracle
- ORACLE停止監聽日誌檔案Oracle
- oracle監聽器日誌過大-處理辦法Oracle
- Oracle監聽日誌2g-監聽啟動報錯Oracle
- 管理監聽器日誌listener.log
- Oracle 11g 檢視監聽日誌Oracle
- rac scan listener log 清理監聽日誌 oracleOracle
- 如何更改監聽器日誌檔名稱
- 刪除oracle 11g的警告日誌和監聽日誌Oracle
- Oracle之備份和清理監聽日誌、告警日誌指令碼Oracle指令碼
- 【LISTENER】禁止產生監聽器日誌的方法
- 關閉監聽的日誌。
- Oracle 跟蹤/告警/監聽日誌的清理指令碼Oracle指令碼
- Oracle監聽日誌過大導致的問題Oracle
- oracle 監聽日誌停止寫入的解決方法Oracle
- 監聽日誌檔案的管理
- online清理oracle 監聽日誌推薦的做法Oracle
- oracle 監聽器配置Oracle
- 使用外部表訪問監聽日誌
- 定時清理監聽日誌的指令碼 。指令碼
- 清理資料庫監聽日誌最好方法資料庫
- oracle 監聽器學習Oracle
- 【聽海日誌】之SCN與OracleOracle
- 11G Oracle 關閉監聽XML日誌產生的方法OracleXML
- oracle 資料庫lsnrctl監聽的日誌路徑和trace檔案Oracle資料庫
- 監聽MySQL的binlog日誌工具分析:CanalMySql
- 如何線上操作監聽日誌listener.log
- Flume監聽Nginx日誌流向HDFS安裝配置Nginx
- 監聽器日誌檔案(listener.log)到底記錄了些啥
- 【聽海日誌】之Oracle SQL*LOADEROracleSQL
- 【聽海日誌】之ORACLE恢復案例Oracle
- 說說Oracle監聽器(一)Oracle
- 說說Oracle監聽器(二)Oracle
- oracle例項和監聽器Oracle
- ORACLE RAC 日誌結構解析Oracle