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

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
视频教程请参考plmhome.ke.qq.com
/ D- J, y* ^$ b" I1 N
===Clearlocks======
clearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
1 ]# Q2 O2 h4 G9 Q- T3 }$ gclearlocks -verbose
% q. I7 J. i& s- k. ]+ X# h; c

! K/ l2 t' J$ O, p0 H, I11.4 的升级比较特殊，特殊的两部如下：

- Y6 m/ \" J3 h( v* @REM === Migrate trace links =====
' H+ w+ ?; G. m' w- l% C) \( v8 c
req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
/ `" F/ X, u- [& ^
8 T2 e8 u$ Z! u1 u* m
====DB =======
=====backup====
% y5 _' @6 ?+ v2 y+ Y0 b( b* t

0 s# T! t/ w# qREM ==Estimate tablespace requirements for update====
Oracle databases:
' L2 m) g; l  v, g9 S  c1. Back up existing Teamcenter data.
- z. t5 ~8 e0 z; H3 g2. Determine the tables affected by the update to Teamcenter 11.4.
0 U+ D9 V- w! c$ La. Enter the following SQL command:
0 Z) B$ P+ b# ^% A& b
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
UNION
) M$ J6 G6 Z0 `' Y4 \, MSELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;
! p% g, R& K# F
b. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
tables, which are also affected by the update process.

Determine the amount of space consumed by each affected table.
1 f9 }+ ~) X- J4 _4 {+ y2 E6 EFor each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),

. W3 z4 B5 ^' u1 B$ ^# senter the following SQL command:
WITH cte1
" }9 `* X& s/ J  L. G. L+ ?' [) z) \AS (SELECT table_name
6 G( b3 b: ]" JFROM user_tables
WHERE table_name = 'TABLE-NAME'),
$ Y$ F$ F- x& a+ y9 k. y6 F0 h# ccte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
9 E; i/ v; M( M! J3 \FROM dba_extents,
8 a+ R/ J) i$ `0 rcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
0 G. x$ T7 e9 k1 ^) G% FAND segment_name = cte1.table_name)
' a! v4 [% \. {& M- A+ E, x# @$ eSELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
FROM cte2;
; x! ?* u/ l+ U& L- p
Replace TABLE-NAME with the name of the given table.


" D4 H1 ^2 f# k: O1 F
' _" q$ i% x  k- C% Q. FREM ==unzip install.zip ======
/ O3 {: [- K: @
TC_ROOT\install\install\unzip -o install.zip
  g- R7 x: T0 V; U( p, H


3 Y$ e. n& N# B' m, |# D3 p6 bREM ===Install patches on a Teamcenter server====

! w/ o! P" v6 |0 e4 v& z* U% mTEM--> updates manager
4 Q2 q8 I" u# Y8 d6 j
REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
! [# z( J8 |* H2 q: a  @' ?
6 x: b% \+ R7 S6 P8 r; V7 jAfter the server is successfully patched, you must manually update your TC_DATA directories.
4 b3 f, N. o5 A4 aa. 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
" v4 W" L9 r; }: C9 Z" p2 Y- W' eexisting files.
. H( r+ D' H' M/ ?. O, Ud. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.






========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
c. In the Confirm dialog box, click Yes.
' X) \3 }2 C# C4 e# Y  I3 e, y* Td. In the Modify Required Context
+ \& L9 s2 j: ]% J* hParameters dialog box, click OK to begin
patching.
e. After the patch is installed, click OK to
close the Progress dialog box.
: k0 F! J. n, y+ R  p: g5 C9. In the Modify Web Application dialog box, click OK.
10. Exit the Web Application Manager.
  d8 `/ j# O  v: C' L- F4 B- ^3 n11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
to your web server.
12. Restart the distribution server.
' n4 ?+ ^. }' S/ k. b( i

( G3 x4 f( G$ `3 ]; H=====Patch Lifecycle Visualization====


0 D9 p0 a' _: N/ P
# r3 S% X) Y8 Q, B===Patch the web tier======

3 h5 u+ M( A3 l3 F8 V: S% [4 z