|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
9 R) f' z4 Q5 M& U( W
" a; Q3 a i+ {+ F1 L6 m/ q cProblem:- `' K$ J4 X1 t% U' J, r, Y
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
2 Z" ?. e4 f' i. _obtain the following message after 180 days.9 I% r% ~) |5 Z, J6 T' u% s
Login was unsuccessful.: Problems encountered logging into TCServer:, U8 n. w- r2 Y6 A# M
... database2 k( R9 c; s. e2 m
Cause: Unable to bind to server running on localhost: 1572
/ q+ N, m. @( S, L# \! @, Q* f! G1 m
9 k% t; d; f2 YAnalysis:2 V/ ?2 e6 `% F+ H# L" G7 U
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
; e; k! ~. C0 ], r/ r |% k; Ecorrectly. However, when you try to connect to the database using sqlplus you can obtain the
! t, {% i* P z* P$ ifollowing error message:4 A" a, M" m! M
ORACLE_HOME=your_oracle_home/ m* N" g& z: e$ M8 x E7 K
ORACLE_SID=your_sid" w5 i" `7 y) M4 M
>%oracle_home%\bin\sqlplus /nolog
& n6 {& v* Q* t+ P2 b" C P/ NSQL> connect
6 n) y5 G+ l+ E& Zinfodba
; o3 T% i: Q3 Y4 \+ D+ _; W5 ?1 tinfodba1 s N" x& a" @. s1 D
ERROR:
7 z3 N; o# ]( f5 P. zORA-28002: the password will expire within 10 days2 R* Y, v. v6 D. l4 }
7 i" ^; |% Z1 J( G9 m# X
In the user tcserver.syslog file we find the error message:) k- z* t7 h+ C% h9 N) P
Connect failed (-28002) for 'infodba' at ***' O, K- n2 l4 o8 `: R3 M
The "infodba" Oracle user seems to be created using the default oracle profile which has an6 ~5 {5 ]4 |1 h' ?3 q d
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database2 _2 H5 m& J- b
an error message, ORA-28002, is sent and the connection fails.8 J* n0 G) ^$ r, D
2 S0 f* F& w, m* r2 W9 e
Solution:
( t" [/ m2 _" |$ B7 X& hFind the infodba profile using SQLPLUS:( s( o4 r" b' e+ p m
SQL> select profile from dba_users where username='INFODBA';
% K) e6 c+ i Q8 U6 A* oList the profile caracteristics:% ~2 H; t9 I( s! u+ u" B, _; P) X
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
' s2 M+ O* j7 M+ n2 p5 MCheck the PASSWORD_LIFE_TIME." O, C) h5 i- m: ?
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
" j; G# g# g" h# s8 o; u6 j; hSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;1 q& M" V* T/ A+ N1 @+ n
Change the password. It will not expire again.# H9 i/ x3 |3 @$ c5 L% i- K
If you don't change the password, it will expire because it was created using a different profile at5 S% Z! T) _8 _) X( q: {
the time.& d' c% w. @1 z3 u1 M6 k4 t
SQL> select expiry_date from dba_users where username ='INFODBA';
0 v3 g t, k! Y1 w# z1 l# J: l=> you obtain an expiration date
4 T! F& m' i1 Y4 s- v9 Y: }SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
# J! @, ^* h) kSQL> alter user infodba identified by infodba ; ( specify your original infodba
' n6 x# V E* s# Ppassword)8 B0 y& H% ^6 n) \( t/ M+ g
SQL> select expiry_date from dba_users where username ='INFODBA';/ z, {8 V* r$ F0 y" j! \3 @/ X, a
=> you have no expiration date.5 I$ B. g1 ]0 a# o% \
" s j! P2 n! V
) Y+ S# @! S/ Q; l, {5 @1 H5 fRemarks:; O$ @) V, p2 X8 S3 @/ |3 y
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable1 T; Q- n1 K7 ]: y& |
in %TC_DATA%\tc_profilevars.bat is always alive and correct.
( B5 K. }2 ]3 g5 T: s6 t: kAnother modification can be done on the default profile:5 d, b4 C- @( ]& t% B
) _/ D) m5 A0 }
ALTER PROFILE DEFAULT LIMIT
, @# o# g# ~ @5 y3 h; \ FAILED_LOGIN_ATTEMPTS UNLIMITED
3 p( n4 e! g/ |% x8 X9 U: X PASSWORD_LIFE_TIME UNLIMITED;
, k8 C, S4 A: Z* w5 A3 U! m
0 }2 T! P$ m6 h7 F! @; s( k |
|