ora-12169 tns net service name given as connect identifier is too long
啟用監聽器動態註冊後,根據$ORACLE_HOME/network/admin/samples目錄,有tnsnames.ora配置示例,執行:
sqlplus as sysdba報如題錯誤
檢視此檔案的相關說明及使用後,修正如下:
-bash-3.2$ pwd
/oracle/product/10.2.0/db_1/network/admin
-bash-3.2$ more tnsnames.ora
# This file contains the syntax information for
# the entries to be put in any tnsnames.ora file
# The entries in this file are need based.
# There are no defaults for entries in this file
# that Sqlnet/Net3 use that need to be overridden
#
# Typically you could have two tnsnames.ora files
# in the system, one that is set for the entire system
# and is called the system tnsnames.ora file, and a
# second file that is used by each user locally so that
# he can override the definitions dictated by the system
# tnsnames.ora file.
/oracle/product/10.2.0/db_1/network/admin
-bash-3.2$ more tnsnames.ora
# This file contains the syntax information for
# the entries to be put in any tnsnames.ora file
# The entries in this file are need based.
# There are no defaults for entries in this file
# that Sqlnet/Net3 use that need to be overridden
#
# Typically you could have two tnsnames.ora files
# in the system, one that is set for the entire system
# and is called the system tnsnames.ora file, and a
# second file that is used by each user locally so that
# he can override the definitions dictated by the system
# tnsnames.ora file.
# The entries in tnsnames.ora are an alternative to using
# the names server with the onames adapter.
# They are a collection of aliases for the addresses that
# the listener(s) is(are) listening for a database or
# several databases.
# the names server with the onames adapter.
# They are a collection of aliases for the addresses that
# the listener(s) is(are) listening for a database or
# several databases.
# The following is the general syntax for any entry in
# a tnsnames.ora file. There could be several such entries
# tailored to the user's needs.
# a tnsnames.ora file. There could be several such entries
# tailored to the user's needs.
orcl= #如果有多個description,這兒本身有個description_list節,因為我們只 邊一個主機上面的資料庫,所有不用 description_list
# one or more descriptions
# If there is just one description, unnecessary ]
(DESCRIPTION=
# Can take values between 512 and 32K
# one or more addresses
# If there is just one address, unnecessary ]
# one or more descriptions
# If there is just one description, unnecessary ]
(DESCRIPTION=
# Can take values between 512 and 32K
# one or more addresses
# If there is just one address, unnecessary ]
#同上,本身也有一個address list節,如有多個address的話
(ADDRESS=
(PROTOCOL=tcp)
(HOST=192.168.19.155)
(PORT=1521)
)
(ADDRESS=
(PROTOCOL=tcp)
(HOST=192.168.19.155)
(PORT=1521)
)
#連線到哪個資料庫(sid及global_name)
(CONNECT_DATA=
(SID=orcl)
(GLOBAL_NAME=orcl)
)
)
-bash-3.2$
(SID=orcl)
(GLOBAL_NAME=orcl)
)
)
-bash-3.2$
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/9240380/viewspace-665509/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【DataGuard】 TNS:could not resolve the connect identifier specifiedIDE
- File name too long window和linux排查,解決Linux
- Oracle案例05——ORA-12162: TNS:net service name is incorrectly specifiedOracle
- 【故障處理】ORA-12162: TNS:net service name is incorrectly specified
- 表結構遷移檔案Identifier name 'xxxxxx' is too long解決IDE
- ORA-12154: TNS:could not resolve service name / TNS-03505: Failed to resolve nameAI
- ORA-12154: TNS:could not resolve the connect identifier specifiedIDE
- ORA-12154: TNS: could not resolve the connect identifier specifiedIDE
- oracle 11g登陸報錯'ORA-12162: TNS:net service name is incorrectly specified'Oracle
- hpux上的定時任務報:ORA-12162: TNS:net service name is incorrectly specifiedUX
- 關於hibernate的 No row with the given identifier existsIDE
- Oracle案例09——ORA-12154: TNS:could not resolve the connect identifier specifiedOracleIDE
- Oracle 10g ORA-12154: TNS: could not resolve the connect identifier specifiedOracle 10gIDE
- RMAN 6217 not connected to auxiliary database with a net service nameUXDatabase
- 關於ORA-12154: TNS:could not resolve the connect identifier specified的問題IDE
- 徹底理解初始化引數SERVICE_NAMES和客戶端TNS中SERVICE_NAME(2)客戶端
- 徹底理解初始化引數SERVICE_NAMES和客戶端TNS中SERVICE_NAME(1)客戶端
- EF:Oracle.DataAccess.Client.OracleException: ORA-12154: TNS:could not resolve the connect identifier specifiedOracleclientExceptionIDE
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!AIENQ
- (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=download))JDBC
- ORA-12514:TNS:listener does not currently know of service requested in connect descriptor
- PLS-00172: string literal too long
- 0403-027 The parameter list is too long for AIXAI
- Laravel 5.4 常見錯誤:Specified key was too longLaravel
- 故障排除:"WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! "AIENQ
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!的分析AIENQ
- DB_NAME&TANCE_NAME&DB_UNIQUE_NAME&ORACLE_SID&GLOBAL_NAME&DB_DOMAIN&SERVICE_NAMEOracleAI
- ORA-01555: snapshot too old: rollback segment number with name "" too small
- Oracle SID VS Service NameOracle
- Oracle SID & SERVICE_NAMEOracle
- 一次WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCKAIENQ
- MySQL:Specified key was too long; max key length is 767 bytesMySql
- 【故障處理】-0403-027 The parameter list is too long
- ORA-01704: string literal too long 與CLOB
- Error running ‘Application’Command line is too longErrorAPP
- db_name,db_domain, global_name, service_name的區別AI
- 【Oracle】service_name和service_names的關係Oracle
- Laravel 5.5 資料遷移問題:Specified key was too longLaravel