|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
5 @. [. A$ W' [- c& q L4 b2 k
Problem:
) H2 ]0 i8 x ]; G2 x3 X+ @If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
" T n- `0 Z* {: X7 }8 sobtain the following message after 180 days., L. T: a1 V5 B2 G2 S
Login was unsuccessful.: Problems encountered logging into TCServer:3 m A% J4 R9 h5 v0 F
... database
1 w/ W& G2 S8 w6 q/ v9 h* _Cause: Unable to bind to server running on localhost: 15720 @3 a3 [+ @! `
- v2 q# p8 X5 ]0 z* \% y1 P2 b1 MAnalysis:9 ]" z8 p' X6 x* [/ W* ]% J
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started( S" B# q6 P$ N, o0 `3 o: E
correctly. However, when you try to connect to the database using sqlplus you can obtain the6 h( ?# s" Q7 t# g: ~# X
following error message:/ T/ `. z. W) C M$ {
ORACLE_HOME=your_oracle_home
# M1 D" Z! A& V5 I( ?ORACLE_SID=your_sid
9 O* m: x; {: N6 o. r>%oracle_home%\bin\sqlplus /nolog
, h) p( A' v; q- L' J9 k4 gSQL> connect
( l' ~! A6 K& v$ s4 e& ~infodba$ G4 r7 U* u9 h( B6 u# [* z
infodba4 W6 j( n8 W( P- F9 C, m) F# T/ `7 k
ERROR:' t' Z2 d# f" X* o* p* Z! G
ORA-28002: the password will expire within 10 days" a& |& [- Z" {2 c; o
' j2 H$ T# y1 E& G6 b9 l$ S
In the user tcserver.syslog file we find the error message: |1 T7 V- |6 Z( ^3 U1 r7 x" z* V1 ?& m
Connect failed (-28002) for 'infodba' at ***
! V: X9 C* q3 ~; D+ @" ^& eThe "infodba" Oracle user seems to be created using the default oracle profile which has an" G% O3 ]. v+ w5 c/ Y) h
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
3 H9 y5 Y2 G/ S# I- San error message, ORA-28002, is sent and the connection fails./ V: u7 p f% B2 {
4 S4 L( K6 t; mSolution:
# @( w @6 H5 rFind the infodba profile using SQLPLUS:8 C9 I# B7 o/ @ U- n2 m4 B( y( A; w
SQL> select profile from dba_users where username='INFODBA';( c' n, S1 m$ ] ^* j
List the profile caracteristics:, C. P O! l( m/ G
SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';0 d4 s: r3 N9 C( Y! x$ m
Check the PASSWORD_LIFE_TIME.
: {4 ^# n3 c& Z. VModify the profile and specify an unlimited PASSWORD_LIFE_TIME:
9 N, I: X9 ?6 {+ qSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;- q/ E) o n+ W0 `
Change the password. It will not expire again.
5 l! ?$ D( b$ YIf you don't change the password, it will expire because it was created using a different profile at2 ]6 }5 K5 a5 p: ^6 Q0 Z; D
the time.4 @0 _- S H5 F1 A
SQL> select expiry_date from dba_users where username ='INFODBA';6 r9 C6 L3 s) j7 A. d/ D
=> you obtain an expiration date# t. M& h! P5 w5 M
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) ; E7 Q: c7 M& ^: B* ~
SQL> alter user infodba identified by infodba ; ( specify your original infodba* S- o, V5 ~0 C; `1 ^+ V1 S( r1 o
password)4 x1 T5 H/ {/ Y8 x9 l( Q% |, y4 G {* w
SQL> select expiry_date from dba_users where username ='INFODBA';
) P) X/ N, L6 B; }- C1 l0 G=> you have no expiration date.
$ d2 T4 I7 {% b8 [. m* G( r+ H* U
' M' m' F g4 S# `# @1 j% B& s
% j% H0 k+ |+ \" u3 rRemarks:
5 G( O& J( ?( M) z7 j- v b/ x( NBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable
: t7 c4 @" ]# {in %TC_DATA%\tc_profilevars.bat is always alive and correct.
" s6 R! f& v4 ?: R: n" C2 L% d; `! vAnother modification can be done on the default profile:; B3 w. k) H; d$ e. O
; G, b+ K5 }! v8 G" v% c' W( UALTER PROFILE DEFAULT LIMIT
1 h4 C, B0 [7 b+ B( S FAILED_LOGIN_ATTEMPTS UNLIMITED# G$ o3 r- l. v2 ^& t1 `4 } b
PASSWORD_LIFE_TIME UNLIMITED;) |% q" y+ C( H a1 l" k
4 I7 [9 a5 B5 t) M0 p; U2 Y6 d9 S( O |
|