Database Reference
In-Depth Information
Chapter 6. Troubleshooting the
Oracle SOA Suite 11g Infrastructure
It is almost a guarantee that administrators of Oracle SOA Suite 11g will have a
need to continuously address issues within the infrastructure. Sometimes deve-
lopers may report deployment issues in the non-production environments. Other
times, the administrator may get an automated alert regarding an infrastructure
failure. In many cases, the root causes of these issues are clear. For example, if a
composite instance that inserts a record to a database fails with an
ORA-12541
,
that is quite straightforward, as the error indicates that the database listener is
unreachable. Simply starting up the listener should resolve this problem.
However, there are many cases where the error thrown requires a deeper level
of troubleshooting to resolve. For example, if an SOA managed server crashes or
crashes frequently, this is obviously not normal behavior and a root cause needs
to be identified. Is it because the JVM ran out of memory? Or is it due to corrup-
tion in the persistent stores? Even if it is confirmed that an
OutOfMemoryError
exception is found in the logs, why did this happen?
The four core problem areas an Oracle SOA Suite
11g
admin-
istrator will often troubleshoot revolve around infrastructure,
code deployment, performance, and composite instances.
There is no step-by-step guide that walks through exactly what to do in every
scenario, as the types of errors you may encounter are endless. However, this
chapter will address the four core troubleshooting areas to provide a guideline
on what you should consider for your troubleshooting strategies. These are infra-
structure, code deployment, performance, and composite instance errors.
