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

admin

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

===Clearlocks======
/ L9 p: ~7 T1 O8 [" k8 s4 Fclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose
. E$ D" E* B+ j0 }+ u5 k+ G

: G3 L% F* ~, p2 W! P: D11.4 的升级比较特殊，特殊的两部如下：
& H' R9 e! b6 Y7 Q: W* L+ Z$ |
7 s9 T- p# h$ f$ p# aREM === Migrate trace links =====
$ A: V+ j+ |; c% q$ Q% S
req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
& K0 |/ D, `. Y9 T

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


: c( J2 l3 E+ F5 K0 k( X: HREM ==Estimate tablespace requirements for update====
Oracle databases:
6 C; K) S& F5 u1 v: I" O1. Back up existing Teamcenter data.
3 [8 |& m; u7 C5 _- [" M  V: l2. 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
UNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;

. J- l; Z" Q0 n: U  A4 F4 o& tb. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
tables, which are also affected by the update process.

0 x2 l5 l4 A1 H, P, @" eDetermine the amount of space consumed by each affected table.
2 p- w, A* X7 vFor each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
% r5 g4 X. y8 z
$ G& v7 l# W. E. Q4 R' Zenter the following SQL command:
0 L; z' J: }- M  T1 F8 ~! ]! |( nWITH cte1
0 g# p: Q4 E! W9 |) ]AS (SELECT table_name
+ [; J  m* F6 H/ `. c) OFROM user_tables
8 O3 k; z/ `3 e- [% U- iWHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
& }- k- w' d9 K8 c$ b# D" u3 |  TFROM dba_extents,
  N6 l2 a0 n1 acte1
0 e! v9 `4 f3 {# s3 Z: TWHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
AND segment_name = cte1.table_name)
; a' w7 x0 [2 kSELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
1 |8 |, n8 n, tFROM cte2;

' R4 D' z( s, X. H8 DReplace TABLE-NAME with the name of the given table.
3 ], L" v7 O' u: l0 {# L


/ q* R" d* g) L/ m( w! o, bREM ==unzip install.zip ======

: n8 B5 n# n: z; ^TC_ROOT\install\install\unzip -o install.zip
2 G/ i! L/ z1 y. H* F1 e

4 x% J- v9 C& @6 Y
REM ===Install patches on a Teamcenter server====
$ K+ v9 d" `& [/ c- g
) ~2 n7 s9 {2 ~3 A1 a4 n3 mTEM--> updates manager

REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
8 q: u, f- x/ M) }3 a$ D3 I
) z! r" U7 k9 X3 k# ~8 IAfter the server is successfully patched, you must manually update your TC_DATA directories.
( n2 d6 d  R8 l$ h0 qa. 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.




& Y! g3 h! k6 f& [
; w: n  b6 u6 u8 ~/ |
========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer

( c4 I$ h' d9 k2 B% ?6 h
0 o7 F2 B: ?3 v) Ua. Click Reinstall Solutions.
4 P& i5 |, u# n- D# p2 [1 {b. In the Reinstall Solution dialog box, click
OK.1
% a  h+ O* I& zc. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
% m! I  p# h, p( fParameters dialog box, click OK to begin
patching.
e. After the patch is installed, click OK to
! B) S, ]; \: Y- M/ l  Zclose the Progress dialog box.
( r: {0 q- c2 \" ]5 x9. 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
to your web server.
2 _1 \: {6 i. C  i/ {/ _12. Restart the distribution server.


2 s; D6 _; M0 M' F% S; v- D% c  X=====Patch Lifecycle Visualization====



# A: h' E# |# Y" S. a" a===Patch the web tier======
# \8 Q. U* E  g- q2 B
* Z/ y5 E" c3 ?6 K
* t1 A; I' J2 q, Q

- T9 ~' V2 N: ?% u0 ]) w