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

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
! W& r' t0 O) [. q  J4 a. S视频教程请参考plmhome.ke.qq.com
0 f. m' B) N6 s! ]. z
===Clearlocks======
clearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose
; ]3 o( w# ^: O1 T0 t# k# j

11.4 的升级比较特殊，特殊的两部如下：

1 E* w- A" [, PREM === Migrate trace links =====

9 u9 T! w) e2 D  ~( A* ]req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba
' \0 m, E) a/ r

" B/ [7 H; s/ k4 T% m====DB =======
7 C1 a2 k3 ~# w( X) X=====backup====

8 k' H5 ~0 t# H! v
REM ==Estimate tablespace requirements for update====
. O' u6 q$ F" F/ B( ^/ F6 C0 ?Oracle 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:
8 w( b- w* H9 n9 W: ~
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
1 G" ~  F4 T0 j/ q+ M, i' b0 KUNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;

b. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
( O1 E) e1 \- r: B  A9 ytables, which are also affected by the update process.
: E* G, m8 n8 K) y
Determine the amount of space consumed by each affected table.
For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),

enter the following SQL command:
' r% c+ U* M9 F" E+ Z) r& C5 XWITH cte1
AS (SELECT table_name
FROM user_tables
7 A6 }* E2 S9 r2 pWHERE table_name = 'TABLE-NAME'),
" |; _  O  f5 g+ zcte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
$ Z- b0 ^* U: z' s/ }FROM dba_extents,
! b# J) t" D+ P8 ?9 \3 a& ecte1
2 \0 Q  H$ W! K) ZWHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
FROM dual)
AND segment_name = cte1.table_name)
SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
FROM cte2;

6 s" N* p+ D  q9 V% aReplace TABLE-NAME with the name of the given table.
' G3 V, L! A/ X! U' k# m! Y


. U: R7 |' ?8 Q9 EREM ==unzip install.zip ======

TC_ROOT\install\install\unzip -o install.zip
' t7 j8 ~) z) d
5 b; W! K% O5 H/ S$ R: s
5 J, p% T/ Q! s3 b7 ~
- o: X& @7 V# SREM ===Install patches on a Teamcenter server====

. R* F0 K- N! cTEM--> updates manager

REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
; ^! a. q* ]; K( i  d* n) G
% M" L4 G7 E  r& ^After the server is successfully patched, you must manually update your TC_DATA directories.
) N9 S. L' O3 S) da. 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
existing files.
d. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.
6 ?' y; [" n! ?8 J* l9 o( x
  z* s' |2 {) A+ l8 t& a- p
$ l) r$ i" g$ p  I7 l+ k9 O( q
8 s. W, @! N- \' o
9 K5 {$ u- \# \0 J

1 J1 ?: @+ s4 }/ a: L! J9 \========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer
/ B( b! D, Z- b: E( h9 T% D
5 e, J5 v. _( M( E- o4 t: B; r
a. Click Reinstall Solutions.
0 R" }5 z( f) k% D4 z( @+ l/ b' Bb. In the Reinstall Solution dialog box, click
OK.1
c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
Parameters dialog box, click OK to begin
9 X$ v/ H$ K" v& I0 a' c+ Vpatching.
! b5 y2 D, w5 x) @2 Me. After the patch is installed, click OK to
0 g- _# a9 d9 Y( U0 H0 [& \close the Progress dialog box.
, a+ e9 a. {- n9. In the Modify Web Application dialog box, click OK.
10. Exit the Web Application Manager.
' W! ~& b, }. v; D! v11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
2 D3 ?4 `. K9 j) gto your web server.
12. Restart the distribution server.

5 j. Z1 o6 [$ L3 [! m* m9 j) S
- O; C6 B$ K& c) V0 ]=====Patch Lifecycle Visualization====

7 l0 F' p" Z. M

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

7 t1 E, P6 ?; E1 Z$ l1 V% D( `. b

  q8 l' _0 X! q3 k) i  [4 P
2 r9 ^* b: M- a! q