SAP BI 4.0 - OS/DB Migration
Hello,
I'm looking for Best Practices to move one BI to a new OS & DB : Source Sun/Oracle 10, Target HPUX or Linux / Oracle 11
In "Business Intelligence Platform Administrator Guide - SAP BusinessObjects Business Intelligence platform 4.0 Support Package 4", Chap "13.5 Considerations and limitations" I saw that "The source and target operating systems must be the same." to perform a copy
Regards
William
Hi,
The reason that it requires the "The source and target operating systems must be the same." to perform a copy is because the copied SIA on the target Oracle 11 would still remember its $BOBJEDIR directory, including solaris_sparc in its path and also for all other servers, CMS, etc.
Thus, you may proceed the system database copy, but, you'd need to be able to delete the old node and create a new SIA/node via ccm.sh.
Before you remove the old SIA node from the CMS database, you'd need to find out its SI_ID, assuming it is 799, from CMC, then stop the SIA and use sqlplus to delete the existing node.
sqlplus CMS_ID@CMS_DB
sqlplus> select objectid from cms_infoobjects7 where objectid = 799;
sqlplus> delete from cms_infoobjects7 where objectid = 799;
sqlplus> commit;
I believe you can find the detail steps from a SAP BO KB as well.
Hope this helps,
Jin-Chong
Similar Messages
-
Best practice to change SAP BW login parameters after Universe migration
Hello All,
I am working with SAP BW and BOBJ XI 3.1.
And we are using "Use specified username and password" Authentication mode when we are establishing the connection to SAP BW. At present after migrating the Universe let's say from Dev to Test, We are logging in to the Universe in the Test environment and modifying the connection parameters to point the Universe to Test BW system.
By default when we migrate the Universe it's still pointingg to BW Dev system.
My question is when we use "Use specified username and password" Authentication mode, what's the best way to change the connection parameters.
I would greatly appreciate your input.
Thanks
PadmaIngo,
Thanks a lot for your response.
At present we are using the standard import wizard.
You think the LifeCycle Management has the option to change the login information during the migration??
Very soon we will be evaluating the tool.
Thanks
Padma -
TADM70: SAP System: Operating System and Database Migration
Dear Colleagues,
SAP is offering a rare opportunity to participate in "TADM70: SAP System: Operating System and Database Migration" in North America.
For details please see
<a href="https://service.education.sap.com/sap(bD1lbiZjPTAwMSZkPW1pbg==)/bc/bsp/sap/hcm_learning/trainingtype.htm?sap-params=b3R5cGU9RCZvYmppZD03MDAxNjA1MA%3d%3d">TADM70</a>
Usually this class is held only at overseas locations. SAP is willing to arrange it in North America. However we need to gather enough participants for this event to occur.
If you are interested and eligible to participate you could prebook this class at SAP Education Portal <a href="https://service.education.sap.com/sap(bD1lbiZjPTAwMSZkPW1pbg==)/bc/bsp/sap/hcm_learning/prebookings.htm">TADM70 Prebooking</a> and you could also contact Annie Normand [email protected] or myself.
Best regards,
Alexander Perelygin
SAP NetWeaver Team Lead
Terasen Gas Inc
E-mail: [email protected]
Phone: 604-592-7519Dear Collegues,
TADM70 : SAP System: Operating System a Classroom Training
will be held
09-Jun-2008 - 11-Jun-2008
at SAP Toronto Training location.
TADM70: SAP System: Operating System and Database Migration
Schedule
Day Date From To
Monday 09.06.2008 09:00 17:00
Tuesday 10.06.2008 09:00 17:00
Wednesday 11.06.2008 09:00 17:00
Availability
Location Language Price Free Places Start Date
SAP Toronto English 2325.00 CAD Yes 09.06.2008 Add to Shopping Cart
Taxes are not included in the price.
Contact Information
Address: SAP Toronto Bloor
1600-2 Bloor St. East
M4W 1A8 - Toronto Phone: 416-929-9746 Fax: 416-927-2160
Those who interested please book it at SAP Education web site or by phone.
Alexander Perelygin -
SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code
Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
<br>
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
<br>
We are again getting error in following steps:
<br>
sapinst.log
<br>
<br>WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
<br>Loading of 'SAPNTAB' import package: OK
<br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
<br>
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
<br>
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
<br>
<br>import_monitor.log.
<br>****************************************************************************************************************************************************
<br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
<br>
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
<br>
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
<br>
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
<br>*************************************************************************************************************************************************
<br>SAPAPPL02.LOG
<br>**************************************************************************************************************************************************
<br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
<br>
(DB) INFO: TVV1 deleted/truncated #20091001110304
<br>
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
<br>
(DB) ERROR: DDL statement failed<br>
(ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
DbSlExecute: rc = 99<br>
(SQL error -539)<br>
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
PrasadHello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
<br>
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
<br>
We are again getting error in following steps:
<br>
sapinst.log
<br>
<br>WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
<br>Loading of 'SAPNTAB' import package: OK
<br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
<br>
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
<br>
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
<br>
<br>import_monitor.log.
<br>****************************************************************************************************************************************************
<br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
<br>
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
<br>
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
<br>
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
<br>*************************************************************************************************************************************************
<br>SAPAPPL02.LOG
<br>**************************************************************************************************************************************************
<br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
<br>
(DB) INFO: TVV1 deleted/truncated #20091001110304
<br>
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
<br>
(DB) ERROR: DDL statement failed<br>
(ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
DbSlExecute: rc = 99<br>
(SQL error -539)<br>
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad -
SAP R/3 4.7 SR1 Migration to MSCS cluster environment
Hi all,
We are planning to move our existing standalone server R/3 production server to cluster environment.
I have some queries regarding this migration
Our R/3 system is running on SAP R/3 4.7x1.10 SR1 on Windows 2003 and Oracle 9.2
1. Central Instance has to be installed in local disk or shared disk
2. Is it correct to R3load procedures to export data from old server and import during Database installation
3. Presently our server is running with kernel 640, but for the new installation kernel will be 620. So when can i upgrade kernel immediately after central instance installation or after CI and DB Instance installation.
Give me some inputs
Thanks & Regards
KTHi, the best place for your questions would have been the forum SAP on Windows.
However, here the answers.
1) CI must be on a shared disk
2) Right, if you don't change the database platform and its release you can also use backup/restore
3) Right. You can also perform the installation with the latest NW04 installation master -
SAP Adapter Best Practice Question for Migration of Channels
I have a best practice question on the SAP adapter when migrating an OSB project from one environment (DEV) to another (QA).
If my project includes an adapter channel that (e.g., Inbound SAP Proxy listening on a channel), how do I migrate that project to another environment if the channel in the target environment is different.
I tried using the search and replace mechanism in the sbconsole, but it doesn't find the channel name in the jca and wsdl files.
What is the recommended way to migrate from one environment to the other when the channel name changes?I have a best practice question on the SAP adapter when migrating an OSB project from one environment (DEV) to another (QA).
If my project includes an adapter channel that (e.g., Inbound SAP Proxy listening on a channel), how do I migrate that project to another environment if the channel in the target environment is different.
I tried using the search and replace mechanism in the sbconsole, but it doesn't find the channel name in the jca and wsdl files.
What is the recommended way to migrate from one environment to the other when the channel name changes? -
SAP extract to Excel changed after migration from ECC5 to ECC6
Hi everyone,
This issue is about getting a proper table when displaying SAP reports in Excel. When extracting to Excel, the data base is presented with summary yellow lines whereas we would rather have a regular table without subtotal. This issue appeared when the system was migrated from ECC5 to ECC6. Please notice that one of the user has currently a proper display. Do you know which parameter shall we change?
Thanks!
Stan B.There are some default setting in the parameters,
Like
RPO0 - User Settings
From FI transactions you can change ti your default settings
Have a look to:
FIT_ALVC X FI Line Items: ALV Grid Control
With KSB1 I see it direct without sub totals and saving.
Click on spreatsheet
Select All Available formats
Select EXCEL (In Existing XXL Format) -
SAP BW on HANA: Error when migrating standard cube to the In-Memory Cube
Hello,
When migrating an standard infocube from a recently migrated BW to BW on HANA in-memory optimized cube, there is an error, for all the cubes.
Implemented few notes, though luck yet. Appreciate if those, who saw and resolved it can help.
Error while executing stored procedure for data implementation
Message no. RSDRI_HDB041
Diagnosis
The InfoCube data to be migrated is processed using a stored procedure. This procedure reported an error.
System Response
Error code: 257
Error text: sql syntax error: line 1 col 14 (at pos 14)
Regards
Manish MadhavHi Mahish,
I see this post is from March. I understand you have got some solution to it already.
If yes, could you please share the solution.
Thanks and regards,
Aaloka -
Queries related to ABAP Programs migration to SAP ECC 6.0
We are planning to re-implement SAP using SAP ECC 6.0 We are currently using SAP R3 Version 4.7
Regarding migration of existing ABAP Programs and data, I have some queries which may kindly be answered by any of the experts of this forum.
1. I have heard that SAP ECC 6.0 or SAP Netweaver 7.0 will never support BDC programs. To upload data into SAP, BAPI is the preferred option. Is that true?
2. In ABAP Programming, relational operator < (less than), > (greater than), <= (less than or equal to) etc are not supported by SAP Netweaver 7.0. In stead, operator contants LT, GT, LE etc must be used. Other wise, SAP reports syntax error. Is thar true?
3. Screens (Dynpros) have been fully programmed in ABAP Objects in almost all programs related to functional modules (SD,MM,PP,FI/CO etc) in SAP ECC 6.0. Is that true?
4. Programs written in SAP R/3 Version 4.7 will report syntax errors when that program is compiled as it is in SAP Netweaver. Is that true?
I request you to kindly reply for these four queries at the earliest.
Thanking you,
K. RANGARAJAN
ABAP ProgrammerSAP ECC6.0 will be supporting BDC programs too.But ,apart from this there are other options like LSMW ,BAPI, ECATT tool
which serves the same purpose . It doesnot mean that SAP wont support BDC.
Coming to relational operators u can use both of them but preferred is operator contants LT, GT, LE.
If there are any obsolete statements or any Obsolete function modules used in version4.7 U will get syntax errors or unicode errors.
Regards,
Lakshman. -
SAP Archiving - Migrating from one archive backend to another.
Hi,
We use SARA for archiving and the archiving system is IBM Provided Filenet Database with ACSAP middle-ware.
From 1999 till 2009 we have archived terabytes of data into Filenet Database.
We plan to discontinue Filenet as our choice of archiving backend system and will like to migrate all existing archived data to the new archivingsystem. We are yet to decide what new system will will move to.
We are looking for help from SAP to answer following questions:
1) Is it possible migrate all past data from existing archiving system to a new one?
2) If Yes, then what is the broad approach? Does the data have to be retrieved back to SAP OR Can it be directly migrated from one backend to another one?
Retrieving the data and reloading into another tool in my opinion would be rather cumbersome and stupid method until this is the only option.
In Any case, at the end of day we want that all the data should be readable from SAP like before.
3) Is there any SAP provided tool that we can use rather then going for a 3rd party product?
4) Please guide to migration related documentation.
Thank you in advance for your support.
Regards,
Chandra.Hello Chandra
yes- there are ways to migrate data out of Filenet into 3rd party tool without retrieving them back through SAP. I am not aware of any SAP tool itself but we have one and could help you with this effort. Please contact me at 610 3508677 and we can discuss the possibilities. -
Content Server Migration in SAP CRM 4.0
Hi,
we have the following problem:
We want to migrate old documents from an old content repository to a
new archive to see them in CRM. How to to this?
We found the note 1043676 to migrate them, but the note is only for SAP R/3. How to migrate old documents to a new one?
Regards
JochenHi
Please locate the boconfig.cfg file e.g. /home/bi4/BI4/setup/boconfig.cfg
If the file has only a few entries it is most definitely corrupted. Check if the boconfig.cfg_old has more lines, if yes make it boconfig.cfg
If that still fails:
- Restore the boconfig.cfg from a backup
- Copy the boconfig.cfg file from a working BI4 system
Then restart BI4
Regards
Roland -
SAP Oracle database 11.2 migrating from Solaris to RedHat Linux (x86_64)
What is SAP guidance on database migration ? What is the best approach ?
I heard person who does migration has to be certified by SAP.Jun He wrote:
Thank you for prompt response. When you say "heterogenous system copy" does not support it, do you mean SAP does not support the converted system or just the process itself ?
>
> Actually I am discussing with SAP about generating a system copy to send over to SAP and they said that Data Pump is an option they can accept. If Datapump is accepted by SAP internally, I would think after migration SAP should support datapump-migrated system.
Hi Jun,
I didn't said that SAP will not support your system, after the migration by Oracle data pump. I noted that OS/DB migration is performed by heterogenous system copy with the migration key.
Under this circumstance, if they accept to support you during the migration process with data pump, there's no problem. As I noted that previously, technically it is possible to migrate the system by using data pump, but I didn't requested that kind of support to SAP. I've been surprized to hear that they will support migration with Oracle data pump method. This is my own assestment.
Will they support you, if you face with a problem during the migration with data pump? Or some other problems you may be face after you go to productive, because of this migration?
>> When you say "heterogenous system copy" does not support it, do you mean SAP does not support the converted system or just the process itself ?
I mean that SAP does not support just process itself and the problem you face because of this migration.
Best regards,
Orkun Gedik
Edited by: Orkun Gedik on Jun 29, 2011 11:11 PM -
Changes to existing Reports,Dictionary objects when we migrate DataBase to SAP HANA
Hi Experts,
Can you please let me know the changes that effect to existing ABAP Dictionary objects, Reports, MPP etc... that we build by using ABAP if we migrate our underlying database to SAP HANA from any RDBMS.
Thanks in advance.
Regards,
Sandeep RajanalaDear Sandeep Rajanala,
In general the existing ABAP code(reports, classes, module pool programs, function modules etc) runs on SAP HANA as before and the existing dictionary objects like tables, views, DDIC types and structures continues to exist and work as before after migration.
However if the existing ABAP Code relies on the technical specifics of the old database , ABAP Code changes might be necessary(which is the case for any database migration ).
For example,
Your ABAP code uses a feature that is specific to the old database and not in the SQL standard and therefore not in Open SQL(consumed via Native SQL using EXEC SQL or ADBC interface)
You have ABAP code that relies on unspecified undocumented implementation behaviour of the old database
the above cases may need minor code changes in ABAP during HANA migration inorder to ensure that your ABAP Code runs with functional correctness after migration.
The SAP note 1785057 gives guidelines on migrating the existing ABAP Custom Code for HANA.
Additionally we have several code inspector checks to find the ABAP code that requires changes and you can find details about these check in SAP note 1912445.
In addition you can find an elaborate guide for transitioning custom ABAP code to HANA here which has a dedicated section on required and recommended adaptations during custom code migration.
You can also find the recording of the SAP Teched 2013 hands on session which focuses completely on ABAP Custom Code migration aspects for HANA here
Hope this answers your question and gives you some pointers on how you could prepare your ABAP for migrating to HANA.
Please revert back if you have further questions.
Best Regards
Sundar. -
DMS: Migration of DIR's from one SAP database to another SAP database
Hi Gurus
We have a content server with originals linked to DIR's in a SAP database. We want to migrate the DIR's to another SAP system. The question is can we link the originals to the new DIR's in the new system without having to download and upload the originals in the content server using the original Phios.
Thanks in advance.
regards
barryHI,
You can change the content server connection to the new server but you can not b able to read the data which is already stored in the content server via old server. But you can store the new documents and you can retrieve the same. you have to download and upload the documents which are stored in the content server via old server.
thanks,
Chaitanya. -
Asian Language problem (###) after OS/DB Migration of SAP BW 3.5
Hello,
We have recently migrated our SAP BW 3.5 system form Windows to Linux OS and now we have some issue in the BEX. when we log in with Language EN in to bex and then run any report related to Japan/China (Asian) then the reports is showing #### in place of Asian characters.
It is fine if we log in to Web reporting we have no issues.
Please provide me the solution asap I will give you full points
System: SAP BW 3.5
OS/DB Migration : from windows 32 bit to Linux 64 bit
Problem: In Bex asian character are shown as '###' when log in with Language "EN"Hello Murali,
Thanks for your information....I got much idea and i will allot full points for you.
But the solution which i for is as below
Option 1 for GUI 710)
step1 -> as you said changed the language in system Regional setting to Japanese
step2 -> upgrade GUI to 710
step3 -> Go to GUI Options and check ON the "With Wizards"
step4 -> go to the GUI-> select the BW system on it -> click on change button
step5 -> go to 'code page tab' and then uncheck "Unicode off" and select the language from default to Japanese
Option 2 for GUI 640 or above)
step1 -> as you said changed the language in system Regional setting to Japanese
step2 ->Go to GUI (640) select the BW system on it -> click on change button or properties
step3 -> click Advance button -> Uncheck 'Default code page' and select the language to 'JA' and then OK
Maybe you are looking for
-
Upgrading to 9iAS 9.0.2.1 from OAS 4.0.8.1
Hi, I would like to use OC4J to develop in J2EE but i have some applications that are developed with the pl/sql web toolkit and running with OAS 4.0.8.1. So i have few questions: 1) Can i use easily 9iAS to have both J2EE applications and web toolkit
-
Error while uploading flat file
Hello My flat file(.csv) has 3 columns.But when i am uploading and when i check Master data, it just shows me the first column.Why is it so? When i maintain Master data, do i have to maintan attr, text and hierarchies?In mapping and transfer rules?Wh
-
i'm preparing for scjp5 n using jdk1.4.2.will i've to change my jdk environment to jdk5 or it won't create any problem in exam.
-
Startup screen is huge. cannot enter password. 2x tap will not reset screen size
screen size is huge. cannot enter password. 2x tap on screen will not resize. tried hard reboot, no luck
-
Why do I keep getting "The procedure entry point sqlite3_wal_checkpoint could not be located in the dynamic link library SQLite3.dll" when I start up my computer?