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

admin

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

Problem:
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
: B! b  c" \; _' ]+ o, X7 m! I) Nobtain the following message after 180 days.
4 r7 t* L6 o+ c: s! d- k  _6 hLogin was unsuccessful.: Problems encountered logging into TCServer:
... database
5 n8 V+ Q2 Q9 CCause: Unable to bind to server running on localhost: 1572

, Q' N& D+ T' D. A  k9 c% rAnalysis:
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
# c6 s8 V) w8 Vcorrectly. However, when you try to connect to the database using sqlplus you can obtain the
, F8 r) L: a9 Z( C7 c# T# Cfollowing error message:
3 X- A  s  I; m+ r) f3 VORACLE_HOME=your_oracle_home
8 g; l( F+ V. L8 P1 M& P6 aORACLE_SID=your_sid
) d  R) R" q9 P0 @! N>%oracle_home%\bin\sqlplus /nolog
SQL> connect
3 G7 `9 o2 ?) J; C/ U) g" e' Dinfodba
infodba
ERROR:
; I. h! B6 o/ B' D* |. nORA-28002: the password will expire within 10 days
6 C" O) i% [4 A+ g
In the user tcserver.syslog file we find the error message:
9 `/ K$ d, e# S' k6 P- U6 [! I7 eConnect failed (-28002) for 'infodba' at ***
The "infodba" Oracle user seems to be created using the default oracle profile which has an
8 e6 \, e- R* C- |9 @expiration 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.
  ]" k4 Q. I6 Z7 L9 D% k
9 r# [1 h4 D' |6 D$ zSolution:
Find the infodba profile using SQLPLUS:
% M5 c4 c- t  ~7 _7 {( oSQL> select profile from dba_users where username='INFODBA';
List the profile caracteristics:
SQL> 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:
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
Change 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
4 R/ F+ c9 J" ~7 B5 Fthe time.
) ~* a- j6 T9 c4 G2 USQL> select expiry_date from dba_users where username ='INFODBA';
+ w# ?2 B1 A2 s  D. L=> you obtain an expiration date
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
$ \0 ]* D3 ^5 P6 v# I2 MSQL> alter user infodba identified by infodba ; ( specify your original infodba
# o& _# r. h4 j' b% M- |9 z, Ipassword)
- ]* o6 |7 W# |8 d1 }SQL> select expiry_date from dba_users where username ='INFODBA';
=> you have no expiration date.
' s$ D% ^/ W( v7 V- ~

Remarks:
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable
in %TC_DATA%\tc_profilevars.bat is always alive and correct.
Another modification can be done on the default profile:

* D" x* Q/ A: i8 vALTER PROFILE DEFAULT LIMIT
5 o  ?3 ^6 j/ O4 @ FAILED_LOGIN_ATTEMPTS UNLIMITED
/ r0 w/ N3 R6 h) N  J PASSWORD_LIFE_TIME UNLIMITED;
8 |% Q% ^0 h7 W' x+ X& u