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

admin

Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
5 I/ z7 Q7 m0 V7 ~& Y" A! t
Problem:
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
1 F, i- N7 ]5 a2 D) r# [7 Aobtain the following message after 180 days.
Login was unsuccessful.: Problems encountered logging into TCServer:
... database
Cause: Unable to bind to server running on localhost: 1572
6 a1 x% f" P8 A- `9 ^2 B! J1 w
0 }4 r& x+ K" @8 H. R& cAnalysis:
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
3 C! S6 b  Q- e# r; P" `correctly. However, when you try to connect to the database using sqlplus you can obtain the
) \. I$ P2 h) S  f& h/ M- z: Ffollowing error message:
ORACLE_HOME=your_oracle_home
1 x8 q; I1 }% `+ yORACLE_SID=your_sid
! ?6 F" i% Y0 O+ c" m>%oracle_home%\bin\sqlplus /nolog
- K, W) g  d; LSQL> connect
" ~1 G, R' Y2 N. Linfodba
infodba
ERROR:
, z0 j1 i/ h3 Q  MORA-28002: the password will expire within 10 days

In the user tcserver.syslog file we find the error message:
Connect failed (-28002) for 'infodba' at ***
' a0 H" \2 y" E$ R7 qThe "infodba" Oracle user seems to be created using the default oracle profile which has an
" v, m% ]$ E7 ^( j! sexpiration 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.

Solution:
Find the infodba profile using SQLPLUS:
5 t. f+ D% ?5 b$ |% a- r8 H* ZSQL> select profile from dba_users where username='INFODBA';
% f; e4 B9 F9 D1 ]List the profile caracteristics:
& W2 Q5 r3 e  v3 ^0 PSQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
Check the PASSWORD_LIFE_TIME.
5 k' ?: Y; u8 {; UModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
7 w* X5 w. \+ E8 }1 p% P: Q! bSQL> 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
the time.
SQL> select expiry_date from dba_users where username ='INFODBA';
1 v) j9 ~% S( a8 F=> you obtain an expiration date
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
) A1 {- ?# s" G- }( c. E% ?0 mSQL> 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 f/ ~0 w" P; N# W% I
! P/ I2 Q% ^1 d8 MRemarks:
0 d; z+ O7 G8 y7 {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:
5 x  S( n. K. U- g' U% u# ?( c( G
8 `2 N1 {( Z2 \. ~- a; Q& NALTER PROFILE DEFAULT LIMIT
7 n2 ~1 N4 n  ?1 X% q( C( V8 f0 I FAILED_LOGIN_ATTEMPTS UNLIMITED
PASSWORD_LIFE_TIME UNLIMITED;