1.5. Verification after configuration

1.5.1. Verification Verifying that the Listener boots.

Log in as Oracle user (If “Listener name” is LISTENER)

$ lsnrctl status LISTENER
LSNRCTL for Linux: Version - Production on 25-3 -2016 14:45:46
Copyright (c) 1991, 2014, Oracle. All rights reserved.
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle-se2.cloud.lab.oratest.com)(PORT=1521))) The status of Listner

Another Name Listener
Version TNSLSNR for Linux: Version - Production
Start Date 25-03-2016 13:53:00
Running time 0day 0hour 52 mins 46secs
Trace Level Off
Security ON: Local OS Authentication
Parameter File /u01/app/oracle/product/
Log file /u01/app/oracle/diag/tnslsnr/oracle-se2/listener/alert/log.xml
Listening Endpoint Summary
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=oracle-se2.cloud.lab.oratest.com)(PORT=5500))(Security=(my_wallet_ directory=/u01/app/oracle/admin/orcl/xdb_wallet))(Presentation=HTTP)(Session=RAW))
Service Summary
The service “orcl” has one Instance.
The Instance “orcl” at the“READY” state has one handler to this service.
The service “orclXDB” has one Instance.
The Instance “orcl” at the“READY” state has one handler to this service.
The command has successfully finished.
Verify that the service has been booting. Verifying that the Instance has booted.

Following is the command in the event SID is “orcl”.

$ sqlplus sys@orcl as sysdba
SQL*Plus: Release Production on 金 3月 25 14:48:19 2016
Copyright (c) 1982, 2014, Oracle. All rights reserved.

Enter password:
Oracle Database 12c Standard Edition Release - 64bit Production

SQL> Verifying the Instance Version.

SQL> select banner from v$version;

Oracle Database 12c Standard Edition Release - 64bitProduction
PL/SQL Release - Production
CORE Production
TNS for Linux: Version - Production
NLSRTL Version - Production

You need to verify the contents as “” as well as “SE2”. Connecting to “EM Database Express”

You need to configure the various settings such as Firewall, etc., if you connect to the EM database express from the external environments. For the procedure of how to configure the settings, please refer to “Enterprise Cloud 2.0 Tutorial Documents”.
NOTE: If the Instance Firewall boots at the default state, the EM Database Express will be blocked and fail to connect. If this incident occurs, you need to stop the current utilizing Firewall temporally, then verify the details on the connectivity. Following is how you shut off the utilizing Firewall temporally, as described below.
# systemctl stop firewalld
Following is the destination URL for this procedure environment.
Or, specify the IP Address.
“User Name” : sys
“Password” : Enter the password you configure.
“as sysdba” : check in
After filling in the details, click “Login”.
Finally, you need to verify that your created Database is appeared at the screen, as above.