|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
) F1 k0 G& r6 r0 q" c; p) k0 Z1 z- ~( w) M% ]. J
Problem:
6 e6 k. ~3 G7 `0 w" O6 Z3 OIf your Server is using Oracle 11g, the Teamcenter users may have a connection problem and2 c* g- z$ B. S k$ H" e. w
obtain the following message after 180 days.3 B9 ~( [1 Q5 s8 H/ Y
Login was unsuccessful.: Problems encountered logging into TCServer:1 K0 \! F" D# G0 H) V
... database
. |; ?, Z; F5 l0 pCause: Unable to bind to server running on localhost: 1572
6 x8 v( F) R( u. \$ G5 v: {6 c3 I: A" Q% e& J
Analysis:
$ i! H9 d! V( O9 L# h% f% i; ^This issue seems to be due to the Oracle 11g changes. All the Oracle services are started0 c" A3 [) t5 @6 r; D2 u
correctly. However, when you try to connect to the database using sqlplus you can obtain the0 D5 ]- l1 K. }: q# M8 K
following error message:
, C5 R9 f7 B- F& I/ qORACLE_HOME=your_oracle_home" z3 T0 h8 I6 P6 q/ X! ^
ORACLE_SID=your_sid0 a! X& B! z% M
>%oracle_home%\bin\sqlplus /nolog
; Z2 Z# W/ o) @/ Q# i8 ^+ K5 S7 LSQL> connect9 z! B4 B. e, ~% q
infodba; ?4 G9 N' T2 O! x, _4 r
infodba: T7 s4 t+ _/ U( \2 W! F& q
ERROR:2 I$ K# {" }+ v H/ ] Q
ORA-28002: the password will expire within 10 days0 |) {& w& E) I( j# i6 C
1 N. C) W3 M4 CIn the user tcserver.syslog file we find the error message:
; q6 H3 b1 a/ f6 EConnect failed (-28002) for 'infodba' at ***
- q) p/ k# \ AThe "infodba" Oracle user seems to be created using the default oracle profile which has an" j0 J* N# e& e% R% z \
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
) s7 Q2 b* Z! Q& X3 v* W/ wan error message, ORA-28002, is sent and the connection fails.
5 A0 I% w' e3 M+ C/ s) \0 F" R
6 ?" k( C' X/ n) j USolution:# B. h7 J3 x: J# n
Find the infodba profile using SQLPLUS:9 u# W' \+ X! E/ S! }5 Q
SQL> select profile from dba_users where username='INFODBA';
$ W7 K3 E4 v1 hList the profile caracteristics:/ K5 T3 ] J* V/ |) x
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
# u7 k1 D& `, @) L/ _2 C m# wCheck the PASSWORD_LIFE_TIME.. z, r3 ~, H# [; W9 { g B
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
1 `1 _* Q+ l3 A: O' d$ [0 b3 ASQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;. Y! }$ q: G1 P$ M" T6 b
Change the password. It will not expire again.
, w3 G( j) w# M" {+ W4 q% H$ cIf you don't change the password, it will expire because it was created using a different profile at$ w# [! p4 H4 u, j) b9 G% H
the time.5 O0 {% S$ r7 D4 q$ u& L9 s
SQL> select expiry_date from dba_users where username ='INFODBA';$ a) C8 k2 H7 L+ y/ T/ L5 d
=> you obtain an expiration date {' u1 A; E4 I" u+ z
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) ' [7 X3 J, w1 z2 A) O& M: z# S) y9 o
SQL> alter user infodba identified by infodba ; ( specify your original infodba$ h. \: w! e8 B: i
password). z( u! G1 E* j3 U+ B8 l+ e' O
SQL> select expiry_date from dba_users where username ='INFODBA';
! y) s; t+ s/ x, Z=> you have no expiration date.3 J9 i6 G" Y9 I$ g! }$ N
: Q, q# c0 c' M; `6 F
H R7 Q6 W, R7 T% xRemarks:9 F3 Z: d0 s! w
Because we have redefined the same original infodba password, the TC_DB_CONNECT variable* a: C5 [) Z; N: k2 ]$ o: D$ n
in %TC_DATA%\tc_profilevars.bat is always alive and correct.' C' r2 L3 p p- ]0 i
Another modification can be done on the default profile:
5 }4 _; ], f; [- W, _- d' J k+ S3 P8 G* \- F7 t( I" H0 u. t
ALTER PROFILE DEFAULT LIMIT
% U) l/ r2 n u8 _ FAILED_LOGIN_ATTEMPTS UNLIMITED+ I% G0 Y' O4 @
PASSWORD_LIFE_TIME UNLIMITED;
, m- w1 P8 T: [ l+ ?' S8 Y6 @2 k' x5 W* h: k( L4 Z: c, _4 I
|
|