The ORACLE_UNQNAME is an operating system environment variable that holds the databases

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, its 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 didnt need to set it as a system-level environment variable.
You may be wondering what generated the question if theres 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:

C:\> netstat -an | findstr /C:1158

TCP
0.0.0.0:1158
0.0.0.0:0

LISTENING

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 dont 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 dont need to navigate the various links that differ between Windows releases.

Many know that you can check the status of the running DB Console with the emctl utility at the
command line. It lets you find the URL that you should enter for the DB Console in a browser. This
knowledge is where users encounter the problem with %ORACLE_UNQNAME% environment variable
($ORACLE_UNQNAME on Linux or Unix).
For example, running the following command raises an error that instructs you to set
the %ORACLE_UNQNAME%environment variable. Although, it leaves many wondering whats 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

Its not hard to find this information when you know how. While the error message complains
about one environment variable, there are actually two environment values you need to set. They
are: %ORACLE_HOSTNAME%and %ORACLE_UNQNAME%.
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
theyre embedded in the files 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.

C:\>set ORACLE_HOSTNAME=localhost
C:\>set ORACLE_UNQNAME=orcl

C:\>emctl status dbconsole

Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
https://localhost:1158/em/console/aboutApplication
Oracle Enterprise Manager 11g is running.
-----------------------------------------------------------------Logs are generated in directory
C:\app\McLaughlinM\product\11.2.0\dbhome_1/localhost_orcl/sysman/log
If youre 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:

https://localhost:1158/em
The browser will prompt you with a security warning like the following:

Click the Add Exception button and youll see the following Windows dialog.

Having granted the exception, you arrive at the following credential web page. Connect as
the SYSDBA using theSYS users 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.