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

admin

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

===Clearlocks======
4 h. ]7 f. I: vclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
7 o, Z; o& t9 p: |$ b: o+ S! Pclearlocks -verbose
& Q! I$ d3 n$ r$ d  `% S7 L' q9 o
5 T% s; E+ d! G2 ?* z' f
11.4 的升级比较特殊，特殊的两部如下：
' L7 D6 z1 N8 C9 a1 P; \8 r
REM === Migrate trace links =====
8 H* x  `, C! l/ J5 P+ ^
9 \! x3 o% D8 k) i" \& ~req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
) q# @4 U" S$ E

0 z  |" e1 Q) {0 \0 G0 l% F& p====DB =======
+ p- H( M$ }; `6 \# j2 a=====backup====


% R# d2 q# T4 `% AREM ==Estimate tablespace requirements for update====
9 Y9 F# I* S+ ]9 \$ vOracle databases:
1. Back up existing Teamcenter data.
2. Determine the tables affected by the update to Teamcenter 11.4.
2 ~- w. b" L3 H+ x, j( O9 S3 \a. Enter the following SQL command:

SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
UNION
* g. d$ ?3 u; X  |5 ?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.
. x" z, @+ b9 u7 [% q- Z, C
' M  @! i2 M4 HDetermine the amount of space consumed by each affected table.
For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
) b! D# I8 F: {$ M  d- U
enter the following SQL command:
8 Z, \' c% e! E5 r: ]WITH cte1
- ?% o4 J- l% m1 e+ QAS (SELECT table_name
+ W4 d" v* l/ Y8 e1 B1 [9 {. \: C6 ~FROM user_tables
9 E# O( ?* i% N; v9 U) i1 ZWHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
FROM dba_extents,
% }4 u# k  t5 hcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
AND segment_name = cte1.table_name)
+ u5 T; y) v; e6 TSELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
FROM cte2;

Replace TABLE-NAME with the name of the given table.
" p# L2 [, {; c$ o
+ i3 R9 O; A3 l# e1 _, V; Y

REM ==unzip install.zip ======
( e, C7 X* M% \/ y
0 x1 j8 s0 T( W( KTC_ROOT\install\install\unzip -o install.zip



REM ===Install patches on a Teamcenter server====
7 V/ ?  E$ c" l! R3 F! Z$ ~& R) }: L
. A% h4 `0 W2 C. ?TEM--> updates manager
. d5 s7 O4 k( X! |: a
REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
, _8 H3 G! N9 s: J
$ C: y$ m% H/ z+ @. ]After the server is successfully patched, you must manually update your TC_DATA directories.
a. Create backups of your current TC_DATA directories.
$ O  Q: k% |% j4 cb. Expand the platform\tc\data.zip file from the temporary location you created in step 1.
$ j0 X5 |1 F2 W! Z) n# ?6 @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.
# q: h% z: H  |) ?
+ C3 j4 z; ~! f. R
: B, V. U2 ?1 {" o

7 H3 h# J! D- X9 G9 S  ]: N3 u
+ F; \% L6 T. q0 S4 \" `
========Patch the rich client using TEM
* f, [& v9 ~6 O+ \0 F. \========Patch the rich client using the Over-the-Web Installer


a. Click Reinstall Solutions.
, I5 v* f0 C4 ?% W' l1 c7 A9 lb. In the Reinstall Solution dialog box, click
# j% |( ?, q1 |0 AOK.1
c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
- v* h) W: H" b( }8 z2 [5 m; BParameters dialog box, click OK to begin
patching.
e. After the patch is installed, click OK to
1 x2 V, b8 l9 A- U8 V- dclose the Progress dialog box.
2 l3 J1 g# p2 V; B* ]+ G- L9. In the Modify Web Application dialog box, click OK.
1 \# C1 l7 @2 M10. Exit the Web Application Manager.
) d$ }1 o& ?8 w1 ]& O! r11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
to your web server.
12. Restart the distribution server.


=====Patch Lifecycle Visualization====

, j( e/ ^: y! [: C) U1 F: x$ Z

===Patch the web tier======
3 z3 j7 ]4 _: c" u% D' G4 A/ f

- G. @4 }& L; {3 J

+ _/ x% B' A7 @, {
& U" _7 |+ p7 J; B5 `