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

admin

Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
- |5 F9 Q: Q4 E' U* W6 K
Problem:
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
( Y  X  G( j9 Tobtain the following message after 180 days.
Login was unsuccessful.: Problems encountered logging into TCServer:
... database
% N  W/ {5 O1 J# C- z% rCause: Unable to bind to server running on localhost: 1572
2 d. T* a( e8 ^' _( d
) R0 m, |) P! o2 J4 Q: ^Analysis:
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
& S8 r: O$ ^* P/ Z/ ?correctly. However, when you try to connect to the database using sqlplus you can obtain the
" @/ o# n2 t0 Y$ y/ m9 }8 _" zfollowing error message:
ORACLE_HOME=your_oracle_home
ORACLE_SID=your_sid
>%oracle_home%\bin\sqlplus /nolog
4 Y' I' V6 w: m5 d7 qSQL> connect
7 r' r, t% ]/ X0 K& y5 g( f. Binfodba
' i5 R: G, z6 J+ e0 ]infodba
ERROR:
ORA-28002: the password will expire within 10 days

1 V  O. C2 n9 u7 ^3 \/ R0 TIn the user tcserver.syslog file we find the error message:
( M( x4 M7 U: C0 S  {: mConnect failed (-28002) for 'infodba' at ***
The "infodba" Oracle user seems to be created using the default oracle profile which has an
4 |  K; S! v7 t0 U+ W% c9 _expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
( J( f9 `# R7 M$ `an error message, ORA-28002, is sent and the connection fails.
! B9 ^" `1 `6 J. R
, l) S) U7 c* `5 }/ ?0 MSolution:
2 M2 ~5 |$ J( l+ I) P, mFind the infodba profile using SQLPLUS:
SQL> select profile from dba_users where username='INFODBA';
List the profile caracteristics:
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
+ }7 M9 z/ X8 ~6 d( t; bCheck 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.
) A' O( y$ ?$ yIf you don't change the password, it will expire because it was created using a different profile at
7 y0 j7 ~) G. ]. qthe time.
; e2 F( @, }' Q5 wSQL> select expiry_date from dba_users where username ='INFODBA';
=> you obtain an expiration date
& K) x! Y* m0 ^  MSQL>alter user infodba identified by tempo ; ( define a temporary pwd)
: u6 U. L* O1 Q: {6 }/ ]3 J& nSQL> alter user infodba identified by infodba ; ( specify your original infodba
$ d7 [* o3 T/ s( Y, s7 zpassword)
. ^) S) r! N7 iSQL> select expiry_date from dba_users where username ='INFODBA';
=> you have no expiration date.


Remarks:
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable
9 K: ~+ U' Z$ o2 ^+ v) `in %TC_DATA%\tc_profilevars.bat is always alive and correct.
1 L2 t2 F3 Q! l7 tAnother modification can be done on the default profile:

" n. P: N$ v3 ~. x( E& u; e4 n& BALTER PROFILE DEFAULT LIMIT
1 G2 F* p& C9 s$ l4 ]0 P6 L; O FAILED_LOGIN_ATTEMPTS UNLIMITED
0 N+ y) u/ j1 J: j7 O1 h: ^- k PASSWORD_LIFE_TIME UNLIMITED;

" }5 l3 i, ^3 j