|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
; v0 l! B! Y0 B0 I" k( q
1 D7 w8 a. }3 a4 \Problem:! S1 B- F4 ?0 d
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
( \" k$ \/ p( W; w9 Zobtain the following message after 180 days. ?6 @) m) w) x& f! s
Login was unsuccessful.: Problems encountered logging into TCServer:
- p, @: {3 }# l ... database: p9 M0 |: G( C P
Cause: Unable to bind to server running on localhost: 1572) K+ N- j" `% b* N; c+ o
; |* k5 {; O9 z, |7 c
Analysis:
+ `) s1 T q+ M. {) bThis issue seems to be due to the Oracle 11g changes. All the Oracle services are started( d3 B& p k; C: [" Y% ^" Z
correctly. However, when you try to connect to the database using sqlplus you can obtain the
8 \8 [4 H& U: s1 @4 ~following error message:9 b1 ^4 E7 ^4 |9 E
ORACLE_HOME=your_oracle_home
: q3 ?- T* D' r2 ~* ^$ T( P KORACLE_SID=your_sid% @) s0 I% [5 Q8 t" T( E) J1 |
>%oracle_home%\bin\sqlplus /nolog
# M( C4 M! o' w) M# v8 {6 ZSQL> connect. u0 z1 z& ^! X( F7 i
infodba! f7 B6 q$ X; |# D, n! `
infodba
" z1 X8 ?& J3 m/ T5 Z, FERROR:# |; u: v! [: h, A) Q& N* `) a. Q
ORA-28002: the password will expire within 10 days
/ w4 e* z1 L" [$ S G: z1 s4 ?) t7 V. ^9 s: T$ t$ Z7 F( Q( v, P8 f1 g
In the user tcserver.syslog file we find the error message:
5 @5 D, x9 o( [9 _Connect failed (-28002) for 'infodba' at ***
) t" t/ G* s9 bThe "infodba" Oracle user seems to be created using the default oracle profile which has an4 ^6 `2 V/ ]* P
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
2 E1 _( n& r# l7 B C& aan error message, ORA-28002, is sent and the connection fails.6 Z. C) j, k+ F, i
$ f9 r, E# [' ^8 i8 O$ s. L1 ?Solution:( z6 R2 T5 j& h( E4 i
Find the infodba profile using SQLPLUS:
- \1 c- }1 T4 X7 Q% q% VSQL> select profile from dba_users where username='INFODBA';
' C! g0 u$ x" `% P) N, v5 g# `List the profile caracteristics:7 ^7 l& Z+ g1 S5 O: k
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
" Z( o$ i1 I- T% _- UCheck the PASSWORD_LIFE_TIME.
; Y$ v& b, }6 QModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
& _. |! f2 H7 uSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;: a. G: J" t1 j7 L2 T( A; ^
Change the password. It will not expire again.
& ~9 R3 M9 c/ i- h p' EIf you don't change the password, it will expire because it was created using a different profile at
) V( z9 C% ?. a* h$ O4 p/ Nthe time.7 x$ W! M8 h. s7 ~1 `
SQL> select expiry_date from dba_users where username ='INFODBA';
0 b- }; n+ k" k1 U=> you obtain an expiration date# q$ F+ n9 _/ x D& @' x
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) . o. g) [4 F# ~% E2 x
SQL> alter user infodba identified by infodba ; ( specify your original infodba
& M7 Q, L. E M8 X1 n1 n# \' Npassword)
! p9 ]# M$ G, F0 |SQL> select expiry_date from dba_users where username ='INFODBA';
9 O' Y7 w1 y, b6 V=> you have no expiration date.
$ ]8 O1 ~, M3 a7 l( ^; ]! @0 ~* j5 W5 f. u
1 P9 l2 H% c8 t" g# F) M x6 _) F
Remarks:
% L* A4 }5 f+ C& D& K/ MBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable- `" O; C; c- H$ M
in %TC_DATA%\tc_profilevars.bat is always alive and correct.1 j% C5 C* |/ f5 ]: G( |: h( s
Another modification can be done on the default profile:$ o+ e& w7 e( O5 [3 o/ X1 }1 r% G
7 ^0 N1 B$ |! I8 G
ALTER PROFILE DEFAULT LIMIT
3 Q# I( v' P+ @& }4 F FAILED_LOGIN_ATTEMPTS UNLIMITED
# m7 C( R3 t+ ?& @+ p) p PASSWORD_LIFE_TIME UNLIMITED;# e! x# k3 I- L( Y/ d
% f! W2 z7 W2 x |
|