CJS-30023 Process call 'D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\brconnect.exe -u
hi all, i got error while installing the ecc 6.0. can u pls suggest me how to solve this problem. i am using RAM : 4 GB DDR 2 processer : dual core 2.5 HDD : 500 GB os - windos server 2003 java -j2sdk1.4.2_17-x64 oracle 10.2
pls help me any one shijo k prakash
BRCONNECT.log
BR0801I BRCONNECT 7.00 (32) BR0805I Start of BRCONNECT processing: cebgvdpf.sta 2009-08-19 10.27.35 BR0484I BRCONNECT log file: D:\oracle\C11\sapcheck\cebgvdpf.sta BR0613E Database instance C11 is shut down BR0806I End of BRCONNECT processing: cebgvdpf.sta 2009-08-19 10.27.35 BR0280I BRCONNECT time stamp: 2009-08-19 10.27.35 BR0804I BRCONNECT terminated with errors
It seems your database crashed/got shut down.
Check the Oracle alert<SID>.log
Markus
Similar Messages
-
PDF files are stored to /usr/sap/ SID SYS/global
True or False --> When a PDF file is generated from within SAP the spool file is stored in /usr/sap/<SID>SYS/global
After a recent upgrade to ECC 6 I'm noticing that a large number of SPOOL* files are in the global directory. Each spool file has 3 components a SPOOL.cfg, SPOOL.xfd and a SPOOL*.ps file .When I examine the spool number using SP01 I see that these jobs all have an output type of PDF. Only files of type PDF appear in the global directory. It does not matter which output device is used. No output device in my system is defined to write to the global directory. Everything is set up to store files to the database.
My assumption is that the generation of a PDF format requires a temporary storage area to convert the data from the "Device Type" setting for the printer (such as Postscript or HPGL) to the PDF format and that the /usr/sap/<SID>SYS/global directory is used for this purpose.
Is there a parameter setting that allows me to modifiy this "conversion" location?Assumptions:
---> You are running on Unix - I don't have instructions for Windows, but they would be analogous
---> Your System ID is TX1
---> 2Gb is big enough to hold your Adobe files
1.) Create a 2Gb file system named /AdobeFiles
2.) Create the required directories under this new file system
- For example: /AdobeFiles/300ADSP
3.) Verify that the user <sid>adm can write to the directory created in step 2
4.) Apply SAP note 1327372
5.) Rename the filesystems that SAP note 1327372 creates
- For example: mv /usr/sap/TX1/SYS/global/300ADSP /usr/sap/TX1/SYS/global/300ADSP-ORG
6.) Create a symbolic link for the required directory to the directory created in step 2
- For example: ln -s /AdobeFiles/300ADSP /usr/sap/TX1/SYS/global/300ADSP
7.) Test your link
cd /usr/sap/TX1/SYS/global/300ADSP
touch TestFile
cd /AdobeFiles/300ADSP/TestFile
Your file should have been created in /AdobeFiles/300ADSP -
/usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
Hi Experts,
We have made a system copy from Production to Quality and it has been done successfully. Now we are able to open the database manually. But when we are trying to start SAP it is not connecting the database base and it is giving error which is given below :
/home/qasadm/startdb.log
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 4764729344 bytes
Fixed Size 2035312 bytes
Variable Size 2432700816 bytes
Database Buffers 2315255808 bytes
Redo Buffers 14737408 bytes
Database mounted.
Database opened.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning and Data Mining options
Mon Apr 12 10:45:40 IST 2010
Connect to the database to verify, that the database is now open
R3trans check finished with return code: 12
ERROR: Startup of database failed
Notify Database Administrator.
/usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
^C
root@bsltest # tail -f /home/qasadm/startdb.log
Connect to the database to check the database state:
R3trans: connect check finished with return code: 12
Database not available
Mon Apr 12 10:55:53 IST 2010
Shutdown database
First trying to shutdown the database - May be,
the database is in the nomount or mount state
Mon Apr 12 10:56:22 IST 2010
starting database
SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 12 10:56:22 2010
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 4764729344 bytes
Fixed Size 2035312 bytes
Variable Size 2432700816 bytes
Database Buffers 2315255808 bytes
Redo Buffers 14737408 bytes
Database mounted.
Database opened.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning and Data Mining options
Mon Apr 12 10:56:42 IST 2010
Connect to the database to verify, that the database is now open
R3trans check finished with return code: 12
ERROR: Startup of database failed
Notify Database Administrator.
/usr/sap/QAS/SYS/exe/run/startdb: Terminating with error code 12
Kindly see the logs and request you to kindly help us how it will resolve this issue.
Regards,
JitendraWe have made a system copy from Production to Quality
After client copy sap schema had been changed thats why its not connecting.
fyi: Client copy and system copy both are different
schema had been changed thats why its not connecting
This is one of the post installation step after doing a system copy(reffer the ssytem copy guide)
Problem has resolved
Great, suggest you to close this thread
Regards,
Nick Loy -
Error 2 for write/read access to a file. File = /usr/sap/SID/SYS/global/999
hi
when i am checking update statistics in db13 it is not creating any log information, and more over it is creating error in sm21 like
Error 2 for write/read access to a file. File = /usr/sap/<SID>/SYS/global/999JOBLG/0001X06000603X23459.
can any one help me.
regards
subhani.Duplicate post
Read and Follow the Forum Rules -
ADS: Can't find /usr/sap/ SAPSID /SYS/global/AdobeDocumentServices
Hello experts,
I try to run Adobe Document Service on NetWeaver CE 7.1 (only a java Stack), but I can't find the directory /usr/sap/<SAPSID>/SYS/global/AdobeDocumentServices/ .. I think, ADS wasn't install during system installation Can anybody help me? It's not explained in the manual https://cw.sdn.sap.com/cw/docs/DOC-46489 ..
Thanks and best regards,
MaxHi,
Looks like ADS usage type was not selected during installation.
In order to ensure if ADS usage type check box was checked or not during installation, goto the SAPINST log files that were written during installation. By default this is written in D:\ drive unless and until specified otherwise.
Search for summary.html in this SAPINST log folder. This html file will clearly explain which usage type was selected during installation.
In case you need ADS, you can run SAPINST again and this time select "Install Additional Usage type" option in the first screen.
Rgds,
Soujanya -
I am installing ECC 6 on Win 2003 Oracle 10G. I am getting following error message during installation.
ERROR 2008-01-07 13:21:35
CJS-30023 Process call 'F:\usr\sap\IDS\SYS\exe\uc\NTI386\brconnect.exe -u / -c -o summary -f stats -o SAPSR3 -p 2' exits with error code 5. For details see log file(s) brconnect.log.
ERROR 2008-01-07 13:21:35
FCO-00011 The step createOracleStatistics with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_ORA|ind|ind|ind|ind|0|0|NW_ORA_Statistics_Create|ind|ind|ind|ind|0|0|createOracleStatistics was executed with status ERROR .
BR0280I BRCONNECT thread 2: time stamp: 2008-01-07 13.21.34
BR0850I 142529 of 142529 objects processed - 237.548 of 237.548 units done
BR0204I Percentage done: 100.00%, estimated end time: 13:21
BR0001I **************************************************
BR0280I BRCONNECT time stamp: 2008-01-07 13.21.34
BR0848I Thread 2 finished with return code 0
BR0280I BRCONNECT time stamp: 2008-01-07 13.21.34
BR0879I Statistics checked for 70290 tables
BR0878I Number of tables selected to collect statistics after check: 12
BR0880I Statistics collected for 72239/70290 tables/indexes
BR0280I BRCONNECT time stamp: 2008-01-07 13.21.35
BR0301E SQL error -1017 at location db_connect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance IDS failed
BR0806I End of BRCONNECT processing: cfflyhxm.sta 2008-01-07 13.21.34
BR0280I BRCONNECT time stamp: 2008-01-07 13.21.35
BR0804I BRCONNECT terminated with errorsHi Prinesh,
It could be your database is probably not running. Check if the instance is up.
Cheers
Deepanshu -
Sap Ecc 6.0 Installation error in Import Java dump e
Hi Friends,
I got error in Phase 20 of 45:-
ERROR 2015-08-06 17:01:26
CJS-30049 Execution of JLoad tool 'E:\j2sdk1.4.2_12\bin\java.exe -classpath "E:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/lib/iaik_jce.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/jload.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/antlr.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/exception.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/jddi.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/logging.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/offlineconfiguration.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/opensqlsta.jar;E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar;H:\usr\sap\ECC\SYS\exe\uc\NTI386\ojdbc14.jar" -sec ECC,jdbc/pool/ECC,
ecc6/sapmnt/ECC/SYS/global/security/data/SecStore.properties,
ecc6/sapmnt/ECC/SYS/global/security/data/SecStore.key -dataDir E:/sap_kol/javacomponent\JAVA_EXPORT\JDMP -job "E:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\IMPORT.XML" -log jload.log' aborts with return code 1.<br>SOLUTION: Check 'jload.log' and 'E:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/jload.java.log' for more information.
ERROR 2015-08-06 17:01:26
FCO-00011 The step importJavaDump with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Jload|ind|ind|ind|ind|9|0|importJavaDump was executed with status ERROR .
INFO 2015-08-06 17:16:48
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Jload|ind|ind|ind|ind|9|0|importJavaDump".
Kindly help me!!
AnuskaHi Markus, Debashis , Uday and Friends,
I am currently Watching Thread.
Plz Help Me.
Regards,
Anuska -
Prob in installation in SAP ECC
Hi,
I am getting a prob while installing SAP ECC 6.0 .. here is the prob...
WARNING 2008-12-05 17:30:57
Execution of the command "D:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs F:\SAP\export1\EXP1;F:\SAP\export2\EXP2;F:\SAP\export3\EXP3;F:\SAP\export4\EXP4;F:\SAP\export5\EXP5;F:\SAP\export6\EXP6;F:\SAP\export6\EXP7;F:\SAP\export6\EXP8;F:\SAP\export6\EXP9;F:\SAP\export6\EXP10;F:\SAP\export6\EXP11 -installDir D:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS -orderBy "" -r3loadExe D:\usr\sap\ECC\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_12"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)Import Monitor jobs: running 1, waiting 2, completed 16, failed 0, total 19.Import Monitor jobs: running 2, waiting 1, completed 16, failed 0, total 19.Loading of 'SAPAPPL2' import package: ERRORImport Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.Loading of 'SAPSSEXC' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 16, failed 2, total 19.
ERROR 2008-12-05 17:30:57
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2008-12-05 17:30:57
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
plz.. let me know what is the exact issue .. ASAP..
Thanks in advance...
Raghunath.SERROR 2008-12-05 17:30:57
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
plz.. let me know what is the exact issue .. ASAP..
No offense - but did you acutally read what´s written?
Markus -
SAP ECC error:'Migration Monitor' exits with error code 103.
Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha dasHello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish. -
SAP ECC 5.0 after installation does not start.
I have installated ECC 5.0 - ABAP Stack in my PC which has 1 GB of RAM and enough hard disk resource. when i start SAP system from MMC it starts and then shuts down after some time. all my work process die one by one.
i have attached the dev_disp file content with this. please advise what could be the problem and how to solve it? Its an emergency, please help..
dev_disp trace file
trc file: "dev_disp", trc level: 1, release: "640"
Thu Apr 12 13:25:23 2007
kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)
length of sys_adm_ext is 312 bytes
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 43
intno 20020600
make: multithreaded, ASCII
pid 1060
***LOG Q00=> DpSapEnvInit, DPStart (09 1060) [dpxxdisp.c 1100]
shared lib "dw_xml.dll" version 43 successfully loaded
Thu Apr 12 13:25:24 2007
shared lib "dw_xtc.dll" version 43 successfully loaded
shared lib "dw_stl.dll" version 43 successfully loaded
shared lib "dw_gui.dll" version 43 successfully loaded
Thu Apr 12 13:25:28 2007
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3886]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: JAVA is not active
DpShMCreate: sizeof(wp_adm) 6624 (828)
DpShMCreate: sizeof(tm_adm) 2219848 (11044)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpShMCreate: sizeof(comm_adm) 192000 (384)
DpShMCreate: sizeof(vmc_adm) 0 (320)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY (addr: 03970040, size: 2505416)
DpShMCreate: allocated sys_adm at 03970040
DpShMCreate: allocated wp_adm at 039717A8
DpShMCreate: allocated tm_adm_list at 03973188
DpShMCreate: allocated tm_adm at 039731B0
DpShMCreate: allocated wp_ca_adm at 03B910F8
DpShMCreate: allocated appc_ca_adm at 03B95748
DpShMCreate: allocated comm_adm_list at 03B96EB8
DpShMCreate: allocated comm_adm at 03B96ED0
DpShMCreate: allocated vmc_adm_list at 03BC5CD0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 03BC5CF8
DpShMCreate: allocated wall_adm at 03BC5D00
MBUF state OFF
Thu Apr 12 13:25:29 2007
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
Thu Apr 12 13:25:30 2007
***LOG Q0K=> DpMsAttach, mscon ( vyasa) [dpxxdisp.c 9736]
Thu Apr 12 13:25:31 2007
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
Thu Apr 12 13:25:32 2007
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 43
Release check o.K.
Thu Apr 12 13:26:10 2007
ERROR => W0 (pid 2052) died [dpxxdisp.c 12187]
ERROR => W1 (pid 2060) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W2 (pid 2068) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => W3 (pid 2076) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => W4 (pid 2084) died [dpxxdisp.c 12187]
ERROR => W5 (pid 2092) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W6 (pid 2100) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W7 (pid 2108) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
killing W0-2052 (SIGUSR2)
ERROR => DpWpKill(2052, SIGUSR2) failed [dpxxtool.c 2468]
killing W1-2060 (SIGUSR2)
ERROR => DpWpKill(2060, SIGUSR2) failed [dpxxtool.c 2468]
killing W2-2068 (SIGUSR2)
ERROR => DpWpKill(2068, SIGUSR2) failed [dpxxtool.c 2468]
killing W3-2076 (SIGUSR2)
ERROR => DpWpKill(2076, SIGUSR2) failed [dpxxtool.c 2468]
killing W4-2084 (SIGUSR2)
ERROR => DpWpKill(2084, SIGUSR2) failed [dpxxtool.c 2468]
killing W5-2092 (SIGUSR2)
ERROR => DpWpKill(2092, SIGUSR2) failed [dpxxtool.c 2468]
killing W6-2100 (SIGUSR2)
ERROR => DpWpKill(2100, SIGUSR2) failed [dpxxtool.c 2468]
killing W7-2108 (SIGUSR2)
ERROR => DpWpKill(2108, SIGUSR2) failed [dpxxtool.c 2468]
NiWait: sleep (10000 msecs) ...
NiISelect: timeout 10000 ms
NiISelect: maximum fd=1661
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 12 13:26:20 2007
NiISelect: TIMEOUT occured (10000 ms)
dump system status
Workprocess Table (long) Thu Apr 12 07:56:20 2007
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 2052 Ended no 1 0 0
1 DIA 2060 Ended no 1 0 0
2 UPD 2068 Ended no 1 0 0
3 ENQ 2076 Ended no 1 0 0
4 BTC 2084 Ended no 1 0 0
5 BTC 2092 Ended no 1 0 0
6 SPO 2100 Ended no 1 0 0
7 UP2 2108 Ended no 1 0 0
Dispatcher Queue Statistics Thu Apr 12 07:56:20 2007
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
3
2000
10
10
--------++++--
+
DIA
5
5
2000
5
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
--------++++--
+
max_rq_id 13
wake_evt_udp_now 0
wake events total 9, udp 8 ( 88%), shm 1 ( 11%)
since last update total 9, udp 8 ( 88%), shm 1 ( 11%)
Dump of tm_adm structure: Thu Apr 12 07:56:20 2007
=========================
Term uid man user term lastop mod wp ta a/i (modes)
Workprocess Comm. Area Blocks Thu Apr 12 07:56:20 2007
=============================
Slots: 300, Used: 1, Max: 0
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
NiWait: sleep (5000 msecs) ...
NiISelect: timeout 5000 ms
NiISelect: maximum fd=1661
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 12 13:26:25 2007
NiISelect: TIMEOUT occured (5000 ms)
Shutdown server ...
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes...
Stop gateway
killing process (2028) (SOFT_KILL)
Stop icman
killing process (2032) (SOFT_KILL)
Terminate gui connections
[DpProcDied] Process lives (PID:2028 HANDLE:1632)
waiting for termination of gateway
NiWait: sleep (1000 msecs) ...
NiISelect: timeout 1000 ms
NiISelect: maximum fd=1661
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 12 13:26:26 2007
NiISelect: TIMEOUT occured (1000 ms)
[DpProcDied] Process died (PID:2028 HANDLE:1632)
[DpProcDied] Process died (PID:2032 HANDLE:1624)
DpHalt: cancel all lcom connections
MPI CancelAll 2 -> 0
MPI DeleteAll 2 -> 0
NiIMyHostName: hostname = 'vyasa'
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 163 bytes
NiBufSend starting
NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name -, type 4, key -
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 9962]
NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiSelClear: removed hdl 3 from selectset
MBUF state OFF
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/8
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 19)
MBUF component DOWN
NiBufClose: clear extensions for hdl 3
NiBufSetStat: bufstat of hdl 3 changed from OK to OFF
NiICloseHandle: shutdown and close hdl 3 / socket 1640
MsIDetach: detach MS-system
EsCleanup ....
***LOG Q05=> DpHalt, DPStop ( 1060) [dpxxdisp.c 8495]
Good Bye .....
and .........
trc file: "dev_disp", trc level: 1, release: "640"
Thu Apr 12 23:42:24 2007
kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)
length of sys_adm_ext is 312 bytes
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 43
intno 20020600
make: multithreaded, ASCII
pid 1544
Thu Apr 12 23:42:25 2007
***LOG Q00=> DpSapEnvInit, DPStart (09 1544) [dpxxdisp.c 1100]
shared lib "dw_xml.dll" version 43 successfully loaded
shared lib "dw_xtc.dll" version 43 successfully loaded
shared lib "dw_stl.dll" version 43 successfully loaded
shared lib "dw_gui.dll" version 43 successfully loaded
Thu Apr 12 23:42:29 2007
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3886]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: JAVA is not active
DpShMCreate: sizeof(wp_adm) 6624 (828)
DpShMCreate: sizeof(tm_adm) 2219848 (11044)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpShMCreate: sizeof(comm_adm) 192000 (384)
DpShMCreate: sizeof(vmc_adm) 0 (320)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY (addr: 03970040, size: 2505416)
DpShMCreate: allocated sys_adm at 03970040
DpShMCreate: allocated wp_adm at 039717A8
DpShMCreate: allocated tm_adm_list at 03973188
DpShMCreate: allocated tm_adm at 039731B0
DpShMCreate: allocated wp_ca_adm at 03B910F8
DpShMCreate: allocated appc_ca_adm at 03B95748
DpShMCreate: allocated comm_adm_list at 03B96EB8
DpShMCreate: allocated comm_adm at 03B96ED0
DpShMCreate: allocated vmc_adm_list at 03BC5CD0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 03BC5CF8
DpShMCreate: allocated wall_adm at 03BC5D00
Thu Apr 12 23:42:30 2007
MBUF state OFF
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
Thu Apr 12 23:42:31 2007
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( vyasa) [dpxxdisp.c 9736]
Thu Apr 12 23:42:33 2007
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
Thu Apr 12 23:42:34 2007
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 43
Release check o.K.
Thu Apr 12 23:43:12 2007
ERROR => W0 (pid 1596) died [dpxxdisp.c 12187]
ERROR => W1 (pid 1020) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W2 (pid 1820) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => W3 (pid 1824) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => W4 (pid 1720) died [dpxxdisp.c 12187]
ERROR => W5 (pid 548) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W6 (pid 1856) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W7 (pid 1904) died [dpxxdisp.c 12187]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
killing W0-1596 (SIGUSR2)
ERROR => DpWpKill(1596, SIGUSR2) failed [dpxxtool.c 2468]
killing W1-1020 (SIGUSR2)
ERROR => DpWpKill(1020, SIGUSR2) failed [dpxxtool.c 2468]
killing W2-1820 (SIGUSR2)
ERROR => DpWpKill(1820, SIGUSR2) failed [dpxxtool.c 2468]
killing W3-1824 (SIGUSR2)
ERROR => DpWpKill(1824, SIGUSR2) failed [dpxxtool.c 2468]
killing W4-1720 (SIGUSR2)
ERROR => DpWpKill(1720, SIGUSR2) failed [dpxxtool.c 2468]
killing W5-548 (SIGUSR2)
ERROR => DpWpKill(548, SIGUSR2) failed [dpxxtool.c 2468]
killing W6-1856 (SIGUSR2)
ERROR => DpWpKill(1856, SIGUSR2) failed [dpxxtool.c 2468]
killing W7-1904 (SIGUSR2)
ERROR => DpWpKill(1904, SIGUSR2) failed [dpxxtool.c 2468]
NiWait: sleep (10000 msecs) ...
NiISelect: timeout 10000 ms
NiISelect: maximum fd=1661
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 12 23:43:22 2007
NiISelect: TIMEOUT occured (10000 ms)
dump system status
Workprocess Table (long) Thu Apr 12 18:13:22 2007
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 1596 Ended no 1 0 0
1 DIA 1020 Ended no 1 0 0
2 UPD 1820 Ended no 1 0 0
3 ENQ 1824 Ended no 1 0 0
4 BTC 1720 Ended no 1 0 0
5 BTC 548 Ended no 1 0 0
6 SPO 1856 Ended no 1 0 0
7 UP2 1904 Ended no 1 0 0
Dispatcher Queue Statistics Thu Apr 12 18:13:22 2007
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
3
2000
10
10
--------++++--
+
DIA
6
6
2000
6
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
--------++++--
+
max_rq_id 14
wake_evt_udp_now 0
wake events total 9, udp 8 ( 88%), shm 1 ( 11%)
since last update total 9, udp 8 ( 88%), shm 1 ( 11%)
Dump of tm_adm structure: Thu Apr 12 18:13:22 2007
=========================
Term uid man user term lastop mod wp ta a/i (modes)
RM-T8, U9, , vyasa, 23:43:11, M0, W-1, , 1/0
Workprocess Comm. Area Blocks Thu Apr 12 18:13:22 2007
=============================
Slots: 300, Used: 2, Max: 1
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
1
DISPATCHER
-1
WPCAAD001
NiWait: sleep (5000 msecs) ...
NiISelect: timeout 5000 ms
NiISelect: maximum fd=1661
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 12 23:43:27 2007
NiISelect: TIMEOUT occured (5000 ms)
Shutdown server ...
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes...
Stop gateway
killing process (1592) (SOFT_KILL)
Stop icman
killing process (1604) (SOFT_KILL)
Terminate gui connections
send SHUTDOWN to REM TM 8
blks_in_queue/wp_ca_blk_no/wp_max_no = 2/300/8
LOCK WP ca_blk 2
return errno (-17) to T8
errormsg without overhead: take mode 0
NiBufIAlloc: malloc NiBufadm, to 0 bytes
try to send 14 to M0
NiBufSend starting
NiIWrite: write 14, 1 packs, MESG_IO, hdl 7, data complete
REL WP ca_blk 2
set status of T8 to TM_DISCONNECTED
NiSelClear: removed hdl 7 from selectset
DpDelSocketInfo: del info for socket 7 (type=3)
NiBufClose: clear extensions for hdl 7
NiBufSetStat: bufstat of hdl 7 changed from OK to OFF
NiICloseHandle: shutdown and close hdl 7 / socket 1492
dp_tm_adm[8].stat = DP_SLOT_FREE
DpGetSchedule: next schedule 1176401612
DpGetSchedule: no schedule found
DpITmSlotRelease: release slot 8
DpListInsert: insert elem 8 into tmadm_free_list (at begin)
DpListInsert: 193 elems in tmadm_free_list
DpListRemove: remove elem 8 from tmadm_inuse_list
DpListRemove: 8 elems in tmadm_inuse_list
[DpProcDied] Process lives (PID:1592 HANDLE:1632)
waiting for termination of gateway
NiWait: sleep (1000 msecs) ...
NiISelect: timeout 1000 ms
NiISelect: maximum fd=1661
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 12 23:43:28 2007
NiISelect: TIMEOUT occured (1000 ms)
[DpProcDied] Process died (PID:1592 HANDLE:1632)
[DpProcDied] Process died (PID:1604 HANDLE:1624)
DpHalt: cancel all lcom connections
MPI CancelAll 2 -> 0
MPI DeleteAll 2 -> 0
NiIMyHostName: hostname = 'vyasa'
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 163 bytes
NiBufSend starting
NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name -, type 4, key -
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 9962]
NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiSelClear: removed hdl 3 from selectset
MBUF state OFF
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 2/300/8
LOCK WP ca_blk 2
make DISP owner of wp_ca_blk 2
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 20)
MBUF component DOWN
NiBufClose: clear extensions for hdl 3
NiBufSetStat: bufstat of hdl 3 changed from OK to OFF
NiICloseHandle: shutdown and close hdl 3 / socket 1640
MsIDetach: detach MS-system
EsCleanup ....
***LOG Q05=> DpHalt, DPStop ( 1544) [dpxxdisp.c 8495]
Good Bye .....Dear Mr.Rafael Toshiaki ,
Sorry for the late reply. Please guide me to solve this issue.
Thanks in advance.
Sreevidya.
trc file: "dev_w0", trc level: 1, release: "640"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
B
B Fri Apr 13 23:40:29 2007
B create_con (con_name=R/3)
B Loading DB library 'F:\usr\sap\HUM\SYS\exe\run\dboraslib.dll' ...
B Library 'F:\usr\sap\HUM\SYS\exe\run\dboraslib.dll' loaded
B Version of 'F:\usr\sap\HUM\SYS\exe\run\dboraslib.dll' is "640.00", patchlevel (0.39)
B New connection 0 created
M systemid 560 (PC with Windows NT)
M relno 6400
M patchlevel 0
M patchno 43
M intno 20020600
M make: multithreaded, ASCII
M pid 3780
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3780) [dpxxdisp.c 1160]
I MtxInit: -2 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: JAVA is not active
M
M Fri Apr 13 23:40:30 2007
M DpShMCreate: sizeof(wp_adm) 6624 (828)
M DpShMCreate: sizeof(tm_adm) 2219848 (11044)
M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
M DpShMCreate: sizeof(comm_adm) 192000 (384)
M DpShMCreate: sizeof(vmc_adm) 0 (320)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: SHM_DP_ADM_KEY (addr: 03970040, size: 2505416)
M DpShMCreate: allocated sys_adm at 03970040
M DpShMCreate: allocated wp_adm at 039717A8
M DpShMCreate: allocated tm_adm_list at 03973188
M DpShMCreate: allocated tm_adm at 039731B0
M DpShMCreate: allocated wp_ca_adm at 03B910F8
M DpShMCreate: allocated appc_ca_adm at 03B95748
M DpShMCreate: allocated comm_adm_list at 03B96EB8
M DpShMCreate: allocated comm_adm at 03B96ED0
M DpShMCreate: allocated vmc_adm_list at 03BC5CD0
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 03BC5CF8
M DpShMCreate: allocated wall_adm at 03BC5D00
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Fri Apr 13 23:40:31 2007
M calling db_connect ...
C Got ORACLE_HOME=F:\oracle\hum\920 from environment
C Client NLS settings: AMERICAN_AMERICA.WE8DEC
C Logon as OPS$-user to get SAPHUM's password
C Connecting as /@HUM on connection 0 ...
C Attaching to DB Server HUM (con_hdl=0,svchp=06EB4ADC,svrhp=037D3524)
C
C Fri Apr 13 23:40:35 2007
C *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12154
[dboci.c 3514]
C *** ERROR => CONNECT failed with sql error '12154'
[dbsloci.c 9750]
C Try to connect with default password
C Connecting as SAPHUM/<pwd>@HUM on connection 0 ...
C Detaching from DB Server (con_hdl=0,svchp=06EB4ADC,srvhp=037D3524)
C Attaching to DB Server HUM (con_hdl=0,svchp=06EB4ADC,svrhp=037D3524)
C
C Fri Apr 13 23:40:40 2007
C *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12154
[dboci.c 3514]
C *** ERROR => CONNECT failed with sql error '12154'
[dbsloci.c 9750]
B ***LOG BV3=> severe db error 12154 ; work process is stopped [dbsh#2 @ 1195] [dbsh 1195 ]
B ***LOG BY2=> sql error 12154 performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-12154: TNS:could not resolve service name [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1269]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9413]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source = 255
M last_tid = 0
M last_mode = 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
M *****************************************************************************
M *
M * LOCATION SAP-Server vyasa_HUM_09 on host vyasa (wp 0)
M * ERROR tskh_init: db_connect
M *
M * TIME Fri Apr 13 23:40:40 2007
M * RELEASE 640
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 9589
M * COUNTER 1
M *
M *****************************************************************************
M
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 730]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 252]
M Entering ThSetStatError
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3780) [dpnttool.c 357] -
Error While Installing SAP ECC 6.0 on Oracle DB at 19th Step Import ABAP
Hey all,
I am NEw to this Forum..And this is My First Post in this Forum...
When I Was Installing SAP Ecc 6.0 on My PC.. I got An Error Message at 19th Step at Monitoring the Job 18...The Issue is Below...
INFO 2013-08-30 06:12:14
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.4.xml'.
INFO 2013-08-30 06:12:14
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.5.xml'.
INFO 2013-08-30 06:12:16
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2013-08-30 06:12:28
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/keydb.3.xml'.
INFO 2013-08-30 06:12:28
Execute step runMigrationMonitor of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0.
INFO 2013-08-30 06:12:33
Switched to user: ramadm.
INFO 2013-08-30 06:12:33
Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.
INFO 2013-08-30 06:12:33
Switched to user: ramadm.
INFO 2013-08-30 06:12:33
Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.
INFO 2013-08-30 06:12:33
Output of C:\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "E:\ECC 6.0\ecc6\DB1\EXP1;E:\ECC 6.0\ecc6\DB2\EXP2;E:\ECC 6.0\ecc6\DB3\EXP3;E:\ECC 6.0\ecc6\DB4\EXP4;E:\ECC 6.0\ecc6\DB5\EXP5;E:\ECC 6.0\ecc6\DB6\EXP6;E:\ECC 6.0\ecc6\DB6\EXP7;E:\ECC 6.0\ecc6\DB6\EXP8;E:\ECC 6.0\ecc6\DB6\EXP9;E:\ECC 6.0\ecc6\DB6\EXP10;E:\ECC 6.0\ecc6\DB6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe D:\usr\sap\RAM\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2013-08-30 06:17:03
Execution of the command "C:\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "E:\ECC 6.0\ecc6\DB1\EXP1;E:\ECC 6.0\ecc6\DB2\EXP2;E:\ECC 6.0\ecc6\DB3\EXP3;E:\ECC 6.0\ecc6\DB4\EXP4;E:\ECC 6.0\ecc6\DB5\EXP5;E:\ECC 6.0\ecc6\DB6\EXP6;E:\ECC 6.0\ecc6\DB6\EXP7;E:\ECC 6.0\ecc6\DB6\EXP8;E:\ECC 6.0\ecc6\DB6\EXP9;E:\ECC 6.0\ecc6\DB6\EXP10;E:\ECC 6.0\ecc6\DB6\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe D:\usr\sap\RAM\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
ERROR 2013-08-30 06:17:03
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2013-08-30 06:17:03
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
This info i found in the log file generated at sapint.log...So I request you all Plz Help me Regard this..and Thanx in Advance..
KumarKumar,
As suggested in this log, please try to see the logs import_monitor.java.log, import_monitor.log
However above log files might not suggest something specific but as we can see the latest error was w.r.t the package SAPAPPL2.
Please try to see SAPAPPL2.log and we should get something specific there as why the loading job failed for this package.
Thanks -
Error in PHASE PREP_EXTRACT/PREIMP: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP4
Hello,
I'm currently in upgrading a SAP R/3 4.7 system to a SAP ECC 6.0 EHP4.
Therefore I followed the Upgrade Guide from marketplace - installation- and upgrade guides - SAP ERP - SAP ERP 6.0 - SAP Enhancement Package 4 for SAP ERP 6.0 - Upgrade Guide SAP ERP including EHP4 SR1 - Unix on MaxDB.
I downloaded media from marketplace/swdc - Installations and Upgrades - SAP Application Components - SAP ERP - SAP ERP ENHANCE PACKAGE - EHP4 FOR SAP ERP 6.0 / NW7.01 - Upgrade.
I'm starting upgrade with upgrade master DVD 51036889_1 and 51036889_2.
Now upgrade breaks down in phase PREP_EXTRACT/PREIMP with error:
Severe error(s) occured in phase PREP_EXTRACT/PREIMP!
Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'
PREIMP.ELG says:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
R3trans preimport and RETURN CODE in R710VPE.REX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
Kernel is stored in /usr/sap/REX/SYS/exe/run and database is ADA (maxdb).
File R710VPE.REX says:
4 EPU201XBEGIN OF SECTION BEING ANALYZED
4 ETW000 R3trans version 6.13 (release 640 - 17.02.10 - 13:07:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 07.03.2011 - 15:28:36
4 ETW000 control file: /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
4 ETW000 > import
4 ETW000 > file='/usr/sap/REX/upg/abap/bin/R710VPE.SAP'
4 ETW000 > safeandslow=yes
4 ETW000 > buffersync =yes
4 ETW000 > commit =1048576
4 ETW000 > importtruncated =yes
4 ETW000 R3trans was called as follows: R3trans -w /usr/sap/REX/upg/abap/tmp/R710VPE.REX -u 1 /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
4 ETW000 active unconditional modes: 1
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
4 EPU202XEND OF SECTION BEING ANALYZED
Can anybody help me out here?
Regards,
JuliaHello,
I run 'R3trans -x' command, but there was no problem - connection to database was working.
Problem was following:
Before starting the sdt service on host, I set environment variables JAVA_HOME and LD_LIBRARY_PATH for sidadm. That's not neccessary and that was the problem. Without setting these variables it is working now.
Thanks,
Julia -
Dispacher not getting Started...SAP ECC 6.0 on Win2K3 and Oracle.
HI Experts,
I have installed SAP ECC 6.0 (OS-Win2003sp2 DB-Oracle10g). Installation was successful, I have also logged in and created a user in SU01. But when I restart the system I am not able to up the sapserver. SAP MMC - dispacher is not starting. I have started OracleListener in service.sap and restarted the system. Un-installed and again installedj2sdk1.4.2_12 and restarted the system...No use, still dispatcher is not getting up....Pls find below paster Developer Trace for Dispatcher....
trc file: "dev_disp", trc level: 1, release: "700"
sysno 00
sid PRD
systemid 560 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 111
intno 20050900
make: multithreaded, Unicode, optimized
pid 2200
Wed Oct 28 09:26:27 2009
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 2200) [dpxxdisp.c 1239]
* shared lib "dw_xml.dll" version 111 successfully loaded*
* shared lib "dw_xtc.dll" version 111 successfully loaded*
* shared lib "dw_stl.dll" version 111 successfully loaded*
* shared lib "dw_gui.dll" version 111 successfully loaded*
* shared lib "dw_mdm.dll" version 111 successfully loaded*
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Wed Oct 28 09:26:32 2009
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds*
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5361]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >sap_PRD_00 <
DpShMCreate: sizeof(wp_adm) 18672 (1436)
DpShMCreate: sizeof(tm_adm) 4232256 (21056)
DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm) 528064 (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1536)
DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 06810040, size: 4892312)
DpShMCreate: allocated sys_adm at 06810040
DpShMCreate: allocated wp_adm at 06812090
DpShMCreate: allocated tm_adm_list at 06816980
DpShMCreate: allocated tm_adm at 068169B0
DpShMCreate: allocated wp_ca_adm at 06C1FDF0
DpShMCreate: allocated appc_ca_adm at 06C25BB0
DpShMCreate: allocated comm_adm at 06C27AF0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 06CA89B0
DpShMCreate: allocated gw_adm at 06CA89F0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 06CA8A20
DpShMCreate: allocated wall_adm at 06CA8A28
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 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
J2EE server info
start = TRUE
state = STARTED
pid = 2404
argv[0] = E:\usr\sap\PRD\DVEBMGS00\exe\jcontrol.EXE
argv[1] = E:\usr\sap\PRD\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=E:\usr\sap\PRD\SYS\profile\PRD_DVEBMGS00_sap
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1048
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=PRD
argv[7] = -DSAPMYNAME=sap_PRD_00
argv[8] = -DSAPPROFILE=E:\usr\sap\PRD\SYS\profile\PRD_DVEBMGS00_sap
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1629]
Wed Oct 28 09:26:33 2009
***LOG Q0K=> DpMsAttach, mscon ( sap) [dpxxdisp.c 11753]
DpStartStopMsg: send start message (myname is >sap_PRD_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
Wed Oct 28 09:26:34 2009
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.
DpJ2eeLogin: j2ee state = CONNECTED
Wed Oct 28 09:26:51 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4248]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444*
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1063) [nixxi.cpp 4248]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2404)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]*
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Wed Oct 28 09:27:13 2009
ERROR => W0 (pid 2412) died [dpxxdisp.c 14441]*
ERROR => W1 (pid 2420) died [dpxxdisp.c 14441]*
ERROR => W2 (pid 2428) died [dpxxdisp.c 14441]*
ERROR => W3 (pid 2436) died [dpxxdisp.c 14441]*
ERROR => W4 (pid 2444) died [dpxxdisp.c 14441]*
ERROR => W5 (pid 2452) died [dpxxdisp.c 14441]*
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W6 (pid 2460) died [dpxxdisp.c 14441]*
my types changed after wp death/restart 0xbe --> 0xbc
ERROR => W7 (pid 2468) died [dpxxdisp.c 14441]*
my types changed after wp death/restart 0xbc --> 0xb8
ERROR => W8 (pid 2476) died [dpxxdisp.c 14441]*
ERROR => W9 (pid 2484) died [dpxxdisp.c 14441]*
ERROR => W10 (pid 2492) died [dpxxdisp.c 14441]*
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W11 (pid 2500) died [dpxxdisp.c 14441]*
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W12 (pid 2508) 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=1577
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Oct 28 09:27:23 2009
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Wed Oct 28 03:57:23 2009
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 2412 Ended no 1 0 0
1 DIA 2420 Ended no 1 0 0
2 DIA 2428 Ended no 1 0 0
3 DIA 2436 Ended no 1 0 0
4 DIA 2444 Ended no 1 0 0
5 DIA 2452 Ended no 1 0 0
6 UPD 2460 Ended no 1 0 0
7 ENQ 2468 Ended no 1 0 0
8 BTC 2476 Ended no 1 0 0
9 BTC 2484 Ended no 1 0 0
10 BTC 2492 Ended no 1 0 0
11 SPO 2500 Ended no 1 0 0
12 UP2 2508 Ended no 1 0 0
Dispatcher Queue Statistics Wed Oct 28 03:57:23 2009
===========================
--------++++--+
| Typ | now | high | max | writes | reads |
--------++++--+
| NOWP | 0 | 2 | 2000 | 6 | 6 |
--------++++--+
| DIA | 5 | 5 | 2000 | 5 | 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 |
--------++++--+
max_rq_id 12
wake_evt_udp_now 0
wake events total 8, udp 7 ( 87%), shm 1 ( 12%)
since last update total 8, udp 7 ( 87%), shm 1 ( 12%)Hi,
Could you please also paste dev_w0 logs ?
Thanks
Sunny -
/usr/sap/trans/actlog - Increase log detail
Hi everyone,
I'm after away of logging when objects are added to deleted from a modifiable change request (eg I want to see the object details, who, and date/time. I'm aware that when you create a new transport request/task that a log is created in /usr/sap/trans/actlog, however I was wondering if there was away to increase the detail level of what is written to the log file, or if someone knows of another way of tracking this information.
Cheers
ShaunOperating system level files in the transport process:
The SAP C program TP, requires a special file structure for the transport process. The file system is operating system dependent. TP uses a transport directory or file system, which is called /usr/sap/trans.
The /usr/sap/trans file system is generally NFS mounted form the development system to other systems unless a system is defined as a single system in the CTS pipeline. All the sub directories should have <SID>adm as the owner and sapsys as the group; and proper read, write and execute access should be given to owner and the group. The TP imports are always performed by <SID>adm.
The following are the subdirectories in /usr/sap/trans:
/data
/cofiles
/bin
/log
/actlog
/buffer
/sapnames
/tmp
/usr/sap/trans/data: holds the data of transport objects after they are released . This subdirectory contains files named R9<5 digits >. containing the exported objects. The example of a data file is R904073.DEV. The extension DEV means the data file was released from the DEV or development system.
/usr/sap/trans/cofiles: The cofiles directory holds the command files for all change requests. This subdirectory contains command files named K9<5 digits>.. They contain, for example, import steps to be performed. files are like a command or control files used to import the data files. The common directory for CTS system is /usr/sap/trans. After a change request is released from the source system , the data is exported immediately to the file system of the operating system. The SAP transport utility TP uses the cofile to transport a data file. The example of a file in cofiles directory is K904073.DEV.
/usr/sap/trans/bin: holds the most important file TPPARAM in the CTS system. TPPARAM file has all the information about the CTS systems in the CTS pipeline. TPPARAM file is the parameter file for the transport program TP and it is the common file for all the systems in the CTS pipeline. As you know already that /usr/sap/trans should be NFS mounted to all the systems in a CTS pipeline, TP program has access to the TPPARAM file from all the systems. The following is an example of typical TPPARAM file for five SAP systems in the CTS pipeline:
#@(#) TPPARAM.sap 20.6 SAP 95/03/28
# Template of TPPARAM for UNIX #
# First we specify global values for some parameters, #
# later the system specific incarnation of special parameters #
# global Parameters #
transdir = /usr/sap/trans/
dbname = $(system)
alllog = ALOG$(syear)$(yweek)
syslog = SLOG$(syear)$(yweek).$(system)
# System spezific Parameters #
# Beispiel T11 #
DEV/dbname = DEV
DEV/dbhost = sap9f
DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
QAS/dbname = QAS
QAS/dbhost = sap8f
QAS/r3transpath = /usr/sap/QAS/SYS/exe/run/R3trans
TRN/dbname = TRN
TRN/dbhost = sap17
TRN/r3transpath = /usr/sap/TRN/SYS/exe/run/R3trans
PRE/dbname = PRE
PRE/dbhost = sap19f
PRE/r3transpath = /usr/sap/PRE/SYS/exe/run/R3trans
PRD/dbname = PRD
PRD/dbhost = sap18f
PRD/r3transpath = /usr/sap/PRD/SYS/exe/run/R3trans
/usr/sap/trans/log: holds the entire log files, trace files and statistics for the CTS system. This subdirectory contains all log files, such as ULOGs, ALOGs, SLOGs, log files named 9<5 digits>. for each executed step, and log files named . for steps that are collectively executed, for example, step N (structure conversion) and step P (move nametabs). When the user goes to SE09 (workbench organizer) or SE10 (customizing organizer) transaction and opens the log for a transport, the log file for that transport will be read from /usr/sap/trans/log directory. Each change request should have a log file. Examples of log files are DEVG904073.QAS, DEVI904073.QAS and DEVV904073.QAS. The name of a log file consists of the names of the change request, the executed step, and the system in which the step was executed:
<source system><action><6 digits>.<target system>
Now we can analyze the above example DEVG904073. QAS. The <source system> = DEV, <action> = G or report and screen generation, <6 digits> = 904073 (these six digits numbers are exactly the same number as the six digits of the transport) and the <target system> = QAS
Possible values for <action> are:
A: Dictionary activation
D: Import of application-defined objects
E: R3trans export
G: Report and screen generation
H: R3trans dictionary import
I: R3trans main import
L: R3trans import of the command files
M: Activation of the enqueue modules
P: Test import
R: Execution of reports after put (XPRA)
T: R3trans import of table entries
V: Set version flag
X: Export of application-defined objects.
/usr/sap/trans/actlog: This subdirectory contains files named Z<6 digits> recording each action on a request or task, for example, creation, release, or change of ownership. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
1 ETK220 “==================================================” “=================
=============================
1 ETK191 “04/30/1998″ Action log for request/task: “DEVK902690″
1 ETK220 “==================================================” “=================
=============================
1 ETK185 “04/30/1998 18:02:32″ “MOHASX01″ has reincluded the request/task
4 EPU120 Time… “18:02:32″ Run time… “00:00:00″
1 ETK193 “04/30/1998 18:02:33″ “MOHASX01″ owner, linked by “MOHASX01″ to “DEVK902691″
4 EPU120 Time… “18:02:33″ Run time… “00:00:00″
1 ETK190 “05/04/1998 11:02:40″ “MOHASX01″ has locked and released the request/task
1 ETK194 “05/04/1998 11:02:40″ **************** End of log *******************
4 EPU120 Time… “11:02:40″ Run time… “00:00:09″
~
~”DEVZ902690.DEV” 10 lines, 783 characters
/usr/sap/trans/buffer: This subdirectory contains an import buffer for each SAP System named after the SID. When a change request is released, the import buffer of the target systems is updated. Contains control information on which requests are to be imported into which systems and in what order the imports must occur. The /usr/sap/trans/buffer will have a directory for each system in the CTS pipeline. For example the buffer file for DEV system is /usr/sap/trans/buffer/DEV.
/usr/sap/trans/sapnames: holds information pertaining to transport requests for each system user. This subdirectory contains files named after the user's logon name. A file is created for each SAP System user, who performs transport actions, and updated when the user releases a request. There are files for each user who released change requests from the system.
/usr/sap/trans/tmp: holds information about temporary data and log files. While the transport is occurring the Basis administrator can find a file that is related to the transport in the tmp directory; that file shows the exact status if the transport (What objects are being imported at that time).
Important SAP delivery class and table types and tables in the CTS process:
Delivery class
The delivery class defines who (i.e. the SAP system itself or the customer) is responsible for maintaining the table contents. In addition the delivery class controls how the table behaves in a client copy and an upgrade. For example when you select a SAP defined profiles to perform a client copy, certain tables are selected according to their delivery class. DD02L table can show what delevery class a table belongs to.
The following delivery classes exist:
A: Application table.
C: Customizing table, maintenance by customer only.
L: Table for storing temporary data.
G: Customizing table, entries protected against overwriting.
E: Control table.
S: System table, maintenance only by SAP.
W: System table, contents can be transported via own TR objects.
Table type
The table type defines whether a physical table exists for the logical table description defined in the ABAP/4 Dictionary and how the table is stored on the database.
The following are different table types in SAP:
Transparent Tables
There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary are same. For every transparent table in SAP, there is a table in database. The business and application data are stored in transparent tables.
Structure
No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
Append Structure
An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.
The following table types are used for internal purposes, for example to store control data or for continuous texts:
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated-pooled tables are stored.
Cluster table
Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
Tables in CTS process:
TRBAT and TRJOB:
TRJOB and TRBAT are the major tables in the CTS process. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself.
By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step. For each transport request , TP program inserts an entry into table TRBAT. If the return code 9999 in this table then the step is waiting to be performed. Return code 8888 indicates that the step is active and currently being processed. A return code of 12 or less indicates that the step is finished. In addition, TP inserts a header entry to let the RDDIMPDP program know to start processing. The column return code will therefore contain a B for begin. When RDDIMPDP is started, it sets the header entry to R(un), and starts the required program. When all the necessary actions are performed for all the transport requests, the column return code contains all the return codes received, and the column TIMESTAMP contains the finishing time. The header entry is set to F(inished). TP monitors the entries in TRBAT and TRJOB tables. When the header entry in TRBAT is set to finished. The entry in TRJOB is deleted.
Transport Tables SE06
TDEVC – Development classes
TASYS – Details of the delivery. Systems in the group that should automatically receive requests, have to be specified in table TASYS.
TSYST – The transport layers will be assigned to the integration systems. ( Define all systems)
TWSYS – Consolidation routes ( define consolidation path)
DEVL – Transport layers are defined here
In “Configuring the CTS system” section, We will learn more about the transport tables in SE06 transaction
Programs in the CTS process:
In the CTS table section we learned about the RDDIMPDP program. RDDIMPDP program needs to be scheduled in all the clients in an instance. It is recommended to schedule the RDDIMPDP as event driven.
RDDPUTPP and RDDNEWPP programs can be used to schedule RDDIMPDP program in the background.
The ABAP/4 programs that RDDIMPDP starts are determined by the transport step to be executed that is entered in the function field of table TRBAT.
Function Job Name Description of transport Steps
J RDDMASGL Activation of ABAP/4 dictionary objects
M RDDMASGL Activation of match codes and lock objects
S RDDDISOL Analysis of database objects to be converted
N RDDGENOL Conversion of database objects
Y RDDGENOL Conversion of matchcode tables
X RDDDICOL Export of AD0 objects
D RDDDIC1L Import of AD0 objects
E RDDVERSE Version management update during export
V RDDVERSL Version management update during import
R RDDEXECL Execution of programs for post – import processing
G RDDDIC3L Generation of ABAP/4 programs and screens
Version Management:
One of the important features of Workbench Organizer is Version Management. This feature works for all the development objects. Using the version management feature the users can compare and retrieve previous versions of objects.
Version management provides for comparisons, restore of previous versions, documentation of changes and assistance in the adjustment of data after upgrading to a new release. With the release of a change request, version maintenance is automatically recorded for each object. If an object in the system has been changed N times, it will have N delta versions and one active version. To display version management, for ABAPs use transaction SE38 and for tables, domains and data elements use SE11. The path to follow is Utilities -> Display version. Using version management the users can view existing version for previously created ABAP code, make changes to the code, compare code versions and restore original version of the code. Now the users will be restore previous versions without cut and paste steps of the past.
TP and R3trans program:
The basis administrator uses TP program to transport SAP objects from one system to another. TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. R3trans is one of the most important utility program called by TP. Before using the TP program, the basis administrator needs to make sure that the CTS system is setup properly and the right version of TP is running in the system. The TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory. It is automatically copied in the install process. A global parameter file TPPARAM that contains the databases of the different target systems and other information for the transport process controls TP. The global parameter file determines which R3trans is used for each system. If the parameter r3transpath is not defined properly then no export and import can be done. The basis administrator should make sure that the default value “r3transpath” is properly defined. Later in this chapter we will learn more about TP and R3trans; also we are going to see how they are used.
Configuring the TPPARAM file:
Each time TP is started, it must know the location of the global parameter file. As we have seen before TPPARAM file should be in directory /usr/sap/trans/bin. The parameters in TPPARAM can either global (valid for each and every system in the cts pipeline) or local to one system. Th parameters are either operating system dependant (these parameters preceded by a keyword corresponding to the specific operating system) or database dependant (contain a keyword corresponding to a specific database system).
The global parameter file provides variables that can be used for defining parameters. The variables can be defined in format: $(xyz). The brackets can be substituted with the “\”-character if required.
The following pre-defined variables are available for the global parameter file:
$(cpu1): The CPU name can be sun or as4 for example. In heterogeneous networks this variable is very important.
$(cpu2): Acronym for the name of the operating system. The example for this variable can be
hp-ux, or sunos . This is an operating system specific variable.
$(dname): Used for the day of the week (SUN,MON,….).
$(mday): Used for the day of the current month (01-31).
$(mname): Used for the name of the month (JAN…DEC).
$(mon): Used for the Month (01-12).
$(system): R/3 System name.
$(wday): Day of the week (00-06, Sunday=00, Monday=01, Tuesday=02 and so on).
$(yday): Day of the current year (001-366). Using the number any day of the year can be chosen.
$(year): Year (Example:1998 or 1999).
$(syear): Short form of the year (two positions).
$(yweek): Calendar week (00-53). The first week begins with the first Sunday of the year.
For the database connection:
The transport environment also needs parameters to connect to the R/3 System database. As we know already the every instance in the R/3 CTS pipeline has its own database, therefore specific parameters should be defined for each database system. From dbtype parameter of RSPARAM file, TP program identifies the database system.
The two parameters “dbname” and “dbhost” are required for ORACLE databases.
DBHOST: is the name of the computer on which the database processes execute. TCP/IP name of the host if NT is being used.
DBNAME: is the name of the database instance.
As of Release 3.0E, two new parameters have been introduced.
DBLOGICALNAME: The default value is $(system). The logical name that was used to install the database.
DBCONFPATH: The default value is $(transdir).
The parameters “dbname” and “dbhost” are also used for INFORMIX databases in an installation:
DBHOST: Same as Oracle.
DBNAME: Name of the database instance, uppercase and lowercase are distinguished here.
INFORMIXDIR : “/informix/<SAPSID>” is the default value. Defines the directory namewhere the database software can be found.
INFORMIXSQLHOSTS: “$(informixdir)/etc/sqlhosts[.tli|.soc]“is default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
INFORMIX_SERVER: “$(dbhost)$(dbname)shm” is the default value. The name of the database server may be specified for a local connect.
INFORMIX_SERVERALIAS: “$(dbhost)$(dbname)tcp”is the default vlue. The name of the database server can be specified for a remote connect.
For Microsoft SQL Server database the two parameters “dbname” and “dbhost” are also required. DBHOST: The TCP/IP name of the host on which the database is running.
DBNAME: The database instance name.
For DB2 in AS/400 only “dbhost” is required.
DBHOST: System name of the host on which the database is running.
If the”OptiConnect” is used, the following line should be specified:
OPTICONNECT 1
For DB2/ AIX
The two parameters “dbname” and “dbhost” are required
DBHOST: The host on which the database processes are running. It is the TCP/IP name of the host for Windows NT (As we have seen in the earlier examples).
DBNAME: Database instance name.
The DB2 for AIX Client Application Enabler Software must also be installed on the host on which tp is running.
ALLLOG: “ALOG” $(syear) $(yweek)”is the default value. This variable can be used in TPPARAM file to specify the name of a file in which tp stores information about every transport step carried out for a change request anywhere in the transport process. The file always resides in the log directory.
SYSLOG: “SLOG $(syear) $(yweek).$(system)” is the default value. This variable can be used to name a file in which tp stores information about the progress of import actions in a certain R/3 System. The file does not store information for any particular change request. The file always resides in the log directory.
tp_VERSION: Zero is the default value. If this parameter is set to not equal to zero, a lower version of tp may not work with this TPPARAM file. If the default value (zero) is set, the parameter has no affect.
STOPONERROR: (Numeric value) The default value is 9. When STOPONERROR is set to zero, tp is never stopped in the middle of an “import” or “put” call. When STOPONERROR is set to a value greater than zero, tp stops as soon as a change request generates a return code that is equal to or greater than this value (The numeric value of the STOPONERROR parameter is stored in the variable BADRC). Change requests, which still have to be processed for the current step, are first completed. A “SYNCMARK” in the buffer of the R/3 System involved, sets a limit here. tp divides the value of this parameter between two internal variables. STOPONERROR itself is treated as a boolean variable that determines whether tp should be stopped, if the return code is too high.
REPEATONERROR (Numeric value too): The default value is 9. The REPEATONERROR parameter is similar to STOPONERROR. The difference is, REPEATONERROR specifies the return code up to which a change request is considered to be successfully processed. Return codes less than REPEATONERROR are accepted as “in Order”. Change requests that were not processed successfully stay in the buffer.
NEW_SAPNAMES: Default value is “FALSE”. A file is created for each user of the R/3 System group in the “sapnames” subdirectory of the transport directory. Except some of the operating system,the name of the user is the name of the file. It is very important to remember hat the special characters or length of the file name could cause problems. If all the R/3 Systems in the transport group have at least Release level 3.0.; TP program is efficient to handle this problem. The user names are modified to create file names that are valid in all operating systems and the real user names are stored in a corresponding file.
Though we have seen so many parameters, for the minimum configuration the following two parameters are very important.
TRANSDIR: specifies the name of the common transport directory. The following is a typical example from TPPARAM of Unix as we have seen before.
transdir = /usr/sap/trans/
DBHOST: contains the name of the database host. In Windows NT environment, this is the TCP/IP host name. The following is an example in Unix:
DEV/dbname = DEV
DEV/dbhost = sap9f
DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
For TP, to control ‘Start and Stop’ command files and database in R/3 the following important parameters are specified in TPPARAM:
Parameters for the tp Function “PUT”: LOCK_EU (boolean) default value is “TRUE”. Though from version 3.1 onward the tp put command is used seldom in cts process still it is important to know how this parameter works. When “tp put” is used, it changes the system change option . If the parameter is set to “FALSE” nothing gets changed. If the parameter is set to “TRUE”, the system change option is set to “Objects cannot be changed” at the beginning of the call, and gets changed back to its previous value at the end of the call. The “tp put” command will give the exact status of the locking mechanism.
LOCKUSER (used as boolean value): Default value is “TRUE”. This parameter is about the user login while tp put call is executed. If this parameter is set to “FALSE”, no locking mechanism for the users takes affect. If this parameter is defined as “TRUE” then a character is set in the database level; so only DDIC and SAP* can log on to the system. Users that have already logged on are not affected (this is a reason for activating the parameters STARTSAP and STOPSAP). The charactertor is removed at the end of the call, and all the users can log on to the SAP R/3 System again.
STARTSAP: Default value is ” “.or “PROMPT” for Windows NT . This parameter is used by TP to start an R/3 System. It is not necessary for the clients to make tp start and stop R/3 system..
STOPSAP: Default value is ” “or “PROMPT” for Windows NT. TP uses this parameter to stop an R/3 System.
STARTDB: Default value is ” “. TP uses the value of this parameter to start the database of an R/3 System.
The parameter is not active under Windows NT.
STOPDB: Default value is ” “. TP uses the value of this parameter to stop the database of an R/3 System.
This parameter is not active under Windows NT.
The above parameters in UNIX can be used as following:
STARTSAP = startsap R3
STOPSAP = stopsap R3
STARTDB = startsap db
STOPDB = stopsap db
In Windows NT:
STARTSAP = \\$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\startsap.exe
R3 <SID> <HOST NAME> <START PROFILE>
STOPSAP = \\$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\stopsap.exe
R3 <SID> <HOST NAME> <INSTANCE> <PROFILE PATH + Instance profile>
The parameters STARTDB and STOPDB are not active under Windows NT.
Parameters for the tp function “CLEAROLD”
DATALIFETIME (Numeric): Default value is “200″. When the data file has reached a minimum age, it is moved to the subdirectory old data with tp check. tp clearold all. The life span of the data files in the data sub directory can be set in days with this all, parameter.
OLDDATALIFETIME (Numeric): Default value is “365″. When a file located in the olddata subdirectory is no longer needed for further actions of the transport system and has reached a minimum age, it is removed with tp check.all, tp clearold all. The minimum age in days can be set with this parameter.
COFILELIFETIME (Numeric): Default value is “365″. This parameter is used just like DATALIFETIME parameter.
LOGLIFETIME (Numeric): Default value is “200″. This parameter applies to the life span of the log files. When the log files in log subdirectory is no longer needed for the transport system and has reached a minimum age, it is deleted with the calls tp check.all, tp clearold all. The minimum age in days can be defined with this parameter.
The Three Key Utilities of the CTS system (TP, R3trans and R3chop):
TP: Earlier in this chapter we have seen the objectives of TP. The TP transport control program is a utility program that helps the user to transport objects from one system to another. TP program is the front-end for the utility R3trans. TP stands for “Transports and Puts”. To make the TP work successfully the CTS system needs to be correctly configured. The following steps are very important for TP to run properly.
The transport directory /usr/sap/trans must be installed and NFS mounted to all the systems in the CTS pipe line.
RDDIMPDP program must be running (event driven is recommended) in each client. RDDIMPDP can be scheduled in the background by executing RDDNEWPP or RDDPUTPP. Use the tp checkimpdp <sap sid> command in /usr/sap/trans/bin directory as <sid>adm user to check RDDIMPDP program.
Use the tp connect <sap sid> command in /usr/sap/trans/bin directory to see whether the tp program is connecting to the database successfully or not. To run TP command the user has to logon as <sid>adm in source or target system.
The R/3 Systems in the CTS pipeline must have different names.
The Global CTS Parameter File TPPARAM must be correctly configured.
The source system (for the export) and target system ( for the import) must have at least two background work processes. TP always schedules the C class job, so if all the background jobs are defined as A class job then there will be problems in transport steps.
Important Tips :.It is always better to have the up to date TP version installed in your system. A user can ftp a current version of TP from SAPSERV4 of SAP. Though R3trans and other utility programs can be used to do the transport, it is recommended to use TP whenever possible for the following reasons..
The exports and imports are done separately using TP program. For example: when a transport is released from the system, the objects are exported from the source database to the operating system and then the import phase starts to transport those objects to the target system.
TP takes care of the order of the objects. The order, that was followed to export the objects; the same order will be followed to import them to the target database.
The TP command processes all change requests or transports in the SAP system buffer that have not yet been imported successfully. All the import steps are executed automatically after TP calls R3trans program to execute the following necessary steps:
Dictionary Import: ABAP/4 dictionary objects will be imported in this step.
Dictionary Activation: Name tabs or runtime descriptions will be written inactively. The R/3 system keeps running until the activation phase is complete. The enqueue modules are the exceptions in the running phase. After the activation of new dictionary structure the new actions are decided to get the runtime objects to the target system.
Structure conversion: If necessary the table structure is changed in this phase.
Move Nametabs: The new ABAP/4 Dictionary runtime objects which were inactive up to now are moved into the active runtime environment in this process. The database structures are adjusted accordingly. From the first step to the Main import step inconsistencies can occur to the R/3 system. After the main import phase all the inconsistency ca be solved.
Main import with R3trans: All the data are imported completely and the system comes to a consistent state.
Activation of enqueue-objects: The enqueue-objects cannot be activated in the same way as the objects of the ABAP/4 Dictionary, so they have to be activated after the main import in this step. They are then used directly in the running system.
Structure Conversion of match codes, Import application defined objects, versioning and execution of user defined activities are some of the steps after activation of enqueue-objects. The next step is generation of ABAP/4 programs and screens, where all the programs and screens associated with the change request are generated. When all the import steps are completed successfully, the transport request is removed from the import buffer.
It is recommended by SAP to schedule regular periods for imports into the target system (e.g. daily, weekly or monthly). Shorter periods between imports are not advisable. The transport to production should not be done in the off hours when the users are not working
TP can be started with different parameters. The “tp help” command can help user to generate a short description about the use of the command.
The following are the some important commands of TP:
For export:
tp export <change request>: The complete objects in the request from the source system will be transported. This command also used by SAP System when it releases a request.
tp r3e <change request>: R3trans export of one transport request.
tp sde <change request>: Application defined objects in one transport request can be exported.
tp tst <change request> <SAP system >: The test import for transport request can be done using this command.
tp createinfo <change request>: This command creates a information file that is automatically done during the export.
tp verse <request>: This command creates version creates versions of the objects in the specified request.
To Check the transport buffer, global parameter file and change requests:
tp showbuffer <sid>: Shows all the change requests ready to be imported to the target system.
tp count <sid>: Using this command users can find out the number of requests in the buffer waiting for import.
tp go <sid>: This command shows the environment variables needed for the connection to the database of the <sid> or target system.
tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The default value is shown for parameters that have not been set explicitly.
To import the change requests or transports:
tp addtobuffer <request>.<sid>: If a change request is not in the buffer then this command is used to add it to the buffer, before the import step starts.
tp import all <sid>: This command imports all the change requests from the buffer to the target system.
tp put <sid>: The objective of this command is same as “tp import all <sid>”, but this command locks the system. This command also starts and stops the SAP system, if the parameters startsap and stopsap parameters are not set to ” “.
tp import <change request> <sid>: To import a single request from the source system to target system.
tp r3h <change request>| all <sid>: Using this command user can import the dictionary structures of one transport or all the transport from the buffer.
tp act <change request>|all <sid>: This command activates all the dictionary objects in the change request.
tp r3i <change request> | all <sid>: This command imports everything but dictionary structures of one.
tp sdi <change request>|all <sid>: Import application-defined objects.
tp gen <change request>|all <sid>: Screen and reports are generated using this command.
tp mvntabs <sid>: All inactive nametabs will be activated with this command.
tp mea <change request>|all <sid>: This command will activate the enqueue modules in the change request.
When you call this command, note the resulting changes to the import sequence.
Additional tp utility options:
tp check <sid>|all (data|cofiles|log|sapnames|verbose): User uses this command to find all the files in the transport directory that are not waiting for imports and they have exceeded the minimum time specified using the COFILELIFETIME, LOGFILELIFETIME, OLDDATALIFETIME and DATALIFETIME parameters of TPPARAM file.
tp delfrombuffer <request>.<sid>: This command removes a single change request from the buffer. In case of TMS, the request will be deleted from the import queue.
tp setstopmark <sid>: A flag is set to the list of requests ready for import into the target system. When the user uses the command tp import all <sapsid> and tp put <sapsid>, the requests in front of this mark are only processed. After all the requests in front of the mark have been imported successfully, the mark is deleted.
tp delstopmark <sid>: This command deletes the stop mark from the buffer if it exists.
tp cleanbuffer <sapsid>: Removes all the change requests from the buffer that are ready for the import into the target system.
tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The users that have already logged on are not affected by the call.
tp unlocksys <sid>: This command unlocks the system for all the users.
tp lock_eu <sid>: This command sets the system change option to “system can not be changed” tmporarily.
tp unlock_eu <sid>: This command unlocks the system for all the changes.
tp backupall <sid>: This command starts a complete backup using R3trans command. It uses /usr/sap/trans/backup directory for the backup.
tp backup delta <sid>: Uses R3trans for a delta backup into /usr/sap/trans/backup directory.
tp sapstart <sid>: To start the R/3 system.
tp stopsap <sid>: To stop the R/3 system.
tp dbstart <sid>: To start the database.
tp dbstop <sid>: To stop the database.
Unconditional modes for TP: Unconditional modes are used with the TP program and these modes are intended for the special actions needed in the transport steps. Using unconditional mode user can manipulate the rules defined by the workbench organizer. The unconditional mode should be used when needed, otherwise it might create problems for the R/3 system database. Unconditional mode is used after the letter “U” in the TP command. Unconditional mode can be a digit between 0 to 9 and each has a meaning to it. The following is a example of a import having unconditional mode.
tp import devk903456 qas client100 U12468
0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.
1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.
2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.
3: When used with tp import, it overwrites the system-dependant objects.
5: During the import to the consolidation system it permits the source systems other than the integration system.
6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.
8: During import phase it ignores the limitations caused by the table classification.
9: During import it ignores that the system is locked for this kind of transport.
R3trans: TP uses R3trans program to transport data from one system to another in the CTS pipeline. efficient basis administrator can use R3trans directly to export and import data from and into any SAP systems. Using this utility transport between different database and operating system can e done without any problems. Different versions of R3trans are fully compatible with each other and can be used for export and import. The basis administrator has to be careful using R3trans for different release levels of R/3 software; logical inconsistency might occur if the up to date R3trans is not used for the current version of R/3 system.
The syntax for using the control file is following:
R3trans [<options>] <control file> (several options used at the same time; at least one option must be there)
For example: R3trans –u 1 –w test.log test
In the above example a unconditional mode is used, a log file “test.log” file is used to get the log result and a control file “test”, where the instructions are given for the R3trans to follow. The user needs to logon as <sid>adm to execute R3trans.
The following options are available for the R3trans program:
R3trans -d : This command is used to check the database connection .
R3trans -u <int>: Unconditional mode can be used as we have seen in the above example.
R3trans -v : This is used for verbose mode. It writes additional details to the log file
R3trans -i <file>: This command directly imports data from data file without a control file.
R3trans -l <file>: This provides output of a table of contents to the log file.
R3trans -n : This option provides a brief information about new features of R3trans.
R3trans –t: This option is used for the test mode. All modifications in the database are rolled back.
R3trans -c <f1> [<f2>]: This command is used for conversion. The <f1> file will be copied to <f2> file after executing a character set conversion to the local character set.
Important tips: Do not confuse the backup taken using R3trans with database backup. The backups taken using R3trans are logical backups of objects. In case something happens to the SAP system these backups can not be used for recovery. R3trans backups can be only used to restore a copy of a particular object that has been damaged or lost by the user.
R3trans -w <file>: As we have seen in the above example this option can be used to write to a log file. If no file is mentioned then trans.log is default directory for the log.
R3trans also can be used for the database backup.
R3trans –ba: This command is used for a complete backup. we will see in the next paragraph how to use
the control file for the backup.
R3trans –bd: This command is used for a delta backup if the user does not want a complete backup.
R3trans –bi: This option -
SAP PI FTP sender adapter not working with SAP ECC over Itanium
Hi,
We have been running normally SAP PI 7.0 SP14 with no issue for a while.
We are now in the process of migrate the SAP ECC system from PA risc to IA platform. We are performing some tests between SAP PI and SAP ECC to check that the platform migration is not affecting us in any way and we have found that FTP adapter sender is not working anymore (receiver is working as usual).
We place some files in the new ECC system and when PI goes to retreive the files it is like it can not read anything. It gives no error but it does not pick any file. This is not happening with the old platform.
Does anyone have any idea?
Thanks a lot for your help
DianaHi,
I am using FTP connection and for the receiver it is working fine.
Thanks
Diana
Maybe you are looking for
-
iPhone 4s just updated with IOS 8. Now my calendar does not offer the full list of items by day on the screen. Instead I see the month and below the month are the appointments in a list for the selected day only. I would like the option to have the f
-
Single Clustered pair - n+1 migration
I am fairly new to the Sun cluster environment, having helped build one single pair cluster connected to fully redunant fibre channels. Currently this is controlling the entire ISPs email and web services. Slowly I am moving into a primary administra
-
Security with Windows on an iMac OS X10.4
If I load Windows XP on my iMac, am I going to run into the same horrific security issues I had with Windows? The reason I went to a Mac was to get rid of all the viruses, etc. Also, do I need a special version of XP for the Mac or just load the soft
-
Where would i get the little screws online for the bottom of my mac?
i sent my mac to get fixed buy apple over a year ago now most of the screws have come out the bottom and ive lost them? he probly didnt screw them in tight enuff? does anybody know where i can order some online with a little screw driver to?
-
Good Day. I am having some doubts regarding SAP Certification. Can U help me.. 01. What are the minimum no of examinations required to clear to get the certificate I wish to go for SABE201, SABE301, SABE 401u2026?? Or else I have to clear SABE5