Distribution of SAP System Components to Disks

Hi everyone! I'm planning an SAP ERP EHP4 installation and I would like to know which is the best distribution for the files
i.e.
Which unit should I choose to install
*SAP System
*DBMS
*SAP Database
*SAP Database transaction log
Should I install all of them on unit C:?
Should I configure RAID 1 or RAID 5?
Thanks for your help

Martha,
It will depend a bit on what hardware resources are available; but I would also suggest that OS should be on drive C (raid 1) on it's own. I would also suggest that the paging file should be on it's own drive as well (also raid 1).
The SAP program, DB files, translog and tempdb should each be on separate drives if you can. The actual drive letters are not relevant. From experience, the DB files and translog are the two elements that are most in need of their own drives.
Raid 1 is used primarily for protection - you have 2 drives, so if one dies, you can replace without losing the data. However, the data is only on one drive (the other is a mirror so there is no increase in performance)
Raid 5 provides protection, but also provides the extra performance. This is because the work is spread across more than one physical drive.
Regards
Tony

Similar Messages

Distribution of sap systems

hello,
do anyone know the distribution of the sap systems to the different operating systems. is there a diagram, like a cake diagram, on the sap marketplace where you can see the distribution.
thanks
winfried geisselbrecht

hello,
do anyone know the distribution of the sap systems to the different operating systems. is there a diagram, like a cake diagram, on the sap marketplace where you can see the distribution.
thanks
winfried geisselbrecht

DB Copy (MSSQL) between two SAP systems with different level and Components

Hi,
we have a SAP system release mysap 2004 SR1 and for "the upgrade project to SAP ECC 6.0 " we installed a new mysap 2004 in a new hardware (sap03) where we have also solution manager running. The new installed Mysap 2004 SR1 is alos running fine in the new hardware.
Now we would like to do DB copy from the old system (sap02) to the the new system sap03 and then we will do the upgrade to SAP ECC 6.0.
After I compared the two systems I have following questions:
1) there are 4 Software Components which are not in the new system (sap03). This are:
PI
FIN_BLERP
BP_INSTRASS
Is this necesary for the DB copy or we do not need this to be able to do the DB copy?
2) The Software Components Level is not the same. Should we have the same level to do the DB Copy?
Thanks in advance
Best regards
HanseAtik

Hi Juan, hi Clas,
just to be clear and to not stuck on the the way:
The systems are as follow:
1) the source system:
                     - Windows Server 2003,
                     - MSSQL Server 2005 with 32 bit.
                     - Mysap 2004 SR1
2) Target system:
                   - Windows Server 2003
                   - MSSQL Server 2005, with 64 bit.
                   - Mysap 2004 SR1 (with less Support package level and no PI, FIN_Basis, BP_BLERP and BP_INTASS coponents)
I hope this will work. could you post the link the DB Copy guide we are talking about?
By this way we will be sure that we are talking about the same DB Copy. Otherwise any mistake in this step will cost more work and time.
Thanks in advance
Best regards
HanseAtik

Database distribution for several SAP Systems

Hi gurues, we have a very important concern about SAP on Z systems, it is possible/recommended to have on on Z system only one DB engine with several databases that correspond to several SAP Systems running on the machine?
Because we have AIX platform right now and we can not have that kind of database landscape, we only can choose between MCOD or one dataabase engine with one datase in one machine (we can not share db engine).
Hope this question is clear enoguh for you.
Regards
Gustavo

Gustavo,
Sadly yes. You'll have to forgive some of my terminology. I actually work on the Basis team at my company and I am not a DBA. We happen to be running DB2 z/OS and we are using datasharing. For a sandbox ECC system we might have SID SE1 and DB2 sub-systems SE11 and SE12. For another sandbox BI system we might have SID SB1 and DB2 sub-systems SB11 and SB12. Even if datasharing is not used (and hence the 12 member would not exist, SE12 for instance), I would strongly recommend against MCOD and instead suggest using a different DB2 system for each SAP SID.
We have spoken to at least 1 customer that implemented their ECC (ABAP only) and Portal (Java only) SIDs as MCOD in the same DB2 z/OS system. Unfortunately, DB2 z/OS has some somewhat arbitrary limits for things like thread storage which MUST exist under the "2gig bar" (apparently due to some 31bit code still in use). Effectively, this limits the number of threads (and in the SAP world the number of SAP work processes) that a single DB2 member can service. I believe the limit is around 800 threads. Of course, with datasharing you can spread the load to multiple instances (SB11, SB12, SB13, SB14, etc), but then you must also plan for extra resources to be available in a planned failover for maintenance type situation. This particular customer ended up needing to fine-tune some java database threads and ended up needing an extra DB2 instance or two to handle the load during maintenance using planned failover.
Brian

Updating Database table across multiple SAP systems

Dear All,
I am working on a requirement which is described as follows:
The requirement is to keep a database table in sync across 10 different SAP clients (for production, test systems etc.). So when the database table is modified in source SAP system, it has to be replicated across all the clients and table of other SAP systems.
So the queries from my side are:
1. Whether XI should be used here as a middleware or direct RFC calls can do the updation across the SAP systems?
2. If XI is to be used what would be the recommended approach (ABAP Proxy to ABAP Proxy communication?)
Hope you can recommend me the best options to achieve this.
Thanks & Regards,
Pratik

it depends on what tables are involved/ what type of data/what transactions cause the update.
If you know the table names - then database level replication may be an option u2013 many projects do refresh their QA system with production data for a very real test data. If not, a hard disk level mirroring may have to be considered.
There are other technologies like change pointers in conjunction with distribution model can also be considered - which could trigger idocs that can be sent to the other systems using ALE layer or ALE *** PI/XI

SAP System Message: Syntx error or generation error in a screen

dear sap basis gurus,
i am currently having problems signing on to our DEV server. i get this error message:
<SID>: SAP System Message
Syntx error or generation error in a screen.
it won't let me log on.
there were no changes made on the server (i.e., profile parameters) lately. it was working really fine after our support package level upgrade about 5 months ago.
have you encountered this problem before? please help me as there we have two imminent go-lives.
thank you very much in advance.
best regards,
albert

hello nick, ashok,
thank you very much for your responses.
i have already resolved this issue by just freeing up some space from our disks. not one of them was full though.
i hope i would no longer encounter the error message.
again, thank you.
best regards,
albert

SAP won't start after recabeling sap system

Hi, 
 
I have recently recabled my sap system (from wireless to wired) and now my sap instance won't start anymore. The weird thing is that nothing major was changed. When i read the logs from the work directory it seems it cannot load dbsdbslib.dll. I have updated to the latest version of the kernel and maxdb (kernel=7.00 patch 221, maxdb=7.6.06.07) and i made very sure i got the right kernel (NT AMD64). I also checked the environment settings for the <sid>adm user. The weird part is that it seems SAP cannot connect to the database, but the databse starts just fine and r3trans -d also returns no errors. Does anyone have an idea what could be wrong? 
 
Kind regards, 
Bas 
 
 
trc file: "dev_disp", trc level: 2, release: "700" 
 
 
command line arg 0: D:\usr\sap\IDE\DVEBMGS00\exe\disp+work.EXE 
command line arg 1: pf=D:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sap 
 
ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("D:\usr\sap\IDE\SYS\exe\uc\NTAMD64\dbsdbslib.dll") 
Error 126 = "The specified module could not be found." [dlnt.c 255] 
sysno 00 
sid IDE 
systemid 562 (PC with Windows NT) 
relno 7000 
patchlevel 0 
patchno 221 
intno 20050900 
make: multithreaded, Unicode, 64 bit, optimized 
pid 3252 
 
kernel runs with dp version 243000(ext=110000) (@(#) DPLIB-INT-VERSION-243000-UC) 
length of sys_adm_ext is 576 bytes 
SWITCH TRC-HIDE on *** 
***LOG Q00=> DpSapEnvInit, DPStart (00 3252) [dpxxdisp.c 1287] 
ShmProtect( 5, 3 ) 
SigIInit: ok (whoami=1) 
Thread handle for mainthread created 
SigIRegisterRoutine: handler for signal 11 installed (SigISegv) 
Pipe created:
.\pipe\SAP3252 
SigIInit: Create Message Thread 
SigIRegisterExitRoutine: exithandler installed (DpHalt) 
SigIRegisterTerminateRoutine: terminatehandler installed (DpHalt) 
 shared lib "dw_xml.dll" version 221 successfully loaded 
 shared lib "dw_xtc.dll" version 221 successfully loaded 
 shared lib "dw_stl.dll" version 221 successfully loaded 
 shared lib "dw_gui.dll" version 221 successfully loaded 
 shared lib "dw_mdm.dll" version 221 successfully loaded 
dp_loc_queue_max_blk: 40000 
mshost: >sap< 
DpSetCancelStrat: set timeout 0 at level 0 
DpSetCancelStrat: set timeout 5 at level 1 
DpSetCancelStrat: set timeout -1 at level 2 
DpSetCancelStrat: set timeout -1 at level 3 
rdisp/softcancel_sequence : -> 0,5,-1 
softcancel_sequence: >0,5,-1< 
use internal message server connection to port 3900 
msserv: >3900< 
dp_bufreftime: 120 sec 
dp_btctime: 60 sec 
dp_autoabaptime: 300 sec 
dp_autothtime: 60 sec 
dp_autojavatime: 300 sec 
dp_vm_alarm_time: 100 msec 
dp_calldelayed_time: 60 sec 
dp_startup_time: 20 
dp_noptime: 0 sec 
dp_keepalive: 1200 sec 
dp_keepalive_timeout: 60 sec 
dp_ms_keepalive: 60 sec 
dp_ms_keepalive_timeout: 300 sec 
switch off dp-keep-alive for old temus 
dp_gui_auto_logout: 0 sec 
dp_spoolalrm: 60 sec 
dp_softcancel_timeout: 5 sec 
rdisp/wp_restart_interval : 300 sec 
DpISetTrcLog: trc logging active, max size = 20971520 bytes 
dp_rfc_check_active: 1 
dp_rfc_check_all_rfcs: 0 
dp_http_check: 1 
check_master_slave: 0 
NiHsLGetServNo: got service name 'sapdp00' from operating system 
NiIGetServNo: servicename 'sapdp00' = port 0C.80/3200 
NiHsLGetServNo: got service name 'sapgw00' from operating system 
NiIGetServNo: servicename 'sapgw00' = port 0C.E4/3300 
NiIMyHostName: hostname = 'sap' 
NiHsLGetNodeAddr: got hostname 'sap' from operating system 
NiIGetNodeAddr: hostname 'sap' = addr 192.168.2.250 
NiHsLGetHostName: found address 192.168.2.250 in cache 
NiIGetHostName: addr 192.168.2.250 = hostname 'sap' (fq) 
Mon Oct 26 16:14:29 2009 
NiHsLGetNodeAddr: hostname 'www.doesnotexist0190.qqq.nxst' not found by operating system 
WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0190.qqq.nxst) took 12 seconds 
Mon Oct 26 16:14:45 2009 
NiHsLGetHostName: address 1.0.0.1 not found by operating system 
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 16 seconds 
NiHsLGetServNo: got service name 'http' from operating system 
NiIGetServNo: servicename 'http' = port 00.50/0080 
NiHsLGetServName: port 1F.90/8080 not found by operating system 
NiHsLGetServName: port FC.2B/64555 not found by operating system 
NiHsLGetServNo: service name 'sapdp9988' not found by operating system 
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5521] 
SigIRegisterRoutine: handler for signal 16 installed (DpTrcOnOff) 
SigIRegisterRoutine: handler for signal 17 installed (DpTrcOnOff) 
SigIRegisterRoutine: alarm handler installed (DpSigAlrm) 
SigIRegisterRoutine: handler for signal 2 installed (DpSigInt) 
SigIRegisterRoutine: handler for signal 15 installed (DpSigInt) 
SigIRegisterRoutine: handler for signal 3 installed (DpSigQuit) 
MtxInit: 30000 0 0 
DpInitMtx: MtxInit o.k. 
PPID environment not found 
Thread handle for mainthread created 
SigIRegisterRoutine: handler for signal 19 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 18 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 24 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 0 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 21 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 22 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 23 installed (DpSigPrivDisp) 
SigIRegisterRoutine: handler for signal 25 installed (DpSigPrivDisp) 
 
 
trc file: "dev_w0", trc level: 2, release: "700" 
 
* 
ACTIVE TRACE LEVEL 2
ACTIVE TRACE COMPONENTS all, MJ
M
M command line arg 0: D:\usr\sap\IDE\DVEBMGS00\exe\disp+work.EXE
M command line arg 1: pf=D:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sap
M command line arg 2: wp_id=0
M
B create_con (con_name=R/3)
B Loading DB library 'D:\usr\sap\IDE\SYS\exe\uc\NTAMD64\dbsdbslib.dll' ...
M *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("D:\usr\sap\IDE\SYS\exe\uc\NTAMD64\dbsdbslib.dll")
Error 126 = "The specified module could not be found." [dlnt.c 255]
B *** ERROR => Couldn't load library 'D:\usr\sap\IDE\SYS\exe\uc\NTAMD64\dbsdbslib.dll'
[dbcon.c 4905]
M sysno 00
M sid IDE
M systemid 562 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 221
M intno 20050900
M make: multithreaded, Unicode, 64 bit, optimized
M pid 4000
M
M kernel runs with dp version 243000(ext=110000) (@(#) DPLIB-INT-VERSION-243000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4000) [dpxxdisp.c 1349]
M Mon Oct 26 16:14:47 2009
M SigIInit: ok (whoami=2)
M Thread handle for mainthread created
M SigIRegisterRoutine: handler for signal 11 installed (SigISegv)
M Pipe created:
.\pipe\SAP4000
M SigIInit: Create Message Thread
M SigIRegisterExitRoutine: exithandler installed (wp_halt)
M SigIRegisterTerminateRoutine: terminatehandler installed (wp_halt)
M SigIRegisterRoutine: handler for signal 16 installed (DpTrcOnOff)
M SigIRegisterRoutine: handler for signal 17 installed (DpTrcOnOff)
M SigIRegisterRoutine: alarm handler installed (DpSigAlrm)
M SigIRegisterRoutine: handler for signal 2 installed (DpSigInt)
M SigIRegisterRoutine: handler for signal 15 installed (DpSigInt)
M SigIRegisterRoutine: handler for signal 3 installed (DpSigQuit)
I MtxInit: 30000 0 0
M DpInitMtx: MtxInit o.k.
M WaitParent Thread 3252 start
M WaitParent Thread 3252 created
M Thread handle for mainthread created
M SigIRegisterRoutine: handler for signal 19 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 18 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 24 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 0 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 21 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 22 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 23 installed (DpSigPrivDisp)
M SigIRegisterRoutine: handler for signal 25 installed (DpSigPrivDisp)
 
 
trc file: "trans.log" 
 
 
4 ETW000 r3trans version 6.14 (release 700 - 12.06.09 - 15:20:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 21.10.2009 - 15:06:04
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Wed Oct 21 15:06:06 2009 0 0.000000
4 ETW000 [dev trc ,00000] db_con_init called 0 0.000000
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 0 0.000000
4 ETW000 [dev trc ,00000] Loading DB library 'dbsdbslib.dll' ... 0 0.000000
4 ETW000 [dev trc ,00000] DlLoadLib success: LoadLibrary("dbsdbslib.dll"), hdl 0, addr 0000000188C00000
4 ETW000 7580 0.007580
4 ETW000 [dev trc ,00000] using "D:\usr\sap\IDE\SYS\exe\uc\NTAMD64\dbsdbslib.dll" 16 0.007596
4 ETW000 [dev trc ,00000] Library 'dbsdbslib.dll' loaded 19 0.007615
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library dbsdbslib.dll 38 0.007653
4 ETW000 [dev trc ,00000] Version of 'dbsdbslib.dll' is "700.08", patchlevel (0.211) 307 0.007960
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library dbsdbslib.dll 26 0.007986
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library dbsdbslib.dll 24 0.008010
4 ETW000 [dev trc ,00000] } DbSlSdbControl(rc=0) 46 0.008056
4 ETW000 [dev trc ,00000] { DbSlSdbControl(con_hdl=-1,command=39,arg_p=0000000000000000) 21 0.008077
4 ETW000 [dev trc ,00000] } DbSlSdbControl(rc=0) 15 0.008092
4 ETW000 [dev trc ,00000] { DbSlSdbControl(con_hdl=-1,command=10,arg_p=0000000003B4F920) 20 0.008112
4 ETW000 [dev trc ,00000] } DbSlSdbControl(rc=0) 15 0.008127
4 ETW000 [dev trc ,00000] New connection 0 created 17 0.008144
4 ETW000 [dev trc ,00000] 000: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 50 0.008194
4 ETW000 [dev trc ,00000] { DbSlSdbControl(con_hdl=-1,command=10,arg_p=0000000001A01768) 31 0.008225
4 ETW000 [dev trc ,00000] } DbSlSdbControl(rc=0) 17 0.008242
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 13 0.008255
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse: 16 0.008271
4 ETW000 [dev trc ,00000] 000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

Edited by: B. v. d. Lienden on Oct 26, 2009 5:18 PM

<div class=Section1>
Natalia,
 
To answer your questions:
1. Did you create the SAP ticket, where this problem is
reported?
I didn't report it to SAP because it is just an IDES test
system. I can easily do a reinstall, but i would like to know the cause and
solution to this problem.
 
2. Do you have dbsdbslib.dll at this location? What version?
Yes, i have the dbsdbslib.dll at location
D:\usr\sap\IDE\DVEBMGS00\exe and also D:\usr\sap\IDE\SYS\exe\uc\NTAMD64
Version is 7000.221.16.41497 (kernel 7.00 SP 221)
 
your requested output:
 
----

disp+work information
----

 
kernel releaseu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 700
 
kernel make variantu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 700_REL
 
compiled onu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 NT 5.2 3790 Service Pack 2 x86
MS VC++ 14.00
 
compiled foru00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 64 BIT
 
compilation modeu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 UNICODE
 
compile timeu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 Aug 23 2009 23:15:57
 
update level u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A00
 
patch numberu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 221
 
source idu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 0.221
 
 
----

supported environment
----

 
database (SAP, table SVERS)u00A0u00A0 700
u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 
operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
Windows NT 6.0
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\ideadm\Application Data
CLIENTNAME=BSF02
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
COMPUTERNAME=SAP
ComSpec=C:\WINDOWS\system32\cmd.exe
DBMS_TYPE=ada
DIR_LIBRARY=D:\usr\sap\IDE\SYS\exe\uc\NTAMD64
DIR_PROFILE=D:\usr\sap\IDE\SYS\profile
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\ideadm
JAVA_HOME=C:\j2sdk1.4.2_21-x64
LOGONSERVER=
SAP
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\j2sdk1.4.2_21-x64\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
Files\Intel\DMIX;D:\usr\sap\IDE\SYS\exe\uc\NTAMD64
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=EM64T Family 6 Model 15 Stepping 13,
GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0f0d
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
PROMPT=$P$G
SAPEXE=D:\usr\sap\IDE\SYS\exe\uc\NTAMD64
SAPLOCALHOST=sap
SAPSYSTEMNAME=IDE
SESSIONNAME=RDP-Tcp#47
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\WINDOWS\TEMP\2
TMP=C:\WINDOWS\TEMP\2
USERDOMAIN=SAP
USERNAME=ideadm
USERPROFILE=C:\Documents and Settings\ideadm
windir=C:\WINDOWS
 
----

disp+work information
----

 
kernel releaseu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 700
 
kernel make variantu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 700_REL
 
compiled onu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 NT 5.2 3790 Service Pack 2 x86
MS VC++ 14.00
 
compiled foru00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 64 BIT
 
compilation modeu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 UNICODE
 
compile timeu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 Aug 23 2009 23:15:57
 
update levelu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 0
 
patch numberu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 221
 
source idu00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 0.221
 
 
----

supported environment
----

 
database (SAP, table SVERS)u00A0u00A0 700
u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0 
operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
Windows NT 6.0
 
 
</div>

Problem in SAP system after ECC 6.0 installation

Hi SAP Gurus,
I have been installing ECC 6.0 with database as ORACLE on Sun Solaris SPARC 64-bit.
I m currently stuck at the phase 27,when the SAP instance is started.
My SAP system is not coming up.
I have checked all profiles with sappfpar pf=<profile> check and none of them are giving errors.they are giving only warnings.
I am hereby pasting the dev_ms,dev_disp & dev_w0 files:
dev_ms:
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 1] Wed Oct 22 14:28:09 2008
[Thr 1] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 370 (Solaris on SPARCV9 CPU)
relno 7000
patchlevel 0
patchno 110
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 19059
[Thr 1] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 19059) [msxxserv_mt. 1824]
[Thr 1] SigISetDefaultAction : default handling for signal 18
[Thr 1] load acl file = /usr/sap/DBM/SYS/global/ms_acl_info
[Thr 1] MsGetOwnIpAddr: my host addresses are :
[Thr 1] 1 : [10.48.152.173] gmsc2 (HOSTNAME)
[Thr 1] 2 : [127.0.0.1] localhost (LOCALHOST)
[Thr 1] MsHttpInit: full qualified hostname = gmsc2.in.capgemini.com
[Thr 1] HTTP logging is switch off
[Thr 1] set HTTP state to LISTEN
[Thr 1] MsHttpOwnDomain: own domain[1] = in.capgemini.com
[Thr 1] ms/icf_info_server : deleted
[Thr 1] *** I listen to port sapmsDBM (3600) ***
[Thr 1] *** I listen to internal port 3900 (3900) ***
[Thr 1] *** HTTP port 8100 state LISTEN ***
[Thr 1] CUSTOMER KEY: >T1454016479<
[Thr 1] Wed Oct 22 14:28:49 2008
[Thr 1] *** ERROR => MsSClientHandle: no server provides service ENQ (4), requested from gmsc2_DBM_00 [msxxserv_mt. 4669]
[Thr 1] Wed Oct 22 14:39:02 2008
[Thr 1] *** ERROR => MsSCheckConnections: no response from client C1 (127.0.0.1) after 300 secs received [msxxserv_mt. 3158]
[Thr 1] *** ERROR => MsSCheckConnections: disconnect now [127.0.0.1] [msxxserv_mt. 3162]
dev_disp:
trc file: "dev_disp.new", trc level: 1, release: "700"
sysno 00
sid DBM
systemid 370 (Solaris on SPARCV9 CPU)
relno 7000
patchlevel 0
patchno 111
intno 20050900
make: single threaded, Unicode, 64 bit, optimized
pid 19060
Wed Oct 22 14:28:11 2008
kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 19060) [dpxxdisp.c 1239]
 shared lib "dw_xml.so" version 111 successfully loaded
 shared lib "dw_xtc.so" version 111 successfully loaded
 shared lib "dw_stl.so" version 111 successfully loaded
 shared lib "dw_gui.so" version 111 successfully loaded
 shared lib "dw_mdm.so" version 111 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >gmsc2_DBM_00 <
DpShMCreate: sizeof(wp_adm) 19344 (1488)
DpShMCreate: sizeof(tm_adm) 5710008 (28408)
DpShMCreate: sizeof(wp_ca_adm) 31200 (104)
DpShMCreate: sizeof(appc_ca_adm) 10400 (104)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/548056/548064
DpShMCreate: sizeof(comm_adm) 548064 (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (2080)
DpShMCreate: sizeof(wall_adm) (40056/36728/88/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 0xffffffff6e400000, size: 6404896)
DpShMCreate: allocated sys_adm at 0xffffffff6e400000
DpShMCreate: allocated wp_adm at 0xffffffff6e402218
DpShMCreate: allocated tm_adm_list at 0xffffffff6e406da8
DpShMCreate: allocated tm_adm at 0xffffffff6e406e08
DpShMCreate: allocated wp_ca_adm at 0xffffffff6e978ec0
DpShMCreate: allocated appc_ca_adm at 0xffffffff6e9808a0
DpShMCreate: allocated comm_adm at 0xffffffff6e983140
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0xffffffff6ea08e20
DpShMCreate: allocated gw_adm at 0xffffffff6ea08ea0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 0xffffffff6ea08ed0
DpShMCreate: allocated wall_adm at 0xffffffff6ea08ed8
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation std
<ES> Info: use normal pages (no huge table support available)EsStdUnamFileMapInit: ES base = 0x0xfffffffe60000000
EsStdInit: Extended Memory 4092 MB allocated
<ES> 1022 blocks reserved for free list.
ES initialized.
Wed Oct 22 14:28:13 2008
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1629]
***LOG Q0K=> DpMsAttach, mscon ( gmsc2) [dpxxdisp.c 11753]
DpStartStopMsg: send start message (myname is >gmsc2_DBM_00 <)
DpStartStopMsg: start msg sent
Wed Oct 22 14:28:14 2008
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 111
Release check o.K.
Wed Oct 22 14:28:21 2008
ERROR => W0 (pid 19071) died [dpxxdisp.c 14441]
ERROR => W2 (pid 19073) died [dpxxdisp.c 14441]
ERROR => W3 (pid 19074) died [dpxxdisp.c 14441]
ERROR => W4 (pid 19075) died [dpxxdisp.c 14441]
ERROR => W5 (pid 19076) died [dpxxdisp.c 14441]
ERROR => W7 (pid 19078) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xbf --> 0xbb
ERROR => W8 (pid 19079) died [dpxxdisp.c 14441]
ERROR => W1 (pid 19072) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xbb --> 0xba
ERROR => W6 (pid 19077) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xba --> 0xb8
ERROR => W9 (pid 19080) died [dpxxdisp.c 14441]
ERROR => W10 (pid 19082) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W11 (pid 19085) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W12 (pid 19087) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=14
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Oct 22 14:28:31 2008
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Wed Oct 22 08:58:31 2008
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 19071 Ended no 1 0 0
1 DIA 19072 Ended no 1 0 0
2 DIA 19073 Ended no 1 0 0
3 DIA 19074 Ended no 1 0 0
4 DIA 19075 Ended no 1 0 0
5 DIA 19076 Ended no 1 0 0
6 UPD 19077 Ended no 1 0 0
7 ENQ 19078 Ended no 1 0 0
8 BTC 19079 Ended no 1 0 0
9 BTC 19080 Ended no 1 0 0
10 BTC 19082 Ended no 1 0 0
11 SPO 19085 Ended no 1 0 0
12 UP2 19087 Ended no 1 0 0
Dispatcher Queue Statistics Wed Oct 22 08:58:31 2008
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
2
2
2000
4
2
--------++++--
+
DIA
3
3
2000
3
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
this is only a part of dev_disp file.
dev_w0:
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
M sysno 00
M sid DBM
M systemid 370 (Solaris on SPARCV9 CPU)
M relno 7000
M patchlevel 0
M patchno 111
M intno 20050900
M make: single threaded, Unicode, 64 bit, optimized
M pid 19071
M
M
M Wed Oct 22 14:28:12 2008
M kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q01=> ThInit, WPStart (Workproc 0 1 19071) [thxxhead.c 1267]
M ThInit: running on host gmsc2
M calling db_connect ...
C Oracle Client Version: '10.2.0.2.0'
C Client NLS settings: AMERICAN_AMERICA.UTF8
C Logon as OPS$-user to get SAPSR3's password
C Connecting as /@DBM on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 0x106ab1350 0x106ab8e10 0x106ac95a8
C Attaching to DB Server DBM (con_hdl=0,svchp=0x106ac94d8,srvhp=0x106acb828)
C
C Wed Oct 22 14:28:13 2008
C Starting user session (con_hdl=0,svchp=0x106ac94d8,srvhp=0x106acb828,usrhp=0x106ab9628)
C Now '/@DBM' is connected (con_hdl 0, nls_hdl 0).
C Got SAPSR3's password from OPS$-user
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=0x106ac94d8,usrhp=0x106ab9628)
C Now I'm disconnected from ORACLE
C Connecting as SAPSR3/<pwd>@DBM on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 0x106ab1350 0x106ab8e10 0x106ac95a8
C Starting user session (con_hdl=0,svchp=0x106ac94d8,srvhp=0x106acb828,usrhp=0x106ab9628)
C
C Wed Oct 22 14:28:14 2008
C Now 'SAPSR3/<pwd>@DBM' is connected (con_hdl 0, nls_hdl 0).
C Database NLS settings: AMERICAN_AMERICA.UTF8
C DB instance DBM is running on gmsc2 with ORACLE version 10.2.0.2.0 since OCT 21, 2008, 06:23:58
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20081022 142812 gmsc2
M db_connect o.k.
M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,
.sar,.gif
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 0xffffffff7397a000, size: 4400000)
M SHM_ROLL_AREA (addr: 0xfffffffe56000000, size: 134217728)
M SHM_PAGING_AREA (addr: 0xfffffffe50000000, size: 67108864)
M SHM_ROLL_ADM (addr: 0xffffffff73db0000, size: 2672386)
M SHM_PAGING_ADM (addr: 0xffffffff77c00000, size: 656416)
M ThCreateNoBuffer allocated 572152 bytes for 1000 entries at 0xfffffffe48004000
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 12176 bytes (50 server) at 0xffffffff77e00000
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation std
X <ES> Info: use normal pages (no huge table support available)ES initialized.
B
B Wed Oct 22 14:28:15 2008
B db_con_shm_ini: WP_ID = 0, WP_CNT = 13, CON_ID = -1
I
I Wed Oct 22 14:28:17 2008
I *** ERROR => shmget(10019,29999888,2016) (22: Invalid argument) [shmux.c 1556]
B dbtbxbuf: Shm Segment 19: Cannot attach
B ***LOG BBB=> ADM message TBX buffer: function shmcreate0 returns RC = 256 [dbtbxbuf#2 @ 16094] [dbtbxbuf1609 4]
B ***LOG BZL=> internal error in table buffer: table buf init fail [dbtbxbuf#2 @ 1701] [dbtbxbuf1701 ]
B dbtbxbuf: return code (sap_rc): 2, Buffer TBX_GENERIC will not be available
B db_tblinit failed
M *** ERROR => ThCallHooks: event handler db_init for event CREATE_SHM failed [thxxtool3.c 260]
M *** ERROR => ThIPCInit: hook failed [thxxhead.c 2067]
M ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c 1509]
M in_ThErrHandle: 1
M *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c 10283]
M
M Info for wp 0
M
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M req.vm = no VM
M attachedVm = no VM
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 19071) [dpuxtool.c 260]
Quick help would be appreciated since installation it held up.
Regards,
Santosh Bhat

Hi,
I am finding following error in your log:
MsSClientHandle: no server provides service ENQ (4), requested from gmsc2_DBM_00 http://msxxserv_mt. 4669
UPD 0 0 2000 0 0
--------++++--
+
ENQ 0 0 2000 0 0
--------++++--
+
BTC 0 0 2000 0 0
--------++++--
+
SPO 0 0 2000 0 0
--------++++--
+
UP2 0 0 2000 0 0
Please assign no. of work processes to at least 1 for above mentioned type of work process.

FJS-00012 ERROR while executing script in start SAP system

Hi experts,
I am getting error in the Oracle preload actions while installing the SAP 4.7 using the ORacle 9.2.0.1..
FJS-00012 Error when executing script in start SAP system(post processing)
My comp configuration is as follows:
160 gb hard disk
RAM 1GB
OS: win 2003 server enterprise edition
oracle 8.1.7
During the Database Load (post processing) section of the
installation, i get an error and the installation fails.
I am giving all the logs here including the trace log and the
Sapview.log file ans sapinst.
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: START OF LOG: 20070511002459
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#5 $ SAP
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\ESA\SYS\exe\run/R3load.exe -ctf I E:\db3\EXPORT3/DATA/SAPVIEW.STR C:\SAPinst ORACLE KERNEL/DDLORA.TPL C:\SAPinst ORACLE KERNEL/SAPVIEW.TSK ORA -l C:\SAPinst ORACLE KERNEL/SAPVIEW.log -o D
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: job completed
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: END OF LOG: 20070511002500
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: START OF LOG: 20070511070423
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#5 $ SAP
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: version R6.20/V1.2
D:\usr\sap\ESA\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst ORACLE KERNEL/SAPVIEW.cmd -l C:\SAPinst ORACLE KERNEL/SAPVIEW.log -stop_on_error
DbSl Trace: Got ORACLE_HOME=D:\oracle\ora81 from environment
DbSl Trace: Client NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Logon as OPS$-user to get SAPESA's password
DbSl Trace: Connecting as /@ESA on connection 0 ...
DbSl Trace: Attaching to DB Server ESA (con_hdl=0,svchp=002BD418,svrhp=002BD224)
DbSl Trace: Starting user session (con_hdl=0,svchp=002BD418,srvhp=002BD224,usrhp=00304E94)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: ORA-1403 when accessing table SAPUSER
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=002BD418,usrhp=00304E94)
DbSl Trace: Now I'm disconnected from ORACLE
DbSl Trace: Try to connect with default password
DbSl Trace: Connecting as SAPESA/<pwd>@ESA on connection 0 ...
DbSl Trace: Starting user session (con_hdl=0,svchp=002BD418,srvhp=002BD224,usrhp=00304E94)
DbSl Trace: Now I'm connected to ORACLE
DbSl Trace: Database NLS settings: AMERICAN_AMERICA.WE8DEC
DbSl Trace: Database instance esa is running on MALTI with ORACLE version 8.1.7.4.1 since 20070511
(DB) INFO: connected to DB
(DB) INFO: /SAPTRX/A_CONDF4 created
(DB) INFO: /SAPTRX/VDASFEV created
(DB) INFO: /SAPTRX/VDASFPAR created
(DB) INFO: /SAPTRX/VD_AOMIL created
(DB) INFO: /SAPTRX/VD_AOPAC created
(DB) INFO: /SAPTRX/VD_AOPAE created
(DB) INFO: /SAPTRX/VD_AOPAI created
(DB) INFO: /SAPTRX/VD_AOPAR created
(DB) INFO: /SAPTRX/VD_AOTD1 created
(DB) INFO: /SAPTRX/VD_AOTD2 created
(DB) INFO: /SAPTRX/VD_AOTDD created
(DB) INFO: /SAPTRX/VD_AOTYP created
(DB) INFO: /SAPTRX/VD_ASPAR created
(DB) INFO: /SAPTRX/VD_CONDL created
(DB) INFO: /SAPTRX/V_AODD02 created
(DB) INFO: /SAPTRX/V_DD03 created
(DB) INFO: /SAPTRX/V_DD03X created
(DB) INFO: /SDF/SMODICOMP created
(DB) INFO: /SDF/SMODIDEVC created
(DB) INFO: /SDF/UMOD_COMP created
(DB) INFO: ACEPSOIT_UPD created
(DB) INFO: ADJV_TRANS_DIF created
(DB) INFO: AFFWV0 created
(DB) INFO: AFKO_LAUFN created
(DB) INFO: AFSPLIT created
(DB) INFO: AFVCP created
(DB) INFO: ALM_ME_T003O_IS created
(DB) INFO: ALM_ME_T350I created
(DB) INFO: ALM_ME_TQ80_T created
(DB) INFO: ANEKPV created
(DB) INFO: APOUPD created
(DB) INFO: APPL_DEVC created
(DB) INFO: APPL_DIAL created
(DB) INFO: APPL_DOMA created
(DB) INFO: APPL_DTEL created
(DB) INFO: APPL_ENQU created
(DB) INFO: APPL_FUGR created
(DB) INFO: APPL_FUGRG created
(DB) INFO: APPL_FUNC created
(DB) INFO: APPL_INDX created
(DB) INFO: APPL_MCOB created
(DB) INFO: APPL_MENU created
(DB) ERROR: DDL statement failed
(CREATE VIEW "APPL_MODS" ( "NAME" , "TYP" , "MEMBER" , "DEVCLASS" ) AS SELECT T0001."NAME", T0001."TYP", T0001."MEMBER", T0002."DEVCLASS" FROM "MODSAP" T0001, "MODSAPA" T0002 WHERE T0001."NAME" = T0002."NAME" AND T0002."MIGRATED" <> 'X')
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
DbSl Trace: Disconnecting from connection 0 ...
DbSl Trace: Closing user session (con_hdl=0,svchp=002BD418,usrhp=00304E94)
DbSl Trace: Detaching from DB Server (con_hdl=0,svchp=002BD418,srvhp=002BD224)
DbSl Trace: Now I'm disconnected from ORACLE
(DB) INFO: disconnected from DB
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\ESA\SYS\exe\run/R3load.exe: END OF LOG: 20070511070433
SAPINST
INFO 2007-05-10 23:59:05
Processing of host operation t_HostInfo_SHARED succeeded.
INFO 2007-05-10 23:59:16
The 'saploc' share exists at directory 'D:\usr\sap'. Choosing drive D: as SAP System drive.
INFO 2007-05-10 23:59:21
Copying file E:/KERNEL/NT/COMMON/OraVolatileDatabaseParameters.xml to: OraVolatileDatabaseParameters.xml.
INFO 2007-05-10 23:59:21
Creating file C:\SAPinst ORACLE KERNEL\OraVolatileDatabaseParameters.xml.
INFO 2007-05-11 00:01:52
Copying file E:/db1/EXPORT1/DB/ORA/DBSIZE.XML to: DBSIZE.XML.
INFO 2007-05-11 00:01:52
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.XML.
INFO 2007-05-11 00:01:52
Copying file system node E:\db1\EXPORT1/DB/ORA/DBSIZE.XML with type NODE to DBSIZE.XML succeeded.
INFO 2007-05-11 00:01:52
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-05-11 00:01:52
Copying file E:/db1/EXPORT1/DB/DDLORA.TPL to: DDLORA.TPL.
INFO 2007-05-11 00:01:52
Creating file C:\SAPinst ORACLE KERNEL\DDLORA.TPL.
INFO 2007-05-11 00:01:52
Copying file system node E:\db1\EXPORT1/DB/DDLORA.TPL with type NODE to DDLORA.TPL succeeded.
INFO 2007-05-11 00:01:52
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-05-11 00:01:57
Moving file C:/SAPinst ORACLE KERNEL/DDLORA.TPL to: orig_ddl_ora_tmp.tpl.
INFO 2007-05-11 00:01:57
Moving file C:/SAPinst ORACLE KERNEL/changed_ddl_ora_tmp.tpl to: DDLORA.TPL.
INFO 2007-05-11 00:01:57
Removing file C:/SAPinst ORACLE KERNEL/orig_ddl_ora_tmp.tpl.
INFO 2007-05-11 00:03:00
Package table created
PHASE 2007-05-11 00:04:15
SAP R/3 Enterprise 4.70 for Oracle
PHASE 2007-05-11 00:04:15
SAP Web Application Server
PHASE 2007-05-11 00:04:15
Request common parameters of SAP System
PHASE 2007-05-11 00:04:15
Create operating system accounts
INFO 2007-05-11 00:04:15
Copying file C:/SAPinst ORACLE KERNEL/keydb.xml to: C:/SAPinst ORACLE KERNEL/keydb.1.xml.
INFO 2007-05-11 00:04:15
Creating file C:\SAPinst ORACLE KERNEL\keydb.1.xml.
INFO 2007-05-11 00:04:15
Copying file C:/SAPinst ORACLE KERNEL/OraVolatileDatabaseParameters.xml to: C:/SAPinst ORACLE KERNEL/OraVolatileDatabaseParameters.1.xml.
INFO 2007-05-11 00:04:15
Creating file C:\SAPinst ORACLE KERNEL\OraVolatileDatabaseParameters.1.xml.
INFO 2007-05-11 00:04:15
Copying file C:/SAPinst ORACLE KERNEL/DBSIZE.XML to: C:/SAPinst ORACLE KERNEL/DBSIZE.1.XML.
INFO 2007-05-11 00:04:15
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.1.XML.
INFO 2007-05-11 00:04:15
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1004 ACCOUNTNAME=malti\SAP_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-05-11 00:04:15
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1005 ACCOUNTNAME=malti\SAP_ESA_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-05-11 00:04:15
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1006 ACCOUNTNAME=malti\SAP_ESA_GlobalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Global Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-05-11 00:04:15
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1007 ACCOUNTNAME=ORA_ESA_DBA ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Operator Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-05-11 00:04:15
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1008 ACCOUNTNAME=ORA_ESA_OPER ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-05-11 00:04:15
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
INFO 2007-05-11 00:04:18
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1009 ACCOUNTNAME=malti\esaadm ACCOUNTTYPE=USER DESCRIPTION=SAP System Administrator MEMBERSHIP=malti\SAP_ESA_GlobalAdmin,malti\Users,Administrators,ORA_ESA_DBA,ORA_ESA_OPER,malti\SAP_LocalAdmin,malti\SAP_ESA_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-05-11 00:04:18
Changing account ACCOUNTID=S-1-5-21-1488183395-3813774055-1856681103-1010 ACCOUNTNAME=malti\SAPServiceESA ACCOUNTTYPE=USER CONDITION=YES DESCRIPTION=SAP System Service Administrator MEMBERSHIP=malti\SAP_ESA_GlobalAdmin,Administrators,ORA_ESA_DBA,ORA_ESA_OPER,malti\SAP_LocalAdmin,malti\SAP_ESA_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-05-11 00:04:18
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
PHASE 2007-05-11 00:04:18
Request operating system user information
PHASE 2007-05-11 00:04:18
Request operating system user information
PHASE 2007-05-11 00:04:18
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
PHASE 2007-05-11 00:04:19
Request operating system user information
INFO 2007-05-11 00:04:20
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1488183395-3813774055-1856681103-500' on host 'malti'!
INFO 2007-05-11 00:04:20
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1488183395-3813774055-1856681103-500' on host 'malti'!
INFO 2007-05-11 00:04:20
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1488183395-3813774055-1856681103-500' on host 'malti'!
INFO 2007-05-11 00:04:20
Evaluating all 'tNT_RegistryEntries' table rows succeeded.
INFO 2007-05-11 00:04:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-05-11 00:04:22
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata6\esa_16 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata1\esa620_1.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata1\esa620_1 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata2\esa620_2.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata2\esa620_2 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata3\esa620_3.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata3\esa620_3 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata4\esa620_4.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata4\esa620_4 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata4\esa620_5.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata4\esa620_5 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata5\esa620_6.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata5\esa620_6 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata5\esa620_7.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata5\esa620_7 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata6\esa620_8.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata6\esa620_8 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata6\esa620_9.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata6\esa620_9 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata6\esausr_1.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata6\esausr_1 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata2\roll_1.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata2\roll_1 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata3\temp_1.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata3\temp_1 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Creating directory D:\oracle\ESA\sapdata1\system_1.
INFO 2007-05-11 00:05:39
Creating file system node D:\oracle\ESA/sapdata1\system_1 with type DIRECTORY succeeded.
INFO 2007-05-11 00:05:39
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-05-11 00:05:40
Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
INFO 2007-05-11 00:05:40
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-05-11 00:05:41
Creating file D:\oracle\ora81\database\initESA.ora.
INFO 2007-05-11 00:05:42
Creating file D:\oracle\ora81\database\initESA.sap.
INFO 2007-05-11 00:05:43
Copying file E:/KERNEL/NT/COMMON/INSTALL/INITSID.DBA to: D:\oracle\ora81/database/initESA.dba.
INFO 2007-05-11 00:05:43
Creating file D:\oracle\ora81\database\initESA.dba.
INFO 2007-05-11 00:05:44
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:05:45
Moving file D:/oracle/ora81/database/initESA.ora to: orig_init_ora_tmp.txt.
INFO 2007-05-11 00:05:45
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\oracle\ora81\database\initESA.ora.
INFO 2007-05-11 00:05:45
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-05-11 00:05:46
Creating file C:\SAPinst ORACLE KERNEL\oradim.log.
INFO 2007-05-11 00:05:51
See 'D:\oracle\ora81/bin/oradim -new -sid ESA -STARTMODE auto' output in 'C:\SAPinst ORACLE KERNEL\oradim.log'.
INFO 2007-05-11 00:05:51
'D:\oracle\ora81/bin/oradim -new -sid ESA -STARTMODE auto' returned with '0'.
INFO 2007-05-11 00:05:52
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:05:57
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:06:02
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:06:27
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:06:29
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:06:51
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:06:54
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:07:21
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:07:24
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:07:27
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:07:29
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:07:31
Moving file D:/oracle/ora81/database/initESA.ora to: orig_init_ora_tmp.txt.
INFO 2007-05-11 00:07:31
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\oracle\ora81\database\initESA.ora.
INFO 2007-05-11 00:07:31
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-05-11 00:07:32
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:07:34
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:08:09
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:08:12
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:08:48
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:08:50
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:09:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:09:29
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:10:04
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:10:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:10:42
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:10:44
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:11:20
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:11:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:11:57
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:12:00
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:12:35
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:12:37
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:13:13
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:13:15
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:13:51
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:13:53
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:14:29
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:14:31
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:15:09
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:15:11
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:15:48
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:15:50
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:16:26
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:16:28
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:17:04
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:17:07
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:17:43
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:17:45
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:18:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:18:24
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:19:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:19:03
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:19:39
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:19:42
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:20:21
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:20:24
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:21:02
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:21:05
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:21:43
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:21:45
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:22:24
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:22:27
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:23:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:23:08
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:23:47
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:23:50
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:23:54
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:23:56
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:12
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:15
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:41
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:43
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:46
Moving file D:/oracle/ora81/database/initESA.ora to: orig_init_ora_tmp.txt.
INFO 2007-05-11 00:24:46
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\oracle\ora81\database\initESA.ora.
INFO 2007-05-11 00:24:46
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
INFO 2007-05-11 00:24:46
Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
INFO 2007-05-11 00:24:47
See 'D:\oracle\ora81/bin/lsnrctl stat' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
INFO 2007-05-11 00:24:47
'D:\oracle\ora81/bin/lsnrctl stat' returned with '3'.
INFO 2007-05-11 00:24:47
Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
INFO 2007-05-11 00:24:48
See 'D:\oracle\ora81/bin/lsnrctl start' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
INFO 2007-05-11 00:24:48
'D:\oracle\ora81/bin/lsnrctl start' returned with '0'.
INFO 2007-05-11 00:24:49
Copying file E:/KERNEL/NT/COMMON/INSTALL/ORADBUSR.SQL to: ./oradbusr.sql.
INFO 2007-05-11 00:24:49
Creating file C:\SAPinst ORACLE KERNEL\oradbusr.sql.
INFO 2007-05-11 00:24:49
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:52
Changed working directory to C:\SAPinst ORACLE KERNEL.
PHASE 2007-05-11 00:24:54
Database Load
INFO 2007-05-11 00:24:56
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:57
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:57
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:58
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:58
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:24:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:25:00
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:25:00
Task files created
INFO 2007-05-11 00:25:00
Command files created
INFO 2007-05-11 00:25:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:25:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 00:25:01
Changed working directory to C:\SAPinst ORACLE KERNEL.
ERROR 2007-05-11 02:18:03
MSC-01015 Process finished with error(s), check log file C:\SAPinst ORACLE KERNEL/SAPAPPL1.log
INFO 2007-05-11 02:18:03
Changed working directory to C:\SAPinst ORACLE KERNEL.
ERROR 2007-05-11 02:44:07
MSC-01015 Process finished with error(s), check log file C:\SAPinst ORACLE KERNEL/SAPSSEX2.log
INFO 2007-05-11 02:44:07
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 03:55:07
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 04:25:07
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 04:42:08
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 04:47:08
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 04:55:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 04:57:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 04:59:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 05:01:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 05:03:22
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 05:04:23
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 05:05:23
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-05-11 07:04:33
Changed working directory to C:\SAPinst ORACLE KERNEL.
ERROR 2007-05-11 07:04:33
MSC-01015 Process finished with error(s), check log file C:\SAPinst ORACLE KERNEL/SAPVIEW.log
ERROR 2007-05-11 07:04:33
FJS-00012 Error when executing script.
THANKS ALLL IN ADVANCE,
Regards,
Malti

no space left on devices...
==> "MOS-01109 Needed space on mountpoint F:/ is 5.248e07 KB, but got only 4.26433e07 KB."
and others...
-> provide more space and restart
GreetZ, AH

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

File from SAP R/3 installation disk

Hi Friends,
I was installing SAP system when I found that one of the disks have been damaged. I will be really thankful if someone can mail me the file SAPAPP11.001 in the DATA directory of DISK 4. Please mail me the file on my email id in my business card.
Thank you so much for your help.

hi ,
yes you can use FTP_CONNECT.
try the below code.
FTP Using SAP Functions
Here is an example of how to FTP a file from the Application server to a remote server using standard SAP functions.
DATA: BEGIN OF MTAB_DATA OCCURS 0,LINE(132) TYPE C,END OF MTAB_DATA.
DATA: MC_PASSWORD(20) TYPE C,MI_KEY TYPE I VALUE 26101957,MI_PWD_LEN TYPE I,MI_HANDLE TYPE I.
START-OF-SELECTION.
MC_PASSWORD = 'password'.
DESCRIBE FIELD MC_PASSWORD LENGTH MI_PWD_LEN.
*-- FTP_CONNECT requires an encrypted password to work
CALL 'AB_RFC_X_SCRAMBLE_STRING'
 ID 'SOURCE' FIELD MC_PASSWORD ID 'KEY' FIELD MI_KEY
 ID 'SCR' FIELD 'X' ID 'DESTINATION' FIELD MC_PASSWORD
 ID 'DSTLEN' FIELD MI_PWD_LEN.
CALL FUNCTION 'FTP_CONNECT'
 EXPORTING
 USER = 'userid'
 PASSWORD = MC_PASSWORD
 HOST = 'servername'
 RFC_DESTINATION = 'SAPFTP'
 IMPORTING
 HANDLE = MI_HANDLE
 EXCEPTIONS
 NOT_CONNECTED = 1
 OTHERS = 2.
CHECK SY-SUBRC = 0.
CALL FUNCTION 'FTP_COMMAND'
 EXPORTING
 HANDLE = MI_HANDLE
 COMMAND = 'dir'
 TABLES
 DATA = MTAB_DATA
 EXCEPTIONS
 TCPIP_ERROR = 1
 COMMAND_ERROR = 2
 DATA_ERROR = 3
 OTHERS = 4.
IF SY-SUBRC = 0.
LOOP AT MTAB_DATA.
 WRITE: / MTAB_DATA.
ENDLOOP.
ELSE.
do some error checking.
ENDIF.
CALL FUNCTION 'FTP_DISCONNECT'
 EXPORTING
 HANDLE = MI_HANDLE
 EXCEPTIONS
 OTHERS = 1.

Multiple SAP systems in MSCS with Oracle

Hello,
We are going to install a BI instance in a MSCS cluster in which there is already a SAP system installed and clustered.
The SO is Windows 2008 and Oracle 10.2.0.4.
My problem is about the Oracle sw. In previous SAP releases there was a guide called "Installation of Multiple SAP systems in MSCS: Oracle".
For my release Netweaver 7.0. EHP1 SR1, there is no specific guide. All the references are the installation guide and part related to MSCS installation and a white paper about "new configuration of multiple SAP systems with Windows 2008 Failover Clustering".
In all that documents I haven't found what to do with the database. In the beginning of the installation documents says that Multiple Oracle_home for different database instances are not supported in an MSCS configuration. But in the pages related to the MSCS installation says "if required, set up multiple Oracle Homes".
So, what's the option? Multiple Oracle_homes or MCOD? Be in mind that I already have a SAP system in this cluster, so I already have an Oracle home c:\oracle\<SID>\102
Have you work in this scenario?
Thanks and best regards,
Ana.

Hi,
Officially SAP does not support Multiple SAP Systems in One MCSC Cluster. If such installation & configuration has been done by SAP Global Technology Partner then and then only SAP provide support.
what's the option? Multiple Oracle_homes or MCOD?
GO for multiple oracle_home , in which the same drive letter for oracle_home should be used on local disks in both MCSC cluster nodes. And the same oracle_home should be junctioned to the shared location on shared space.
The Chapter 7 High Availability with Microsoft Cluster Service of [Inst. Guide SAP NetWeaver 7.0 incl. EHP1 SR1|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000659894&_OBJECT=011000358700000353072009E] contains all the required information with detail. Refer it.
Regards,
Bhavik G. Shroff

Multiple SAP Systems In One MSCS Cluster

We have installed a NW 7.0 EHP abap stack in a MSCS Cluster with 2 nodes.
This was installed as a standard Cluster Install.
We have now higlighted a requirement to install a 2nd (Java ) instance in this Cluster Group.
The NW 7.0 EHP1 documentation and Note 1321854 shows that multiple SAP systems in one MSCS cluster is supported.
The documentation, however, is not clear if the 2nd instance can be installed when the 1st instance was installed without the preperations for Multiple Systems.
There are no further documentation or guidelines to help.
Has anyone come across this situation or managed to install 2 SAP instances in one Cluster Group based on Windows 2003, SQL Server 2005.
Regards

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

SAP Applications and Business Suite Installed on an SAP System

Hi to all SAP gurus,
I have a couple of questions:-
1) Is there any way to find out about the SAP applications installed on an SAP system? I used CCMS to find out about the Installed SAP
components. But does this list give the correct information? Also, can we find out which are the major and minor components from this list?
2) Can there be more than one business suite (CRM, SRM, SCM etc.) installed on a single SAP system? Or is it always the case that a single SAP system can have only one business suite installed on it so that it can either be a CRM system, SRM system or something else.
3) Is there any way (Any database table or RFC function) I can find out out about the business suite installed on a particular SAP system? One thing I saw in SAP GUI is that the title bar reads "Customer Relationship Management" if it is a CRM system. Is this a fool-proof way to find out whether an SAP system is a CRM system, SRM system etc. If yes, will this information be stored in a database table or is there any RFC function so that I can get this data programatically?
Please bear with my BIG questions. I would be grateful if any of you guys can help me on these questions. Please let me know if I have to provide clarity on any of my queries. Thanks in advance

Hi Mike,
Thanks a lot for your suggestions.
I did some research towards this as suggested by you.
1) I tried out SPAM. But this is giving more or less the same information that I am already getting using the database table "CVERS" or the RFC function module "DELIVERY_GET_INSTALLED_COMPS". Both of these give information about the installed SAP components. But these modules don't give the precise information as to which particular business suite application is installed on the SAP system.
2) I checked out the site -http://service.sap.com/instguides but couldn't get much help on here. I couldn't exactly get any information about the combinations of the business suite applications
that can be installed on an SAP system.
However, I was curious about one thing which I observed on my SAP system. The SAP GUI title bar reads "SAP Easy Access Customer Relationship Management". Can we be come to a conclusion that this is an SAP system with CRM installed on it?
Also, the installed components for this system lists "BBPCRM" as one of the application component. Can we say that this is a CRM system by looking at this? If yes, are you aware of such a similar component for the other applications SRM, PLM, SCM which tells us about the business suite application installed on the SAP system?
3) I did some rigorous search for RFC function modules that give the information I need. I came across 2 RFC function modules which give information on the SAP applications installed on an SAP system:-
a) TERM_GET_TOPLEVEL_COMPONENTS
b) SKWF_APPLS_GET
The function module "TERM_GET_TOPLEVEL_COMPONENTS" is showing a list of business suite applications installed but I am not sure if it's giving the correct information because it shows both CRM and SRM in the applications list for an SAP system.
I'd be most interested for your further suggestions regarding this.
Thanks again
- John

Data Migration from IDES to Vanilla open source SAP System

Can any one help me as to what are the SD tables that should be migrated between 2 SAP systems in order to operationalize a complete Sales Cycle . This information has to be provided to the Basis team . Where i should i start from and what should be my approach ?

Tables in Sales and Distribution (SD) :
Document Flow
VBFA - Document flow (alg.)
VTFA - Flow shipping documents
Sales order :
VBAK - Header data
VBAP - Item data
VBPA - Partners in sales order
VBKD - Sales district data
VBEP - Data related to line items, delivery lines
Billing document :
VBRK - header data
VBRP - Item data
Shipping :
VTTK - Shipment header
VTTP - Shipment item
VTTS - Stage in transport
VTSP - Stage in transport per shipment item
VTPA - Shipment partners
VEKP - Handling Unit - Header Table
VEPO - Packing: Handling Unit Item (Contents)
Delivery :
LIKP - Delivery header
LIPS - Delivery item
Pricing :
KONH - Conditions header
KONP - Conditions items
KONV - Procedure ( billing doc or sales order)
KOND
Contracts :
VEDA - Contract data
Regards,
Rajesh Banka

Distribution of SAP System Components to Disks

Similar Messages

Maybe you are looking for