The eG manager configuration failed. What could have contributed to this?
Make sure that the database instance you specified is valid. Connect from the “sqlplus” prompt using the database administrator user name and password to make sure that the database instance is up.
Make sure that the database instance can be reached from the eG manager system (e.g., firewalls between the manager and the database could result in database connection problems)
Check that the tablespaces specified when creating a new user are valid.
Ensure that the tablespaces specified have enough space to host the eG database tables.
I have the eG manager working. Now, I have shifted my database to another server. Can I reconfigure the manager to work with the new database?
Information regarding the eG manager’s database connection is maintained in the file <EG_HOME_DIR>/manager/config/eg_db.ini. By editing this file, you can modify the database that the eG manager will use.
My eG manager is using an Oracle backend. Lately, my manager is experiencing a lot of connection issues. When I checked the manager tomcat debug file, I found the following error message: “
java.sql.SQLException: OALL8 is in an inconsistent state
”. What is the reason for this error, and how do I resolve the connection issues that have surfaced as a result?
This error message appears when there is a JDBC driver mismatch - i.e., when the JDBC driver bundled with the eG manager is not compatible with the JDBC driver of the Oracle database that is in use in the monitored environment.
To resolve this issue, do the following:
Take a backup of the JDBC driver that is bundled with the eG manager, from the <EG_INSTALL_DIR>\lib folder.
Download the latest release of the JDBC driver that is compatible with the version of the Oracle database server that is in use in your environment, using the link: http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
Rename the downloaded driver as
classes12.zip
in case of Windows, or as
classes11.zip
in case of the Unix manager.
Copy the renamed file to the <EG_INSTALL_DIR>\lib directory (in case of the Windows manager), or the
/opt/egurkha/lib
directory in case of the Unix manager.
Restart the eG manager.
How do I change the eG manager’s port?
Stop the eG manager.
Look for the script
start_manager.bat
in the
<EG_HOME_DIR>\lib
directory, and modify the port there, but do not run the script.
Next, proceed to change the
egurkha
web site’s port. To do so, first, go into the Windows Internet Service Manager (Start -> Programs -> Administrative Tools -> Internet Information Services (IIS) Manager).
In the
Internet Information Services
window that appears, right-click on the manager host and select
Properties
from the shortcut menu.
From the
Master Properties
list box therein, select the
egurkha
web site and then, click the
Edit
button alongside it to edit its properties.
Upon clicking, a
WWW Service Master Properties
dialog box will appear. The
Web Site
tab of the dialog box will open, by default. Change the
TCP Port
entry in that tab, so as to make the eG manager listen to the new port.
Similarly, you need to reconfigure all agents (manually) to talk to the manager using the new port. You can do this by editing the
debugoff
script (Windows) in the <EG_HOME_DIR>\lib directory, or
start_agent
script file (UNIX) in the same directory.
Search for port 7077 and replace it with your port number. Save the file and run the script file. Restart the agent and check if it is talking to the new port.
eG Innovations, Inc.,
33 Wood Ave. South, Suite 600, Iselin,
NJ 08830, USA
Phone: +1 (866) 526 6700
eG Innovations B.V.,
WTC, Den Haag, Prinses Margrietplantsoen 33,
2595 AM Den Haag,
The Netherlands
Phone: +31 (0)70-2055210
