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

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
视频教程请参考plmhome.ke.qq.com
* ?! v: y! G$ ?3 E: E
" ^% u4 A2 w- H  D===Clearlocks======
" P0 _  h1 T' Y6 y) Hclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose
& t/ z+ h( Q6 N

3 Y7 @7 W  W+ x6 O* V4 k11.4 的升级比较特殊，特殊的两部如下：

# ?! K0 z$ Q* }+ I" m9 JREM === Migrate trace links =====
6 c! F1 @9 `( p( |; f6 `1 h% d: H0 `. V8 Q
: `' z, v! c! ]# t; Dreq_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba


====DB =======
+ ^) g! P# S6 O8 M5 R2 g=====backup====
$ o' b5 v4 Y7 p5 r7 C3 H5 G
' n* x  T+ t; D9 b* l; Q: |
REM ==Estimate tablespace requirements for update====
Oracle databases:
1. Back up existing Teamcenter data.
2. 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
3 Q3 Z2 z8 d+ T5 c6 U  ^. GUNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;
! a$ U& ^- W& T0 E7 P- ~) l
b. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
$ A0 T6 e% i1 z: f& ytables, which are also affected by the update process.
' N# R( K$ X% R6 F' M4 E  }4 R, |
Determine the amount of space consumed by each affected table.
4 C* |3 }; c# r3 dFor each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
" Z2 B1 c  b& V+ W# S
% i+ ?! Y: `2 P& `7 J8 f% wenter the following SQL command:
2 d7 O9 q* i- C% F1 f4 IWITH cte1
" {$ `/ N7 h# i, f# jAS (SELECT table_name
7 b5 ~& v3 w3 v% m1 T( n. lFROM user_tables
# X* N8 J; E- F) zWHERE table_name = 'TABLE-NAME'),
2 W( b; P4 ?# U1 K7 r8 G1 `$ \) \0 Ycte2
4 a* o; I3 i1 K3 w- XAS (SELECT SUM(blocks) * 8 / 1024 MB
FROM dba_extents,
1 p' s# G2 b, N! L" @. ?; gcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
0 [+ W9 X( Y/ j1 \7 Z  D) ~FROM dual)
5 F5 J! Z" K1 t8 ^" KAND segment_name = cte1.table_name)
SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
0 h# d4 g4 {9 G1 Z- o7 OFROM cte2;
/ P9 m) w. r% ]& b- e5 ~; _
' M; E6 ?2 N3 P  J0 mReplace TABLE-NAME with the name of the given table.
9 q  i9 d0 C9 t  F4 R
- ?3 T3 H* d5 }6 N' K% y# S" ?
8 z& N( {2 {# s- D
REM ==unzip install.zip ======
" W& R" m) c/ t& X8 X) \
TC_ROOT\install\install\unzip -o install.zip


  O* H" M8 v9 D1 j
REM ===Install patches on a Teamcenter server====

/ ]% }( b: C1 U1 Q% STEM--> updates manager
  {9 o; u* h; K  r7 W
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.
a. Create backups of your current TC_DATA directories.
( a/ R% r# _! G$ t6 @( P' D* ub. 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
7 o; Y6 p( H* e% i. [9 ^( M( |existing files.
9 i- w+ [1 L. k$ Z4 @d. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.
+ ~5 F) H! K$ }4 s8 ]! [




# G/ H! p  F, }5 J* j; k6 U. U: Y
========Patch the rich client using TEM
8 A/ U+ H- [$ X9 ^! N9 h+ U========Patch the rich client using the Over-the-Web Installer
" ]( v8 \+ v- a1 r3 Z
3 |) |- M; n1 B! o
a. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
OK.1
7 D. i9 |7 q( [8 Y! \c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
Parameters dialog box, click OK to begin
" N8 P* t+ B* q5 q4 xpatching.
2 y6 P! M8 k+ }2 w3 Fe. After the patch is installed, click OK to
close 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
1 \3 L) B; Y) F% @5 @to your web server.
1 k8 t$ [% h/ |3 r12. Restart the distribution server.

$ J+ d# W, v1 e$ Y
=====Patch Lifecycle Visualization====
  G8 ~4 Y0 X# O  m* f% ]* @6 D


===Patch the web tier======

3 _2 Y& J, c; a9 h
3 U" C8 v' f" n6 O3 z- T
7 j3 \* K) E% }! m3 ]# s