|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user! r* {2 ~* V9 Q" @
6 W7 r8 |6 F: }9 l! S
Problem:1 C8 n* {' z2 a4 f( R) w: {
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and; l; j- d3 m" ^& l% e
obtain the following message after 180 days.+ D) F. [+ O+ J8 a+ x
Login was unsuccessful.: Problems encountered logging into TCServer:6 T5 C3 X% R3 ~0 L" G0 ?% y0 o
... database0 G5 W' s- A* _+ m5 T6 u
Cause: Unable to bind to server running on localhost: 1572 ^4 f" h! E- y2 @/ x/ y7 y
$ s, {1 C1 _' s0 |$ r+ b1 `3 m/ fAnalysis:5 f0 G- }( [4 j
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started. c8 D" }' o# @5 i
correctly. However, when you try to connect to the database using sqlplus you can obtain the! n+ S, N" B. m. R }- U, B; ?
following error message:
2 D: Z3 F- E4 ~ I/ }4 z% F% LORACLE_HOME=your_oracle_home
9 T6 p/ x3 u8 @2 Y6 `1 P- a, q7 yORACLE_SID=your_sid
$ ^" j; Y$ ~1 B% n7 o>%oracle_home%\bin\sqlplus /nolog
1 V% e- R$ s" A [SQL> connect
& G4 ]& w2 R4 \/ [4 ]) ginfodba
. R3 d5 z. B0 _6 {! Y& Jinfodba
! v# j6 ~) q# Q& TERROR:$ }0 u& m7 I+ ^6 v3 ~/ f! I
ORA-28002: the password will expire within 10 days
; W* }. V( z+ N0 R& N# ?( { n/ d# U
In the user tcserver.syslog file we find the error message:- Y' V. |: [9 z2 u4 D7 f" q
Connect failed (-28002) for 'infodba' at ***
! w! T% N% @ w0 ?# B BThe "infodba" Oracle user seems to be created using the default oracle profile which has an: z' D k9 Q A" u9 s/ v
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database- z+ a$ d* B4 f! ^
an error message, ORA-28002, is sent and the connection fails.
+ ^+ ?" u U* Q5 A" H" w$ J6 L, T' F% l$ v3 k
Solution:6 E; s0 Z/ J3 s7 V6 t2 w2 ]
Find the infodba profile using SQLPLUS:0 ]+ D( g. ?5 s2 ]$ ]+ \# @
SQL> select profile from dba_users where username='INFODBA';* {4 |% l7 {5 X! z$ I
List the profile caracteristics:0 d) M8 f( p/ t% \0 i3 b# p
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
" I/ ?, S( J7 C6 J$ U. G" LCheck the PASSWORD_LIFE_TIME., ]3 b; b$ H0 F- b' e- G3 O
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:% r9 s5 d& w2 ^4 b: V
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
! H5 z* @: f# gChange the password. It will not expire again.
% Q" a, z! s; L9 ^$ i: R; S2 J) E7 \If you don't change the password, it will expire because it was created using a different profile at
0 L" z+ {3 a1 P' w7 M% g) lthe time.
7 g) w0 n" @+ ]: c. U* A$ kSQL> select expiry_date from dba_users where username ='INFODBA';3 _/ _4 o$ {4 ~! V6 n
=> you obtain an expiration date( @4 G @. i! W7 e
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
- h/ {$ ^0 b9 {% Q# l! e5 \SQL> alter user infodba identified by infodba ; ( specify your original infodba2 l1 S6 V+ Q j, u. D) G
password)
- G3 J5 y7 Z' u" ESQL> select expiry_date from dba_users where username ='INFODBA';$ M+ C+ L, N' Z6 M- E2 V
=> you have no expiration date., d! u& j* a$ ?
/ _3 F$ z. t+ [ W8 G
: h4 t& H: X3 r. x/ F/ h
Remarks:' s8 d2 C5 k1 F9 K! N8 ]9 T
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable* N: w+ G" z7 J+ c
in %TC_DATA%\tc_profilevars.bat is always alive and correct.8 q2 I0 }/ @/ p. a4 U" j, U
Another modification can be done on the default profile:
) G1 l) j+ R# x* D* B/ o3 V* j K( \) V9 ` q
ALTER PROFILE DEFAULT LIMIT4 {: R4 d9 j/ g) o
FAILED_LOGIN_ATTEMPTS UNLIMITED
* B H) Z7 Q& c+ Y% Y PASSWORD_LIFE_TIME UNLIMITED;
6 }. X \" |" a6 v
( o9 X: w0 a; R% O |
|