88.Teamcenter 的账号infodba数据库oracle过期的处理

admin

Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
8 r/ p" o& g7 X/ s$ A
5 c3 ?0 }& ~0 O  y4 SProblem:
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
obtain the following message after 180 days.
) N* j) w/ w; r9 B/ u% [/ V' d8 }. LLogin was unsuccessful.: Problems encountered logging into TCServer:
6 i6 T) [' K4 q2 L' e# V. a0 B/ `% u ... database
' B1 T9 N* }) V  O" c  hCause: Unable to bind to server running on localhost: 1572
2 c8 I$ u, I. y( Y- Y
Analysis:
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
  j8 S0 M: H8 Z/ E) @% a6 o5 Ecorrectly. However, when you try to connect to the database using sqlplus you can obtain the
following error message:
ORACLE_HOME=your_oracle_home
ORACLE_SID=your_sid
/ x9 j7 ]8 F1 j  X/ |& _# v6 f+ R>%oracle_home%\bin\sqlplus /nolog
/ d  F% k, N* a2 o3 BSQL> connect
1 Z# @; _( N  ^/ j! Minfodba
infodba
ERROR:
9 N  B$ J# k& g+ S9 o9 l( LORA-28002: the password will expire within 10 days

In the user tcserver.syslog file we find the error message:
, y  @1 L* F( [4 [) @" d) ^- JConnect failed (-28002) for 'infodba' at ***
The "infodba" Oracle user seems to be created using the default oracle profile which has an
; Y4 c) v% C& K; J3 V6 uexpiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
an error message, ORA-28002, is sent and the connection fails.

" b# Y, i& |4 \) a3 ~! USolution:
Find the infodba profile using SQLPLUS:
' {( p# p1 v& ~" @SQL> select profile from dba_users where username='INFODBA';
% Q! G% r) ]  o, L, a$ v; e  ]List the profile caracteristics:
! u2 w0 ^3 D' D7 zSQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
Check the PASSWORD_LIFE_TIME.
: v0 a) z5 I  _; X& G/ IModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
! v8 r7 D2 i/ y7 zSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
Change the password. It will not expire again.
3 C8 J" A0 G$ G: }) }2 s/ I: tIf you don't change the password, it will expire because it was created using a different profile at
the time.
9 N* y$ y# i2 H% t0 X$ HSQL> select expiry_date from dba_users where username ='INFODBA';
: z- ~( K0 A1 h. h+ v=> you obtain an expiration date
8 W  s9 M2 |) E4 z/ n$ X: CSQL>alter user infodba identified by tempo ; ( define a temporary pwd)
  M5 R- q3 \* x' s5 cSQL> alter user infodba identified by infodba ; ( specify your original infodba
password)
SQL> select expiry_date from dba_users where username ='INFODBA';
=> you have no expiration date.
8 l$ N: v0 ^( h6 `4 E
; m* I8 s/ u7 O) ?; \  G6 y
Remarks:
) z1 w5 W# n0 ~+ `3 h7 ZBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
in %TC_DATA%\tc_profilevars.bat is always alive and correct.
  n& S! `4 m% N& AAnother modification can be done on the default profile:

5 M6 d7 s/ L, q% ^. wALTER PROFILE DEFAULT LIMIT
+ k% ~1 C  w" _. V: H, g$ ? FAILED_LOGIN_ATTEMPTS UNLIMITED
3 q" ~6 t# i% w# }- f3 I PASSWORD_LIFE_TIME UNLIMITED;
) C- L! L# f' Q$ J/ x0 W