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

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
9 b) M2 T) C. q视频教程请参考plmhome.ke.qq.com
" S7 P  Z( b: U8 F5 ?, s7 H8 @8 e
===Clearlocks======
clearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
' k. h: V8 b' a/ kclearlocks -verbose
% Q6 D- F6 Z8 Z6 D1 M' ]$ E# d: c
9 Q% U& K) c! q! M% y% ]" x
11.4 的升级比较特殊，特殊的两部如下：

REM === Migrate trace links =====

: U  {& t! H- L# s6 [9 creq_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba


- h; U& w+ B$ F5 S; ]====DB =======
=====backup====


3 x3 S$ Y  c8 t. Z7 L( }REM ==Estimate tablespace requirements for update====
& W; Y" u1 x4 b8 y8 [2 {0 h) w5 TOracle databases:
9 G0 M1 c6 P7 }8 p3 j1. Back up existing Teamcenter data.
7 _1 u& y$ m3 d! W& y2. 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
+ h' D6 x3 w0 V9 _, a2 DSELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;
+ S, L! a' s- b/ N
: w8 ]" c& h$ G; nb. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
tables, which are also affected by the update process.
9 m$ {% b3 x" K9 `# S: I
3 W! S4 X! z  sDetermine the amount of space consumed by each affected table.
For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
0 Y; ^2 K( s! j7 Y( z! ^; m
* d) t# m% z! U3 N5 y* Aenter the following SQL command:
WITH cte1
- }3 a: R2 A; U0 {% D0 aAS (SELECT table_name
FROM user_tables
: u( p) j/ G* I) HWHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
1 D2 t7 N  G$ f& KFROM dba_extents,
/ U# E4 Y! _7 J% b, R5 octe1
4 F- D: E, H* nWHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
# c1 S- ?% V. _% `% zAND segment_name = cte1.table_name)
# g. V% P2 I5 M& k1 Q1 C' ]SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
8 T/ q2 H: F9 P! w  k! j- ^2 XFROM cte2;

7 }# b7 z: T: Q6 i/ T( IReplace TABLE-NAME with the name of the given table.
# Q6 ~# I* S2 ~. u: D8 m; Z


/ @& O' T7 y$ ^" {8 `5 s1 l1 @9 D: s" cREM ==unzip install.zip ======
4 K0 c) L% K5 K; C3 G
  W1 B, R  @( @7 L8 ~TC_ROOT\install\install\unzip -o install.zip



8 s% T7 n! h  z( w+ r/ hREM ===Install patches on a Teamcenter server====
& W3 Q: x* ~, a* V5 T) H
TEM--> updates manager

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

  v8 }% Y+ H3 {3 e# D$ {After 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.
- @1 m8 z5 h- Pc. Copy the expanded contents of the data.zip file to your TC_DATA directories, overwriting
existing files.
, A# R) u. z: w" l* V5 Rd. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.






- L2 U! H% G( l" d% g========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer
0 ~7 B( \& c% X  K
) p3 G  P' v( R- r; J- |
a. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
OK.1
c. In the Confirm dialog box, click Yes.
' u+ d# l4 L' s8 U* B$ qd. In the Modify Required Context
Parameters dialog box, click OK to begin
patching.
e. After the patch is installed, click OK to
close the Progress dialog box.
9. In the Modify Web Application dialog box, click OK.
$ {' ~1 X2 M# F( ]5 o10. Exit the Web Application Manager.
4 g! [& n" E% {( z11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
to your web server.
12. Restart the distribution server.

" F# F. y1 h/ g. k* u
=====Patch Lifecycle Visualization====

: S) g+ P" ?/ x$ `" u) {' L1 T

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


; e. `! Z' b. M+ q* w. o0 k7 R1 l
7 T0 e; Y8 a- f' a
/ t2 _. A/ g8 X  f9 q. B