Teamcenter11.2 升级到 Teamcenter 11.4 图文教程

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
5 n  P% ]3 z3 U视频教程请参考plmhome.ke.qq.com
+ _6 `8 k+ @0 W
===Clearlocks======
clearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose
0 A3 ]( l) U( i5 n/ Y1 c

$ r" L6 [3 _, z* P) T& u" b9 U; C11.4 的升级比较特殊，特殊的两部如下：
- ?5 B$ O! B$ q% T
  X. y/ }# K" {% O  kREM === Migrate trace links =====

! n. w6 u7 Q0 |0 j# L" ureq_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
5 c$ E6 g0 x& H* Y- d! k) Q& }

====DB =======
=====backup====


8 q3 h/ s3 j  ~9 w# BREM ==Estimate tablespace requirements for update====
/ _+ x4 d0 Q# t4 a: ?Oracle databases:
2 u  ?  y1 g; T, D* G' {0 q1. Back up existing Teamcenter data.
2. Determine the tables affected by the update to Teamcenter 11.4.
7 f1 L. g1 X: Y" Q, M8 Aa. Enter the following SQL command:

SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
& x/ S# k5 l1 u" X1 ]8 L& w, P" O8 vUNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;
3 s3 g7 _; ^3 `# E, I. _
+ C; g  C4 J) kb. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
tables, which are also affected by the update process.
* d, K7 D, x! A$ G
6 e( p3 l9 F% J/ R- bDetermine the amount of space consumed by each affected table.
7 }6 j2 J* H. P) [For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),

enter the following SQL command:
, J. ~+ ]: F8 WWITH cte1
2 |( K% g% N& W- s; ?2 LAS (SELECT table_name
FROM user_tables
6 S' h- w: P; c' N  w/ gWHERE table_name = 'TABLE-NAME'),
% Y& ~& S, F% q9 H' h5 Gcte2
" i( g# y8 }* X0 i4 W% LAS (SELECT SUM(blocks) * 8 / 1024 MB
FROM dba_extents,
( x. N7 [% g: m0 v& Kcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
7 h( B" }' [# k' p; R: Y% [FROM dual)
AND segment_name = cte1.table_name)
. Y. P& k% X- a! j3 |1 W, rSELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
3 u8 i# L4 ^# g4 QFROM cte2;
, ?/ I9 F1 ~5 ]; S. r  U
Replace TABLE-NAME with the name of the given table.
5 b1 U: Q3 z" _
' q- l. R7 g( h1 b# ?" d0 a2 h
$ g: _! Y/ ~" b; ~
REM ==unzip install.zip ======

, |) C. J- {- M$ ?0 h5 Z. \TC_ROOT\install\install\unzip -o install.zip


% `/ Y' X" Q# X7 }6 a( c! G
6 [. U$ ]5 S) `; Y9 r; M! PREM ===Install patches on a Teamcenter server====

1 Z1 a4 m: f1 c. S1 a" `' }/ Z7 A! JTEM--> updates manager

REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip

After the server is successfully patched, you must manually update your TC_DATA directories.
# Z3 ^2 D; h7 R/ M3 Va. Create backups of your current TC_DATA directories.
b. Expand the platform\tc\data.zip file from the temporary location you created in step 1.
c. Copy the expanded contents of the data.zip file to your TC_DATA directories, overwriting
existing files.
d. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.
( r. c0 s) v! y0 V
, L6 R& ~3 \2 e2 T. b1 W" v




========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer
3 ^# O" h0 s% h$ d

7 S9 l5 r2 s& O# x4 ua. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
OK.1
9 x1 j4 p. l3 S' H% Bc. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
* a) a( `. Y7 i, m7 I" eParameters dialog box, click OK to begin
: k7 R7 `, C; _# z7 a" Cpatching.
e. After the patch is installed, click OK to
4 ^+ ?2 o9 q8 W4 Dclose the Progress dialog box.
9. In the Modify Web Application dialog box, click OK.
3 d) b& l2 b( R, G) B  U: U10. Exit the Web Application Manager.
3 n: \% T8 Y3 h5 @: A6 A: y8 x# ]11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
& L# r0 H5 g# Xto your web server.
12. Restart the distribution server.

7 p; ^% |  ?* t0 `" f3 i* \
4 Q& @" j4 a$ T3 m. X+ U=====Patch Lifecycle Visualization====


% N8 N' T* D2 \
===Patch the web tier======
. E% U; H  Y  ?( X