How to start, shut down, and obtain the installation information of Oracle cloud control 12c, cloud12c

How to start, shut down, and obtain the installation information of Oracle cloud control 12c, cloud12c

The entire installation of Oracle cloud control 12c is complicated. The installation path, logon password, port number, and many other configurations are confusing. This article describes how to obtain the various port numbers, URLs, and how to start and disable cloud control after the installation is complete for your reference.

For cloud control Installation configuration, see Oracle Enterprise Manager Cloud Control 12c Release 3 Installation.

1. Current Environment Configuration

Copy codeThe Code is as follows:
[Oracle @ oel63 ~] $ More ~ /. Bash_profile
#. Bash_profile
# Get the aliases and functions
If [-f ~ /. Bashrc]; then
.~ /. Bashrc
Fi
# User specific environment and startup programs
PATH = $ PATH: $ HOME/bin
Export PATH
# Oracle Settings
TMP =/tmp; export TMP
TMPDIR = $ TMP; export TMPDIR
ORACLE_HOSTNAME = oel63.ycdata.net; export ORACLE_HOSTNAME
ORACLE_UNQNAME = ora11g; export ORACLE_UNQNAME
ORACLE_BASE =/u01/ora11g; export ORACLE_BASE
ORACLE_HOME = $ ORACLE_BASE/db_1; export ORACLE_HOME
ORACLE_SID = ora11g; export ORACLE_SID
PATH =/usr/sbin: $ PATH; export PATH
PATH = $ ORACLE_HOME/bin: $ PATH; export PATH
LD_LIBRARY_PATH = $ ORACLE_HOME/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH = $ ORACLE_HOME/jlib: $ ORACLE_HOME/rdbms/jlib; export CLASSPATH
Export OMS_HOME =/u01/oms12375/oms
Export AGENT_HOME =/u01/agent12cr2/core/12.1.0.3.0
[Oracle @ oel63 ~] $ More/etc/issue
Oracle Linux Server release 6.3
Kernel \ r on an \ m
[Oracle @ oel63 ~] $ Sqlplus-v
SQL * Plus: Release 11.2.0.3.0 Production

2. Start repository DB and OMS

Copy codeThe Code is as follows:
# Before starting oms, you need to start the Repository DB, which is used to store the collected monitoring information
# Start the listener when starting the database. Otherwise, you will receive the Failed to connect to repository database.
# However, OMS will automatically restart. When the DB and listener are detected to be UP (OMS will be automatically restarted once it identifies that database and listener are up .)
[Oracle @ oel63 ~] $ Lsnrctl start
[Oracle @ oel63 ~] $ Ps-ef | grep pmon | grep-v grep
[Oracle @ oel63 ~] $ Sqlplus/as sysdba
SQL> startup
SQL> exit
 
# Use the following command to start oms and agent
[Oracle @ oel63 ~] $ OMS_HOME/bin/emctl start oms
[Oracle @ oel63 ~] $ AGENT_HOME/bin/emctl start agent

3. view the installation information

Copy codeThe Code is as follows:
# View the previous installation information and port information, and connect to the cloud control console accordingly
[Oracle @ oel63 ~] $ Cd $ OMS_HOME/install
[Oracle @ oel63 install] $ more eminstall.info
INSTALL_TYPE = NOSEED
UPGRADE = false
ORACLE_MIDDLEWARE_HOME_LOCATION =/u01/oms12375 # Weblogic installation location
OMS_HOME =/u01/oms12301/oms # OMS installation location
AGENT_HOME =/u01/agent12cr2/core/12.1.0.3.0 # Agent installation location
AGENT_BASE_DIR =/u01/agent12cr2 # Agent base Directory
 
# Below are some important port information
[Oracle @ oel63 install] $ more portlist. ini
Enterprise Manager Upload Http Port = 4889
Enterprise Manager Upload Http SSL Port = 4903
Enterprise Manager Central Console Http SSL Port = 7802
Node Manager Http SSL Port = 7403
Managed Server Http Port = 7202
Enterprise Manager Central Console Http Port = 7788
Oracle Management Agent Port = 3872
Admin Server Http SSL Port = 7102
Managed Server Http SSL Port = 7301
[Oracle @ oel63 install] $ more setupinfo.txt
This information is also available:
/U01/oms12301/oms/install/setupinfo.txt
See below for information pertaining to your Enterprise Manager installation:
 
# The following is the URL for logging on to the cloud control console and logging on to Weblogic. Perform corresponding management based on this URL.
Use the following URL to access:
1. Enterprise Manager Cloud Control URL: https://oel63.ycdata.net: 7802/em
2. Admin Server URL: https://oel63.ycdata.net: 7102/console
The following details need to be provided during the additional OMS install:
1. Admin Server Hostname: oel63.ycdata.net
2. the Admin Server Port is 7102.
You can find the ports details used by this deployment at:/u01/oms12301/oms/install/portlist. ini

NOTE:
An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the Repository becomes unusable.
A backup of the OMS configuration is available in/u01/gc_inst/em/EMGC_OMS1/sysman/backup on host oel63.ycdata.net. see Cloud Control Administrators Guide for details on how to back up and recover an OMS.
NOTE: This backup is valid only for the initial OMS configuration. for example, it will not reflect plug-ins installed later, topology changes like the addition of a load balancer, or changes to other properties made using emctl or emcli. backups shoshould be created on a regular basis to ensure they capture the current OMS configuration. use the following command to backup the OMS configuration:
/U01/oms12301/oms/bin/emctl exportconfig oms-dir <backup dir>

4. Disable OMS and repository DB

Copy codeThe Code is as follows:
[Oracle @ oel63 ~] $ OMS_HOME/bin/emctl stop oms-all
[Oracle @ oel63 ~] $ AGENT_HOME/bin/emctl stop agent
[Oracle @ oel63 ~] $ Lsnrctl stop
[Oracle @ oel63 ~] $ Export ORACLE_SID = ora11g
[Oracle @ oel63 ~] $ Sqlplus/as sysdba
SQL> shutdown immediate;

How Does oracle 12c access the graphic interface, that is, the Enterprise Manager? There is a manger console on the 11g, and 12c is gone. Can you help me?

1. Start EM Database Express 12c and set the port to enable EM Express.
SQL> show parameter dispatchers
SQL> exec DBMS_XDB_CONFIG.setHTTPPort (8080 );

2. Install Oracle Enterprise Manager Cloud Control 12c.

Oracle12c Installation Error

1. Solve the c $ share problem first.
2. Test whether c $ share is successful. The method is to hit net use \ localhost \ c $ in cmd. The failure will be like this ..: System Error 53
The network path was not found. Success is like this: The command is successfully completed.
3. If Step 3 fails, check whether the "TCP/IP NetBIOS Helper" service in "service" is enabled. If not, start the service. Solve the Problem of system error 53:
When the command net usenet use \ localhost \ c $ is used, error 53 is generated and the network path cannot be found. I entered the net share command in the Virtual Machine and found that there was only one IPC $ (the original share was disabled by default). After Baidu's translation, I found a solution: Step 1: check the AutoShareServer and autosharwks registry values to ensure that they are not set to 0. Click Start> Run, enter regedit, and press enter to enter the Registry Editor.
Step 2: locate and click HKEY_LOCAL_MACHINESystemCurrent ControlSetServicesLanmanServerParameters. Step 3: If LanmanServerParameter
If the value of AutoShareServer and autosharwks DWORD in the s subitem is set to 0, the value is changed to 1.