Sys
Sys
Sys
Export preparation:
Export:
PV1w0r1d
Next
10
Note: Create a folder(PV1EXPORT) where you want to take the export of the source system(PV1) Next
11
Neglect it
12
next
13
Next
14
Next
15
next
16
17
18
19
20
Export_monitor.log
ERROR: 2009-10-20 20:11:26 com.sap.inst.migmon.LoadTask run Unloading of 'SAPAPPL0' export package is interrupted with R3load error. Process 'H:\usr\sap\PV1\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL0.cmd -datacodepage 4103 -l SAPAPPL0.log -stop_on_error' exited with return code 2. For mode details see 'SAPAPPL0.log' file. Standard error output: sapparam: sapargv( argc, argv) has not been called. sapparam(1c): No Profile used. sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
H:\usr\sap\PV1\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP H:\usr\sap\PV1\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE] Compiled Nov 18 2008 23:19:12 H:\usr\sap\PV1\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL0.cmd -datacodepage 4103 -l SAPAPPL0.log -stop_on_error
(DB) INFO: connected to DB (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8 (DB) INFO: Export without hintfile (GSI) INFO: dbname = "PV120090811070846 " 21
(GSI) INFO: vname = "ORACLE (GSI) INFO: hostname = "BCHSAP007 (GSI) INFO: sysname = "Windows NT" (GSI) INFO: nodename = "BCHSAP007" (GSI) INFO: release = "5.2" (GSI) INFO: version = "3790 Service Pack 2"
" "
(GSI) INFO: machine = "8x AMD64 Level 6 (Mod 23 Step 10)" (GSI) INFO: instno = "INITIAL "
(RTF) ########## WARNING ########### Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(EXP) ERROR: DbSlExeRead failed rc = 103, table "TPFET" (SQL error 942) error message returned by DbSl: ORA-00942: table or view does not exist (DB) INFO: disconnected from DB
22
https://forums.sdn.sap.com/thread.jspa?threadID=1171791
SQL> select USERNAME from dba_users; USERNAME OPS$SAPSERVICERSD OPS$ORARSD OPS$RSDADM SYS SYSTEM SAPSR3 SAPSR3DB OUTLN TSMSYS DIP DBSNMP 11 rows selected.
SQL> desc sapsr3.taora; ERROR: ORA-04043: object sapsr3.taora does not exist
Seems like tables are not created in the target system. Was the import phase successful? Carefully analyze the import logs and check for errors.. Two more questions... Did you create the oracle tablespaces manually? Did you run SMIGR_CREATE_DDL in the source system before export? Solve by creating the tables manually
23
(EXP) ERROR: DbSlExeRead failed rc = 103, table "TPFET" (SQL error 942) error message returned by DbSl: ORA-00942: table or view does not exist
Goto
24
SAPAPPL0.TSK
Solution: no problem, you have an extra entry in your active nametab. You could delete the entry if the table does not exists in DDIC and DB. You may also set the table in the Task file (SAPAPPL0.TSK) from err to ign (ignore). This will export this package without this table. SAPAPPL1.log
(EXP) ERROR: DbSlExeRead failed rc = 103, table "TPFHT" (SQL error 942) error message returned by DbSl: ORA-00942: table or view does not exist (DB) INFO: disconnected from DB
SAPAPPL1.TSK
Solution
You may also set the table in the Task file (SAPAPPL1.TSK) from err to ign (ignore). This will export this package without this table.
25
Start the SMIGR_CREATE_DDL program before you export the data from the source system. This program allows you to copy database objects that do not correspond to SAP standards. These objects include partitioned (fragmented) tables and bitmap indexes. Special '<TABART>.SQL' files are generated for these objects. These files contain 'native DDL' (create) statements and can be analyzed by R3load. Proceed as follows: * Log on to the live BW client as a user with 'SAP_ALL' rights. * Go to transaction SE38 and call program 'SMIGR_CREATE_DDL'. * Select the database platform and the database version of your target system. * Set the 'Unicode migration' indicator if your target system is an SAP Unicode system. * Specify a directory for the '<TABART>.SQL' files to be generated. * Execute program 'SMIGR_CREATE_DDL'. The system now generates the DDL statements and writes them into the directory specified. * You must ensure that no more changes, such as activations or field changes, are made in the BW system after you call the SMIGR_CREATE_DDL report and before you export the data. The safest thing to do is to call this report directly before the export while the system is still locked for the user. * The report SMIGR_CREATE_DDL creates files of the form <TABART>.SQL. If these files are not created, then BW-specific processing is not required because tables of this type do not exist in the system. This is the case if BW is not operated actively in the system. In this case, this note no longer applies and the migration should be carried out in accordance with the standard guidelines. You can access report 'SAP_DROP_TMPTABLES' (see Note 449891) before the export if you experienced problems with temporary tables during the test import. This report deletes all temporary tables. However, this has a short-term impact on query performance in the source system. Tasks after the export
Copy the generated DDL '<TABART>. SQL' files to the <export directory>/DB/<DBSYS> of the target system before you import the data. This is the only way that R3load can evaluate these special files. Tasks after the import
After the successful import, you must call report RS_BW_POST_MIGRATION. For more information, see Note 948780.
26
27
IMPORT: Installation master Java components Export dvd kernel Errors during import phase For the export 1. Create database phase Before this phase Swap the kernel to what source has kernel level 144 during installation source has 185 but the installation sr3 has
144 185 usr/sap/SID/SYS/exe/uc/ntadm64 replace this with 185 kernel. 2.Import abap phase Goto Init(SID).ORA Processes 80 200 400
Issues after system copy 1. Java Engine cannot start Error: Core service p4 failed Configtool instance display/change cluster data instance property sheet change the host to the current (it will be having the host entry of PHV(source system) Configtool > instance > dispatcher > services > p4 > bindhost See SAP Note: 609603 - Problems with Multiple NICs and SAP J2EE Engine.
28
29
30
31
32
33
successfull
34
EXPORT:
1.INSTALL ORACLE 2.Copy the latest kernel of PHV(Source)-185 you need to replace during the installation while import 3. Start the installation
35
36
37
38
39
40
41
42
43
r0cknr011
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
r0cknr011
60
61
62
63
64
65
66
67
68
69
70
71
Note: SWAP the kernel with 185 of the source system before the create database stage. Note: the kernel mounted is 144
72
73
2. IMPORT ABAP phase D:\oracle\PQ5\102\database\initPQ5.ora processes = 80 sessions = 96 change it to processes = 200 sessions = 400 to avoid error during import ABAP phase error: no sufficient sessions
74
75
76
77
sapinst_dev.log Loading of 'SAPAPPL0_2' import package: ERROR Import Monitor jobs: running 15, waiting 9, completed 4, failed 1, total 29. Loading of 'DOKCLU' import package: ERROR Import Monitor jobs: running 13, waiting 9, completed 4, failed 3, total 29. Loading of 'D010TAB' import package: ERROR Import Monitor jobs: running 13, waiting 9, completed 4, failed 3, total 29. Loading of 'SAPNTAB' import package: ERROR Import Monitor jobs: running 12, waiting 9, completed 4, failed 4, total 29. Loading of 'REPOSRC' import package: ERROR Loading of 'SXMSCLUR' import package: ERROR Import Monitor jobs: running 10, waiting 9, completed 4, failed 6, total 29. Import Monitor jobs: running 10, waiting 9, completed 4, failed 6, total 29. Loading of 'SWWCNTP0' import package: ERROR Import Monitor jobs: running 9, waiting 9, completed 4, failed 7, total 29. Loading of 'SXMSCLUP' import package: OK 78
Import Monitor jobs: running 8, waiting 9, completed 5, failed 7, total 29. Import Monitor jobs: running 9, waiting 8, completed 5, failed 7, total 29. Import Monitor jobs: running 10, waiting 7, completed 5, failed 7, total 29. Import Monitor jobs: running 11, waiting 6, completed 5, failed 7, total 29. Import Monitor jobs: running 12, waiting 5, completed 5, failed 7, total 29. Import Monitor jobs: running 13, waiting 4, completed 5, failed 7, total 29. Import Monitor jobs: running 14, waiting 3, completed 5, failed 7, total 29. Import Monitor jobs: running 15, waiting 2, completed 5, failed 7, total 29. Import Monitor jobs: running 16, waiting 1, completed 5, failed 7, total 29. Loading of 'SAPDODS' import package: ERROR Import Monitor jobs: running 15, waiting 1, completed 5, failed 8, total 29. Loading of 'SAPDDIM' import package: OK Import Monitor jobs: running 14, waiting 1, completed 6, failed 8, total 29. Loading of 'SAP0000' import package: OK Import Monitor jobs: running 13, waiting 1, completed 7, failed 8, total 29. Loading of 'SAPDFACT' import package: OK Import Monitor jobs: running 12, waiting 1, completed 8, failed 8, total 29. Loading of 'SAPUSER' import package: OK Import Monitor jobs: running 11, waiting 1, completed 9, failed 8, total 29. Loading of 'SAPSLOAD' import package: OK Import Monitor jobs: running 10, waiting 1, completed 10, failed 8, total 29. Loading of 'SAPCLUST' import package: OK Import Monitor jobs: running 9, waiting 1, completed 11, failed 8, total 29. Loading of 'SAPSDOCU' import package: OK Import Monitor jobs: running 8, waiting 1, completed 12, failed 8, total 29.
79
Loading of 'DYNPSOURCE' import package: ERROR Import Monitor jobs: running 7, waiting 1, completed 12, failed 9, total 29. Loading of 'SAPSPROT' import package: OK Import Monitor jobs: running 6, waiting 1, completed 13, failed 9, total 29. Loading of 'SAPSDIC' import package: OK Import Monitor jobs: running 5, waiting 1, completed 14, failed 9, total 29. Loading of 'D010INC' import package: OK Import Monitor jobs: running 4, waiting 1, completed 15, failed 9, total 29. Loading of 'SAPAPPL1' import package: OK Import Monitor jobs: running 3, waiting 1, completed 16, failed 9, total 29. Loading of 'SAPSSEXC_1' import package: OK Import Monitor jobs: running 2, waiting 1, completed 17, failed 9, total 29. Loading of 'SAPAPPL2' import package: OK Import Monitor jobs: running 1, waiting 1, completed 18, failed 9, total 29. Loading of 'SAPAPPL0_1' import package: OK Import Monitor jobs: running 0, waiting 1, completed 19, failed 9, total 29.
80
81
82
83
84
85
UPDATE STATISTICS 1.collect and then update statistics 2.check table spaces and adjust PSAPSR3 97 63 SYSTEM 96 15 SGEN
86
1. SE06
87
Yes
88
Yes
89
Note: if its a normal installation choose standard installation and move with yes 2. STMS
90
System overview
91
YES
92
93
-----------------------------------------------------------------------------------------------------------------------------------------3. SICK
3. SMLG
SAVE
94
RZ12
95
-----------------------------------------------------------------------------------------------------------------------------------------4. SM36 Standard jobs select all the jobs schedule them -------------------------------------------5. APPLY LICENSE SPAM status
ABAP SLICENSE
97
----------------------------------------------------------------------6. Operation modes Maintain here SM63, check here RZ04 SM63
Change
98
99
---------------------------------------------------------7.PROFILES Delete the old profiles Select the profile default delete Select the profile instance delete
Select the profile start delete Change the values from PHV to PQ5 ------------------------------------------------------8. STZAC CET to IST SU01 ----------------------------------------------10. SGEN 11. SALE
100
XI CHECKS
Change the values in the exchange profile ans start the changes else where in the system 1.
Login to IR and perform the following activities a. Check the JRE/install if not already b. Check whether PRIMAVERA 6.2 tpz, SAP BASIS 7.00 , SAP ABAP 7.00 are present c. Environment clear SLD Data cache d. tools transport from SLD import software component versions
101
Exit
102
103
104
105
106
YES
Or have PISUPER here Sld data supplier change the user to PI SUPER 107
108
109
110
111
112
113
114
115
116
Goto logon&security give the password (PHVSUPER1)once again and save Path prefix: /dir/CacheRefresh
117
TCP/IP
118
119
Note: If you do not perform the visual admin tasks then you get the above error for RFCs.
AI_RUNTIME_JCOSERVER
120
Change to PQ5
121
122
LCRSAPRFC
123
SAPSLDAPI
Change to PQ5
124
125
126
127
128
129
130
131
7. SPROXY
SPROX_CHECK_IFR_ADDRESS
SPROX_CHECK_HTTP_COMMUNICATION
132
SPROX_CHECK_IFR_RESPONSE
133
BUSINESS SYSTEM
2.INSPIRE
134
4.PRIMAVERA
135
RWB CHECKS:
136
137