Netweaver 7.0 EHP 1 upgrade on AIX platform runtime error

Dear all,
I am currently running on Netweaver 7.0 on IBM AIX / Oracle 10.2 platform.
I am trying to upgrade Kernel from 700 to 701 release patch level 39.
Unfortunately after extracting few of the exe files Example disp+work are
giving error as
could not load disp+work progarm
rtld : 0712-001 Symbol XTCgetprefixForURI was referenced
from module disp+work(), but a runtime definition of the symbol was not found
rtld : 0712-002 fatal error : exiting
I have faced this error in Windows platform where we need to run some microsoft DLL
as per SAP Note 684106 which clears these fatal runtime errors,
but this note applies to only windows platform .
Is there any note specific to AIX platform.
Please let me know ASAP.
Best Regards,
RR
Edited by: BASISRR on Sep 23, 2009 10:32 PM

Hello!
We get this problem on an HP-UX server as well....
After replacing the SAP Kernel (from NW700) to NW701 patch level 69,
during a EHP1 upgrade of this system, the dispatcher and dw-processes is not starting (using startsap/stopsap-scripts)!
In the dev_ms we get following error message:
"/usr/lib/hpux64/dld.so: Unsatisfied code symbol 'XTCGetPrefixForURI' inload module 'dw.sapSID_DVEBMGS20'."
We started the processes manuellay instaed, using "dw.sapSID_DVEBMGS20
pf=/sapmnt/SID/profile/SID_DVEBMGS20_sapsid", and succesfully upgraded
the ABAP-part to EHP1.
Do we have to patch HP-UX?
server:sidadm 32> uname -a
HP-UX server B.11.31 U ia64 3960812771 unlimited-user license
server:sidadm 33>

Similar Messages

  • /ASU/UPGRADE is terminated.(Runtime Error! disp+work.EXE)

    Dear all,
    I was doing sap upgrade .
    So I tried pre-check /ASU/UPGRADE, So workprocess was Terminated.
    Popup Appered .
    "Application Popup : Microsoft Visual C++ Runtime Library : Runtime Error!
    Program: D:\usr\sap\SKT\SYS\exe\run\disp+work.EXE
    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information."
    If not you know, please tell us how to proceed.
    Best Regards,
    Naofumi Yamazu
    from
    WIndows Server 2003 x64 R2/SP2
    Oracle 10.2.0.4 x64
    SAP R/3 46C SR1 ( Kernel 46D_EXT 32bit)
    SAP_BASIS / 20
    SAP_ABA / 20
    SAP_APPL / 16
    SAP_HR / 6
    ST-PI 2005_1_46C / 8
    To
    WIndows Server 2003 x64 R2/SP2
    Oracle 10.2.0.4 x64
    SAP ERP 6.0 SR3 ( Kernel 700 x64)

    SM21
                         System Log: Local Analysis of kokitmp                    1
    From date/time............. 10.11.2011 / 10:00:00
    To date/time...............   .  .     /
    User.......................
    Transaction code...........
    Terminal...................
    Task.......................
    Problem class..............
    Further restrictions.......
    Sorted ? ................ SOFI
    Pages with single entries 00000100
    With statistics............
                         System Log: Local Analysis of kokitmp                    2
    |Time    |Ty.|Nr|Cl.|User        |Tcod|MNo|Text                     Date : 10.11.11
    |10:51:53|DIA|00|000|DDIC        |/ASU|Q0E|Signal e06 received by operating system
    |10:51:53|DIA|00|000|DDIC        |/ASU|Q02|Stop Workproc 0, PID 860
    |10:56:36|RD |  |   |            |    |Q0I|Operating system call recv failed (error
    |        |   |  |   |            |    |   |no. 10054)
    |10:56:51|WRK|00|   |            |    |Q0Q|Start Workproc 0, Pid 3248
    |10:56:54|DIA|00|000|DDIC        |/ASU|R47|Delete session 001 after error 023
    |10:58:48|DIA|01|000|DDIC        |/ASU|Q0E|Signal e06 received by operating system
    |10:58:49|DIA|01|000|DDIC        |/ASU|Q02|Stop Workproc 1, PID 1620
    |11:00:33|RD |  |   |            |    |Q0I|Operating system call recv failed (error
    |        |   |  |   |            |    |   |no. 10054)
    |11:00:51|WRK|00|   |            |    |Q0Q|Start Workproc 1, Pid 8348
    |11:00:51|DIA|01|000|DDIC        |/ASU|R47|Delete session 002 after error 023
    |11:06:11|DIA|01|000|DDIC        |/ASU|Q0E|Signal e06 received by operating system
    |11:06:11|DIA|01|000|DDIC        |/ASU|Q02|Stop Workproc 1, PID 8348
    |11:07:11|WRK|00|   |            |    |Q0Q|Start Workproc 1, Pid 2880
    |11:07:11|DIA|01|000|DDIC        |/ASU|R47|Delete session 002 after error 023
    |11:27:19|DIA|00|   |            |    |Q02|Stop Workproc 0, PID 3248
    |11:27:19|RD |  |   |            |    |Q0I|Operating system call recv failed (error
    |        |   |  |   |            |    |   |no. 10054)
    |11:27:20|DIA|01|   |            |    |Q02|Stop Workproc 1, PID 2880
    |11:27:20|BTC|09|   |            |    |Q02|Stop Workproc 9, PID 428
    |11:27:20|DIA|02|   |            |    |Q02|Stop Workproc 2, PID 2088
    |11:27:20|BTC|12|   |            |    |Q02|Stop Workproc12, PID 356
    |11:27:20|BTC|11|   |            |    |Q02|Stop Workproc11, PID 2812
    |11:27:20|DIA|04|   |            |    |Q02|Stop Workproc 4, PID 1864
    |11:27:20|DIA|03|   |            |    |Q02|Stop Workproc 3, PID 268
    |11:27:20|BTC|10|   |            |    |Q02|Stop Workproc10, PID 412
    |11:27:20|SPO|13|   |            |    |Q02|Stop Workproc13, PID 2340
    |11:27:23|ENQ|08|   |            |    |Q02|Stop Workproc 8, PID 196
    |11:27:23|UPD|06|   |            |    |Q02|Stop Workproc 6, PID 3032
    |11:27:23|UPD|07|   |            |    |Q02|Stop Workproc 7, PID 456
    |11:27:23|UP2|14|   |            |    |Q02|Stop Workproc14, PID 2256
    |11:27:23|UPD|05|   |            |    |Q02|Stop Workproc 5, PID 2292
    |11:27:26|DP |  |   |            |    |Q0M|Message server disconnected
    |11:27:26|DP |  |   |            |    |Q05|R/3 System stop, dispatcher PID 28
    |11:27:27|MS |  |   |            |    |Q02|Stop Msg Server, PID 1328
    |11:28:04|DP |  |   |            |    |E10|Buffer SCSA Generated with Length 4096
    |11:28:04|DP |  |   |            |    |Q00|R/3 System start, SAPSYSTEM 00, dispatcher
    |        |   |  |   |            |    |   |PID 2596
    |11:28:04|MS |  |   |            |    |Q01|Start Msg Server, 1 times since system
    |        |   |  |   |            |    |   |startup. PID 1272
    |11:28:04|DP |  |   |            |    |Q0K|Connection to message server (on kokitmp)
    |        |   |  |   |            |    |   |established
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 1, Pid 9200
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 4, Pid 684
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 9, Pid 1748
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc13, Pid 404
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 7, Pid 1840
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 0, Pid 8852
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 2, Pid 2408
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc10, Pid 1264
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc11, Pid 2960
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 8, Pid 2192
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 5, Pid 8912
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 6, Pid 1796
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc14, Pid 1096
    |11:28:04|RD |  |   |            |    |S00|SAP Gateway Started (PID: 5152)
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc 3, Pid 8860
    |11:28:04|WRK|00|   |            |    |Q0Q|Start Workproc12, Pid 892
    |11:28:05|DIA|00|   |            |    |BB0|Buffer TABL started with 6000000 bytes
    |11:28:05|DIA|00|   |            |    |BB0|Buffer TABLP started with 002048000 bytes
    |11:28:05|DIA|00|   |            |    |BB0|Buffer EIBUF started with 4096k bytes
    |11:28:05|DIA|00|   |            |    |BB0|Buffer CUA started with 3000k bytes
    |11:28:05|DIA|00|   |            |    |BB0|Buffer CALE started with 500000 bytes
    |11:28:05|UPD|07|   |            |    |E10|Buffer RSCPCCC Generated with Length
    |        |   |  |   |            |    |   |3000000
    |11:28:07|DIA|00|000|SAPSYS      |    |A10|Initialization complete
    |11:28:28|DIA|00|000|SAPSYS      |    |AB0|Run-time error "ASSIGN_LENGTH_0" occurred
    |11:28:29|DIA|00|000|SAPSYS      |    |AB1|> Short dump "111110 112828 kokitmp SAPSYS
    |        |   |  |   |            |    |   |" generated
    |11:28:29|DIA|00|000|SAPSYS      |    |D01|Transaction termination 00 671 (
    |        |   |  |   |            |    |   |ASSIGN_LENGTH_0 20111110112828kokitmp
    |        |   |  |   |            |    |   |SAPSYS 0001 )
    |11:28:42|DIA|00|000|DDIC        |/ASU|Q0E|Signal e06 received by operating system
    |11:28:42|DIA|00|000|DDIC        |/ASU|Q02|Stop Workproc 0, PID 8852
    |11:29:24|WRK|00|   |            |    |Q0Q|Start Workproc 0, Pid 2420
    |11:29:25|DIA|00|000|DDIC        |/ASU|R47|Delete session 002 after error 023
    |11:33:28|DIA|00|000|SAPSYS      |    |AB0|Run-time error "ASSIGN_LENGTH_0" occurred
    |11:33:28|DIA|00|000|SAPSYS      |    |AB1|> Short dump "111110 113328 kokitmp SAPSYS
    |        |   |  |   |            |    |   |" generated
    |11:33:28|DIA|00|000|SAPSYS      |    |D01|Transaction termination 00 671 (
    |        |   |  |   |            |    |   |ASSIGN_LENGTH_0 20111110113328kokitmp
    |        |   |  |   |            |    |   |SAPSYS 0001 )
    |11:38:24|DIA|00|000|SAPSYS      |    |GC2|RSALSUP5 cancelled due to timeout
    |11:44:33|DIA|01|000|DDIC        |/ASU|Q0E|Signal e06 received by operating system
    |11:44:33|DIA|01|000|DDIC        |/ASU|Q02|Stop Workproc 1, PID 9200
    |11:45:04|RD |  |   |            |    |Q0I|Operating system call recv failed (error
    |        |   |  |   |            |    |   |no. 10054)
    |11:45:04|WRK|00|   |            |    |Q0Q|Start Workproc 1, Pid 8780
    |11:45:04|DIA|01|000|DDIC        |/ASU|R47|Delete session 001 after error 023
    Reading:
    Number of records read.........       1346
    Number of records selected.....         82
    Old records skipped............       1264
    Further selection:
    Number of records read.........         82
    Number of records selected.....         76
    Parameter records suppressed...          6
    Number of records printed......         76
    End of system log
                         System Log: Local Analysis of kokitmp                    3
                        C o n t e n t s
    Contents              Page              Start            End
    Selection criteria     1
                           2        10.11.2011  10:51:53 - 11:45:04
    Contents               3
    End of program  -

  • 10g upgrade on AIX platform

    I am just wondering whether someone else has already done a similar task (from 8.1.7.4 to 10.1.0.4 on AIX 5.2)...Which are the main risks or issues in doing this job?
    I have already done a research within this forum, Metalink and Web but nothing / none seems to do the same job.
    Otherwise could you please point me to useful articles on this subject?
    Thanks in advance

    Check this document:
    Note:263809.1 - Complete checklist for manual upgrades to 10gR1 (10.1.0.x)
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=263809.1
    Ciao, Aron

  • Can we install SAP Netweaver 2004s, without installing ABAP engine on AIX?

    Hi,
    Can we install SAP Netweaver 2004s, without installing ABAP engine on AIX?
    Thanks

    Hi
    Yes you can install java engine.Run sapinst from installation master cd and select only java engine installation.There will be check boxes abd you have to choose java engine.Also check the nwo4s installation guide.It will guide you throughly.Keep in mind to use correct jdk required for your kind of installatiom.
    Reward points if useful

  • ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative

    Hi Basis Expert,
    while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
    Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
    Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
    We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
    Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
    Hope anybody can share a bit your experience on this issue. we try search the note and  find the forum but no luck.
    Thanks

    Hi,
    > 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
    > 2EETG011 "No shadow system""DB-connect not against shadow tables !"
    >
    It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
    http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
    Thanks
    Sunny
    Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM

  • EHP 7 upgrade & Mopz in Solman 7.1 SP 8

    Hi Everyone,
    I am currently working on EHP 7 upgrade for my ECC 6 EHP 6 system. I began my work in ECC with SLD data push and SMSY, LMDB config, in Solman now moved on with MOPZ config to download EHP SPS. I have a query here, is it important to have the entire system data updated with SMSY and LMDB in Solman? i understand that MOPZ checks the current system Patch level from SMSY/LMDB and based on our target selection it calculates and recommends. just wondering how exactly it happens!. Bacause we have our BO system and few other non SAP systems in the landscape that are not updated with the SMSY/LMDB but they also should be considerd for the upgrade to check if there are dependencies.
    so my question is, do we have to push data from non sap also and maintaine in SMSY and LMDB before we perform EHP SPS download from MOPZ?
    other question is, if we perform upgrade in a ECC Sandbox environment (usually a copy of Production), it is not necessary to have sandbox for Portal, PI and other systems. so what is the recommended approach here? do we have to select the Developement  ECC system from MOPZ so that we will have other Dev systems (PI, Portal.,..etc) present in the SMSY & LMDB and MOPZ recommendation will be perfect?
    please help me understand this
    Thanks,
    Shiv

    Instead of reviewing SMSY, you should switch over to the LMDB as it is the future for system data in SolMan.
    The reason its telling you ERP 6.0 SPS25 is because it is not taking into account your Ehp, SAP still has to support customers who haven't taken the Ehp (perhaps unicode issues, 32 bit to 64 bit, etc) so this is a way to compare.  I found a bar graph that explained this in a very simple picture, however I can't find it online and leads me to believe I read/saw it in a book.  Also think of this my company is currently updating ECC from Ehp 5 SPS 4 to Ehp7 SPS 4, the SPS are the same due to the Ehp change and resetting the SPS counter back to 0, but in mopz I believe it shows SPS 28 or 29 for ECC 6.0; so essentially there is nothing you can or need to fix for the system data.  If this is still confusing I will try to track down the bar graph example I saw.
    As for logical components you can create your own (and is advised to do so as SAP could remove entries on you during a SolMan upgrade) so you could list it as z_ERP or zEhpERP or z_ECC; however it makes sens to you and your co-workers/customer, when you manage the system and the button that allows you to configure the system, the first section in the new window stays red until you assign a logical component to the system.  So you might already have something assigned to the system(s).
    SAP doesn't list it as BO, and I'm not sure if you can run a successful mopz on BO systems; if you leverage the PAM at SAP you can track down dependencies.  I also believe Process Orchestration is only 7.3/7.31/7.4 which is compatible with Ehp 7.
    SAP PAM:  http://service.sap.com/pam
    As for BO, do you have the following under the SWDC?
    Installations and Upgrades - B" SBOP BI platform (former SBOP Enterprise)" SBOP BI PLATFORM (ENTERPRISE)" SBOP BI PLATFORM 4.1

  • SAPLFAGL_ITEMS_SELECT runtime error in FAGLL03 after ECC EHP 7 upgrade

    Hi all,
    We have recently upgraded to SAP ECC to EHP7, after this we are getting SAPLFAGL_ITEMS_SELECT runtime error in FAGLL03 report.
    Runtime error is not about a time out
    I have searched for a note but could not find any on this problem.
    Information on where terminated
        The termination occurred in ABAP program "SAPLFAGL_ITEMS_SELECT", in
    "FAGL_GET_ITEMS_BSEG". The main program
        was "FAGL_ACCOUNT_ITEMS_GL ".
        In the source code, the termination point is in line 412 of (Include)
        program "LFAGL_ITEMS_SELECTU08".
    Thanks in advance,

    Hi,
    Check this SAP note1578577 - FAGLL03: Dump DBIF_RSQL_INVALID_RSQL. Another one is 1728986. Cannot check further as I am not aware of exact patch level.
    If this does not help kindly raise it to SAP as dump is in standard object.
    Regards,
    Anand Raichura

  • Netweaver Upgrade with EPHI - PostProcesing - Sintax error

    HI Experts
    Im using EPHI to upgrade my BI 7.0 SPS20 to BI EHP1 SPS5. After reach the POSTPROCESSING step,
    the tool ask to run SPAU check on the system.
    When i execute it SPAU load, but when i try to Reset to original any obj ( i have 2 reset ) the system
    dumps  with the following sintax error :
    " Runtime Errors         SYNTAX_ERROR                                                                
    Date and Time          02.10.2009 23:00:34  " 
    Short text :Syntax error in program "CL_I18N_BIDI==================CP"
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be                         
          terminated because it has                                                                    
         come across a statement that unfortunately cannot be executed.                                                                               
    The following syntax error occurred in program                                                
          "CL_I18N_BIDI==================CP " in include                                               
          "CL_I18N_BIDI==================CCAU " in                                                     
           line 2: A class already exists with the name "LCL_UNITTEST_I18N_BIDI".
    I check the logs in .../abap/log/ for ADJ errors but all the seems to be OK (no errors or warnings).
    Could you kindly give some advices, Please
    Daniel
    Edited by: Daniel Ayarza on Oct 3, 2009 3:38 AM

    FULL DUMP
    Runtime Errors         SYNTAX_ERROR                                                                
    Date and Time          02.10.2009 23:00:34                                                                               
    Short text :Syntax error in program "CL_I18N_BIDI==================CP"                                                                               
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be                         
          terminated because it has                                                                    
         come across a statement that unfortunately cannot be executed.                                                                               
    The following syntax error occurred in program                                                
          "CL_I18N_BIDI==================CP " in include                                               
          "CL_I18N_BIDI==================CCAU " in                                                     
         line 2:                                                                               
    "A class already exists with the name "LCL_UNITTEST_I18N_BIDI"."                              
    The include has been created and last changed by:                                             
         Created by: "SAP "                                                                               
    Last changed by: "SAP "                                                                       
         Error in the ABAP Application Program                                                                               
    The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be                         
          terminated because it has                                                                    
         come across a statement that unfortunately cannot be executed.                                                                               
    Error analysis                                                                               
    The following syntax error was found in the program                                           
          CL_I18N_BIDI==================CP :                                                           
         "A class already exists with the name "LCL_UNITTEST_I18N_BIDI"."                              
    Trigger Location of Runtime Error                                                                  
         Program                                 CL_GUI_ALV_GRID===============CP                       
         Include                                 CL_GUI_ALV_GRID===============CM05S                    
         Row                                     1                                                      
         Module type                             (METHOD)                                               
         Module Name                             CHECK_FOR_BIDI_FLAG                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    >>>>> method CHECK_FOR_BIDI_FLAG.                                                                  
         2                                                                               
    3   check CL_I18N_BIDI=>BIDI_CTRL_CODES_ACTIVE eq abap_true.                                   
         4                                                                               
    5   data: fcat type lvc_s_fcat,                                                                
         6         bidi type lvc_s_bidi_flag,                                                           
         7         ret  type i.                                                                               
    8                                                                               
    9   clear mt_bidi_flag.                                                                        
        10                                                                               
    11   loop at m_cl_variant->mt_fieldcatalog into fcat.                                           
        12     check not fcat-dd_roll is initial.                                                       
        13                                                                               
    14     bidi-fieldname = fcat-fieldname.                                                         
        15     CALL METHOD cl_i18n_bidi=>get_bidi_flags                                                 
        16       EXPORTING                                                                               
    17         im_dtel        = fcat-dd_roll                                                        
        18       IMPORTING                                                                               
    19         EX_LTR_FLAG    = bidi-ltr                                                           
        20         EX_FILTER_FLAG = bidi-filter

  • Runtime Errors SYNTAX_ERROR in SAPLS_CODE_INSPECTOR after the ECC6.0 upgrad

    we recently upgraded our development test sandbox from 46C to ECC6.0 using downtime minimized strategy for practice purposes.After a sucessful completion of the upgrade we applied all the support packages successfully upto the latest available. Upon testing we found that everything else works fine except code inspector. Everytime we go to transaction sci we get syntax error
    Runtime Errors         SYNTAX_ERROR
    Date and Time          08/20/2008 08:26:29
    Short text
         Syntax error in program "SAPLS_CODE_INSPECTOR ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "????????????????????????????????????????" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLS_CODE_INSPECTOR " in
          include "LS_CODE_INSPECTORTOP " in
         line 11:
         ""SCI_DYNP" must be a flat structure. You cannot use internal tables, s"
         "trings, references, or structures as components. ."
         The include has been created and last changed by:
         Created by: "SAP "
         Last changed by: "CRENSHAWDP "
         Error in the ABAP Application Program
         The current ABAP program "????????????????????????????????????????" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Please eliminate the error by performing a syntax check
         (or an extended program check) on the program "SAPLS_CODE_INSPECTOR ".
         You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    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.
    r analysis
    The following syntax error was found in the program SAPLS_CODE_INSPECTO
    ""SCI_DYNP" must be a flat structure. You cannot use internal tables, s
    "trings, references, or structures as components. ."
    to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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
    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.
    tem environment
    SAP-Release 700
    Application server... "kiel"
    Network address...... "138.254.140.161"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "000B7B2ED600"
    Character length.... 8 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "kiel"
    Database type..... "ORACLE"
    Database name..... "UPD"
    Database user ID.. "SAPR3"
    Terminal................. "D800204486"
    Char.set.... "en_US.ISO8859-1"
    SAP kernel....... 700
    created (date)... "Jun 22 2008 20:58:25"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 166
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 16128
    EM...... 8379840
    Heap.... 0
    Page.... 40960
    MM Used. 705904
    MM Free. 3481488
    r and Transaction
    Client.............. 070
    User................ "CRENSHAWDP"
    Language key........ "E"
    Transaction......... "SCI "
    Transactions ID..... "48AB59A7D7E00112E10080008AFE8CA1"
    Program............. "????????????????????????????????????????"
    Screen.............. " "
    Screen line......... 0
    Information on where terminated
    Contents of system fields
    Name     Val.
    SY-SUBRC 0
    SY-INDEX 0
    SY-TABIX 0
    SY-DBCNT 0
    SY-FDPOS 0
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    SY-MSGTY
    SY-MSGID
    SY-MSGNO 000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20080820
    SY-UZEIT 082629
    SY-XPROG
    SY-XFORM
    Internal notes
        The termination was triggered in function "ab_genprog"
        of the SAP kernel, in line 1551 of the module
         "//bas/700_REL/src/krn/runt/abgen.c#10".
        The internal operation just processed is " ".
        Internal mode was started at 20080820082629.
        Program name.........: "SAPLS_CODE_INSPECTOR ".
        Error message........: ""SCI_DYNP" must be a flat structure. You cannot use
         internal tables, s".
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = 2684354560
    => Stack limit     = unlimited
    => Core limit      = unlimited
    => File size limit = unlimited
    => Heap address  = 0x11716f260
    => Stack address = 0xfffffffffff2a20
    => Stack low     =  0xfffffffffff2a20
    => Stack high    =  0xffffffffffff710
    => Stack Trace:
    #AixStack() at 0x1000a2474
    #CTrcStack2() at 0x1000a256c
    #rabax_CStackSave__Fv() at 0x1000d0e04
    #ab_rabax() at 0x1000cd7e4
    #ab_genprog() at 0x100b3d5f8
    #newload__FPCcP13TmpSubpoolDirUiPUi() at 0x1002194ac
    #ab_LoadProgOrTrfo__FPCcUiPUi() at 0x10021905c
    #ab_load() at 0x100218e2c
    #ab_LoadMainProg() at 0x100820d6c
    #dystartx() at 0x100ade944
    #dy_cdiag() at 0x100833174
    #ab_ctransaction__Fv() at 0x100ae1ef0
    #ab_retdynp__Fi() at 0x100821c98
    #ab_dstep() at 0x100821924
    #dynpmcal() at 0x100e932e0
    #dynppai0() at 0x100e905ec
    #dynprctl() at 0x100e99d48
    #dynpen00() at 0x100e8cc18
    #Thdynpen00() at 0x1000f9ed4
    #TskhLoop() at 0x1000fec7c
    #ThStart() at 0x100115890
    #DpMain() at 0x1017f4b14
    #nlsui_main() at 0x1018e2b6c
    We contacted SAP OSS about this problem and they suggested that we check our LS_CODE_INSPECTORTOP include in program SAPLS_CODE_INSPECTOR and revert it to the original version. We did that and still are getting this error. Any suggestions how to fix this issue. All advices are welcome.
    Thanks.
    Kamran

    Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
    Regards
    Juan

  • Is anyone using SAP Data Services 4.x on AIX platform?

    Just want to have an idea if anyone using Data Services 4.x on AIX platform
    I am interested in the following install
    Information Platform Services 4.1
    Data Services 4.2
    Information Steward 4.2

    Hi Sri,
    Please refer the below link regarding BODS installation in AIX platform.
    Installing BusinessObjects Data Services 4.0 on AIX
    Link:
    http://alexzy.blogspot.in/2012/04/installing-businessobjects-data.html
    Pre and post production steps of BODS 12.2.2 upgrade to BODS 4.1
    Link:
    http://scn.sap.com/docs/DOC-47411
    Thanks,
    Daya

  • Where can I download Sybase ASE 16 for AIX platform?

    I can't find the place to download Sybase ASE16 for AIX platform? Is anybody know where to download it?

    Hi Wei,
    You can get it in our SAP Software download & license keys
    https://websmp208.sap-ag.de/~form/handler?_APP=00200682500000002722&_EVENT=DISPLAY&_HIER_KEY=501100035870000019642&_HIER…
    Installations and Upgrades - A" SAP ADAPTIVE SERVER ENTERPRISE"  SAP ASE 16
    > Installations
    > AIX
    SAP ASE 16.0 -> AIX
    51047803 SAP ASE 16.0 - AIX 64-bit
    Enjoy it,
    Regards,
    Franklin

  • IPod touch is not recognized by Windows (with a connect to iTune screen) after OS 5.1.1 upgrade and received an 1602 error

    My iPod touch is not recognized by Windows 7 and will not appear on My Computer as a storage device after OS 5.1.1 upgrade and received an 1602 error.  My iPod is now having a connect to iTune screen.

    Error 1600, 1601, 1602: Try the following steps to resolve this error:
    Ensure proper USB isolation troubleshooting has been performed, and test with a known-good cable.
    Follow the steps listed for Error 1604.
    This error may be resolved by disabling, deactivating, or uninstalling third-party security, antivirus, and firewall software. See steps in this article for details on troubleshooting security software.
    http://support.apple.com/kb/TS3694#error1602

  • After Upgrade to latest iTunes, it will not open.Uninstall and reinstall did not help Getting this error message ''  Runtime Error R6034 '' An application has made an attempt to load the C runtime library incorrectly''. 3 windows PCs.1 vista, 2 windows7 7

        I upgraded to the latest iTunes 11.1.4, after a prompt from the iTunes store. But will not open after the upgrade. One of three error messages told me to reinstall. I did. Restarted and scanned.  But no help there. So I unistalled and re installed from Apples' website. The installation was okay as usual but still will not open. Keep getting the same error messages. '' Runtime Error R6034, ''  '' An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.''  That's the error messages I get when I try to open the New installed iTunes 11.1.4. Right now there is no iTunes on any of my PCs. Installed but will not open. Please Help.Thanks.
    Jonas.
    3 Windows PCs. Safari 5.1.5 ( One Laptop with Vista. Two Windows 7 64 bit on All in One Sony desktop PCs. )

    Try the following user tip:
    Troubleshooting issues with iTunes for Windows updates

  • ECC 6 SR3 upgrade I am getting following error at  RSVBCHCK

    2EETQ241 Errors found in logfiles - accumulated in file "PSVBCHCK.ELG"
    1EETQ203 Upgrade phase "JOB_RSVBCHCK_D" aborted with errors
    1 ETH010XRSVBCHCK: Check of open update requests
    2EETG050 Update records still exist - Please process.
    There is no SM13 nor SMQ1 entries in the system, also reorganiezed update records, also checked following.
    SQL> select * from sapr3.VBERROR;
    no rows selected
    SQL> select * from SAPR3.VBERROR;
    no rows selected
    SQL> select * from SAPR3.VBMOD;
    no rows selected
    SQL> select * from SAPR3.VBHDR;
    no rows selected
    SQL>
    Incase anyone had faced similar issues, and found a workarond please let me know
    thanks.

    Hi Mathew,
    Please check if your system has the ABAP program "RMCEXCHK" as per OSS Note  no. 1083709.
    Once you run this program, it exactly would let you know what are the areas which are causing the issues. Based on that you can empty out the LIS Set up tables.
    Also, can you please check the update program for LIS has emptied out the entries in SMQ1.
    Regards,
    Anil

  • Runtime Error in VL01N after upgrade from 4.6c to ECC 6.0

    hi, 
       We are doing a upgrade project from 4.6c to ECC 6.0 and when we are running the VL01n tcode and as soon as we hit enter in easy access screen its throwing a runtime error as " The key of internal table "XLIPS" contains components of type  'X' or "XSTRING". The "READ TABLE XLIPS" statement is not permitted for such tables in a unicode context'. The xlips is declared as:
    DATA: BEGIN OF XLIPS OCCURS 15.
    INCLUDE STRUCTURE LIPSVB.
    DATA: END OF XLIPS.
    so i have checked the lipsvb structure in that i dont find the key fields of type X or XSTRING all are of type CHAR 4. this LIPSVB is the Reference structure for  XLIPS and YLIPS.
    THANKS IN ADVANCE.

    Please  see the  Patch level of the  SD, FI ,etc...
    and  apply  it   the basis   should   find  it  out  .... for  ECC6.0   then  minimum level  of  patches  should  be   upgraded.
    please  ,login to help.sap.com  ... there  in the  search  see the  document   of the pateches  for the   ECC6.0 for SD & FI ... like wise  for  all  Modules  ....
    Reward  points if it is usefulll ...
    Girish

Maybe you are looking for

  • My ipod lost all of my songs

    my ipod lost all of the information for all the songs i had on my ipod... the songs are there because it is an 8g 4th generation ipod, but says it only has 4g of memory left... i had plugged it into my computer, but it wasn't registering, so i pulled

  • Inventory value increase

    Hi, (Initially wrongly posted this in BI and hence repeating here) Is there any way I can post a transaction to increase the inventory value ? We have a requirement. After the product is manufactured it (Wine) is kept in warehouse for curing purpose

  • Digital Signature on TDS certificate - Vendors

    Dear All, Their is possiblity to insert digital signature on TDS certificate given to employees(form 16), but is their any chance of inseting the digital signature on TDS certificate given to Vendors. Thanks & Regards Krishna Chaitanya

  • Error during Order confirmation

    Hi , Can anyone tell us whether can we do confirmation if there is a material shortage. IF order qty is 10 and there is material shortage for one of the rawmaterials and if we are trying to do confirmation by entering Yield qty as 10. Will system all

  • Interns! Employers! What would you consider to be essential knowledge for learning Illustrator?

    Hello all, I'm going to be a Teaching Assistant for an introductory vector graphics class at a university. I'm currently in the sorts of creating the curriculum for my tutorial sessions, which will primarily be technical demonstrations of various fea