|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
( ]5 ~( @9 i' ~, M$ h8 b7 ~( v6 B8 e; B3 r( g7 u" g' d e
Problem:. x' g2 E& ^# e$ `
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
6 X3 O2 M; i' N7 U' Dobtain the following message after 180 days.0 L7 n) r' `* M( z$ N7 T) F5 v7 p9 r
Login was unsuccessful.: Problems encountered logging into TCServer:
& ~3 K9 L6 k+ u/ @ ... database. [6 j/ t9 A0 j4 a, N" U
Cause: Unable to bind to server running on localhost: 1572
3 C& ^! T6 p1 v
8 M4 K: C/ W+ TAnalysis:
% P5 K6 _) j2 B( V% q4 f% ^ q% ]8 lThis issue seems to be due to the Oracle 11g changes. All the Oracle services are started
8 o8 F" u2 ]0 x5 u' {& G+ U1 F7 ^& ^7 ncorrectly. However, when you try to connect to the database using sqlplus you can obtain the5 X8 t! B% K0 M2 p" x3 @3 G% @
following error message:. r* C7 B& S7 ?5 k
ORACLE_HOME=your_oracle_home
& z( I7 N7 |% F3 s! \1 r9 Q$ s2 _ORACLE_SID=your_sid
/ b c; `. u, \& n>%oracle_home%\bin\sqlplus /nolog( E2 m# l; }1 s( ` S; _
SQL> connect
/ a. b* g2 q! H) v0 Ninfodba+ b* h7 Y' O" x- Y! ^: n
infodba8 _( g6 I, T- a. x$ f5 N9 V- @- j- \" q
ERROR:
* G& r! j$ o* u8 b: `ORA-28002: the password will expire within 10 days3 @+ C" `* j% A) r# H
3 T& _6 V% i% R+ e- B
In the user tcserver.syslog file we find the error message:4 w5 m! P' t. _% t8 S; Q
Connect failed (-28002) for 'infodba' at ***6 T3 P" R" f' G6 D. T: T
The "infodba" Oracle user seems to be created using the default oracle profile which has an
: x( E0 U y i$ pexpiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
$ m- T [) L; San error message, ORA-28002, is sent and the connection fails.
3 n) q+ _1 A0 M) m; e& E& R" R4 T1 ?8 X9 R+ @% R* _8 [" p
Solution:' L8 n% Y/ P5 ?8 e3 q
Find the infodba profile using SQLPLUS:
, J. i+ o( s$ aSQL> select profile from dba_users where username='INFODBA';) m, B! [ {" U) A. [) }' p
List the profile caracteristics:7 w7 `, k& {# i( k5 K
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';) i8 M2 s0 L% O+ g5 g' y6 e
Check the PASSWORD_LIFE_TIME.5 y. u* z/ ]' v) B5 ~4 U2 K+ q
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
% B' W* c& Q# ` i+ t- L2 F/ t9 nSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;5 d7 ?5 a( b! M! ~2 p9 N3 p
Change the password. It will not expire again.* z7 ^& g( e; m0 ?% c% V5 X
If you don't change the password, it will expire because it was created using a different profile at
, _7 p) d- \# M/ W& g: cthe time.) k* V6 n6 t# B
SQL> select expiry_date from dba_users where username ='INFODBA';' f2 }5 }% j; [5 M" ?, v5 Q
=> you obtain an expiration date+ C& k% b% T6 D6 C: S" q# X8 N# [/ ]
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) 5 d) F8 o3 f2 _/ \+ a
SQL> alter user infodba identified by infodba ; ( specify your original infodba# T4 P6 ^! L: i P* \
password)% q. Q8 u" [* d/ k. F& @
SQL> select expiry_date from dba_users where username ='INFODBA';, R* p7 D$ Y- w t" x, X$ Z0 `
=> you have no expiration date.
: m) f% x3 f$ B0 \/ F1 H) L2 A! W2 M
8 @0 q& {& s5 J1 f2 b
Remarks:
' U8 X- T2 D- IBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
" y! d; n# {5 b" Pin %TC_DATA%\tc_profilevars.bat is always alive and correct.( O6 r& Q6 _5 i0 C* ?1 \5 V9 p! {
Another modification can be done on the default profile:5 Y- ]7 r4 }3 L3 H8 T* A5 Q) c# I& Y
2 m7 e: p8 p* }; ?7 ~
ALTER PROFILE DEFAULT LIMIT( K" g1 `% E/ j- b E8 b
FAILED_LOGIN_ATTEMPTS UNLIMITED
9 Z* r) ]( f+ E+ v& v PASSWORD_LIFE_TIME UNLIMITED;
$ d& _) ^3 {1 p) N9 |
3 h! G, E8 t; V& B3 J# X |
|