Oracle Enterprise Manager Grid Control is a product of Oracle Corporation, using this this we can monitor and administrate the supported targets like databases, servers, ets.. . Installation process of Grid control configuration include installing, Oracle Database for repository, Weblog Application Server, applying required patches, installing OMS and final installing grid control agents on desired server targets and registering targets.
To configure Grid Control server “GRIDCTL” (172.30.30.240) is allocated for OMS, Repository Database and Web logic application server.
Configuration
|
Hosting Server
|
IP Address
|
Operating System
|
Repository Database
|
GRIDCTL
|
172.30.30.240
|
Microsoft Windows Server 2003 Server 5.2 Service Pack 2 (32-bit)
|
Web Logic App Server
|
GRIDCTL
|
172.30.30.240
|
Microsoft Windows Server 2003 Server 5.2 Service Pack 2 (32-bit)
|
Grid Control OMS
|
GRIDCTL
|
172.30.30.240
|
Microsoft Windows Server 2003 Server 5.2 Service Pack 2 (32-bit)
|
Grid Control hosting server “GRICTL” configuration is listed below.
Configuration
|
GRIDCTL
|
IP Address
|
172.30.30.240
|
Operating System
|
Microsoft Windows Server 2003 Server 5.2 Service Pack 2 (32-bit)
|
RAM
|
8 GB
|
Number of Processors
|
2
|
Hardware Platform
|
DELL PowerEdge 2800
|
To configure Grid Control, plat form based grid control release and versions, target server plat form agent versions and pre requisites of Grid Control need to be finalized. Below table lists products adopted to configure grid control system
To configure Grid Control, prerequisites need to be configured in advance. Below prerequisites are configured for Grid Control
Note: Please refer Grid control Documentation for Prerequisites
Hardware Requirements
Below Table Lists Required Physical Memory for Oracle Management Service and Oracle Management Agent
Installation Type
|
Physical Memory (RAM)
|
Oracle Management Service
|
3 GB
|
Oracle Management Agent
|
512 MB
|
Below Table Lists Recommended Physical Memory and Hard Disk Space for Oracle Management Repository
Installation Type
|
Physical Memory (RAM)
|
Hard Disk Space
|
Small(< 100 monitored targets)
|
2 GB
|
50 GB
|
Medium(< 1000 monitored targets)
|
4 GB
|
100 GB
|
Large(< 10,000 monitored targets)
|
6 GB
|
400 GB
|
Operating System Requirements
Ensure that you install Enterprise Manager Grid Control only on certified operating systems as mentioned in My Oracle Support note 412431.1.
Temporary Directory Space Requirements
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. For example, /tmp on UNIX hosts and c:\Temp on Microsoft Windows hosts.
JDK Requirements
Ensure that you have SUN JDK 1.6_18 version installed on the host where you are planning to install Enterprise Manager Grid control. This is required for all UNIX 64 bit platforms and Microsoft Windows 64 bit platforms.If you have a JDK installed, then verify its version by navigating to the <jdk>/bin directory and running the following command. The output of this query should give you the complete version number.
java -fullversion
You can also download the JDK from the following location, and you can also refer to My Oracle Support note 1063587.1 for an example on installing JDK 1.6_18 on Linux x86_64 platform.
Note: JROCKET is not supported.
Oracle WebLogic Server Requirements
1) Ensure that Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1) is already installed on the host where you plan to install Enterprise Manager Grid Control.
2) Ensure that the installation was a typical installation, and even if it was a custom installation, ensure that components chosen for custom installation were the same as the ones associated with a typical installation
3) Ensure that the installation was under the Middleware Home directory. For example, /scratch/aime/Oracle/Middleware1/wlserver_10.3
Enterprise Manager Grid Control will create a new domain in this Oracle WebLogic Server, and not use any of the existing domains.
For information on installing Oracle WebLogic Server, see My Oracle Support note 1063762.1. For more information, downloads, demos, access the following URL:
http://www.oracle.com/technology/products/weblogic/index.html
Oracle WebLogic Server Patch Requirements
Ensure that you apply patch ID WDJ7 on Oracle WebLogic Server using the Oracle Smart Update utility. This patch fixes bugs 8990616, 9100465, and 9221722.
For information on applying this patch, see My Oracle Support note 1072763.1.
For information on Oracle Smart Update utility, see Oracle Smart Update Installing Patches and Maintenance Packs documentation available at:
Existing Database Version Requirements
Ensure that the existing, certified Oracle Database is one of the databases listed in My Oracle Support note 412431.1. The database can reside either on the host where you are installing the product or on a remote host.
(Optional) If you are installing using Oracle Database 11g Release 1 (11.1.0.7.0), then ensure that you apply the patch for bug# 9066130.
(Optional) If you are installing using Oracle Database 11g Release 2 (11.2.0.1.0), then ensure that you apply the patch for bug# 9002336 and 9067282.
Note: For information about these patches and their availability for different platforms, see My Oracle Support note 1073166.1.
Existing Database Requirements
After configuring database below configurations need to be done at database level.
Existing Database Not to Be in QUIESCE Mode
Existing Database Not to Have Database Control
Existing Database Not to Have SYSMAN and SYSMAN_MDS Schema
Database Initialization Parameters Requirements
Fine-Grained Access Control Requirements
UNDO Tablespace Size Requirements
UNDO Tablespace and Temporary Tablespace Settings Requirements
Archive Logging Settings Requirements
Tablespace-Related Hard Disk Space Requirements
Existing Database Not to Be in QUIESCE Mode
| |||||||||||||||||||||||||||||||||||||||
Ensure that existing, certified Oracle Database is not in QUIESCE mode. To verify this, run the following SQL in the database:
select active_state from v$instance;
| |||||||||||||||||||||||||||||||||||||||
Existing Database Not to Have Database Control
| |||||||||||||||||||||||||||||||||||||||
Ensure that your existing, certified Oracle Database does NOT have Database Control SYSMAN schema. If it has, that is, if your existing database is configured with Database Control, then deconfigure it.
1.Verify whether your database has Database Control SYSMAN schema.
To do so, log in to the database as SYS user and run the following query:
SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN'
If the result of this query is 1, then the database has this schema, so deconfigure it.
2.Before deconfiguring the Database Control, set the environment variable ORACLE_HOME to the Oracle home of the database, and ORACLE_SID to the SID of the database.
For example, in bash shell, you can set them in the following way:
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export ORACLE_SID=orcl
3.Deconfigure the Database Control.
To deconfigure Database Control for a standalone database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.
$<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
To deconfigure Database Control for a Real Application Cluster (RAC) database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.
$<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
Note: If the deconfigure operation hangs, then refer to My Oracle Support note 375946.1.
| |||||||||||||||||||||||||||||||||||||||
Existing Database Not to Have SYSMAN and SYSMAN_MDS Schema
| |||||||||||||||||||||||||||||||||||||||
Ensure that your existing, certified Oracle Database does NOT have Database Control SYSMAN schema. If it has, that is, if your existing database is configured with Database Control, then deconfigure it.
1.Verify whether your database has Database Control SYSMAN schema.
To do so, log in to the database as SYS user and run the following query:
SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN'
If the result of this query is 1, then the database has this schema, so deconfigure it.
2.Before deconfiguring the Database Control, set the environment variable ORACLE_HOME to the Oracle home of the database, and ORACLE_SID to the SID of the database.
For example, in bash shell, you can set them in the following way:
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export ORACLE_SID=orcl
3.Deconfigure the Database Control.
To deconfigure Database Control for a standalone database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.
$<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
To deconfigure Database Control for a Real Application Cluster (RAC) database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.
$<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
Note: If the deconfigure operation hangs, then refer to My Oracle Support note 375946.1.
| |||||||||||||||||||||||||||||||||||||||
Database Initialization Parameters Requirements
| |||||||||||||||||||||||||||||||||||||||
Ensure that you have correctly set the database initialization parameters for the existing, certified Oracle Database so that the Management Repository can be created.
| |||||||||||||||||||||||||||||||||||||||
Fine-Grained Access Control Requirements
| |||||||||||||||||||||||||||||||||||||||
Ensure that the fine-grained access control option is set to TRUE in the existing, certified Oracle Database so that the Management Repository can be created. To verify this, run the following command:
select value from v$option where parameter = 'Fine-grained access control';
| |||||||||||||||||||||||||||||||||||||||
UNDO Tablespace Size Requirements
| |||||||||||||||||||||||||||||||||||||||
Ensure that the UNDO tablespace has a minimum space of 200 MB. To verify this, run the following query:
SELECT SUM(DECODE(autoextensible,'YES',200*1024*1024+1,bytes)) total
FROM dba_data_files f, dba_tablespaces s
WHERE s.contents = 'UNDO'
AND s.tablespace_name = f.tablespace_name;
Note: The result of this query is in bytes.
If the minimum space is less than 200 MB, then set it to 200 MB by running the following command:
alter database datafile <location datafile> resize 200M;
| |||||||||||||||||||||||||||||||||||||||
UNDO Tablespace and Temporary Tablespace Settings Requirements
| |||||||||||||||||||||||||||||||||||||||
Ensure that the UNDO tablespace and the TEMP tablespace are autoextensible in the existing, certified Oracle Database. To verify this, run the following command:
select count(*) from dba_temp_files where tablespace_name='TEMP' and AUTOEXTENSIBLE <> 'YES';
select count(*) from dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE <> 'YES';
If the result of the query is 0, then the tablespace is autoextensible. If the result it not 0, then refer to Oracle Database Administrator's Guide available in the following location to make the tablespace autoextensible.
| |||||||||||||||||||||||||||||||||||||||
Archive Logging Settings Requirements
| |||||||||||||||||||||||||||||||||||||||
(Recommended) Ensure that you turn on archive logging in the existing, certified Oracle Database for any environment where continuity of data is important. To verify this, run the following command:
select log_mode from v$database;
| |||||||||||||||||||||||||||||||||||||||
Tablespace-Related Hard Disk Space Requirements
| |||||||||||||||||||||||||||||||||||||||
Ensure that you allocate a minimum of 1 GB hard disk space for the following tablespaces:
•Management Tablespace (mgmt.dbf)
•Configuration Data Tablespace (mgmt_ecm_depot1.dbf)
•JVM Diagnostics Data Tablespace (mgmt_ad4j.dbf)
Oracle also recommends that you keep the auto-extend feature enabled for the tablespace data files.
Note that the space requirement increases as the number of monitored targets increase, along with the input/output performance demands on the storage devices.
| |||||||||||||||||||||||||||||||||||||||
Host File Requirements
Ensure that the host name specified in the /etc/hosts file is unique, and ensure that it maps to the correct IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page.
The recommended format of the /etc/hosts file is <ip> <fully_qualified_host_name> <short_host_name>.
For example,
141.81.5.71 ost1.foo.com host1
Installation Process
To configure Grid Control, following path of installation is adopted (as recommended)
1) Install Oracle 11g R2 (11.2.0.1) Database Software
2) Apply apply the patch”9736835” for bug# 9002336 and 9067282.
3) Create Database (GRIDDB.ctd.com) for repository
4) Configure required prerequisites on Database
5) Install SUN JDK 1.6.0_23
6) Install Weblogic Server 10.3.2 (Oracle Fusion Middleware 11g Release1 Patch Set 1)
7) Apply patch ID WDJ7 on Oracle WebLogic Server. Refer My Oracle Support note 1072763.1.
8) Install Oracle Enterprise Manager Grid Control
9) Install Grid Control Agents on Desired Targets
Repository Database GRIDDB Configuration
For Oracle EM Grid Control OMS repository requirements a database GRIDDB is configured. Below are configuration details are listed
Oracle Software Installation
Install Oracle 11g R2 (11.2.0.1) Database Software is installed for GRIDDB Database on GRIDCTL (172.30.30.240) Server.
Oracle Database version: 11.2.0.1
Oracle Inventory: C:\Program Files\Oracle\Inventory
Oracle Database Home Path: D:\oracle\product\11.2.0\db_home
Patches: 9736835
Patch 9736835 Installation on 11.2.0.1 Database Software
F:\p9736835>set ORACLE_HOME=D:\oracle\product\11.2.0\db_home
F:\p9736835>set ORACLE_HOME=D:\oracle\product\11.2.0\db_home
F:\p9736835>cd F:\p9736835\9736835
F:\p9736835\9736835>
F:\p9736835\9736835>
F:\p9736835\9736835>set ORACLE_HOME=D:\oracle\product\11.2.0\db_home
F:\p9736835\9736835>f:\OPatch\opatch apply
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation. All rights reserved.
Oracle Home : D:\oracle\product\11.2.0\db_home
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.2.0.1.3
OUI version : 11.2.0.1.0
OUI location : D:\oracle\product\11.2.0\db_home\oui
Log file location : D:\oracle\product\11.2.0\db_home\cfgtoollogs\opatch\opatch2011-05-20_17-02-35PM.log
Patch history file: D:\oracle\product\11.2.0\db_home\cfgtoollogs\opatch\opatch_history.txt
ApplySession applying interim patch '9736835' to OH 'D:\oracle\product\11.2.0\db_home'
Running prerequisite checks...
Prerequisite check "CheckActiveFilesAndExecutables" failed.
The details are:
Following files are active :
D:\oracle\product\11.2.0\db_home\bin\orageneric11.dll
D:\oracle\product\11.2.0\db_home\bin\oraclient11.dll
D:\oracle\product\11.2.0\db_home\bin\orapls11.dll
D:\oracle\product\11.2.0\db_home\bin\oraxml11.dll
D:\oracle\product\11.2.0\db_home\bin\oranhost11.dll
ApplySession failed during prerequisite checks: Prerequisite check "CheckActiveFilesAndExecutables" failed.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code = 74
F:\p9736835\9736835>f:\OPatch\opatch apply
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation. All rights reserved.
Oracle Home : D:\oracle\product\11.2.0\db_home
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.2.0.1.3
OUI version : 11.2.0.1.0
OUI location : D:\oracle\product\11.2.0\db_home\oui
Log file location : D:\oracle\product\11.2.0\db_home\cfgtoollogs\opatch\opatch2011-05-20_17-05-42PM.log
Patch history file: D:\oracle\product\11.2.0\db_home\cfgtoollogs\opatch\opatch_history.txt
ApplySession applying interim patch '9736835' to OH 'D:\oracle\product\11.2.0\db_home'
Running prerequisite checks...
Patch 9736835: Optional component(s) missing : [ oracle.ntoledb.odp_net_1, 11.2.0.1.0 ]
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = 'D:\oracle\product\11.2.0\db_home')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '9736835' for restore. This might take a while...
Backing up files affected by the patch '9736835' for rollback. This might take a while...
Execution of 'cmd /C "F:\p9736835\9736835\custom\scripts\pre.bat" -apply 9736835 ':
Return Code = 0
Patching component oracle.rdbms.rsf, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\bin\orageneric11.dll"
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\admin\orageneric11.sym"
Copying file to "D:\oracle\product\11.2.0\db_home\bin\oraclient11.dll"
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\admin\oraclient11.sym"
Copying file to "D:\oracle\product\11.2.0\db_home\bin\orapls11.dll"
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\admin\orapls11.sym"
Copying file to "D:\oracle\product\11.2.0\db_home\bin\oraimr11.dll"
Patching component oracle.rdbms, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\Bundle\Patch2\catcpu.sql"
Copying file to "D:\oracle\product\11.2.0\db_home\Bundle\Patch2\catcpu_rollback.sql"
Copying file to "D:\oracle\product\11.2.0\db_home\Bundle\Patch2\bug8856467.sql"
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\admin\bundledata_WINBUNDLE.xml"
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\xml\xsl\kustat.xsl"
Copying file to "D:\oracle\product\11.2.0\db_home\bin\oracle.exe"
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\admin\oracle.sym"
Patching component oracle.rdbms.util, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\bin\tkprof.exe"
Patching component oracle.rdbms.dbscripts, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\rdbms\admin\catmeta.sql"
Patching component oracle.rdbms.plsql, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\lib\orapls11.lib"
Patching component oracle.xdk.rsf, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\bin\oraxml11.dll"
Copying file to "D:\oracle\product\11.2.0\db_home\lib\oraxml11.lib"
Patching component oracle.network.rsf, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\bin\oranhost11.dll"
Patching component oracle.oraolap, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\olap\admin\xumuts.plb"
Patching component oracle.ntoledb.odp_net_2, 11.2.0.1.0...
Copying file to "D:\oracle\product\11.2.0\db_home\bin\OraOps11w.dll"
Copying file to "D:\oracle\product\11.2.0\db_home\odp.net\bin\2.x\Oracle.DataAccess.dll"
ApplySession adding interim patch '9736835' to inventory
Verifying the update...
Inventory check OK: Patch ID 9736835 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 9736835 are present in Oracle Home.
Execution of 'cmd /C "F:\p9736835\9736835\custom\scripts\post.bat" -apply 9736835 ':
Return Code = 0
The local system has been patched and can be restarted.
OPatch succeeded.
F:\p9736835\9736835>
Listener Configuration
As part of installation process, prior to Database Creation listeners need to be created. Below listeners are created for test database servers.
Listener Name
|
Port Running
|
Registered Instances
|
LISTENER_GRIDDB
|
3333
|
GRIDDB
|
GRIDDB Database Configuration
The configuration details are given below
Configuration
|
Status
|
Database Version
|
11.2.0.1
|
Database Home Path
|
D:\oracle\product\10.2.0\db_home
|
Global Database Name
|
GRIDDB.ctd.com
|
Database ID
|
2177093354
|
SGA+PGA
|
500 MB
|
Redo Log file size
|
50 MB
|
Database Character Set
|
WE8MSWIN1252
|
Connection Mode
|
Dedicated
|
Service Available Port
|
3333
|
Service Available Listener
|
LISTENER_GRIDDB
|
Archive Log Mode
|
Disabled
|
Initialization Parameters
After many configuration changes, GRIDDB Database initialization parameters are finalized and implemented for grid control implementation.
Initialization Parameters
| |
griddb.__db_cache_size=192937984
griddb.__java_pool_size=4194304
griddb.__large_pool_size=4194304
griddb.__oracle_base='D:\oracle\product\11.2.0'#ORACLE_BASE set from environment
griddb.__pga_aggregate_target=209715200
griddb.__sga_target=524288000
griddb.__shared_io_pool_size=0
griddb.__shared_pool_size=301989888
griddb.__streams_pool_size=4194304
*.audit_file_dest='D:\oracle\product\11.2.0\admin\GRIDDB\adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='D:\oracle\oradata\GRIDDB\control01.ctl','D:\oracle\product\11.2.0\flash_recovery_area\GRIDDB\control02.ctl'
*.db_block_size=8192
*.db_domain='ctd.com'
*.db_name='GRIDDB'
*.db_recovery_file_dest='D:\oracle\product\11.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=5218762752
*.diagnostic_dest='D:\oracle\product\11.2.0'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=GRIDDBXDB)'
*.job_queue_processes=0
griddb.job_queue_processes=1000
*.local_listener='LISTENER_GRIDDB'
*.log_archive_dest_1='LOCATION=D:\oracle\ArchiveLog\GRIDDB'
*.log_archive_format='ARC%S_%R_%T.ARCH'
*.log_buffer=10485790
*.open_cursors=350
*.pga_aggregate_target=209715200
*.processes=500
*.remote_login_passwordfile='EXCLUSIVE'
*.session_cached_cursors=250
*.sga_target=524288000
*.undo_tablespace='UNDOTBS1'
| |
Weblogic Server Configuration
As part of grid control installation process Web logic Server 10.3.2 (Oracle Fusion Middleware 11g Release1 Patch Set 1) is mandatory for middleware requirements. Web logic server is installed in “GRIDCTL” (172.30.30.240) server
Middleware Home: D:\oracle\product\11.1.0\Middleware
SUN JDK Installed Location: C:\Java\jdk1.6.0_23
Web logic Server: D:\oracle\product\11.1.0\Middleware\Weblogic10.3
Patch ID WDJ7 Installation
Followed instructions in Metalink Doc id: 1072763.1 for Patch WDJ7 installation
Patch Installation
| |
D:\>cd D:\oracle\product\11.1.0\Middleware\utils\bsu
D:\oracle\product\11.1.0\Middleware\utils\bsu>bsu.cmd -prod_dir=D:\oracle\product\11.1.0\Middleware\Weblogic10.3 -patchlist=WDJ7 -verbose install
Encountered unrecognized argument: install
"prod_dir" is not a valid option for "[gui]"
"patchlist" is not a valid option for "[gui]"
"verbose" is not a valid option for "[gui]"
-help Displays this usage message. REQUIRED
-version Displays version information.
-view View information about applied or downloaded patches. REQUIRED
-profile The name of the profile to utilize.
-patch_download_dir The location of the patch cache directory.
-status Specifies installation status when using the view option. (applied|downloaded) REQUIRED
-verbose Display verbose output
-prod_dir The product installation directory. REQUIRED
-report Generate a report of patches applied in a BEA home. REQUIRED
-bea_home BEA Home to use.
-product_mask [regexp] Restrict report to a matching product(s).
-release_mask [regexp] Restrict report to a matching product release(s).
-profile_mask [regexp] Restrict report to a matching profile(s).
-patch_id_mask [regexp] Restrict report to a matching patch(es).
-output_format Output format. (text|xml)
-output_file Output file (stdout will be used if not specified)
-install Install a patch. REQUIRED
-patchlist The list of patches. REQUIRED
-profile The name of the profile to utilize.
-patch_download_dir The location of the patch cache directory.
-verbose Display verbose output
-prod_dir The product installation directory. REQUIRED
-remove Remove a patch. REQUIRED
-patchlist The list of patches. REQUIRED
-profile The name of the profile to utilize.
-verbose Display verbose output
-prod_dir The product installation directory. REQUIRED
-gui Runs GUI mode. DEFAULT
-log The path to the log file.
-log_priority The log priority. (trace|debug|info|warn|error|fatal)
D:\oracle\product\11.1.0\Middleware\utils\bsu>bsu.cmd -prod_dir=D:\oracle\product\11.1.0\Middleware\Weblogic10.3 -patchlist=WDJ7 -verbose -install
Encountered unrecognized patch ID: WDJ7
D:\oracle\product\11.1.0\Middleware\utils\bsu>bsu.cmd -prod_dir=D:\oracle\product\11.1.0\Middleware\Weblogic10.3 -patchlist=WDJ7 -verbose -install
Encountered unrecognized patch ID: WDJ7
D:\oracle\product\11.1.0\Middleware\utils\bsu>bsu.cmd -prod_dir=D:\oracle\product\11.1.0\Middleware\Weblogic10.3 -patchlist=WDJ7 -verbose -install
Checking for conflicts..
No conflict(s) detected
Installing Patch Set ID: WDJ7
Starting installation of Patch ID: XLXA
Installing D:\oracle\product\11.1.0\Middleware\utils\bsu\cache_dir\XLXA.jar
Extracting D:\oracle\product\11.1.0\Middleware\patch_wls1032\patch_jars\Bug9221722_1032.jar
Updating D:\oracle\product\11.1.0\Middleware\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar
Old manifest value: Class-Path=
New manifest value: Class-Path=../../../patch_jars/Bug9221722_1032.jar
Result: Success
Starting installation of Patch ID: 4D53
Installing D:\oracle\product\11.1.0\Middleware\utils\bsu\cache_dir\4D53.jar
Extracting D:\oracle\product\11.1.0\Middleware\patch_wls1032\patch_jars\Bug9100465_1032.jar
Updating D:\oracle\product\11.1.0\Middleware\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar
Old manifest value: Class-Path=../../../patch_jars/Bug9221722_1032.jar
New manifest value: Class-Path=../../../patch_jars/Bug9100465_1032.jar ../../../patch_jars/Bug9221722_1032.jar
Result: Success
Starting installation of Patch ID: NIXN
Installing D:\oracle\product\11.1.0\Middleware\utils\bsu\cache_dir\NIXN.jar
Extracting D:\oracle\product\11.1.0\Middleware\patch_wls1032\patch_jars\bug8990616_1032.jar
Updating D:\oracle\product\11.1.0\Middleware\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar
Old manifest value: Class-Path=../../../patch_jars/Bug9100465_1032.jar ../../../patch_jars/Bug9221722_1032.jar
New manifest value: Class-Path=../../../patch_jars/bug8990616_1032.jar ../../../patch_jars/Bug9100465_1032.jar ../../../patch_jars/Bug9221722_1032.jar
Result: Success
D:\oracle\product\11.1.0\Middleware\utils\bsu>
| |
Grid Control Installation
As part of grid control installation process prerequisites of installing Web logic Server 10.3.2 (Oracle Fusion Middleware 11g Release1 Patch Set 1) and repository hosting database “GRIDDB” installed in “GRIDCTL” (172.30.30.240) server.
Using this existing infrastructure Grid control is installed with options existing middleware and database options.
Middleware Home Used: D:\oracle\product\11.1.0\Middleware
Database Used: GRIDDB.ctd.com
Grid Control URL: https://172.30.30.240:7799/em
This information is also available at:
D:\oracle\product\11.1.0\Middleware\oms11g\install\setupinfo.txt
See below for information pertaining to your Enterprise Manager installation:
Use the following URL to access:
1. Enterprise Manager Grid Control URL: https://GRIDCTL:7799/em
2. Admin Server URL: https://GRIDCTL:7101/console
The following details need to be provided during the additional OMS install:
1. Admin Server Hostname: GRIDCTL
2. Admin Server Port: 7101
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. Please run following command to backup the Management Service configuration including the emkey and keep the backup on another system:
emctl exportconfig oms -dir <backup location>
Agent Installation
As part of grid control installation process agent installation is the final stem to configured desired target to administrate through grid control,
Modified Response File
| |
RESPONSEFILE_VERSION=2.2.1.0.0
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=true
#MYORACLESUPPORT_USERNAME=<Value Unspecified>
#MYORACLESUPPORT_PASSWORD=<Value Unspecified>
#COLLECTOR_SUPPORTHUB_URL=<Value Unspecified>
INSTALL_UPDATES_SELECTION="skip"
STAGE_LOCATION=<Value Unspecified>
ORACLE_AGENT_HOME_LOCATION=D:\oracle\product\11.1.0\gridctl_agent_home
DEINSTALL_LIST={"oracle.sysman.top.agent","11.1.0.1.0"}
b_silentInstall=true
TOPLEVEL_COMPONENT={"oracle.sysman.top.agent","11.1.0.1.0"}
SELECTED_LANGUAGES={"en"}
COMPONENT_LANGUAGES={"en"}
#-------------------------------------------------------------------------------
#OMS_HOST:<String> OMS host info required to connect to OMS
#OMS_PORT:<String> OMS port info required to connect to OMS
#AGENT_REGISTRATION_PASSWORD:<String> Agent Registration Password needed to
# establish a secure connection to the OMS.
#-------------------------------------------------------------------------------
OMS_HOST=172.30.30.240
OMS_PORT=4889
AGENT_REGISTRATION_PASSWORD=hcl12345
s_agentSrvcName="OracleGridCtlAgent11g"
####################################################################################
#Please Don't change the values of these variables
####################################################################################
#-------------------------------------------------------------------------------
#FROM_LOCATION:<String> Complete path to the products.xml.
#b_upgrade:<Boolean> "whether it is Upgrade or not"
#EM_INSTALL_TYPE:<STRING> install type
#-------------------------------------------------------------------------------
FROM_LOCATION="../stage/products.xml"
b_upgrade=false
EM_INSTALL_TYPE="AGENT"
| |
Installation
| |
Installation and Configuration Issues
While installing and after installing grid control I face configuration issues, to resolve that I have changed some configurations with the help of taken help from oracle support. In this sub section I mentioned what are all issues I faced while configuring GRID control.
Below table lists major issues I faced while and after configuring Grid Control
1
|
On Solaris 10.2.0.4 listener is showing status Down in EM Grid Control even though it is actually running and status confirmed via lsnrctl status command.
|
Issues Statue :
Issues Encountered and Fixed
Issue/Problem :
10.2.0.4 listener is showing status Down in EM Grid Control even though it is actually running and status confirmed via lsnrctl status command. The error message seen in Grid Control console is:
“The listener is down: Failed to tnsping LISTENER_VATMSTRDR”
Metalink Source:
This is documented on Metalink as :
Bug 10070623: STATUS DOWN FOR LISTENER 10.2 MANAGED BY AGENT 11G
Solution:
The fix for this was to edit the emctl executable which is located in the AGENT_HOME/bin directory.
Stop the agent via the emctl stop agent command
Take a backup of the emctl file and change the following lines
LD_PRELOAD_64=$UMEMLOC:${LD_PRELOAD_64}
export LD_PRELOAD_64
To
if [ "$LD_PRELOAD_64" = "" ] ; then
LD_PRELOAD_64=$UMEMLOC
else
LD_PRELOAD_64=$UMEMLOC:${LD_PRELOAD_64}
fi
export LD_PRELOAD_64
Start the agent.
Check the status of the Oracle 10.2.0.4 listener. It should now show as up!
|
2
|
Agent Auto Start in Unix failed
|
Agent Auto Start in Unix failed
| |
Issues Statue :
Issues Encountered and Fixed
Issue/Problem :
After system reboot grid agent auto restart failed,
Oracle Support Source:
Created SR: id
But no solution by Oracle Support
Root Cause:
1) No unix sudo pacakages available
2) Problem with "/etc/init.d/gcstartup" and “$ORACLE_HOME(AGENT_HOME)/install/unix/scripts/agentstup” scripts
Solution:
1) Installed sudo packages on “appserver3,”dbserver1”, “dbserver2”, and “dbserver3”
2) edit "/etc/init.d/gcstartup"
In 10.2.0.5:
Change----> /bin/su - vat10gas -c "/app/vat10gas/oracle/product/11.1.0/gridctl/agent10g/install/unix/scripts/agentstup $1"
to-------> /app/vat10gas/oracle/product/11.1.0/gridctl/agent10g/install/unix/scripts/agentstup $1
in 11.1.0.1
change---->$SU - $user -c "$i/install/unix/scripts/agentstup $1";
to-----> $i/install/unix/scripts/agentstup $1;
3) edit "$ORACLE_HOME(AGENT_HOME)/install/unix/scripts/agentstup"
change---->executingUser=$USER
to----->executingUser=`/usr/xpg4/bin/id -un`
| |
3
|
Data guard ,Transport and apply lag of logical standby database is showing Null
|
Data guard ,Transport and apply lag of logical standby database is showing Null
| |
Issues Statue :
Issues Encountered and Fixed
Issue/Problem :
Data guard ,Transport and apply lag time of logical standby database is showing Null
Oracle Support Source:
Created SR:
Solution Provided by Oracle Support
Root Cause:
1) Because of Bug on Database Level
2) V$DATAGUARD_STATS have null values in logical standby
3) Bugs: 5673525, 7363939, 6874522
Solution:
Installed RDBMS Patch 6874522 on Production and Standby Database Software
| |
No comments:
Post a Comment