Bug 10137324 - Unconditional trace in LGWR tracefile "Making upinbls request to LNS ..." [ID 10137324.8]

		修改时间 29-NOV-2011 类型 PATCH 状态 PUBLISHED

Bug 10137324 Unconditional trace in LGWR tracefile "Making upinbls request to LNS ..."

This note gives a brief overview of bug 10137324.
The content was last updated on: 29-NOV-2011
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Rdbms)

Range of versions believed to be affected Versions BELOW 12.1

Versions confirmed as being affected

10.2.0.4

Platforms affected Generic (all / most platforms affected)

Fixed:

This issue is fixed in

12.1 (Future Release)
11.2.0.3 (Server Patch Set)
11.2.0.2.4 Patch Set Update
11.2.0.2 Bundle Patch 12 for Exadata Database
11.2.0.2 Patch 11 on Windows Platforms

Symptoms:	Related To:
Unwanted or Excess Trace / Alert messages	(None Specified)

Description

LGWR trace files contain messages such as:
 
  Making upinbls request to LNSb (ocis 0x0x2aaaacc9ce48). Begin time is
  <09/20/2010 11:06:48> and NET_TIMEOUT is <180> seconds
  NetServer pid:11280
 
even though LOG_ARCHIVE_TRACE is not set.
 
These messages are generated because of unconditional tracing statements and do not indicate any error. This may be misleading and cause some concern to customers.
 
Workaround
 Ignore messages like those above in tracefiles.

ITPub博客

Making upinblc request to NSS2 NET_TIMEOUT is <10> seconds

Bug 10137324 Unconditional trace in LGWR tracefile "Making upinbls request to LNS ..."

Affects:

Fixed:

Symptoms:

Related To:

Description

最新文章

*Product (Component)*	Oracle Server (Rdbms)
*Range of versions believed* to be affected**	Versions BELOW 12.1
*Versions confirmed* as being affected**	10.2.0.4
Platforms affected	Generic (all / most platforms affected)