Skip to Content
Prior/Later Unicode Conversion Episodes [Updated 12-Feb-2008]
  • 0.001 – [Destroyed by space pirates]
  • 0.002 – Community Day and Onward
  • 0.003 – Revenge of The Space Monster
  • 0.004 – Children of Murphy
  • 0.005 – Journey to the Edge of Quality
  • 0.006 – The Calm Before the Storm of Quality
  • 0.007 – Passage to Production
  • 0.008 – Unicode The Final Descent
  • 1.000 – The Final Chapter

Lessons learned during post-Unicode conversion testing in development

  • Extended syntax check – previously would not fail; after Unicode, will fail.  Developers have safely ignored this up till now.
  • Oracle environment scripts – some head scratching to get all the tools to work.
  • SCM development – Java update was required, missing on 1st plan
  • LiveCache – Missed executable patches on failover node, one more checklist tickler.
  • R/3 and SCM copybacks are complete; needed to wipe pre-Unicode SQL Trace file.

Planning for Quality and Production

The SAP Unicode Conversion guide has a graphic showing system requirements.

image

Our landscape for this second phase is more complex:

image

Each cylinder represents a working database, with disk storage up to 6TB, not including the file export space.

Quality System Preparation

  As of 21-Dec-2007, here is where our R/3 pre-Unicode scanning stood:

 

image

 

We expect to have under 100,000 vocabulary words to identify, similar to what we saw in our prior R/3 and BW conversions. 

For the last several days, we pushed the TST servers average CPU values up and over 90%.

image

image

image

SPUMG TST status

This is a tabular view of the above SPUMG status screen shot, showing progress on the preconversion steps.

Job Status Job Number Scan Level In Process Initial Completed Warning Ignored
  0 Consistency Check 0 0 39,085 0 0
Is running 15 Tables without Language Information 15 3,452 27,849 450 0
  0 Tables with Ambiguous Lang. Information 0 7,769 0 0 0
  0 Tables with Language Information 0 7,562 0 0 0
  0 Reprocess 0 449 0 0 0
  0 INDX Table Analysis 0 404 0 0 0

Here is an extract from SM66, showing the background process jobs doing the table scans.  Some have been running for over a week. 

SM66 during TST scans

Server Typ      PID Status   Time User Report Action/Reason for waiting Table
towtstap01_TST_02 BTC 364740 running 19231 SCHEDGPASIA ZMMTBLEX Sequential read MSEG
towtstap01_TST_02 BTC 761990 running 753406 QA-BDILLING UMG_SCAN    
towtstap01_TST_02 BTC 704710 running 73236 QA-BDILLING UMG_SCAN    
towtstap01_TST_02 BTC 708774 running 86396 QA-BDILLING UMG_SCAN Sequential read S751
towtstha02_TST_02 DIA 3215488 stopped   QA-EMILLER      
towtstha02_TST_02 BTC 3035204 running 753340 QA-BDILLING UMG_SCAN Sequential read CKMI1
towtstha02_TST_02 BTC 3129558 stopped 73 SCHEDULER   CMRCV / 15550141  
towtstha02_TST_02 BTC 3137790 running 576023 QA-BDILLING UMG_SCAN Sequential read RFBLG
towtstha02_TST_02 BTC 3391634 running 90024 QA-BDILLING UMG_SCAN Sequential read CDCLS
towtstsv01-z_TST_02 BTC 2576532 running 77714 QA-BDILLING UMG_SCAN Sequential read CE1NAPT
towtstsv01-z_TST_02 BTC 11702480 running 47810 QA-BDILLING UMG_SCAN    
towtstsv01-z_TST_02 BTC 4284468 running 47650 QA-BDILLING UMG_SCAN    
towtstsv01-z_TST_02 BTC 7499924 running 47641 QA-BDILLING UMG_SCAN    
towtstsv01-z_TST_02 BTC 8106142 running 46970 QA-BDILLING UMG_SCAN Sequential read S710
towtstsv01-z_TST_02 BTC 3567646 running 3259 QA-BDILLING UMG_SCAN    
towtstsv01-z_TST_02 BTC 3518526 running 46740 QA-BDILLING UMG_SCAN Sequential read VBFA
towtstsv01-z_TST_02 BTC 11518024 running 46649 QA-BDILLING CL_UMG_W    
towtstsv01-z_TST_02 BTC 3576046 running 44331 REGRESSION ZMMTBLEX Sequential read MSEG

ST04

Finally, here are the SQL statements for UMG_SCANNER that have done more than 10,000,000 disk reads… 

Executions Disk reads   Reads/Exec Buffer gets   Bgets/exec Proc. rows    Rproc/Exe SQL statement Program name First load time
30 43,108,515 1,436,951 57,547,616 1918254 58,062,090 1,935,403 SELECT FROM CKMI1… UMG_SCANNER 2007-12-15/16:07:40
125 39,056,422 312,451 52,620,554 420964 171,961,309 1,375,691 SELECT FROM BSIS… UMG_SCANNER 2007-12-15/00:18:28
4 33,698,992 8,424,748 33,492,346 8373087 3,335,905 833,976 SELECT FROM CE1NAPT … UMG_SCANNER 2007-12-20/12:37:22
232 27,035,126 116,531 50,633,044 218246 461,837,169 1,990,678 SELECT FROM COEP … UMG_SCANNER 2007-12-12/17:37:49
252 25,443,669 100,967 54,683,309 216997 502,091,496 1,992,427 SELECT FROM ZZGLA… UMG_SCANNER 2007-12-12/17:12:20
156 23,840,795 152,826 189,698,776 1216018 103,474,387 663,297 SELECT FROM RFBLG … UMG_SCANNER 2007-12-12/17:36:06
56 20,369,302 363,738 27,064,663 483298 64,534,879 1,152,409 SELECT FROM BSIS… UMG_SCANNER 2007-12-15/00:38:01
1 19,962,700 19,962,700 9,820,358 9820358 2,000,001 2,000,001 SELECT FROM BSIS … UMG_SCANNER 2007-12-14/11:46:51
5 19,680,187 3,936,037 140,810,212 28162042 77,661,173 15,532,235 SELECT FROM RFBLG…   UMG_SCANNER 2007-12-12/16:35:04
1 15,602,394 15,602,394 59,775,263 59775263 2,000,001 2,000,001 SELECT FROM LIPS … UMG_SCANNER 2007-12-19/23:52:53
11 11,804,980 1,073,180 83,907,209 7627928 41,827,855 3,802,532 SELECT FROM RFBLG … UMG_SCANNER 2007-12-14/03:34:21
21 10,658,314 507,539 10,169,702 484272 41,488,055 1,975,622 SELECT FROM PBHI … UMG_SCANNER 2007-12-20/10:38:45
1 10,101,160 10,101,160 5,974,760 5974760 2,000,001 2,000,001 SELECT FROM CKMI1 … UMG_SCANNER 2007-12-15/11:01:07
To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply