Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Latest Forum Threads in SAP NetWeaver Technology Platform

older | 1 | .... | 9 | 10 | (Page 11) | 12 | 13 | .... | 76 | newer

    0 0

    Hello communities,

     

    We are in the step to upgrade our SRM System 5.5 to SRM 7.0 EHP2

     

    We did the following :

     

    1. Generate the XML via the MOPZ (Option Upgrade with Enhancement Package Installation)

    2. Download all the files links to this XML stacks

     

    The current release and the target release were well regognize. by the MOPZ

     

    3. Put all the files in a download directory with the XML

    4. Start the SUM (Software Update Manager 1.6)

    5. Pass all the preparation steps

    6. The source release and the target relese were well detected byt SUM

     

    But in the phase PREP_INPUT/SELSTACKXML_ASK

     

    I've got the following error :

     

    ETQ373 parameter "EV_MESSAGE" = "The stack configuration is not valid for the system XXX, inst.-no. XXXXXXX"

     

    In the log SELSTACKXMLA.LOG (I can see)

     

    1 ETQ359 RFC Login to: System="XXX", AsHost="XXXX" Nr="00", GwHost="XXXXX", GwService="sapgw00"

    2 ETQ232 RFC Login succeeded

    4 ETQ010 Date & Time: 20121129154338

    1 ETQ233 Calling function module "OCS_API_GET_STACK_INFO" by RFC

    2 ETQ373 parameter "IV_STACK_GUID" = ""

    2 ETQ373 parameter "IV_STACK_FILE" = "/usr/sap/XXX/SUM/abap/tmp/SMSDXML_XXX_20121128121003.255.xml"

    1 ETQ234 Call of function module "OCS_API_GET_STACK_INFO" by RFC succeeded

    4 ETQ010 Date & Time: 20121129154338

    2 ETQ399 Table ET_CVERS_INITIAL (#0):

    2 ETQ399 Table ET_CVERS_EXPORT (#0):

    2 ETQ399 Table ET_CVERS_TARGET (#0):

    2 ETQ374 parameter "EV_RC" = "8"

    2 ETQ373 parameter "EV_MESSAGE" = "The stack configuration is not valid for the system XXX , inst.-no. XXXXXX"

    4 ETQ399 ... Error reading stack info (rc = 8, reason = "The stack configuration is not valid for the system XXX , inst.-no. XXXXX")

    4EETQ399 Stack configuration not useable: The stack configuration is not valid for the system XXX , inst.-no. XXXXX

     

    So I'm wondering if it is really the good way to upgrade our SRM system ?

     

    I used the upgrade guide for SRM 7.0 EHP2 Abap + upgrade guide for SRM 7.0 EHP2 Java + SUM Update Guide (+ some OSS notes) and I've found no trace about the "Export DVD", "Java DVD" etc...all set of DVD that I've used in the past for upgrading our ECC system (1 year ago).

     

    Is that really the path to upgrade our SRM System ???

     

    This sound  strange for me that my system could be upgraded with so less bunch of files (93 files were downloaded with the XML), I have the feeling that it looks more  the files needed for an EHP update but not for an update !

     

    But then why in the "SUM" it's recommended to follow this path ???

     

    Anyone has already use the "SUM" to do this kind or upgrade ?

     

    Thanks a lot  for your input :-)

     

    Dom./


    0 0

    HI everybody,

     

    I am using BAPI_ACC_DOCUMENT_POST and I am getting the error in topic. You should know that this happens while I am calling a report that encapsulates this BAPI, from a BTE FM SAMPLE_process_00001120, to create a 2nd FI document in parallel of the 1st one I am creating using FB01 (double creation of FI doc ). I get data from BKPF and BSEG parameters amid FB01 process and fill BAPI structures accordingly.

     

    You should also know that when I run this BAPI in a separate report with the same that from BKPF and BSEG but hard coded, I get my document posted without any problem. It is a bit weird!

     

    those reports are:

     

    ZTEST_DOC_POST_ALT data are hard coded, it works.

     

    ZTEST_DOC_POST data got from BKPF and BSEG in FB01 process, it leads to the error in subject.

     

    Thanks in advance for your reply,

    Abder


    0 0

    HI Experts,

     

    There is one Function module called in a Report . I am not able to open this FM in se37 and get message that FM does not exist.

    However this FM gives the output by creating entry in a table as I checked in debugging of report. Debugger also does not go to the source code of this FM.

    Does anyone know how to see source code of this Function Module ?

    SE37 does not help.

     

     

    Regards,

    Pradeep


    0 0

    Hello,

     

    We performed an upgrade to our BW 7.01 environment. We followed the ASU recomendations prior and after the upgrade. Everything seems to be OK except for the fact that we are unable to retrieve data from the source systems. The connections are OK and "Activate" and "Check" give positive feedback.

     

    I've attached the error we're receiving in the BW monitor regarding the process.

     

    Any ideas of what can be wrong?

     

    I've double checked most of the BW configuration, base on another 7.31 environment, and everything seems to be setup OK.

     

    Regards,


    0 0

    Hi experts!!

     

    i hope you can help me to solve this problem:

     

    i'm doing a clean installation of SAP NW7.31, at the abap import phase there is getting an error, i'm installing over RHEL6 & Sybase

     

    this are the  logs:

     

     

     

    SPM:


    ad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:42.391
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.

    INFO       2013-05-30 15:43:43.478
    [sixxcstepexecute.cpp:804]
    Execute step readPackageInfo of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:43.682
    [syuxccuren.cpp:562]
         
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
              lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:44.752 [sixxcstepexecute.cpp:804]
    Execute step writeDdlMappingFile of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:44.948
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:46.19
    [sixxcstepexecute.cpp:804]
    Execute step createMigrationKeyCmdFile of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:46.215
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:47.364
    [sixxcstepexecute.cpp:804]
    Execute step testMigrationKey of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:47.565
    [syuxccuren.cpp:562]
           
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:48.663
    [sixxcstepexecute.cpp:804]
    Execute step createPropertyFileForMigrationMonitor of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:48.930
    [syuxcpath.cpp:471]
           
    CSyPath::createFile() lib=syslib module=syslib
    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/import_monitor_cmd.properties.
    INFO       2013-05-30 15:43:49.132
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:50.283 [sixxcstepexecute.cpp:804]
    Execute step createPropertyFileForMigrationMonitorController of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:50.481
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:51.632
    [sixxcstepexecute.cpp:804]

    Execute step exitForMigrationMonitor of component |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:51.823
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)

               lib=syslib
    module=syslib

    Working directory changed to /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.
    INFO       2013-05-30 15:43:52.935
    [sixxcstepexecute.cpp:804]

    Execute step setHdbDatabaseReorgParameters of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:53.126
    [syuxccuren.cpp:562]
           
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.

    INFO       2013-05-30 15:43:54.255
    [sixxcstepexecute.cpp:804]
    Execute step runMigrationMonitorCreateTables of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:54.456
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.

    INFO       2013-05-30 15:43:55.553
    [sixxcstepexecute.cpp:804]

    Execute step runHdbDatabaseReorg of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0

    INFO       2013-05-30 15:43:55.748
    [syuxccuren.cpp:562]
            
    CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath&
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP)
               lib=syslib
    module=syslib
    Working directory changed to
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP.

    INFO       2013-05-30 15:43:56.894
    [sixxcstepexecute.cpp:804]

    Execute step runMigrationMonitor of component
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
    INFO       2013-05-30 15:43:58.426
    [syuxcpath.cpp:471]
            
    CSyPath::createFile() lib=syslib module=syslib

    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/import_monitor.java.log.

    INFO       2013-05-30 15:43:58.709
            
    CJSlibModule::writeInfo_impl()

    Output of /tmp/sapinst_exe.3318.1369942895/jre/bin/java -classpath migmon.jar
    -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is
    written to the logfile import_monitor.java.log.

    WARNING    2013-05-30 16:13:59.435
            
    CJSlibModule::writeWarning_impl()

    Execution of the command "/tmp/sapinst_exe.3318.1369942895/jre/bin/java
    -classpath migmon.jar -showversion -Xmx1024m
    com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code
    103. Output:
    java version "1.6.0_24"

    Java(TM) SE Runtime Environment (build 6.1.029)
    SAP Java Server VM (build 6.1.029 17.0-b16, Jun 29 2011 08:21:37 - 61_REL -
    optU - linux amd64 - 6 - bas2:155500 (mixed mode))

    Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.

    Loading of 'SAPNTAB' import package: OK

    Import Monitor jobs: running 0, waiting 28, completed 1, failed 0, total 29.

    Import Monitor jobs: running 1, waiting 27, completed 1, failed 0, total 29.

    Import Monitor jobs: running 2, waiting 26, completed 1, failed 0, total 29.

    Import Monitor jobs: running 3, waiting 25, completed 1, failed 0, total 29.

    Import Monitor jobs: running 4, waiting 24, completed 1, failed 0, total 29.

    Import Monitor jobs: running 5, waiting 23, completed 1, failed 0, total 29.

    Import Monitor jobs: running 6, waiting 22, completed 1, failed 0, total 29.

    Import Monitor jobs: running 7, waiting 21, completed 1, failed 0, total 29.

    Import Monitor jobs: running 8, waiting 20, completed 1, failed 0, total 29.

    Loading of 'REPOSRC' import package: ERROR

    Import Monitor jobs: running 7, waiting 20, completed 1, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 19, completed 1, failed 1, total 29.

    Loading of 'SMIMCONT1' import package: OK

    Import Monitor jobs: running 7, waiting 19, completed 2, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 18, completed 2, failed 1, total 29.

    Loading of 'STERM_TEXT' import package: OK

    Import Monitor jobs: running 7, waiting 18, completed 3, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 17, completed 3, failed 1, total 29.

    Loading of 'DOKCLU' import package: OK

    Import Monitor jobs: running 7, waiting 17, completed 4, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 16, completed 4, failed 1, total 29.

    Loading of 'ATAB' import package: OK

    Import Monitor jobs: running 7, waiting 16, completed 5, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 15, completed 5, failed 1, total 29.

    Loading of 'SEOSUBCODF' import package: OK

    Import Monitor jobs: running 7, waiting 15, completed 6, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 14, completed 6, failed 1, total 29.

    Loading of 'SEOCOMPODF' import package: OK

    Import Monitor jobs: running 7, waiting 14, completed 7, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 13, completed 7, failed 1, total 29.

    Loading of 'TODIR' import package: OK

    Import Monitor jobs: running 7, waiting 13, completed 8, failed 1, total 29.

    Import Monitor jobs: running 8, waiting 12, completed 8, failed 1, total 29.

    Loading of 'SAPSPROT' import package: ERROR

    Import Monitor jobs: running 7, waiting 12, completed 8, failed 2, total 29.

    Loading of 'DD03L' import package: OK

    Import Monitor jobs: running 6, waiting 12, completed 9, failed 2, total 29.

    Loading of 'SAPSSRC' import package: ERROR

    Import Monitor jobs: running 5, waiting 12, completed 9, failed 3, total 29.

    Import Monitor jobs: running 6, waiting 11, completed 9, failed 3, total 29.

    Import Monitor jobs: running 7, waiting 10, completed 9, failed 3, total 29.

    Import Monitor jobs: running 8, waiting 9, completed 9, failed 3, total 29.

    Loading of 'SAPSLOAD' import package: ERROR

    Import Monitor jobs: running 7, waiting 9, completed 9, failed 4, total 29.

    Import Monitor jobs: running 8, waiting 8, completed 9, failed 4, total 29.

    Loading of 'SAPPOOL' import package: OK

    Import Monitor jobs: running 7, waiting 8, completed 10, failed 4, total 29.

    Loading of 'WDY_UI_PROPERTY' import package: OK

    Import Monitor jobs: running 6, waiting 8, completed 11, failed 4, total 29.

    Import Monitor jobs: running 7, waiting 7, completed 11, failed 4, total 29.

    Import Monitor jobs: running 8, waiting 6, completed 11, failed 4, total 29.

    Loading of 'SAPSDOCU' import package: OK

    Import Monitor jobs: running 7, waiting 6, completed 12, failed 4, total 29.

    Loading of 'SAPSLEXC' import package: OK

    Import Monitor jobs: running 6, waiting 6, completed 13, failed 4, total 29.

    Loading of 'SAPCLUST' import package: OK

    Import Monitor jobs: running 5, waiting 6, completed 14, failed 4, total 29.

    Import Monitor jobs: running 6, waiting 5, completed 14, failed 4, total 29.

    Import Monitor jobs: running 7, waiting 4, completed 14, failed 4, total 29.

    Import Monitor jobs: running 8, waiting 3, completed 14, failed 4, total 29.

    Loading of 'SAPDDIM' import package: OK

    Import Monitor jobs: running 7, waiting 3, completed 15, failed 4, total 29.

    Loading of 'SAPDFACT' import package: OK

    Import Monitor jobs: running 6, waiting 3, completed 16, failed 4, total 29.

    Loading of 'SAPDODS' import package: OK

    Import Monitor jobs: running 5, waiting 3, completed 17, failed 4, total 29.

    Import Monitor jobs: running 6, waiting 2, completed 17, failed 4, total 29.

    Import Monitor jobs: running 7, waiting 1, completed 17, failed 4, total 29.

    Loading of 'SAP0000' import package: OK

    Import Monitor jobs: running 6, waiting 1, completed 18, failed 4, total 29.

    Loading of 'SAPUSER' import package: OK

    Import Monitor jobs: running 5, waiting 1, completed 19, failed 4, total 29.

    Loading of 'SAPSDIC' import package: OK

    Import Monitor jobs: running 4, waiting 1, completed 20, failed 4, total 29.

    Loading of 'SAPAPPL1' import package: ERROR

    Import Monitor jobs: running 3, waiting 1, completed 20, failed 5, total 29.

    Loading of 'SAPSSEXC' import package: ERROR

    Import Monitor jobs: running 2, waiting 1, completed 20, failed 6, total 29.

    Loading of 'SAPAPPL0' import package: ERROR

    Import Monitor jobs: running 1, waiting 1, completed 20, failed 7, total 29.

    Loading of 'SAPAPPL2' import package: ERROR

    Import Monitor jobs: running 0, waiting 1, completed 20, failed 8, total 29.

    ERROR      2013-05-30 16:13:59.491
            
    CJSlibModule::writeError_impl()

    CJS-30022  Program 'Migration Monitor' exits with error code 103. For
    details see log file(s) import_monitor.java.log, import_monitor.log.

    ERROR      2013-05-30 16:14:01.737
    [sixxcstepexecute.cpp:937]

    FCO-00011  The step runMigrationMonitor with step key
    |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor
    was executed with status ERROR ( Last error reported by the step: Program
    'Migration Monitor' exits with error code 103. For details see log file(s)
    import_monitor.java.log, import_monitor.log.).

    INFO       2013-05-30 16:14:03.534
    [syuxcpath.cpp:471]

            
    CSyPath::createFile() lib=syslib module=syslib
    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/__instana_tmp.xml.

    INFO       2013-05-30 16:14:08.113
    [syuxcpath.cpp:509]
            
    CSyPath::createDirectory() lib=syslib module=syslib
    Creating directory
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING.

    INFO       2013-05-30 16:14:08.114 [syxxcdir.cpp:355]

             
    CSyDirectoryImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP,
    ISyNode::CopyMoveMode_t 0x1ISyProgressObserver* )

               lib=syslib
    module=syslib

    Copying directory /usr/sap/mediabw73/SPM2/COMMON/REPORTING to:
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING.
    INFO       2013-05-30 16:14:08.140
    [syuxcfile.cpp:602]
             
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING, ISyNode::CopyMoveMode_t
    0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib
    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/report.template.xml' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.
    INFO       2013-05-30 16:14:08.151
    [syuxcfile.cpp:602]
             
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 
               lib=syslib
    module=syslib

    Copied file
    '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/jspm_deployStatusRender.xsl' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.

    INFO       2013-05-30 16:14:08.160
    [syuxcfile.cpp:602]
             
    CSyFileImpl::copy(const CSyPath & /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/filter.xml' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.
    INFO       2013-05-30 16:14:08.169
    [syuxcfile.cpp:602]
            
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 
               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/UndeploymentResults.xsl'
    to '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.

    INFO       2013-05-30 16:14:08.182 [syuxcfile.cpp:602]

             
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/DeployStatusRender_sapinst.xsl'
    to '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.

    INFO       2013-05-30 16:14:08.191
    [syuxcfile.cpp:602]
            
    CSyFileImpl::copy(const CSyPath & /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/common_templates.xsl' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.
    INFO       2013-05-30 16:14:08.197
    [syuxcfile.cpp:602]
            
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file
    '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/DeployStatusRender_Short_sapinst.xsl'
    to '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.

    INFO       2013-05-30 16:14:08.312
    [syuxcfile.cpp:602]

             
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/scadata.xml' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.



    INFO       2013-05-30 16:14:08.317
    [syuxcfile.cpp:602]

             
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/logs.template' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.



    INFO       2013-05-30 16:14:08.324
    [syuxcfile.cpp:602]

             
    CSyFileImpl::copy(const CSyPath &
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/OverallStatus.xsl' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.



    INFO       2013-05-30 16:14:08.380
    [syuxcfile.cpp:602]

             
    CSyFileImpl::copy(const CSyPath & /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING,
    ISyNode::CopyMoveMode_t 0x1, ISyProgressObserver*) const 

               lib=syslib
    module=syslib

    Copied file '/usr/sap/mediabw73/SPM2/COMMON/REPORTING/filter_multiple.xml' to
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING'.



    INFO       2013-05-30 16:14:08.407
    [syuxcpath.cpp:471]

             
    CSyPath::createFile() lib=syslib module=syslib

    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/loginquirer.properties.



    INFO       2013-05-30 16:14:08.430
    [syuxcpath.cpp:471]

             
    CSyPath::createFile() lib=syslib module=syslib

    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/loginquirer.properties.escaped.



    INFO       2013-05-30 16:14:08.442 [syuxcfile.cpp:273]

             
    CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

               lib=syslib
    module=syslib

    Removed file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/loginquirer.properties.



    INFO       2013-05-30 16:14:08.524 [syuxcpath.cpp:471]

             
    CSyPath::createFile() lib=syslib module=syslib

    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/java.log.



    INFO       2013-05-30 16:14:08.822

             
    CJSlibModule::writeInfo_impl()

    Output of /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/sapjvm/sapjvm_6/bin/java
    -classpath /tmp/sapinst_exe.3318.1369942895/JAR/loginquirer.jar
    com.sap.sdt.loginquirer.LogInquirerMain -p loginquirer.properties -c
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/filter.xml
    -o TroubleTicketResults.xml -t
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/report.template.xml
    is written to the logfile java.log.



    INFO       2013-05-30 16:14:19.320

             
    CJSlibModule::writeInfo_impl()

    Execution of the command
    "/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/sapjvm/sapjvm_6/bin/java
    -classpath /tmp/sapinst_exe.3318.1369942895/JAR/loginquirer.jar
    com.sap.sdt.loginquirer.LogInquirerMain -p loginquirer.properties -c /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/filter.xml
    -o TroubleTicketResults.xml -t
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/report.template.xml"
    finished with return code 0. Output:

    *_LOGS macro: Cannot find logs template file /info.logs.template

    *_LOGS macro: Cannot find logs template file /info.logs.template

    *_LOGS macro: Cannot find logs template file /info.logs.template

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/DeployInfo.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/export_time.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/import_time.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/UndeploymentResultsFirst.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/DeploymentResults.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/DeploymentResults_1.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/UndeploymentResultsSecond.html

    *_LOGS macro: Cannot find logs template file undefined/JspmAnalysis.html

    *_LOGS macro: Cannot find logs template file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/CEScanInboxResult.html



    INFO       2013-05-30 16:14:19.369
    [syuxcpath.cpp:471]

             
    CSyPath::createFile() lib=syslib module=syslib

    Creating file
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/java.log.



    INFO       2013-05-30 16:14:19.641

             
    CJSlibModule::writeInfo_impl()

    Output of /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/sapjvm/sapjvm_6/bin/java
    -classpath /tmp/sapinst_exe.3318.1369942895/JAR/loginquirer.jar
    com.sap.sdt.loginquirer.JavaTransformer -in TroubleTicketResults.xml -style
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/OverallStatus.xsl
    -out LogAnalyzer.html -Dstatus=error
    -Dkeydb_xml=/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/keydb.xml
    -Dinstana_xml=/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/__instana_tmp.xml
    is written to the logfile java.log.



    INFO       2013-05-30 16:14:24.045

             
    CJSlibModule::writeInfo_impl()

    Execution of the command
    "/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/sapjvm/sapjvm_6/bin/java
    -classpath /tmp/sapinst_exe.3318.1369942895/JAR/loginquirer.jar
    com.sap.sdt.loginquirer.JavaTransformer -in TroubleTicketResults.xml -style
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/OverallStatus.xsl
    -out LogAnalyzer.html -Dstatus=error -Dkeydb_xml=/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/keydb.xml
    -Dinstana_xml=/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/__instana_tmp.xml"
    finished with return code 0. Output:

    INFO: Starting to transform 'TroubleTicketResults.xml' to 'LogAnalyzer.html'
    using stylesheet
    '/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/REPORTING/OverallStatus.xsl'.

    INFO: Input parameters:

        status=error

      
    instana_xml=/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/__instana_tmp.xml

        keydb_xml=/tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/keydb.xml

    INFO: Transformation finished.



    May 30, 2013 11:54:57 PM [Info]: >>    :  
    [140736841762560]   23:54:57    ***Warning: Potential
    spurious wakeup occurred at object <0x0000000015477bd0> (a
    java.awt.EventQueue), awaking thread "AWT-EventQueue-0"
    tid=0x00007ffff0b97fa0.

    May 30, 2013 11:54:57 PM [Info]: >> "AWT-EventQueue-0"
    cpu=1713860.00 [reset 1713860.00] ms allocated=5968724512 B (5.56 GB) [reset
    5968724512 B (5.56 GB)] defined_classes=330

    May 30, 2013 11:54:57 PM [Info]: >> io= file i/o: 3847/127 B, net i/o:
    0/0 B, files opened:2, socks opened:0  [reset file i/o: 3847/127 B, net
    i/o: 0/0 B, files opened:2, socks opened:0 ]

    May 30, 2013 11:54:57 PM [Info]: >> prio=10 tid=0x00007ffff0b97fa0
    nid=0xd5a runnable  [_thread_in_vm (_running),
    stack(0x00007fffd965c000,0x00007fffd975d000)

    May 30, 2013 11:54:58 PM [Info]: >> ] [0x00007fffd975b000]

    May 30, 2013 11:54:58 PM [Info]: >>  
    java.lang.Thread.State: WAITING (on object monitor)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.lang.Object.wait(J)V(Native Method)

    May 30, 2013 11:54:58 PM [Info]: >>     - waiting on
    <0x0000000015477bd0> (a java.awt.EventQueue)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.lang.Object.wait()V(Object.java:485)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventQueue.getNextEvent()Ljava/awt/AWTEvent;(EventQueue.java:485)

    May 30, 2013 11:54:58 PM [Info]: >>     - locked
    <0x0000000015477bd0> (a java.awt.EventQueue)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventDispatchThread.pumpOneEventForFilters(I)Z(EventDispatchThread.java:236)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V(EventDispatchThread.java:184)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V(EventDispatchThread.java:174)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V(EventDispatchThread.java:169)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V(EventDispatchThread.java:161)

    May 30, 2013 11:54:58 PM [Info]: >>     at
    java.awt.EventDispatchThread.run()V(EventDispatchThread.java:122)

     

    AND this is the REPOSRC.log

     

     

     

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load:
    START OF LOG: 20130530154529



    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id:
    //bas/720_REL/src/R3ld/R3load/R3ldmain.c#17 $ SAP

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: version R7.20/V1.4 [UNICODE]

    Compiled Jan 15 2013 18:27:27

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load -ctf I
    /usr/sap/mediabw73/51043205/DATA_UNITS/EXP1/DATA/REPOSRC.STR
    /tmp/sapinst_instdir/NW731/SYB/INSTALL/NW731/SYB/STD/ABAP/DDLSYB.TPL
    REPOSRC.TSK SYB -l REPOSRC.log





    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: job completed

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20130530154529



    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20130530154529



    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id:
    //bas/720_REL/src/R3ld/R3load/R3ldmain.c#17 $ SAP

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: version R7.20/V1.4 [UNICODE]

    Compiled Jan 15 2013 18:27:27

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load -i REPOSRC.cmd -dbcodepage 4103 -l
    REPOSRC.log -c 99000000 -loadprocedure fast



    (DB) INFO: connected to DB

    (SQL) INFO: Searching for SQL file SQLFiles.LST

    (SQL) INFO: SQLFiles.LST not found

    (SQL) INFO: Searching for SQL file /usr/sap/mediabw73/51043205/DATA_UNITS/EXP1/DB/SQLFiles.LST

    (SQL) INFO: /usr/sap/mediabw73/51043205/DATA_UNITS/EXP1/DB/SQLFiles.LST not
    found

    (SQL) INFO: Searching for SQL file SSEXC.SQL

    (SQL) INFO: SSEXC.SQL not found

    (SQL) INFO: Searching for SQL file /usr/sap/mediabw73/51043205/DATA_UNITS/EXP1/DB/SYB/SSEXC.SQL

    (SQL) INFO: /usr/sap/mediabw73/51043205/DATA_UNITS/EXP1/DB/SYB/SSEXC.SQL not
    found

    (DB) INFO: REPOSRC created

    (SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

      rc = 99, table "REPOSRC"

      (SQL error 0)

      error message returned by DbSl:

    [ASE Error SQL208:42000]DBPROPERTIES not found. Specify owner.objectname or use
    sp_help to check whether the object exists (sp_help may produce lots of
    output).



    (IMP) ERROR: ExeFastload: rc = 2

    (DB) ERROR: failed to load table "REPOSRC", index
    "REPOSRC~0" is not created.

    (DB) ERROR: failed to load table "REPOSRC", index
    "REPOSRC~SPM" is not created.

    (DB) INFO: disconnected from DB



    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: job finished with 3 error(s)

    /usr/sap/BPA/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20130530154539

     

     

    Thanks in advance!!


    0 0
  • 08/21/07--06:18: Appointment Calendar in LSO
  • Hi All,

     

    I am working on LSO (Learning Solutions) and needs to reflect the trainings booked by the participants into their appoint calendars. How can i do this? Can any one help.

     

    Regards


    0 0
  • 01/29/09--01:21: RE: SAP BW Browser problem
  • Hi,

     

    We have a problem with SAP BW Browser. Whenever we try to open SAP

    BW3.X->Browser, it throws out error saying 'wdbbapp.exe has encountered

    a problem and needs to close.We are sorry for the inconvenience.'

     

    We have SAP FRONTEND 710(patch level 11) installed on Windows Xp

    (SERVICE PACK 2). Have tried uninstalling and then reinstalling the

    frontend. Still the problem exists.

     

    How do i go about solving this problem?

     

    Please give your inputs..

     

    Regards,

    Sowmya K


    0 0

    Hello Gurus,

    I'm stuck for few days with error below. Will be grateful for you help.

     

    Phase :

    +++++

    Create ABAP Secure Store

    Error :

    +++++

           An error occurred while processing option SAP NetWeaver 7.3 > Oracle > SAP Systems > Process Integration > Standard System > Standard System( Last error reported by the step: No such file 'D:/usr/sap/N73/SYS/exe/uc/NTAMD64/rsecssfx.exe'.). You can now:

    • Choose Retry to repeat the current step.
    • Choose Log Files to get more information about the error.
    • Stop the option and continue with it later.      

     

    LogAnalyzer.htm Content:

    +++++++++++++++++++

    Last successfully executed installation step: ABAP_SSFS -> prepare @ 21:18:35

     

    An error occurred at step:
    ERROR 2013-06-05 21:22:44.138 [sixxcstepexecute.cpp:995]
    FCO-00011 The step createSSFS with step key ABAP_SSFS -> createSSFS was executed with status ERROR

     

    Thank you all in advance

    Salah


    0 0

    Hi

    We are implementing the Safety Belt functionality for BEx Analyser as per note 1411545 (BExAnalyzer: safety belt for large resultsets).

    Has anyone found a way to configure SAP BW for BEx analyser, so no results are returned when the Safety Belt cell restriction is exceeded? We are on BEx 7.3 SP 3 and BW 7.3 SP 07.

     

     

    Background and Issue:

    When BEx analyser returns more cells than what is defined by the safety belt setting, the message appears i.e. “Result set too large”. However, the data (a portion of the data that fits within the safety belt setting), is still displayed.

     

    This behaviour is different from Analysis for Office, where no results are displayed when more cells are returned compared to the BW Cell restriction setting.

     

    Our users are not comfortable with how BEx behaves, since it is inconsistent with Analysis for Office’s behaviour. In addition, they do not accept the risk, that end users will continue reporting numbers, although only a portion of the data is returned.

     

    So I am asking if anyone knows of a way to configure the system, so no results are returned, when we exceed the safety belt setting.

     

    Regards


    0 0

    Hello,

     

     

    Can anyone worked on the restriction of Intercompany park & post authorization please advice on the below,

     

     

    Users should have the ability to park or post intercompany documents against their trading partners, but only post
    other documents or view their own company data.

     

     

    Example:

     

    User1 –UK 

    User2 –Netherlands

     

     

    User1 can park or post intercompany documents against Netherlands.

    User2 can park or post intercompany documents against UK.

     

     

    User1 can view the intercompany document against Netherlands

    User2 can view the intercompany document against UK.

     

     

    User1 can only post other documents for UK

    User2 can only post other documents for Netherlands

     

    User1 can only view UK data

    User2 can only view Netherlands data.

     

     

    Question:

     

    How can this be handled? Can this be handled via document type, company code and trading partner parameters in authorization?

     

     

    Thank You,

    Vadivel.K


    0 0
  • 05/30/13--05:27: sap app server down.
  • hi everyone,
         My manager told to me of my PRD server was down yesterday morning. My manager said some users could not login the system , and he found one app server was down. He restarted the app server and seems everything is ok now.  But he asked me to find out what caused the server down.

    I have checked the  dev trace files of the app server today.

    I did not find any useful log in the dev_disp.old. 

    but I found the some dev_wp*.old  files record like below (the server has 76 wp, 0~19 record like below)

    M Tue May 28 06:55:22 2013
    M  ThAlarmHandler (1)
    M  ThAlarmHandler: set CONTROL_TIMEOUT/DP_CONTROL_JAVA_EXIT and break sql
    B  db_sqlbreak() = 1
    M  ThAlarmHandler: return from signal handler
    M
    M Tue May 28 06:56:22 2013
    M  ThAlarmHandler (2)
    M  ThAlarmHandler: 2. ALARM: terminate process (pid=9408, user is T138/M0)
    M  ThAlarmHandler: prv_action of W0: 0x2
    M  ThAlarmHandler: set clean state of T138/M0 to DP_TIMEOUT
    M  ThAlarmHandler: prv_action of W0: 0xa
    M  ThAlarmHandler: save snc contexts
    M  ThISncSaveAllContexts: save 0 snc contexts
    M  ThAlarmHandler: C-Stack during alarm handler
    M                     C-STACK
    (0)  0x4000000001b363b0  CTrcStack + 0x1d0 at dptstack.c:227 [dw.sapP20_D20]
    (1)  0x4000000001733100  ThAlarmHandler + 0x11e0 at thxxhead.c:21417 [dw.sapP20_D20]
    (2)  0x4000000001664520  DpSigAlrm + 0x220 at dpxxtool.c:2295 [dw.sapP20_D20]
    (3)  0xe00000013305f440       Signal 14 (SIGALRM) delivered
    (4)  0xc00000000054ee70  _semop_sys + 0x30 [/usr/lib/hpux64/libc.so.1]
    (5)  0xc0000000005607e0  _semop + 0xe0 at ../../../../../core/libs/libc/shared_em_64_perf/../core/syscalls/t_semop.c:19 [/usr/lib/hpux64/libc.so.1]
    (6)  0x4000000001707680  RqOsSem + 0xb0 at semux.c:1186 [dw.sapP20_D20]
    (7)  0x40000000017097a0  SemRq + 0x810 at semux.c:1814 [dw.sapP20_D20]
    (8)  0x4000000004cc2990  EsILock + 0x2410 at esxx.c:3449 [dw.sapP20_D20]
    (9)  0x4000000004cca410  STD_EsAttach + 0x1d0 at esxx.c:2348 [dw.sapP20_D20]
    (10) 0x4000000004cd5110  EsAttach + 0x90 at esxxfunc.c:874 [dw.sapP20_D20]
    (11) 0x4000000004c988c0  EmContextAttach + 0x1e0 at emxx.c:932 [dw.sapP20_D20]
    (12) 0x40000000018e20a0  ThCheckEmState + 0x300 at thxxmem.c:438 [dw.sapP20_D20]
    (13) 0x40000000018dd780  ThRollIn + 0x380 at thxxmem.c:870 [dw.sapP20_D20]
    (14) 0x400000000175bc20  ThSessionRestore + 0x180 at thxxhead.c:22129 [dw.sapP20_D20]
    (15) 0x40000000017250b0  TskhLoop + 0x1210 at thxxhead.c:3542 [dw.sapP20_D20]
    (16) 0x400000000171f000  ThStart + 0x5d0 at thxxhead.c:10759 [dw.sapP20_D20]
    (17) 0x40000000015ab260  DpMain + 0x870 at dpxxdisp.c:1152 [dw.sapP20_D20]
    (18) 0x40000000015a4b60  main + 0x80 at thxxanf.c:64 [dw.sapP20_D20]
    (19) 0xc00000000006e9b0  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
    M
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 9408) [dpuxtool.c   268]

    other wp*.old just record wp heap memory is not enough and asked us to change the parameter.


    Could anyone give me any suggestions how to find out what caused the issues?

    regards .


    0 0

    Hi experts.

     

    Need your help please.

     

    I'm trying to install NW7.3 but stacked "Create Database" phase:

     

    Error detail:

    +++++++++

     

           An error occurred while processing option SAP NetWeaver 7.3 > Oracle > SAP Systems > Process Integration > Standard System > Standard System( Last error reported by the step: SQL statement or script failed. DIAGNOSIS: Error message: Executable C:\oracle\ORA\11203/bin/sqlplus returns 1.. SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.). You can now:

    • Choose Retry to repeat the current step.
    • Choose Log Files to get more information about the error.
    • Stop the option and continue with it later.

    Log files are written to C:\Program Files/sapinst_instdir/NW730/ORA/INSTALL/NW730/ORA/STD/AS.    

     

    The ora_sql_results.log content:

    ++++++++++++++++++++++++

     

     

     

    ================================================================================

    2013-06-01, 19:45:43 SAPINST ORACLE start logging for

     

     

    SHUTDOWN ABORT;

     

     

    exit;

     

     

    Output of SQL executing program:

     

     

     

     

     

     

    SQL*Plus: Release 11.2.0.3.0 Production on Mon Jun 1 19:45:44 2013

     

     

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

     

     

    ERROR:

    ORA-12560: TNS:protocol adapter error

     

     

     

     

    SP2-0751: Unable to connect to Oracle.  Exiting SQL*Plus

     

     

     

     

    SAPINST: End of output of SQL executing program C:\oracle\ORA\11203/bin/sqlplus.

     

     

    SAPINST found errors.

    SAPINST The current process environment may be found in sapinst_ora_environment.log.

     

     

    2013-06-01, 19:45:45 SAPINST ORACLE stop logging

     

     

     

     

     

     

     

     

     

     

     

     

    ================================================================================

    2013-06-01, 19:46:07 SAPINST ORACLE start logging for

     

     

    SHUTDOWN IMMEDIATE;

     

     

    exit;

     

     

    Output of SQL executing program:

     

     

     

     

     

     

    SQL*Plus: Release 11.2.0.3.0 Production on Mon Jun 1 19:46:07 2013

     

     

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

     

     

    ERROR:

    ORA-01031: insufficient privileges

     

     

     

     

    SP2-0751: Unable to connect to Oracle.  Exiting SQL*Plus

     

     

     

     

    SAPINST: End of output of SQL executing program C:\oracle\ORA\11203/bin/sqlplus.

     

     

    SAPINST found errors.

    SAPINST The current process environment may be found in sapinst_ora_environment.log.

     

     

    2013-06-01, 19:46:09 SAPINST ORACLE stop logging

     

     

     

     

     

     

     

     

     

     

     

     

    ================================================================================

    2013-06-01, 19:46:09 SAPINST ORACLE start logging for

     

     

    STARTUP NOMOUNT;

     

     

    exit;

     

     

    Output of SQL executing program:

     

     

     

     

     

     

    SQL*Plus: Release 11.2.0.3.0 Production on Mon Jun 1 19:46:09 2013

     

     

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

     

     

    ERROR:

    ORA-01031: insufficient privileges

     

     

     

     

    SP2-0751: Unable to connect to Oracle.  Exiting SQL*Plus

     

     

     

     

    SAPINST: End of output of SQL executing program C:\oracle\ORA\11203/bin/sqlplus.

     

     

    SAPINST found errors.

    SAPINST The current process environment may be found in sapinst_ora_environment.log.

     

     

    2013-06-01, 19:46:10 SAPINST ORACLE stop logging

     

     

    Thanks in advance

    Salah


    0 0
  • 06/05/13--04:50: Last logon to the SAP Portal
  • Hi all

     

    please assist. We have a request to see when last users logged on the SAP Portal.

     

    The client is using EP7.3 ECC6 EHP5.

     

    They would like a list of all users as well as the last logon date.

     

    thanks in advance.

     

    Regards,

    Faeeda


    0 0

    Hi All,

     

    A background Job SAP_COLLECTOR_FOR_PERFMONITOR is failing at specific time i.e, at 0,4,8,12,16 hours daily with a dump (EXPORT_TOO_MUCH_DATA) and i cannot find logs in ST03 (what are the programs it is executing) .

     

     

       Job                          Spool Job Doc Job CreatedB Status      Start date Start time Duration(sec.) Delay (sec.

     

       SAP_COLLECTOR_FOR_PERFMONITOR              DDIC     Canceled    31.05.2013 16:00:26          44       26
       SAP_COLLECTOR_FOR_PERFMONITOR              DDIC     Canceled    31.05.2013 00:00:26          55       26

     

     

    Job Log :

     

    Date   Time Message text

     

    31.05.2013 16:00:26 Job started

    31.05.2013 16:00:26 Step 001 started (program RSCOLL00, variant , user ID DDIC)

    31.05.2013 16:00:30 Job CCMS_COLL_DB:RSDBPREV        has been sche

    31.05.2013 16:00:30 Clean_Plan:Cleanup of DB13 Plannings

    31.05.2013 16:00:30 Clean_Plan:started by RSDBPREV                   on server ep1vci

    31.05.2013 16:00:30 Clean_Plan:Cleaning up jobs of system EP1

    31.05.2013 16:00:31 Clean_Plan:finished

    31.05.2013 16:01:10 Internal session terminated with a runtime error (see ST22)

    31.05.2013 16:01:10 Job cancelled

     

     

     

    ST22 : ABAP Dump

     

     

    Runtime Errors     EXPORT_TOO_MUCH_DATA
    Except.            CX_SY_COMPRESSION_ERROR
    Date and Time      31.05.2013 16:01:10

     

    Short text


    Too much data for export.

     

    What happened?


    Runtime error

    The current ABAP program "CL_SWNC_COLLECTOR_DB==========CP" had to be

    terminated because one

    of the statements could not be executed at runtime.

     

    What can you do?


    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator

    You can use the ABAP dump analysis transaction ST22 to view and manage

    termination messages, in particular for long term reference.

    Error analysis


    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_COMPRESSION_ERROR', was not

    caught in

    procedure "SAVE_AGGREGATE" "(METHOD)", nor was it propagated by a RAISING

    clause.

    Since the caller of the procedure could not have anticipated that the

    exception would occur, the current program is terminated.

    The reason for the exception is:

    The dataset stored under an EXPORT/IMPORT ID is restricted

    by

    1. The maximum possible size of 2 GB

    2. The length of a data record and the capacity of the

    sequence counter. This error occurs only if the capacity of the

    sequence counter does not go beyond 255.

    How to correct the error


    1. Data must be distributed into portions of 2GB

    2. 3 possible solutions:

    - Either increase the sequence counter (field SRTF2) to include INT4

    or

    -export less data

    or

    -distribute the data across several IDs

    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:

    "EXPORT_TOO_MUCH_DATA" "CX_SY_COMPRESSION_ERROR"

    "CL_SWNC_COLLECTOR_DB==========CP" or "CL_SWNC_COLLECTOR_DB==========CM00O"

    "SAVE_AGGREGATE"

    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

     

     

     

     

     

    ST03 : Unable to find Error logs (Expert Mode--> Collector and performance DB-->Performance Monitor--> log and execution times)

     

    04.06.2013    07:00:35    No errors

    04.06.2013    06:00:34    No errors

    04.06.2013    05:00:35    No errors

    04.06.2013    03:00:39    No errors

    04.06.2013    02:00:34    No errors

    04.06.2013    01:00:34    No errors

     

     

    Please help me out.

     

    Vijay

     

    Message was edited by: Benny Schaich-Lebek


    0 0

    Hi,

     

    I have the file system /usr/sap are in 90% of used space in one of my portals and I need to get some space in it. One of the biggest files that I have is in this file system:

     

    /usr/sap/DAA/SMDA97/SMDAgent, can I delete the files presented in the screen? or not?

     

    SMDAgent.PNG

     

    Thanks!
    Carlos


    0 0
  • 05/31/13--02:42: Database upgrade issue
  • Dear Experts,

     

    I also need to upgrade the database as mentioned in the below Link

     

    http://scn.sap.com/thread/3367755

     

    But the solution mentioned in that link is not clear, request to please guide me through this phase.

     

    Regards,

    Omkar B


    0 0

    Hi Friends,

     

    We have a below business requirement, did anyone worked on the same please advice.

     

    Users should have the ability to park or post inter-company documents against their trading partners, but only post
    other documents or view their own company data.

     

    Example:

     

    User1 – UK

    User2 – Netherlands

     

    User1 can park or post inter-company documents against Netherlands.

    User2 can park or post inter-company documents against UK.

     

    User1 can view the inter-company document against Netherlands

    User2 can view the inter-company document against UK.

     

    User1 can only post other documents for UK

    User2 can only post other documents for Netherlands

     

    User1 can only view UK data

    User2 can only view Netherlands data.

     

    Question:

    How can this be handled? Can this be handled via document type, company code and trading partner parameters
    in authorization?

     

    Thank You,

    Vadivel K.


    0 0

    Hi,

     

    We have installed SAP NW7.3 Ehp1 ( AS Java ) on HP-UX / Sybase.

     

    What are the post installation activities required.

     

    Our intention is just run Java applications on NW 7.3 Platform.

     

    Regards,

    Sivarajesh.


    0 0

    Hi all,

     

    Can any one tell me how  to  Bi4 - How to create SAP BusinessObjects Document List template into EP 7.3.x

     

     

    Thanks in advance,

     

    Haresh


    0 0
  • 05/26/13--07:11: PAGE FILE REcommandation
  • Dear Team,

     

    We have 4 drive on windows C, D, E and F.....page file given from c and d drive e and f having database and log ,,,,now we are moving our datafile from e and f to san .....now our e and f is free ................we have allocated 64 GB of page file from C drive and D drive page size is 100 GB ....can we split the page file now ....C 64 gb ,,D 50 GB ,,,E 50 GB ,,F 50 GB.....

     

    My mean is if we will change the page file after sap installation.....whether it will make any difference in performance........

     

    Need your expert advice....

     

     

    Rableen


older | 1 | .... | 9 | 10 | (Page 11) | 12 | 13 | .... | 76 | newer