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

admin

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

' H. ?2 I' {- T3 e7 V1 e===Clearlocks======
clearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose
& P0 t4 H* g( h* M0 s1 r1 k5 B

' W3 w! n) [5 |9 V( p1 D11.4 的升级比较特殊，特殊的两部如下：

+ ]3 ]8 d$ T6 l3 K# I# z, @/ N6 WREM === Migrate trace links =====

+ E* X  Q' L0 i1 n, V) Oreq_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba

) g" U$ U) @" B
7 j5 C: S3 i  N& c====DB =======
=====backup====

4 T' a" p  `2 s$ H/ C: @0 g8 G9 f
REM ==Estimate tablespace requirements for update====
- {# R( P3 A0 xOracle 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:
0 B- |5 b, F5 P' q4 B
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
8 V/ Z; ^2 E% i( f1 |: h0 OUNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;

b. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
9 H, s$ n# p% w/ s. }: ytables, which are also affected by the update process.
8 X; g- O, ]: M6 b% x! S( ~. I/ n
Determine the amount of space consumed by each affected table.
For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
3 O3 H1 t; S" K) G/ S
enter the following SQL command:
WITH cte1
AS (SELECT table_name
FROM user_tables
& |: A( S, U# e  ^4 O1 h0 KWHERE table_name = 'TABLE-NAME'),
' P. k& D- y$ D, R- D9 R- X( `0 ^+ Ncte2
! F* i. n: r2 ]8 y* }/ {5 VAS (SELECT SUM(blocks) * 8 / 1024 MB
FROM dba_extents,
7 B7 G: j1 m& u+ S2 i! _  v8 L% zcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
$ y; g/ ]* L. H6 B2 KFROM dual)
! h7 y* |& B: IAND segment_name = cte1.table_name)
4 Q" ?. m$ L) a5 A) SSELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
, D4 m0 Z2 b, ]  P% ?! LFROM cte2;

Replace TABLE-NAME with the name of the given table.
5 K' z" J' s* e) A) w) n

* g% Q3 Y9 u- I6 h2 q( H2 f1 P
! D4 l! E- \, iREM ==unzip install.zip ======
( m- t1 b- V: s  r7 J) p% g2 g
. m. O: p1 y( J2 o* X" hTC_ROOT\install\install\unzip -o install.zip
/ X+ l0 B- U6 F' }/ B- N, C7 h

1 w+ D, G/ g! g1 O0 d- B) K( I! q
REM ===Install patches on a Teamcenter server====

3 I2 z; N+ V6 X: ?TEM--> updates manager
' K# c* w# y- [; U3 F1 I
REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
& @  d. g, j. X' H. N
After the server is successfully patched, you must manually update your TC_DATA directories.
; N, t( n( I, L. V6 Q. Ga. Create backups of your current TC_DATA directories.
3 B- i' [3 ^7 A# u2 @& ob. Expand the platform\tc\data.zip file from the temporary location you created in step 1.
2 \- ]! Z. v* D5 Mc. 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.


6 m% @7 w3 c& q3 X" W
3 Y& F, V2 b* f5 u
; p- [* B, r: k6 r3 F, w+ v. @+ Z* E' w
5 i: |# ~# b. G
========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer

6 |/ k! ?) |: Z: L0 @
a. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
5 T: }# B; y" f! ]+ W1 GOK.1
c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
Parameters dialog box, click OK to begin
3 a( v: V9 N- V, x# y& mpatching.
9 X. _& N: ^7 i7 s& o2 Z: N6 S' de. After the patch is installed, click OK to
close the Progress dialog box.
! O4 H& M. e- H: ^' p1 q! S9. In the Modify Web Application dialog box, click OK.
. E+ Y. y+ m, k8 j8 [* w) p7 z6 |& u' @10. Exit the Web Application Manager.
11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
to your web server.
12. Restart the distribution server.

& t: l( `9 c' i* \0 Y& r$ |" B
=====Patch Lifecycle Visualization====
' I) f  q  L( f4 s& X, Y

4 }" I& \% p6 x0 F' d( G8 k" k+ t
===Patch the web tier======

" J/ R' K2 {% i* D" N6 T
5 U# |: F: o' y

9 l9 o( v8 O! c2 F
6 @& i- l  a( J$ t( t1 e& p' y