EBCDIC ASCII SAP R/3 Code Page Conversion In-Place Procedure for Systems on iSeries (AS/400) - BETA
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
SAP R/3 Code Page Conversion
EBCDIC Æ ASCII
In-Place Procedure
for Systems
on iSeries (AS/400)
Release 4.6D
Version 0.95
BETA
SAP® AG Neurottstr. 16 D-69190 WalldorfSAP AG
Copyright
Copyright
Copyright 2002 SAP AG. All rights reserved.
No part of this documentation may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP AG.
SAP AG further does not warrant the accuracy or completeness of the information, text,
graphics, links or other items contained within these materials. SAP AG shall not be
liable for any special, indirect, incidental, or consequential damages, including without
limitation, lost revenues or lost profits, which may result from the use of these materials.
The information in this documentation is subject to change without notice and does not
represent a commitment on the part of SAP AG in the future.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft®, Windows, NT® ,EXCEL, and SQL-Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2, Parallel Sysplex®, MVS/ESA, AIX®,
S/390®, OS/390®, OS/400®, AS/400®, iSeries, pSeries, xSeries, zSeries, z/OS®, AFP,
Intelligent Miner; WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic
Server are trademarks of IBM Corp. in USA and/or other countries.
Oracle is a registered trademark of Oracle Corporation, California, USA.
UNIX®, X/Open®, OSF/1, and Motif are registered trademarks of The Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C ® ,
World Wide Web Consortium, Laboratory for Computer Science NE43-358,
Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139.
JAVA ® is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road,
Palo Alto, CA 94303 USA.
JAVASCRIPT ® is a registered trademark of Sun Microsystems, Inc., used under license
for technology invented and implemented by Netscape.
ADABAS is a registered trademark of Software AG
SAP, SAP Logo, mySAP.com, mySAP Marketplace, mySAP Workplace, mySAP
Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA,
ABAP, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI,
SAPPHIRE, Management Cockpit, SEM, SAP DB are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All
other products mentioned are trademarks or registered trademarks of their respective
companies.
2 July 2002SAP AG
Contents
Contents
Chapter 1: Introduction ................................................................................................ 1–1
General Information.................................................................................................... 1–2
Terminology................................................................................................................ 1–5
BW and SEM System Considerations........................................................................ 1–5
ABAP Program Loads ................................................................................................ 1–5
General Requirements and Restrictions .................................................................... 1–6
Organizational Preparations....................................................................................... 1–8
Technical Preparations............................................................................................. 1–11
Code Page Conversion Tool Considerations ........................................................... 1–16
Chapter 2: R3load In-Place Procedure on iSeries...................................................... 2–1
Overview .................................................................................................................... 2–2
Requirements and Restrictions .................................................................................. 2–3
Preparing the In-Place Conversion ............................................................................ 2–4
Unloading the Database............................................................................................. 2–5
Converting to the ASCII Code Page........................................................................... 2–7
Troubleshooting........................................................................................................ 2–13
Chapter 3: General Subsequent Actions .................................................................... 3–1
Subsequent Technical Actions ................................................................................... 3–2
July 2002 3SAP AG
Typographic Conventions
Typographic Conventions
This convention. . . is used for. . .
Menu Text menu names and menu items; also field names and screen
titles.
Select File → Open
User Entry exact user input. These are words and characters you type on
the keyboard exactly as they are in the documentation;
also UNIX users like root, mail, ftp etc.
Enter tail -f R3INST.log
File Name file names, UNIX scripts and paths/directories; also screen
messages.
Delete the line starting with dba in the file /etc/group
variables in general, e.g. variable user entries or file names
The home directory of the user ora is
/oracle/
Book Title cross-references to other books
This icon. . . helps you identify. . .
Example an Example. Examples help clarify complicated concepts or
activities.
Note a Note. Notes can contain important information like special
considerations or exceptions.
Caution
a Caution. Cautions should help you avoid errors, for example,
those that could lead to data loss.
4 July 2002SAP AG
Typographic Conventions
Change History
July 2002 5SAP AG Introduction
Contents
Chapter 1: Introduction
Contents
General Information.............................................................................................................. 1–2
Terminology .......................................................................................................................... 1–4
BW and SEM System Considerations................................................................................. 1–4
ABAP Program Loads........................................................................................................... 1–4
General Requirements and Restrictions ............................................................................ 1–4
General Requirements....................................................................................................... 1–4
Restrictions ........................................................................................................................ 1–5
Organizational Preparations ................................................................................................ 1–7
Technical Preparations ........................................................................................................ 1–9
Preparing the System ........................................................................................................ 1–9
Code Page Conversion Tool Considerations................................................................... 1–13
July 2002 1–1Introduction SAP AG
General Information
General Information
This documentation describes how to make a code page conversion from EBCDIC to ASCII
when your operating system is OS/400.
A code page conversion should only be done by a person with experience in copying systems
and with knowledge of the operating system, the database, and the ABAP Dictionary.
The person performing the code page conversion must either have attended the Code
Page Conversion seminar provided by SAP (UABC92) or be certified by SAP to perform
OS/DB conversions (course TABC92).
A webform is provided by SAP, which you can use to provide information needed by the
conversion support group. You should fill out the form and send it to SAP some weeks before
the actual conversion takes place to allow time to deal with any open issues. You can find the
form via the following URL:
KWWS VHUYLFHVDSFRPaIRUPVDSQHW"B6+257.(<
then click on the link “Code Page Conversion Notice Form”
If there is a problem accessing the URL, then try :
KWWS VHUYLFHVDSFRPJSP
!*OREDO3DUWQHU7HFKQRORJ\
!,QW&&,%0
!,%03ODWIRUPV
!L6HULHV&RGHSDJH&RQYHUVLRQ
!&RGH3DJH&RQYHUVLRQ1RWLFH)RUP
Caution
The PTFs SF67186 (V4R5) or SI03716 (V5R1) from IBM are prerequisites for the in-
place conversion procedure. From operating system release V5R2M0 the PTF is included
in the standard system.
Only the central instances will be converted by this procedure. Application servers should
be deleted and re-installed. 3-tier sites will need to reconfigure to 2-tier for the duration of
the code page conversion procedure.
SAP Notes
Read the following SAP Notes before beginning the code page conversion. These notes
contain the most recent information regarding the code page conversion. They are available
only in English.
Number Title
1–2 July 2002SAP AG Introduction
General Information
500950 R/3 EBCDIC → ASCII Codepage Conversion
39510 AS/400: ASCII-EBCDIC Considerations
Make sure that you have the most recent version of these Notes.
Caution
The code page conversion may occasionally destroy the contents of some ABAP variants,
where information is stored in variable length character strings. This can mean that field
length data (which is stored as binary containers within these strings) will be converted to
a new value instead of being left unchanged, thus invalidating the information. For this
reason, it is advisable for you to make a note of all important variants and, in the rare
cases where this problem occurs, to re-enter them manually after the code page
conversion is complete. If you encounter this problem, report it to SAP by creating a
message in component BC-INS-AS4 in the SAPNet − R/3 Frontend
Note
A full system backup should be performed before beginning the code page
conversion.
Note
If you experience problems during an EBCDIC → ASCII code page conversion of a
production system, create a message in component BC-INS-AS4 in the SAPNet − R/3
Frontend.
SAP will process SAPNet R/3 Frontend messages concerning problems with the
code page conversion only if there is a contact person available on site, who is either
a SAP-certified migrator or else has attended the SAP Code Page Conversion
Seminar.
July 2002 1–3Introduction SAP AG
Terminology
Terminology
Source System and Target System
For an in-place code page conversion, the source system and the target system remain the
same, having the same .
Code page Conversion
Inplace replication of an SAP System for the purpose of converting the databases from
EBCDIC to ASCII. Certain SAP parameters may change during an in-place conversion.
Placeholders
Placeholders such as are used in commands. They are used in the same way as in the
SAP System installation documentation, and must be replaced with the values valid for your
site.
BW and SEM System Considerations
The main difference between the code page conversion of an R/3 System on the iSeries and
that of a BW System or a BW-based system such as SEM, results from the DB-platform
specific implementation of the Fact-Table indexing. This extremely platform-specific
implementation of these indices cannot be depicted in the ABAP Dictionary, so this
information is not available for the SAP Tools R3LDCTL and R3LOAD.
In this documentation, the additional steps required for the code page conversion of a BW or
SEM System will be described in specific sections in this documentation.
ABAP Program Loads
The ABAP loads are platform and code page-dependent programs which are generated during
runtime and which are stored in database tables. They are not exported when you use the
R3LOAD procedure to convert your SAP System. The ABAP loads are generated in the target
system when they are first used.
General Requirements and Restrictions
General Requirements
Caution
The following in-place conversion method must not be used for systems with a non-Latin-
1 code page.
1–4 July 2002SAP AG Introduction
General Requirements and Restrictions
The export/import procedure, described in the SAP documentation SAP R/3 Code Page
Conversion EBCDIC ->ASCII Export/Import Procedure for Systems on iSeries (AS/400),
must be used.
To make a code page conversion, the versions of the SAP System and the installation tools
must be the same on the ASCII and EBCDIC systems (exceptions are only allowed if they are
described in an SAP Note). Order the latestt version of the conversion CD CD51017882
before starting the code page conversion. Obtain the latest versions of the notes.
Caution
The PTFs SF67186 (V4R5) or SI03716 (V5R1) from IBM are prerequisites for the in-
place conversion procedure. From operating system release V5R2M0, the PTF is included
in the standard system.
Caution
SAP Note 39510 deals with points arising from the different sort sequences between
ASCII and EBCDIC. Programs that have been developed by the customer should be
checked for potential problems in connection with sorts, processing of ranges, SELECT-
OPTIONS, CPIC and up/download considerations. Authorization and domain definitions
should also be checked, as they may be specified by means of ranges.
Restrictions
Caution
The source system must be in a consistent state before it can be copied and the in-place
conversion should only be performed when the SAP System is inactive.
Caution
SAP recommends in any case that the *INTERACT memory pool should not be
configured, as there is normally very little truly interactive load on an R/3 system. For the
July 2002 1–5Introduction SAP AG
General Requirements and Restrictions
code page conversion it is important that this restriction be observed, as otherwise all the
R3SETUP procedures, which run in QINTER, will block the pool *INTERACT. As we
also recommend that performance adjustment (QPFRADJ) is turned-off, there is little hope
of the system correcting itself automatically in the worst case.
Note
The language-set code page may not be changed during the SAP code page conversion (for
example, Latin-1 (EBCDIC, 0120) to Latin-2 (ASCII, 1401)). If the system does not use
the SAP code page 0120 (see table TCPDB), create a message in component BC-INS-AS4
in the SAPNet − R/3 Frontend to obtain the necessary code page conversion tables. Code
page 0120 will be converted to 1100 during the standard code page conversion.
The following profile parameters should never be set on the system: Action Item
• install/codepage/db/transp
• install/codepage/db/non_transp
• install/codepage/appl_server
• abap/locale_ctype
Instead, table TCPDB should be correctly maintained for the system environment.
1–6 July 2002SAP AG Introduction
Organizational Preparations
Organizational Preparations
Note
Take into account the downtime of the source system (for preparations and conversion)
when planning the code page conversion.
Note
For BW and SEM systems, you must make sure that a minimum level of BW 2.1C with
Support Package 15 is installed on your system. If necessary, an upgrade should be
performed prior to the code page conversion. To avoid the following spurious but non-
critical errors in the post-conversion processing, SP17 or later should be installed. The
messages may be ignored if they occur.
Error Messages :
Cannot add index to table RSMDCNVTAB CHA Error # 3
Cannot add index to table RSMDCNVTAB SID Error # 3
Archive Files
If at all possible, make an archiving run before running the code page conversion, as this will
reduce the amount of data to be converted.
Configuration Analysis / Hardware Analysis
The following factors have to be determined:
• The expected size of the database
• Additional disks or other hardware required
• 10% additional memory required
• No additional CPU requirement
• Approximately 5% additional disk requirement for the exported pooled and cluster tables
during the in-place conversion
• For R/3 Systems: 55-70% additional disk requirement
• For BW or SEM systems: 40-50% additional disk requirement
Note
See Hardware and Software Requirements Check in the SAP System installation
documentation to determine the system requirements.
July 2002 1–7Introduction SAP AG
Organizational Preparations
Test Run / Schedule
• Perform a test run of the code page conversion. The time taken by the test run is used to
calculate the system downtime:
− Perform a complete test run, meaning that the entire database is converted.
Approximate system downtime will be equal to the total test time (that is, time for the
conversion and any post-installation processing).
− For BW and SEM systems, you must also take time to build the DB indices for the
Fact Tables and may have to rename the logical system.
− Test all critical transactions on the system after conversion.
Calculating the system downtime is particularly important for very large databases
(VLDB) or when tapes are being used.
• Define a schedule for the test conversion and the final conversion.
1–8 July 2002SAP AG Introduction
Technical Preparations
Technical Preparations
In order to ensure the consistency of the database, it is necessary to prepare the source system
and to carry out some subsequent actions after the conversion is complete. This is not
necessary when performing a test run.
The following list describes important preparatory actions (for further information on SAP
System administration, see the SAP Online Documentation).
Preparing the System
• Check that the latest IBM Info APAR for your system release has been implemented
before running the code page conversion.
• The latest ASCII kernel should be loaded to the system with at some convenient point
prior to the code page conversion using the following commands:
LODRUN DEV(*OPT) DIR(‘OS400/AS400/TOOLS’)
ADDLIBLE LODR3KRN
LODR3KRN SAVLIB(R346DAOPT) DEV(*STMF)
STMFDIR('/QOPT/CD51017882/OS400/AS400/V4R5M0')
KRNLIB(R346DAOPT)
This kernel may not be applied at this point, however. The apply kernel follows in the
course of the conversion procedure.
The ASCII runtime environment is also required for correct running of the R/3 System in
an ASCII environment. For operating system releases prior to V5R2M0, QADRT must be
implemented and entered in QSYSLIBL before the code page conversion is started. The
download for License Program 5799AAS to install QADRT may be found on the
Application Factory ASCII C/C++ Run Time Page at :
KWWS ZZZ LEPFRPGHYHORSHUIDFWRU\DVFLLUWLQGH[KWPO
The installation can be performed with the following command :
RSTLICPGM LICPGM(5799AAS) DEV(*SAVF) LNG(2924) SAVF(my_lib/QADRT)
To enter QADRT in QSYSLIBL, proceed as follows :
− WRKSYSVAL QSYSLIBL
− Enter option ‘2’ to change the system value QSYSLIBL
− Enter QADRT as the last entry in the system library list
Note
The entry of QADRT in the system library list has no impact at all on the running of SAP
systems in EBCDIC
• No canceled or pending update requests should be in the system. Check this via: Tools →
Administration → Monitor → Update (SM13). If canceled or pending updates exist, these
must be updated again or deleted from all clients. You can see whether canceled or
July 2002 1–9Introduction SAP AG
Technical Preparations
pending updates exist by finding out if table VBDATA contains any entries. Proceed as
follows in order to find the canceled or open updates:
1. Call transaction SM13.
2. Delete the default values for the client, user, and time.
3. Choose all update requests.
If canceled or pending records exist, then these must be updated again or deleted. Check
whether this action was successful using transaction SE16 for table VBDATA.
• Call DB02 and choose Refresh File Statistics to refresh the content of the statistics file
DBSTATTDB4, which is referenced to optimize the R3LOAD package sizes.
• On non-BW/SEM Systems you should run the consistency check of DB02 and save the
output for later comparison.
• Suspend all released jobs: this may be done with the report BTCTRNS1.
• FI customers: An additional consistency check can be performed by running the job
SAPF190 before the code page conversion, as well as after, and then comparing the
results. No customer data may be changed in the meantime. (Accounting → Financial
Accounting → General ledger → Periodic Processing → Closing → Check/count →
Comparison)
• FI customers: Consistency can be checked further by running the jobs RFUMSV00 (tax on
sales/purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions),
RAABGA01 (fixed asset retirements) before the code page conversion, as well as after, and
then comparing the results. No customer data may be changed in the meantime.
• CO customers: An additional consistency check can be performed by running the report
group 1SIP before the code page conversion, as well as after, and then comparing the
results. No customer data may be changed in the meantime.
• BW and SEM customers: Correction report SAP_DROP_TMPTABLES to delete
temporary objects
Tables from a special namespace are used to store and re-use temporary information in
BW systems. Since these tables are sometimes created using native SQL, no ABAP
Dictionary (DDIC) information exists for them. This can lead to problems if the tables are
converted. Since the information contained in these tables is in any case redundant, they
should be deleted before performing the code page conversion. The name of such tables
should match one of the following patterns:
− /BI0/01
− /BI0/02
− /BI0/02T
− /BI0/03
− /BI0/04*
− /BI0/06
As logging is performed on other BW tables, these tables should not be deleted using
native SQL. Use the report SAP_DROP_TMPTABLES, specifying all the parameters, to
delete them.
• BW and SEM customers: Correction report SAP_BW_MIGRATION
1–10 July 2002SAP AG Introduction
Technical Preparations
− Check for changed Infocubes, ODS Objects and PSA structures
Infocubes will be activated during code page conversion to generate the correct
structures (table layout, indexing). Therefore, check the system to ensure that there
are no new versions of these objects, which have not yet been activated. All the latest
versions should be activated before starting the code page conversion and also prior to
any other pre-unload analyses, as the activation may also have an impact on them.
Run report SAP_BW_MIGRATION, specifying the parameters as follows :
‘Modified Versions’ (P_MODIF) = only check for changes.
‘Check and Repair’ (P_REPAIR) = perform the check and then automatically
generate all changed objects
− Check the Data Class
BW transactional data tables, which are in fact tables, are handled differently from
other table types (for example, Basis tables, metadata) by the code page conversion.
The data class is used to recognize these tables, which should belong to class
DFACT. No other tables should be entered in this data class.
Run report SAP_BW_MIGRATION with the parameters set as follows :
‘Differing Data Classes’ (P_DATACL) = check data classes
‘Check and Repair’ (P_REPAIR) = perform the check and then automatically
generate all changed objects
− DB2/400-Specific Operations on the Source System
Due to a long-standing program error, there is a possibility that some entries in the
table DBDIFF may be incorrect. This can cause problems during the generation of the
new ASCII system. In order to avoid these problems, the program
SAP_BW_MIGRATION should be run with the parameter ‘Repair DBDIFF Entries’
(P4_DBDIF) specified.
Due to program cancellations, a situation may rarely arise, whereby temporary BW-
Tables are not registered in BW. The report SAP_DROP_TMPTABLES will not,
therefore, clear these tables. The program SAP_BW_MIGRATION should be run
afterwards, with the parameter ‘Delete Temporary Tables’ (P4_TMPTA) specified in
order to remove these tables.
Once the reports SAP_DROP_TMPTABLES and SAP_BW_MIGRATION have been
run, no more work may be done in the BW system, since the effects of these
corrections could be undone by the BW functions.
At this point the code page conversion should be started.
Caution
Prerequisites for a code page conversion:
July 2002 1–11Introduction SAP AG
Technical Preparations
Before running the in-place code page conversion, make sure that:
- No upgrade-prepare is performed.
- No incremental conversion is in progress.
To test if an incremental conversion is in progress, start the transaction ICNV. If there are
any table entries in the TICNV, an incremental conversion is in progress. In this case, you
have the following options:
1. Defer the code page conversion until the incremental conversion has finished.
2. Try to finish the incremental conversion by performing the following steps:
a) If the tables are in state ‘For conversion’ or in state ‘Done’, delete the entries by
choosing CONTROL -> DELETE ENTRY.
b) If the tables are in any other state, you have to finish the incremental conversion.
Choose the button Assistant and proceed according to the Online Documentation.
1–12 July 2002SAP AG Introduction
Code Page Conversion Tool Considerations
Code Page Conversion Tool Considerations
Note
It is recommended that you use the latest version of the code page conversion tools
R3SETUP, R3LDCTL and R3LOAD for your SAP System release (EBCDIC and/or
ASCII) if not stated otherwise. If patches for the programs are available, you can
download them from the SAP Service Marketplace. Otherwise, the latest version will be
available on the conversion CD.
You can find the EBCDIC patches at:
http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000019588&
No patches are currently available for the ASCII version.
For the latest documentation, refer to SAP Note 500950.
July 2002 1–13SAP AG R3load In-Place Procedure on iSeries
Contents
Chapter 2: R3load In-Place Procedure on iSeries
Contents
Overview ........................................................................................................................ 2–2
Requirements and Restrictions ................................................................................... 2–3
Requirements............................................................................................................. 2–3
Technical Restrictions ................................................................................................ 2–3
Preparing the In-Place Conversion ............................................................................. 2–4
Loading the Objects Required for the Conversion ..................................................... 2–4
Copying the Command Files from CD ....................................................................... 2–4
Unloading the Database ............................................................................................... 2–5
User Entries for R3SETUP......................................................................................... 2–5
Converting to the ASCII Code Page ............................................................................ 2–7
Converting to the ASCII Code Page on iSeries.......................................................... 2–7
Installing a Central Instance with Database ............................................................... 2–9
Troubleshooting .......................................................................................................... 2–12
In the Database Unload............................................................................................ 2–12
In the Database Load............................................................................................... 2–14
July 2002 2–1R3load In-Place Procedure on iSeries SAP AG
Overview
Overview
This chapter describes the in-place code page conversion procedure for the DB2/400
platform.
With the SAP installation tool R3SETUP, you can export and import your database in a
database-independent format. This procedure generates a database export of all SAP
cluster and pooled tables and converts all others that are defined in the ABAP Dictionary
in-place, without performing an export/import.
The R3load procedure consists of three main steps:
1. Unloading the pool and cluster databases that are not to be converted in-place
2. Performing the in-place conversion for the transparent tables
3. Reloading the pooled and cluster databases
Caution
Only central instances will be converted by this procedure. Application servers should
be deleted and re-installed. 3-tier sites will need to reconfigure to 2-tier for the
duration of the code page conversion procedure.
2–2 July 2002SAP AG R3load In-Place Procedure on iSeries
Requirements and Restrictions
Requirements and Restrictions
Requirements
• The PTFs SF67186 (V4R5) or SI03716 (V5R1) from IBM are prerequisites for the
in-place conversion procedure. From operating system release V5R2M0 the PTF is
included in the standard system.
• A full system backup should be performed before beginning with the code page
conversion.
• Sufficient free disk space for the in-place conversion.
About 5% additional space will be required temporarily, for the pooled and cluster
tables that must be exported.
For an R/3 system, an increase of 55-70% disk space utilization may be expected
after the in-place conversion. For BW, an increase of about 50% in the database size
may be expected.
Technical Restrictions
• R3SETUP will convert all SAP objects that are defined in the ABAP Dictionary.
Other objects are not converted by R3SETUP (for example, amended query option
files – QAQQINI copied and amended for specific system).
• Changes to database objects that cannot be maintained in the ABAP Dictionary
(Transaction SE14) will not be converted.
• Some objects (for example, EVIs) will not be converted even though they are
accessible with SE14. EVIs from the BW standard system will be rebuilt when report
SAP_INFOCUBE_INDEXES_REPAIR is run. Any customer-generated EVIs will
have to be manually rebuilt.
• No index names longer than 18 characters are allowed on the database to be
converted.
• The language-set code page may not be changed during the conversion (for example,
Latin-1(EBCDIC, 0120) may not be converted to Latin-2 (ASCII, 1401) or vice-
versa). If source tables do not have an SAP code page of 0120, you should create a
message on component BC-INS-AS4 in the SAPNet – R/3 Frontend to obtain the
necessary code page conversion tables. The standard code page conversion will
convert EBCDIC 0120 to ASCII 1100.
See also the section ”General Requirements and Restrictions” in chapter “Introduction”.
July 2002 2–3R3load In-Place Procedure on iSeries SAP AG
Preparing the In-Place Conversion
Preparing the In-Place Conversion
See also the chapter “Introduction”, section “General Preparations”, and the chapter
”Preparations”.
Loading the Objects Required for the Conversion
1. Sign on to your iSeries machine with a user that has the same authority as QSECOFR.
2. Enter the command:
CALL R3400/R3INLPGM.
3. Check that the library R3SETUP does not exist. It should be renamed if it exists.
4. Place the code page conversion CD into the CD drive of your iSeries machine.
5. To load the objects required for installation and configuration from the CD, execute
the LODRUN (Load and Run) command by entering:
LODRUN DIR(‘/OS400/AS400/INSTALL’)
Copying the Command Files from CD
1. Add the R3SETUP library to your library list. To do so, enter the following command:
ADDLIBLE R3SETUP
Note
If, for any reason, the library R3SETUP is to be renamed on your system then this
must be done before the CPYR3CPC command in step 3 is executed. The command
sets up a new link based on the name of the R3SETUP library. A subsequent rename
will invalidate this link.
2. Check that the directories /tmp/unload/, /tmp/reload/ and
/tmp/data/ do not exist.
3. Enter the command:
CPYR3CPC SID() METHOD(*INPLACE)
is the SAP system ID of the system you want to convert.
4. Log off from the system.
The following template files are copied to the directories listed below:
/tmp/unload/ DBEXIP.R3S
/tmp/reload/ DBCPIP.R3S, DBCPIPBW.R3S
In addition the directory /tmp/data/ is also created to contain the export files.
2–4 July 2002SAP AG R3load In-Place Procedure on iSeries
Unloading the Database
Note
Running R3SETUP (General Procedure)
For information on using R3SETUP, see Chapter 5 of the documentation SAP Basis
Installation: IBM eServer iSeries
Unloading the Database
User Entries for R3SETUP
Caution
Authorization problems might occur due to a switch from your logon user to
OFR. Therefore, you should always log off and then log on again as a user
with QSECOFR authorization before restarting R3SETUP.
1. Sign on again to your iSeries machine with a user that has the same authority as
QSECOFR.
2. Enter the following commands :
CALL R3400/R3INLPGM
STOPSAP (and wait until the system has really stopped)
cd ’/tmp/unload/’
addlible R3SETUP
Note
Use DSPLIBL to ensure that R3SETUP is ahead of the kernel in your library list.
CHGMSGQ MSGQ(QSECOFR) DLVRY(*HOLD)
CHGJOB BRKMSG(*HOLD)
The change to the message queue and the job should prevent long-running terminal
sessions being held up by BREAK messages.
Note
If SAPOSCOL is active on this , it should also be stopped.
3. Start R3SETUP with the specified command file option, specifying the command file
to unload the pooled and cluster tables that are not to be converted in-place:
July 2002 2–5R3load In-Place Procedure on iSeries SAP AG
Unloading the Database
R3SETUP dbexip.r3s
4. In the Requesting installation details step (CENTRDBINSTANCE_IND_DB4ASCII),
you are prompted to enter your choice or confirm the default value:
• The SAP system ID of the EBCDIC system, this must be the original .
• The SAP instance number of the EBCDIC system, this must be the original
number.
• The name of the SAP central instance host of the EBCDIC system, this must be
the original host-name.
• The maximum number of parallel processes you wish to run, for example 8.
Note
SAP recommends a value of #CPUs * 4 for this parameter if you are able to use
100% of the available processing capacity.
R3SETUP now runs through the remaining export steps without requiring further user
entries. A complete list of the steps is given here. The output files will be split up into
export files with suffix .001, .002, .003, and so on. The size of the export files will be
calculated based on an internal algorithm in R3LOAD.
Step Description Technical Name
Requesting export details DB4CPC_DBEXPORTINSTANCE_OS4_DB4
Check validity of TCPDB entry DB4CPC_TR_TCPDBCHECK_OS4_IND
Requesting export-specific parameters DB4CPC_DBEXPASSISTENT_OS4_DB4
Requesting information on CD-ROMs DBEXPSERVER_IND_IND
Creating the export directories DBEXPDIRECTORIES_IND_DB4
Creating the R3load control files DB4CPC_R3LDCTL_OS4_DB4
Clear Monitor Data DB4CPC_DB4CLEANUPEXPORT_OS4_IND
Creating a link for R3load R3LOADLINK_IND_DB4
Copying the control files for R3load DBEXPCOPYR3LDCTLFILES_IND_IND
Creating the command files for the export DB4CPC_DBEXPR3LOADCMD_OS4_DB4
Preparing to start R3load DBR3LOADEXECDUMMY_IND_IND
Exporting the database DB4CPC_DBEXPR3LOADEXEC_OS4_DB4
When the export has finished, R3SETUP ends with the message R3SETUP finished.
List of Files Unloaded from iSeries
Files from Directory /tmp/data/
2–6 July 2002SAP AG R3load In-Place Procedure on iSeries
Converting to the ASCII Code Page
Files with extension 001, 002, ...
Files with extension STR, TOC, TPL
Watching the Unload Progress
All error messages, warnings and other information from R3SETUP are written to the log
file DBEXIP.log.
You can obtain online help on a message by clicking on it in the log view and choosing
Help.
Important error, warning and info messages are also written to your terminal and to the
message queue R3DATA/R3CPCWARN.
When R3SETUP Stops
If R3SETUP exits with an error message, see the log file for error details and possible
solutions. Eliminate the cause of the error and restart R3SETUP. The unload will be
continued with the step that had not finished successfully.
When the unload is completed, R3SETUP ends with the message R3SETUP finished.
Caution
PLEASE NOTE : DO NOT, UNDER ANY CIRCUMSTANCES,
ATTEMPT TO START THE R/3 SYSTEM IN THE PERIOD
BETWEEN RUNNING R3SETUP TO UNLOAD AND THEN RUNNING
IT AGAIN TO RELOAD THE CONVERTED DATABASES
Converting to the ASCII Code Page
Converting to the ASCII Code Page on iSeries
Performing the Switch to the ASCII Kernel
Note
This switch must be performed after the R3SETUP unload using the EBCDIC kernel
has been successfully completed and before the R3SETUP conversion of the central
instance is started.
July 2002 2–7R3load In-Place Procedure on iSeries SAP AG
Converting to the ASCII Code Page
Use the following procedure to activate the ASCII kernel, which has been previously
loaded from the migration CD. For more information, see “Technical Preparations”.
RMVR3KRN
ADDLIBLE
APYR3KRN SID() KRNLIB() DLTSQLPKG(*YES)
Note
If the deletion of the SQL-Packages does not work for any reason, you can either
repeat the APR3KRN command as given above or use DLTR3PKG to delete them
DLTR3PKG SID() PKGTYPE(*ALL)
If the deletions still fail, delete the packages manually. The libraries from which they
need to be deleted have names of the format R3annnn. SQL Packages are also
contained in libraries with the generic name R3X000*
Please note : No SQL Packages should be deleted from the library QSYS !
Caution
Log off from the session to clean up any residual session pointers to EBCDIC objects.
2–8 July 2002SAP AG R3load In-Place Procedure on iSeries
Converting to the ASCII Code Page
Reloading the Database
Caution
Authorization problems might occur due to a switch from your logon user to
OFR. Therefore, you should always log off and then log on again as a user
with QSECOFR authorization before restarting R3SETUP.
1. Sign on again to your iSeries machine with a user that has the same authority as
QSECOFR..
2. Run the initial program to set up the OFR environment:
CALL R3400/R3INLPGM
CHGMSGQ MSGQ(QSECOFR) DLVRY(*HOLD)
CHGJOB BRKMSG(*HOLD)
The change to the message queue and the job should prevent long-running terminal
sessions being held up by BREAK messages.
3. Add the library R3SETUP to your library list and change your current directory to the
one containing the reload templates:
ADDLIBLE R3SETUP
CD ‘/tmp/reload/’
4. Start R3SETUP specifying the command file for converting the code page of an R/3
dialog instance:
R3SETUP dbcpip.r3s
For BW and SEM systems: Use the template dbcpipbw.r3s
5. In the Requesting installation details step (CENTRDBINSTANCE_IND_DB4ASCII),
you are prompted to enter your choice or confirm the default values:
• Your SAP system ID of the ASCII system. The original must be entered
here.
• The SAP instance number of the ASCII system. The original instance number
must be entered here.
• The name of the SAP central instance host of the system. The original host name
must be entered here.
• Enter the name of the ASCII Kernel Library
• Enter the number of parallel R3load processes you require, for example 8
Note
SAP recommends a value of #CPUs * 4 for this parameter if you are able to use
100% of the available processing capacity.
July 2002 2–9R3load In-Place Procedure on iSeries SAP AG
Converting to the ASCII Code Page
R3SETUP now runs through the remaining installation steps without requiring further
user entries, unless the password for the DDIC user has been changed from the default
value. If this change has been made, then a password-entry will be required for the steps
which run after DBR3START_IND_DB4ASCII. A complete list of the performed steps is
listed below:
Step Description Technical Name
Requesting installation details DB4CPC_CENTRDBINSTANCE_OS4_DB4ASCII
SAP codepage needed to install an ASCII DB4CPC_DB4ASCIIINFO_IND_DB4ASCII
system
Check that the ASCII kernel is available DB4CPC_CHKASCIIKRN_OS4_IND
Checking Available Space for the SAP Instance DB4CPC_CENTRDBSPACECHECK_OS4_DB4ASCII
Requesting information on CDs DB4CPC_CDSERVERMIG_OS4_DB4ASCII
Delete SQL Packages DELETE_EPACKAGE_OS4_DB4ASCII
Create ASCII locales DB4CREATELOCALE_IND_DB4ASCII
Copying the PTF Check File CPYPTFFILE_IND_DB4ASCII
Checking if the DB Export CD is available CHECKEXPORTCDINCDROM_IND_IND
Creating a link for R3load R3LOADLINK_IND_DB4ASCII
Clean up selected data (DDIC, DBMON, IFS) DB4CLEANUPASCII_OS4_IND
Copy sort sequence tables DB4CREATESORTTABLE_IND_DB4ASCII
Creating the command files for the DB load DBR3LOADCMD_IND_IND
Preparing to load the ABAP Dictionary tables DBR3LOADDDICDUMMY_IND_DB4ASCII
Loading the ABAP Dictionary tables DB4CPC_DBR3LOADDDIC_OS4_DB4ASCII
Preparing to start R3load DBR3LOADEXECDUMMY_IND_IND
R/3 Systems only: Loading the database DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII
BW/SEM Systems only: Loading the database DB4CPC_DBR3LOADEXEC_BW_OS4_DB4ASCII
BW/SEM Systems only: Loading the BW Fact DB4CPC_DBR3LOADFACT_OS4_IND
Tables
Preparing to load the database views DBR3LOADVIEWDUMMY_IND_IND
Loading the database views DB4CPC_DBR3LOADVIEW_OS4_DB4ASCII
Deleting ASCII loads DELETELOADS_IND_DB4ASCII
Starting journaling STARTJOURNAL_IND_DB4ASCII
Ensuring ABAP Dictionary consistency DIPGNTAB_IND_DB4ASCII
Deleting the SQL packages DELETE_PACKAGE_IND_DB4ASCII
Changing code page specific records DB4CPC_TCPDBENTRY_OS4_IND
Clear the tables TATGPC and TATGPCA DB4CLEANUPTATGPC_OS4_IND
Creating a temporary R/3 license DBR3LICSTANDALONE_IND_DB4ASCII
Starting the R/3 System DBR3START_IND_DB4ASCII
Post-activation of runtime objects for RFCRDDGENMC_IND_IND
2–10 July 2002SAP AG R3load In-Place Procedure on iSeries
Converting to the ASCII Code Page
synchronous matchcodes
Adjust background entries RFCRSBTCUPD_IND_IND
July 2002 2–11R3load In-Place Procedure on iSeries SAP AG
Troubleshooting
Troubleshooting
In the Database Unload
Technical Name Problem Solution
Unexplained error in job Logoff and logon again
log ‘R3SETUP ended before restarting
abnormally’. No other R3SETUP.
error messages.
DbSl returns error DLTR3PKG and then
SQL0104 (RC=-104) restart R3SETUP
‘Invalid token’
DB4CPC_DBEXPORTINSTANCE_OS4_DB4 Message : Name Incorrect version of
Db4CodePageConv not R3SETUP is being used.
known to registry Probably an old version is
being used due to an
incorrect library list or else
the latest patches for the
EBCDIC versions of
R3SETUP, R3LDCTL and
R3LOAD have not been
downloaded from the SAP
Service Marketplace
DB4CPC_TCPDBCHECK_OS4_IND More than one code The fields CPTRANSFLD
page defined in the table and CPPOOLCLUS must
TCPDB. contain the same, valid
code page value. There
should be only one entry !
DB4CPC_TCPDBCHECK_OS4_IND Conversion of code page Only code pages 0120,
xxxxx not supported by 0410, 0500, 0610, 0700,
SAP 0800 and 0860 are
supported
DB4CPC_R3LDCTL_OS4_DB4 Message : invalid or Incorrect version of
incomplete option “-o” R3LDCTL is being used.
for Probable cause: the latest
/sapmnt//exe/ patches for the EBCDIC
R3ldctldb4 –o versions of R3LDCTL and
R3LOAD have not been
downloaded from the SAP
Service Marketplace
DB4CPC_DBEXPR3LOADEXEC_OS4_DB4 QCM tables exist in the Check the situation using
nametab but not on the the following SELECTs to
database. For possible compare, then delete the
reasons, see note 9385. relevant entries from
2–12 July 2002SAP AG R3load In-Place Procedure on iSeries
Troubleshooting
SAPAPPL1_n.STR.
SELECT * FROM
R3DATA/DDNTT
WHERE TABNAME LIKE
‘QCM%’
SELECT * FROM
R3DATA/DDNTF
WHERE TABNAME LIKE
‘QCM%’
.
July 2002 2–13R3load In-Place Procedure on iSeries SAP AG
Troubleshooting
In the Database Load
Technical Name Problem Solution
Unexplained error in job Logoff and logon again
log ‘R3SETUP ended before restarting
abnormally’. No other R3SETUP.
error messages.
DbSl returns error DLTR3PKG and then
SQL0104 (RC=-104) restart R3SETUP
‘Invalid token’
DB4CPC_CENTRDBINSTANCE_OS4_DB4AS Message : Name Incorrect version of
CII Db4CodePageConv not R3SETUP is being used.
known to registry Probably an old version is
being used due to an
incorrect library list.
DB4CREATELOCALE_IND_DB4ASCII Message ‘Locale Install Extended NLS
xx_xx_Isnn using ccsid Support (Licpgm.
500 failed to create into 5769SS1 Product Option
R3400 ‘ 21)
DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII Message: SQL0603 Wait until all R3LOAD
‘Unique index cannot be jobs have finished and then
created because of perform the following
duplicate keys’ during procedure for any tables
creation of primary key with the SQL0603 problem
1. CRTDUPOBJ with
DATA(*YES) to copy the
contents of the affected
table to a separate library
2. delete the table in
R3DATA using
CLRPFM
3. restart R3SETUP after
performing steps 1 and 2
for any affected tables. The
create of primary keys
should work now
4. CPYF with
ERRLVL=*NOMAX to
recreate each table saved in
step 1 in R3DATA
Duplicates will be dropped
and logged in the joblog
2–14 July 2002SAP AG R3load In-Place Procedure on iSeries
Troubleshooting
Open a problem report in
BC-INS-AS4.
DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII CHGPF for the CCSID Create a message in
fails due to existence of SAPNet – R/3 Frontend in
a CCSID mod. flag on component BC-INS-AS4.
some individual
column(s) of the
database.
DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII SAP* log files contain Reorganise the affected file
SQL –906 errors from and increase the maximum
DbSl.. The R3LOAD access path size to 1 TB, as
joblog has MCH3203 follows :
with error code RGZPFM
1720,error class 0 FILE(R3DATA/xxx
xx)
CHGPF
FILE(R3DATA/xxx
xx)
ACCPTHSIZ(*MAX1TB)
DB4CPC_TCPDBENTRY_OS4_IND Error 250 : unable to Investigate the job log for
change code page table additional messages. If you
TCPDB cannot solve the problem,
then open a problem report
under BC-INS-AS4.
DB4CPC_TCPDBENTRY_OS4_IND Error 251 : inplace Use the Export/Import
conversion only allowed procedure
for code page 0120
DB4CPC_TCPDBENTRY_OS4_IND Error 252 : invalid Correct the parameter in
parameter error
DB4CPC_TCPDBENTRY_OS4_IND Error 253 : conversion Only code pages 0120,
of code page xxxxx not 0410, 0500, 0610, 0700,
supported by SAP 0800 and 0860 are
supported
DB4CPC_TCPDBENTRY_OS4_IND Error 254 : invalid entry The fields CPTRANSFLD
in table TCPDB and CPPOOLCLUS must
contain the same, valid
code page value
DB4CPC_TCPDBENTRY_OS4_IND Error 255 : unable to It is necessary to logoff and
retrieve current code then logon between the
page from TCPDB unload and the reload steps
to ensure the correct system
environment
RFCRDDGENMC_IND_IND Lock wait (LCKW) Use WRKACTJOB to
RFCRSBTCUPD_IND_IND problems during the investigate the situation.
running of these reports. “Kill” all but one of the
July 2002 2–15R3load In-Place Procedure on iSeries SAP AG
Troubleshooting
ABAPs are being affected work processes,
generated during the allowing them to restart
start of the SAP system normally. After this, the
and this conflicts with problem is normally solved
the run requests in these as the SAP system will
steps. have performed its
COMMITs by then. You
can then restart the
procedure if necessary.
2–16 July 2002SAP AG General Subsequent Actions
Contents
Chapter 3: General Subsequent Actions
Contents
Subsequent Technical Actions............................................................................................ 3–2
Subsequent Actions Required on the ASCII System ......................................................... 3–2
July 2002 3–1General Subsequent Actions SAP AG
Subsequent Technical Actions
Subsequent Technical Actions
Subsequent Actions Required on the ASCII System
Actions on Operating System Level
• Adapt the configuration files on operating system level to meet network and SAP
requirements.
• Adapt additional software components, for example, RFC, CPIC, SAP ArchiveLink, if
required.
Actions on Database Level
None required
Actions on SAP System Level
• Run installation check: Tools → Administration → Administration → Installation Check
(transaction SICK).
• Delete the SAPscript loads as described in note 6873
• Delete canceled and finished jobs.
Execute program RSBTCDEL, marking the field delete with forced mode: Tools → ABAP
Workbench → ABAP Editor (SE38).
• Reschedule your cancelled jobs using report BTCTRNS2.
• Adapt all jobs needed in the target system:
1. Copy the old jobs
2. Modify the new jobs
3. Delete the old jobs.
• Check the consistency of the Temporary Sequential Objects (TemSe) (“Are there files of
TemSe objects for which no TemSe objects exist?”): Tools → CCMS → Spool → TemSe
administration (SP12). For more information, see SAP Note 16875.
• Adapt the definition of the printers (device types and character set definitions) to meet the
new system requirements.
• Adapt the RFC destination: Tools → Administration → Administration → Network →
RFC destinations (SM59). Clean the transactional RFC: Tools → Administration →
Monitor → Transactional RFC (SM58). See the relevant description in the SAP Online
Documentation.
• Check and, if necessary, amend or reactivate system profiles using transaction RZ10.
• Adapt other CCMS settings, for example, alert thresholds, if required.
• Make data archived in the source system (data that does not reside in the database but was
moved to a different storage location using SAP Archive Management) accessible in the
ASCII system. Adapt the file residence information in the ASCII system. Refer to the SAP
3–2 July 2002SAP AG General Subsequent Actions
Subsequent Technical Actions
Online Documentation (Basis Components → System Administration → Application Data
Archiving and Reorganization) for help.
Checking the ASCII System
The following actions are suitable for checking the consistency of the ASCII system:
• Call transaction STMS to set up the Transport Management System.
• Perform initial consistency check (SM28).
• Check the system log (SM21).
• Non-BW/SEM Systems : Check the consistency of the database (DB02) and compare
with the consistency check which you ran prior to the in-place conversion.
• Perform server check (SM51).
• Test transactions frequently used by the customer.
• FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results
to those gained on the source system before the code page conversion (Accounting →
Financial Accounting → General ledger → Periodic Processing → Closing →
Check/count → Comparison).
• FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history
sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) and compare
the results to those gained on the source system before the code page conversion.
• CO customers: Run the report group 1SIP and compare the results to those gained on the
source system before the code page conversion.
• BW customers: Up to this point in the conversion procedure the Fact Tables have neither
been converted nor generated, since neither R3LDCTL nor R3LOAD is able to process the
required information. The newly-installed BW system contains the logic to perform this
task, however. Start the report SAP_INFOCUBE_INDEXES_REPAIR in the background.
If Symmetric Multiprocessing (SMP) is installed on your system, it should be used to
speed up the index creation. Nevertheless, SMP should be deactivated again afterwards, as
it is not usually necessary for the normal operation of a BW system.
Note
Only EVIs from the BW standard system will be rebuilt by this procedure. It is the
customer’s responsibility to generate any EVIs that were generated outside the standard.
While the indices for the Fact Tables are being rebuilt, you can perform the final BW-
specific operations after the code page conversion. Run the report
SAP_BW_MIGRATION, specifying parameter ‘Index Model Tables’(P4_DMTAB), to
activate missing indices for a number of model tables. This only takes a few seconds.
July 2002 3–3You can also read
