Database Reference
In-Depth Information
1.6 when it all goes wrong
over the life of complex systems or during times of large change, such as an upgrade,
you may find you need help diagnosing issues. This section highlights several very use-
ful tools that may be used in a variety of problem analysis situations (table 1.14). When
diagnosing a problem, I suggest: reviewing the log files, using any tools that seem to
make sense for the given situation, and, after you have exhausted your knowledge and/
or patience, logging a support case with the appropriate vendor.
1.6.1 Troubleshooting Tools and Tuning Documents
If you are in any type of infrastructure role, I hope the below utilities are familiar to you
(table 1.15). If not, check them out and, hopefully, you find them as useful as I do.
The resources in table 1.16 provide further information on specific platforms and/or
tuning.
1.7 aDDitional Deployment ConsiDer ations
1.7.1 Supported Sotware
In order to qualify for support from your software vendors, you must use a supported
operating system. oracle maintains a certification matrix that documents the operating
systems and other supporting software both on server and client.
Table 1.14 Troubleshooting Steps
Major Version
Symptom
Recommended Action
ALL
Essbase does not start
1. Check disk space on application and data drives
2. review hyperion log files
3. review operating system log files and/or windows
event viewer
4. versions 9-11.1.1 Confirm Shared Services and
openLDAP are started; assumes you are using
Shared Services security
ALL
Application does
not start
1. Check disk space on application and data drives
2. review hyperion log files
3. Confirm no other ESSSvr processes are running for
specific application name
4. Confirm that no third-party backup process has
application files locked
5. Cycle machine if 3 and 4 are not issues
6. If cycling machine does not work, you likely have a
corrupted database
7. Confirm you have a good backup before proceeding
with this step. remove the following type of files
from your database directories: *.ind, *.pag, *.esm,
*.tct. next start the database, then restore and
calculate your data
ALL
Corrupt security file
1. Essbase.log file says your security file is corrupted
2. Locate last backup of the file (ideally from previous
night), restore and restart Essbase
Search WWH ::




Custom Search