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

admin

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

: [9 b+ T& C6 J! X1 _) h===Clearlocks======
. G8 |  A1 Z( ~) Y; ~clearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose
: l( o. }- ?5 g1 ^1 G3 n

11.4 的升级比较特殊，特殊的两部如下：
6 t5 S; G1 Y) }3 c/ S: a) T
REM === Migrate trace links =====

req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
: \4 c1 y( t( Z2 e/ E$ l+ I# p
* M4 @+ w8 G  B3 K+ |. n
! `1 x3 g/ [# S% L====DB =======
( f( c* f) E$ n6 Q9 H( f=====backup====
' S7 h! G/ P. J! Q2 ]

- T9 r7 N5 {" `- v3 a6 nREM ==Estimate tablespace requirements for update====
4 H- M% W+ ?9 L& KOracle databases:
1. Back up existing Teamcenter data.
' Z: s, h8 ]8 v# y+ y3 m2. Determine the tables affected by the update to Teamcenter 11.4.
a. Enter the following SQL command:
6 T) N% f5 P( H: m" s7 h8 ?; i
) m2 d/ ]. ~4 t0 ~- X% Z( Q9 [% iSELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
UNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;
+ L/ m/ ^5 m6 k
: S+ b  @% q5 V) U: Sb. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
, L- f) h7 ^# z% t8 |tables, which are also affected by the update process.

Determine the amount of space consumed by each affected table.
" Q( z5 g- v8 K3 D: `6 rFor each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
6 H; g) [8 ]( P  `
+ J4 r* p" F& G& G! _5 }enter the following SQL command:
WITH cte1
AS (SELECT table_name
3 W$ j3 t1 N- b, @; P7 T7 hFROM user_tables
0 j# Q6 Y/ o" w  {WHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
3 n. D) S3 S) c  ?4 c4 J8 xFROM dba_extents,
$ a% V& n. H- W3 Q* s( q/ s8 Xcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
AND segment_name = cte1.table_name)
1 K/ e! J& V1 m7 ]! s) F) QSELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
/ b9 t3 k2 S3 j7 l" H3 }FROM cte2;
- h4 a* m, A! o9 V
, v9 w6 r  Z8 a2 m/ r+ wReplace TABLE-NAME with the name of the given table.

0 o, u3 V- p3 ]) Q, ?
8 V% |2 o) A& N1 D
REM ==unzip install.zip ======
, Y+ _! X+ n8 I5 `- ^' p; e
TC_ROOT\install\install\unzip -o install.zip
4 i* d* }  j* H% f; H

: i* m, O) A8 ^" F: w* Z; x, y
9 @9 c0 ]% V! q" d% ^' uREM ===Install patches on a Teamcenter server====

TEM--> updates manager

, \+ u; X- p5 f$ E" s. `+ uREM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip

$ b" x/ k; L7 V. k& ]) Q7 jAfter the server is successfully patched, you must manually update your TC_DATA directories.
a. Create backups of your current TC_DATA directories.
% M  V2 r- g; }* g. S- C) Bb. Expand the platform\tc\data.zip file from the temporary location you created in step 1.
$ i1 I& o' Q4 U- h0 s  bc. Copy the expanded contents of the data.zip file to your TC_DATA directories, overwriting
existing files.
( T9 o  G, \2 R7 sd. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.



  j9 W) o# p5 _( T4 n! U8 o) u1 @
5 M6 \# T& A7 J$ U9 X
+ Z9 d- R5 p) Y7 A' ?! e
========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
- d% ]0 M" t) {" Kc. In the Confirm dialog box, click Yes.
+ E0 y$ p, v5 `) r) r; ^& d; G  pd. In the Modify Required Context
Parameters dialog box, click OK to begin
3 O/ a3 J& X' l! L) npatching.
e. After the patch is installed, click OK to
close the Progress dialog box.
9. In the Modify Web Application dialog box, click OK.
# k& `9 u% S" L4 ~/ G10. Exit the Web Application Manager.
11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
to your web server.
12. Restart the distribution server.


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

/ j5 W. g/ T. p4 m
2 A+ O$ t) g  K5 n
===Patch the web tier======
3 w& x8 ^' I: X6 B

# I) d9 Q; v# O: C
2 @. L) `" b: r( M5 c* Q
, H  Z+ A. P: n3 j9 _
+ f& {0 ?8 m, n6 o& Q" [) Y