|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
) t: |, O0 h4 g; A6 o- R, _5 ~6 a9 t( P' {: K) a2 Q
Problem:
& n8 @$ n2 P6 |% g# eIf your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
9 s$ I. p' P0 \% mobtain the following message after 180 days.
" u% a& K6 J/ `! z5 \% y& @Login was unsuccessful.: Problems encountered logging into TCServer:
$ E0 s# |& B3 q1 q" W5 z8 P. } ... database0 C C8 l& {7 n9 O7 ^ H
Cause: Unable to bind to server running on localhost: 1572
$ q5 Z5 |' y# s) f) W+ U* a8 H, h9 w K7 M6 @5 q, V
Analysis:" C9 }1 B+ N, ]: y
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
& k f6 A) v- q2 q7 [( fcorrectly. However, when you try to connect to the database using sqlplus you can obtain the
3 D' N# o' r. `( l8 a9 {/ efollowing error message:9 `8 y8 f9 s" E( e$ i0 s
ORACLE_HOME=your_oracle_home2 O( |- ^: b' a
ORACLE_SID=your_sid
" Q2 [3 V( ?# }>%oracle_home%\bin\sqlplus /nolog
$ t& U2 N- U: D% ASQL> connect
8 r' j0 r7 `1 |) Winfodba
, a) X6 {( S3 B5 Jinfodba% S: w2 n, b V" R, S7 ?
ERROR: H& t$ D" j, }& U, p
ORA-28002: the password will expire within 10 days
6 Y) u4 `! ]- y1 k
; r1 ?. L7 a2 u+ y4 ?1 b: oIn the user tcserver.syslog file we find the error message:0 M o9 j3 o' v8 l3 R3 h" I6 H: ~
Connect failed (-28002) for 'infodba' at ***/ K+ R, C) }4 `
The "infodba" Oracle user seems to be created using the default oracle profile which has an }2 `! w2 ~: S+ ]6 w7 m
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
" C6 c: q( f! J; [: wan error message, ORA-28002, is sent and the connection fails.
% | R# b8 L, ?, K0 |+ i* }3 Y+ Q3 Q& _ X% I
Solution:
d8 }0 F& z7 sFind the infodba profile using SQLPLUS:, k" J6 ~" C+ c0 M# E8 m; y8 u
SQL> select profile from dba_users where username='INFODBA';
! _' X8 ?7 C( a. T6 i3 F7 `- O9 oList the profile caracteristics:
5 S' ]% V1 S, \, kSQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
2 W7 h) B, t+ v% q. i5 C5 oCheck the PASSWORD_LIFE_TIME.
' I& g$ h9 I, H0 }+ |Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:& l( t3 t6 d' F$ x* f7 t+ r
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;, t7 o" C$ J) J6 ?: n
Change the password. It will not expire again.
- m! D( m2 V4 c1 ]! }If you don't change the password, it will expire because it was created using a different profile at
- d& o q$ ?; Q& k2 z% Ithe time.
4 t+ e" y7 q) }% ?! v3 TSQL> select expiry_date from dba_users where username ='INFODBA';4 @' D! h' ?9 e& u9 y+ J, j
=> you obtain an expiration date
* Q: a$ T7 L/ [( P8 e+ DSQL>alter user infodba identified by tempo ; ( define a temporary pwd)
2 u) p2 \6 Z! ^ G4 hSQL> alter user infodba identified by infodba ; ( specify your original infodba
$ A4 Z2 j( l1 G9 cpassword): W% i" F' L& ^# M ?3 K
SQL> select expiry_date from dba_users where username ='INFODBA';
* `- N5 V* h2 a" p5 O/ @" I=> you have no expiration date.* c$ _- q, Z! Y z3 {' s
3 o6 f" l- X8 `+ I7 e4 c( m- K
5 I, J/ a+ a9 @* Z9 n0 g2 |
Remarks:7 @; J$ I# t& c3 k& r7 p
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable
& k! z1 u' t- s/ D0 @in %TC_DATA%\tc_profilevars.bat is always alive and correct.' o7 T4 k& I6 g( Q4 }- I( H2 Q
Another modification can be done on the default profile:
8 K: O- ]+ G- W2 [& [, O9 j9 o" t- [$ Q$ Q5 X+ |' m
ALTER PROFILE DEFAULT LIMIT4 g4 n' ?! m( g
FAILED_LOGIN_ATTEMPTS UNLIMITED
5 b$ ^! y! Z" W/ [8 I PASSWORD_LIFE_TIME UNLIMITED;
8 n3 H6 R! G/ l! h- e
, i6 k+ f1 A m# d6 `$ b* @ |
|