|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user
1 @4 @# N, \& T9 \
1 Q/ ^* o4 I/ H# @( }* ?Problem:
: T# P& a" a I. S1 lIf your Server is using Oracle 11g, the Teamcenter users may have a connection problem and
, \2 I+ L9 v g0 aobtain the following message after 180 days.! N8 ^+ n3 h7 w0 X4 J
Login was unsuccessful.: Problems encountered logging into TCServer:9 f% ?8 E$ [- n& n# x
... database& L' S/ \4 ? l) [) H, r
Cause: Unable to bind to server running on localhost: 1572$ R2 a$ Z* U1 J5 A
% G$ Y* ~( l4 Y, Y o9 B6 |Analysis:
5 K* w5 F+ [7 u- h; F& Q, \! L% RThis issue seems to be due to the Oracle 11g changes. All the Oracle services are started
. L7 |# Q0 F( k/ pcorrectly. However, when you try to connect to the database using sqlplus you can obtain the8 o! e6 @; M0 k+ O& B
following error message:
+ t) c, k' G9 nORACLE_HOME=your_oracle_home
1 E& J" S9 U) u% g& i- O2 R7 F+ TORACLE_SID=your_sid
5 q4 w7 T. p# b6 ^ ]>%oracle_home%\bin\sqlplus /nolog3 M l3 _" Y, D: C! i1 }
SQL> connect9 b: {! l g6 ?, E: h; r
infodba
7 v$ j! Y" F+ J5 N- qinfodba
) \! i. C! D8 h9 D, h; ^ERROR:
7 X: z' m. D3 h" ?1 ^1 BORA-28002: the password will expire within 10 days
+ X- b5 T" i) O5 h- I& T* j
+ {7 R+ {, b2 p x7 j! [In the user tcserver.syslog file we find the error message:
! o2 b8 O( }+ pConnect failed (-28002) for 'infodba' at ***" m/ g3 w( E8 Z# f; H# Y/ ]' g4 q; |
The "infodba" Oracle user seems to be created using the default oracle profile which has an
0 q" I' l J& h' l' ^8 ^expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database
8 X- Y+ D2 @2 p9 V1 |# h Nan error message, ORA-28002, is sent and the connection fails.3 i: l8 r% P$ w# p# V
; z# N1 Y o* C2 dSolution:
$ K# ^8 {1 x9 \8 p# |! y' PFind the infodba profile using SQLPLUS:9 e& V* Q! q" E% M* S
SQL> select profile from dba_users where username='INFODBA';
; Z+ f8 s1 b/ B* I# d' n2 t2 X! rList the profile caracteristics:
$ D7 c# H! G9 u" R/ l% P4 @SQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';
& z7 w0 c. r0 UCheck the PASSWORD_LIFE_TIME.% R1 V0 x2 j( o+ T# k2 o
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
- C) y0 B/ e* X8 Q8 N$ t4 U* J9 WSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;2 ^* [3 Z3 C4 f$ H/ c! F
Change the password. It will not expire again., |2 j6 [( v/ I# ~/ m0 ~* W0 _- ^& d
If you don't change the password, it will expire because it was created using a different profile at* L4 a2 O- w1 ^ o
the time.0 |& q' q4 Y4 _3 f- |$ |" Z7 y' Y
SQL> select expiry_date from dba_users where username ='INFODBA';; }- d! g; i/ ^* q/ d6 Z
=> you obtain an expiration date
$ ]9 o u+ T6 Y5 fSQL>alter user infodba identified by tempo ; ( define a temporary pwd) : q9 \- ]1 e& W3 z# N
SQL> alter user infodba identified by infodba ; ( specify your original infodba
2 D' ~. g- N$ t$ Kpassword)
+ E, m; q. P$ f3 x) zSQL> select expiry_date from dba_users where username ='INFODBA';% O; U+ S y$ b
=> you have no expiration date.3 J( k; q; ~. w& |' M
1 b# a, f& {1 }4 `3 |7 ? g6 i9 G$ o3 E4 o, ]
Remarks:
- S5 G. b4 k+ ?Because we have redefined the same original infodba password, the TC_DB_CONNECT variable" ?% O2 R, g: M/ Q0 C4 P% R" I
in %TC_DATA%\tc_profilevars.bat is always alive and correct., o% S$ `6 w- ]1 G# B9 n" l
Another modification can be done on the default profile:/ W6 N$ C5 m) \
3 O5 d! |% i. V# y
ALTER PROFILE DEFAULT LIMIT
# K' k* P- g4 a/ O2 b; J: P FAILED_LOGIN_ATTEMPTS UNLIMITED' q N; `7 L5 g0 g5 C" v2 N% h
PASSWORD_LIFE_TIME UNLIMITED;
# \7 T% r2 k' s/ q ~3 i; z( F! Y h8 E5 d
|
|