Prepare to export ABAP

Hi ALL
Now i try to prepare to export ABAP useing SAPinst,but it's a error
we paltform:
ECC6 SR3 with EPH3
Oracle 10.2.0.4
HP-UX 11i 31
TRACE 2010-10-14 17:29:31.630
Function setMessageIdOfExceptionMessage: nw.processError
ERROR 2010-10-14 17:29:31.630
 CJSlibModule::writeError_impl()
CJS-30023 Process call '/usr/sap/QAS/SYS/exe/run/R3ldctl -p /usr/sap/export/ABAP/DATA -l R3ldctlExp
ort.log' exits with error code 2. For details see log file(s) R3ldctlExport.log.
TRACE 2010-10-14 17:29:31.630 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
TRACE 2010-10-14 17:29:31.670 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 8964
ERROR 2010-10-14 17:29:31.720 [sixxcstepexecute.cpp:951]
FCO-00011 The step runR3ldctl with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_ABAP_Prepare_
Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Prepare_Export|ind|ind|ind|ind|0|0|runR3ldctl was executed
with status ERROR .
TRACE 2010-10-14 17:29:31.740 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP ERP 6.0 Support Rele
ase 3 > Software Life-Cycle Options > System Copy > Oracle > Source System Export > Central System >
Based on AS ABAP > Export Preparation. You may now <ul> <li> choose Retry to repeat the
current step. </li> <li> choose View Log to get more information about the error. </li> <li>
stop the task and continue with it later. </li> </ul> Log files are written to /install_tmp/sap
inst_instdir/ERP/LM/COPY/ORA/EXP/CENTRAL/AS-ABAP/PREEXP. </body></html>
TRACE 2010-10-14 17:29:31.740 [iaxxgenimp.cpp:1255]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
R3ldctlExport.log
(IDL) Info: ddldb2lib version is 700.20
(CLL) Info: creating initial tpl data
DbSl Trace: invalid DBSL data type: DBSL_DATA_SHORT_CHAR
ERROR: Select for get_version failed
(IDL) Info: ddldb2lib version is 700.20
(CLL) Info: creating initial tpl data
DbSl Trace: invalid DBSL data type: DBSL_DATA_SHORT_CHAR
ERROR: Select for get_version failed

> ECC6 SR3 with EPH3
> Oracle 10.2.0.4
> HP-UX 11i 31
> R3ldctlExport.log
It seems you patched your R3ldctl with the wrong one, you use the R3ldctl for DB2 instead for Oracle.
Markus

Similar Messages

EXPORT ABAP ERROR (BEK) ERROR: SAPSYSTEMNAME not in environment

HI ALL,
we have started migration of ecc6.0 from windows (mssql) to linux(maxdb). While taking export abap all the export packages are ended with same error . i have set the envirornment variables for jdk. even though i am getting the same error.here i paste the log
Unloading of 'TODIR' export package: ERROR
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled May 3 2010 23:35:53
E:\usr\sap\DE5\SYS\exe\run\R3load.exe -e TODIR.cmd -datacodepage 4103 -l TODIR.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(GSI) INFO: dbname = "DE5MEXICO "
(GSI) INFO: vname = "MSSQL "
(GSI) INFO: hostname = "MEXICO "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "MEXICO"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "2x Intel 80686 (Mod 23 Step 8)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: job finished with 1 error(s)
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: END OF LOG: 20110510080946
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: START OF LOG: 20110510081801
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled May 3 2010 23:35:53
E:\usr\sap\DE5\SYS\exe\run\R3load.exe -e TODIR.cmd -datacodepage 4103 -l TODIR.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(RD) ERROR: unexpected end of file "F:\mexico_latest_export\ABAP\DATA\TODIR.TOC"
(WTF) INFO: expected error, don't panic ...
(GSI) INFO: dbname = "DE5MEXICO "
(GSI) INFO: vname = "MSSQL "
(GSI) INFO: hostname = "MEXICO "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "MEXICO"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "2x Intel 80686 (Mod 23 Step 8)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: job finished with 1 error(s)
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: END OF LOG: 20110510081801
this is export_monitor log
Export Monitor jobs: running 0, waiting 5, completed 2, failed 44, total 51.
Export Monitor jobs: running 1, waiting 4, completed 2, failed 44, total 51.
Export Monitor jobs: running 2, waiting 3, completed 2, failed 44, total 51.
Export Monitor jobs: running 3, waiting 2, completed 2, failed 44, total 51.
Export Monitor jobs: running 4, waiting 1, completed 2, failed 44, total 51.
Unloading of 'SCPRVALS' export package: ERROR
Export Monitor jobs: running 3, waiting 1, completed 2, failed 45, total 51.
Unloading of 'SCPRSVALS' export package: ERROR
Export Monitor jobs: running 2, waiting 1, completed 2, failed 46, total 51.
Unloading of 'SAPUSER' export package: ERROR
Export Monitor jobs: running 1, waiting 1, completed 2, failed 47, total 51.
Unloading of 'SAPUSER1' export package: ERROR
Export Monitor jobs: running 0, waiting 1, completed 2, failed 48, total 51.
Export Monitor jobs: running 1, waiting 0, completed 2, failed 48, total 51.
Unloading of 'TODIR' export package: ERROR
Export Monitor jobs: running 0, waiting 0, completed 2, failed 49, total 51.
TRACE 2011-05-10 08:18:31.884
2011-05-10 08:18:31.884 FSPath(C:\j2sdk1.4.2_16\bin\java.exe) done
TRACE 2011-05-10 08:18:31.884
2011-05-10 08:18:31.884 ChildApplication(C:\j2sdk1.4.2_16\bin\java.exe).run(): 103. done.
TRACE 2011-05-10 08:18:31.884
2011-05-10 08:18:31.884 Java.run() done: 103
TRACE 2011-05-10 08:18:31.884
2011-05-10 08:18:31.884 FSPath(C:\j2sdk1.4.2_16\bin\java.exe) done
TRACE 2011-05-10 08:18:31.884
2011-05-10 08:18:31.884 ChildApplication(C:\j2sdk1.4.2_16\bin\java.exe).runAs() done
TRACE 2011-05-10 08:18:31.884
Function setMessageIdOfExceptionMessage: nw.programError
ERROR 2011-05-10 08:18:31.884
 CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.
TRACE 2011-05-10 08:18:31.884 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2011-05-10 08:18:31.900 [sixxcstepexecute.cpp:951]
FCO-00011 The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.).
TRACE 2011-05-10 08:18:31.900 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP ERP 6.0 Support Release 3 > Software Life-Cycle Options > System Copy > MS SQL Server > Source System Export > Central System > Based on AS ABAP > Database Instance Export( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.). You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/ERP/LM/COPY/MSS/EXP/CENTRAL/AS-ABAP/EXP. </body></html>
TRACE 2011-05-10 08:18:31.900 [iaxxgenimp.cpp:1255]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
can any one please help me thanks in advance
Vardhan!

Sorry for the above paste,
HI ALL, we have started migration of ecc6.0 from windows (mssql) to linux(maxdb). While taking export abap all the export packages are ended with same error . i have set the envirornment variables for jdk. even though i am getting the same error.here i paste the log Unloading of 'TODIR' export package:
ERROR E:\usr\sap\DE5\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP E:\usr\sap\DE5\SYS\exe\run\R3load.exe: version R7.00/V1.4 [UNICODE] Compiled May 3 2010 23:35:53 E:\usr\sap\DE5\SYS\exe\run\R3load.exe -e TODIR.cmd -datacodepage 4103 -l TODIR.log -stop_on_error (DB)
INFO: connected to DB (DB) INFO: Export without hintfile (GSI)
INFO: dbname = "DE5MEXICO " (GSI) INFO: vname = "MSSQL " (GSI)
INFO: hostname = "MEXICO " (GSI) INFO: sysname = "Windows NT" (GSI)
INFO: nodename = "MEXICO" (GSI)
INFO: release = "5.2" (GSI)
INFO: version = "3790 Service Pack 2" (GSI)
INFO: machine = "2x Intel 80686 (Mod 23 Step 8)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
E:\usr\sap\DE5\SYS\exe\run\R3load.exe: job finished with 1 error(s) E:\usr\sap\DE5\SYS\exe\run\R3load.exe: END OF LOG: 20110510080946 E:\usr\sap\DE5\SYS\exe\run\R3load.exe:
START OF LOG: 20110510081801 E:\usr\sap\DE5\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP E:\usr\sap\DE5\SYS\exe\run\R3load.
exe: version R7.00/V1.4 [UNICODE] Compiled May 3 2010 23:35:53 E:\usr\sap\DE5\SYS\exe\run\R3load.exe -e TODIR.cmd -datacodepage 4103 -l TODIR.log -stop_on_error (DB) INFO: connected to DB (DB)
INFO: Export without hintfile (RD)
ERROR: unexpected end of file "F:\mexico_latest_export\ABAP\DATA\TODIR.TOC" (WTF)
INFO: expected error, don't panic ... (GSI)
INFO: dbname = "DE5MEXICO " (GSI)
INFO: vname = "MSSQL " (GSI)
INFO: hostname = "MEXICO " (GSI)
INFO: sysname = "Windows NT" (GSI)
INFO: nodename = "MEXICO" (GSI)
INFO: release = "5.2" (GSI)
INFO: version = "3790 Service Pack 2" (GSI)
INFO: machine = "2x Intel 80686 (Mod 23 Step 8)"
(BEK) ERROR: SAPSYSTEMNAME not in environment E:\usr\sap\DE5\SYS\exe\run\R3load.exe: job finished with 1 error(s) E:\usr\sap\DE5\SYS\exe\run\R3load.exe: END OF LOG: 2011051008
Can any help me in solving the above error
Thanks in advance
Vardhan!

Error when exporting ABAP Programs and the Project

Hi All,
I keep on getting the following errors when I'm exporting the entire Project or only ABAP Programs (see attached screenshots).
- Screenshot 1 shows an error when exporting a Project.
- Screenshot 2 shows an error when exporting ABAP Program(s).
These errors occur in the DEV environment.
Please help.
Thank you all.
Kind regards,
Roli

Hi Ramakrishna,
I will send the log file for when exporting a project. However, the issue of exporting ABAP Programs is nor resolved.
In CMC we had to configure the system to Generate ABAP = True.
Thank you.
Kind regards,
Roli

Java Export ( ABAP+JAVA) BI 7.0

Could someone please help me to understand ..
1 . Purpose of java export
2 . Should we take java export immediately after database backup (ABAP) completes . how these two ( ABAP+Java) , how they are interrelated .
3. If database backup ( ABAP) fails for a given day , then is it fruitful to take java export of that particular day .
Thanks

Hi,
1. Purpose of java export
Because complete recovery of java system can only be possible with file ssytem recovery.
2 . Should we take java export immediately after database backup (ABAP) completes . how these two ( ABAP+Java) , how they are interrelated .
Yes
3. If database backup ( ABAP) fails for a given day , then is it fruitful to take java export of that particular day .
Nope it will not help you to recover the ssytem.
Regards,
Vamshi.

Export ABAP proxy as wsdl file

Hi,
Does anyone know how to export the abap proxy into a wsdl file in R3?

Hi,
in SPROXY, open the proxy and choose Goto=>Display WSDL
Best regards,
Markus

Error while exporting ABAP programs for transport

Hi,
In the process of exporting my abap programs so that they can be transported, I released my work request.
However, during release, errors were encountered, and the status of the release was set to 'Release Started'.
The error encountered was
'[STOP ICON] ===> HALT: rscpi_init fails with rc = 1 (twconv. c:957) Please contact the SAP support.'
Can anyone help? Thanks.

check all the objects used in ur report are in same package
Edited by: BrightSide on May 14, 2008 3:53 PM

Export ABAP List to Excel and send it as email attachment

Hi,
I have a program that sends email to employees, using SAP Office, this email sends an attachment in html (an abap lisp exported to html). To create this attachment I use LIST_FROM_MEMORY to recover data and then WWW_HTML_FROM_LISTOBJECT to create the html file.
Then the email is sent using SO_NEW_DOCUMENT_ATT_SEND_API1 and it works fine. But now I need to send this ABAP List as an Excel instead of sending as a HTML file.
How can I do this? Is this possible?
Thanks in advance
Best regards
P.S: I've tried to recover information from ABAP List as an ASCII file (using LIST_TO_ASCII instead of WWW_HTML_FROM_LISTOBJECT) and then sending the file as an XLS instead of HTM (this is determined in PACKING_LIST parameter of SO_NEW_DOCUMENT_ATT_SEND_API1), but when I open the excel file, all information is stored in the first cell, so you cannot perform any operation on it.

Hi,
Please refer to the link below :
http://www.sapdev.co.uk/reporting/rep_spooltopdf.htm
or
http://www.sapdev.co.uk/reporting/email/attach_xls.htm
Thanks,
Sriram Ponna.

Export ABAP only from BI ABAP-JAVA system

Hi All,
We have several problems with an BI 7.0 system.
on this system is ABAP and BI JAVA installed.
is it possible to export the ABAP part ONLY and use this for a new installation ??
Thisnew installation must include ABAP and BI JAVA.
are there some notes for it?? and is this supported by SAP??
Thanks,

Hi,
Yes this is possible. Under the link http://service.sap.com/instguides follow to the system copy part and there you get the documents pertaining to the export of only ABAP part from the dual stack.
It should be possible for you take it up from there on.
regards and do reward if helpful

Export ABAP Classes to File

How can I export an ABAP class to file? After exporting how can I import an ABAP class from file?
Thanks
Rene

Hello,
I have the same problem: export and import ABAP classes.
You said to check out the CL_OO_* classes but I did not
find a method to export or import classes to or from file.
I really would be thankful when you could give me a more specific answer.
Regards,
Alex

System Copy - ABAP export using R/3 load -- RSCP ERROR: Altername NameTab

Hi all,
I am trying to export BW3.5 system using sapinst (R/3 load method). In the phase of executing export jobs , I am getting the error in SAPSSEXC.log by mentioning it as altername too old.
The log files are below.
RSCP ERROR: Altername NameTab too old
E:\usr\sap\BWA\SYS\exe\run/R3load.exe: START OF LOG: 20090209061745
E:\usr\sap\BWA\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#22 $ SAP
E:\usr\sap\BWA\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]
Compiled Feb 19 2008 23:17:57
E:\usr\sap\BWA\SYS\exe\run/R3load.exe -datacodepage 1100 -e C:\Program Files\sapinst_instdir\NW04\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.cmd -l C:\Program Files\sapinst_instdir\NW04\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log -loadprocedure fast
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "hsotname                                                                                "
(GSI) INFO: vname    = "MSSQL                           "
(GSI) INFO: hostname = "hostname                                                  "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "hostname"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 16 (Mod 2 Step 3)"
(GSI) INFO: instno   = "0020239136"
(NT) Error: DOKCLU: normal NameTab from 20041108162211 younger than alternate NameTab from 20010201171049!
(SYSLOG) INFO: k CQF : DOKCLU&20010201171049&20041108162211&                rscpgdio 47
(RSCP) ERROR: -
3-
(RSCP) ERROR: code:   64 RSCPECALL
(RSCP) ERROR: Altername NameTab too old
(RSCP) ERROR: module: rscpgdio location:   47 line: 2964
(RSCP) ERROR: TSL01: CQF p3: DOKCLU&20010201171049&20041108162211&
(RSCP) ERROR: -
myCluster (55.18.Exp): 897: received return code 64 from rscpCheckNTTimeStamps.
myCluster (55.18.Exp): 898: suspicious create timestamp of alternate nametab encountered.
myCluster (55.18.Exp): 902: create timestamps of nametab: 20041108162211; alternate nametab: 20010201171049.
myCluster (55.18.Exp): 294: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
E:\usr\sap\BWA\SYS\exe\run/R3load.exe: job finished with 1 error(s)
E:\usr\sap\BWA\SYS\exe\run/R3load.exe: END OF LOG: 20090209061749
Then I have followed the note and i have modified the environment variable with the value
I18N_IGNORE_ABAP_FEATURE = 20080303_N1148541
Kindly advice me on the same.Please give all your suggestions to ovecome from this error.
System Environments
SAP : BW 3.5
Database: MSSql 2005
OS: 64 Bit Ms Windows 2003 server
Regards
Vijay

Dear,
Please check your Database is connected or not ,this is very critical error in the database.
please go through the SAP notes 738858 and 978244.
Warm Regards.
Mohammed Hassan Naveed

PREPARE for Java complains of wrong OS though it is correct for ABAP

Hello Team
I am in the process of upgrading our CRM 5.0 Unicode (Dual Stack -
ABAPJAVA) systems to CRM 2007 Unicode (Dual Stack - ABAPJAVA) system
on a LINUX X84_64 Operating System env.
I am having issues when I start the JPREPARE from the SAP CRM 2007
Upgrade Master DVD on Linux_X86_64 (51033255_19) for the first time as
mentioned in the CRM 2007 Java Upgrade guide. It complains of SAPCAR
file missing and it says OS Linux not supported by this CD.
This is the command I am using - JPREPARE <upgrade directory> from
the Upgrade Master mount point
This is the exact error message I get:- ERROR: Missing
file /sapcd/CRM60_Upg/51033255_19/LINUX_X86_64/SAPCAR. Operating system
Linux not supported by this CD.
where /sapcd/CRM60_Upg/51033255_19/ is the mount point for the SAP CRM
2007 Upgrade Master DVD on Linux_X86_64 (51033255_19)
The upgrade directory is created correctly with
755 permissions and owned by <sid>adm
All it does is it creates a empty exe directory in the upgrade
directory and throws the above mentioned error.
Where as I was able to launch the PREPARE for ABAP succesfully from the
same CRM 2007 Upgrade Master DVD on Linux_X86_64 (51033255_19)
I am in the middle of the PREPARE phase for ABAP and it wanted me to
start the JAVA Prepare phase. I am surprised by this as it did not
throw an error when I started the PREPARE phase for ABAP.
I am stuck with this error and unable to move forward. Can you please
let me know how do I proceed.
Has anyone faced this problem before or am I doing anything wrong here?
Thank you!

I was able to get over this by using the DVD - SAP CRM 2007 Java Upgrade for all OS -(51033255_25) upgrade Master DVD.
Thanks!

System copy errors during ABAP export ECC 5.0

Hi
I'm need to do system system copy for our ECC 5.0 system on Win/ora platform. I have followed the system copy document from SMP. I'm getting the below error while exporting the ABAP schema. Could someone guide me on how to fix this.
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPCLUST.log
=======================
(NT) Error: AABLG: normal NameTab from 20050112230750 younger than alternate NameTab from 20000323230317!
(SYSLOG) INFO: k CQF : AABLG&20000323230317&20050112230750&                 rscpgdio 47
(RSCP) ERROR: -
3-
(RSCP) ERROR: code:   64 RSCPECALL
(RSCP) ERROR: Altername NameTab too old
(RSCP) ERROR: module: rscpgdio location:   47 line: 3007
(RSCP) ERROR: TSL01: CQF p3: AABLG&20000323230317&20050112230750&
(RSCP) ERROR: -
myCluster (55.20.Exp): 924: received return code 64 from rscpCheckNTTimeStamps.
myCluster (55.20.Exp): 925: suspicious create timestamp of alternate nametab encountered.
myCluster (55.20.Exp): 929: create timestamps of nametab: 20050112230750; alternate nametab: 20000323230317.
myCluster (55.20.Exp): 299: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
======================
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPPOOL.log
===========================
(NT) Error: AT01: normal NameTab from 20050112234859 younger than alternate NameTab from 20011002204708!
(SYSLOG) INFO: k CQF : AT01&20011002204708&20050112234859&                  rscpgdio 47
(CNVPOOL) Altername NameTab too old AT01&20011002204708&20050112234859&   Abort.
(CNVPOOL) conversion failed for row 0 of table VARKEY = 010100
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: environemnt variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
=========================
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log
===========================
(NT) Error: DOKCLU: normal NameTab from 20050112230750 younger than alternate NameTab from 20000323224119!
(SYSLOG) INFO: k CQF : DOKCLU&20000323224119&20050112230750&                rscpgdio 47
(RSCP) ERROR: -
3-
(RSCP) ERROR: code:   64 RSCPECALL
(RSCP) ERROR: Altername NameTab too old
(RSCP) ERROR: module: rscpgdio location:   47 line: 3007
(RSCP) ERROR: TSL01: CQF p3: DOKCLU&20000323224119&20050112230750&
(RSCP) ERROR: -
myCluster (55.20.Exp): 924: received return code 64 from rscpCheckNTTimeStamps.
myCluster (55.20.Exp): 925: suspicious create timestamp of alternate nametab encountered.
myCluster (55.20.Exp): 929: create timestamps of nametab: 20050112230750; alternate nametab: 20000323224119.
myCluster (55.20.Exp): 299: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
========================
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSDIC.log
========================
(EXP) INFO: check for inactive NameTab entries: Ok.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
=======================
Thanks & Regards
Jagan

C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPCLUST.log
C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPPOOL.log
C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log
C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSDIC.log
paste the above logs here.
Thanks
SM

Export database

Good evening friends, I am having an error when you export from my base that is 70GB, giving this error sapappl1_1, ran the reports and SMIGR_CREATE_DDL SAP_DROP_TMPTABLES, which can be.
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Export Monitor jobs: running 1, waiting 35, completed 0, failed 0, total 36.
Export Monitor jobs: running 2, waiting 34, completed 0, failed 0, total 36.
Export Monitor jobs: running 3, waiting 33, completed 0, failed 0, total 36.
Export Monitor jobs: running 3, waiting 32, completed 1, failed 0, total 36.
Export Monitor jobs: running 3, waiting 31, completed 2, failed 0, total 36.
Unloading of 'BALDAT' export package: OK
Export Monitor jobs: running 2, waiting 31, completed 3, failed 0, total 36.
Export Monitor jobs: running 3, waiting 30, completed 3, failed 0, total 36.
Unloading of 'D010INC' export package: OK
Export Monitor jobs: running 2, waiting 30, completed 4, failed 0, total 36.
Export Monitor jobs: running 3, waiting 29, completed 4, failed 0, total 36.
Unloading of 'DD03L' export package: OK
Export Monitor jobs: running 2, waiting 29, completed 5, failed 0, total 36.
Export Monitor jobs: running 3, waiting 28, completed 5, failed 0, total 36.
Unloading of 'DDPRS' export package: OK
Export Monitor jobs: running 2, waiting 28, completed 6, failed 0, total 36.
Export Monitor jobs: running 3, waiting 27, completed 6, failed 0, total 36.
Unloading of 'D010TAB' export package: OK
Export Monitor jobs: running 2, waiting 27, completed 7, failed 0, total 36.
Export Monitor jobs: running 3, waiting 26, completed 7, failed 0, total 36.
Unloading of 'DOKCLU' export package: OK
Export Monitor jobs: running 2, waiting 26, completed 8, failed 0, total 36.
Unloading of 'OCSCMPLOBJ' export package: OK
Export Monitor jobs: running 1, waiting 26, completed 9, failed 0, total 36.
Export Monitor jobs: running 2, waiting 25, completed 9, failed 0, total 36.
Export Monitor jobs: running 3, waiting 24, completed 9, failed 0, total 36.
Unloading of 'SAPAPPL0_1' export package: OK
Export Monitor jobs: running 2, waiting 24, completed 10, failed 0, total 36.
Export Monitor jobs: running 3, waiting 23, completed 10, failed 0, total 36.
Unloading of 'DYNPSOURCE' export package: OK
Export Monitor jobs: running 2, waiting 23, completed 11, failed 0, total 36.
Export Monitor jobs: running 3, waiting 22, completed 11, failed 0, total 36.
Unloading of 'REPOSRC' export package: OK
Export Monitor jobs: running 2, waiting 22, completed 12, failed 0, total 36.
Export Monitor jobs: running 3, waiting 21, completed 12, failed 0, total 36.
Unloading of 'SAPAPPL1_2' export package: OK
Export Monitor jobs: running 2, waiting 21, completed 13, failed 0, total 36.
Export Monitor jobs: running 3, waiting 20, completed 13, failed 0, total 36.
Unloading of 'SAPAPPL1_3' export package: OK
Export Monitor jobs: running 2, waiting 20, completed 14, failed 0, total 36.
Export Monitor jobs: running 3, waiting 19, completed 14, failed 0, total 36.
Unloading of 'SAPAPPL0_2' export package: OK
Export Monitor jobs: running 2, waiting 19, completed 15, failed 0, total 36.
Export Monitor jobs: running 3, waiting 18, completed 15, failed 0, total 36.
Unloading of 'SAPAPPL2_2' export package: OK
Export Monitor jobs: running 2, waiting 18, completed 16, failed 0, total 36.
Export Monitor jobs: running 3, waiting 17, completed 16, failed 0, total 36.
Unloading of 'SAPCLUST' export package: OK
Export Monitor jobs: running 2, waiting 17, completed 17, failed 0, total 36.
Export Monitor jobs: running 3, waiting 16, completed 17, failed 0, total 36.
Unloading of 'SAPAPPL2_1' export package: OK
Export Monitor jobs: running 2, waiting 16, completed 18, failed 0, total 36.
Export Monitor jobs: running 3, waiting 15, completed 18, failed 0, total 36.
Unloading of 'SAPDDIM' export package: OK
Export Monitor jobs: running 2, waiting 15, completed 19, failed 0, total 36.
Export Monitor jobs: running 3, waiting 14, completed 19, failed 0, total 36.
Unloading of 'SAPDFACT' export package: OK
Export Monitor jobs: running 2, waiting 14, completed 20, failed 0, total 36.
Export Monitor jobs: running 3, waiting 13, completed 20, failed 0, total 36.
Unloading of 'SAPDODS' export package: OK
Export Monitor jobs: running 2, waiting 13, completed 21, failed 0, total 36.
Export Monitor jobs: running 3, waiting 12, completed 21, failed 0, total 36.
Unloading of 'SAPPOOL' export package: OK
Export Monitor jobs: running 2, waiting 12, completed 22, failed 0, total 36.
Export Monitor jobs: running 3, waiting 11, completed 22, failed 0, total 36.
Unloading of 'SAPNTAB' export package: OK
Export Monitor jobs: running 2, waiting 11, completed 23, failed 0, total 36.
Export Monitor jobs: running 3, waiting 10, completed 23, failed 0, total 36.
Unloading of 'SAPSDOCU' export package: OK
Export Monitor jobs: running 2, waiting 10, completed 24, failed 0, total 36.
Unloading of 'SAPSDIC' export package: OK
Export Monitor jobs: running 1, waiting 10, completed 25, failed 0, total 36.
Export Monitor jobs: running 2, waiting 9, completed 25, failed 0, total 36.
Export Monitor jobs: running 3, waiting 8, completed 25, failed 0, total 36.
Unloading of 'SAPSLOAD' export package: OK
Export Monitor jobs: running 2, waiting 8, completed 26, failed 0, total 36.
Export Monitor jobs: running 3, waiting 7, completed 26, failed 0, total 36.
Unloading of 'SAPSPROT' export package: OK
Export Monitor jobs: running 2, waiting 7, completed 27, failed 0, total 36.
Export Monitor jobs: running 3, waiting 6, completed 27, failed 0, total 36.
Unloading of 'SAPSLEXC' export package: OK
Export Monitor jobs: running 2, waiting 6, completed 28, failed 0, total 36.
Export Monitor jobs: running 3, waiting 5, completed 28, failed 0, total 36.
Unloading of 'SAPSSEXC_1' export package: OK
Export Monitor jobs: running 2, waiting 5, completed 29, failed 0, total 36.
Export Monitor jobs: running 3, waiting 4, completed 29, failed 0, total 36.
Unloading of 'SAPSSEXC_3' export package: OK
Export Monitor jobs: running 2, waiting 4, completed 30, failed 0, total 36.
Export Monitor jobs: running 3, waiting 3, completed 30, failed 0, total 36.
Unloading of 'SAPSSRC' export package: OK
Export Monitor jobs: running 2, waiting 3, completed 31, failed 0, total 36.
Export Monitor jobs: running 3, waiting 2, completed 31, failed 0, total 36.
Unloading of 'SAPUSER' export package: OK
Export Monitor jobs: running 2, waiting 2, completed 32, failed 0, total 36.
Export Monitor jobs: running 3, waiting 1, completed 32, failed 0, total 36.
Unloading of 'SAPUSER1' export package: OK
Export Monitor jobs: running 2, waiting 1, completed 33, failed 0, total 36.
Export Monitor jobs: running 3, waiting 0, completed 33, failed 0, total 36.
Unloading of 'SAPSSEXC_2' export package: OK
Export Monitor jobs: running 2, waiting 0, completed 34, failed 0, total 36.
Unloading of 'UJF_DOC' export package: OK
Export Monitor jobs: running 1, waiting 0, completed 35, failed 0, total 36.
Unloading of 'SAPAPPL1_1' export package: ERROR
Export Monitor jobs: running 0, waiting 0, completed 35, failed 1, total 36.

Hi Sunny, thank you for your help tracking log
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110627232455
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#7 $ SAP
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Aug 11 2009 00:02:15
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe -ctf E E:\usr\sap\export\ABAP\DATA\SAPAPPL1_1.STR E:\usr\sap\export\ABAP\DB\DDLMSS.TPL SAPAPPL1_1.TSK MSS -l SAPAPPL1_1.log
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: job completed
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110627232455
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110627232456
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#7 $ SAP
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Aug 11 2009 00:02:15
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL1_1.cmd -datacodepage 4103 -l SAPAPPL1_1.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(GSI) INFO: dbname   = "NWTFINITY-SAP                                                                                "
(GSI) INFO: vname    = "MSSQL                           "
(GSI) INFO: hostname = "FINITY-SAP                                                      "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "FINITY-SAP"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "8x AMD64 Level 6 (Mod 15 Step 11)"
(GSI) INFO: instno   = "INITIAL   "
(EXP) TABLE: "/1CPMB/B_IDD1RM4" #20110627232501
(EXP) ERROR: DbSlPrepare/BegRead failed
rc = 103, table "/1CPMB/XGJT6VMAS"
(SQL error 208)
error message returned by DbSl:
Invalid object name '/1CPMB/XGJT6VMAS'.
Statement(s) could not be prepared.
(DB) INFO: disconnected from DB
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
E:\usr\sap\NWT\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110627235407

System copy NW04S ABAP+Java same host

Hi All
I have this dev system ECC 6.0 (SAP_SID and DB_SID: D01) ABAPJava system and enterprise portal 7.0 (SAP_SID and DB_SID: P01) on the same host (hostname: host1). Now I need to do a system copy of the D01 ABAPJava system to build new system D02 on the same host - host1. Its Oracle 10g/Solaris 10.
My understanding is, after all preparations, to run sapinst with the 'database-independent procedure' to export ABAP+Java at the same time, which creates the Migration Export CD image. Does anyone know of any issues with system copies on the same host? I think I dont need to install Oracle software as its already there, right? I need to get the oracle and sap directories created for the new system D02, please correct me.
Thanks
Ali

Hi,
My understand was have the same installation of ABAP+JAVA ( UR CASE) which will install oracle and everything else auto...and lauch sapinst >> system copy >> then export to anyfolder, move that folder to target system. In target system, launch sapinst >> system copy>> and import.
Thanks,
Feel free to revert back.

Database update statistic failed during Export phase

NW2004s system with Oracle 10G on windows 2003 server and clustered enviornment.
During System copy ,when it is checking uodated statistic ,it is giving the follwoing error.
BR0301E SQL error -20000 in thread 4 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPDAT"', TABNAME => '"/BIC/FZPCA_CLI"', ESTIMATE_PERCENT => 10, METHOD_OPT => 'FOR COLUMNS SIZE 225 "KEY_ZPCA_CLIP" FOR COLUMN
ORA-20000: index "SAPDAT"."/BIC/FZPCA_CLI~010" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 13159
ORA-06512: at "SYS.DBMS_STATS", line 13179
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPDAT./BIC/FZPCA_CLI

Now I have started EXPORT Preparation phase.System is up and running .Getting the following error.
ERROR 2007-12-05 09:04:53
CJS-30023 Process call '
sapbwqgui4\sapmnt\BWQ\SYS\exe\uc\NTAMD64\R3ldctl.exe -p F:\Export\ABAP\DATA -l R3ldctlExport.log' exits with error code 2. For details see log file(s) R3ldctlExport.log.
ERROR 2007-12-05 09:04:53
FCO-00011 The step runR3ldctl with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_ABAP_Prepare_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Prepare_Export|ind|ind|ind|ind|0|0|runR3ldctl was executed with status ERROR .
R3ldctlExport.log'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1017
DbSl Trace: CONNECT failed with sql error '1017'
ERROR: DbSlConnect rc= 99
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1017
DbSl Trace: CONNECT failed with sql error '1017'

Prepare to export ABAP

Similar Messages

Maybe you are looking for