|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user9 E' _5 P/ b. a, j
, y) h; U5 {) K. O' |7 P
Problem:
$ s/ e# K2 }* [0 ]% }8 Z+ WIf your Server is using Oracle 11g, the Teamcenter users may have a connection problem and u& k3 y& Q- V6 `& C2 @$ _
obtain the following message after 180 days.
# V! U9 V& i4 s" \Login was unsuccessful.: Problems encountered logging into TCServer:$ h* j* ^$ @0 A k
... database
% N# a" |3 A7 q) h0 CCause: Unable to bind to server running on localhost: 1572
- G- A1 x a% `" V$ M
2 p. }; l1 F8 q. ?7 B3 y! lAnalysis:' }, R, J+ I4 \2 i9 B
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
" R4 c% ~/ ^$ ]6 D, ucorrectly. However, when you try to connect to the database using sqlplus you can obtain the
/ A( m* z$ m, [following error message:! i) t* D, g. \3 M/ M5 k$ e
ORACLE_HOME=your_oracle_home$ P4 t5 d% ?& g( N* k) b% B; ^4 S
ORACLE_SID=your_sid- f( t9 F4 P. |# A/ s4 [
>%oracle_home%\bin\sqlplus /nolog! r- G/ i( K; R. H: f
SQL> connect
" K" ` o4 t/ f- x; jinfodba# V- K# |5 A( E" E
infodba4 [+ G) x6 K# } [- m+ U( `# l. C
ERROR:$ s( e" ^0 U3 e9 B! A |+ m
ORA-28002: the password will expire within 10 days' `% s: r$ t1 o: a
. }9 y& Q" r$ w; B& g9 q3 aIn the user tcserver.syslog file we find the error message:( B) K/ Z, n4 }2 Y
Connect failed (-28002) for 'infodba' at ***
9 t/ K$ A0 H( n ^The "infodba" Oracle user seems to be created using the default oracle profile which has an( Z! r3 `( t4 E! D& k
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
C4 J# Y4 ^2 M. W1 u4 Oan error message, ORA-28002, is sent and the connection fails.
. v, x7 o: q3 A5 m
7 ?6 Y m- S$ v! W: ^9 eSolution:
5 ^: P2 r$ M# U% i" h+ U$ d$ fFind the infodba profile using SQLPLUS:. E% M! t8 \0 a+ _
SQL> select profile from dba_users where username='INFODBA';
5 X- d) z, I ?! l4 s+ \7 c9 X: HList the profile caracteristics:) [3 A' a7 e# t. g: a3 Y0 I$ K- v& T
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';0 d$ K6 U% L- z9 x3 O6 t, a
Check the PASSWORD_LIFE_TIME.- @/ o) s" j# p9 e4 J
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
6 [8 U. h% i' b- ~5 tSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;2 k( g0 Q' T" @; ^% y2 @1 S$ h1 E
Change the password. It will not expire again." `6 N' A/ @, F- z2 d
If you don't change the password, it will expire because it was created using a different profile at
0 y6 r! e- m& ithe time.0 d9 D* Y& e5 S
SQL> select expiry_date from dba_users where username ='INFODBA';* H. F1 [7 n. _, y0 C: ~% _" Z
=> you obtain an expiration date P* @& r+ U- @9 c3 v& E
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
/ T, u& ^- m1 ?* T. lSQL> alter user infodba identified by infodba ; ( specify your original infodba1 K+ \8 [9 B$ u5 i; z: K
password)
5 M, r2 l, }. t; ?SQL> select expiry_date from dba_users where username ='INFODBA';# c5 h! w% j: m6 I- [" E
=> you have no expiration date.
% i# G2 D* I; _2 q' Q% o. w: e) R' k j5 v; @8 w7 W9 Z
- |5 ^: C, |2 ~4 w- P. O" zRemarks:
1 a ]. G& v! m4 l' P) wBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
8 O* T; O# Z3 a, C, Q2 }in %TC_DATA%\tc_profilevars.bat is always alive and correct.
: U+ b: T0 z7 R0 DAnother modification can be done on the default profile:
; V6 e8 z1 q4 {7 U+ L) c' e( a7 m& k0 R+ {& {! {+ d
ALTER PROFILE DEFAULT LIMIT5 \7 F) o. q( B$ f, C
FAILED_LOGIN_ATTEMPTS UNLIMITED
) R7 Y R2 I4 Z. z8 T' k PASSWORD_LIFE_TIME UNLIMITED;1 @6 J# O, f* j% |0 W- x) \- I
% P4 J4 D' ]0 ~7 o5 Z
|
|