- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
5#
发表于 2013-9-5 20:17:45
ODM FINDING:
JServer Version is Displayed Incorrectly In SQL*Plus Banner
A SQL*Plus connection normally shows the JServer Release version in the banner output. For example:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Oracle Data Mining
options
JServer Release 9.2.0.6.0 - Production
Notice that the JServer release is not correct. It does not match up to the version of database to which you are connecting. For example:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Oracle Data Mining
options
JServer Release 9.2.0.6.0 - Production
Note that the Enterprise Edition is 9.2.0.5.0 and the JServer Release is 9.2.0.6.0.
CAUSE
The following scenario can cause this anomaly:
A 9.2.0.6 version listener in one ORACLE_HOME that is configured to listen for a 9.2.0.5 instance in another home. LD_LIBRARY_PATH or SHLIB_PATH
in the listener's environment is set to include a pointer to the 9.2.0.6 $ORACLE_HOME/lib directory. This is where the erroneous JServer release
information is originating.
SOLUTION
Configure the environment so that it does not include an $LD_LIBRARY_PATH or a $SHLIB_PATH pointer to $ORACLE_HOME/lib. Restart the listener with this new profile. SQL*Plus
connections that are made via the listener will now show the correct JServer Release information.
|
|