DB13 ended with error during initilization tape

Dear Friend,
We upgraded solution manager server 6 month back to Solman 4.0 and oracle 10g. But during initialization of tape by DB13 i facing error as "Credential retrieval failed" same error occuerd if i execute online backup with DB13. But by brtools initialization tape work nice but not DB13. Also in SM37 initilization job finished not anyy error
Please find below message ,
BR0280I BRBACKUP time stamp: 2007-12-22 12.36.10
BR0301E SQL error -12638 at location BrInitOraCreate-2, SQL statement:
'CONNECT / AT PROF_CONN IN SYSOPER MODE'
ORA-12638: Credential retrieval failed
BR0303E Determination of Oracle version failed
BR0206I End of backup volume initialization
BR0280I BRBACKUP time stamp: 2007-12-22 12.36.10
BR0054I BRBACKUP terminated with errors
Please reply me.
Thanks in advance.
Rd,
Sachin

Hi Sachin ,
Though sometimes ORA-12638 can be resolved by restarting the database services in cases where Oracle on Windows is being used, although for this user it was not helpful.
However, the following direction was given, and once administered, was a successful resolution to ORA-12638:
Please check the sqlnet.ora file. Change the following entry and try, this will work.
Original Entry - SQLNET.AUTHENTICATION_SERVICES= (NTS)
Modified Entry - SQLNET.AUTHENTICATION_SERVICES= (NONE)
Hope this might help you mate .
Regards,
Gokul B

Similar Messages

Online backup by DB13 ended with error not by BRTOOLS

Dear Friends,
I am trying to take online backup by DB13 of my CRM Dev system but it is ended with error , but when i check in SM37 it show finished.
By using BRTOOLS it work proparly but not by DB13.
Other Details :-
OS :- Win 2003 server
DB :- Oracle 10g
error message is :-
Detail log: bdxbnwwr.ant
BR0051I BRBACKUP 7.00 (26)
BR0055I Start of database backup: bdxbnwwr.ant 2008-01-19 10.48.21
BR0484I BRBACKUP log file: F:\oracle\CD1\sapbackup\bdxbnwwr.ant
BR0252W Function remove() failed for 'f:\oracle\cd1\102\database\sap.ora' at location BrInitOraCreate-1
BR0253W errno 13: Permission denied
BR0252W Function remove() failed for 'f:\oracle\cd1\102\database\sap.ora' at location BrInitOraCopy-7
BR0253W errno 13: Permission denied
BR0166I Parameter 'control_files' not found in file f:\oracle\cd1\102\database\initCD1.ora - default assumed
BR0252E Function CreateFile() failed for 'G:\ORACLE\CD1\SAPDATA3\TEMP_1\TEMP.DATA1' at location BrFileStatGet-2
BR0253E errno 5: Access is denied.
BR0273E Determination of file status for G:\ORACLE\CD1\SAPDATA3\TEMP_1\TEMP.DATA1 failed
BR0314E Collection of information on database files failed
BR0056I End of database backup: bdxbnwwr.ant 2008-01-19 10.48.45
BR0280I BRBACKUP time stamp: 2008-01-19 10.48.45
BR0054I BRBACKUP terminated with errors
So please help on this issue and reply ASAP.
Thanks,
Regards,
Sachin Jadhav
BASIS

Hello Friends,
I m facing one problem while taking backup form db13. can sombuddy help me to solve this problem following is the log file details
Job started
Step 001 started (program RSDBAJOB, variant &0000000000011, user ID BASIS)
Execute logical command BRBACKUP On host eccqa
Parameters:-u / -jid FLLOG20081015143102 -c force -t online -m full -p initIEQ.sap.wed -a -c force -p initIEQ.s
ap.wed -s
BR0051I BRBACKUP 7.00 (32)
BR0055I Start of database backup: bdzapxni.fnd 2008-10-15 14.31.02
BR0484I BRBACKUP log file: /oracle/IEQ/sapbackup/bdzapxni.fnd
BR0280I BRBACKUP time stamp: 2008-10-15 14.31.02
BR0301E SQL error -27140 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-27140: attach to post/wait facility failed
BR0310E Connect to database instance IEQ failed
BR0280I BRBACKUP time stamp: 2008-10-15 14.31.02
BR0301E SQL error -27140 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-27140: attach to post/wait facility failed
BR0310E Connect to database instance IEQ failed
BR0056I End of database backup: bdzapxni.fnd 2008-10-15 14.31.02
BR0280I BRBACKUP time stamp: 2008-10-15 14.31.02
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2008-10-15 14.31.02
BR0291I BRARCHIVE will be started with options '-U -jid FLLOG20081015143102 -d disk -c force -p initIEQ.sap.wed -s'
BR0002I BRARCHIVE 7.00 (32)
BR0006I Start of offline redo log processing: adzapxni.sve 2008-10-15 14.31.02
BR0484I BRARCHIVE log file: /oracle/IEQ/saparch/adzapxni.sve
BR0280I BRARCHIVE time stamp: 2008-10-15 14.31.02
BR0301W SQL error -27140 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-27140: attach to post/wait facility failed
BR0310W Connect to database instance IEQ failed
BR0280I BRARCHIVE time stamp: 2008-10-15 14.31.02
BR0301W SQL error -27140 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-27140: attach to post/wait facility failed
BR0310W Connect to database instance IEQ failed
BR0278W Command output of '/oracle/IEQ/102_64/bin/sqlplus /nolog < /oracle/IEQ/saparch/.adzapxni.spi':
SQL*Plus: Release 10.2.0.2.0 - Production on Wed Oct 15 14:31:02 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
SQL> Connected to an idle instance.
SQL>
SQL> ORA-01034: ORACLE not available
SQL> Disconnected
BR0280I BRARCHIVE time stamp: 2008-10-15 14.31.02
BR0279W Return code from '/oracle/IEQ/102_64/bin/sqlplus /nolog < /oracle/IEQ/saparch/.adzapxni.spi': 0
BR0302W SQLPLUS call for database instance IEQ failed
BR0323W 'Archive log list' for database instance IEQ failed
BR0252E Function fopen() failed for '/oracle/IEQ/saparch/archIEQ.log' at location arch_last_get-1
BR0253E errno 13: Permission denied
BR0016I 0 offline redo log files processed, totalsize 0.000 MB
BR0280I BRARCHIVE time stamp: 2008-10-15 14.31.02
BR0301W SQL error -27140 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-27140: attach to post/wait facility failed
BR0310W Connect to database instance IEQ failed
BR0252W Function fopen() failed for '/oracle/IEQ/saparch/archIEQ.log' at location BrCleanup-8
BR0253W errno 13: Permission denied
BR0121W Processing of log file /oracle/IEQ/saparch/archIEQ.log failed
BR0007I End of offline redo log processing: adzapxni.sve 2008-10-15 14.31.02
BR0280I BRARCHIVE time stamp: 2008-10-15 14.31.02
BR0005I BRARCHIVE terminated with errors
BR0280I BRBACKUP time stamp: 2008-10-15 14.31.02
BR0292I Execution of BRARCHIVE finished with return code 3
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished
it showing me above messege every time ..
Thanks
Vijay

XPRAS_AIMMRG phase ended with error during SCM7.0 EHP to 7.02

Hi,
We are performing SCM EHP upgrade from 7.0 to 7.02.
In execution phase XPRAS_AIMMRG failed with error.
Environment details:
OS : HP-UX 11.31
DB : Oracle 11.2.0.3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR731XPRA90000007.SD1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A4WERSDS 250 Start imact of DataSource D versions: "0" deleted, "2" written
A4WERSDS 253 Write dependent D versions with class "CL_RSTRAN_TRFN"
A4WERSDS 253 Write dependent D versions with class "CL_RSBK_DTP"
A4WERSDS 251 End impact handling of DataSource D versions
A3 ERSO 778 End of after import methode "RS_SHMP_AFTER_IMPORT" ("Contentmodus") - runtime: "00:14:32"
A2EERSO 870XStarting after import method "RS_DTRF_AFTER_IMPORT" for object type(s) "DTRF" in Content mode
A4 ERSTRAN 085 Transformation "0GSZMPO4NLEA9RDSTQTHIRFN5JVWAORR" deleted in version "D" of "DDIC"
A4 ERSTRAN 085 Transformation "0INP02M6KR8J2PLPTJB6A5Y6Y1KHPKE5" deleted in version "D" of "DDIC"
A4 ERSTRAN 085 Transformation "0M1BZ39AX226FAUB4BXZJ75MTGJ254F6" deleted in version "D" of "DDIC"
A4 ERSTRAN 085 Transformation "06HLC79ZEZFRSH6GGITYS9K9T10F4ZEE" deleted in version "D" of "DDIC"
A4 ERSTRAN 085 Transformation "00ZJFXBPY250GL1GM1YRVNL9CPGINOGQ" deleted in version "D" of "DDIC"
A2EERSAR 203 Source system "RD1CLNT300" does not exist
2EESY530 An exception has occurred
2EESY530 An exception has occurred
A3 ERSO 778 End of after import methode "RS_DANM_AFTER_IMPORT" ("Contentmodus") - runtime: "00:00:00"
A2 ERSO 870XStarting after import method "RS_DANS_AFTER_IMPORT" for object type(s) "DANS" in Content mode
A3 ERSO 778 End of after import methode "RS_DANS_AFTER_IMPORT" ("Contentmodus") - runtime: "00:00:00"
A2 ERSO 870XStarting after import method "RS_DDMM_AFTER_IMPORT" for object type(s) "DDMM" in Content mode
A3 ERSO 778 End of after import methode "RS_DDMM_AFTER_IMPORT" ("Contentmodus") - runtime: "00:00:00"
A2EERSO 870XStarting after import method "RS_DTPD_AFTER_IMPORT" for object type(s) "DTPD" in Content mode
A2EERSAR 203 Source system "RD1CLNT300" does not exist
A2EERSAR 203 Source system "RD1CLNT300" does not exist
A2EERSAR 203 Source system "RD1CLNT300" does not exist
A2 ERSO 870XStarting after import method "RS_DPLQ_AFTER_IMPORT" for object type(s) "DPLQ" in Content mode
A3 ERSO 778 End of after import methode "RS_DPLQ_AFTER_IMPORT" ("Contentmodus") - runtime: "00:00:00"
A2 ERSO 870XStarting after import method "RS_DPLC_AFTER_IMPORT" for object type(s) "DPLC" in Content mode
A3 ERSO 778 End of after import methode "RS_DPLC_AFTER_IMPORT" ("Contentmodus") - runtime: "00:00:00"
A2 ERSO 854XStart after-import methods for texts
2EEPU133 Errors occurred during post-handling "RS_AFTER_IMPORT_D" for "DODS" "L"
3 EPU135 "RS_AFTER_IMPORT_D" belongs to package "RSO_TLOGO"
2EEPU136 The errors affect the following components:
2EEPU137 "BW-WHM-MTD" ("Metadata (Repository)")
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
Thanks
Abhishek

Hi,
Kindly follow link MAIN_NEWBAS/XPRAS_AIMMRG errors &laquo; my experience with SAP
and SAP Note 122597.
Regards,
Gaurav

Transport control program tp ended with error code 0203

when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.

Dear Allen,
The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
<b>tp Commands:</b>
tp addtobuffer <request> <sapsid>
As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
All the steps of the entry are re-initialized.
If the entry found is not an initial entry, the import step for the command file is set to *4000 .
Before you call this command and its options, consider the effects of changing the import sequence.
tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
tp delfrombuffer <request> <sapsid>
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
tp delstopmark <sapsid>
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
tp export <request>
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
tp reformatbuffer <sapsid> [options]
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
Option downtorelease <Release>
The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
Displaying the unformatted buffer (using showbuffer <SID> )
Displaying the original buffer (using showbuffer buffer=<SID>SAV )
Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
Resetting the changes (using reformatpuffer and the option Iagree no )
If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Option Iagree
Here are the following values for this option:
yes ( true )
Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no ( false )
Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
tp setstopmark <sapsid>
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
If there is no stop mark, it is automatically generated by the commands
tp import all <sapsid> and tp put <sapsid> .
When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
tp showparams <sapsid>
This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
tp verse <request>
This creates versions of the objects in the specified request. This transport step is contained in command export .
As of Release 4.5A, more actions that prepare the export are performed in this step.
Thanks and Regards,
Naveen.

Process Chain Ended with Errors - cause unknown

I have had several instances of process chains stopping for no apparent reason. The stops occur between 2 master data infopackage loads. The last step is green and the next is grey. The PSA table has been updated successfully for the last step. All IDocs are in green status in both systems. The monitor for the last successful step does say "Ended with Errors" although no errors are evident. The process chain starts back up via Repeat at the next (grey) step and continues successfully. There were no system problems or connection interruptions that occurred during the time the process chains failed. There were no changes in the remote user profile.
This exact problem has occurred a half dozen times since our application of ECC Support Packs several months ago and had not occurred before. The infopackages are different each time. Two different process chains have had this problem. I have re-activated and re-scheduled the process chains without solving the problem.
Thanks for any ideas on why this may be occurring or what I can do to prevent it.
Patty Moffatt

Hi Des,
Here's my BW release info:
SAP_ABA        640       0019 SAPKA64019     Cross-Application
SAP_BASIS      640       0019 SAPKB64019     SAP Basis
PI_BASIS       2005_1_6400009 SAPKIPYJ69     Basis Plug-In
ST-PI          2005_1_6400008 SAPKITLQH8     SAP Solution Tools Plug-
SAP_BW         350       0019 SAPKW35019   SAP_BW
ECC SPs 13-21 were applied before the BW problem started:
SAP_BASIS      640       0021 SAPKB64021
SAP_ABA        640       0021 SAPKA64021
PI_BASIS       2005_1_6400012 SAPKIPYJ6C
ST-PI          2005_1_6400008 SAPKITLQH8
SAP_BW         350       0021 SAPKW35021
PI             2004_1_5000016 SAPKIPZI6G
The process chain step and the monitor load both are green. The Details tab shows all the processing is green, but the Process Chain itself is red with "Errors Occurred. There have been no runtime dumps.
Patty

Delete Indexes Variant ended with errors in Process chain

Hi experts,
I have a process chain which executes dialy to load data Info Cube we create the index and finally we delete the index after that we have few variants..
Remaining all variants are executed with out errors except delete index variant I checked the error message it shows that <b>" The system has not finished loading request APO_R46PWZHRIA7JS9NOM8X879QEZJ into data target ZUP_CARF1"</b>
It is so happened weekly twice or trice not every day. one day it was running with out any errors and one day this process chan was ended with errors.
I need to know the reason why this variant was executed with errors.?
I need your valule sugestions regarding this issue.
Regards
sailekha

hi sailekha,
therevare some functional constraint of processes.
while deleting indexes
it is not possible to:
                              loading
                              indexes are being built
                              stastics are being built
                              during rollup
                              while compressing
                              while updating.
my be u can check which is the other process chain that does all above oprations in concerned infoprovider.
bye

Program ended with error or warning, return code: F

Friends, During client export i am facing below mention error, Pl suggest asap
Client export from 06.04.2011 18:00:44
System ID............................ PPT
R/3 Release.......................... 700
Basis Support Package...............SAPKB70018
Host................................. pptest
Start in background............. .....X
User................................. SUPER
Parameter
Source client........................ 500
Source client user masters............500
Copier profile:.......................SAP_ALL
Table selection
Command file......................... PPTKT00008
Customizing data .....................X
With application data................ X
Initialize and recreate......... X
Change documents are not copied
Transport control program tp ended with error code 0012
Error exporting request PPTKT00008 23:40:31
Program ended with error or warning, return code: F
Runtime (seconds) : 20,390
End of processing: 23:40:33

There could be three things possibly causing this error:
1. There is some database issues, that is the connection to the database maybe is lost that's why TP ends.
2. The TP return Code can also arise due to issues at the OS level, where SAP is installed.
3. Due to permission issues also this can creep in. By permission issues I mean there are not enough permissions, please use trace ST01 and run the process again.
Also please paste the Imort Log, as it can help in further analysis and with that please give your database and OS informations.

Tp program ended with error code 0012

during export client from PRD to QAS i got the following error
3 ETA072 Exit program "CLIENTCOPY_SELECT_TEXTID_ALL" successfully executed "20:13:54"
2 ETA090 Command file for "tp" is written under: "PRDKT00029" "20:25:04"
2 ETA091 For client transport, "        55,612" entries entered in command file
2 ETA090 Command file for "tp" is written under: "PRDKX00029" "20:25:04"
2 ETA091 For client transport, "           419" entries entered in command file
2 ETA375 Transport program TP started successfully for "PRDKX00029" "20:25:05"
1 EXT200 Transport control program tp ended with error code "0012""A tool used by tp aborted""EXPORT PRDKT00029 client500 U18 pf=/usr/sap/tr
1 ETA377 Error exporting request "PRDKT00029" "20:54:04"
1 ETA146 Program ended with error or warning, return code: "F"
1 ETA027 Runtime (seconds)         : "         2,455"
1 ETA152 End of processing: "20:54:04"
any can help me
Thanks

Hi Ehab,
Yes !..
ALOG and SLOG can help analyze the problem and provide you the possible solution...
Make sure that you are using updated KERNEL and TP program before exporting the client..
Regards.
Rajesh Narkhede

Transport control program tp ended with error code 0212

Hi all,
I have created a two system landscape of development & production server. But while I am releasing any request from develpoment server a error is showing: " Transport control program tp ended with error code 0212 Errors: could not access file as supposed (see dev_tp or S".I have chosen development server as domain controller. TMS alert viewer error message also contains the following information------>command: TMS_MGR_READ_TRANSPORT_QUEUE
                                                                       service: transport service
                                                                       start : online
                                                                       Function: TMS_TP_SHOW_BUFFER
                                                                       message: TP_REPORTED_ERROR
In import monitor it's showing : "tp finished: could not access file as supposed (see dev_tp or SLOG1113.K"
Can you tell me how to resolve this issue?

dev_tp contains:
This is R3trans.exe version 6.14 (release 700 - 09.04.10 - 11:26:00).
unicode enabled version
usage: R3trans.exe [<options>] <control_file>
The control_file describes what R3trans has to do.
The following options are possible:
-c f1 f2 : Copy file f1 to f2 with character set conversion.
-d       : DB connect. Test if SAP database is available.
-i file : Import from file without using a control file.
-l file : List the contents of file to the log file.
-m file : List the contents of file to allow tp to create a cofile.
-t       : Test. All database changes are rolled back.
-t4      : Trace level 4. Switch on developer trace.
-u <int> : Unconditional modes. See below.
-v       : Verbose. Write more details to the log file.
-w file : Log file. The default log file is 'trans.log'.
-x       : DB connect without access on any SAP table.
R3trans.exe finished (0012).
& the slog file is not there in the trans/log directory

The report l runs very night and gets ended with error

Dear all,
I am facing a problem in solution manger. There is an report (Program/Command RDSMOPSOL_MONIREFRESH ) will runs very night and get ended with error and there is Run-time error "MESSAGE_TYPE_X".
Please suggest how to solve the problem.
Is this report is necessary   for the system because it is not mention in the sap stand jobs.
SM37 log
Job started
Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
Opening and closing session started. Session SM2000000000065
Opening and closing the session was successful. Session: SM2000000000065
Opening and closing session started. Session SM2000000000005
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
SM:CSA SESSION REFRESH
No. Program/Command       Prog. type Spool list Parameter      User Lang.
1 RDSMOPSOL_MONIREFRESH ABAP                  &0000000000876 BASIS EN
Sm21 log
00:00:50 DIA 00 000 SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
00:30:57 BTC 08 200 BASIS             R68 Perform rollback
00:30:57 BTC 08 200 BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
00:30:57 BTC 08 200 BASIS             AB1 > Short dump "081112 003057 sapsm BASIS " generated
00:30:57 BTC 08 200 BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
00:30:57 BTC 08 200 BASIS             R68 Perform rollback
00:30:57 BTC 08 200 BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... T    Transaction Problem
Development class... SABP
Further details for this message type
Module name......... abdynpro
Line................ 1133
Error text.......... ab_jmess
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
a.. MESSAGE_TYPE_X
Technical details
File................ 000048
Position............ 0000253620
Entry type.......... l      ( Error (Module, Row)            )
Message ID.......... AB 0
Variable parts...... ab_jmess                                            abdynpro1133
Time     Ty. Nr Cl. User         Tcod MNo Text                                                                    Date : 12.11.08
00:30:57 BTC 08 200 BASIS             AB1 > Short dump "081112 003057 sapsm BASIS " generated
etails
ecording at local and central time........................ 12.11.2008 00:30:57
ask................ 05312 . 08 B8 BTC background processor No. 08
ser................ BASIS
lient.............. 200
erminal............
ession............. 1
ransaction code....
rogram name........
roblem class....... K    SAP Web AS Problem
evelopment class... SABP
BAP Mini dump
ate................ 20081112
ime................ 003057
ost................ sapsm
ser................ BASIS
ocumentation for system log message AB 1 :
A short dump was generated for the specified program termination.
You can analyze this short dump in the system log evaluation by
selecting this line or evaluating Table SNAP (Transaction ST22).
echnical details
ile................ 000048
osition............ 0000253800
ntry type.......... s      ( ABAP Runtime Error             )
essage ID.......... AB 1
ariable parts...... 081112003057sapsm   BASIS
Time     Ty. Nr Cl. User         Tcod MNo Text                                                                    Date : 12.11.08
00:30:57 BTC 08 200 BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... K    SAP Web AS Problem
Development class... SDYN
Module name.........
Location............
T100................ 00                  671
Parameters..........
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 00                  671
ABAP/4 processor: &
No documentation exists for message 00671
Parameter
a.. MESSAGE_TYPE_X
00:30:57 BTC 08 200 BASIS             R68 Perform rollback
Details
Recording at local and central time........................ 12.11.2008 00:30:57
Task................ 05312 . 08 B8 BTC background processor No. 08
User................ BASIS
Client.............. 200
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... W    Warning
Development class... STSK
Further details for this message type
Module name......... thxxhead
Line................ 1240
Error text..........
Caller.............. ThIRoll
Reason/called....... roll ba
Documentation for system log message R6 8 :
An error has causes an SAP rollback. All database updates are reset.
Technical details
File................ 000048
Position............ 0000254520
Entry type.......... m      ( Error (Function,Module,Row)    )
Message ID.......... R6 8
Variable parts......                                       ThIRollroll bathxxhead1240
Regards,
Shiva

Hi karteek,
I have check there is Switch of operation mode but when I have checked the t-code sm63 there is no new mode are in normal mode.
There is one thing I want to ask dose this report (Program/Command RDSMOPSOL_MONIREFRESH ) run   in your system or any one server because I have think there is some problem in job shued
and is also not mention in the sap stand jobs.
there is an error in sm21 in job.
BASIS        SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:
BASIS        SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was specified
Is this SM37 log
Job started
Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
Opening and closing session started. Session SM2000000000065
Opening and closing the session was successful. Session: SM2000000000065
Opening and closing session started. Session SM2000000000005
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
Sm21 log
SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
BASIS             R68 Perform rollback
BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
BASIS             AB1 > Short dump "081111 003056 sapsm BASIS " generated
BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111003056sapsm BASIS 2001 )
BASIS             R68 Perform rollback
BASIS             R49 Communication error, CPIC return code 017, SAP return code 223
BASIS             R64 > CPI-C function: CMINIT(SAP)
*BASIS        SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:*
*BASIS        SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was*
specified
BASIS             R68 Perform rollback
BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
BASIS             AB1 > Short dump "081111 220948 sapsm BASIS " generated
BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111220948sapsm BASIS 2001 )
Details Page 2 Line 6 System Log: Local Analysis of sapsm                     1
Time     Ty. Nr Cl. User         Tcod MNo Text
00:00:51 DIA 00 000 SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
Details
Recording at local and central time........................ 13.11.2008 00:00:51
Task................ 04100 . 00 D0 Dialog work process No. 00
User................ SAPSYS
Client.............. 000
Terminal............
Session............. 1
Transaction code....
Program name........
Problem class....... S    Operation Trace
Development class... SBTC
Sm63
Start/end time   Name of the active operation mode
   00.00 - 01.00    Normal
   01.00 - 02.00    Normal
   02.00 - 03.00    Normal
   03.00 - 04.00    Normal
   04.00 - 05.00    Normal
   05.00 - 06.00    Normal
   06.00 - 07.00    Normal
   07.00 - 08.00    Normal
   08.00 - 09.00    Normal
   09.00 - 10.00    Normal
   10.00 - 11.00    Normal
   11.00 - 12.00    Normal
   12.00 - 13.00    Normal
   13.00 - 14.00    Normal
   14.00 - 15.00    Normal
   15.00 - 16.00    Normal
   16.00 - 17.00    Normal
   17.00 - 18.00    Normal
   18.00 - 19.00    Normal
   19.00 - 20.00    Normal
   20.00 - 21.00    Normal
   21.00 - 22.00    Normal
   22.00 - 23.00    Normal
   23.00 - 00.00    Normal
Regards,

'import (8) ended with errors' i got this error

Hi experts,
while transporting request no from devlopment to production the following error is displayed in SE09 TCODE.
IMPORT (8) ENDED WITH ERRORS. More details of this error message is
transport request : glpk901850
system :glp
tp path : tp
version and release :372.04.29 700
main import
ended with return code => 8.
how to solve this error.
pls help me in this

duplicate post locked.
Thomas

Transport control program tp ended with error code 0208

Hello
I installed minisap NW2004s on XP/SP2 VMWARE 4.5. The installation it self's works fine, but have some problems in the stms. when i call the transport queue there appears an error as follow:
System   NSP              Command TMS_MGR_READ_TRANSPORT_QUEUE
Client   000              Service Transport Service
User     TMSADM           Start    Online
Date     12.10.2006       Function TMS_TP_SHOW_BUFFER
Time     07:13:13         Message TP_REPORTED_ERROR
Transport control program tp ended with error code 0208
Errors: error in transportprofil (param missing
unknown,.
Any Idea? Thanks for your help.
Regards, George

Hi
You can edit the parameter profile using RZ10 and RZ11. You should not copy but manually edit the parameters. Also you need to make a consistency check so that the parameters will be copied to the database from the OS level. You will find an option to perform consistency check in RZ11.
Hope that helps.

Transport control program tp ended with error code 0211

Dear Experts,
I have a problem in doing the import after the client export was successfully done.
I am actaully tring to do a client import/export from the PRD server to DEV server.
On PRD the client is 900 and on the DEV the client is 240.
I have manually copied the transport requests created into the
/usr/sap/trans/cofiles and /usr/sap/trans/data folders to the same on the DEV server.
After coping them,
I have tried to add these transport requests to the DEV server queue, i get the following error message
Transport control program tp ended with error code 0211
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: ADDTOBUFFER RT2KT00014 RT1 pf=/usr/sap/trans/bin/T
Return code: 0211
Error text: no info about transport request found
Request: RT2KT00014
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.
After this I have tried to add the transports to the buffer at the OS level using the command
./tp pf=TPPARAM addtobuffer "RT2KT00014" RT1 U18 by going to the folder
/usr/sap/trans/bin
But it says that the tp is not found.
I have also checked the permissions for the TRANS folder, it has full access i.e 777
This is where i am struck, and the client has to be imported asap as the requirement for the SUPPORT TEAM is very urgent.
We are on AIX, Oracle 10G and ECC6
Thanks and regards
Harry

Dear Imtiaz,
Thanks for your quick fire reply...
The link helped me but it could not resolve my issue..
Infact i found it my self that the transport requests had to be given full FILE PERMISSIONS at the OS level
I logged in as ROOT
and changed directory to /usr/sap/trans/cofile and gave the command
chmod 777 RT00014.RT2 and
chmod 777 RX00014.RT2
and then went to STMS>SYSTEMS>Import View>Extras>Other requests--> Add ..
Here i added the request nos and then it added up in the queue and then i started the import.
Anyway thank you very for your reply..
Awareded points to you.
Thanks and regards
Harry...

Transport control program tp ended with error code 0247

Hi,
Our landscape is such that any transport request once released, gets imported to Q system immediately. However there is another system (another box REG - regression testing) to which I would like to import a request but the transport queue of REG system does not show the request. So I tried to explicitly add it to the queue but I get the following error message, 'Transport control program tp ended with error code 0247.
There doesn't seem to be a problem with data & CO files as the same request is in Q system and the changes are all transported successfully.
This request is a transport of copy that contains some ABAP code. (changes to the relevant package can be saved only in local requests therefore transport of copy is recommended to transport the changes).
The changes appear correctly in Q system but for REG system the request neither appears in the queue nor be added to it.
Can someone advise where the problem is.
Cheers,
KC

Hi
When the REG system is not in the system landscape, probably you may not have Data & Co files in that system & you need to have those files separately in the REG system path & then import it.
Do consult Basis team on this issue.
Thanks,
Murali.

STMS: Transport control program tp ended with error code 0232

Dear ERP Gurus,
I just encountered problem with STMS in my PRD system. The import is just stuck up on "tp connecting to database". It won't continue unitl the system gives me this error message:
Transport control program tp ended with error code 0232
Errors: connect failed
The tp System log says:
ERROR: Connect to PRD failed (20090227135454, probably wrong environment)
I have verified that the suggestion in SAP Note 165708 has already been implemented in our DEV, QAS, and PRD instances.
Any idea why I am having this problem? Imports were running fine yesterday. Please help.
Your prompt response is highly appreciated.
Thanks a lot.
Best Regards,
Albert

Hi Albert,
First check import monitor and delete all requests from queue, which are still getting imported.
And go to /usr/sap/trans/tmp and mv all those tmp files to other location.
Then kill all OS jobs which are getting execute with tp.
Check all jobs are runnig fine, related to transportation. If not reschedule the same.
Then start importing.
Before doing this just check whether your stms related RFCs are working fine.
I think One of your RFC is getting struck. just try to change ip or hostname accordingly and try.
Regards
Nick Loy

DB13 ended with error during initilization tape

Similar Messages

Maybe you are looking for