oracle unqname что это
Переменная среды ORACLE_UNQNAME не определена. Пожалуйста, установите ORACLE_UNQNAME на уникальное имя базы данных
У меня есть пакетный файл, который запускает службы Oracle
Но при выполнении скрипта я получаю:
Я использую 64-битную Windows 7 с 64-битной Oracle 11gR2. Любая информация будет очень полезна. Спасибо и С уважением.
4 ответа 4
Если у вас несколько IP-адресов, убедитесь, что адаптер статического адреса является основным, или добавьте адаптер Microsoft Loopback с адресом 10.10.10.10 в соответствии с инструкциями Oracle перед установкой. Предустановочные требования Oracle
Добавьте ORACLE_HOSTNAME и значение [имя компьютера] в переменные среды. Это был последний шаг, который наконец исправил мою установку. Обратите внимание, что вам нужно убедиться, что вы можете разрешить свою машину по этому адресу как по квалифицированному, так и по неквалифицированному имени машины. Возможно, вам придется настроить HOSTS, чтобы сделать это. Установка на компьютеры с несколькими IP-адресами
Если эти две вещи верны, ваши listener.ora и tnsnames.ora будут правильно соответствовать отдельной конфигурации em, и вам следует избегать требования устанавливать ORACLE_UNQNAME.
С наилучшими пожеланиями!
Чтобы получить доступ к консоли Oracle Enterprise Manager Console из клиентского браузера, на сервере должен быть запущен процесс dbconsole. Этот процесс автоматически запускается после установки.
Однако, если процесс не запущен из-за перезапуска системы или другого события, вы можете запустить его вручную из командной строки.
Чтобы запустить процесс dbconsole:
Запустите следующее утверждение:
Кроме того, вы можете остановить процесс и просмотреть его статус.
Чтобы остановить процесс dbconsole:
Чтобы просмотреть состояние процесса dbconsole:
MacLochlainns Weblog
Michael McLaughlin’s Technical Blog
What’s ORACLE_UNQNAME?
It started with a three part question: What’s the URL to run the DB Console for Oracle Database 11gR2 on Windows 7, and what’s the ORACLE_UNQNAME and why isn’t it defined by the installation. The first part is easy (shown further below), but the second and third parts were more involved.
The ORACLE_UNQNAME is an operating system environment variable that holds the database’s unique name value. You can find it with the following query as the SYSTEM user (through SQL*Plus):
SELECT name, db_unique_name FROM v$database;
By the way, it’s not set as a Windows environment variable by default. You would need to do that manually (an example of setting an environment variable is here). The Oracle Universal Installer (OUI) actually used it to configure the already running DB Console service (with a successful installation). Once there, it didn’t need to set it as a system-level environment variable.
You may be wondering what generated the question if there’s already a configured service. You encounter the error when dropping down to the command line. First, you verify that the ports are running with this command:
While this blog discusses the hard way to determine whether the DB Console is running, you can simply open the Windows Services to see whether the DB Console is running. Likewise, if you know the URL, enter it in your browser. Assuming you don’t know how to do either or are just a gluten for the command line, the rest of this post is important.
You can see your Windows services by typing services.msc in the Start->Run Command field. That way you don’t need to navigate the various links that differ between Windows releases.
For example, running the following command raises an error that instructs you to set the %ORACLE_UNQNAME% environment variable. Although, it leaves many wondering what’s the right value to enter.
C:\> emctl status dbconsole Environment variable ORACLE_UNQNAME not defined. Please set ORACLE_UNQNAME to database unique name.
If you object to using the Windows services to start and stop the OEM tool, you can do it at the command-line like the status example above. Having set the environment variables, you can start the DB console with this command-line syntax:
C:\> emctl start dbconsole
Having set the environment variables, you can stop the DB console with this command-line syntax:
C:\> emctl stop dbconsole
You can find them by navigating to the %ORACLE_HOME%\oc4j\j2ee\ folder (or directory). The file name of the DB Console file tells you the values for these environment variables because they’re embedded in the file’s name. A snapshot from Windows Explorer shows them both.
You can set these environment variables as shown below in command shell of Windows (Linux or Unix users should use terminal), and then successfully run emctl from the command line.
If you’re using Linux or Unix, the export commands differ. You can check this other post for those. They under step 8 in that post.
You then enter the following URL in a browser to use the newly installed DB Console:
The browser will prompt you with a security warning like the following:
Click the Add Exception button and you’ll see the following Windows dialog.
Having granted the exception, you arrive at the following credential web page. Connect as the SYSDBA using the SYS user’s account when you require extraordinary privileges. Doing so, shows a security risk in the console. You should connect as the SYSTEM user with NORMAL access generally, as shown below.
The following home page shows after your credentials are validated.
Hope that helps those trying to sort out running the DB Console and finding the magic %ORACLE_UNQNAME% value. Check this other blog post for instructions to reconfigure OEM.
Environment variable ORACLE_UNQNAME not defined. Please set ORACLE_UNQNAME to database unique name.
Client’s server can not start em, error message as follows:
Environment variable ORACLE_UNQNAME not defined. Please set ORACLE_UNQNAME to database unique name.
What needs to be checked?
1. The hostname in TNS and LSN configuration files in the Oracle directory
2, hostname in /etc/hosts under Linux
are all hostname consistent?
If you are sure that the hostname and sid instance name are correct
Then, I suggest you perform the emc reconstruction operation
$ sqlplus / as sysdba
SQL> alter user dbsnmp identified by py123456;
User altered.
SQL> drop role MGMT_USER;
Role dropped.
SQL> drop user MGMT_VIEW cascade;
User dropped.
SQL> drop user sysman cascade;
User dropped.
SQL> drop user sysman cascade;
SQL> drop PUBLIC SYNONYM MGMT_TARGET_BLACKOUTS;
Synonym dropped.
SQL> drop public synonym SETEMVIEWUSERCONTEXT;
Synonym dropped.
SQL>quit
STARTED EMCA at May 26, 2017 10:37:01 AM
EM Configuration Assistant, Version 11.2.0.3.0 Production
Copyright (c) 2003, 2011, Oracle. All rights reserved.
Enter the following information:
Database SID: oracle11
log4j:WARN No appenders could be found for logger (emSDK.config).
log4j:WARN Please initialize the log4j system properly.
Listener port number:
Listener ORACLE_HOME [ ]:
Password for SYS user:
Password for DBSNMP user:
Password for SYSMAN user:
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
If you see this warning
WARNING: ORA-00955: name is already used by an existing object—
this is the configured doesn’t clean up, run
Finally, em can start up.