Observing poor performance on the execution of the quereis

I am executing a relatively simple query which is rougly taking about 48-50 seconds to execute. Can someone suggest an alternate way to query the semantic model where we can achieve response time of a second or under. Here is the query
PREFIX bp:<http://www.biopax.org/release/biopax-level3.owl#>
PREFIX rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#>
PREFIX ORACLE_SEM_FS_NS:<http://oracle.com/semtech#dop=24,RESULT_CACHE,leading(t0,t1,t2)>
SELECT distinct ?entityId ?predicate ?object
WHERE
?entityId rdf:type bp:Gene .
?entityId bp:name ?x .
?entityId bp:displayName ?y .
?entityId ?predicate ?object .
FILTER(regex(?x, "GB035698", "i")||regex(?y, "GB035698", "i"))
Same query executed from sqldeveloper takes about as long as well
SELECT distinct /*+ parallel(24) */subject,p,o
FROM TABLE
(sem_match ( '{?subject rdf:type bp:Gene .
?subject bp:name ?x .
?subject bp:displayName ?y .
?subject ?p ?o
filter (regex(?x, "GB035698", "i")||regex(?y, "GB035698", "i") )
sem_models ('biopek'),
null,
sem_aliases
( sem_alias
('bp',
'http://www.biopax.org/release/biopax-level3.owl#'
NULL,
null,null ))
Is there anything I am missing, can we do anything to optimize our data retrieval?
Best Regards,
Ami

For better performance when using FILTER involving regular expression, you may want to create a full-text index on MDSYS.RDF_VALUE$ table as described in:
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e11828/sdo_rdf_concepts.htm#CIHJCHBJ
I am assuming that you are checking for case-insensitive occurrence of the string GB035698 in ?x or ?y. (On the other hand if you are checking if ?x or ?y is equal to a case-insensitive form of the string GB035698, then the filter could be written in an expanded form involving just value-equality checks and would not need a full-text index for performance.)
Thanks.

Similar Messages

  • Failed in the execution of the ODCIINDEXINSERT routine while loading points

    I used SQL*Loader from 11.2 client to load million records into a 11.2 spatial table (points with longitude and latitude) and I got the following error:
    SQL*Loader: Release 11.2.0.1.0 - Production on Fri Oct 12 10:17:57 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    ORA-39776: fatal Direct Path API error loading table CISDWSYS.VEHICLE_LOCATION_FACT
    ORA-29875: failed in the execution of the ODCIINDEXINSERT routine
    ORA-22054: underflow error
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 720
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 225
    SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
    Load completed - logical record count 45000.The table has a spatial index on VEHICLE_LOCATION column with MDSYS.SDO_GEOMETRY data type. Both table and spatial index are partitioned “monthly” by MESSAGE_DATETIME column. The database is 11.2 (11gR2), the client and SQL*Loader is version 11.2.
    My control file is:
    options (direct=yes, bindsize=20971520, readsize=20971520)
    Load data
    Append
    into table VEHICLE_LOCATION_FACT
    fields terminated by ","
    (VEHICLE_LOCATION_MESSAGE_ID  CONSTANT 222,
    MESSAGE_DATETIME Date 'YYYY-MM-DD HH24:MI:SS',
    ROUTE_NUMBER,RUN_NUMBER,VEHICLE_NUMBER,BADGE_NUMBER,
    TRIP_DIRECTION,GPS_LONGITUDE_NUMBER,GPS_LATITUDE_NUMBER,DIVISION_NUMBER,
    VEHICLE_LOCATION COLUMN OBJECT
         SDO_GTYPE Integer EXTERNAL,
         SDO_SRID  CONSTANT 8265,
         SDO_POINT COLUMN OBJECT
           ( X     FLOAT EXTERNAL,
             Y     FLOAT EXTERNAL
    )I noticed that number for "Load completed - logical record count" is not always same. For example, when data file size is around 300 MB the logical record count is 45000 and when the data file size is 500 MB then logical record count is 110000. The data in both files is of the same nature, just vehicles GPS locations (points).
    The control.log file is
    SQL*Loader: Release 11.2.0.1.0 - Production on Fri Oct 12 10:17:57 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    Control File:   Load_Vehicle_Locations_2.ctl
    Data File:      CIS_VehLoc_L05120603gps.txt
      Bad File:     CIS_VehLoc_L05120603gps.bad
      Discard File:  none specified
    (Allow all discards)
    Number to load: ALL
    Number to skip: 0
    Errors allowed: 50
    Continuation:    none specified
    Path used:      Direct
    Table VEHICLE_LOCATION_FACT, loaded from every logical record.
    Insert option in effect for this table: APPEND
       Column Name                  Position   Len  Term Encl Datatype
    VEHICLE_LOCATION_MESSAGE_ID                               CONSTANT
        Value is '222'
    MESSAGE_DATETIME                    FIRST     *   ,       DATE YYYY-MM-DD HH24:MI:SS
    ROUTE_NUMBER                         NEXT     *   ,       CHARACTER           
    RUN_NUMBER                           NEXT     *   ,       CHARACTER           
    VEHICLE_NUMBER                       NEXT     *   ,       CHARACTER           
    BADGE_NUMBER                         NEXT     *   ,       CHARACTER           
    TRIP_DIRECTION                       NEXT     *   ,       CHARACTER           
    GPS_LONGITUDE_NUMBER                 NEXT     *   ,       CHARACTER           
    GPS_LATITUDE_NUMBER                  NEXT     *   ,       CHARACTER           
    DIVISION_NUMBER                      NEXT     *   ,       CHARACTER           
    VEHICLE_LOCATION                  DERIVED     *           COLUMN OBJECT       
    *** Fields in VEHICLE_LOCATION
    SDO_GTYPE                            NEXT     *   ,       CHARACTER           
    SDO_SRID                                                  CONSTANT
        Value is '8265'
    SDO_POINT                         DERIVED     *           COLUMN OBJECT       
    *** Fields in VEHICLE_LOCATION.SDO_POINT
    X                                    NEXT     *   ,       CHARACTER           
    Y                                    NEXT     *   ,       CHARACTER           
    *** End of fields in VEHICLE_LOCATION.SDO_POINT
    *** End of fields in VEHICLE_LOCATION
    ORA-39776: fatal Direct Path API error loading table CISDWSYS.VEHICLE_LOCATION_FACT
    ORA-29875: failed in the execution of the ODCIINDEXINSERT routine
    ORA-22054: underflow error
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 720
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 225
    SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
    Table VEHICLE_LOCATION_FACT:
      0 Rows successfully loaded.
      0 Rows not loaded due to data errors.
      0 Rows not loaded because all WHEN clauses were failed.
      0 Rows not loaded because all fields were null.
      Date cache:
       Max Size:      1000
       Entries :       192
       Hits    :     44808
       Misses  :         0
    Bind array size not used in direct path.
    Column array  rows :    5000
    Stream buffer bytes:  256000
    Read   buffer bytes:20971520
    Total logical records skipped:          0
    Total logical records rejected:         0
    Total logical records discarded:        0
    Total stream buffers loaded by SQL*Loader main thread:        9
    Total stream buffers loaded by SQL*Loader load thread:        9
    Run began on Fri Oct 12 10:17:57 2012
    Run ended on Fri Oct 12 10:18:34 2012
    Elapsed time was:     00:00:37.16
    CPU time was:         00:00:00.32I’m confused by this reported “underflow error” because all data in the data file are correct values. When I drop the spatial index and load the records by using the same control file, same data file and the same table, I don’t get any error and later I recreate the spatial index without errors. That should mean that the values in the data file are good, no “under” values.
    Also, when I don't use "DIRECT=yes" loading in the control file, then SQL*Loader loads all records with no errors, but it takes hours which is too long.
    I want to avoid to have to drop the spatial index every morning before the data loading process, because it is a very large table and it takes 45-60 minutes to recreate that index partition, and that much time delay is not good.
    Can anyone please provide an advice or point to some link with examples of how to use “sqlldr” to load large number of records into a spatial table with spatial index?
    Thank you,
    Milan

    Hi Milan,
    take a look to "Oracle Database Data Cartridge Developer's Guide" [http://docs.oracle.com/cd/E11882_01/appdev.112/e10765/dom_idx.htm#autoId50] (here is the 11g rel2 version but is the same with 9i)
    Domain Indexes and SQLLoader*
    SQLLoader conventional path loads and direct path loads are supported for tables on which domain indexes are defined, with two limitations:
    -The table must be heap-organized.
    +-The domain index cannot be defined on a LOB column.+
    To do a direct path load on a domain index defined on an IOT or on a LOB column, perform these tasks:
    -Drop the domain index
    -Do the direct path load in SQL*Loader.
    -Re-create the domain indexes.
    doesn't seem to be possible to use "direct path method" with spatial (domain) indexes
    i hope for you that there is a workaround ...
    good luck,
    CarlT

  • An error has ocurred during the execution of the Extract_Rom

    I have this problem
    Trouble Ticket Report----
    Upgrade to SAP NetWeaver'04s
    SID................: J2E
    Hostname...........: sapepd
    Install directory..: d:/usr/sap/J2E
    Upgrade directory..: D:\usr\sap\jupgrade
    Database...........: Microsoft SQL Server
    Operating System...: NT
    JDK version........: 1.4.2_11 Sun Microsystems Inc.
    SAPJup version.....: 1.1.101
    Source release.....: 630
    Target release.....: 700
    Current usages.....: DI;EP;AS
    ABAP stack present.: false
    The execution of PREPARE/EXTRACT/EXTRACT_ROMS ended in error.
    0 of 1 extractions have been successful. 1 extractions have not been
    successful. See previous messages.
    Could not extract AKK from mount point D:\DVD\51031778 Kernel7
    \KU_WINDOWS_I386. See previous messages.
    Could not execute file system operation with name Extract and
    parameters archive:SAPEXE.SAR,
    target_dir:D:\usr\sap\jupgrade\data\kernel.
    The SAPCAR process has ended with an error exit code 6. See
    D:\usr\sap\jupgrade\log\EXTRACT_SAPEXE.SAR_ROM_08.OUT.
    More information can be found in the log file
    D:\usr\sap\jupgrade\log\EXTRACT_ROMS_ROM_08.LOG.
    Use the information provided to trouble-shoot the problem. There might
    be an OSS note providing a solution to this problem. Search for OSS
    notes with the following search terms:
    com.sap.sdt.ucp.phases.PhaseTypeExtractRom
    com.sap.sdt.ucp.tools.dda.ManagedRomsException
    0 of 1 extractions have been successful. 1 extractions have not been
    successful. See previous messages.
    EXTRACT_ROMS
    PREPARE
    NetWeaver Upgrade
    SAPJup
    Java Upgrade
    END of Trouble Ticket Report----
    *******************BEGIN THE EXTRACT_ROMS_ROM_08.LOG********
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\usr\sap\jupgrade\log\EXTRACT_ROMS_ROM_08.LOG]/>
    <!PATTERN[EXTRACT_ROMS_ROM_08.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC10C8070000000006E60010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#PREPARE/EXTRACT/EXTRACT_ROMS#
    #1.5#C000AC10C8070000000006E70010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom#
    #1.5#C000AC10C8070000000006E80010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#dialog#ExtractRom#
    #1.5#C000AC10C8070000000006E90010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#romFile#RequiredRoms.xml#
    #1.5#C000AC10C8070000000006EA0010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:696)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:696)#Java###Checking phase parameters .#2#dialog#romFile#
    #1.5#C000AC10C8070000000006EB0010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:702)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:702)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
    #1.5#C000AC10C8070000000006F80010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    LABEL.ASC#
    #1.5#C000AC10C8070000000006F90010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000006FA0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FB0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000006FC0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SRM
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FD0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SCM
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FE0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_ERP
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FF0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_CRM
    LABEL.ASC#
    #1.5#C000AC10C8070000000007000010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    LABEL.ASC#
    #1.5#C000AC10C8070000000007010010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031778 Kernel7
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000007020010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007030010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007040010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C8070000000007050010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007060010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007070010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007080010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007090010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000070A0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C80700000000070B0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000070C0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C80700000000070D0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000070E0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C80700000000070F0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007100010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007110010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007120010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:95)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:95)#Java###Validatable parameter has been validated by validator .#2#DVDMountPointTable#DVDMountPointTable#
    #1.5#C000AC10C8070000000007130010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    LABEL.ASC#
    #1.5#C000AC10C8070000000007140010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000007150010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABEL.ASC#
    #1.5#C000AC10C8070000000007160010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000007170010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SRM
    LABEL.ASC#
    #1.5#C000AC10C8070000000007180010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SCM
    LABEL.ASC#
    #1.5#C000AC10C8070000000007190010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_ERP
    LABEL.ASC#
    #1.5#C000AC10C80700000000071A0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_CRM
    LABEL.ASC#
    #1.5#C000AC10C80700000000071B0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    LABEL.ASC#
    #1.5#C000AC10C80700000000071C0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031778 Kernel7
    LABELIDX.ASC#
    #1.5#C000AC10C80700000000071D0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C80700000000071E0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000071F0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C8070000000007200010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007210010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007220010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007230010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007240010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007250010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007260010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007270010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C8070000000007280010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007290010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C80700000000072A0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000072B0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C80700000000072C0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000072D0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:139)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:139)#Java###Process ID , name has been started.#2#36#SAPCAR#
    #1.5#C000AC10C80700000000072E0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:141)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:141)#Java###Command line: #2#  #D:
    usr
    sap
    jupgrade
    exe
    SAPCAR -xvf D:/DVD/51031778 Kernel7/KU_WINDOWS_I386/DBINDEP/SAPEXE.SAR -R D:
    usr
    sap
    jupgrade
    data
    kernel#
    #1.5#C000AC10C80700000000072F0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:142)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:142)#Java###Standard out: #2#  #D:
    usr
    sap
    jupgrade
    log
    EXTRACT_SAPEXE.SAR_ROM_08.OUT#
    #1.5#C000AC10C8070000000007300010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#36#
    #1.5#C000AC10C8070000000007310010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#36#SAPCAR#
    #1.5#C000AC10C8070000000007320010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#36#SAPCAR#6#
    #1.5#C000AC10C8070000000007330010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#Java###The SAPCAR process has ended with an error exit code 6. See D:
    usr
    sap
    jupgrade
    log
    EXTRACT_SAPEXE.SAR_ROM_08.OUT.##
    #1.5#C000AC10C8070000000007340010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#Java###Could not execute file system operation with name Extract and parameters archive:SAPEXE.SAR, target_dir:D:
    usr
    sap
    jupgrade
    data
    kernel.##
    #1.5#C000AC10C8070000000007350010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#Java###Could not extract AKK from mount point D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386. See previous messages.##
    #1.5#C000AC10C8070000000007360010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC10C8070000000007370010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#Java###The SAPCAR process has ended with an error exit code 6. See D:
    usr
    sap
    jupgrade
    log
    EXTRACT_SAPEXE.SAR_ROM_08.OUT.##
    #1.5#C000AC10C8070000000007380010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#Java###Could not execute file system operation with name Extract and parameters archive:SAPEXE.SAR, target_dir:D:
    usr
    sap
    jupgrade
    data
    kernel.##
    #1.5#C000AC10C8070000000007390010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#Java###Could not extract AKK from mount point D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386. See previous messages.##
    #1.5#C000AC10C80700000000073A0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:339)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:339)#Java###0 of 1 extractions have been successful. 1 extractions have not been successful. See previous messages.##
    #1.5#C000AC10C80700000000073B0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#PREPARE/EXTRACT/EXTRACT_ROMS#
    #1.5#C000AC10C80700000000073C0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/13 10:11:04#
    #1.5#C000AC10C80700000000073D0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/13 10:11:54#
    #1.5#C000AC10C80700000000073E0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:00:50.092#
    #1.5#C000AC10C80700000000073F0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
    /////////////////////////////////7END THE FILE////////////////////////777
    I read the notes and I donu00B4t find the problem
    Best Regards,
    Luis Moreno

    .

  • An error has occurred during the execution of the JSPM_MAIN phase.

    Hi,
    When I run the go.bat for running SLD, I am getting the following exception.
    An error has occurred during the execution of the JSPM_MAIN phase.
    Cannot initialize application data. Could not determine profile parameters. Error while retrieving value j2ee/dbhost,j2ee/dbname,j2ee/dbtype, with retriever com.sap.sdt.tools.sysinfo.ProfileDataRetriever. Could not extract value with key j2ee/dbhost,j2ee/dbname,j2ee/dbtype, from file D:/usr/sap/CE1/SYS/profile/DEFAULT.PFL. A possible reason could be that the path to the directory containing the sappfpar executable is not included in the PATH environment variable. Could not start process sappfpar. Error while executing process sappfpar. java.io.IOException: CreateProcess: sappfpar all pf=D:/usr/sap/CE1/SYS/profile/DEFAULT.PFL error=2
    You can find more information in the log file D:\usr\sap\CE1\J01\j2ee\JSPM\log\log_2007_07_11_18_49_45\JSPM_MAIN_1_01.LOG.
    Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words:
    com.sap.sdt.jspm.phases.PhaseTypeJSPM
    com.sap.sdt.jspm.gui.JspmUiException
    Cannot initialize application data.
    JSPM_MAIN
    JSPMPhases
    NetWeaver Upgrade
    SAPJup
    Java Upgrade
    Any inputs regarding this highly appreciated.
    Thanks
    Siva

    You can look at the following link, it may help
    https://www.sdn.sap.com/irj/sdn/directforumsearch?userid=3474257&rankby=10001&start=90

  • N unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    some one can help me please
    i have no idea what i must to do.
    an unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    The Exception Handler gave all the info that you need. No need to print the whole stack trace.
    The exception handler says
    Exception Details: java.lang.IllegalArgumentException
    TABLE1.NAME
    Look in the session bean (assuming that is where your underlying rowset is). Look in the _init() method for statements similar to the following:
    personRowSet.setCommand("SELECT * FROM TRAVEL.PERSON");
    personRowSet.setTableName("PERSON");
    What do you have?

  • Ng An exception occurred during the execution of the current web request.

    An exception occurred during the execution of the current web request. Please contact the administrator to review the stack trace in the event log for more information about the error.
    this error occured while making changes to the mapings, there was "&" in the source account and some test also loaded in the text,
    the versio n of FDM is 11.1.2.0
    I understand that because of loading & in the source account it is causing this issue,
    How to delete this invalid char from database, which table and column will contain this information, Please advise me how to proceed on this.
    thanks,
    msr

    This TSQL will do the trick. It's not the cleanest as I just wrote it, but it will dynamically remove the & from the data mapping tables and replace any invalid entries with the phrase INVALID.
    --Remove && from Data Maps
    --Charles Beyer ([email protected])
    --NOTES : 'Hackish' version for demonstration purposes
    -- Declare working variables
    DECLARE @strTableName varchar(255)
    DECLARE @strSql Nvarchar(500)
    -- Create cursor to iterate through each Data Map table.  Look in special table sysobjects to get a list of the tables.
    DECLARE crsDataMapTables Cursor For
       select name
          from sysobjects
          where name like 'tdatamap%'
             and xtype = 'U'
    Open crsDataMapTables
    Fetch Next from crsDataMapTables Into @strTableName  --Get the name of the first Data Map table and place it into working variable
    While @@FETCH_STATUS = 0 Begin  --While records (table names) exist, execute loop logic
    print 'Cleaning table : ' + @strTableName
      --Multi-pass updates to check the SrcKey, TargKey, and WhereClauseValue fields for the invalid character
      --Dynamic SQL is used below so that we can use the Table Name from the cursor..
      Set @strSQL = 'UPDATE ' + @strTableName + ' set SrcKey = ''Invalid'' where SrcKey like (''%&%'')'
      exec (@strSQL)
      Set @strSQL = 'UPDATE ' + @strTableName + ' set TargKey = ''Invalid'' where TargKey like (''%&%'')'
      exec (@strSQL)
      Set @strSQL = 'UPDATE ' + @strTableName + ' set WhereClauseValue = ''Invalid'' where WhereClauseValue like (''%&%'')'
      exec (@strSQL)
      Fetch Next from crsDataMapTables Into @strTableName
    End
    --Dispose of Cursor as we are done.
    Close crsDataMapTables
    Deallocate crsDataMapTables
     

  • Unhandled exception occurred during the execution of the workflow instance

    I had a workflow and library working with no issues, but had to move the library and export the workflow to another subsite (though on the same web site/collection).  I followed these how-tos:
    http://msdn.microsoft.com/en-us/library/office/jj819316%28v=office.15%29.aspx
    http://technet.microsoft.com/en-us/library/ee428301%28v=office.15%29.aspx
    Anyway, I've stripped all actions from the workflow and only have an Assign Task, but get this below:
    An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentException: ContentTypeId at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
    instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    To troubleshoot, I removed all library columns, removed then re-added the Custom Content type the New Document uses, and still the same error - with the workflow going into Suspended mode.
    I also tried the removal of the file from /Relationships%20List/allitems.aspx and de-activating then re-activating the SharePoint Publishing feature, also that didn't work.
    I've gone into ULS, but unable to find anything definitive, so not sure what to try next?
    Thank you,
    Chad

    Hi Chad,
    Glad to hear the issue is resolved. Content types could be used for multiple lists in SharePoint site at the same time.
    However, I'm not quite sure why you said the resolution is for a "bug". I read the article per your link:
    http://www.andrewconnell.com/blog/SP2013-Workflow-Custom-Task-Outcomes
    The article is showing how to create custom outcomes buttons in task forms. As I understand, the issue you encountered is that workflow migrated from the other site shows the suspended status.
    Please be more specific on the issue if assistance is needed. If this is the second question, I’d recommend you open another thread in the relevant forum and provide specific information about the issue. In order to avoid confusion and keep track of troubleshooting
    steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently.
    Thanks for the understanding.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase

    Hi ,
         During upgrade of EHP1 - NW 700 i am getting a error in configuration step like An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase
    The validation of the deploy queue was not successful. Request to check queue sapjup-queue completed with error. JSPM version is 7.01.4.0.17. Current JSPM log directory is /usr/sap/BIP/DVEBMGS00/j2ee/JSPM/log/log_2009_08_11_11_44_10.
    You can find more information in the log file /EHPI/java/log/PREPARE_JSPM_QUEUE_CSZ_01.LOG.
    Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue com.sap.sdt.sapjup.tools.sapjupjspm.JSPMRapiException The validation of the deploy queue was not successful. PREPARE_JSPM_QUEUE INIT NetWeaver Enhancement Package Installation SAPJup Java Enhancement Package Installation
    When reporting problems to SAP Support, attach the trouble ticket file /EHPI/java/log/TroubleTicket_01.txt to your message
    Plz help me to  analyze on this issue.
    Regards,
    Hari

    Hi Vasil Dimitranov
                              Thanks for your response.I have went through the log wat u said and found that only Java Patch JSPM is deployed in my system and the others patches are found be taken from the xml file and not deployed due to this below errors.
    Aug 11, 2009 11:53:33 AM [Error]: java.lang.NullPointerException:
    Aug 11, 2009 11:53:33 AM [Error]: Request to check queue sapjup-queue completed with error.
    Aug 11, 2009 11:53:33 AM [Error]: Request to check queue sapjup-queue completed with error.
    JSPM version is 7.01.4.0.17. Current JSPM log directory is /usr/sap/BIP/DVEBMGS00/j2ee/JSPM/log/log_2009_08_11_11_44_10
    Aug 11, 2009 11:53:33 AM [Info]: Message type received disconnect.
    Aug 11, 2009 11:53:33 AM [Info]: Remote connection is closed.
    Aug 11, 2009 11:53:34 AM [Warning]: Refusing connection.
    Aug 11, 2009 11:53:34 AM [Warning]: Network input/output exception has occurred: Error during read
    Aug 11, 2009 11:53:34 AM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
    Aug 11, 2009 11:53:34 AM [Info]: Start time: 2009/08/11 11:45:25.
    Aug 11, 2009 11:53:34 AM [Info]: End time: 2009/08/11 11:53:34.
    Aug 11, 2009 11:53:34 AM [Info]: Duration: 0:08:08.764.
    Aug 11, 2009 11:53:34 AM [Info]: Phase status is initial.
    Plz help me on this to analyze regarding the check queue sapjup-queue .
    Thanks in Advance.
    Regards,
    Hari

  • Error occured during the execution of the JSPM_main phase

    Hi,
    When ever I try to Start JSPM i get the following error saying that Cannot detect system kernel under the directory c:\usr\sap\EPD\sys directory and also error occured during the execution of the JSPM_main phase.
    Can any one help me in this regard.
    Thanks in advance.
    Thanks
    Venu

    Hi Anand,
    Please find the log file below.
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[C:\usr\sap\EPD\JC20\j2ee\JSPM\log\log_2007_04_03_16_57_45\JSPM_MAIN_1_01.LOG]/>
    <!PATTERN[JSPM_MAIN_1_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC190C09000000000016019B539300042D33A14D91C0#1175599679640#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#JSPM/JSPMPhases/JSPM_MAIN#
    #1.5#C000AC190C09000000000017019B539300042D33A14DD040#1175599679656#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.jspm.phases.PhaseTypeJSPM#
    #1.5#C000AC190C09000000000018019B539300042D33A1531000#1175599680000#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:560)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:560)#Java###Starting Initialize dialog...##
    #1.5#C000AC190C0900000000001E019B539300042D33A15C5AE8#1175599680609#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:462)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:462)#Java###Detecting system parameters...##
    #1.5#C000AC190C0900000000001F019B539300042D33A15C5AE8#1175599680609#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#C:
    usr
    sap
    EPD
    JC20
    j2ee
    JSPM
    log
    log_2007_04_03_16_57_45
    DETECT_SYSTEM_PARAMETERS_01.LOG#
    #1.5#C000AC190C0900000000002D019B539300042D33A1AA1558#1175599685703#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:483)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:483)#Java###Detection of system parameters has finished.##
    #1.5#C000AC190C0900000000002E019B539300042D33A1AA4FF0#1175599685718#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:470)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:470)#Java###Initialize dialog has been processed.##
    #1.5#C000AC190C0900000000002F019B539300042D33A1AA4FF0#1175599685718#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1043)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1043)#Java###Starting dialog...#1#LogIn#
    #1.5#C000AC190C09000000000039019B539300042D33AA43E180#1175599830000#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1048)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1048)#Java###Dialog has been confirmed by the user.#1#LogIn#
    #1.5#C000AC190C0900000000003A019B539300042D33AA467D78#1175599830171#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Checking connectivity for SDM server on host , port ...#2#aprins02#52018#
    #1.5#C000AC190C0900000000003B019B539300042D33AA539CD8#1175599831031#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Connection to SDM server on host , port is valid.#2#aprins02#52018#
    #1.5#C000AC190C0900000000003C019B539300042D33AA65F810#1175599832234#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:192)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:192)#Java###Detecting components of the J2EE engine...##
    #1.5#C000AC190C0900000000003D019B539300042D33AA65F810#1175599832234#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#C:
    usr
    sap
    EPD
    JC20
    j2ee
    JSPM
    log
    log_2007_04_03_16_57_45
    DETECT_SYSTEM_COMPONENTS_01.LOG#
    #1.5#C000AC190C09000000000052019B539300042D33B5C8DEE8#1175600023265#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logError(JspmExtLoggingManager.java:275)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logError(JspmExtLoggingManager.java:275)#Java###Error during operation. For more information about the operation, see the previous message. For more information about the error, see the next messages.##
    #1.5#C000AC190C09000000000053019B539300042D33B5C91D68#1175600023281#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:258)#######Thread[main,5,main]##0#0#Warning#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:258)#Java###There are some WARNING messages in the child log .#1#C:
    usr
    sap
    EPD
    JC20
    j2ee
    JSPM
    log
    log_2007_04_03_16_57_45
    DETECT_SYSTEM_COMPONENTS_01.LOG#
    #1.5#C000AC190C09000000000054019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC190C09000000000055019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:285)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:285)#Java###java.io.IOException: CreateProcess: C:/usr/sap/EPD/JC20/exe/disp+work -V error=2##
    #1.5#C000AC190C09000000000056019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:284)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:284)#Java###Error while executing process C:/usr/sap/EPD/JC20/exe/disp+work.##
    #1.5#C000AC190C09000000000057019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:130)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:130)#Java###Could not start process C:/usr/sap/EPD/JC20/exe/disp+work.##
    #1.5#C000AC190C09000000000058019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.KernelRetriever.getCommandOutput(KernelRetriever.java:240)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.KernelRetriever.getCommandOutput(KernelRetriever.java:240)#Java###disp+work executable file cannot be run.##
    #1.5#C000AC190C09000000000059019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:767)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:767)#Java###Could not detect current system kernel in the C:
    usr
    sap
    EPD
    JC20
    exe directory.##
    #1.5#C000AC190C0900000000005A019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:435)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:435)#Java###Could not detect central instance kernel in directory C:
    usr
    sap
    EPD
    JC20
    exe.##
    #1.5#C000AC190C0900000000005B019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentsFromSystem(DetectKernelComponent.java:464)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentsFromSystem(DetectKernelComponent.java:464)#Java###Could not detect system kernel under the C:
    usr
    sap
    EPD
    SYS directory.##
    #1.5#C000AC190C0900000000005C019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectComponentsFromSystem(DetectKernelComponent.java:554)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectComponentsFromSystem(DetectKernelComponent.java:554)#Java###Could not detect version information of the current system kernel.##
    #1.5#C000AC190C0900000000005D019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:220)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:220)#Java###Could not detect deployed components.##
    #1.5#C000AC190C0900000000005E019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:676)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:676)#Java###Cannot initialize application data.##
    #1.5#C000AC190C0900000000005F019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#JSPM/JSPMPhases/JSPM_MAIN#
    #1.5#C000AC190C09000000000060019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/04/03 16:57:59#
    #1.5#C000AC190C09000000000061019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/04/03 17:03:43#
    #1.5#C000AC190C09000000000062019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:05:43.640#
    #1.5#C000AC190C09000000000063019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
    Thanks
    Venu

  • Where does the execution of the code begin

    Hi all,
    I am wondering where the execution of the code below begin.
    Declare
    cursor c_zip(p_state in zipcode.state%type) is
    select zip, city , state
    from zipcode
    where state=p_state
    begin
    for r_zip in c_zip('NJ')
    loop
    dbms_output.put_line(r_zip.city||' '||r_zip.zip');
    end loop;
    end;

    At the first statement after the begin keyword?

  • Netsh becoming cetsh during the execution of the script

    netsh becoming cetsh during the execution of the script - for DHCP

    Hi Venky6262,
    As Philippe said, please post more detailed information about this issue to help us to troubleshoot, like what do you want to achieve with the cmd netsh, your code and the error.
    In addition, there are good examples to use Netsh commands for DHCP:
    http://technet.microsoft.com/en-us/library/cc787375(v=ws.10).aspx
    Best Regards,
    Anna

  • Rotating images: Poor performance and incorrect direction of the dropshadow

    I've created an extremely simple application that is rotating a bitmap image. I have two issues:
    1) The performance is quite frankly terrible with stuttering and screen tearing. Is there any way to improve the performance or is this a known limitation of JFX's rendering?
    2) The Image has a dropshadow, but as the image rotates so does the shadow which is not the behavior I want since that makes it look like the lightsource is also moving. How can I get around this? I want the shadow to stay on the bottom right. Am I putting the dropshadow in the wrong location in the scenegraph?
    import javafx.scene.text.Text;
    import javafx.scene.text.Font;
    import javafx.scene.effect.*;
    import javafx.scene.image.ImageView;
    import javafx.scene.image.Image;
    import javafx.animation.Interpolator;
    import javafx.animation.Timeline;
    var x: Number;
    Timeline {
        repeatCount: Timeline.INDEFINITE
        autoReverse: true
        keyFrames: [
             at (0s) {x => 0.0},
             at (5s) {x => 365.0 tween Interpolator.LINEAR}
    }.play();
    Stage {
        title: "Application title"
        width: 800
        height: 1000
        scene: Scene {
            content: [
                ImageView {
                    image: Image {
                        url: "{__DIR__}image.jpg"
                    effect: DropShadow {
                        offsetX: 5
                        offsetY: 5
                    translateX: 10
                    translateY: 10
                    rotate: bind x
    }

    lol, nope, that still won't show the image... i guess i have really screwed up my install on this system. i had nb6.5 beta then i installed the new nb for javafx but it created an new instance of the app instead of updating the old one. so i removed both and installed the new one... think i will try and setup the nb on a totally clean system and open the app from there and recompile to see if somethin hinky is going on with that.

  • The execution of the query doesn't end

    Hi,
    I have this completely nested query:
    SELECT S.sname from S where
       S# in (select S# from table where 
      P# in (select P# from table1 where table1.name
    = 'Bodg') 
      and
               Jn in (select J# from table 2 where table2.something= 'hjgfjh')
       but when pressed execute, the execution doesn't stop, in fact it doesn't execute.
    Can anybody help me what is the problem please?
    Thanks

    This is a C# forum.  Do you have some problem with C# code?
    You may be better off in an SQL forum.  But I suggest that you decide if the query doesn't execute or executes forever.  The two problems you have cited are exact opposites of each other.
    If the code doesn't execute then you need to explain what 'pressed execute' means and show us the associated code.
    If the code doesn't stop then you should double check if it just runs for a long time.  How big are the tables, what indexes are defined, why don't you use a join are the kinds of questions that will be asked in an SQL forum.
    Paul Linton

  • Block the execution of the click on Button Create (Item 1)

    Hi every body
    Does anyone know how to stop execution of the standard treatment generated by the click on Item "1" :  Create.
    In Fact, I want to make a condition before the execution of treatment corresponding to the click on the Item "1" :
    if the condition is met so "Standard Create" run normally , in the other case, "Standard Create" is stopped.
    Thank you for heping me,
    Haifa ABID

    Capture the Item Event, then check the FormUID, EventType = ItemPressed, BeforeAction = True and ItemUID = "1". Then check your condition. If StandardCreate = True then do nothing, if StandardCreate = False then BubbleEvent = False this will stop the rest of the standard action from processing.
    E.g.
    Private Sub oApplication_ItemEvent(ByVal FormUID As String, ByRef pVal As _
    SAPbouiCOM.ItemEvent, ByRef BubbleEvent As Boolean) Handles oApplication.ItemEvent
    If FormUID = "YourFormUID" And pVal.EventType = _
    SAPbouiCOM.BoEventTypes.et_ITEM_PRESSED And pVal.BeforeAction = True _
    And pVal.ItemUID = "1" Then
                If StandardCreate = False Then
                    BubbleEvent = False
                    YourProcess()
                End If
            End If
    End Sub

  • How do you reset/close the execution using the API?

    I am trying to programmatically launch different sequences then look at the final results.  The results of the execution always show the results from the first call to
    TS_ExecutionGetResultStatus.  Even if I execute a different sequence.  Is there a method to close the last execution results? 
    Thanks,
    Mike
    Here is a code snippet of what I am doing.
        tsErrChk(TSUI_SequenceFileViewMgrRun (tsoHandles.sequenceFileViewMgr, &errorInfo, CA_DEFAULT_VAL, NULL));
        CA_DiscardObjHandle(tsoHandles.Executions);
        tsErrChk(TSUI_ApplicationMgrGetExecutions(tsoHandles.applicationMgr, &errorInfo, &tsoHandles.Executions));
        tsErrChk(TSUI_ExecutionsGetItem(tsoHandles.Executions, &errorInfo, 0, &tsoHandles.Execution));
        if (bWait)
        { // Wait
            while (Test_Running())
            { // Running
                ProcessSystemEvents();
                iCount++;
            } // Running
        } // Wait
        tsErrChk(TS_ExecutionGetResultStatus(tsoHandles.Execution, &errorInfo, &szResults));
        if (strcmp(szResults, "Passed") == 0)
            bRet = TRUE;
        if (strcmp(szResults, "Failed") == 0)
            bRet = FALSE;
    Solved!
    Go to Solution.

    Hey Mike,
    It looks like you're on the right track but from the code you pasted you are always referencing the same execution.  Because the TS_ExecutionGetResultStatus function just returns the status of whichever Execution object you decide to pass it, you first should verify that you passing it the correct object. When you call the TSUI_ExecutionsGetItem function:
    tsErrChk(TSUI_ExecutionsGetItem(tsoHandles.Executions, &errorInfo, 0, &tsoHandles.Execution));
    you are passing a value of zero for the ItemIdx input. Try changing your value from 0 to any number between 1 and one less than the result of TSUI_ExecutionsGetCount (because of zero indexing). Give this a try and see if this helps.
    Lars

  • Why do I get "Insufficient memory to continue the execution of the program" in SQL Service Report Services

    Hi fellas,
    I'm facing some serious issues with SSRS. I've tried to create a map report in SQL server reporting service 2008R2. I've insert a map using ESRI shapefile and connected it to my Dataset. Everything seemed to be fine up until I've tried to preview the results
    and I got this:
    I've tried to resolve the problem by increasing the "MaximumTotalPc", but then I got this:
    Ever since this happened my SSRS is acting like it has gotten a virus. I've tried to delete the report, but it doesn't let me and the window I've posted above keeps on popping up every few seconds while the program is open.
    Any idea why do I get it and how can I deal with it?
    P.S. I'm not any kind of developer and I'm not really familiar with the technical language. I need an explanation written in user friendly language, please :-)

    Hi Ellie55,
    According to your description that you are experiencing the issue when you are creating the ESRI shapefile map on the SSRS 2008 R2, you got some error “the number of map point elements for “Map1” exceeds the maximum limits for map” when you click  to
    preview the map, you trying to set the properties of “MaximumTotalPointCount” to fix this issue but cause another error about the “insufficient memory”, right?
    By default, a map can have 20,000 map elements or 1,000,000 points. If your map exceeds these limits, you can increase the MaximumTotalPointCount and the MaximumSpatialElementCount, but it may cause the insufficient memory because of the too much points
    and elements. So I recommend you that you can use one of the following approaches for you have got problem increase the limitations:
    Remove a layer.
    Decrease the map resolution.
    Decrease the map viewport coordinates to view a smaller area.
    If the spatial data comes from a report dataset, set a filter to limit the data from the dataset. The filter must be set on a field that is not a spatial data type.
    If the spatial data comes from a SQL Server database, change the query to use spatial functions to limit the data to a smaller area.
    Details information for your reference :
    http://prashantmishrasblog.blogspot.com/2012/10/using-map-in-ssrs-reports-part1.html
    http://msdn.microsoft.com/en-us/library/ee240843.aspx
    As you this error also caused you can’t delete the report, please try to close the program in the task manager and find the path of project in your computer to delete the .rdl file in your workspace and redesign the map again.
    Any problem, please feel free to ask
    Regards
    Vicky Liu

Maybe you are looking for