|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
8 W5 C0 ]/ M7 W
; ]; c% J" y, F. x, C* pProblem:* x/ Y) }' f; p$ }" z# H
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
: t! z7 o5 |1 u6 ^7 w/ R% q8 Cobtain the following message after 180 days.
- `3 g+ `! n' I3 B1 C, x- cLogin was unsuccessful.: Problems encountered logging into TCServer:
% ~$ K* c* A5 ?" X* z3 i ... database
- L$ ^ r# r' `! r; xCause: Unable to bind to server running on localhost: 1572
% Y5 E6 S5 K0 U" g
- p4 G# x: z5 f# R5 u" M0 ]Analysis:9 _* P1 o9 H2 d( a6 ^( u; O, P
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started
T) q8 Z- o8 Y" E( a" B: kcorrectly. However, when you try to connect to the database using sqlplus you can obtain the3 H k( s O" o$ V$ J
following error message:
5 y5 z W; l# M* F2 DORACLE_HOME=your_oracle_home
9 }, x( C3 G. N$ |) yORACLE_SID=your_sid
0 |+ Z6 T& S+ y$ u, I8 Z4 V>%oracle_home%\bin\sqlplus /nolog. b$ `( c1 v. L$ Z
SQL> connect
+ M: N0 |( L+ l" A7 ginfodba4 t) p/ o* t' A$ ^- W0 V
infodba
. _, H" z2 Y* M( [6 b2 @ERROR:8 Z' _( w# d8 V
ORA-28002: the password will expire within 10 days: U+ p u( X: W8 f0 o( i
( d$ b) I4 |1 [9 `* C, D$ g& Z# P
In the user tcserver.syslog file we find the error message:
8 a. C: v* c! h( T7 ]Connect failed (-28002) for 'infodba' at ***5 U# y( o% G% `+ }7 G: Q% G
The "infodba" Oracle user seems to be created using the default oracle profile which has an
9 f: f! f( r3 c# mexpiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
3 u2 k7 R$ S5 m: f1 Z- Aan error message, ORA-28002, is sent and the connection fails.4 z! ~2 v8 y$ W% O. T4 a% b0 v" B" j8 Y
! P$ y7 _' N! \6 V4 n0 h
Solution:1 s/ m* M2 ~/ y) Y# l
Find the infodba profile using SQLPLUS:$ G6 f( V/ K# m4 N# \. x
SQL> select profile from dba_users where username='INFODBA';+ I D- q* {2 T/ ~3 X
List the profile caracteristics:5 B) p l: ^ y$ F! _# w
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';# c1 Y9 S! B& m+ T0 m
Check the PASSWORD_LIFE_TIME.
8 t' ~5 a8 v) U6 Q5 {% SModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
0 a5 e {0 e h# o! TSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
& J/ T; b' d; ^" s+ {6 C' @2 PChange the password. It will not expire again.$ f4 `: R, I( ?, u! J, L
If you don't change the password, it will expire because it was created using a different profile at
* t( e8 A6 C+ P6 ?the time.0 \/ z0 |8 L% O) p" E& p
SQL> select expiry_date from dba_users where username ='INFODBA';
4 Y7 X2 o$ q8 f; P+ F+ k=> you obtain an expiration date7 H$ @5 t8 Q5 K) x5 Q9 E0 w
SQL>alter user infodba identified by tempo ; ( define a temporary pwd)
$ y- N3 u# @' D5 }$ Z& c& |SQL> alter user infodba identified by infodba ; ( specify your original infodba( Q6 \% Y, ?) \, t) h4 P) Q/ J% T
password)
; Y( s+ ] G$ |+ _6 aSQL> select expiry_date from dba_users where username ='INFODBA';* s+ Z6 }% N4 R" M( v
=> you have no expiration date.
9 O0 ?: U; Q e7 n$ U9 j/ p7 z$ B3 M. I) @" v* b7 `
1 p2 B3 w- B1 T! \1 \. b: P& k
Remarks:4 r' l/ @6 R3 h! w5 y. J8 V
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable8 C& C( [: L- N A; l
in %TC_DATA%\tc_profilevars.bat is always alive and correct.
# a; j& l9 e5 b" n k% \ PAnother modification can be done on the default profile:
2 p( V: g, K: M: \2 \, C x; K
8 @) j. r- F# G( Y3 B; X1 ^ALTER PROFILE DEFAULT LIMIT. [! @ ]7 o& P$ j% c% ]3 Z
FAILED_LOGIN_ATTEMPTS UNLIMITED5 s1 R) P1 ?, {2 T3 G
PASSWORD_LIFE_TIME UNLIMITED;- s: a2 m0 P6 O8 P R
1 x8 e9 N( |; _( n+ s R+ S3 q+ [ |
|