|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user) `( K& L, t3 o6 k3 _
- ?" D0 C: m1 L, w; D9 \3 OProblem:$ I( m0 c6 F6 | Y' o5 \- S4 W5 h
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and' T: o( J! k+ k7 V# _4 A
obtain the following message after 180 days.9 A1 j' B& [8 s6 @
Login was unsuccessful.: Problems encountered logging into TCServer:" `0 f8 v2 ^! V( F+ g% K( Y( Y
... database3 n' O \' L/ x6 B) N/ ^
Cause: Unable to bind to server running on localhost: 1572
5 b& j0 X8 O0 F' I% P" {
2 o( i% @5 {' O$ V: S A; ~/ oAnalysis:+ ~# G: `( o0 U/ M: {7 Y4 |
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
4 [; A) M' m+ j+ t" p+ ]correctly. However, when you try to connect to the database using sqlplus you can obtain the
( \8 j. B( F$ k# a" e* k3 Lfollowing error message:# {# h2 @6 Q: G8 R; G2 R' o
ORACLE_HOME=your_oracle_home
9 a! {# |1 H; a9 I9 WORACLE_SID=your_sid5 s, }5 u7 N7 \8 `! ~
>%oracle_home%\bin\sqlplus /nolog$ V3 X- t9 h" G& j3 e8 B3 X/ c; m
SQL> connect8 f( ?( @. i1 v. I( L- h5 c
infodba' g+ c5 U& g8 A) Q
infodba
; ]! g* p" n4 r" b* V; t3 d+ {' y2 x( iERROR:
: U. Y! @% \- c& r2 I7 H- AORA-28002: the password will expire within 10 days
5 }; M' m6 ]1 N6 n0 t
, S6 p$ f# R6 ~In the user tcserver.syslog file we find the error message:
5 A2 O( C! v1 T' g) ?Connect failed (-28002) for 'infodba' at ***3 ~0 I% b- m& R
The "infodba" Oracle user seems to be created using the default oracle profile which has an
: ~% o' W0 T1 Cexpiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database4 S2 r4 b* h* Y0 Y2 {
an error message, ORA-28002, is sent and the connection fails.3 j* S/ {# V u3 J2 n3 M9 |
" I# [* J+ N x5 M0 c# R" a, {! ^Solution:8 w" P4 p* ~% T' D h& b
Find the infodba profile using SQLPLUS:
' U: F% a. W$ z/ q# b+ ZSQL> select profile from dba_users where username='INFODBA';2 E3 h: T4 c) l; E& \: e
List the profile caracteristics:* c% X& g- {3 i) t% p; x; {) `
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
* ]* M8 E; J0 _, MCheck the PASSWORD_LIFE_TIME.
/ Y% }6 U( I$ u5 i; s1 h% V" e4 b/ iModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
+ Y e2 d1 E+ }- ?9 G' L3 ?7 M- ESQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;! a) m( L! M5 q! U% }. _
Change the password. It will not expire again.
, M% G H C) F2 l4 A* B3 dIf you don't change the password, it will expire because it was created using a different profile at
7 y2 y8 {, D! t. f6 ]. r' A0 l4 U" n. _the time.
. A8 S0 d: S iSQL> select expiry_date from dba_users where username ='INFODBA';2 G( e- {- G; g: n7 \. P+ V6 S8 g& t
=> you obtain an expiration date. v6 {! Z8 K4 u5 ?3 g
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
( H# G/ F1 ~- `9 F, X% D+ sSQL> alter user infodba identified by infodba ; ( specify your original infodba
8 g+ a4 u$ q6 `9 S1 Cpassword)8 c2 I5 Z% X+ U& L
SQL> select expiry_date from dba_users where username ='INFODBA';- ?1 A* Y% i/ k' d
=> you have no expiration date.
6 a) M2 X4 T$ u8 a8 Y; Z
. J4 D& H2 l" l# S3 Z: v7 S6 J# d. ]1 x7 M2 q
Remarks:
6 Y& l6 h" k0 Z6 O4 wBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
! w. O U4 R2 n+ u cin %TC_DATA%\tc_profilevars.bat is always alive and correct.3 B% t, A2 I" u" |* m' A% C
Another modification can be done on the default profile:
9 s1 ]+ _: i! W# K
' J+ u1 f% w' rALTER PROFILE DEFAULT LIMIT& A' _# _. f8 [
FAILED_LOGIN_ATTEMPTS UNLIMITED. B2 W7 M& M& l2 D& r2 `
PASSWORD_LIFE_TIME UNLIMITED;# ?5 h& \, Y/ {. f
! _1 j6 L; b1 L2 J o0 w |
|