|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
Teamcenter - Oracle 11g and the expiration date for "infodba" Oracle user+ h3 \9 P0 o- u: X8 q7 @! t$ s3 p) X
- L. z5 t" ^& L. \6 A- }3 B( E
Problem:7 h' Y- R! ~+ `' m
If your Server is using Oracle 11g, the Teamcenter users may have a connection problem and- c7 V- S$ x# ]' P. B0 ^1 P
obtain the following message after 180 days.9 O& ^3 @4 W6 g* g" ~
Login was unsuccessful.: Problems encountered logging into TCServer:
; v7 s% F1 Y0 m9 N/ h: ~ t, D ... database
1 y4 v/ z% s- ]1 }. K4 n) `( BCause: Unable to bind to server running on localhost: 1572
0 ^% d/ ], O' T7 c; A$ j" u ^1 ?( t
) h( @5 ]) w* ~, GAnalysis:( |4 ~4 H; c- `' D
This issue seems to be due to the Oracle 11g changes. All the Oracle services are started9 r8 }& S/ Q' T1 K5 m: s
correctly. However, when you try to connect to the database using sqlplus you can obtain the
$ L) j `, t/ y2 H: I$ Lfollowing error message:" U6 q' C0 a' [$ N! B# o+ V
ORACLE_HOME=your_oracle_home
) H9 J$ O: D+ G5 @, ]; RORACLE_SID=your_sid
8 X7 K: r/ w) B, l% B% H% |7 r>%oracle_home%\bin\sqlplus /nolog3 W9 d$ Q W. }# A: i9 G. r! ^
SQL> connect
/ t2 U% C; H0 P& finfodba5 F n. U4 k4 E# ^
infodba
& `, D2 f: o' L" Y+ ?% i& MERROR:
( y) X' Y5 a3 ~, ZORA-28002: the password will expire within 10 days
0 m5 S( y, [2 m! s% M3 A$ C/ V' X: K0 }, J$ ^
In the user tcserver.syslog file we find the error message:
9 H) A% o6 Q* `1 K$ L* P7 g# GConnect failed (-28002) for 'infodba' at ***
3 ~4 ]2 U, B, H% YThe "infodba" Oracle user seems to be created using the default oracle profile which has an' X% [2 p9 a7 T! G0 `6 S( }, I
expiration date of 180 days. When the Teamcenter user tries to connect to the Oracle database: R$ C7 Y: x; s- [& n, q" {
an error message, ORA-28002, is sent and the connection fails.! h& c4 O2 d. L# X- P
3 G1 R) s* H4 n+ m' n" eSolution:4 F) I) t7 i Y, w$ h! K) d
Find the infodba profile using SQLPLUS:) S4 B$ r% Y3 x i2 H P* h
SQL> select profile from dba_users where username='INFODBA';$ r9 `1 M( J! V0 u4 E
List the profile caracteristics:
3 O1 S' |& `+ r6 A8 ZSQL> select resource_name,liMit from dba_profiles where profile='DEFAULT';8 a! k @9 m7 f+ S* D( J2 \4 R' j8 h6 f
Check the PASSWORD_LIFE_TIME.0 t8 P. J% [# E! H
Modify the profile and specify an unlimited PASSWORD_LIFE_TIME:
9 x9 D6 X) x" j/ b* W9 PSQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
* U4 B/ k0 ^) _+ M, j) {; XChange the password. It will not expire again.
' _) E6 d5 ^, E4 ?- SIf you don't change the password, it will expire because it was created using a different profile at
% ^, ^( }) V- Rthe time.
5 u% ~& g; v+ R0 d+ ~SQL> select expiry_date from dba_users where username ='INFODBA';
* G7 D7 [+ t8 l# s/ H=> you obtain an expiration date( }. G; M1 j# Y- U0 ^0 L" S- d" |
SQL>alter user infodba identified by tempo ; ( define a temporary pwd) ! T" t% ?. W, S" W( @
SQL> alter user infodba identified by infodba ; ( specify your original infodba; a, E" A) c/ C& N% F7 y% l
password), T+ E) [ i! [# A% w
SQL> select expiry_date from dba_users where username ='INFODBA';
2 g3 t3 R* T( l0 H1 }. T; R( q=> you have no expiration date.% R/ t6 @9 T7 a/ k
6 D! F7 Q+ H6 A9 b I1 S
) l' b; H$ ]# M3 X2 ^Remarks:
w) w' X Y9 d7 Q7 ?) I) Z6 RBecause we have redefined the same original infodba password, the TC_DB_CONNECT variable; B( ?! R: [+ H8 ]& i/ T
in %TC_DATA%\tc_profilevars.bat is always alive and correct.) r$ g6 T5 ^; G9 v9 [
Another modification can be done on the default profile:
! ?. |9 U4 S5 E( b4 V# J. m6 |* Z3 V3 R$ e6 X
ALTER PROFILE DEFAULT LIMIT6 }9 S( a6 R1 L* e7 L9 [2 H+ s( b
FAILED_LOGIN_ATTEMPTS UNLIMITED
9 Y7 {1 O$ Z7 i0 n7 Q PASSWORD_LIFE_TIME UNLIMITED;/ O j9 ~3 P* X" |. p. h
: E+ P. t4 H0 j. W/ I C& n/ a
|
|