|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user+ ]0 k: x' Y/ c0 }
$ s1 ^) h9 D% Y) X i6 i
Problem:
. X6 P }' I/ ]* q8 jIf your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
- _" z8 v5 M' {0 @obtain the following message after 180 days.
+ ]) x/ b/ _- `, n8 z2 d- s$ ULogin was unsuccessful.: Problems encountered logging into TCServer:$ Z, v% r$ B6 v5 i3 E: Z9 L* m
... database
0 x$ H7 v3 R" o2 G3 sCause: Unable to bind to server running on localhost: 15725 _: i- R( j8 [/ ~% f
2 x" d3 e* m5 F% d" I% ~: a
Analysis:
" S. ]. M: @; RThis issue seems to be due to the Oracle 11g changes. All the Oracle services are started; [: }5 t3 |6 V9 `: G, x+ M6 \
correctly. However, when you try to connect to the database using sqlplus you can obtain the' t; h3 F" J6 g1 S6 A
following error message:
6 n2 R4 O) X' xORACLE_HOME=your_oracle_home
1 {$ E# R: l. J" xORACLE_SID=your_sid
( }3 j0 S5 J$ p' c7 ^>%oracle_home%\bin\sqlplus /nolog6 o8 s: T0 E- H, s% @( j: s" x
SQL> connect* D' ~: {4 K. W: r0 c6 c- S3 X
infodba
6 T# P [& M+ I0 Y* Ginfodba
N* }0 C0 U9 ~7 g% s8 H S, U) Z( ~ERROR:
( v- E, [5 [* H0 O. \ORA-28002: the password will expire within 10 days1 H; D8 k7 R. o! [/ @ \% M
' c' o$ K G% a6 I6 E0 ~
In the user tcserver.syslog file we find the error message:. z7 _0 ]- s4 j9 F3 U
Connect failed (-28002) for 'infodba' at ***7 U) p( ` o7 v2 ^7 ~2 E
The "infodba" Oracle user seems to be created using the default oracle profile which has an1 m3 n0 ~9 w- M# [+ Y
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database4 V9 m- j4 |! F2 c
an error message, ORA-28002, is sent and the connection fails., a3 }( `9 W. u4 F' p
* ?3 [- j* \# Q) z7 X/ MSolution:* c) e+ |! m" Q- M
Find the infodba profile using SQLPLUS:
5 U X1 R. c9 L, f8 i; F, n" K8 |SQL> select profile from dba_users where username='INFODBA';& L, q8 ^" g- Y2 u$ o
List the profile caracteristics:1 n4 ?1 q* e ?2 \
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';9 ^; p& ?' ^# L
Check the PASSWORD_LIFE_TIME.
1 T4 s6 {+ W6 H8 f$ \* F" X; p; IModify the profile and specify an unlimited PASSWORD_LIFE_TIME:( O( }" m/ q! l
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
4 y: c/ ~& Z2 M6 G MChange the password. It will not expire again.7 U+ E* O5 P( s: j0 I
If you don't change the password, it will expire because it was created using a different profile at: V7 q. h- a5 L1 S
the time.
1 U2 i5 i2 D) l2 q; e. OSQL> select expiry_date from dba_users where username ='INFODBA';
K; K$ {& g5 }* f& a4 P=> you obtain an expiration date" B, u% ^- w: K8 ?7 |# K+ j6 | a
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) / H6 |9 Q/ C" B
SQL> alter user infodba identified by infodba ; ( specify your original infodba
- x" _; ^8 ~9 G! M5 ?3 Spassword)
! h4 X# T4 L& L$ KSQL> select expiry_date from dba_users where username ='INFODBA';& w4 ` e2 [$ q4 U
=> you have no expiration date.% w2 `0 l. D, G
% z! V- r, y% ?% d# L) R( t! Q. G8 q. F4 _# Q
Remarks:
& N5 o8 N/ T7 q/ yBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
5 b/ H0 U8 O$ j" l2 ^in %TC_DATA%\tc_profilevars.bat is always alive and correct.- p; |9 ` ^7 k5 t) z( h
Another modification can be done on the default profile:
' o+ s. Q& K4 s& _ h3 @( G+ I& x
$ p/ G( v7 @% x6 Z: o) ~ALTER PROFILE DEFAULT LIMIT
; n& y) O- J( |/ U6 { FAILED_LOGIN_ATTEMPTS UNLIMITED& Z' }( c: ?: T9 T
PASSWORD_LIFE_TIME UNLIMITED;; i+ f3 _6 ^. b: l* F- P9 _, o
) Y+ R# U6 \- O4 y8 w
|
|