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

admin

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

  [. ~- E7 k. o: i/ _===Clearlocks======
7 S/ n  z9 \8 ^6 L) gclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
2 V: U5 w5 F- l: b5 ~clearlocks -verbose
7 X. P; |# L! c% S% ^8 l
1 ?& l" \" S- c. }2 b1 r) M
11.4 的升级比较特殊，特殊的两部如下：
" w, Y. A* B% s- w3 U% y- ~
REM === Migrate trace links =====

req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba


2 m3 H8 b' T* K3 C+ S% _7 a====DB =======
=====backup====
$ A6 [! \) ~% ]
9 W; {+ n' Y" X8 f; K- i) ?& E
& I! ^. |+ O" i4 _( iREM ==Estimate tablespace requirements for update====
Oracle databases:
6 N& h5 L( k# b5 m1. 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
UNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;

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.
For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),

! }6 S2 v' k$ j( y. Benter the following SQL command:
WITH cte1
/ g* l; b5 i( b. U6 uAS (SELECT table_name
2 q+ w1 F( u1 D' ?4 U$ P1 PFROM user_tables
8 t2 @0 M. G3 J$ f' uWHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
FROM dba_extents,
cte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
: Z. c+ N, N' kAND segment_name = cte1.table_name)
SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
FROM cte2;
9 Y7 x4 d! m2 d9 R# e
Replace TABLE-NAME with the name of the given table.
. A* e- b3 A' A* `& ?4 `3 V
  j7 k% W0 G# q0 ^# a$ G

REM ==unzip install.zip ======
: C9 _. ~  n+ L2 |
, q1 P" ]2 g0 I) c( J* VTC_ROOT\install\install\unzip -o install.zip
5 O" ~$ v0 t  C% o. Y/ H4 V


REM ===Install patches on a Teamcenter server====

TEM--> updates manager
0 ^: M6 O8 B7 g! f
- ]# n2 v2 B6 f' @' m  E; x/ k( jREM === 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.
. u% K+ [- v- q3 db. 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
8 {1 w' ^' h5 V  L0 Cexisting files.
- w8 L( @) `& d8 Ad. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.
  r3 S. c  Y2 x( y6 ^& T2 }! Y





. K6 v( o! [) G( Y- S) ]========Patch the rich client using TEM
7 v6 s7 G, h& _% Z. p! G. F2 y/ M' A5 ^========Patch the rich client using the Over-the-Web Installer
9 @: r3 u3 U* L/ O  o4 N

a. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
% b; P  @; ^  S; c( J6 \1 O/ HOK.1
c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
Parameters dialog box, click OK to begin
patching.
$ t  Q/ h- d) `1 ~3 d/ m" s1 M0 P. @e. After the patch is installed, click OK to
& S. H4 {4 m6 A$ N) W+ E' i; Vclose the Progress dialog box.
  g+ }4 f4 |" ?& |' S8 n9. In the Modify Web Application dialog box, click OK.
10. Exit the Web Application Manager.
+ v( Y$ v8 }. l8 I4 i11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
to your web server.
12. Restart the distribution server.

2 n' V$ Y! [. T3 i0 j
=====Patch Lifecycle Visualization====

0 ]; j/ Y& ?" s% M2 L# T6 A4 x

4 o/ \6 c$ x/ C" x6 ]===Patch the web tier======
+ O0 i4 W1 \: q/ w6 I& d% [" ^$ Q
" r; ~0 r! K) t6 p4 t+ G
$ [+ R3 O/ w) G