Mixed (Java & ABAP w/different sources) System Copy Failed- NW 7.0 SR3/SP14

Hello SAP Friends! Our NW admin did a dual stack system copy where the ABAP server came from system 1 and the Java server came from system 2. This worked fine for ABAP (duh it was installed first), but the Java system copy was a disaster. the server started but many key services did not.
Why?
Many of the configuration entries were not generated properly. For example, a new, unknown SID was created, and many entries referenced System 1 (the ABAP source, not even the Java source). We were able to find and fix some incorrect config entries, but we still couldn't get all of the services we needed to work.
I think NW is so complicated that such a configuration is probably impossible, but maybe I am wrong.
Does anyone have tips? Or can confirm that this would never work?
The current plan is to install the Java Server from scratch as an add-in, which is less effort than searching through all the config files without any certainty that it will work. Hopefully it will work.
Many thanks in advance.

Hi Matt,
What kind of infos are you looking for? I didn't perform the copy, have just been trying to figure out how to get all of the Java stack's services to start properly. As far as I know, it was done using the standard System Copy wizard. The ABAP server was done as a central instance and then the Java server was copied and installed as a java add-in.
I have asked the admin to post the details to this thread, but it would be helpful if you could mention what types of info and details you are looking for.
Thanks and Best Regards,
John

Similar Messages

Massive copy of BW transformation between different source system

Hi all,
in my BW I have different source systems. I have mapped several objects to one source system.
Now I need to copy all the transformation to other source systems. These source system are different instance of ECCs, there are the same extractor in all the systems.
I can't use the BDLS becouse these move the transformations between the system not copy it.
I try to create a Transport and using the Conversion of Logical System Names but this change only the objects with source sytems dependencies, it don't change the technical name of transformation, and do not create a tranformation to the new system but overwrite the existing one.
Do you know if there are some program or some procedure to copy transformation between sourcesystem in BW?
Thanks in advance
Mario

Hi,
you can do a Retrofit (System copy), Generally, retrofit happens between two different BW systems.
check with your basis team if the retrofit is possible with in the same BW system but for different clients.
Note : System copy will overwrite all the objects.
Regards,
Sudheer

Problems Delta Extractor after Homogeneous Source System Copy

Hi,
We have R/3 system landscape HUD, HUQ, HUP. And we have BW system landscape BWD and BWP.
We connect BWD to HUQ and BWP to HUP.
We made a homogeneous system copy from HUP to HUQ.
We haven´t made any homogeneous system copy from BWP to BWD.
We have applied the next OSS note after source system copy:
325525 Copying and renaming systems in a BW environment
184322 Procedure after DB copy of BW source system
184754 Procedure after BW database copy.
But we have problems in our BW Development (BWD), and we have the next Dump "MESSAGE_TYPE_X" when we can change any delta infopacket, the next text are from Dump:
"MESSAGE_TYPE_X" C
"SAPLRSS1 " or "LRSS1F11 "
"RSM1_CHECK_FOR_DELTAUPD"
I think that the problem is about inconsistencies between RSSDLINIT/SEL tables in BW side and ROOSPRMSC/F tables in R/3 side.
Please could you tell how can i solve this Dump, because i can restrart and initial and delta packet for different Datasource and i can´t do anything.
Thanks in advanced,

Hi,
We are upgrading our R/3 system from 4.7 to Ecc 6.
While copying database tables we are using Clinet Carrier tool which is considering only clinet dependent tables. Hence we are loosing our BW delta queue entries in RSA7 of ugraded system.
We found ROOSPRMSC and ROOSPRMSF tables and copying these 2 tables may resolve the issue and We copied and delta went fine.But we are not sure of only these are the tables to be considered.
Please let us know what are the relevent tables to be considered to make the Delta to work while copying Data base tables from one system to another.
Thanks in Advance
Regards,
R@ngzz

Differentiating Master Data from two different source systems

Friends,
i have used standard InfoObjects that provide master data for two InfoCubes which take data from two different source systems. Now the some of the master data is identical in both the source systems (example: 10 stands for "Industrial" in one whereas 10 stands for "Agricultural" in the other). What do i do so that the system(BW) differentiates the two.
Thanks in advance for all the help.
Mike

I tried to include the 0SOURSYSTEM in the compounding of this InfoObject (for master data) but it gives me a list of other objects that use this InfoObject as a reference characteristic and also says that this InfoObject is used in a ODS and data needs to be emptied in the ODS before activating this InfoObject. Please let me know if there is any way out of it.
Thanks
Mike

Source system RFC fails after transport

Hi all
in our QA system any transport containing a process chain causes the RFC connection to the source ECC6 system to fail after too many logon attempts.
This doesn't happen when we send the same transport to production.
Any ideas?
Regards
Hayley

Hi
thanks, but I had already checked out this note. This refers to the post processing of the transport on BW of client 000 logging onto the BW client to carry out changes, not the RFC connection to the BW ECC source system.
The transport goes through ok, and the process chain can be activated, however at this point we always notice that the ECC source system connection fails with an RFC error, as soon as we get the password reset and changed in SM59 it works ok.

Dialog Instances Java are not up after System Copy NW2004s SR2 ABAP+JAVA

Hello guys,
I have just performed a system copy of our BW system (douple stack NW2004s) wich consists from CI and 2 DIs. First I made an export using SAPINST (Software from SAP_BUSINESS_SUITE_2005_SR2 for sparc solaris), where I choosed in SAP Installation Master->SAp Netweaver 2004s Support Release 2->Additional Software Life-cycle Tasks->System Copy->Oracle->Source System->Central System->Based on ABAP and Java->Database and Central Instance Export. I couldn't find any special task for export java from my dialog instances, so I thought it would be ok like that. Then I used the same software on my target system, choosed ...Additional Software Life-cycle Tasks->System Copy->Oracle->Target System->Central System->Based on ABAP and Java->Central System Installation. In the Dialog input phase of SAPINST I indicated that use db specific tools to copy your database. So I made the database restore+recovery with our DB tools and continued withthe SAPINST and Import.
Afterwards the ABAP part and Java on the central Instance run perfect, but Java Stack is not up by both of Dialog Instances. I have checked the configtool on the server where the CI is running (the DIs are running on different linux servers) and couldn't see any entries for my dialog instances, only the CI was seable there. I tried to start configtool from the application server, but there I could find only the file config.properties in the directory /usr/sap/<SID>/.../j2ee/configtool/, others were simply not there, so it was impossible to start it. Have i forgotten something by EXPORT/IMPORT or I should just use other software for coping a System with douple stack on a CI and DIs? Or should I get configtools for Linux platform ( have searched but not found yet) and try to make the same changes wich i have done by the CI before i started Java on the CI? The most irritated point is that i can't see the dialog instanes in Configtool from the CI.
Any other suggestions and good advices?
Thanks a lot in advance.
Regards, Polina

Hi Manoj, 
I have founded following information in the work directory of one of my dialog instances ( where the java stack doesn't want to start after the copy): /usr/sap/SID/instance/work/ 
1) std_server0.out is in the condition before the system copy, no new data was written there. 
2)dev_disp 
DpJ2eeStart: j2ee state = STARTED 
DpJ2eeLogin: j2ee state = CONNECTED 
Fri Feb 26 12:58:04 2010 
ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212] 
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
Fri Feb 26 12:58:20 2010 
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN 
Fri Feb 26 12:57:20 2010 
***LOG Q0I=> NiIBindSocket: could not delete file '/tmp/.sapstream64984' for hdl 2: unlink (1: Operation not permitted) [nixxi.cpp 3207] 
ERROR => NiIBindSocket: could not delete file '/tmp/.sapstream64984' (hdl 2; errno=0) [nixxi.cpp 3214] 
WARNING => NiIBind: Could not bind local domain socket, only listening on internet socket [nixxi.cpp 3491]
It seems that java is trying to start but something goes wrong and it have to shut down
3)dev_bootstrap 
[Thr 1086335296] JLaunchIExitJava: exit hook is called (rc = 66) 
[Thr 1086335296] ********************************************************************** 
ERROR => The Java VM terminated with a non-zero exit code. 
Please see SAP Note 943602 , section 'J2EE Engine exit codes' 
for additional information and trouble shooting. 
********************************************************************** 
[Thr 1086335296] SigISetIgnoreAction : SIG_IGN for signal 17 
[Thr 1086335296] JLaunchCloseProgram: good bye (exitcode = 66)
4) jvm_bootstrap.out 
... 
Exception occurred: 
com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/dispatcher/ID264509300" does not exist.
.. 
Exception occurred: 
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties! 
 at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476) 
 at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146) 
com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID264509300) in the database! Check database consistency or local Bootstrap properties! 
[Bootstrap module]> Problem occurred while performing synchronization.
j2ee/instance_id = ID2645093 <--- that is the ID of those DI where i took these traces from. So it seems that this ID is not in the database at all. Probably the infromation about the java stack of my DIs was not exported at all...
Thanks in advance. 
Regards, 
Polina

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|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 ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

Unable to open the export file during Import ABAP phase on tar(System copy)

Hi Experts,
We are encountering the following error during Import ABAP phase on target system as we are performing system copy on target system as part of hardware migration(Data center migration).
Scenario:
Sourrce system - BI- ABAP(7.01), Win 2003 x64 unicode,Oracle 10.2.0.4
Target system - BI-ABAP(7.01), Win 2008 R2 unicode, Oracle 11.2.0.1
Actually on source system the data has been generated using migration monitor by using table splitting option and transferred on target system thru ftp option.
During Import process while selecting the Database installation type we have selected the installation method as "Standard systemcopy/Migration(load based)" and not checked the option "Start Migration montior Manually".
As far as my concern this error has nothing to do with this selection.please correct me If i am wrong.
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110428082000
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 23:41:07
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe -dbcodepage 4103 -i test_MIGKEY.cmd -l test_MIGKEY.log -K
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(TFH) ERROR: Unable to open
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA\ARFCSDATA.TOC
(TFH) ERROR: OS error message: Invalid argument
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110428082003
Kindly revert with resolutions and suggestions and any hint to the oss notes as we haven't found anything specific to this error.
Regrds,
Dheeraj

\\10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA\ARFCSDATA.TOC
Please check if above said file located under specified path where SAPINST searvhing for it ie at
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA. if this file dont exist them it may be the case that your export is not proper.
Also check if user from which you have started this SAPINST is able to access
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA.
Thanks..
Mohit

MAXDB Dataabase system Copy - Fail on Phase ABAP Import - Index

Hi All
I wonder if somebody can shed some light on the below; we are doing a system copy of Production BW to QA BW; on ABAP import phase we get an error in the log SAPAPPL1.log (The Database being used is MAXDB)
ERROR : Execute for create index /BI0/E0FC_C06P on /BI0/E0FC_C06 failed (dbrc=99). (SQL error -7055) error message returned by DbSl: SQL-Statement: CREATE INDEX "/BI0/E0FC_C06P" ON "/BI0/E0FC_C06" ( "KEY_0FC_C06P" , "KEY_0FC_C06T" , "KEY_0FC_C06U" , "KEY_0FC_C061" , "KEY_0FC_C062" , "KEY_0FC_C063" , "KEY_0FC_C064" , "KEY_0FC_C065" )
I have checked in the releavant TSK file to see whether I can change the offending line from "err" to "ok", this does not help;
Second thing I tried to do was to drop the index using but keep on getting message that index does not exist
Any help would be apreciated, would I need to re-run the export
Kind Regards
Peter

> I wonder if somebody can shed some light on the below; we are doing a system copy of Production BW to QA BW; on ABAP import phase we get an error in the log SAPAPPL1.log (The Database being used is MAXDB)
>
> ERROR : Execute for create index /BI0/E0FC_C06P on /BI0/E0FC_C06 failed (dbrc=99). (SQL error -7055) error message returned by DbSl: SQL-Statement: CREATE INDEX "/BI0/E0FC_C06P" ON "/BI0/E0FC_C06" ( "KEY_0FC_C06P" , "KEY_0FC_C06T" , "KEY_0FC_C06U" , "KEY_0FC_C061" , "KEY_0FC_C062" , "KEY_0FC_C063" , "KEY_0FC_C064" , "KEY_0FC_C065" )
>
> I have checked in the releavant TSK file to see whether I can change the offending line from "err" to "ok", this does not help;
Did you execute the report SMIGR_CREATE_DDL on the source system and placed the resulting .SQL files in the ABAP/DB/ADA directory before starting the import?
Markus

Java Program in Different Operation Systems

Just one question? can I use a java program (.jar) compiled in windows, in my solaris only by copying the .jar , or do I need to compile it with the solaris SDK?
Thanks in advance for your help and sorry for my ignorance.
Javier

Hi,
It is not required to recompile bcoz the .jar file contains .class files which are independent of Operating system which will be taken care (interpreted) by JVM.
Actually there is different JVM's for different operating systems(Windows 98,Unix,OS/2). No need to have differend java class file for different operating system. Pls, remember Java is platform independent language.
Regards,
S.Prabu

We would like to test old deltas from the source system( copied to new)

Hi Gurus,
The scenario is
They will make a DB copy of the Prod system onto a QA system, the Copied system will have
its system ID changed(SID) to a new one.
There will be deltas available in the RSA7, as this is a copy of the 3 weeks old prod
system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
We would like to test these delta's to BW Dev. why we would like to do the delta's to the
BW dev system is to check whether we can do system copies without clearing the delta's on
the source system.
After the system copy we will do all the activities necessary to reflect the system changes
a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
reflect the changes of the BW Prod system to BW Dev system.
b. Likewise, we will perform all the above activities on the BW dev system by changing the
existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
the new Source system with the new (SID).
c. We will check the source system connection
d. Replicate the datasources on the new source system
e. Activate the Transfer rules for the new source system.
Now for us to do delta's from the new source system to the Bw dev system we need to change
underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
destination to the BW dev system.
What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
and also the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
like to know if this is the case .
Lastly, appreciate if anyone can say if this is possible to do without having to clear the
BW delta queue on the source system.

Hi Ramesh,
Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source) in the BW system on the copied source system
tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
response much appreciated.
Kalyan

SMD + Java Services Missing on the System Copy Installation of SolMan

Hello,
I Installed Solution Manager with system copy option.
Backup a database from source and restore it on the target
I did the Export system image from the source and loaded it on the target system in one of the steps of SAPinst on the target system.
When the process finished I found out that the SMD doesnt show up on the SAP Management Console and can't see any JAVA service running.
It's Missing something ? I'll appreciate yours help.
Regards,
Sergio Maziano

Hi Sergio,
What release of SolMan?
Please check note 1317500 (J2EE Engine does not start after target system installation)
SMD is another SAP System (Solution Manager Diagnostics) which is installed with SAPINST since new versions
Regards.

Import ABAP error in ECC6 system copy targert

Hi Experts,
 I am istalling SAP Ecc 6 in System copy targrt, ABAP import fail in 2/87. I got the error Loading of 'SAPDFACT' import package: ERRORImport Monitor jobs.
My OS Windows 2003 64 bit and Oracle 10.2. Please find the log files belo. Please help me to solve this issue
:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325173244
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -ctf I H:\MVGK IDESBackup-march2010\ABAP\DATA\SAPDFACT.STR C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS\DDLORA.TPL SAPDFACT.TSK ORA -l SAPDFACT.log
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job completed
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325173244
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325173244
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "AT220100325020343 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "KENKI "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "KENKI"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 7)"
(DB) INFO: /BI0/E0RSTT_C01 created #20100325173245
(IMP) INFO: import of /BI0/E0RSTT_C01 completed (0 rows) #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~0 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~01 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~02 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~04 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~05 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~06 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~07 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~08 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~09 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~10 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~11 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~12 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~13 created #20100325173245
DbSl Trace: Error 1408 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1408 occurred when executing SQL stmt (parse error offset=57)
(DB) ERROR: DDL statement failed
(CREATE INDEX "/BI0/E0RSTT_C01~P" ON "/BI0/E0RSTT_C01" ( "KEY_0RSTT_C01P" , "KEY_0RSTT_C01T" , "KEY_0RSTT_C01U" , "KEY_0RSTT_C011" , "KEY_0RSTT_C012" , "KEY_0RSTT_C013" , "KEY_0RSTT_C014" , "KEY_0RSTT_C015" , "KEY_0RSTT_C016" , "KEY_0RSTT_C017" , "KEY_0RSTT_C018" , "KEY_0RSTT_C019" , "KEY_0RSTT_C01A" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325173245
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325174158
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "AT220100325020343 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "KENKI "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "KENKI"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 7)"
(DB) ERROR: DDL statement failed
(DROP INDEX "/BI0/E0RSTT_C01~P")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 1408 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1408 occurred when executing SQL stmt (parse error offset=57)
(DB) ERROR: DDL statement failed
(CREATE INDEX "/BI0/E0RSTT_C01~P" ON "/BI0/E0RSTT_C01" ( "KEY_0RSTT_C01P" , "KEY_0RSTT_C01T" , "KEY_0RSTT_C01U" , "KEY_0RSTT_C011" , "KEY_0RSTT_C012" , "KEY_0RSTT_C013" , "KEY_0RSTT_C014" , "KEY_0RSTT_C015" , "KEY_0RSTT_C016" , "KEY_0RSTT_C017" , "KEY_0RSTT_C018" , "KEY_0RSTT_C019" , "KEY_0RSTT_C01A" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325174158
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325180802
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325180808
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325182246
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325182251
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325183259
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325183304
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100326100904
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100326100910
Thanks in Advance
Jose H

Hi,
You can check the defined enviornment variable using command prompt and System properties.
Open Command Prompt and give "set" command. It will show you active environment variable.
You can also set missing environment variables in system properties.
Start -->Control Panel --> System
On Advanced Tab --> Environment Variables.
After logging to the database if it shows message "Connected to idle instance", that means your database is not started.
Please start the database using below SQL command.
Open Command Prompt
C:\Sqlplus / as sysdba
SQL>startup
Once it says "Database opened", retry SAP installation.
You can also check the database status in SQL prompt using below command:
SQL> select instance_name,status from v$instance;
It must show output like:
INSTANCE_NAME STATUS
<SID> OPEN
Regards.
Rajesh Narkhede

BEx Integration with different source systems

Hi All
I know we can create BEx querys on top of an infoprovider. But instead of storing data into BW and creating reports using BEx tools can we integrate BEx with the other source systems. Like Business Objects tool which can be integrated with different sources. My client wants to know whether we can integrate with BEx for the following
Support data source -- SAP BW
Support data source -- Oracle
Support data source -- MS SQL Server
Support data source -- MS Access
Support data source -- MS Excel
Support data source -- ASCII Text files
Support data source -- XML/XSD
Support data source -- Web Services
Support data source -- SAP R/3
Support data source -- BO Universe
Thanks for letting me know your opinions

Hi,
in theory you can. You will still have a virtual provider on top of your Infosource which will be connected to your datasource; thus you'll have to create the structures; you'll have to load master data as well... so not so nice solution if you think that at this stage, the storage will be the less of your costs....
How are you going to deal with R/3 data?? I mean a great advantage of BW is really when you have an R/3 behind...
I'd rather consolidate all these disparate datasources using the Visual compsoer which can get this data out of nearly an datasource and merge them in one single report; in theory again you could implement all BEx functionalities but at which cost and effort??
Weird that a customer is asking such a question because it is usually the other way around: use SAP BW data in another front-end... by the way SAP is going to acquire BO soon....
hope this helps...
Olivier.

Source system copy

hi all,
my question is
i need to make a copy of source system,i.e make a copy,then what will happen to my delta?
whether i have to initialize this delta again?
regards,
nnpr

If you have copied the BW system and also the source system at the same time, the delta points should be set there. So you don't need re-init again.
If the source system is not copied then you don't have the option except reinit delta.
Procedure: You need to do reinit without data transfer and in order to reinit, you have to delete the existing one, otherwise, it won't let you do it.
Hope it helps..

Mixed (Java & ABAP w/different sources) System Copy Failed- NW 7.0 SR3/SP14

Similar Messages

Maybe you are looking for