Database Reference
In-Depth Information
The issue can be resolved by untargeting the
soa-infra
application from all
servers in the cluster, bouncing back all managed servers, and retargeting it
back to the cluster. This is clearly an infrastructure problem.
Infrastructure error—Unable to extend LOB segment
Not all errors are directly due to issues within your SOA infrastructure. All run-
ning and completed instances in Oracle SOA Suite 11g are saved in a backend
datastore. Lack of free space in the database may prevent the composite in-
stances from completing their processing. For instance, you are most likely to
see the following exception if your database runs out of disk space:
oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.BatchUpdateException: ORA-01691: unable to extend lob segment DEV_SOAINFRA.SYS_LOB$$ by 128 in tablespace DEV_SOAINFRA
These messages typically indicate space issues in the database that will likely
require adding more data files or more space to the existing data files. Addition-
ally, completed instances can be purged and disk space can be reclaimed by ex-
ecuting the purge scripts. You will learn more about this in
Chapter 8
,
Managing
the Metadata Services Repository and Dehydration Store
.
We have covered several brands of exceptions that can be encountered to
give you an idea of the types of errors that you might expect. It is impossible
to provide a comprehensive list of errors, and our intent is to show you why
we have classified some errors as infrastructure while others are composite in-
stance ones. Most of the time it is obvious, but other times it is not. Differentiat-
ing between both helps limit your troubleshooting efforts to a particular area.
Using thread dumps
The following screenshot shows a warning on
AdminServer
. Warnings do not
necessarily mean that a server is unresponsive, but are clearly an indication that
you should look into the cause.
