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

admin

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

===Clearlocks======
+ y* ]( O- I7 X2 Q- O! @6 r2 uclearlocks -assert_all_dead -u=infodba -p=infodba -g=dba
clearlocks -verbose


11.4 的升级比较特殊，特殊的两部如下：
4 S* K/ `( @$ G  B1 E. S7 _
% a# c$ x5 {2 E" k: \8 HREM === Migrate trace links =====

. p% [2 L  ^6 c0 Y# @req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba

$ [) P( x* i- E9 r  T! T
====DB =======
& n. p$ M% u+ ?=====backup====
  J+ n5 w/ I  }5 b
2 Z( l# ~; @$ R4 Z* \
REM ==Estimate tablespace requirements for update====
Oracle databases:
1. Back up existing Teamcenter data.
+ K# P& ^( w* |$ d; v2. Determine the tables affected by the update to Teamcenter 11.4.
- p  Z! ?7 [" Ca. 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;
2 [% N; I2 y5 ~% i1 B4 k' e
& \7 f; q5 w# t; bb. To the resulting list of tables, add the PIMANEXPORTRECORD and PPOM_STUB
tables, which are also affected by the update process.
# l( I* n: q- y
Determine the amount of space consumed by each affected table.
For each table identified in step 2 (including PIMANEXPORTRECORD and PPOM_STUB),
: W% S0 ~& v- u' h
) I* m9 V, A7 Y8 Y% O: t, Eenter the following SQL command:
WITH cte1
AS (SELECT table_name
+ p! ?! T. K) ^1 \/ f1 P9 SFROM user_tables
WHERE 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+ E. G1 y' b( d# o9 n4 e+ F5 JAND segment_name = cte1.table_name)
SELECT ROUND(SUM(mb), 0) || ' MB' AS ESTIMATED_SPACE
  I- c5 v$ M9 P" d6 ?! F$ C- `FROM cte2;
% N! L4 T1 y! \5 D6 {
Replace TABLE-NAME with the name of the given table.
8 c2 i$ T7 O: A) R


- S; \1 {+ y8 y/ R5 ZREM ==unzip install.zip ======

" s2 l* s7 d% q/ p$ r* I; ?TC_ROOT\install\install\unzip -o install.zip



2 Y: a0 m% A: q7 L8 p" l3 WREM ===Install patches on a Teamcenter server====
: Y* n7 o; j; ^; s# v
TEM--> updates manager
: T$ M3 Q$ n) V' l0 g
REM === Update kit location : product-level_number_platform.zip  // Tc11.4_wntx64.zip
# E, o3 N& b2 k( V+ M$ K
After the server is successfully patched, you must manually update your TC_DATA directories.
a. Create backups of your current TC_DATA directories.
. r2 S! l# |' Mb. Expand the platform\tc\data.zip file from the temporary location you created in step 1.
1 S' Y8 n7 e( C3 `: r5 ?c. Copy the expanded contents of the data.zip file to your TC_DATA directories, overwriting
5 A( J7 I5 ~4 s2 f8 P# cexisting files.
d. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.

6 M+ N+ f) [0 r7 |1 l5 X/ Y& `




========Patch the rich client using TEM
3 E2 O5 E/ L9 l! ~6 T$ J& [========Patch the rich client using the Over-the-Web Installer

" t! z5 i+ U: q; |6 O0 S# p) f& i
2 {; W+ Q4 s# |2 Ma. Click Reinstall Solutions.
b. In the Reinstall Solution dialog box, click
OK.1
c. In the Confirm dialog box, click Yes.
d. In the Modify Required Context
. B& e) Y% w7 n+ I4 j& n& ]Parameters dialog box, click OK to begin
patching.
$ J2 n0 T+ L# B1 a2 Ze. After the patch is installed, click OK to
close the Progress dialog box.
9. In the Modify Web Application dialog box, click OK.
+ `7 C& ^. \7 L  Q( a10. Exit the Web Application Manager.
/ Q) G& i& \* i. J+ H11. Copy the otwweb directory from your WEB_ROOT\staging-location\webapp_root directory
. O: m5 O: z% _! a4 k9 _3 O, Ato your web server.
12. Restart the distribution server.
+ [1 P) m  ~9 O+ z* s
8 d) ]- Z5 k& A
=====Patch Lifecycle Visualization====
: k& L' K2 L( ]) w1 W5 ^
) Z' C$ O: A7 A  |1 p
2 u9 w7 H% V3 Y& `' v) }! A  Z9 j' _
===Patch the web tier======
/ U3 d* L, E& v- J

9 ]( W/ Y- ~9 ^, U
- f( v! |, E* h" e7 n8 {

' |, Q9 c, [$ V5 R- n8 Z