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

admin

Teamcenter11.2 升级到 Teamcenter 11.4 图文教程
视频教程请参考plmhome.ke.qq.com
: u6 Y' H) p+ }% x/ `) h
===Clearlocks======
. V' g( P# O0 b1 L+ J! T) k7 Gclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose


+ W4 y/ q+ m. |9 E3 ~11.4 的升级比较特殊，特殊的两部如下：

! i" i% v$ z% L- f' \- tREM === Migrate trace links =====
2 [$ n6 R) [9 f$ e
req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba


7 Z6 q4 |7 ?0 C# c+ I====DB =======
=====backup====


" D1 d. ^1 d- C" SREM ==Estimate tablespace requirements for update====
Oracle databases:
1. Back up existing Teamcenter data.
& M/ U0 o7 M4 c6 }" {2. Determine the tables affected by the update to Teamcenter 11.4.
a. Enter the following SQL command:
% L2 R. q2 n; E, P; P9 {7 {& O
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 8192) <> 0
UNION
SELECT ptname FROM PPOM_CLASS WHERE BITAND(pproperties, 32768) <> 0;
# J7 h) |2 {9 b5 ~! K6 p& f% d
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),

enter the following SQL command:
WITH cte1
/ K% d$ L: b7 eAS (SELECT table_name
FROM user_tables
2 i+ Z8 V+ X/ X' C2 SWHERE table_name = 'TABLE-NAME'),
cte2
AS (SELECT SUM(blocks) * 8 / 1024 MB
" r/ ]6 t& b& K$ ]! A2 ?0 {& A6 zFROM dba_extents,
" k6 V9 a' T: b3 fcte1
WHERE owner = (SELECT SYS_CONTEXT('userenv', 'current_schema')
( ?" D; `! l; j* e1 J3 E8 aFROM dual)
6 S0 P0 Z; m5 ]- i& m/ lAND segment_name = cte1.table_name)
SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
FROM cte2;
8 ?! h$ O" I9 F% ?% W
Replace TABLE-NAME with the name of the given table.
, j6 ?; h* b0 a0 d
8 Y* X8 h" |/ c& f6 ~9 ^

$ ^9 u6 x& a6 P* l  S+ ]REM ==unzip install.zip ======

/ M. m0 ^4 n& v$ {, c+ i+ uTC_ROOT\install\install\unzip -o install.zip
0 v4 I6 S2 r  U
6 `( U5 {  J, \% J

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

, R3 _. I3 x1 ?/ w- iTEM--> updates manager

REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip

, c8 i9 t- k( C9 Z9 Z3 `* j2 ZAfter the server is successfully patched, you must manually update your TC_DATA directories.
a. 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.
0 A2 o6 a4 k# B6 Uc. Copy the expanded contents of the data.zip file to your TC_DATA directories, overwriting
2 C) E, K7 q9 t7 k# Hexisting files.
d. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.
/ y. D4 n- ^& N- i1 c3 |

, r1 N* m& L4 g* |/ b" ?2 @



6 B3 C4 j3 E% _& r========Patch the rich client using TEM
========Patch the rich client using the Over-the-Web Installer


a. Click Reinstall Solutions.
4 S" U2 U; v+ D, F, k) y, Vb. In the Reinstall Solution dialog box, click
OK.1
. D2 G/ F0 l* f# ]c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
) Y" a6 l4 i% l; hParameters dialog box, click OK to begin
/ L& G5 g  |) S- c) r; s/ Spatching.
6 p0 q0 [! I; A2 q, P, De. After the patch is installed, click OK to
) w5 ]. T8 C# c1 eclose the Progress dialog box.
$ X8 I: e/ ]' c  a% ~$ d- F! L1 o$ _% t9. In the Modify Web Application dialog box, click OK.
10. Exit the Web Application Manager.
11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
' u  N( i& [6 }& Z) ~# y: R! Rto your web server.
% l1 Y$ x3 \: g; D2 ^% t) R12. Restart the distribution server.
# q9 c2 l; T* r' D+ r0 i

% k1 D, t( t: S=====Patch Lifecycle Visualization====



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

* G2 O6 u; H' b& ^9 S/ q1 N
, y9 T% S7 }: m" g# ^
3 h+ N6 X* K; H' x& Q

; W% V7 v% v) |) }' S7 f$ T