Owners Manual

Troubleshooting Your Application | Troubleshooting
692 OMNM 6.5.2 User Guide
3. Modify
oware.appserver.ip property in file [installation
root]\oware\synergytomcat-x.x.x/webapps/ROOT/WEB-INF/classes/
portal-ext.properties
.
4. Verify the file does not specify the old IP anywhere else. If it does, replace
with new IP address and save.
5. Next, modify the IP address in any shortcut URL properties and click OK.
[installation root]\oware\synergy\tomcat-x.x.xx\bin\portal.url
(Web Document tab)
6. Type
ipaddresschange -n <new IP address> in a command prompt/shell.
7. Restart application and web server.
• Ensure any other of the application’s installation(s) have been completely removed, if you
have uninstalled a previous version.
• Make sure no other MySQL databases are installed (some Linux packages include them by
default).
• You must be user with administrator permissions to install.
Standalone Database Installation Problems
• Errors appear after installing a standalone database, even though its connection has been
verified successful using pingdb utility.
Solution: After setting the environment in a shell (Windows: oware , Linux: . /etc/
.dsienv
) Verify the following commands have been run on the application server.
• loaddb (create OpenManage Network Manager database)
•
loaddb -d instead of loaddb if the tablespace has not been created.
•
loaddb -s (create synergy/portal database)
•
dbpostinstall (seed components and resolve database schema changes)
After confirming the above, start the application server and synergy portal after application
server is up/ready.
Install-From Directory
Installation package files must not be in the installation destination directory.
Installer Logs
Installation logs are in $OWARE_INSTALL_ROOT . Log files are setup.log, app_setup.log,
and db_setup.log (this last log does not appear if you install an Oracle database). An empty or
missing
app_setup.log means no applications were installed. This can result from a truncated
owareapps directory name. Solution: Correct the directory name and attempt the installation
again.
Startup Issues
The following are some possible problems with application startup. Remember: after you first
install this application, the application server takes longer to start. Be patient the first time you
start the application.
The two most common reasons for the inability to start an application server which worked
previously are the following: