R3trans import
Does a R3trans import of a table perform and append or an insert?
While I was performing a R3trans import of a table, my database ran out of space and the process stopped. I need to restart the process, but I do not want duplicate records in the table. If R3trans uses insert I won't have duplicate records
Hello Bondy,
R3trans Export and Import of tables:-
During Export of tables,R3trans will call the control file which is mentioned in the command line
"R3trans -w log file export control file"
Delete statements mentioned in export control file are not sql statements. Its only active while doing import.
• While exporting these delete statements get added in the created dump file
• While importing it will delete the contents of respective tables and then import
For more details - export control file of R3trans SAPnote 130906 - How can versions be transported?
For more details on R3trans export and Import Sap Note:1942
So in your case,check whether you have used delete statements in your export control file.
If delete statements are present in export control file,while importing it will first delete the current entries of table and then import.
If delete statements are not present, the entries will get appended.
Hope you got some information
Thanks,
Needu
Similar Messages
-
Exporting and importing table using R3trans program between 2 clients
Hi,
How to export and import a table between to clients in a same system using R3trans program?
I need to copy a table from Client 020 in a system to client 040 of the same system using R3 trans. I need to know the procedure.
Can any one advice
Regards,
SureshThis is how you do a export and import of table entries.
Export:
Open Notepad and type the following,
export
client = 020
file = 'clone.export.<sid>.<client no>.data'
select * from <client_dependent_tablename1>
select * from <client_dependent_tablename2>
select * from <client_dependent_tablenamen>
Save the file as export.ctl
Run R3trans export.ctl
and the data of these files will be stored in a file called clone.export.<sid>.data in the directory from which you have called R3trans
Import:
Open Notepad,
import
client = 040
file = clone.export.<sid>.<client no>.data
buffersync = yes
Save the file as import.ctl
Run R3trans import.ctl
Cheers!
Bidwan
Message was edited by:
Bidwan Baruah -
Transport classes and programs to another server
Except for transport routing and charm copy function, do we have other ways to do so?
for example copy or so forth.
best regards,
Blake LeHi Blake
SAP R/3 Correction and Transport System
Operating 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 . 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. These 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. 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: holds action log files. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
1 ETK220 u201C==================================================u201D u201C=================
=============================
1 ETK191 u201C04/30/1998u2033 Action log for request/task: u201CDEVK902690u2033
1 ETK220 u201C==================================================u201D u201C=================
=============================
1 ETK185 u201C04/30/1998 18:02:32u2033 u201CMOHASX01u2033 has reincluded the request/task
4 EPU120 Timeu2026 u201C18:02:32u2033 Run timeu2026 u201C00:00:00u2033
1 ETK193 u201C04/30/1998 18:02:33u2033 u201CMOHASX01u2033 owner, linked by u201CMOHASX01u2033 to u201CDEVK902691u2033
4 EPU120 Timeu2026 u201C18:02:33u2033 Run timeu2026 u201C00:00:00u2033
1 ETK190 u201C05/04/1998 11:02:40u2033 u201CMOHASX01u2033 has locked and released the request/task
1 ETK194 u201C05/04/1998 11:02:40u2033 **************** End of log *******************
4 EPU120 Timeu2026 u201C11:02:40u2033 Run timeu2026 u201C00:00:09u2033
~
~u201DDEVZ902690.DEVu201D 10 lines, 783 characters
/usr/sap/trans/buffer: transport buffer of the target systems; 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. 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 u201CConfiguring the CTS systemu201D 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 u201Cr3transpathu201D 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 u201C\u201D-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,u2026.).
$(mday): Used for the day of the current month (01-31).
$(mname): Used for the name of the month (JANu2026DEC).
$(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 u201Cdbnameu201D and u201Cdbhostu201D 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 u201Cdbnameu201D and u201Cdbhostu201D 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 : u201C/informix/<SAPSID>u201D is the default value. Defines the directory namewhere the database software can be found.
INFORMIXSQLHOSTS: u201C$(informixdir)/etc/sqlhosts[.tli|.soc]u201Cis default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
INFORMIX_SERVER: u201C$(dbhost)$(dbname)shmu201D is the default value. The name of the database server may be specified for a local connect.
INFORMIX_SERVERALIAS: u201C$(dbhost)$(dbname)tcpu201Dis the default vlue. The name of the database server can be specified for a remote connect.
For Microsoft SQL Server database the two parameters u201Cdbnameu201D and u201Cdbhostu201D 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 u201Cdbhostu201D is required.
DBHOST: System name of the host on which the database is running.
If theu201DOptiConnectu201D is used, the following line should be specified:
OPTICONNECT 1
For DB2/ AIX
The two parameters u201Cdbnameu201D and u201Cdbhostu201D 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: u201CALOGu201D $(syear) $(yweek)u201Dis 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: u201CSLOG $(syear) $(yweek).$(system)u201D 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 u201Cimportu201D or u201Cputu201D 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 u201CSYNCMARKu201D 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 u201Cin Orderu201D. Change requests that were not processed successfully stay in the buffer.
NEW_SAPNAMES: Default value is u201CFALSEu201D. A file is created for each user of the R/3 System group in the u201Csapnamesu201D 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 u2018Start and Stopu2019 command files and database in R/3 the following important parameters are specified in TPPARAM:
Parameters for the tp Function u201CPUTu201D: LOCK_EU (boolean) default value is u201CTRUEu201D. 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 u201Ctp putu201D is used, it changes the system change option . If the parameter is set to u201CFALSEu201D nothing gets changed. If the parameter is set to u201CTRUEu201D, the system change option is set to u201CObjects cannot be changedu201D at the beginning of the call, and gets changed back to its previous value at the end of the call. The u201Ctp putu201D command will give the exact status of the locking mechanism.
LOCKUSER (used as boolean value): Default value is u201CTRUEu201D. This parameter is about the user login while tp put call is executed. If this parameter is set to u201CFALSEu201D, no locking mechanism for the users takes affect. If this parameter is defined as u201CTRUEu201D 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 u201D u201C.or u201CPROMPTu201D 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 u201D u201Cor u201CPROMPTu201D for Windows NT. TP uses this parameter to stop an R/3 System.
STARTDB: Default value is u201D u201C. 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 u201D u201C. 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 u201CCLEAROLDu201D
DATALIFETIME (Numeric): Default value is u201C200u2033. 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 u201C365u2033. 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 u201C365u2033. This parameter is used just like DATALIFETIME parameter.
LOGLIFETIME (Numeric): Default value is u201C200u2033. 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 u201CTransports and Putsu201D. 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 u201Ctp helpu201D 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 u201Ctp import all <sid>u201D, 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 u201D u201C.
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 u201Csystem can not be changedu201D 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 u201CUu201D 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 u2013u 1 u2013w test.log test
In the above example a unconditional mode is used, a log file u201Ctest.logu201D file is used to get the log result and a control file u201Ctestu201D, 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 u2013t: 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 u2013ba: 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 u2013bd: This command is used for a delta backup if the user does not want a complete backup.
R3trans u2013bi: This option will display backup information.
The following are some of the examples of control files:
We have already learned how to use a command for the logical backup of the objects in the database. To get a complete backup the following example control file can be used.
backup all
file = /usr/sap/trans/backall
The option u201Cfile = u2026u201D is the name of the directory into which the data files are to be written. If you are taking a complete backup of DEV system then the backup file is going to look like u201CDEV.A000.bcku201D the next complete
Reward if useful
Regards
divya -
Estimating Activation Time of Business Functions in EhP3
Can anyone estimate how long the activation of c.100 Business Functions plus one industry business function set (ECC-DIMP) ought to take when the transport is imported into a new system? This is in ERP 6 with EhP3.
I know some BFs will activate faster than others, but on average? In our QA system this has taken c.12 hours.
Based on Thomas Weiss' weblog series (great stuff there) I understand that (1) all the activated code is compiling for the first time, and (2) all the DDIC table appends are taking place.
So I wonder also if the size of the tables (# records) affect the run-time of the background job SFW_ACTIVATE_SF0X.
P.S. We are on Basis 70018, and may need to investigate SAP Note 1278120 (available in 70019) to get improved logging. I've also seen the answer by Ralf regarding SAP Note 1276225 to fix a bug in 70018 that reactivates business functions (this was in [Terry's thread|SFW5 repeating already activated BF] ) .You may be try the R3trans parallel option from note
Note 1127194 - R3trans import with parallel processes
I have no in-depth knowledge on how the switch framework does transport but what I can say is that using this options certain phases of the import are running in parallel as opposed to sequentially when only one R3trans is used.
Note: This is not the same as the parallel option in SPAM/SAINT. This options does in-transport parallelization (one transport is imported with several R3trans where possible).
Just a guess, I have not tested that for SFW5.
Markus -
Hi All,
I want to know the ways to copy data in a maintainable table from one system to other system ( in different landscape).
Kindly pass on your inputs.
Thanks.
Regards,
Arun.Another Link to Transport:www dotsaptechnical dot com/Tips/Basis/Transport/TableEntries dot htm
or
This would be a Basis solution..:
create the file export.ctl in the system source. Then:
Export File = 'export.dat' Client = 201 Select * from table
And in the system target create the file: import.ctl
Import File = 'export.dat' Client = 301
Then execute in the source systems: R3trans export.ctl
This creates a file named export.dat, then copy this file to target system and execute in the target system: R3trans import.ctl
This imports the table to the target system.
[More info|http://searchsap.techtarget.com/generic/0,295582,sid21_gci1341095,00.html] -
/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 -
Error while importing a transport request
Hi,
I installed two SAP ECC6 EHP6 IDES sytems and created a transport route between them.
When I try to import a Transport request I get the following error:
HALT: inconsistent preview tables E071K_STR (size=344) and E071KS_PREVIEW (size=128)
Please help me find a solution to this problem.Hello Occoro,
There are multiple steps you need to do, I am not sure if the following note is applicable to your version of SAP.
1730009 - Import queue does not work
Downloading R3trans and tp is similar to downloading kernel.
Download the versions relevant to your SAP Kernel 7.20, the latest patch should be available at http://service.sap.com/swdc
In the same area where you get SAP Kernels, you should be able to get files such as:
R3trans_xxx-xxxxxx.SAR
tp_xxx-xxxx.SAR
Download these files, uncar them to your kernel directory typically /sapmnt/<SID>/exe
Refer to the following note for more details:
19466 - Downloading SAP kernel patches
Good luck.
Regards,
Siddhesh -
SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903
Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.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
WARNING: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain. -
Import support package SAPKB70015 at PI System is stuck on IMPORT_PROPER
Dear Expert,
I have some problem when import support package SAPKB70015 at PI System.
IT had shown as below.
Main import
Transport request : SAPKB70015
System : CXI
tp path : tp
Version and release: 372.04.08 700
sap_dext called with msgnr 4:
db call info
function: db_report_interface
fcode: UPDATE_REPORT
tabname: TEXT
len (char): 40
key: /OSP/CL_CJS_CONTEXT===========CP
retcode: 4
Main import
End date and time : 20081120021353
Ended with return code: ===> 12 <===
And I checked the transport log,It shown as below.
4 ETW690 COMMIT "360444" "53156878"
3 ETW674Xstart import of "LIMUCLSD/OSP/CL_CJS_CONTEXT" ...
4 ETW000 1 entry for TADIR updated (R3TRCLAS/OSP/CL_CJS_CONTEXT ).
4 ETW000 REPOS /OSP/CL_CJS_CONTEXT===========CP A replaced.
4 ETW000 dev trc ,00000 Thu Nov 20 02:13:53 2008 39924798 39.924798
4 ETW000 http://dbsloci. ,00000 *** ERROR => Cannot update a LOB column for more than one row piecewise
4 ETW000 85 39.924883
4 ETW000 dev trc ,00000 sc_p=0x110f57d68,no=55,idc_p=0x110f70638,con=0,act=1,slen=125,smax=256,#vars=5,stmt=0x111e1f700,tabl
e=REPOTEXT
4 ETW000 66 39.924949
4 ETW000 dev trc ,00000 prep=0,lit=0,nsql=0,lobret=1,#exec=1,dbcnt=2,upsh_p=(nil),ocistmth_p=0x111e20098
4 ETW000 53 39.925002
4 ETW000 dev trc ,00000 IN : cols=4,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=4294967295,rsize=84,vmax=32,bound=1,iobuf_p=0x111
0a4220,vda_p=0x111e21a60
4 ETW000 58 39.925060
4 ETW000 dev trc ,00000 lobs=1,lmax=4,lpcnt=0,larr=0x111e22180,lcurr_p=(nil),rret=0
4 ETW000 48 39.925108
4 ETW000 dev trc ,00000 OUT: cols=1,rmax=0,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=0,vmax=32,bound=0,iobuf_p=(nil),vda_p=0x1
11e222c0
4 ETW000 55 39.925163
4 ETW000 dev trc ,00000 lobs=1,lmax=4,lpcnt=0,larr=0x111e22220,lcurr_p=(nil),rret=2
4 ETW000 47 39.925210
4 ETW000 dev trc ,00000 UPDATE "REPOTEXT" SET "DATA" = :A0 WHERE "PROGNAME" = :A1 AND "R3STATE" = :A2 AND "LANGUAGE" = :A3
4 ETW000 51 39.925261
4 ETW000 dev trc ,00000 RETURNING "DATA" INTO :A4; 29 39.925290
4 ETW000 dbrepolo ,00735 ***LOG BZY=>unexpected return code 2 calling dbrepolo#? @ 735
4 ETW000 75 39.925365
2EETW000 sap_dext called with msgnr "4":
2EETW000 -
db call info -
2EETW000 function: db_report_interface
2EETW000 fcode: UPDATE_REPORT
2EETW000 tabname: TEXT
2EETW000 len (char): 40
2EETW000 key: /OSP/CL_CJS_CONTEXT===========CP
2EETW000 retcode: 4
1 ETP154 MAIN IMPORT
1 ETP110 end date and time : "20081120021353"
1 ETP111 exit code : "12"
1 ETP199 ######################################
System information
SAP = NW2004s SR3
Database = Oracle 10.2.0.2
OS versions = AIX 5.3
Tp version = 700 Unicode 179
R3trans version = 700 Unicode 183
PS.I checked tp connect return code 0 and R3trans u2013s return code 0
Could you please suggest how to fix this problem?
Thank you very much
JaturongIu2019ve updated database statistics and then try to reimport the package again. But It canu2019t import package.
Are you still getting the same error after you retry the statistics update? -
How to export Tabel? (Exporting and Importing of RFCDES table)
Hi,
We are doing system Refresh on qualitysystem,
I want to export the Tables and reimport them after system refresh
Tables like: RFCDES
How can export this table ?
How to import the table?
It is very urgent, Please give me the solution as soon as possible
Note: we are using BRTOOLS
Points awarded
Regards,
RaviHi Ravi,
Create a control file like "rfcdes_export.ctl"
export
file '/usr/sap/data/export_rfc.dat
delete from rfcdes
select * from rfcdes
Take the export :
R3trans -w rfcdes_export.log rfcdes_export.ctl
Create the control file "rfc_import.ctl"
import
file '/usr/sap/data/export_rfc.dat'
Import it:
R3trans -w rfc_import.log -u 1268 rfc_import.ctl
Hope it will help you.
Best Wishes.
Kumar -
Error while upgrading Patch SAPKB70014- Error R3trans received signal 11
Dear All
while updating my basis patch level to sapkb70014 I m facing the error at DDIC import phase related to R3trans recived signal 11.My tp version is accurate as required . Kernel versin is 238 Can you guys help me to solve the same
Regards
ShilpaHi
Please continue to run the SPAM again. Also check the Note 822379. If the problem didnt solve yet, post complete log.
Regards,
Rajan -
SAP is not coming up after system refresh with Export/Import option
Hi,
I have exported Java 6.40 and finished the refresh successfully. And I imported the Java successfully. After importing Java, I restarted SAP but is not coming up. When I checked the dev_w0 trace file, I got the following information.
trc file: "dev_w0", trc level: 1, release: "640"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
B
B Wed Aug 05 10:48:17 2009
B create_con (con_name=R/3)
B Loading DB library 'F:\usr\sap\IDS\SYS\exe\run\dboraslib.dll' ...
B Library 'F:\usr\sap\IDS\SYS\exe\run\dboraslib.dll' loaded
B Version of 'F:\usr\sap\IDS\SYS\exe\run\dboraslib.dll' is "640.00", patchlevel (0.220)
B New connection 0 created
M sysno 00
M sid IDS
M systemid 560 (PC with Windows NT)
M relno 6400
M patchlevel 0
M patchno 247
M intno 20020600
M make: multithreaded, Unicode
M pid 844
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 844) [dpxxdisp.c 1170]
I MtxInit: -2 0 0
M DpSysAdmExtCreate: ABAP is active
M DpShMCreate: sizeof(wp_adm) 20328 (1452)
M DpShMCreate: sizeof(tm_adm) 2969176 (14772)
M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
M DpShMCreate: sizeof(comm_adm) 290000 (580)
M DpShMCreate: sizeof(vmc_adm) 0 (424)
M DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
M DpShMCreate: SHM_DP_ADM_KEY (addr: 05FE0040, size: 3391480)
M DpShMCreate: allocated sys_adm at 05FE0040
M DpShMCreate: allocated wp_adm at 05FE1B88
M DpShMCreate: allocated tm_adm_list at 05FE6AF0
M DpShMCreate: allocated tm_adm at 05FE6B18
M DpShMCreate: allocated wp_ca_adm at 062BB970
M DpShMCreate: allocated appc_ca_adm at 062C1730
M DpShMCreate: allocated comm_adm_list at 062C3670
M DpShMCreate: allocated comm_adm at 062C3688
M DpShMCreate: allocated vmc_adm_list at 0630A358
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 0630A380
M DpShMCreate: allocated wall_adm at 0630A388
M ThTaskStatus: rdisp/reset_online_during_debug 0
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 Wed Aug 05 10:48:18 2009
M calling db_connect ...
C Prepending e:\oracle\IDS to Path.
C got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
C Client NLS settings: AMERICAN_AMERICA.UTF8
C Logon as OPS$-user to get SAPIDS's password
C Connecting as /@IDS on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 05B17398 05B1C458 05B1BEC0
C Attaching to DB Server IDS (con_hdl=0,svchp=05B1BE14,srvhp=05B1CA84)
C Starting user session (con_hdl=0,svchp=05B1BE14,srvhp=05B1CA84,usrhp=05B256B8)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
[dboci.c 4508]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c 11395]
C Try to connect with default password
C Connecting as SAPIDS/<pwd>@IDS on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 05B17398 05B1C458 05B1BEC0
C Starting user session (con_hdl=0,svchp=05B1BE14,srvhp=05B1CA84,usrhp=05B256B8)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
[dboci.c 4508]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c 11395]
B ***LOG BY2=> sql error 1017 performing CON [dbsh#3 @ 1204] [dbsh 1204 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#3 @ 1204] [dbsh 1204 ]
B ***LOG BY2=> sql error 1017 performing CON [dblink#3 @ 428] [dblink 0428 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#3 @ 428] [dblink 0428 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1283]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9708]
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 ord-sapproj_IDS_00 on host ord-sapproj (wp 0)
M * ERROR tskh_init: db_connect
M *
M * TIME Wed Aug 05 10:48:18 2009
M * RELEASE 640
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 9893
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 255]
M Entering ThSetStatError
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 844) [dpnttool.c 357]
I have checked database connectivity with the command 'r3trans -d', it got finished with the return code 0012 and the trace.log file is showing the following information.
=======================================
4 ETW000 r3trans version 6.13 (release 640 - 17.07.08 - 08:11:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 05.08.2009 - 10:52:31
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Wed Aug 05 10:52:34 2009 0.000000
4 ETW000 [dev trc ,00000] db_con_init called 0.000000
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 0.000000
4 ETW000 [dev trc ,00000] Loading DB library 'dboraslib.dll' ... 0.000000
4 ETW000 [dev trc ,00000] load shared library (dboraslib.dll), hdl 0 8449 0.008449
4 ETW000 [dev trc ,00000] using "f:\usr\sap\IDS\SYS\exe\run\dboraslib.dll"
4 ETW000 37 0.008486
4 ETW000 [dev trc ,00000] Library 'dboraslib.dll' loaded 18 0.008504
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library dboraslib.dll
4 ETW000 27 0.008531
4 ETW000 [dev trc ,00000] Version of 'dboraslib.dll' is "640.00", patchlevel (0.220)
4 ETW000 219 0.008750
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library dboraslib.dll
4 ETW000 27 0.008777
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library dboraslib.dll
4 ETW000 36 0.008813
4 ETW000 [dev trc ,00000] New connection 0 created 26 0.008839
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 34 0.008873
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 22 0.008895
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse:
4 ETW000 25 0.008920
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 32 0.008952
4 ETW000 [dev trc ,00000] Setting DIR_CLIENT_ORAHOME is not set as environment variable,
4 ETW000 assuming using instant client with unspecified location.
4 ETW000 227 0.009179
4 ETW000 [dev trc ,00000] -->oci_initialize (con_hdl=0) 130 0.009309
4 ETW000 [dev trc ,00000] got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
4 ETW000 32 0.009341
4 ETW000 [dev trc ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8 23827 0.033168
4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPIDS's password 34 0.033202
4 ETW000 [dev trc ,00000] Connecting as /@IDS on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
4 ETW000 35 0.033237
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 32 0.033269
4 ETW000 [dev trc ,00000] 0 UTF8 1 0253CDB0 02541E18 02541880
4 ETW000 112 0.033381
4 ETW000 [dev trc ,00000] Allocating service context handle for con_hdl=0 29 0.033410
4 ETW000 [dev trc ,00000] Allocating server context handle 25 0.033435
4 ETW000 [dev trc ,00000] Attaching to DB Server IDS (con_hdl=0,svchp=025417D4,srvhp=025423DC)
4 ETW000 51 0.033486
4 ETW000 [dev trc ,00000] Assigning server context 025423DC to service context 025417D4
4 ETW000 41860 0.075346
4 ETW000 [dev trc ,00000] Allocating user session handle 47 0.075393
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=025417D4,srvhp=025423DC,usrhp=0254AFA8)
4 ETW000 50 0.075443
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 4381 0.079824
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 31 0.079855
4 ETW000 [dev trc ,00000] set_ocica() -> OCI or SQL return code 1017 23 0.079878
4 ETW000 [dev trc ,00000] Try to connect with default password 80 0.079958
4 ETW000 [dev trc ,00000] Connecting as SAPIDS/<pwd>@IDS on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
4 ETW000 28 0.079986
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 31 0.080017
4 ETW000 [dev trc ,00000] 0 UTF8 1 0253CDB0 02541E18 02541880
4 ETW000 32 0.080049
4 ETW000 [dev trc ,00000] Assigning username to user session 0254AFA8 19 0.080068
4 ETW000 [dev trc ,00000] Assigning password to user session 0254AFA8 25 0.080093
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=025417D4,srvhp=025423DC,usrhp=0254AFA8)
4 ETW000 32 0.080125
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 1691 0.081816
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 28 0.081844
4 ETW000 [dev trc ,00000] set_ocica() -> OCI or SQL return code 1017 18 0.081862
4 ETW000 [dblink ,00428] ***LOG BY2=>sql error 1017 performing CON [dblink#3 @ 428]
4 ETW000 119 0.081981
4 ETW000 [dblink ,00428] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#3 @ 428]
4 ETW000 30 0.082011
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'IDS'"
=================================================================================
Kindly suggest me the solution to resolve the issue.
Thanks & regards,
MogileeswarPlease check the logs it is clrerly mentioned thet your sapsystem is not able to connect to database.
ERROR => CONNECT failed with sql error '1017' [dbsloci.c 11395] B ***LOG BY2=> sql error 1017 performing CON [dbsh#3 @ 1204] [dbsh 1204 ] B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#3 @ 1204] [dbsh 1204 ] B ***LOG BY2=> sql error 1017 performing CON [dblink#3 @ 428] [dblink 0428 ] B ***LOG BY0=> ORA-01017: invalid username/password
Check the Note------Note 713685 - Hom./Het.System Copy SAP Web AS 6.40
run these commands:
brconnect -u / -c -l E -f chpass -o SAPSR3 -password whatever_you_want
sqlplus /nolog @sapdba_role.sql SID NT
Also check the parameter DBS_ORA_SCHEMA is set to SAPSR3.
Also read note 400241.
Thanks
Rishi Abrol -
Error while importing SPAM version 7.0/33 Tp ended with error code 12.
Hi all,
Os: Windows 2003 advanced server
DB: MaxDB 7.6
SAP: NetWeaver 2004S - (ABAP+JAVA) EP
When i was trying to import latest SAPM on the system. V 7.0/33 it got stopped in the middle at
IMPORT_PROPER phase.
Please find the error as follows:
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: IMPORT_PROPER
- Reason for error: TP_STEP_FAILURE
- Return code: 0012
- Error message: OCS Package SAPKD70033, tp step "R", return code
0012
Notes on phase IMPORT_PROPER
In this phase repository objects and table entries are imported. This
phase can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called.
o TP_FAILURE: The program tp could not be executed. For more
information on this, see the SLOG or ALOG log file.
o TP_STEP_FAILURE: A tp step could not be executed. To find the cause
of the error, see the appropriate log, such as the import log.
If the cancelation message contains a tp step 6, N or S, the step in
question is independent of the transport request. You can find these
logs under the node Import steps not specific to transport request
in the log overview.
Alternatively, you can find these logs in the following files in the
log directory of your transport directory (usually:
/usr/sap/trans/log):
- tp Step 6: P<YY><MM><DD>.<SID>
- tp Step N: N<YY><MM><DD>.<SID>
- tp Step S: DS<YY><MM><DD>.<SID>
You can display these files using the report RSPUTPRT or by calling the
transaction AL11.
A prerequisite of the Support Package Manager is that the Change and
Transport System (CTS) is configured correctly. For more detailed
information, read the online documentation available from Help -> SAP
Library -> mySAP Technology Components -> SAP Web Application Server ->
Change and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
In the import log file the errors was :
Program terminated (job: RDDEXECL, no.: 14444101)
Job log for this job is ;
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server nanadual were synchronized
ABAP/4 processor: SYSTEM_RUDI_INVALID
Job cancelled
Please let me know if you need more details...
Best Regards,
NandaHi Nanda,
Please check your trans log for further details .
It cud be caused due to unavailability of RDDIMPDP batch job which is mandatory for any SPAM / SP updates to work.
If this is the case you wud require to trigger the batch job RDDIMPDP using report RDDNEWPP(From SE38). This needs to be triggered in 000 as well as other existing clients too.
once this is done please resume your SPAM Update. it shud go ahead.
Next possibility that you cud check is updating your tp / R3trans with latest available from Service market place.
Hope this helps you.
Regards,
Prem -
I am getting the following error at Import ABAP phase ...
Dear All,
I am getting the following error at Import ABAP phase when performing the system copy function (Import) via ./sapinst ( OS - LINUX and DATABASE-ORACLE 10g)...
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/RXT/SYS/exe/run/R3load: START OF LOG: 20090102154030
/usr/sap/RXT/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/RXT/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Apr 1 2006 00:08:29
/usr/sap/RXT/SYS/exe/run/R3load -testconnect
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/RXT/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/RXT/SYS/exe/run/R3load: END OF LOG: 20090102154030
Thanx,
AmitDear Juan,
Trans.log is ;
isrxi:rxtadm 7> cat trans.log
4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 02.01.2009 - 16:45:09
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Fri Jan 2 16:45:09 2009 62 0.000062
4 ETW000 [dev trc ,00000] db_con_init called 13 0.000075
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 21 0.000096
4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/RXT/SYS/exe/run/dboraslib.so' ...
4 ETW000 26 0.000122
4 ETW000 [dev trc ,00000] load shared library (/usr/sap/RXT/SYS/exe/run/dboraslib.so), hdl 0
4 ETW000 9099 0.009221
4 ETW000 [dev trc ,00000] Library '/usr/sap/RXT/SYS/exe/run/dboraslib.so' loaded
4 ETW000 16 0.009237
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000 30 0.009267
4 ETW000 [dev trc ,00000] Version of '/usr/sap/RXT/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.46)
4 ETW000 42 0.009309
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000 21 0.009330
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000 25 0.009355
4 ETW000 [dev trc ,00000] New connection 0 created 16 0.009371
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 21 0.009392
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 17 0.009409
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse:
4 ETW000 15 0.009424
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 16 0.009440
4 ETW000 [dev trc ,00000] -->oci_initialize (con_hdl=0) 195 0.009635
4 ETW000 [dev trc ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8 1567 0.011202
4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPSR3's password 14 0.011216
4 ETW000 [dev trc ,00000] Connecting as /@RXT on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000 15 0.011231
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 17 0.011248
4 ETW000 [dev trc ,00000] 0 UTF8 1 0x9342150 0x9349ba0 0x935a298
4 ETW000 16 0.011264
4 ETW000 [dev trc ,00000] Allocating service context handle for con_hdl=0 15 0.011279
4 ETW000 [dev trc ,00000] Allocating server context handle 11 0.011290
4 ETW000 [dev trc ,00000] Attaching to DB Server RXT (con_hdl=0,svchp=0x935a1c8,svrhp=0x935c4a8)
4 ETW000 63 0.011353
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
4 ETW000 1787 0.013140
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '12541'
4 ETW000 16 0.013156
4 ETW000 [dev trc ,00000] Try to connect with default password 46 0.013202
4 ETW000 [dev trc ,00000] Connecting as SAPSR3/<pwd>@RXT on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000 15 0.013217
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 16 0.013233
4 ETW000 [dev trc ,00000] 0 UTF8 1 0x9342150 0x9349ba0 0x935a298
4 ETW000 15 0.013248
4 ETW000 [dev trc ,00000] server_detach(con_hdl=0,stale=0,svrhp=0x935c4a8)
4 ETW000 14 0.013262
4 ETW000 [dev trc ,00000] Detaching from DB Server (con_hdl=0,svchp=0x935a1c8,srvhp=0x935c4a8)
4 ETW000 13 0.013275
4 ETW000 [dev trc ,00000] Deallocating server context handle 0x935c4a8 20 0.013295
4 ETW000 [dev trc ,00000] Allocating server context handle 20 0.013315
4 ETW000 [dev trc ,00000] Attaching to DB Server RXT (con_hdl=0,svchp=0x935a1c8,svrhp=0x935c4a8)
4 ETW000 25 0.013340
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
4 ETW000 430 0.013770
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '12541'
4 ETW000 16 0.013786
4 ETW000 [dblink ,00431] ***LOG BY2=>sql error 12541 performing CON [dblink#3 @ 431]
4 ETW000 85 0.013871
4 ETW000 [dblink ,00431] ***LOG BY0=>ORA-12541: TNS:no listener [dblink#3 @ 431]
4 ETW000 15 0.013886
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'RXT'"
isrxi:rxtadm 8>
Regards,
Amit -
Error in Import ABAP phase on slution manager - R3load-testconnect
Hi all,
I am installing solman and got error in Import ABAP phase
here is the log
WARNING 2010-05-20 08:13:27.982 Execution of the command "/usr/sap/SM7/SYS/exe/run/R3load -testconnect" finished with return code 127. Output: /usr/sap/SM7/SYS/exe/run/R3load: error while loading shared libraries: /oracle/client/10x_64/instantclient/libnnz10.so: cannot restore segment prot after reloc: Permission denied
> R3trans -d
This is R3trans version 6.14 (release 700 - 14.02.08 - 14:55:00).
unicode enabled version
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/SM7/SYS/exe/run') or dbms_type ('ORA')"
R3trans finished (0012).
SQL> startup;
ORACLE instance started.
Total System Global Area 4613734400 bytes
Fixed Size 2090048 bytes
Variable Size 2315258816 bytes
Database Buffers 2281701376 bytes
Redo Buffers 14684160 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
Please advice
Regards
Palle
Edited by: palle26 on May 20, 2010 11:00 AMhi
After insattaling oracle, i didn't apply oracle patch.
when it throwed error , r3load-testconnect, then i stoped listener & applied patch and continued with the installation .
DB is not getting started. when i used > startup;
ORACLE instance started.
Total System Global Area 4613734400 bytes
Fixed Size 2090048 bytes
Variable Size 2315258816 bytes
Database Buffers 2281701376 bytes
Redo Buffers 14684160 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
R3trans -d
This is R3trans version 6.14 (release 700 - 14.02.08 - 14:55:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'SM7'"
R3trans finished (0012).
SQL> select status from v$instance;
ERROR:
ORA-03114: not connected to ORACLE
one of the blog said to restart the server. i did it but now if i say hotname
it is giving full domain name as sap-server.lgcnsglobal.com instead of sap-server
Do i need to uninstall oracle and do it again , if so how do i uninstall oracle?
regards
sandhya
Maybe you are looking for
-
Hoe can i print pdf report(created from jasper report) without preview
<%@ include file="jsp_connect_db.jsp" %> <% //============================================== //Report Exporting //============================================== File reportFile = new File(application.getRealPath("rno0700.jasper"))
-
Hi All We have a requirement around trx control and found earlier esponse on trasaction control very helpful . Just need help on one aspect . Our business need is to stop the user from entering effort or amount above certain limit , for e.g Total acc
-
FCSS1 and Leopard - apple supported!
Contrary to an earlier post by someone, if you look at http://docs.info.apple.com/article.html?artnum=307092 it is clearly stated that whilst FCP 4 (and earlier) is not supported FCS1 and FCS2 are! Final Cut Pro 4: Not supported on Mac OS X 10.5 Leop
-
Creating SC's from external system
Hi there, Does anyone have experience creating shopping carts into SRM from a different application (via an interface). I know about the existence of BAPI BAPI_SCEC_CREATE but would like to know if anyone has experience and maybe already some hints/t
-
SAF Agent on WebLogic Server 10.3.5
We have 2 applications hosted on weblogic server 9.2 MP3 server instances running on separate boxes. A SAF Agent configured on one instance is used to forward messages between the applications. We are planning to upgrade the server to WL 10.3.5 where