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

admin

Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
; w7 Q* t0 C- {8 l5 |
Problem:
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
obtain the following message after 180 days.
Login was unsuccessful.: Problems encountered logging into TCServer:
) s* T# ?& t. F6 S+ b ... database
$ k% t4 I0 L) [& TCause: Unable to bind to server running on localhost: 1572
/ ~5 z$ V: `' _7 Y, P  p; l4 l/ C
Analysis:
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
correctly. 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
" D( l& F! y+ R>%oracle_home%\bin\sqlplus /nolog
: o* H: m/ K- r; ^SQL> connect
" [2 E6 N5 I+ {5 L( h8 _4 D1 ?infodba
infodba
2 V5 z& E/ [2 j. V) i+ W8 mERROR:
8 x$ r/ s6 r& V! `ORA-28002: the password will expire within 10 days

& ?% |% m$ o  b9 W$ UIn the user tcserver.syslog file we find the error message:
Connect failed (-28002) for 'infodba' at ***
; A2 S4 q2 N; K- A( f& a+ vThe "infodba" Oracle user seems to be created using the default oracle profile which has an
, u1 S' |7 L9 U8 g6 m+ mexpiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
8 I4 N4 H" l* Aan error message, ORA-28002, is sent and the connection fails.

Solution:
7 s; j' S$ ~, Q! Y6 W1 j0 o2 VFind the infodba profile using SQLPLUS:
. k+ Z! Q5 @: F8 J  ?4 D' d7 tSQL> select profile from dba_users where username='INFODBA';
List the profile caracteristics:
+ b% `* p, o( j0 }9 y' ASQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
Check the PASSWORD_LIFE_TIME.
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
% Q9 f- u! B1 o, PSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
# `9 Y, n+ L4 X9 b9 l) R, [+ wChange the password. It will not expire again.
If you don't change the password, it will expire because it was created using a different profile at
7 \. U5 f1 K; S1 R+ ]0 x& Qthe time.
SQL> select expiry_date from dba_users where username ='INFODBA';
* M0 n* S  {, |4 W( K=> you obtain an expiration date
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
0 f" A- ^& H$ r0 x8 C8 gSQL> alter user infodba identified by infodba ; ( specify your original infodba
# o, v( s1 {( T( h. Y/ w! n" v* }password)
" P5 c/ r8 r; h1 _5 ]$ I, qSQL> select expiry_date from dba_users where username ='INFODBA';
9 U' j9 v0 ~7 `" k  }% R=> you have no expiration date.


- k! A% V* \: s" h: nRemarks:
  i! R2 h. a- a7 x3 K+ tBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
6 G$ z  f' B" V  j* J6 \' a0 B( qin %TC_DATA%\tc_profilevars.bat is always alive and correct.
Another modification can be done on the default profile:

ALTER PROFILE DEFAULT LIMIT
3 Q$ w3 Q5 Y7 f" q8 Q: Q- i FAILED_LOGIN_ATTEMPTS UNLIMITED
: Q8 t/ q& M# _" @+ @ PASSWORD_LIFE_TIME UNLIMITED;
: H5 ~' R5 R4 W8 j+ F- R3 c/ }