Agent
receives
an
HTTP
Unauthorized
(401)
response
code
Agent
can
receive
an
Unauthorized
(401)
response
code
for
a
number
of
reasons,
such
as:
v
The
agent
did
not
provide
a
client
certificate
as
part
of
the
SSL
handshake,
which
can
be
caused
by
the
agent
connecting
in
on
the
wrong
port.
The
agent
must
connect
in
on
the
port
which
is
configured
for
SSL
client
authentication.
v
The
client
certificate
provided
as
part
of
the
SSL
handshake
revoked.
Known
report
limitations
The
following
are
known
limitations
for
the
reporting
capabilities
of
the
Tivoli
Intelligent
Orchestrator:
Running
any
report
with
too
many
objects
selected
fails
Running
any
report
with
too
many
objects
selected
generates
the
following
error:
COPJEE389E:
The
report
contains
too
many
objects.
Retry
with
fewer
selections.
Cause
Based
on
the
information
in
the
log
files,
this
error
is
triggered
by
the
following
DB2
Universal
Database
error:
DB2
error
-
SQL0101N
The
statement
is
too
long
or
too
complex.
Two
causes
have
been
identified:
v
The
application
heap
size
and
statement
heap
size
are
not
large
enough
to
process
the
request.
v
The
report
contains
too
many
selected
objects,
which
generates
an
SQL
statement
that
is
too
large
to
be
handled
in
one
single
report.
Solution
1.
Increase
the
Java
memory
to
prevent
your
computer
from
becoming
slow
or
unresponsive.
Increase
the
application
heap
size
and
the
statement
heap
size
incrementally
by
1024,
until
the
problem
is
alleviated.
To
complete
this
task:
a.
Open
a
DB2
Universal
Database
command
window
and
enter
the
following
commands
to
increase
the
application
heap
size
and
statement
heap
size:
db2
update
db
cfg
for
$DB2_DB_NAME
using
applheapsz
<size>
db2
update
db
cfg
for
$DB2_DB_NAME
using
stmtheap
<size>
where
$DB2_DB_NAME
is
the
name
of
the
DB2
database
that
you
want
to
modify.
2.
Instead
of
selecting
individual
objects,
try
grouping
objects
first,
and
then
select
the
object
groups.
For
example,
you
might
want
to
try
selecting
groups
of
systems
or
entire
application
tiers
or
resource
pools
rather
than
selecting
individual
systems.
Grouping
objects
will
reduce
the
number
of
selections,
making
the
report
more
manageable.
Chapter
7.
Common
problems
and
known
limitations
in
Tivoli
Intelligent
Orchestrator
77
Summary of Contents for 51
Page 2: ......
Page 8: ...vi Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 46: ...34 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 50: ...38 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 56: ...44 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 90: ...78 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 102: ...90 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 106: ...94 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 232: ...220 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 236: ...224 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 246: ...234 Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide...
Page 247: ......
Page 248: ...Printed in USA SC32 2216 00...