<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Unicode conversion in situ in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-in-situ/m-p/10864151#M1886944</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi SCN,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking at the possibility of running a Combined Upgrade &amp;amp; Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.&lt;/P&gt;&lt;P&gt;However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?&lt;BR /&gt;This seems logically problematic as you need a target system to import to.&lt;/P&gt;&lt;P&gt;I can imagine a process along these lines though...:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Take SAP layer offline&lt;/P&gt;&lt;P&gt;2. Run full backup of system&lt;/P&gt;&lt;P&gt;3. Export system&lt;/P&gt;&lt;P&gt;4. Drop database* (to make clean ready for new import)&lt;/P&gt;&lt;P&gt;5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...&lt;/P&gt;&lt;P&gt;6. ....and continue to run import into that database&lt;/P&gt;&lt;P&gt;7. Complete Unicode conversion process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However the big issue here for me is&lt;/P&gt;&lt;P&gt;(a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple&lt;/P&gt;&lt;P&gt;(b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any input/discussion on these points would be very welcome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, doonan_79&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 Jan 2015 16:40:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-01-12T16:40:28Z</dc:date>
    <item>
      <title>Unicode conversion in situ</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-in-situ/m-p/10864151#M1886944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi SCN,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking at the possibility of running a Combined Upgrade &amp;amp; Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.&lt;/P&gt;&lt;P&gt;However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?&lt;BR /&gt;This seems logically problematic as you need a target system to import to.&lt;/P&gt;&lt;P&gt;I can imagine a process along these lines though...:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Take SAP layer offline&lt;/P&gt;&lt;P&gt;2. Run full backup of system&lt;/P&gt;&lt;P&gt;3. Export system&lt;/P&gt;&lt;P&gt;4. Drop database* (to make clean ready for new import)&lt;/P&gt;&lt;P&gt;5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...&lt;/P&gt;&lt;P&gt;6. ....and continue to run import into that database&lt;/P&gt;&lt;P&gt;7. Complete Unicode conversion process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However the big issue here for me is&lt;/P&gt;&lt;P&gt;(a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple&lt;/P&gt;&lt;P&gt;(b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any input/discussion on these points would be very welcome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, doonan_79&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jan 2015 16:40:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-in-situ/m-p/10864151#M1886944</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-01-12T16:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: Unicode conversion in situ</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-in-situ/m-p/10864152#M1886945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.&lt;/P&gt;&lt;P&gt;Allowing for parallel export/import, but going back to the original configured host to complete the process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Jan 2015 13:32:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-in-situ/m-p/10864152#M1886945</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-01-13T13:32:05Z</dc:date>
    </item>
  </channel>
</rss>

