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

admin

Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user

3 V  z+ a$ D1 Z' M+ ?) @5 a8 VProblem:
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
- U$ V+ J9 s+ J! K/ L5 {- [obtain the following message after 180 days.
4 h, o% Z" h9 E9 O( m( m9 O1 G' RLogin was unsuccessful.: Problems encountered logging into TCServer:
  W" ^0 R9 h* K# \ ... database
Cause: Unable to bind to server running on localhost: 1572

Analysis:
7 f+ K0 y* s( r# N& WThis issue seems to be due to the Oracle 11g changes. All the Oracle services are started
9 e2 H7 L: W: A8 V, q+ Z* F, x2 xcorrectly. 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
& u6 Y0 v! E; T7 i) ]& L# ^9 x>%oracle_home%\bin\sqlplus /nolog
6 R6 t7 R* v2 d& gSQL> connect
8 N( r; x7 `' D5 i1 Q' Ainfodba
4 ]( c6 n, |- L* F: Dinfodba
ERROR:
ORA-28002: the password will expire within 10 days
* _1 B' I3 p! C2 z9 [, @
In the user tcserver.syslog file we find the error message:
+ Z" ]2 U: H/ I. _Connect failed (-28002) for 'infodba' at ***
The "infodba" Oracle user seems to be created using the default oracle profile which has an
0 M0 A6 c4 K. \. g& t3 _; Dexpiration 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.

* Y$ v/ h' M8 G7 K* k. \Solution:
% a, K4 {5 N. C5 a3 mFind the infodba profile using SQLPLUS:
+ Q9 P/ l* j7 S  m3 J4 B1 `SQL> select profile from dba_users where username='INFODBA';
8 k# e$ I. E3 s% ]5 r* OList the profile caracteristics:
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
0 r+ b" C& y- n6 wCheck the PASSWORD_LIFE_TIME.
9 ~7 A( V5 w" c; x  t3 g5 }' S- |Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
0 b! r) X; }. L0 _& HChange 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
the time.
SQL> select expiry_date from dba_users where username ='INFODBA';
=> you obtain an expiration date
" t3 y6 Z  o, _5 MSQL>alter user infodba identified by tempo ; ( define a temporary pwd)
: O- W  w/ M$ q. H' W* PSQL> alter user infodba identified by infodba ; ( specify your original infodba
& t0 b  K( F1 }$ |) X& b. ]password)
! f- O# {* |" Y. I  _9 i5 e5 wSQL> select expiry_date from dba_users where username ='INFODBA';
=> you have no expiration date.
$ q( X# U6 e# X# ]! O2 N
6 f4 q" b2 `7 Y+ V" _5 r
& w. ^% x# `1 K% B- F2 a' w4 ^0 wRemarks:
! ]' G7 w$ N& O8 V2 Z4 wBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
2 T: d) s" n* E  Q. vin %TC_DATA%\tc_profilevars.bat is always alive and correct.
& p  m1 |7 B# ~Another modification can be done on the default profile:

ALTER PROFILE DEFAULT LIMIT
FAILED_LOGIN_ATTEMPTS UNLIMITED
, k! V8 o1 p+ [" N0 m  a PASSWORD_LIFE_TIME UNLIMITED;
$ X( E: x. B7 R. q. Q' O* I