Users Guide
Troubleshooting Your Application | Troubleshooting
710 OMNM 6.5.3 User Guide
• Execute pingdb to test database connectivity.
• Check network interfaces and connectivity between application server and database.
• Try connecting with MySQL Workbench or other tool.
• Verify database is up and healthy.
• Verify database login/password has not changed or expired (default user/password: root/
dorado)
IV “Too Many Connections” Error
. Ironically, this error may indicate the
max_connections
parameter in your
my.cnf
files is too
small
. To use more connections, change the setting in the
my.cnf
file. For example, in
\oware3rd\mysql\X_X_X-64\my.cnf,
under the
[mysqld]
section add:
max_connections = 500
You can login to mysql to check current settings:
mysql -u root --password=dorado
mysql> show variables like 'max_connections';
To check open connections
mysql> SHOW STATUS WHERE `variable_name` = 'Threads_connected';
Oracle Database Issues
Best practice for Oracle database users is to have a database administrator configure their Oracle
application before installing OpenManage Network Manager to use an Oracle database. This
ensures correct configuration, best performance and connection with the database.
Patches
You can patch OCPs or add them new (for new applications, drivers, or features). If you are
installing only a single component, rather that a re-installation with the full installation wizard,
installation is a three-step process:
1
Extract (
ocpinstall -x [filename(s)]
)
2
Optionally, update/verify the database schema (on database servers only). (
ocpinstall -l
[filename(s)]
)
3
Seed the database (on database servers only). (
ocpinstall -s [filename(s)]
)
NOTE:
When using hostname as oracle connection URL, sometime installer may append colon to the URL after
the upgrade. Workaround: remove the colon from the URL in the installed.properties and portal-
ext.properties.
Refer to the
Installation Guide
for more about Oracle databases.
If you are adding jars for patches, turn applications off, rename and move the old jar before you
copy in a new jar. Then delete the contents of
oware/temp.