Configuring the eG Manager

1. 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.

2. 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.

3. 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.

4. How do I change the eG manager’s port?

   For this, follow the steps below on a Windows manager:

   • Login to the eG manager host.
   • Stop the eG manager.
   • Go to the command prompt and switch to the <EG_INSTALL_DIR>\lib directory.
   • Run the changeManagerSettings.bat from that directory. This batch file, upon execution, will prompt you to modify the eG manager's port. Type the new port at that prompt.

   • The batch file will then update the eG manager's configuration with the new port.

   To change the port on a Unix manager, do the following:

   • Login to the eG manager host.
   • Stop the eG manager.
   • Go to the Shell prompt and switch to the /opt/egurkha/bin directory.
   • Run the reset_manager script from that directory. This script, upon execution, will prompt you to modify the eG manager's port. Type the new port at that prompt.

   • The script will then update the eG manager's configuration with the new port.