精华内容
下载资源
问答
  • 前几天升级Oracle数据库,从11.2.0.1升级至11.2.0.4,安装完成后,打开PL/SQL,显示ORA-12514,如图: 问题阐述 ORA-12514:监听程序当前无法识别链接描述符中请求的服务,简单的来说就是Oracle数据库的监听器配置有...
  •  在Oracle安装目录中搜索找到listener.ora文件,并修改成txt格式后打开(在修改之前建议做好备份),需要添加的代码及添加位置如下图所示: (SID_DESC =  (GLOBAL_DBNAME = ORCL)  (ORACLE_HOME =E:\Oracle\...
  • Oracle安装好修改配置NET Manager就可以连接了却出现了ORA-12514ORA-28547错误,本文将介绍如何解决
  • ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务 解决方法ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务 解决方法ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务 解决方法ORA-12514 ...
  • 相信各位都遇到过这样一个问题吗,数据库安装好一后过不了几天,就会出现连接不上本地数据库的的事情,而且还会出现报错代码,在这个时候你可能就不知所措了,而对于新手来说就更成问题了,而且无从下手,而解决这个...
  • ora-12514的错误的原因

    2015-02-03 14:39:03
    ora-12514的错误的原因 ,ora-12514的错误的几个最根本的原因 从根源上解决错误
  • ORA-12514错误解决办法

    2014-09-16 10:50:39
    oracle的ORA-12514错误 解决办法
  • ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务
  • 解决ora-12514其中一种情况,很好使的方法哦。
  • Unable to connect to database ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Failed. Warning: You are no longer connected to ORACLE. Please complete the ...

    dgmgrl sys/xxx@prebilla
    dgmgrl sys/xxx@prebillb
    create configuration adg as primary database is prebilla connect identifier is prebilla;
    add database prebillb as CONNECT IDENTIFIER IS prebillb MAINTAINED AS PHYSICAL;

    show CONFIGURATION verbose
    show database verbose prebilla
    show database verbose prebillb
    SWITCHOVER TO prebillb
    ENABLE CONFIGURATION;

    DGMGRL> SWITCHOVER TO prebillb
    Performing switchover NOW, please wait...
    Operation requires a connection to instance "prebill" on database "prebillb"
    Connecting to instance "prebill"...
    Connected.
    New primary database "prebillb" is opening...
    Operation requires startup of instance "prebill" on database "prebilla"
    Starting instance "prebill"...
    Unable to connect to database
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

    Failed.
    Warning: You are no longer connected to ORACLE.

    Please complete the following steps to finish switchover:
            start up instance "prebill" of database "prebilla"

    原因是:StaticConnectIdentifier 的 SERVICE_NAME配置自动变成prebilla_DGMGRL StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prebillb)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=prebilla_DGMGRL)(INSTANCE_NAME=prebill)(SERVER=DEDICATED)))'
    根据监听listener.ora

    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = prebill)
          (ORACLE_HOME = /home/oracle/app/oracle/product/11.2.0/db_1)
          (SID_NAME = prebill)
        )
      )
    LISTENER =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = prebillb)(PORT = 1521))
      )
    ADR_BASE_LISTENER = /home/oracle/app/oracle

    修改成如下即可:
    edit database prebilla set property StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prebilla)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=prebill)(INSTANCE_NAME=prebill)(SERVER=DEDICATED)))';
    edit database prebillb set property StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prebillb)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=prebill)(INSTANCE_NAME=prebill)(SERVER=DEDICATED)))';

            
    DGMGRL> SWITCHOVER TO prebilla
    Performing switchover NOW, please wait...
    Operation requires a connection to instance "prebill" on database "prebilla"
    Connecting to instance "prebill"...
    Connected.
    New primary database "prebilla" is opening...
    Operation requires startup of instance "prebill" on database "prebillb"
    Starting instance "prebill"...
    Unable to connect to database
    ORA-12545: Connect failed because target host or object does not exist

    Failed.
    Warning: You are no longer connected to ORACLE.

    Please complete the following steps to finish switchover:
            start up instance "prebill" of database "prebillb"

    原因是/etc/hosts没有配置ip和主机名对应。

    测试:

    切换:

    DGMGRL> switchover to prebillb
    Performing switchover NOW, please wait...
    Operation requires a connection to instance "prebill" on database "prebillb"
    Connecting to instance "prebill"...
    Connected.
    New primary database "prebillb" is opening...
    Operation requires startup of instance "prebill" on database "prebilla"
    Starting instance "prebill"...
    ORACLE instance started.
    Database mounted.
    Database opened.
    Switchover succeeded, new primary is "prebillb"
    DGMGRL> switchover to prebilla
    Performing switchover NOW, please wait...
    Operation requires a connection to instance "prebill" on database "prebilla"
    Connecting to instance "prebill"...
    Connected.
    New primary database "prebilla" is opening...
    Operation requires startup of instance "prebill" on database "prebillb"
    Starting instance "prebill"...
    ORACLE instance started.
    Database mounted.
    Database opened.
    Switchover succeeded, new primary is "prebilla"

    检查:

    SQL> conn sys/xxx@prebillb as sysdba

    Connected.
    SQL> select database_role ,protection_mode ,protection_level ,open_mode from v$database ;

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PHYSICAL STANDBY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ ONLY

    SQL> /

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PHYSICAL STANDBY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ ONLY

    SQL> /

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PHYSICAL STANDBY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ ONLY

    SQL> /

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PHYSICAL STANDBY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ ONLY

    SQL> /

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PHYSICAL STANDBY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ ONLY

    SQL> /

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PHYSICAL STANDBY MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ ONLY WITH APPLY

    SQL> conn sys/xxx@prebilla as sysdba
    Connected.
    SQL> select database_role ,protection_mode ,protection_level ,open_mode from v$database ;

    DATABASE_ROLE    PROTECTION_MODE      PROTECTION_LEVEL     OPEN_MODE
    ---------------- -------------------- -------------------- --------------------
    PRIMARY          MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE  READ WRITE
     

    参考处理:

    DGMGRL>switchover to <standby> Fails with ORA-12514 (Doc ID 1582927.1)

    Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
    Oracle Cloud Infrastructure - Database Service - Version N/A and later
    Oracle Database Cloud Exadata Service - Version N/A and later
    Oracle Database Backup Service - Version N/A and later
    Oracle Database Exadata Express Cloud Service - Version N/A and later
    Information in this document applies to any platform.

    SYMPTOMS

     As a process of DGMGRL>ENABLE configuration broker automatically do following,

    1.adds static entry in listener.ora

    2. update the value of staticconnectidentifier accordingly.

    This issue here is switchover will fail with "ORA-12514".
     

    DGMGRL> switchover to chicago
    Performing switchover NOW, please wait...
    Operation requires a connection to instance "chicago" on database "chicago"
    Connecting to instance "chicago"...
    Connected as SYSDBA.
    New primary database "chicago" is opening...
    Operation requires startup of instance "boston" on database "boston"
    Starting instance "boston"...
    Unable to connect to database using (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(PORT=1521)(HOST=<hostname>))(CONNECT_DATA=(SERVICE_NAME=boston_DGMGRL)(INSTANCE_NAME=boston)(SERVER=DEDICATED)))
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

    Failed.
    Warning: You are no longer connected to ORACLE.

    Please complete the following steps to finish switchover:
            start up instance "boston" of database "boston"

    CAUSE

     While adding static entry broker makes an entry for GLOBAL_NAME=<DB_UNIQUE_NAME> but in broker configuration staticconnectidentifier it adds as <SID>_DGMGRL.

    For example,


    1.

    DGMGRL>show database verbose boston;

        StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(PORT=1521)(HOST=<hostname>))(CONNECT_DATA=(SERVICE_NAME=boston_DGMGRL)(INSTANCE_NAME=boston)(SERVER=DEDICATED)))'
        StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'

    DGMGRL>show database verbose chicago;

        StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(PORT=1521)(HOST=<hostname>))(CONNECT_DATA=(SERVICE_NAME=chicago_DGMGRL)(INSTANCE_NAME=chicago)(SERVER=DEDICATED)))'
        StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'


    2.

    listener.ora,

      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = boston)  <----------Here the global_name should be boston_DGMGRL
          (ORACLE_HOME = /<oracle_home>)
          (SID_NAME = boston)
        )
        (SID_DESC =
          (GLOBAL_DBNAME = chicago) <----------Here the global_name should be chicago_DGMGRL
          (ORACLE_HOME = /<oracle_home>)
          (SID_NAME = chicago)
        )

    SOLUTION

    Either change the staticconnectidentifier of standby to <SID> or change the listener.ora static entry GLOBAL_NAME = <SID>_DGMGRL to avoid this issue in feature.

    NOTE : For current restart failure we will have to manually start the new primary database. There are two solution for this issue.

    SOLUTION 1  : Modify the staticconnectidentifier to available listener service

    ----------------

    Primary db_unique_name is boston
    Standby db_unique_name is chicago

    Check the listener services.

    On both primary and standby,

     $ lsnrctl services

    Now edit the staticconnectidentifier to any available services of respective database.

    1. Connect to DGMGRL,


    DGMGRL> edit database chicago set property staticconnectidentifier='(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(PORT=1521)(HOST=<hostname>))(CONNECT_DATA=(SERVICE_NAME=chicago)(INSTANCE_NAME=chicago)(SERVER=DEDICATED)))';

    NOTE : edit boston value for any future role transition,

    DGMGRL> edit database boston set property staticconnectidentifier='(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(PORT=1521)(HOST=<hostname>))(CONNECT_DATA=(SERVICE_NAME=boston)(INSTANCE_NAME=boston)(SERVER=DEDICATED)))';


    2. DGMGRL>show configuration;

    For switchover reference,

    <<1582837.1>> - 12c Dataguard Switchover Best Practices using DGMGRL(Dataguard Broker Command Prompt)

    SOLUTION 2 : Add static listener entry with the name mentioned in staticconnectidentifier i.e default service taken by DGMGRL which add configuration with the service_name of <SID>_DGMGRL
    ------------

    Modify static entry on listener.ora of current Standby.

    1. Standby (chicago)server,

    vi $ORACLE_HOME/network/admin/listener.ora
     

        (SID_DESC =
          (GLOBAL_DBNAME = chicago_DGMGRL)   <----------------add _DGMGRL 
          (ORACLE_HOME = /<oracle_home>)
          (SID_NAME = chicago)
        )


    2. Same way change the static entry of current primary also for feature role transition.
     

    NOTE : Example given for the default port(1521). For non default port set the local_listener on the respective database where ORA-12514 was thrown.

    Example,

    lsnrctl status

    .........

    Listener Log File /<path>/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<host IP>)(PORT=1525)))

    SQL>alter system set local_listener='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<host IP>)(PORT=1525)))';

    Details refer,

    8.3.40 StaticConnectIdentifier

    Oracle® Data Guard
    Broker
    11g Release 2 (11.2)

    展开全文
  • ORA-12514: 错误的解决

    2021-05-17 10:34:18
    今天在本机上连接rman时抛出12514的错误:C:\Documents and Settings\Administrator>rman nocatalog target sys/sys@colin恢复管理器: Release 10.2.0.1.0 - Production on星期二7月17 09:36:34 2007Copyright (c...

    今天在本机上连接rman时抛出12514的错误:

    C:\Documents and Settings\Administrator>rman nocatalog target sys/sys@colin

    恢复管理器: Release 10.2.0.1.0 - Production on星期二7月17 09:36:34 2007

    Copyright (c) 1982, 2005, Oracle.All rights reserved.

    RMAN-00571:

    RMAN-00569: ERROR MESSAGE STACK FOLLOWS

    RMAN-00571:

    RMAN-00554:内部恢复管理器程序包初始化失败

    RMAN-04005:目标数据库中存在错误:

    ORA-12514: TNS:监听程序当前无法识别连接描述符中请求的服务

    这个错误很常见,造成这个错误的原因也比较多,根据在线文档上的错误描述为:

    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

    Cause:The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

    Action:

    - Wait a moment and try to connect a second time.

    - Check which services are currently known by the listener by executing: lsnrctl services

    - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.

    - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.

    - Check for an event in the listener.log file.

    笔者这边遇到的情况为,每次关闭数据库重新启动后都会抛这样的错误。

    SQL> shutdown immediate;

    数据库已经关闭。

    已经卸载数据库。

    ORACLE例程已经关闭。

    C:\Documents and Settings\Administrator>sqlplus sys/sys@colin as sysdba

    SQL*Plus: Release 10.2.0.1.0 - Production on星期二7月17 11:30:09 2007

    Copyright (c) 1982, 2005, Oracle.All rights reserved.

    ERROR:

    ORA-12514: TNS:监听程序当前无法识别连接描述符中请求的服务

    察看监听文件的配置为:

    SID_LIST_LISTENER =

    (SID_LIST =

    (SID_DESC =

    (SID_NAME = PLSExtProc)

    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)

    (PROGRAM = extproc)

    ) ----注意这里缺少了相应得数据库服务

    )

    LISTENER =

    (DESCRIPTION_LIST =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))

    )

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)(HOST = COLIN)(PORT = 1521))

    )

    )

    下面呢就利用net manager为监听添加相应得数据库服务了

    注:上面是一个添加数据库服务的图片

    服务添加完成后,保存下,再看监听的配置:

    SID_LIST_LISTENER =

    (SID_LIST =

    (SID_DESC =

    (SID_NAME = PLSExtProc)

    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)

    (PROGRAM = extproc)

    )

    (SID_DESC =

    (GLOBAL_DBNAME = colin)

    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)

    (SID_NAME = colin)

    )-------相应的数据库服务添加上了

    )

    LISTENER =

    (DESCRIPTION_LIST =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))

    )

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)(HOST = COLIN)(PORT = 1521))

    )

    )

    好了下步就是要重新装入下监听器

    C:\Documents and Settings\Administrator>lsnrctl reload

    LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 17-7月-2007 12:0

    2:25

    Copyright (c) 1991, 2005, Oracle.All rights reserved.

    正在连接到(DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))

    命令执行成功

    我们再来显示下监听的状态:

    C:\Documents and Settings\Administrator>lsnrctl status

    LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 17-7月-2007 12:0

    2:56

    Copyright (c) 1991, 2005, Oracle.All rights reserved.

    正在连接到(DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))

    LISTENER的STATUS

    ------------------------

    别名LISTENER

    版本TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Produ

    ction

    启动日期17-7月-2007 09:39:35

    正常运行时间0天2小时23分21秒

    跟踪级别off

    安全性ON: Local OS Authentication

    SNMPOFF

    监听程序参数文件D:\oracle\product\10.2.0\db_1\network\admin\listener.o

    ra

    监听程序日志文件D:\oracle\product\10.2.0\db_1\network\log\listener.log

    监听端点概要...

    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))

    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=colin)(PORT=1521)))

    服务摘要..

    服务"PLSExtProc"包含1个例程。

    例程"PLSExtProc",状态UNKNOWN,包含此服务的1个处理程序...

    服务"colin"包含1个例程。

    例程"colin",状态UNKNOWN,包含此服务的1个处理程序...

    命令执行成功

    再关闭数据库,然后再连接数据库。Ok,no problem了~

    SQL> shutdown immediate

    数据库已经关闭。

    已经卸载数据库。

    ORACLE例程已经关闭。

    C:\Documents and Settings\Administrator>sqlplus sys/sys@colin as sysdba

    SQL*Plus: Release 10.2.0.1.0 - Production on星期二7月17 12:03:06 2007

    Copyright (c) 1982, 2005, Oracle.All rights reserved.

    已连接到空闲例程。

    展开全文
  • ora-12514:TNS:监听程序当前无法识别连接描述符中请求的服务bug,解决文档.
  • ORA-12514问题解决

    2021-05-17 10:34:04
    版本:11.2.0.1.0 - 64bit本机安装Oracle后链接测试发现以下情况:sqlplus scott/tiger 正常登陆sqlplus scott/tiger@orcl 登陆失败,提示ORA-12514错误,应该是无法识别服务名ORCL为此查阅资料,找到以下解决方案:...

    版本:11.2.0.1.0 - 64bit

    本机安装Oracle后链接测试发现以下情况:

    sqlplus scott/tiger 正常登陆

    sqlplus scott/tiger@orcl  登陆失败,提示ORA-12514错误,应该是无法识别服务名ORCL

    为此查阅资料,找到以下解决方案:

    -------------------------------------------------------------------

    找到oracle安装目录下listener文件:

    原文件如下:

    SID_LIST_LISTENER =

    (SID_LIST =

    (SID_DESC =

    (SID_NAME = CLRExtProc)

    (ORACLE_HOME = d:\app\Administrator\product\11.2.0\dbhome_1)

    (PROGRAM = extproc)

    (ENVS = "EXTPROC_DLLS=ONLY:d:\app\Administrator\product\11.2.0\dbhome_1\bin\oraclr11.dll")

    )

    )

    LISTENER =

    (DESCRIPTION_LIST =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))

    (ADDRESS = (PROTOCOL = TCP)(HOST = idylan)(PORT = 1521))

    )

    )

    ADR_BASE_LISTENER = d:\app\Administrator

    修改后如下:

    SID_LIST_LISTENER =

    (SID_LIST =

    (SID_DESC =

    (SID_NAME = CLRExtProc)

    (ORACLE_HOME = d:\app\Administrator\product\11.2.0\dbhome_1)

    (PROGRAM = extproc)

    (ENVS = "EXTPROC_DLLS=ONLY:d:\app\Administrator\product\11.2.0\dbhome_1\bin\oraclr11.dll")

    )

    (SID_DESC =

    (GLOBAL_DBNAME = ORCL)

    (ORACLE_HOME = d:\app\Administrator\product\11.2.0\dbhome_1)

    (SID_NAME = ORCL)

    )

    )

    LISTENER =

    (DESCRIPTION_LIST =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))

    (ADDRESS = (PROTOCOL = TCP)(HOST = idylan)(PORT = 1521))

    )

    )

    ADR_BASE_LISTENER = d:\app\Administrator

    保存,后sqlplus scott/tiger@orcl 可正常登陆。

    --------------------------

    dylan    presents.

    相关阅读:

    0b1331709591d260c1c78e86d0c51c18.png

    展开全文
  • ORA-12514的解决方法(多图)08-07栏目:技术TAG:ora-12514ora-12514我本机安装的数据库版本是oracle11G R2,用plsql连接时候,报ora-12514如下错误:www.jhua.orgjhua.org但是在cmd里用sqlplus连接已经创建的用户...

    ORA-12514的解决方法(多图)

    08-07栏目:技术

    TAG:ora-12514

    ora-12514

    我本机安装的数据库版本是oracle 11G R2,用plsql连接时候,报ora-12514如下错误:

    www.jhua.org

    120506103217931.jpg

    jhua.org

    但是在cmd里用sqlplus连接已经创建的用户时候,报如下错误: copyright www.jhua.org

    120506103217932.jpg

    jhua.org ORA-01034 - Oracle not available

    copyright jhua.org

    ORA-27101 - shared memory realm does not exist

    copyright www.jhua.org

    网上查了几个解决资料,说是oracle home和sid的问题,或者是让使用Net configuration Assistant重建本地网络服务名。实践了一下,都不管用。 https://www.jhua.org

    经过总结,使用如下方法解决比较好:

    https://www.jhua.org

    1、首先看一下 ORACLE_BASE\ORACLE_HOME\DATABASE 下面的 ORADIM.LOG 文件

    https://www.jhua.org

    E:\APP\psun\product\11.2.0\dbhome_1\database:

    jhua.org

    看日志才发现原来报的下面的错误!! copyright jhua.org

    ORA-00119: invalid specification for system parameter local_LISTENER

    www.jhua.org

    ORA-00132: syntax ERROR or unresolved network name 'LISTENER_ORCL'

    www.jhua.org

    120506103217933.jpg www.jhua.org

    2、进过查找该错误,发现是tnsnames.ora文件中少了如下语句的原因

    www.jhua.org

    LISTENER_MAXIMO =

    copyright jhua.org

    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))

    copyright www.jhua.org

    添加后,重启数据库实例服务,重启监听程序:

    www.jhua.org

    120506103217934.jpg jhua.org

    再次使用SQLPLUS、plsql连接,好了,呵呵!

    www.jhua.org

    120506103217935.jpg https://www.jhua.org jhua.org

    www.jhua.org

    https://www.jhua.org

    相关阅读

    ORA-12514 jhua.org

    在使用PLSQL Developer登录时出现ora-12514错误。

    在安装完成oracel之后数据库一直在启动状态,并没有关闭过,所以一直没问题,

    当关闭

    jhua.org

    ORA-12154:TNS:无法解析指定的连接标识符

    https://www.jhua.org

    ORA-12154:TNS:无法解析指定的连接标识符

    根本的解决方法是需要增加系统的环境变量: www.jhua.org

    “ora-12154无法解析指定的连接标识符”问题解决

    https://www.jhua.org

    环境:win10, oracle10.2.1, plsql 7.4问题:安装完oracle后,使用plsql连接数据库,发现总是报“ora-12154无法解析指定的连接标识符”错 www.jhua.org

    Oracle错误 ora-12514 解决方法

    https://www.jhua.org

    成功连到数据库上之后,查看listener状态:lsnrctl status

    status READY 状态,需要由非归档转为归档模式,故操作如下:

    1.关闭数据库shu

    copyright jhua.org

    ORA-000845 与 /dev/shm(tempfs) https://www.jhua.org

    MEMORY_TARGET参数在Oracle 11g被引进,主要是用于控制Oracle对于系统内存的使用,首次将SGA与PGA整合到一起实现自动管理。一旦设置

    https://www.jhua.org

    阅读量:100000+

    上一篇:COleVariant与常用基

    推荐量:5277

    下一篇:卡方分布(Chi-sq

    展开全文
  • 这时pl/sql developer连接oracle时报出“ORA-12514: TNS: 监听程序当前无法识别连接描述符中请求的服务”的错误,再次修改listener.ora文件,修改前该文件内容为 SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_...
  • 早上同事用PL/SQL连接虚拟机中的Oracle数据库,发现又报了“ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务”错误,帮其解决后,发现很多人遇到过这样的问题,因此写着这里。也许你没有遇到过,原因如下:...
  • 今天用rman连接数据库报错[linuxidc@rhel55 ~]$rman target sys/Oracle@orcl ORA-12514: TNS:listener does not currently know今天用rman连接数据库报错[linuxidc@rhel55 ~]$rman target sys/Oracle@orclORA-12514:...
  • ORA-12514:TNS 监听问题

    2021-05-05 05:37:27
    解决问题:ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务测试环境:RedHat7.4 + Oracle 11g 64位相关说明:数据库服务器:Oracle11g 64位软件的安装位置为/u01/app/oracle/product/11.2.0/dbhome_1,...
  • window server 安装的Oracle很久不用连接不上了,报ORA-12514:TNS:监听程序当前无法识别连接描述符中请求的服务,查看了服务实例名都是正确的。 二、查找问题 使用SQLplus本机连接: sqlplus system/system 出现...
  • 问题1:ORA-12154: TNS: 无法解析指定的连接标识符 在一台服务器上部署了Oracle客户端,使用IP/SID的方式访问,老是报ORA-12154错误,而使用tnsnames访问却没有问题,对比了我本机的配置并查阅了一下资料,Easy Connect ...
  • 该楼层疑似违规已被系统折叠隐藏此楼查看此楼【问题】:在登录oracle报错时提示ORA-12514的错误 【分析】使用telnet 127.0.0.1 1521 命令能正常执行,说明监听程序是正常的,端口正常,此时怀疑是数据库出现了问题...
  • 这里写自定义目录标题 plsql远程连接oracle数据库 ORA-12514错误解决 plsql远程连接oracle数据库 有两种方法 第一种需要安装oracle客户端 第二种需要通过 plsql 和 oracle 即时客户端(instantclient)来连接 oracle ...
  • 但是这个时候出现了另一个12514的异常,如下: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor 解决方案: 在服务器端的listener.ora文件中对应部分添加下面的黑体...
  • 虚拟机安装Oracle备忘:ORA-12514错误的解决[日期:2011-08-02]来源:Linux社区作者:taowei20061122[字体:大 中 小][Oracle@oracle_taowei_RedHat~]$ lsnrctl status 查看监听器是否启动如果没有启动监听,则运行...
  • Ora-12514原因及处理方法

    千次阅读 2021-03-29 20:42:46
    1)、ORA-12541:TNS:没有监听器 服务器端的监听器没有启动,另外检查客户端IP地址或端口填写是否正确。启动监听器: $lsnrctlstart 2)、ORA-12154:TNS:无法处理服务名 检查输入的服务名与配置的服务名是否一致。...
  • ora-12514报错解决方法

    2021-05-07 02:36:01
    现象:在客户端用PL/SQL DEV连接连虚拟机的数据库,报错误ORA-12514。原因:在网上差了下,大部分是在Windows平台安装数据库,或者在虚拟机安装Linux系统的Oracle后重启产生的现象。Oracle Net Services - Version ...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 5,088
精华内容 2,035
关键字:

ora-12514

友情链接: ecpri.rar