|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user% c+ u& q) o; z4 g( X4 [
9 j( a- S4 P j$ Z
Problem:! P. l* L8 E- n( ~. m9 W
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
2 B4 Z- C0 M, o5 d9 N: Z+ ]obtain the following message after 180 days.1 e* C. B7 P8 q8 q( \, z `2 D
Login was unsuccessful.: Problems encountered logging into TCServer:5 w1 Z; c& p" l& Y, F! Z2 {" C. {6 H
... database- F1 `; M; }0 _
Cause: Unable to bind to server running on localhost: 15722 g1 z+ }$ W* N' |* A+ d
( l6 m5 |" l/ n# bAnalysis:& B. I- t s- `) \2 e& D+ W( N
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
8 C/ ?, ^. M& vcorrectly. However, when you try to connect to the database using sqlplus you can obtain the
: G0 b8 {4 g+ g6 j/ Ufollowing error message:% D8 |$ n$ H6 F2 ^! ~
ORACLE_HOME=your_oracle_home( ^! ~# k4 V0 L% T
ORACLE_SID=your_sid
9 J! T* W6 \4 C7 J) g>%oracle_home%\bin\sqlplus /nolog/ i! B1 s+ [; f. k% A, }) T
SQL> connect, X2 ]- G8 M3 u' n" {7 k
infodba( ^: E8 r- v; W- _3 Z7 Z4 ~
infodba& }+ s/ A- H; Q7 R
ERROR:& z" R+ y8 e$ ]' J, C( z9 N
ORA-28002: the password will expire within 10 days
4 O% C7 [& `/ M3 L
3 B) W6 t/ j6 A8 E: IIn the user tcserver.syslog file we find the error message:
5 S0 P) s$ L3 H6 rConnect failed (-28002) for 'infodba' at ***- M2 u/ r5 T- E) L7 K0 N C
The "infodba" Oracle user seems to be created using the default oracle profile which has an5 V" p1 y2 A0 q6 O1 m7 N
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
; |6 h4 q* l3 h/ @9 Can error message, ORA-28002, is sent and the connection fails.
/ v. S; T/ }! ]# j2 w; m9 u m
7 C+ s3 [$ }0 s! X' h1 sSolution:. A; T3 H$ E) q) X. D, n( i
Find the infodba profile using SQLPLUS:0 R% x) \7 P; ~* J5 H* k1 @
SQL> select profile from dba_users where username='INFODBA';
- X/ |5 E& ?2 z5 e4 ?List the profile caracteristics:7 N- }* v& z6 |4 C
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';1 p6 I+ B( K9 c; A
Check the PASSWORD_LIFE_TIME.
; H- w+ n; j6 v8 o% u- k5 n6 zModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
8 Q) g1 V" @- e% Y- V" ^2 U A& J. fSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
( x$ f2 Q5 I! D5 p% GChange the password. It will not expire again.
1 Q; ~6 S! H( H; ?" BIf you don't change the password, it will expire because it was created using a different profile at6 ?% w) c! ?! @. d4 V
the time.
' Y; D+ z9 R8 S7 k* B, V- XSQL> select expiry_date from dba_users where username ='INFODBA';9 H& e$ P, b& c! g0 K/ X
=> you obtain an expiration date1 d" Q+ P; U* C6 |' F
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) 3 |/ F1 T; O0 P2 K
SQL> alter user infodba identified by infodba ; ( specify your original infodba( r* K5 M% p& T8 E, b
password)
' Y* T+ q, G( a k4 s5 F. OSQL> select expiry_date from dba_users where username ='INFODBA';6 J6 C, `4 o/ G
=> you have no expiration date.9 J8 I- W! [8 a/ [1 c
: q% V( n! l$ {, N2 M. B- I
E4 s+ a3 M" y. j' ^, Y7 JRemarks:
* p" {% l- U$ y; N3 J6 kBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable! l7 j- `4 n2 ^* P* N
in %TC_DATA%\tc_profilevars.bat is always alive and correct.2 u$ m, {. Q$ A2 R' q Z+ V
Another modification can be done on the default profile:; A8 y+ K, s8 a/ }) h
; c) Q$ ?+ I; H7 F2 y% R/ cALTER PROFILE DEFAULT LIMIT5 v$ f2 {# e, @5 c; b2 d% g5 b
FAILED_LOGIN_ATTEMPTS UNLIMITED
: }' V" ~# r& E9 G0 }8 k PASSWORD_LIFE_TIME UNLIMITED;
- P" J1 E! Q: w% l5 q- X+ d& d" ?$ }5 ~! Y* C; d0 I( j
|
|