Содержание
- samadhandba
- Journey to world of ORACLE DBA with Samadhan
- ORA-00119: invalid specification for system parameter LOCAL_LISTENER / ORA-00132: syntax error or unresolved network name ‘LISTENER_
- Oracle Database 11g (11.1.0.6.0) > ORA-00119 & ORA-00132 errors
- ORA-00119,ORA-00132 during duplicate target database for standby in 11gR2
- Database creation: Warning ORA-00119, ORA-00132
- getting error:ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00132: synta
- Best Answer
- Answers
samadhandba
Journey to world of ORACLE DBA with Samadhan
ORA-00119: invalid specification for system parameter LOCAL_LISTENER / ORA-00132: syntax error or unresolved network name ‘LISTENER_
September 28, 2012 by samadhan
Today i face this issue after Oracle 11g upgrade and posting it for you as it is.
Problem:
The local_listener parameter has been set, the listener is running, but when attempting to start the instance an ORA-00119 is reported:
SQL*Plus: Release 11.2.0.2.0 Production on Fri Sep 28 11:34:29 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name ‘LISTENER_SID
Reason :
Oracle only checks for listeners running on the default port (1521). It would have to spend all day trying every possible port number otherwise. You’ll need to give it some help to find your listener.
Solution:
Simply add an entry to the servers tnsnames.ora pointing at the listener. As mention below
TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.2.0 – Production on 28-SEP-2012 13:13:36
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
/oracle/SID/112_64/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (SDU = 2768) (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = sidb00) (PORT = 1527))) (CONNECT_DATA = (SID = SID) (GLOBAL_NAME = SID.WORLD)))
OK (20 msec)
Now it is working. Also wana add one more point.
make sure that parameter by name *.local_listener=’LISTENER_SID’ in pfile as it is mention.
I Hope this article helped to you. I am expecting your suggestions/feedback.
It will help to motivate me to write more articles….
Источник
Oracle Database 11g (11.1.0.6.0) > ORA-00119 & ORA-00132 errors
Oracle Database 11g (11.1.0.6.0)
I am creating a new Oracle 11g database in our Development environment. This is my first time installing a 11g database. During the install process, Database Configuration Assistant window appears and ‘Copying database files’ is highligted and the Clone database creation in progress is at 2%, when I get the following Database Configuration Assistant error:
ORA-00119: invalid specification for system parameter LOCAL_LISTENEr
ORA-00132: syntax error or unresolved network name ‘LISTENER_DEVTEST1’
ORA-01078: failure in processing system parameters
Research Info
===============================================
*$ more listener.ora*
# listener.ora Network Configuration File: /u002/dbsvr/oratst/11.1/network/admin
/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1524))
(ADDRESS = (PROTOCOL = TCP)(HOST = dallinux02.clubcorp.com)(PORT = 1524))
)
)
===============================================
*$ more tnsnames.ora*
# tnsnames.ora Network Configuration File: /u002/dbsvr/oratst/11.1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
LISTENER_DEVTEST1 =
(ADDRESS = (PROTOCOL = TCP)(HOST = dallinux02.clubcorp.com)(PORT = 1524))
===============================================
*$ lsnrctl status*
LSNRCTL for Linux: Version 11.1.0.6.0 — Production on 11-MAR-2009 14:11:44
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1524)))
STATUS of the LISTENER
————————
Alias LISTENER
Version TNSLSNR for Linux: Version 11.1.0.6.0 — Production
Start Date 11-MAR-2009 14:04:06
Uptime 0 days 0 hr. 7 min. 37 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u002/dbsvr/oratst/11.1/network/admin/listener.ora
Listener Log File /u002/dbsvr/oratst/diag/tnslsnr/dallinux02/listener/alert/log.xml
Listening Endpoints Summary.
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1524)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dallinux02.clubcorp.com)(PORT=1524)))
The listener supports no services
The command completed successfully
================================================
Port 1524 is not being used by another database.
Источник
ORA-00119,ORA-00132 during duplicate target database for standby in 11gR2
I am running
duplicate target database for standby from active database
command from RMAN.
I went thru step-by-step on how to create a standby database from the textbook i got from my Oracle Univ. 11g Data Guard course. I set up all the listener.ora and tnsnames.ora files using netmgr, but I’m getting local_listener error.
Here’s what I am running in rman:
run <
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert ‘kyledb’,’kylerep’
set db_unique_name=’kylerep’
set db_file_name_convert=’/kyledb/’,’/kylerep/’
set log_file_name_convert=’/kyledb/’,’/kylerep/’
set control_files=’/oradata/kylerep/control01.ctl’
set log_archive_max_processes=’4′
set fal_client=’kylerep’
set fal_server=’kyledb’
set standby_file_management=’AUTO’
set log_archive_config=’dg_config=(kyledb,kylerep)’
set log_archive_dest_1=’service=kyledb ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=kyledb’
;
>
And here’s the error i get:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/12/2010 17:33:28
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name ‘LISTENER_KYLEDB’
result of
SQL>show parameter local_listener;
entry in my listener.ora is
SID_LIST_KYLEDB_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = kyledb.kyledev.usms.doj.gov)
(ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = kyledb)
)
)
KYLEDB_LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
)
and entry in tnsnames.ora file is
KYLEREP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = kyledbdev.usms.doj.gov)(PORT = 7898))
)
(CONNECT_DATA =
(SERVICE_NAME = kylerep.kyledbdev.usms.doj.gov)
)
)
KYLEDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = kyledb.kyledev.usms.doj.gov)
)
)
LISTENER_KYLEDB =
(ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
Can anyone help me figure out what went wrong?
Источник
Database creation: Warning ORA-00119, ORA-00132
I am using SUSE Linux Enterprise Server 11 SP4 and I used the following guide to install and configure Oracle Grid (12.2.1) and Oracle Database 12c Release 1 (12.1.0.2):
Installation of Oracle Grid as well as the installation of the Database software finished without issues. Unfortunately the creation of a new database is producing some warnings during the database creation process:
I am providing you the contents of the following files, so you can see how the setup looks like:
and the .bash_profile:
According to this article (http://dba-oracle.com/bk_ora_00119.htm) I decided to modify the SPFILE/PFILE. First I tried to get an overview which files are located in ASM by using the command asmcmd. After entering asmcmd no command (for example: ls, cd, ..) was working. After some research I changed the following parameters:
After changing the parameters the commands are working now. In /DATA/ there are the following files which I can find:
SQL> show parameter spfile
NAME TYPE VALUE
spfile string +DATA/ASM/ASMPARAMETERFILE/registry.253.937097749
I was surprised of the result, because I was expecting to find the SPFILE in the folder ORCL instead. But I tried to continue and create a PFILE from the SPFILE with the following command:
SQL> CREATE PFILE=’/home/oracle/my_init.ora’ FROM SPFILE’+DATA/ASM/ASMPARAMETERFILE/REGISTRY.253.937097749′
After hitting enter a new line shows up with the number «2» and waiting for some input from my end I think. Hitting again enter it finishes, but no PFILE was created.
Anyway is the started approach to fix this warning the correct one? If you think yes then what should I do to edit the SPFILE successfully
Источник
getting error:ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00132: synta
I am in the 11gr2 database cloning process for EBS12.1.3
The relevant entry of my init.ora is » local_listener = SAND_LOCAL «
After starting the database I get following error.
ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00132: syntax error or unresolved network name ‘SAND_LOCAL’ .
when i comment out #local_listener = SAND_LOCAL, then can start the database . All other database cloning part are completed but so far could not fix the issue.
Below se below the entries of tnsnames.ora and listener.ora
[email protected] /backup/SAND/11gR2/product/11.2.0.4/network/admin/unix server)> cat tnsnames.ora
# This file is automatically generated by AutoConfig. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink Note
# 387859.1 for assistance.
#$Header: NetServiceHandler.java 120.19.12010000.8 2013/02/26 12:11:13 dhakumar ship $
IFILE=/backup/SAND/11gR2/product/11.2.0.4/network/admin/unix server/unix server_ifile.ora
[email protected] (/backup/SAND/11gR2/product/11.2.0.4/network/admin/unix server)> cat listener.ora
# $Header: ad8ilsnr.ora 120.3.12010000.3 2010/03/09 07:07:03 jmajumde ship $
# This file is automatically generated by AutoConfig. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink Note
# 387859.1 for assistance.
# Net8 definition for Database listener
(ADDRESS = (PROTOCOL = TCP)(HOST = unixserver )(PORT = 1566))
# added parameters for bug# 9286476
# ADR is only applicable for 11gDB
orasand 1 0 08:00:00 pts/3 0:00 /backup/SAND/11gR2/product/11.2.0.4/bin/tnslsnr SAND -inherit
[email protected](/backup/SAND/11gR2/product/11.2.0.4/network/admin/SAND_unixserver)> tnsping SAND_LOCAL
TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.4.0 — Production on 29-JUN-2017 11:04:50
Copyright (c) 1997, 2013, Oracle. All rights reserved.
Used parameter files:
Best Answer
Thank you everybody. The issue is fixed.
What I have done.
1)-Since it was oracle ebs 12.1.3 (11gR2) database. I changed init.ora file that was copied from the source database.
2)-Removed local_listener = SAND_LOCAL » from init.ora file.
3)- Ran perl adcfgclone.pl dbTier again, this time it completed successful til end
4)- When adcfgclone job completed, I was able to connect to database with any error message.
5)- When I checked init.ora file , the local_listener = SAND_LOCAL was there in the file uncommented.
Answers
When was last time listener worked without error?
What changed since then?
Why are you using non-standard listener name & port# when you obviously don’t know what you are doing?
No listener.ora file is required to start & use the listener.
move or remove listener.ora the start the listener using default values.
First, see MOS Doc id 359386.1
Your ORACLE_HOME is under a directory named ‘/backup’? How very odd . . .
There are some things I find odd about your tnsnames, but from the above it appears that it is created by Oracle E-Business Suite configuration . . .
In spite of my previous comment, why is your listener running on a non-standard port? Is this an E-Business requirement?
In spite of my previous comment, why does this entry list both SERVICE_NAME and INSTANCE_NAME?
While technically not wrong, I’ve never (in over 20 years as an Oracle dba) seen a net service name «SID_LIST_something». Looks like a confusion between tnsnames.ora and listener.ora, where it would be quite normal to have a SID_LIST section.
Your IFILE spec has an embeded space between «unix» and «server_ifile.ora» This doesn’t work in *nix.
And what is that second line («[email protected](/backup/SAND/11gR2/product/11.2.0.4/network/admin/unix server)>»)
So you named your listener SAND instead of the default name of LISTENER. This is more than odd, it simply makes admin more difficult, for no good reason.
Again, that embedded space . . .
I can’t even guess the purpose of an IFILE in the listener.ora. Nor that line following. In fact, just now checking the Net Services Reference, I don’t even see where IFILE is a legitimate parameter in listener.ora.
Since this appears to be E-Business suite (please confirm) I’ll have to be the first to admit that I’ve never worked with that product and the possibility exists of it doing some «odd» things with network config, but it looks to me like a lot of mis-understandings on how the pieces fit together.
Источник
Если вы столкнулись с: ORA-27101: [область разделяемой памяти не существует]
ora-00119【ora-00119 invalid specification for system parameter】
ora-00132【syntax error or unresolved network name ‘LISTENER_ORCL’】
Среда: win7 64-битный Oracle 11g
Простая команда sql:
Сначала войдите в sqlplus: sqlplus / nolog;
База данных входа: conn / as sysdba;
Затем запустите базу данных: запуск;
обнаружил ora-00119 【ora-00119 недопустимую спецификацию для системного параметра】
ora-00132【syntax error or unresolved network name ‘LISTENER_ORCL’】:
Теперь кажется вполне понятно, что 00119 означает, что oracle не запустился!
А теперь более простой:
[Решение] Способ ①: Таким образом, каждый раз, когда компьютер перезагружается, вам нужно запускать базу данных с идентификатором sysdba, преимущества: может углубить впечатление об основных секретах SQL, недостатки: проблемы;
1. Найдите папку: pfile; хотя все устанавливают oracle по разному, вы обязательно найдете эту папку в каталоге установки!
Например, моя папка:
D:appjamb008adminorclpfile
2. В этом файле есть файл: init.ora.1132014143422, который на самом деле является pfile, файлом, который используется для запуска oracle!
3. Откройте его с помощью WordPad, найдите local_listener, затем измените его значение (исходное значение называется LISTENER_ORCL) и замените его на ADDRESS_LIST в вашем tnsnames.ora:
4. Затем вернитесь в cmd и выполните:
startup pfile=’D:appjamb008adminorclpfileinit.ora.1132014143422′
5. Войдите в систему с помощью plsql еще раз: системный менеджер успешно работает! ! !
————————————————— —— Великолепный разделитель —————————————— ————————————————— ——
[Решение] Способ №: (То, что говорят в Интернете о копировании pfile в spfile и т. Д., Это слабо !!!) Все же используйте этот «слабый метод».
1. Войдите как sysdba
sqlplus /nolog
conn /as sysdba
2. Создайте spfile.
create spfile from pfile = ‘D:appjamb008adminorclpfileinit.ora.1132014143422’
Файл создан
Вот небольшое объяснение: oracle11g Этот файл находится в: D: app jamb008 product 11.2.0 dbhome_1 database
10g Этот документ находится в папке: D: app jamb008 product 11.2.0 dbhome_1 dbs;
Начать заново:
startup
3. На этом этапе мы обнаружили, что оракул был успешно запущен, а затем перезапустили компьютер, снова вошли в систему с помощью plsql и обнаружили, что база данных была напрямую введена.
вперед от:https://blog.csdn.net/xb12369/article/details/26720275
September 28, 2012 by samadhan
Today i face this issue after Oracle 11g upgrade and posting it for you as it is.
Problem:
The local_listener parameter has been set, the listener is running, but when attempting to start the instance an ORA-00119 is reported:
SQL*Plus: Release 11.2.0.2.0 Production on Fri Sep 28 11:34:29 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name ‘LISTENER_SID
Reason :
Oracle only checks for listeners running on the default port (1521). It would have to spend all day trying every possible port number otherwise. You’ll need to give it some help to find your listener.
Solution:
Simply add an entry to the servers tnsnames.ora pointing at the listener. As mention below
LISTENER_SID.WORLD=
(DESCRIPTION =
tnsping LISTENER_SID.WORLD
TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.2.0 – Production on 28-SEP-2012 13:13:36
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
/oracle/SID/112_64/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (SDU = 2768) (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = sidb00) (PORT = 1527))) (CONNECT_DATA = (SID = SID) (GLOBAL_NAME = SID.WORLD)))
OK (20 msec)
Now it is working. Also wana add one more point.
make sure that parameter by name *.local_listener=’LISTENER_SID’ in pfile as it is mention.
I Hope this article helped to you. I am expecting your suggestions/feedback.
It will help to motivate me to write more articles….!!!!
Thanks & Regards,
Samadhan
https://samadhandba.wordpress.com/
“Key for suceess, always fight even knowing your defeat is certain….!!!!
Posted in Backup and Recovery | Tagged list, listener, ORA-00119, ORA-00132, Oracle, tnsping | 1 Comment