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

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
视频教程请参考plmhome.ke.qq.com

3 y- R- _0 q/ L+ J* }, p. \===Clearlocks======
* p( m% p6 @  C# }- A( f, Zclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
. d; E0 L; o9 z5 c) q# uclearlocks -verbose

9 x4 _1 U5 H1 E' q
11.4 的升级比较特殊，特殊的两部如下：
( ~( w7 l. Q6 R/ \
. x3 B: X: s5 i$ _. ~REM === Migrate trace links =====
5 X; b5 G! n2 u: \3 y
1 A+ m1 K1 o, f' i# W: L$ k: H+ Jreq_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
8 ?$ x1 G: U9 ]' w9 f, N4 P' m
/ ]; z, y8 p+ x  r+ u
0 r; J& l" ?  e. I4 u+ H( M====DB =======
6 E" O1 J; w4 ]; z" \=====backup====
2 H) R" c6 K; |0 |) G

REM ==Estimate tablespace requirements for update====
Oracle databases:
7 [, f9 B! Q; K; W- n3 ~9 z1. Back up existing Teamcenter data.
# [; W' V# g) C2 ]3 W2 d2. Determine the tables affected by the update to Teamcenter 11.4.
a. Enter the following SQL command:

SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
+ B! L1 X$ ?: a! W# x9 I2 _* nUNION
% O) x) X# X  sSELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;

6 `( n" I' J- b2 n! F2 }b. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
tables, which are also affected by the update process.
' y$ D8 \; ^3 b  @( z$ h
Determine the amount of space consumed by each affected table.
2 J  O. J, {& Z- ?3 F, y" \* BFor each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
( M# W5 B, j/ x2 {, D9 m% a
" ~) g; L6 X7 \7 w$ w- yenter the following SQL command:
WITH cte1
AS (SELECT table_name
FROM user_tables
* G9 U: P9 q) J6 [! Z# WWHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
FROM dba_extents,
7 ~/ T$ V, R7 H/ v. ]& Ycte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
; x2 }  O  @8 ~0 o. Q' zFROM dual)
AND segment_name = cte1.table_name)
SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
7 y3 V$ g# v  k8 h) ZFROM cte2;
. {; P) J5 Y+ \
Replace TABLE-NAME with the name of the given table.

" s' `: a- H7 k# U
) k" X6 \0 n( d. f+ @$ b
1 l0 N0 q7 F# R6 r% \REM ==unzip install.zip ======

+ [1 i! N. {3 H( q) y# |/ lTC_ROOT\install\install\unzip -o install.zip

) \* T3 _4 d  c
% _- m! G) o: T' y4 u  W# T3 Y# Y
REM ===Install patches on a Teamcenter server====

6 Q0 T% N* @6 U( D8 UTEM--> updates manager

REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
% g( X: K, n' j" Q6 O  }
; f8 j- l, b% FAfter the server is successfully patched, you must manually update your TC_DATA directories.
a. 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.
6 }# a4 m& R0 m0 G+ F( Qd. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.
3 X( {3 p( Z- F' P
. l) S! ~) ~/ f9 _7 c% `

9 H7 D# j+ j$ ~6 Y7 A- D

% h# d3 Z2 ?5 ]" _8 ?
# E2 N' [  ?! z; o========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer


a. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
OK.1
# q4 e( `& y2 s; V( u5 z1 Ac. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
. g; g  J5 l: H; y4 J* J# i- ~; GParameters dialog box, click OK to begin
patching.
/ M" c! b% F1 P+ C; b0 E! S$ oe. After the patch is installed, click OK to
- [" S# z  h- _6 s& mclose the Progress dialog box.
9. In the Modify Web Application dialog box, click OK.
10. Exit the Web Application Manager.
11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
% }7 F2 ?6 R( F$ @to your web server.
/ o! `/ d' D; J6 `+ L3 T12. Restart the distribution server.
  ]. O' o  v4 {/ v

=====Patch Lifecycle Visualization====

) A( t2 \" d6 P# T

  g1 [% h# r# e) I===Patch the web tier======
: f4 J7 V; M, @



( X9 W: m) P9 I7 ~