Grid Control Agent无法配置成功的案例分享
最近在做GC的实验,在GC服务器上软件都顺利安装成功,OMS和自己上面的AGENT也都能够顺利启动,但是就是DB服务器的agent死活配置不
DB服务器:
[root@ocm1 ~]# su - oracle
[oracle@ocm1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sat Jan 10 09:57:00 2015
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SYS@PROD> startup
ORACLE instance started.
Total System Global Area 314572800 bytes
Fixed Size 2020480 bytes
Variable Size 96471936 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
Database mounted.
Database opened.
SYS@PROD> !
[oracle@ocm1 ~]$ emctl status agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
[oracle@ocm1 ~]$ emctl reload agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent is Not Running
[oracle@ocm1 ~]$ emctl start agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Starting agent ................................. failed.
Consult the log files in: /u01/app/oracle/agent10g/sysman/log
[oracle@ocm1 ~]$ cd /u01/app/oracle/agent10g/sysman/log
[oracle@ocm1 log]$ ll -lrth
total 28K
-rw-r----- 1 oracle oinstall 0 Jan 7 21:07 nfsPatchPlug.log
-rw-r----- 1 oracle oinstall 448 Jan 9 22:26 secure.log
-rw-r----- 1 oracle oinstall 462 Jan 10 09:57 agabend.log
-rw-r----- 1 oracle oinstall 5.0K Jan 10 09:57 emagent.nohup
-rw-r----- 1 oracle oinstall 11K Jan 10 09:58 emctl.log
[oracle@ocm1 log]$ tail -10 agabend.log
Fri Jan 9 21:42:53 2015
XXXXXXXXXXXXXXXX
Fri Jan 9 22:58:32 2015
XXXXXXXXXXXXXXXX
Fri Jan 9 23:00:38 2015
XXXXXXXXXXXXXXXX
Sat Jan 10 09:46:11 2015
XXXXXXXXXXXXXXXX
Sat Jan 10 09:57:55 2015
XXXXXXXXXXXXXXXX
[oracle@ocm1 log]$ tail -10 emagent.nohup
----- Sat Jan 10 09:46:15 2015::EMAgent exited at Sat Jan 10 09:46:15 2015 with return value 0. -----
----- Sat Jan 10 09:46:15 2015::EMAgent was shutdown normally. -----
----- Sat Jan 10 09:46:15 2015::Exiting watchdog loop
-----
----- Sat Jan 10 09:57:55 2015::Agent Launched with PID 4935 at time Sat Jan 10 09:57:55 2015 -----
----- Sat Jan 10 09:57:58 2015::Checking status of EMAgent : 4935 -----
----- Sat Jan 10 09:57:58 2015::EMAgent exited at Sat Jan 10 09:57:58 2015 with return value 0. -----
----- Sat Jan 10 09:57:58 2015::EMAgent was shutdown normally. -----
----- Sat Jan 10 09:57:58 2015::Exiting watchdog loop
-----
[oracle@ocm1 log]$ tail -10 emctl.log
4025 :: Sat Jan 10 09:57:37 2015::AgentStatus.pm:Abnormal exit code.
4456 :: Sat Jan 10 09:57:48 2015::AgentLifeCycle.pm: Processing reload agent
4456 :: Sat Jan 10 09:57:48 2015::AgentStatus.pm:Processing reload agent
4456 :: Sat Jan 10 09:57:48 2015::AgentStatus.pm:emdctl status agent returned 0
4456 :: Sat Jan 10 09:57:48 2015::AgentStatus.pm:Agent is not running. Just doing encrypt
4892 :: Sat Jan 10 09:57:55 2015::AgentLifeCycle.pm: Processing start agent
4892 :: Sat Jan 10 09:57:55 2015::AgentLifeCycle.pm: EMHOME is /u01/app/oracle/agent10g
4892 :: Sat Jan 10 09:57:55 2015::AgentLifeCycle.pm:status agent returned with retCode=0
4892 :: Sat Jan 10 09:57:59 2015::AgentLifeCycle.pm:Watch dog processs id: 4914 exited with an exit code of 0
4892 :: Sat Jan 10 09:58:25 2015::AgentLifeCycle.pm: Exited loop with retCode=0
没有发现什么有价值的信息,于是查看make.log,这里记录着软件安装时候的编译记录
[oracle@ocm1 log]$ pwd
/u01/app/oracle/agent10g/sysman/log
[oracle@ocm1 log]$ cd ../../install
[oracle@ocm1 install]$ ll -lrth
total 40K
drwxr-x--- 2 oracle oinstall 4.0K Jan 7 21:06 utl
drwxr-x--- 3 oracle oinstall 4.0K Jan 7 21:06 oneoffs
-rw-r--r-- 1 oracle oinstall 12K Jan 7 21:06 make.log
drwxr-x--- 3 oracle oinstall 4.0K Jan 7 21:06 unix
-rw-r----- 1 oracle oinstall 784 Jan 7 21:06 envVars.properties
-rw-r--r-- 1 oracle oinstall 107 Jan 7 21:06 readme.txt
-rw-r----- 1 oracle oinstall 87 Jan 7 21:06 portlist.ini
drwxr-x--- 2 oracle oinstall 4.0K Jan 7 21:07 chainedInstall
[oracle@ocm1 install]$ tail -10 make.log
make: *** [/u01/app/oracle/agent10g/rdbms/lib/rman] Error 1

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
