Sm21 errors

I am getting following errors in sm21 marked red frequently.
1     Transaction Canceled TD 419 ( )
2     Perform rollback
3     Operating system call recv failed (error no. 131 )
4     Operating system call gethostbyaddr failed (error no. 0 )
5     Connection to user 22468 (C100015 ), terminal 100 (bom-cor-dsk8) lost
6     Delete session 001 after error 061
7     SQL statement violates database system restriction
8     Connection to user 13700 (T001176 ), terminal 110 (bom-cor-dsk2) lost
9     Communication error, CPIC return code 017, SAP return code 22
     > CPI-C function: CMINIT(SAP)                               
10     HTTP/RFC session has been deleted following timeout
how to solve them?

HI
many of the errors which you are getting are quite normal in many cases. Most of them will come when you cancell a job / terminate a transaction.
CPIC errors will come during RFC communication.These are mainly due to System load/huge data transfer through RFC e.t.c
also depends on the type of RFC you are using.
Mainly you need to look for ABAP dumps with errors related to Database , normally DBIF*** or SQL **** like that
Hope this helps..
Regards
Sreenath
Award points if it is useful

Similar Messages

  • SM21 - Error found in PBT environment, FM = SPBT_GET_CURR_RESOURCE_INFO

    Hi,
    During idoc processing we see following messages generated in SAP system log which complain that the servers are getting disconnects from message server..
    SM21 ::
    Error found in PBT environment, FM = SPBT_GET_CURR_RESOURCE_INFO
    > Failure checking whether server is active/inactive
    Documentation for system log message EK 1 :
    While processing parallel background tasks, the system discovered an
    error in the specified function module. The reason for the error is
    described in the corresponding system log entry.
    Failure checking whether server is active/inactive
    Documentation for system log message EK 5 :
    While processing "parallel background tasks", the system could not
    determine whether the application servers involved are active or
    inactive. This is possibly because the connection to the message server
    was lost.
    Please help me to resolve the issue.
    Thanks and Regards
    Mohsin

    Hello.
    May be I had the same problem, because in sm21 i saw analog message.
    As it appeared the qrfc (smqs) scheduler has problem (smqs - monitor) whith one of the instance included in my group:
    Name of AS Group (DEFAULT = All):        parallel_generators
    In transaction sarfc we founded the problem instance. This instance had red status "Error in configuration". We removed the problem instance from group parallel_generators. After this qrfc  scheduler worked succesfully.
    The instance had problem because parameter "Activated (0 or 1)" = 0 (sarfc configuration of qoutes). If you change this parameter to value 1, you can include the instance back to group.

  • SM21 Errors DIA 000 000 SAPSYS D01 Transaction Canceled 00 152

    OK I have done almost every search I c an think of in service.sap.com, here and in Google.  I have exhausted my mind... I can not figure out what is causing the problem.  Here is what I am seeing:
    14:16:12 DIA 000 000 SAPSYS            R68 Perform rollback
    14:17:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
    14:17:13 DIA 000 000 SAPSYS            R68 Perform rollback
    14:18:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
    14:18:13 DIA 000 000 SAPSYS            R68 Perform rollback
    14:19:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
    14:19:13 DIA 000 000 SAPSYS            R68 Perform rollback
    14:20:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
    14:20:13 DIA 000 000 SAPSYS            R68 Perform rollback
    14:21:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
    14:21:13 DIA 000 000 SAPSYS            R68 Perform rollback
    14:22:14 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
    14:22:14 DIA 000 000 SAPSYS            R68 Perform rollback
    Double clicking I see:
    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                  152
    Name or password is incorrect. Please re-enter
    No documentation exists for message 00152
    As you can see this is happening many times a second.  I have checked the batch jobs and can not see anything there.  I see that there is a incorrect name or password but where?  I can not dig it up.  This is a Netweaver 04 XI 3.0 box running on a HP-UX platform.  XI Seems to be running fine so I don't want to reset all the JAVA passwords.  Is there any way to trace this down.  I set the Trace on the Dialog process' to 3 but I can not decipher them.
    Please give me any advice as I am stuck.  This is not stopping us from working but it is getting hard to read through the logs in SM21 when this is none stop.
    Best Regards,
    Paul

    Hi
    The error
    14:17:13 DIA 000 000 SAPSYS D01 Transaction Canceled 00 152 ( )
    14:17:13 DIA 000 000 SAPSYS R68 Perform rollback
    Is basically a logon time error, when you try to logon through SAPGUI in dialog mode, the instance is 000 and logon takes place through dialog process 000.
    As SM21 log further says:
    Name or password is incorrect. Please re-enter
    This is the message you get at bottom screen of gui when you enter wrong user id or password.
    Many a times when user wrongly enter the invalid logon data this error is evident in SM21 log.
    Now in your case this is occuring every minute, so there might be some process which initiates a dialog logon to the system every minute but unable to do that.
    So in this case this could be the CCMS monitoring component on a remote system e.g. a Solution Manager system, which is monitoring your XI system and trying to login to get the data.
    Please check if this is possibility in your case.
    Hope this might help.
    Rahul

  • SM21 error messages

    Hi All,
    When I execute the SM 21 am getting the error messages like the following.
    When it accessed a file, the TemSe software received an unexpected
    error message from the operating system (or file system). The message
    contains the current file name and the value of the "errno" variables
    of the C system.
    Additional specifications for error number 9
    Name for errno number EBADF*
    No documentation available for error EBADF*
    Please suggest us
    Thanks
    Sravani

    Hi Sravani,
    Check the below SAP Note
    Note 39283 - ABAP debugger and SysLog F3V with errno 9
    Hope it helps.
    Veerendra.

  • Error when write data object in archiving (BW)

    HI:
    I am making an infocube archiving,this process is cancelled due to an error.
    the error is:
    Error E/S en fichero de archivo
    BW02sapmntBWPArchivingBWP_BW_0_BWCZRT_C05_20             BA        024
    Error al grabar un objeto de datos                                                    RSARCH      215
    El job ha sido cancelado tras excepción de sistema ERROR_MESSAGE.                                     00        564
    Please help me in this issue.
    Regards,
    Ernesto.

    Hi Ernesto:
    First you should try to write the message in English mi amigo! That way you will get answers, en español muy difícil que alguien te responda! ;-D
    Can you post the SM21 error message and if there any Short Dump (ST22)
    Regards,
    Federico

  • Process chains get an error when run analysis process

    When my PRD system‘s process chains run analysisi process, I  gets below error message:
    Error occurred when starting the parser: Error when opening an RFC connection (FUNCTION: 'R
    Message no. BRAINOLAPAPI011
    Diagnosis
    Failed to start the MDX parser.
    System Response
    Error when opening an RFC connection (FUNCTION: 'R
    Procedure
    Check the Sys Log in Transaction SM21 and test the TCP-IP connection MDX_PARSER in Transaction SM59.
    It's OK when i test the TCP-IP connection MDX_PARSER in Transaction SM59.
    The Sys Log in Transaction SM21(error part):
    M Wed Mar 19 09:22:50 2014
    M  *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35, r, ..) returned -14 [thxxexec.c
    M  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
    A  RFC 1878  CONVID 18933904
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    A  RFC> ABAP Programm: SAPLSTPA (Transaction: )
    A  RFC> User: JY-LKZ (Client: 900)
    A  RFC> Destination: CALLTP_AIX (handle: 8, DtConId: 530F4E5C30AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
    A  RFC SERVER> RFC Server Session (handle: 1, 68443927, {5328109B-5F5D-12A0-E100-8000C0A8642F})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
    A  RFC SERVER> Called function module: TMS_CI_START_SERVICE
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
    FUNCTION: 'RfcExecProgramKernel'
    RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35
    [abrfcio.c    9213]
    A  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE
    M
    M Wed Mar 19 09:23:15 2014
    M  *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61, r, ..) returned -14 [thxxexec.c
    M  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
    A  RFC 1878  CONVID 18968493
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    A  RFC> ABAP Programm: SAPLSTPA (Transaction: )
    A  RFC> User: TMSADM (Client: 000)
    A  RFC> Destination: CALLTP_AIX (handle: 3, DtConId: 530F4E7830AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
    A  RFC SERVER> RFC Server Session (handle: 1, 70212851, {53281195-8F75-0F10-E100-8000C0A8642F})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
    A  RFC SERVER> Called function module: TMS_CI_START_SERVICE
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
    FUNCTION: 'RfcExecProgramKernel'
    RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
    PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61
    [abrfcio.c    9213]
    A  {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE.
    ps.
    1、IT's everything ok in the development system.
    2、It’s ok when i repeat this analysis process .
    3、It’s ok when i run this analysis process in analysis process designer.
    4、Attachment is the sys log in sm21.
    Thanks everyone.

    Hi Vignesh.B,
    Yes,it's not user's problem . But i don't  think it APD's problem .Cause all APD has the same problem and .
    Below is one of APD souce and target :
    Hope this information  is useful .
    Regards,
    Lian

  • Refresh Runtime Error in TCODE DB02

    Hello Experts!
    Was just trying to refresh the statistics that I have for my DB Spaces in DB02, but I suddenly come up with this error. Can anyone tell me what this means and why this is suddenly happening (As I had no problems using this functionality just last week). Thanks!
    ST22 Error Log:
    Runtime Errors         DBIF_DSQL2_SQL_ERROR                                           
    Exception              CX_SY_NATIVE_SQL_ERROR                                         
           Occurred on     03/30/2009 at 11:11:51                                                                               
    SQL error "-727" occurred when executing EXEC SQL.                                                                               
    What happened?                                                                               
    The error occurred in the current database connection "DEFAULT".                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                              
    and make a note of the actions and input that caused the                              
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                        
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer              
    termination messages, especially those beyond their normal deletion                  
    date.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception will be dealt with in more detail               
    below. The exception, assigned to the class 'CX_SY_NATIVE_SQL_ERROR', was not         
    caught, which                                                                        
    led to a runtime error. The reason for this exception is:
                                                                                    How to correct the error                                                                               
    Database error text........: "INF-727: Invalid or NULL TBLspace number given to    
    dbinfo(dbspace)."                                                                 
    Triggering SQL statement...: "FETCH NEXT "                                         
    Internal call code.........: "[DBDS/NEW DSQL]"                                     
    Please check the entries in the system log (Transaction SM21).                                                                               
    You may able to find an interim solution to the problem                            
    in the SAP note system. If you have access to the note system yourself,            
    use the following search criteria:                                                                               
    "DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC                                     
    "RSINFTD1 " or "RSINFTD1 "                                                         
    "START-OF-SELECTION"                                                                               
    If you cannot solve the problem yourself, please send the                          
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                       
       To obtain this, select the "Print" function on the current screen.              
    2. A suitable hardcopy prinout of the system log.                                  
       To obtain this, call the system log with Transaction SM21                       
       and select the "Print" function to print out the relevant                       
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,                 
       supply the source code.                                                                               
    4. Details regarding the conditions under which the error occurred    
       or which actions and input led to the error.                                                                               
    SM21 Error Log:
    BY2 Database error -727 at FET                              
    BY0 > INF-727: Invalid or NULL TBLspace number given to     
    BY0 > dbinfo(dbspace).                                      
    R68 Perform rollback                                        
    AB0 Run-time error "DBIF_DSQL2_SQL_ERROR" occurred          
    AB1 > Short dump "090330 111151 gtbwspd 10002568 " generated

    Hi.
    I already had this issue and I solved by this way:
    My issue happened in the following SQL statement:
    94 EXEC SQL.
    SELECT MAX(A.NEXTSIZE)
    96 FROM SYSTABLES A, SYSFRAGMENTS B
    97 WHERE DBINFO('DBSPACE',B.PARTN) = :TS_CHECK-DBSNAME
    98 AND A.PARTNUM = 0
    99 AND A.TABID = B.TABID
    100 INTO :MAXEXT
    101 ENDEXEC.
    1) Please run the following sql query:
    select fragtype, tabid, partn from sysfragments where partn = 0
    2) Figure out which table it is:
    select tabname from systables where tabid =<tabid>
    3) Check the indexes of that table with oncheck -cI.
    4) If you found indexes DISABLED, then you should enable them again.
    5) To solve the problem you can:
    -enable dropped indexes:
    set indexes,constraints for <table> enabled;
    -rebuild the indexes
    Afterwards this operation should be corrected.
    I hope I could be helpful.
    Thanks,
    Walter Oliveira.

  • System restarted with messages "Error adding a request to the dispatcher ""

    Hi,
    Today ECC system restarted. The following error messages were found in SM21
    " Error adding a request to the dispatcher queue ( UP2)
    Request (type UP2) cannot be processed "
    I cheched Queue information for this system by navigating to Goto-->Server name --> information -->Queue information
    NOWP     0     21     2,000     25,181,608     25,181,608
    DIA     0     13     2,000     3,384,734     3,384,734
    UPD     0     29     2,000     185,673     185,673
    ENQ     0     69     2,000     18,928,082     18,928,082
    BTC     0     0     2,000     0     0
    SPO     0     3     2,000     5,539     5,539
    UP2     0     2,000     2,000     107,232     107,232
    This is the first time a error of this kind is noticed. Can some tell me what could be the root cause and how to fix this issue?
    Regards,
    Chaitanya.

    hello,
    in the UPD queue you see:
    UP2 0 2,000 2,000 107,232 107,232
    indicating that in a moment there were 2000 records in the dispatcher queue.
    In SM13 you recognize the records which update V2 are not procesed yet, they have the status "V1 processed".
    Are the UP2 work processes occupied?
    kind regards,
    Mercedes

  • SCM WP trace file error message

    Hi,
    We are getting the below error in our work process trace files for our SCM 5.1 system
    Tue Dec 30 17:35:51 2008
      ***LOG Q0I=> NiPGetHostByName: hostname 'OPTSERVER' not found: gethostbyname [niuxi.c 1470]
    At same time, we have system log entries as below:
    19:07:34 BTC  031 009 APOADMIN                Q0  I Operating system call gethostbyname failed (error no. 0 )
    Documentation for system log message Q0 I :
    The specified operating system call was returned with an error.
    For communication calls (receive, send, etc) often the cause of errors
    are network problems.
    It could also be a configuration problem at operating system level.
    (file cannot be opened, no space in the file system etc.).
    Does anyone know about this?? The RFC connections between APO server and Optimizer server are working fine and there is no issue. However, for any dialog/background process we are getting the error above. Please suggest.
    Regards,
    Sandeep.

    Hi Senthil,
    Thanks for your reply. As in the note 388193 that you have mentioned job /SAPAPO/OM_REORG_DAILY is executed daily in our system and there does not seem to be any issue with optimizer installation as optimizer is working fine and there is no connection problem with scm system.
    However the SM21 errors keeps coming.
    13:48:15 BTC  031 009 APOADMIN                Q0  I Operating system call gethostbyname failed (error no. 0 )
    13:54:38 BTC  031 009 APOADMIN                Q0  I Operating system call gethostbyname failed (error no. 0 )
    14:01:24 BTC  031 009 APOADMIN                Q0  I Operating system call gethostbyname failed (error no. 0 )
    14:07:59 BTC  031 009 APOADMIN                Q0  I Operating system call gethostbyname failed (error no. 0 )
    Regards,
    Sandeep

  • ECC6 Error

    Hi All,
    we have ECC 6 Server on Oracle database 10g, wehen we access SM21, error logs daily we find the error
    BTC 015 R1  9 Initialization ALERTS Failed, Return Code 000249
    it started in the midnight and it scheduled on hourly basis
    Please help me to resolve the issue
    thanks & Regds
    manish

    Hi manoj,
    3 BTC are Configured and there is no OM configured ,I have checked in Work directory , It is Showing Shared mememory segment problem
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    ERROR => ShmGet: Shared Pool Space exhausted. PoolKey=10 [shmux.c      2369]
    ERROR => AlCreateAttachShm_AS: ShmCreate (SHM_CREATE) rtc = 1 [alxxappl.c   768]
    ERROR => CCMS: sAlInit: could not create/attach shared memory key 13 (rtc = 249) [alxx.c       1187]
    ERROR => AlDpAdmInit: sAlInit rtc = 249 [alxx.c       555]
    ***LOG R19=> ThInit, AlThAdmInit` ( ALERTS 000249) [thxxhead.c   1730]
    please help
    Thanks & Regds
    manish

  • CO-PA extraction

    I have couple of questions in FI and CO-PA....
    1. What happens when we intialise the delta for the first time in CO-PA? I read some where saying " Initialiation should be performed on Summarization level which we can do in KEDV transaction...what exactly it means??? is there any special way to do that??
    2. Even for FI when we intialise the delta for the first time will it gets dataset from Line item tables or is there any medium like summarization level for FI also??
    3. What if Delta is lost in CO-PA? how to do reinit???
    4. Same with FI. I was told if delta is lost in FI then we need to make an entry in TPS31 table??? cos history will be lost in BWFI_AEDAT table???
    5. I am not clear with intialisation for both Cost based and account based....
    In the document it says for account based initialisation should be performed on Summarization level which can be done in KEDV? and for Cost based it says data can only be read from Summarization level if characteristics from line item is not selected??/

    Dear Srini
    could you be more precise about the problem? E.G. ST22, SM21, Error Code ...
    Be aware that if you have two development clients (one for customizing and one for data) the Extractor will work only on one of them: see note 354760 for more details. This is the main problem I remember we had with CO-PA, a part from performance ...
    Hope it helps
    GFV

  • Update was terminated on WSM8 " POSTING_ILLEGAL_STATEMENT"

    Hi all
    our system is ecc6 with IS -retail activated. support Stack level is 12 and database is oracle , os is windows.
    We are getting express document error " Update was terminated " when executing WSM8 . on ST22, we are getting following error
    POSTING_ILLEGAL_STATEMENT . We applied note 1053491
    which is similar to the issue but it does not solve.
    Here are the st22 dump details
    Runtime Errors POSTING_ILLEGAL_STATEMENT
    Date and Time 24.04.2008 19:03:48
    Short text
    Statement "COMMIT" is not allowed in this form.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSYDB" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    There is probably an error in the program
    "SAPLSYDB".
    This program is triggered in the update task. There, the
    following ABAP/4 statements are not allowed:
    - CALL SCREEN
    - CALL DIALOG
    - CALL TRANSACTION
    - SUBMIT
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "POSTING_ILLEGAL_STATEMENT" " "
    "SAPLSYDB" or "LSYDBU27"
    "DB_COMMIT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    this is sm21 error log
    Time      Type      Nr      Clt      User      TCode      Grp      N      Text
    18:09:55      UP1      006      600      SAUGATA             AB      0      Run-time error "POSTING_ILLEGAL_STATEMENT" occurred
    Run-time error "POSTING_ILLEGAL_STATEMENT" occurred
    Details
    Recording at local and central time........................ 24.04.2008 18:09:55
    Task......      Process      User......      Terminal      Session      TCode      Program      Cl      Problem cl      Package
    05460      V1 Update Task No. 006      SAUGATA      LB-TULIP      1                    T      Transaction Problem      SABP
    Further details for this message type
    Module nam      Line      Error text
    thxxvb      1346      ThVBCheckCommit
    Documentation for system log message AB 0 :
    The specified runtime error has occurred in the system.
    Parameter
    abcdefghijklmnopqrstuvwxyz .. POSTING_ILLEGAL_STATEMENT
    Technical details
    File      Offset      RecFm      System log type      Grp      N      variable message data
    66      160740      l      Error (Module, Row)      AB      0      ThVBCheckCommit thxxvb 1346
    Please check and let me know if you need more details.

    Hi Jelena,
    Here is the source code extract  where error is .   Will this be a standard sap program or a program modified by abaper?.
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    1 FUNCTION DB_COMMIT.                                                                               
    2 *"----
        3 ""Lokale Schnittstelle:                                                                    
        4 *"----
        5                                                                               
    6   EXEC SQL.                                                                               
    >>>>>     COMMIT WORK                                                                               
    8   ENDEXEC.                                                                               
    9                                                                               
    10 ENDFUNCTION.                                                                               
    Can you share some more tips on  this.
    Thank you once again for that help full answer.

  • St04 z/os system log

    Hi!
    We have SAP  on IBM DB2 UDB for z/OS (SAP Web AS 6.40 SR1,DB2 V8).
    When I logon with tso user on sap and start sto4 --> z/os system log, i see error in sm21:
    Error executing stored procedure DSNACCJS - MES_TXT: __login() unsuccessful :  EDC5164I SAF/RACF error 
    What's the problem?

    Hello Zoran,
    Check out this link, where the error is pointed by IBM.
    Hope this helps in your issue.
    http://www-1.ibm.com/support/docview.wss?uid=isg1OA11753
    Rgds,
    Sri
    (Thanks for any points you assign )

  • Transaction Canceled BT 510

    Hello All,
    I am getting many system log " Transaction Canceled BT 510" in client 000 user sapsys. There are no dumps occuring and no BTC jobs failing. the system log entry shows. can some body provide me some information about it.
    ============================
    Failed to read step table
    &CAUSE&
    When a job is started, the individual steps are processed in sequenti
    order.  For this to function, the steps must be read in their defined
    order and then processed.
    The appearance of this message means that the read access to the step
    in the current job failed.
    &SYSTEM_RESPONSE&
    The job involved cannot be started normally, and is therefore set to
    status "Cancelled".  In addition, this message is recorded in the
    corresponding job log.
    &WHAT_TO_DO&
    Check the SAP system log for messages that occurred around the time o
    this message.  In particular, look for messages from the database
    interface, which will normally describe the cause of the problem more
    precisely.
    If no database-specific log entries exist for this problem, please
    contact your SAP system administrator for further analysis.
    ============================

    Hello Kiran,
    While deleting any entries you need to be careful enough. Please first check on TEST system before proceeding to DEV to avoid unnecessary complications.
    you can also delete the entries from SQL level.
    DELETE FROM SAPR3.TBTCO WHERE JOBNAME = 'XXXXX' AND RELUNAME = 'YYYYYY' AND SDLSTRTDT > 'YYYYMMDD'
    Please note that SAP will not advise and support if anything goes worng.
    when you got SM21 error log "Transaction Canceled BT 510", did you check SM50, SM12, workprocess logs and alert SID log  to drill down the issue further?
    Thank you,
    Shyam

  • Cannot open audit file

    Hello Friends,
    As a part of re-platform activity our production application servers are moved from AIX to Windows operating system. But CI is still in AIX.
    From the next day of re-platform activity we are getting the SM21 error log as "Cannot open audit file: /migrate/<SID>/audit/log\<DATE>.AUD. This log is generating only on Windows application servers and not on CI(AIX).
    All the file systems are properly mounted from AIX to Windows.
    DIR_AUDIT parameter value also maintained in default profile as /migrate/<SID>/audit/log
    Can any one please suggest
    Thanks in advance,
    Mahi.

    Hi ,
    Some parameters which might help you for this"
    Name Description
    FN_AUDIT                Name of security audit file audit_++++++++
    DIR_AUDIT                Directory for security audit files
    *rsau/enable                Enable Security Audit*
    rsau/max_diskspace/local      Maximum space for security audit file
    rsau/max_diskspace/per_day      Maximum size of all security audit files per day
    rsau/max_diskspace/per_file      Maximum size of one single security audit file
    rsau/selection_slots           Number of selection slots for security audit
    rsau/user_selection           Defines the user selection method used inside kernel functions
    Also refer to the SAP Note:: 539404 - FAQ: Answers to questions about the Security Audit Log
    Please do the cross check of the related param's and also check the SAP note which might be very helpful.
    Regards,
    Sanjeev Nagalikar

Maybe you are looking for