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

admin

Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
, \) m* e2 Q9 \4 \; @- v6 T
1 b) d* d8 R, a$ g  CProblem:
" T0 H) a) W" u$ p' B) K+ ~If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
& M. A# \4 |$ aobtain the following message after 180 days.
Login was unsuccessful.: Problems encountered logging into TCServer:
6 r4 `/ }1 y( h* B9 A; K ... database
9 A& E; _0 o/ W. Q' @Cause: Unable to bind to server running on localhost: 1572

7 C9 O7 C5 d0 ?) S" F7 J4 oAnalysis:
# f# }' i: X$ F  VThis issue seems to be due to the Oracle 11g changes. All the Oracle services are started
3 Q2 K$ g3 x( O$ acorrectly. However, when you try to connect to the database using sqlplus you can obtain the
$ S3 T. h7 N3 e8 I' h1 R" bfollowing error message:
ORACLE_HOME=your_oracle_home
ORACLE_SID=your_sid
>%oracle_home%\bin\sqlplus /nolog
SQL> connect
infodba
infodba
. L  Q) @- \- Q6 P2 f7 e: `" b' `ERROR:
ORA-28002: the password will expire within 10 days
* G+ Y0 D4 m) ]) i7 E
+ D. ~( D! ^* Y; `) b  c/ ^$ s' HIn the user tcserver.syslog file we find the error message:
Connect failed (-28002) for 'infodba' at ***
The "infodba" Oracle user seems to be created using the default oracle profile which has an
% _4 h+ ]5 s( P  V1 c+ I3 _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.
( B( D/ C( ]/ _; N, h
Solution:
( [0 H, M9 L) n3 U; vFind the infodba profile using SQLPLUS:
0 C2 z9 x, @' ?* Q4 CSQL> select profile from dba_users where username='INFODBA';
5 n) t1 `# z0 H7 C& k) ~* k  PList the profile caracteristics:
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
Check the PASSWORD_LIFE_TIME.
: ~! f7 ^0 B3 @% p; \: L" KModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
. ~; o! a" X9 ZSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
3 Q$ l' R% M9 y8 D8 {% `, \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
& X5 z; x% s# N% C; l* Y! Fthe time.
SQL> select expiry_date from dba_users where username ='INFODBA';
! o: ^, T: G, P2 S: Z% D=> you obtain an expiration date
% z) `7 ?2 f  c+ QSQL>alter user infodba identified by tempo ; ( define a temporary pwd)
3 }* f6 a0 z) N* X8 USQL> 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.

$ g6 F# v: t2 V8 P/ Z6 J  V  Y$ a1 Q
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.
4 b) G; N; u# N1 m: nAnother modification can be done on the default profile:

+ D4 {' F* m$ |; t& F) sALTER PROFILE DEFAULT LIMIT
FAILED_LOGIN_ATTEMPTS UNLIMITED
PASSWORD_LIFE_TIME UNLIMITED;
: P0 y* d9 x+ D0 V
3 T. y1 O) Z! x1 r- _3 o" z& b