WPA IO stack analysis

REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f
xperf -on PROC_THREAD+LOADER+CSWITCH+FILENAME+FILE_IO+FILE_IO_INIT+DRIVERS+FLT_IO_INIT+FLT_IO+FLT_FASTIO+FLT_IO_FAILURE -f kernel.etl -stackwalk CSwitch+DiskReadInit+DiskWriteInit+DiskFlushInit+FileCreate+FileCleanup+FileClose+FileRead+FileWrite+MiniFilterPreOpInit+MiniFilterPostOpInit -BufferSize 1024 -MaxBuffers 1024 -MaxFile 1024 -FileMode Circular
I'm trying to get a stack walk of an application that is experiencing very slow IO to a StorNext mounted SAN. The SAN is mounted via the StorNext client. We are not certain where the latency is occurring. Therefore I have decided to use Windows Performance
Analyzer to try and track down the issue. Above are the settings we are using.
In the File IO Duration by process, thread and etc… All the stacks show n/a. However for the MiniFilter graph I get all the stacks. Unfortunately it does not seems that the StorNext mounted volume is using a MiniFilter, as there are no threads listed that
relate to the write operation to the SAN. 
How can I get the stack for FILE_IO? Also if anyone is familiar with the StorNext client and how it implements its' driver that would be greatly appreciated.
Thanks in advanced
dblk

Update the latency we are seeing is up to 59 sec to write 512KB buffer. This issue is really crippling a live production environment. Any help would be greatly appreciated.
dblk
stacks
no stacks

Similar Messages

  • How to Automate Error Stack Analysis   -- How to guide

    I was wondering if anybody has successfully implemented this How to Guide
    "http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e01c300f-e02f-2c10-46a8-b5ac929bc4ac"
    I am getting errors while saving the code for the Functional Module listed in there, and would like to get the exact working Abap code.
    Thanks.

    Hi,
    pls chk this link it may help you...
    http://help.sap.com/saphelp_nw70/helpdata/en/42/fbd598481e1a61e10000000a422035/content.htm
    rgds,

  • JDBInsight 2.0 Released - True J2EE/JDBC Resource Transaction Analysis !!

    DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation of J2EE performance management products from JInspired.
    Downloads: http://www.jinspired.com/products/jdbinsight/downloads/index.html
    JDBInsight is the first product to effectively integrate Java profiling information with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived from its support of the Java VM Profiling Interface (JVMPI) such as Java call stack analysis, cpu, blocking and waiting measurements at the transaction path level. Clock measurements are adjusted for blocking, waiting and gc pauses. New features in this release
    - New console user interface: Many new informative visualizations of J2EE transactions and performance execution profiles have been added. Including call stack graphs, entry point tree maps, sequence diagrams, call stack and transaction transcripts. Additional views included allow for navigation of the performance profile via database table or column, Java package, class, or method, technology classification, SQL tokens, or transaction entry points.
    - Java call stack classification engine: Developers, testers, database and J2EE server administrators can now better understand the interaction of various Java enterprise technologies with corporate databases. Classifications are available for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets, JTS, JDBC, and Struts.
    - Terminal services: The terminal services add-on provides a quick and easy way to communicate with multiple servers without having to use a graphical user interface. This facilitates the streamlined connection, activation and deactivation of profiles on local or remote servers with the ability to control multiple servers from a single terminal. The terminal environment provides a powerful environment to create and schedule snapshot information, in order to monitor servers at regular intervals, with the ability to store and retrieve snapshots from any mounted drive, as well as providing a rich set of commands, that can be executed from saved scripts, to assist in analysis of this highly detailed profile data.
    - Transaction demarcations: JDBInsight 2.0 is the first performance management product to have the ability to detect and present resource transaction demarcations - allowing visual sub-transaction identification.
    - Resource Management: JDBInsight keeps counters representing objects states for each JDBC interception point create a resource object. When a JDBC resource changes state the allocation site counters are updated. This helps to pinpoint source code locations where resource objects are created and not closed properly or freed from memory. Because an interception is a combination of call stack and SQL the view caters for generic J2EE application frameworks which create objects based on application parameters and callers.
    - Xml expor: Various statistical measurements can be viewed in Xml format and copied into applications for custom report generation.
    - Server options: Additional system properties to customize the small amount of overhead added during runs.
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying the performance tuning and testing of J2EE(tm) applications, which access data through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the access of enterprise data by J2EE(tm) client-, web-, and bean containers. The analysis can encompass transaction executions, from multiple J2EE(tm) containers. JDBInsight captures timing and execution information for enterprise data accessed by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an Entity Bean using a container's persistence engine. JDBInsight can also profile non-J2EE applications that access enterprise data through the JDBC(tm) API.
    What distinguishes JDBInsight from other profiling and performance management tools on the market is that JDBInsight provides analysis from a sequence perspective instead of simply showing a call tree. Inefficiencies in J2EE applications occur mainly at the transaction level such as repeating the execution of a particular SQL locally and globally. JDBInsight facilitates the recognition of database interaction patterns that exhibit inefficiencies when viewed in terms of the sequential execution of a business and/or resource transaction.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for Application Performance Tuning and Testing that focuses directly on early identification within the development and testing lifecycle. Jinspired offers sophisticated analytical tools, that capture transactional behaviour and performance timing information, across multiple containers in a single console, and presents this information intuitively to the user "Visualizing the Invisible".

    any one

  • JDBInsight 2.0 Released - True Transaction Analysis !!!

    Check out the product and revised documentation at:
    http://www.jinspired.com/products/jdbinsight/downloads/index.html
    PRESS RELEASE
    =============
    DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
    in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
    of J2EE performance management products from JInspired.
    JDBInsight is the first product to effectively integrate Java profiling information
    with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
    from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
    analysis, cpu, blocking and waiting measurements at the transaction path level.
    Clock measurements are adjusted for blocking, waiting and gc pauses. New features
    in this release
    - New console user interface: Many new informative visualizations of J2EE transactions
    and performance execution profiles have been added. Including call stack graphs,
    entry point tree maps, sequence diagrams, call stack and transaction transcripts.
    Additional views included allow for navigation of the performance profile via
    database table or column, Java package, class, or method, technology classification,
    SQL tokens, or transaction entry points.
    - Java call stack classification engine: Developers, testers, database and J2EE
    server administrators can now better understand the interaction of various Java
    enterprise technologies with corporate databases. Classifications are available
    for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
    JTS, JDBC, and Struts.
    - Terminal services: The terminal services add-on provides a quick and easy way
    to communicate with multiple servers without having to use a graphical user interface.
    This facilitates the streamlined connection, activation and deactivation of profiles
    on local or remote servers with the ability to control multiple servers from a
    single terminal. The terminal environment provides a powerful environment to create
    and schedule snapshot information, in order to monitor servers at regular intervals,
    with the ability to store and retrieve snapshots from any mounted drive, as well
    as providing a rich set of commands, that can be executed from saved scripts,
    to assist in analysis of this highly detailed profile data.
    - Transaction demarcations: JDBInsight 2.0 is the first performance management
    product to have the ability to detect and present resource transaction demarcations
    - allowing visual sub-transaction identification.
    - Resource Management: JDBInsight keeps counters representing objects states for
    each JDBC interception point create a resource object. When a JDBC resource changes
    state the allocation site counters are updated. This helps to pinpoint source
    code locations where resource objects are created and not closed properly or freed
    from memory. Because an interception is a combination of call stack and SQL the
    view caters for generic J2EE application frameworks which create objects based
    on application parameters and callers.
    - Xml export: Various statistical measurements can be viewed in Xml format and
    copied into applications for custom report generation.
    - Server options: Additional system properties to customize the small amount of
    overhead added during runs.
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying
    the performance tuning and testing of J2EE(tm) applications, which access data
    through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
    access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
    analysis can encompass transaction executions, from multiple J2EE(tm) containers.
    JDBInsight captures timing and execution information for enterprise data accessed
    by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
    Entity Bean using a container's persistence engine. JDBInsight can also profile
    non-J2EE applications that access enterprise data through the JDBC(tm) API.
    What distinguishes JDBInsight from other profiling and performance management
    tools on the market is that JDBInsight provides analysis from a sequence perspective
    instead of simply showing a call tree. Inefficiencies in J2EE applications occur
    mainly at the transaction level such as repeating the execution of a particular
    SQL locally and globally. JDBInsight facilitates the recognition of database interaction
    patterns that exhibit inefficiencies when viewed in terms of the sequential execution
    of a business and/or resource transaction.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
    Application Performance Tuning and Testing that focuses directly on early identification
    within the development and testing lifecycle. Jinspired offers sophisticated analytical
    tools, that capture transactional behaviour and performance timing information,
    across multiple containers in a single console, and presents this information
    intuitively to the user "Visualizing the Invisible".

    Dear Friend...
    ur error concerning...
    "In default.properties, I changed {transaction/sessionbean}.timeout from 0 to 100. Sometime after this, error.log contained:
    "SQL Exception: Table or view 'Entity1BeanTable' already exists in
    schema 'APP'". "
    Ur XML file contains
    "<create-table-deploy>true</create-table-deploy>"
    The first time u deploy ur bean,table is created with the query specified.once u shutdown the server
    "<delete-table-undeploy>false</delete-table-undeploy>" property does not allow the app server to drop the table.
    This leaves u with the above mentioned error/exception when u start the server for the second time as ur server tries to create the table again.Moreover this will not hinder the starting process of the server.
    ganesh

  • JDBInsight 2.0 Released - True JDBC Transaction Analysis !!!

    Check out the new product release and revised documentation at:
    http://www.jinspired.com/products/jdbinsight/downloads/index.html
    PRESS RELEASE
    =============
    DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
    in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
    of J2EE performance management products from JInspired.
    JDBInsight is the first product to effectively integrate Java profiling information
    with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
    from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
    analysis, cpu, blocking and waiting measurements at the transaction path level.
    Clock measurements are adjusted for blocking, waiting and gc pauses. New features
    in this release
    - New console user interface: Many new informative visualizations of J2EE transactions
    and performance execution profiles have been added. Including call stack graphs,
    entry point tree maps, sequence diagrams, call stack and transaction transcripts.
    Additional views included allow for navigation of the performance profile via
    database table or column, Java package, class, or method, technology classification,
    SQL tokens, or transaction entry points.
    - Java call stack classification engine: Developers, testers, database and J2EE
    server administrators can now better understand the interaction of various Java
    enterprise technologies with corporate databases. Classifications are available
    for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
    JTS, JDBC, and Struts.
    - Terminal services: The terminal services add-on provides a quick and easy way
    to communicate with multiple servers without having to use a graphical user interface.
    This facilitates the streamlined connection, activation and deactivation of profiles
    on local or remote servers with the ability to control multiple servers from a
    single terminal. The terminal environment provides a powerful environment to create
    and schedule snapshot information, in order to monitor servers at regular intervals,
    with the ability to store and retrieve snapshots from any mounted drive, as well
    as providing a rich set of commands, that can be executed from saved scripts,
    to assist in analysis of this highly detailed profile data.
    - Transaction demarcations: JDBInsight 2.0 is the first performance management
    product to have the ability to detect and present resource transaction demarcations
    - allowing visual sub-transaction identification.
    - Resource Management: JDBInsight keeps counters representing objects states for
    each JDBC interception point create a resource object. When a JDBC resource changes
    state the allocation site counters are updated. This helps to pinpoint source
    code locations where resource objects are created and not closed properly or freed
    from memory. Because an interception is a combination of call stack and SQL the
    view caters for generic J2EE application frameworks which create objects based
    on application parameters and callers.
    - Xml export: Various statistical measurements can be viewed in Xml format and
    copied into applications for custom report generation.
    - Server options: Additional system properties to customize the small amount of
    overhead added during runs.
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying
    the performance tuning and testing of J2EE(tm) applications, which access data
    through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
    access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
    analysis can encompass transaction executions, from multiple J2EE(tm) containers.
    JDBInsight captures timing and execution information for enterprise data accessed
    by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
    Entity Bean using a container's persistence engine. JDBInsight can also profile
    non-J2EE applications that access enterprise data through the JDBC(tm) API.
    What distinguishes JDBInsight from other profiling and performance management
    tools on the market is that JDBInsight provides analysis from a sequence perspective
    instead of simply showing a call tree. Inefficiencies in J2EE applications occur
    mainly at the transaction level such as repeating the execution of a particular
    SQL locally and globally. JDBInsight facilitates the recognition of database interaction
    patterns that exhibit inefficiencies when viewed in terms of the sequential execution
    of a business and/or resource transaction.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
    Application Performance Tuning and Testing that focuses directly on early identification
    within the development and testing lifecycle. Jinspired offers sophisticated analytical
    tools, that capture transactional behaviour and performance timing information,
    across multiple containers in a single console, and presents this information
    intuitively to the user "Visualizing the Invisible".

    Check out the new product release and revised documentation at:
    http://www.jinspired.com/products/jdbinsight/downloads/index.html
    PRESS RELEASE
    =============
    DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
    in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
    of J2EE performance management products from JInspired.
    JDBInsight is the first product to effectively integrate Java profiling information
    with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
    from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
    analysis, cpu, blocking and waiting measurements at the transaction path level.
    Clock measurements are adjusted for blocking, waiting and gc pauses. New features
    in this release
    - New console user interface: Many new informative visualizations of J2EE transactions
    and performance execution profiles have been added. Including call stack graphs,
    entry point tree maps, sequence diagrams, call stack and transaction transcripts.
    Additional views included allow for navigation of the performance profile via
    database table or column, Java package, class, or method, technology classification,
    SQL tokens, or transaction entry points.
    - Java call stack classification engine: Developers, testers, database and J2EE
    server administrators can now better understand the interaction of various Java
    enterprise technologies with corporate databases. Classifications are available
    for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
    JTS, JDBC, and Struts.
    - Terminal services: The terminal services add-on provides a quick and easy way
    to communicate with multiple servers without having to use a graphical user interface.
    This facilitates the streamlined connection, activation and deactivation of profiles
    on local or remote servers with the ability to control multiple servers from a
    single terminal. The terminal environment provides a powerful environment to create
    and schedule snapshot information, in order to monitor servers at regular intervals,
    with the ability to store and retrieve snapshots from any mounted drive, as well
    as providing a rich set of commands, that can be executed from saved scripts,
    to assist in analysis of this highly detailed profile data.
    - Transaction demarcations: JDBInsight 2.0 is the first performance management
    product to have the ability to detect and present resource transaction demarcations
    - allowing visual sub-transaction identification.
    - Resource Management: JDBInsight keeps counters representing objects states for
    each JDBC interception point create a resource object. When a JDBC resource changes
    state the allocation site counters are updated. This helps to pinpoint source
    code locations where resource objects are created and not closed properly or freed
    from memory. Because an interception is a combination of call stack and SQL the
    view caters for generic J2EE application frameworks which create objects based
    on application parameters and callers.
    - Xml export: Various statistical measurements can be viewed in Xml format and
    copied into applications for custom report generation.
    - Server options: Additional system properties to customize the small amount of
    overhead added during runs.
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying
    the performance tuning and testing of J2EE(tm) applications, which access data
    through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
    access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
    analysis can encompass transaction executions, from multiple J2EE(tm) containers.
    JDBInsight captures timing and execution information for enterprise data accessed
    by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
    Entity Bean using a container's persistence engine. JDBInsight can also profile
    non-J2EE applications that access enterprise data through the JDBC(tm) API.
    What distinguishes JDBInsight from other profiling and performance management
    tools on the market is that JDBInsight provides analysis from a sequence perspective
    instead of simply showing a call tree. Inefficiencies in J2EE applications occur
    mainly at the transaction level such as repeating the execution of a particular
    SQL locally and globally. JDBInsight facilitates the recognition of database interaction
    patterns that exhibit inefficiencies when viewed in terms of the sequential execution
    of a business and/or resource transaction.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
    Application Performance Tuning and Testing that focuses directly on early identification
    within the development and testing lifecycle. Jinspired offers sophisticated analytical
    tools, that capture transactional behaviour and performance timing information,
    across multiple containers in a single console, and presents this information
    intuitively to the user "Visualizing the Invisible".

  • CR2008 Purchasing Report needed

    Hi
    Has anyone created a Purchasing report in Crystal Reports 2008 based on AP Invoices and AP Credit Notes. I have created a WPA (Weekly Purchase Analysis) report but based off AP Invoice table (OPCH & PCH1), now the company is wanting to have Credit Notes added to this report.
    I have created a UDF called WPA on the OPCH form which is a Mandatory field so when running the WPA Report you can run it by WPA # and Project to get your results (Parameter), now how will I acheive this by adding the AP Credit Note fields ORPC & RPC1 to the report so if I create x2 Invoice's (different suppliers) for say WPA # 1010 and I Credit one, on the WPA Report I will want to see Invoice 1 (NumCard = 1) = R100, Invoice 2 (NumCard = 2) = 100, Credit Note 1 (NumCard = 2) = -100, Total = 100.
    Any suggestions or ideas will be most helpful.
    Regards
    Kurt Walters

    Hi Kurt,
    That is possible using "Shared Variable".
    Check this link: [Sub-report data in report|Sub-report data in report].
    1.Initialize a shared variable in Report.
    2.Pass the Credit memo value to the 'Shared variable' in Sub-report
    3.Now create a formula in Report like
          Sub-total = {Invoice total} - {SharedVariable}
    In order to know more about shared variable, post a separate question in [SAP Crystal Reports Design - Forum|SAP Crystal Reports;.
    Hope this helps.
    Regards,
    Bala

  • Zfs list on solaris express 11 always reads from disk (metadata not cached)

    Hello All,
    I am migrating from OpenSolaris 2009.11 to SolarisExpress 11.
    I noticed that "zfs list" takes longer than usual, and is not instant. I then discovered via a combination of arcstat.pl and iostat -xnc 2 that every time a list command is issued, there are disk reads. This leads me to believe that some metadata is not getting cached.
    This is not the case in OpenSolaris where repeated "zfs list" do not cause disk reads.
    Has anyone observed this, and do you know of any solution?
    This is on an IDLE sustem with 48 GB of RAM - with plenty of free memory.

    Hi Steve,
    Great info again. I am still new to dtrace, particularly navigating probes and etc. I've seen that navigation tree before.
    I would like to start by answering your questions:
    Q) Have you implemented any ARC tuning to limit the ARC?
    -> No out of the box config
    Q) Are you running short on memory? (the memstat above should tell you)
    -> Definetelly not. I have 48 GB ram, ARC grows to about 38 GB and then stops growing. I can reproduce problem at boot at will with only 8GB used. Nothing is getting aged out of the ARC at that time. Only those metadata reads never get stored.
    Q) Are any of your fileystems over 70% full?
    -> No. I am curious, what changes when this happens? Particularly in regards to ARC - perhaps another discussion, I don't want to distract this subject.
    Q) Have you altered what data is/is not cached? ($ zfs get primarycache)
    -> No - everything should be cached. I also have recently added l2cache (80GB). The metadata is not cached there neither.
    I am not yet familiar with dtrace processing capabilities, thus I had to parse output via perl. Notice how each execution has the exact same number of misses. This is due to the fact that these particular datablocks (metadata blocks) are not cached in the arc at all:
    :~/dtrace# perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h' ^C
    :~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
    dtrace: script './zfs_list.d' matched 4828 probes
    dtrace: pid 11021 has exited
    $VAR1 = {
              ':arc-hit' => 2,
              ':arc-miss' => 192
    :~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
    dtrace: script './zfs_list.d' matched 4828 probes
    dtrace: pid 11026 has exited
    $VAR1 = {
              ':arc-hit' => 1,
              ':arc-miss' => 192
    :~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
    dtrace: script './zfs_list.d' matched 4828 probes
    dtrace: pid 11031 has exited
    $VAR1 = {
              ':arc-hit' => 12,
              ':arc-miss' => 192
    :~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
    dtrace: script './zfs_list.d' matched 4828 probes
    dtrace: pid 11036 has exited
    $VAR1 = {
              ':arc-hit' => 4,
              ':arc-miss' => 192
    :~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
    dtrace: script './zfs_list.d' matched 4828 probes
    dtrace: pid 11041 has exited
    $VAR1 = {
              ':arc-hit' => 27,
              ':arc-miss' => 192
    :~/dtrace# I presume next steps would be to perform stack analysis on which blocks are been not cached. I don't know how to do this ... I am guessing this is a mid-function probe? "| arc_read_nolock:arc-miss" I don't know how to access it's parameters.
    FYI, here's an example of a cache miss in my zfs list:
      0  -> arc_read                             
      0    -> arc_read_nolock                    
      0      -> spa_guid                         
      0      <- spa_guid                         
      0      -> buf_hash_find                    
      0        -> buf_hash                       
      0        <- buf_hash                       
      0      <- buf_hash_find                    
      0      -> add_reference                    
      0      <- add_reference                    
      0      -> buf_cons                         
      0        -> arc_space_consume              
      0        <- arc_space_consume              
      0      <- buf_cons                         
      0      -> arc_get_data_buf                 
      0        -> arc_adapt                      
      0          -> arc_reclaim_needed           
      0          <- arc_reclaim_needed           
      0        <- arc_adapt                      
      0        -> arc_evict_needed               
      0          -> arc_reclaim_needed           
      0          <- arc_reclaim_needed           
      0        <- arc_evict_needed               
      0        -> zio_buf_alloc                  
      0        <- zio_buf_alloc                  
      0        -> arc_space_consume              
      0        <- arc_space_consume              
      0      <- arc_get_data_buf                 
      0      -> arc_access                       
      0       | arc_access:new_state-mfu         
      0        -> arc_change_state               
      0        <- arc_change_state               
      0      <- arc_access                       
      0     | arc_read_nolock:arc-miss           
      0     | arc_read_nolock:l2arc-miss 
      0      -> zio_read                         
      0        -> zio_create                     
      0          -> zio_add_child                
      0          <- zio_add_child                
      0        <- zio_create                     
      0      <- zio_read                         
      0      -> zio_nowait                       
      0        -> zio_unique_parent              
      0          -> zio_walk_parents             
      0          <- zio_walk_parents             
      0          -> zio_walk_parents             
      0          <- zio_walk_parents             
      0        <- zio_unique_parent              
      0        -> zio_execute                    
      0          -> zio_read_bp_init             
      0            -> zio_buf_alloc              
      0            <- zio_buf_alloc              
      0            -> zio_push_transform         
      0            <- zio_push_transform         
      0          <- zio_read_bp_init             
      0          -> zio_ready                    
      0            -> zio_wait_for_children      
      0            <- zio_wait_for_children      
      0            -> zio_wait_for_children      
      0            <- zio_wait_for_children      
      0            -> zio_walk_parents           
      0            <- zio_walk_parents           
      0            -> zio_walk_parents           
      0            <- zio_walk_parents           
      0            -> zio_notify_parent          
      0            <- zio_notify_parent          
      0          <- zio_ready                    
      0          -> zio_taskq_member             
      0          <- zio_taskq_member             
      0          -> zio_vdev_io_start            
      0            -> spa_config_enter           
      0            <- spa_config_enter           
      0            -> vdev_mirror_io_start       
      0              -> vdev_mirror_map_alloc    
      0                -> spa_get_random         
      0                <- spa_get_random         
      0                -> vdev_lookup_top        
      0                <- vdev_lookup_top        
      0              <- vdev_mirror_map_alloc    
      0              -> vdev_mirror_child_select 
      0                -> vdev_readable          
      0                  -> vdev_is_dead         
      0                  <- vdev_is_dead         
      0                <- vdev_readable          
      0                -> vdev_dtl_contains      
      0                <- vdev_dtl_contains      
      0              <- vdev_mirror_child_select 
      0              -> zio_vdev_child_io        
      0                -> zio_create             
      0                  -> zio_add_child        
      0                  <- zio_add_child        
      0                <- zio_create             
      0              <- zio_vdev_child_io        
      0              -> zio_nowait               
      0                -> zio_execute            
      0                  -> zio_vdev_io_start    
      0                    -> spa_syncing_txg    
      0                    <- spa_syncing_txg    
      0                    -> zio_buf_alloc      
      0                    <- zio_buf_alloc      
      0                    -> zio_push_transform 
      0                    <- zio_push_transform 
      0                    -> vdev_mirror_io_start
      0                      -> vdev_mirror_map_alloc
      0                      <- vdev_mirror_map_alloc
      0                      -> vdev_mirror_child_select
      0                        -> vdev_readable  
      0                          -> vdev_is_dead 
      0                          <- vdev_is_dead 
      0                        <- vdev_readable  
      0                        -> vdev_dtl_contains
      0                        <- vdev_dtl_contains
      0                      <- vdev_mirror_child_select
      0                      -> zio_vdev_child_io
      0                        -> zio_create     
      0                          -> zio_add_child
      0                          <- zio_add_child
      0                        <- zio_create     
      0                      <- zio_vdev_child_io
      0                      -> zio_nowait       
      0                        -> zio_execute    
      0                          -> zio_vdev_io_start
      0                            -> vdev_cache_read
      0                              -> vdev_cache_allocate
      0                              <- vdev_cache_allocate
      0                            <- vdev_cache_read
      0                            -> vdev_queue_io
      0                              -> vdev_queue_io_add
      0                              <- vdev_queue_io_add
      0                              -> vdev_queue_io_to_issue
      0                                -> vdev_queue_io_remove
      0                                <- vdev_queue_io_remove
      0                              <- vdev_queue_io_to_issue
      0                            <- vdev_queue_io
      0                            -> vdev_accessible
      0                              -> vdev_is_dead
      0                              <- vdev_is_dead
      0                            <- vdev_accessible
      0                            -> vdev_disk_io_start
      0                            <- vdev_disk_io_start
      0                          <- zio_vdev_io_start
      0                        <- zio_execute    
      0                      <- zio_nowait       
      0                    <- vdev_mirror_io_start
      0                  <- zio_vdev_io_start    
      0                  -> zio_vdev_io_done     
      0                    -> zio_wait_for_children
      0                    <- zio_wait_for_children
      0                  <- zio_vdev_io_done     
      0                <- zio_execute            
      0              <- zio_nowait               
      0            <- vdev_mirror_io_start       
      0          <- zio_vdev_io_start            
      0          -> zio_vdev_io_done             
      0            -> zio_wait_for_children      
      0            <- zio_wait_for_children      
      0          <- zio_vdev_io_done             
      0        <- zio_execute                    
      0      <- zio_nowait                       
      0    <- arc_read_nolock                    
      0  <- arc_read                              I've compared the output of a single-non cached metadata read, to a single read from filesystem by running dd and read from a file that is not in the cache. The only difference in the stack is that the non-cached reads are missing:
      0                                -> vdev_queue_offset_compare
      0                                <- vdev_queue_offset_compare This is called in "-> vdev_queue_io_to_issue ". But I don't think this is relevant, perhaps related to metadata vs file data read.
    What do you think should be next?

  • JDBInsight 2.0 Announced - See @ JavaOne Next Week

    DUBLIN, IRELAND - 5 June, 2003 - JInspired (www.jinspired.com), a leader in J2EE™ transaction analysis, today announced JDBInsight 2.0, the next generation of J2EE performance management products from JInspired. JDBInsight will be available for preview at JavaOne 2003 in San Francisco.
    JDBInsight is the first product to effectively integrate Java profiling information with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived from its support of the Java VM Profiling Interface (JVMPI) such as Java call stack analysis, CPU, blocking and waiting measurements at the transaction path level.
    The "Best Java Application Monitoring Tool" just got better. JDBInsight 2.0 sports a new client interface that once again shows that JInspired is the leader in delivery of rich and informative visualizations of J2EE transactions and performance execution. The products innovative use of symbols and graphics is unrivalled within the Java performance assurance industry.
    With the new Java call stack classification engine developers, testers and J2EE administrators can now understand the interaction of various technologies with corporate databases. Classifications engines are available for Java enterprise technologies such as EJB, JSP, Servlets, JTS, CORBA, JDBC, JCA, Web Services, JDO and Struts. JInspired will also be announcing new engines over the coming weeks for various web/persistence technologies such as JavaServer Faces, Tapestry, WebWork, and Hibernate.
    JDBInsight 2.0 is the first performance management product to have the ability to detect and present resource transaction demarcations – allowing visual sub-transaction identification.
    Take JDBInsight Product Tour
    http://www.jinspired.com/products/jdbinsight/tour.html
    Read JDBInsight 2.0 Product Factsheet
    http://www.jinspired.com/products/jdbinsight/jdbinsightv2_0_productsheet.pdf
    In addition to the JDBInsight Version 2.0 feature rich client interface, JDBInsight also provides a suite of functional command-line utilities, JDBInsight 2.0 Terminal Services. The Terminal Services component of JDBInsight 2.0 delivers the server to a wide variety of desktops without the need for graphical environments. The JDBInsight 2.0 Terminal Services provides a quick and easy way to communicate with multiple servers without having to use a graphical user interface. This facilitates the streamlined connection, activation and deactivation of profiles on local or remote servers with the ability to control multiple servers from a single terminal.
    These Terminal Services also provide a powerful environment to create and schedule snapshot information, in order to monitor servers at regular intervals, with the ability to store and retrieve snapshots from any mounted drive, as well as providing a rich set of commands to assist in analysis of this highly detailed data. Learn about JDBInsight 2.0 Terminal Services
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying the performance tuning and testing of J2EE™ applications, which access data through the Java Database Connectivity (JDBC™) API. JDBInsight analyses the access of enterprise data by J2EE™ client-, web-, and bean containers. The analysis can encompass transaction executions, from multiple J2EE™ containers. JDBInsight captures timing and execution information for enterprise data accessed by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC™ or an Entity Bean using a container's persistence engine. JDBInsight can also profile non-J2EE applications that access enterprise data through the JDBC™ API.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for Application Performance Tuning and Testing that focuses directly on early identification within the development and testing lifecycle. Jinspired offers sophisticated analytical tools, that capture transactional behaviour and performance timing information, across multiple containers in a single console, and presents this information intuitively to the user "Visualizing the Invisible”.

    Glad to hear I'm not the only lucky one! Reading these forums has helped me a lot, but it has also made me a bit paranoid. I understand that Support > Discussions is by its nature focused on problems, though. I've always thought that technology companies tend to focus more on adding features, whereas they'd be better off to focus on making all the features work properly all the time for everyone! Apple has often been a leader in this regard (best overall service record of any major hardware company by numerous consumer polls), but they've been growing fast lately and I confess I fear their quality control may have some challenges 'scaling' to the larger size of their user base. It's great to see so many helpful users in these forums trying to act as volunteer apple support staff!
    2 ghz Core2duo iMac 17"   Mac OS X (10.4.8)  

  • JDBInsight 2.0 Performance Tool @ JavaOne 2003

    JInspired Announces JDBInsight 2.0 @ JavaOne 2003
    DUBLIN, IRELAND - 5 June, 2003 - JInspired (www.jinspired.com), a leader in J2EE™
    transaction analysis, today announced JDBInsight 2.0, the next generation of J2EE
    performance management products from JInspired. JDBInsight will be available for
    preview at JavaOne 2003 in San Francisco.
    JDBInsight is the first product to effectively integrate Java profiling information
    with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
    from its support of the Java VM Profiling Interface (JVMPI) such as Java call
    stack analysis, CPU, blocking and waiting measurements at the transaction path
    level.
    The "Best Java Application Monitoring Tool" just got better. JDBInsight 2.0 sports
    a new client interface that once again shows that JInspired is the leader in delivery
    of rich and informative visualizations of J2EE transactions and performance execution.
    The products innovative use of symbols and graphics is unrivalled within the Java
    performance assurance industry.
    With the new Java call stack classification engine developers, testers and J2EE
    administrators can now understand the interaction of various technologies with
    corporate databases. Classifications engines are available for Java enterprise
    technologies such as EJB, JSP, Servlets, JTS, CORBA, JDBC, JCA, Web Services,
    JDO and Struts. JInspired will also be announcing new engines over the coming
    weeks for various web/persistence technologies such as JavaServer Faces, Tapestry,
    WebWork, and Hibernate.
    JDBInsight 2.0 is the first performance management product to have the ability
    to detect and present resource transaction demarcations – allowing visual sub-transaction
    identification.
    Take JDBInsight Product Tour
    http://www.jinspired.com/products/jdbinsight/tour.html
    Read JDBInsight 2.0 Product Factsheet
    http://www.jinspired.com/products/jdbinsight/jdbinsightv2_0_productsheet.pdf
    In addition to the JDBInsight Version 2.0 feature rich client interface, JDBInsight
    also provides a suite of functional command-line utilities, JDBInsight 2.0 Terminal
    Services. The Terminal Services component of JDBInsight 2.0 delivers the server
    to a wide variety of desktops without the need for graphical environments. The
    JDBInsight 2.0 Terminal Services provides a quick and easy way to communicate
    with multiple servers without having to use a graphical user interface. This facilitates
    the streamlined connection, activation and deactivation of profiles on local or
    remote servers with the ability to control multiple servers from a single terminal.
    These Terminal Services also provide a powerful environment to create and schedule
    snapshot information, in order to monitor servers at regular intervals, with the
    ability to store and retrieve snapshots from any mounted drive, as well as providing
    a rich set of commands to assist in analysis of this highly detailed data. Learn
    about JDBInsight 2.0 Terminal Services
    About JDBInsight
    JDBInsight is an innovative enterprise development product, aimed at simplifying
    the performance tuning and testing of J2EE™ applications, which access data through
    the Java Database Connectivity (JDBC™) API. JDBInsight analyses the access of
    enterprise data by J2EE™ client-, web-, and bean containers. The analysis can
    encompass transaction executions, from multiple J2EE™ containers. JDBInsight captures
    timing and execution information for enterprise data accessed by Servlets, JavaServer
    Pages, Session- and Entity Beans using JDBC™ or an Entity Bean using a container's
    persistence engine. JDBInsight can also profile non-J2EE applications that access
    enterprise data through the JDBC™ API.
    About JInspired
    JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
    Application Performance Tuning and Testing that focuses directly on early identification
    within the development and testing lifecycle. Jinspired offers sophisticated analytical
    tools, that capture transactional behaviour and performance timing information,
    across multiple containers in a single console, and presents this information
    intuitively to the user "Visualizing the Invisible”.

    CPU speed may play a role but after experimenting with Activity Monitor it looks like available memory is key. For example if I export a 100% crop of a 10 megapixel RAW file to JPG it sometimes takes over a minute. When this happens there is essentially zero free memory. Also, preview updates are usually running in the background. At other times there is ~100MB free memory and it performs better.
    I do agree with a post elsewhere that on my machine, at least, the sliders have so much lag it is hard to get the effect you want. Constantly over and under shooting. Might be livable since some nice effects can be had if you work at it.

  • Process chains time outs and hangs with no error msg - in SP13

    Hi all,
    We are having all kind of weird problems after we patched our system with SP13. Our process chain time outs and hangs, but surprisingly we never get any error msg. And scarier part is, the problem seems to be intermittent. PC runs fine on some days and hangs on some.
    Further analysis into the dump – as below
    Termination occurred in the ABAP program "SAPLRSSM" -
    in "RSSM_SLEEP_DEBUG".
    The main program was "SAPMSSY1 ".
    In the source code the termination point is in (Include) program "LRSSMU39".
    This refers to an issue that appears to have been addressed by OSS Note
    934648(meant for SP8). This notes also indicates to populate RSADMIN table to
    exclude "RSSM_SLEEP_DEBUG". Not sure if this note is valid for SP13? However we went ahead and populated the RSADMIN table.
    So now we have no clue what’s going on and where to fix the issue.
    As per SAP suggestion we applied the following notes:
    0000653996  Analyzing lock situations
    0000893563  Correction: Deadlock on completion of a remote chain
    0000994007  Corrections: Deadlock with external status query
    0001005481  Correction: Process successful, but there is no instance
    0001047174  Correction: Incorrect scope when locking in process chains
    0001051957  Correction: TIME_OUT during dialog confirmation of processes
    0001083660  Report for error stack analysis
    Nothing seems to help us. And SAP suggested a few options, which we implemented to no rescue.
    I’m sure that many of the customers have applied SP13, and want some feedback from them, if this is happening in their systems too?
    If so, how did you fix this issue?
    Or this situation is unique to us?Please note that no settings were changed as of SP13 to that of what they were in SP12(unless it is a side effect of the patch itself). Everything worked fine with SP12 and is still working on the BIP system. All the problems are in BIQ patched to SP13.
    Any pointers or insight would be appreciated. We have a customer msg open with SAP, and going back and forth, but nothing seemed to work as of today.
    Thanks,
    Voodi

    Not sure which OSS helped us get past the issue, as SAP asked us to apply a ton of notes. But along which the notes, SAP has some suggestions for us, which we think did the magic. After the implementation of the suggestin we never faced the same issue again. The suggestion by SAP:
    move the process chain callback in a batch job by executing
    program RSSM_TRACE_SWITCH and selecting the flag "verifcation
    of asynchronous processes - execute in batch".
    Lemme know if this doesnt fix the issue, I can give all the notes that SAP asked us to apply.
    Message was edited by:
            voodi

  • Analysis of stack trace

    Hi Experts,
    i have an null pointer exception error in a message on adapter engine level.
    It's allways the same message what occurs this error.
    The message content in netweaver message monitoring contains following error:
    Application error occurred during request processing.
      Details:   Error [javax.servlet.ServletException: null], with root cause [java.lang.NullPointerException: null].
    Exception id: [0019B9F3058800A2000005E400001834000496E2E17B13EF]
    I have read the sap note 859465. There is recommended to take a look in the stack trace.
    Now i want to analyse the stack trace of the pi.
    But i have no idea where to find that stack trace.
    Can somebdy help me?
    Many thanks!!!

    if you are using PI 7.1, then use NWA and Java system reports/log viewer link to get details
    or by default you can find them - /usr/sap/<SID>/DVEBGS001/j2ee/cluster/server0/log.

  • STACK 13 ANALYSER DOES NO WORK WITH SAPGUI 6.40

    HI,
    We are not able to use the analyser with the following installation.(Query button are not active)
    (Query designer is working).
    STACK 13
    SAPGUI 6.40  (SP25)
    Latest hot fix .
    Security is not active on  excel.
    When we use the sapgui 7 it's working, but we cannot upgrade the sapgui for end users.
    Is there something to check regarding .net version?
    Is the latest version working with sap gui 6.40
    Thanks for yout help.

    Hi Antoine,
    Have you seen this weblog? Here these issues are discussed in details.
    Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
    Regards,
    Praveen

  • Crash dump analysis:  arguments on the kernel stack

    I�m working with SunOS 5.8 on SPARC sun4u.
    System hangs up periodically (due to some error in our proprietary FS ).
    So I�m trying to figure out what really happens - syncing system and then inspect crash dump using adb(mdb).
    Having printed all the kernel threads I found few of them that are matter of interest for me, but all the tracebacks show me garbage instead of calling arguments.
    Below is one such thread:
    0x300025912e8: lwp procp wchan
    3000258ee20 30002ccaab8 31001001240
    0x300025911f8:
    pc sp
    cv_wait+0x38 2a10056ac01
    page_lock+0x118(1041c560, 1041be70, 0, 0, 31001001200, 1)
    page_lookup+0x104(10410800, 10428698, 1, 1, 226e0, 1041bd60)
    ufs_getpage+0x620(2000, 1, 30002f137b0, 1, 0, 2000)
    segmap_fault+0x110(2000, 0, 2a751b48000, 2, 2, 0)
    fbread+0xa8(1041a400, 2a751b48000, 2a751b48000, 200, 2a10056b9d8, 0)
    ufs_readdir+0x160(1fff, 30002f13670, 418, 0, 2a10056bac0, 200)
    getdents64+0xe8(30001aec198, 12, 418, 180e88, 30002f562b8, 0)
    syscall_trap32+0xa8(12, 180e88, 418, 64, 0, 0)
    I inspected this thread�s stack using various macroses provided by adb :
    i.e. Stackregs, stacktrace but seems that only pc and fp registers have been saved for each frame in stack. Anyway looks like incoming parameters have not been put into frames. Its probably ok, cause as I for as I know Solaris puts registers onto stack in case of register window underflow and overflow traps.
    Question: how to extract incoming params for functions that comprise thread�s stack

    First of all, since you are already in Sol 8, just
    switch to mdb from adb - the former one provides much
    more macroes and built-in commands for crash dumpanalysis.
    - thats off topic, sorry. This is just a matter of preferences (constantly jumping from 5.8 to 5.7, most macroses that are in use written by me )
    Also, the parameters to page_lock look pretty sane.May be I don"t understand something. Anyway :
    Here is a line from stack
    page_lock+0x118(1041c560, 1041be70, 0, 0, 31001001200, 1)
    This is a prototype:
    int page_lock(page_t *pp, se_t se, kmutex_t *lock, reclaim_t reclaim)
    Usually %o0(%i0) is used for the first argument , so 0x1041c560 should point to a valid page_t structure (if we are not about to panic), but points somewhere else:
    1041c560$<pagepse_mutex+0x240:vnode hash vpnext
    0 0 0
    pse_mutex+0x258:vpprev next prev
    0 0 0
    pse_mutex+0x270:offset selock lckcnt
    0 0 0
    pse_mutex+0x27e:cowcnt cv io_cv
    0 0 0
    pse_mutex+0x284:iolock_state fsdata state
    0 0 0
    Anyway, the stack trace entry in question is:
    ufs_readdir+0x160(1fff, 30002f13670, 418, 0, 2a10056bac0, 200)
    while prototype is
    static int ufs_readdir(struct vnode *, struct uio *, struct cred *, int *);
    Looks like poiner to vnode_t is 0x1fff�
    Here seems to be 2 possibilities:
    1)We are really passing some garbage as parameters
    or
    2)Register windows were not flushed onto stack
    Actually this thread was not active when I did sync to machine.
    Is it true that when kernel is rescheduling thread it drops registers onto stack ?
    What docs should I refer to? (except �Panic!� by Chris Drake )
    ask Tiffi where the
    hell they are).
    Sorry man, it's probably one of my old ones...
    Lets leave Tiffi alone ... and you know that she"s not an author of what I"m currently fixing :)
    .... Even more, you know exectly who was it :)
    Thank you for answering.
    Any comments?

  • Tools for root cause analysis of stack corruption?

    I'm experiencing extremely rare stack corruption that results in SEGV core dumps for a large and complex C++ program. Having run all the standard tools such as IBM Rational Purify, Sun mdb/libumem and dbx/rtc (although unfortunately using dbx check -access takes inordinately long and eventually crashes before the main() function is executed), I am no closer to discovering the root cause of the stack corruption. I'm confident based on the tools run and on the stack trace from the core dump that the problem is not heap corruption, but stack corruption.
    The environment is Sun Studio 12 (but not update 1) on Solaris 10 on SPARC. The program is compiled with minor optimisation (-xO2 -xbuiltin=%all).
    Is anyone aware of other tools or approaches that could help pinpoint the problem? Your help would be much appreciated!
    Thanks in advance,
    Simon

    If you are in fact having stack corruption issues, I don't think any of the tools you mentioned other than Purify would help you identify it.
    You may also be simply running out of stack space, and not having corruption issues. Is your app multi-threaded? If so, you could increase the stack size your threads use to something larger than the default.
    Another thing you can look for are syslog entries stating "no swap space to grow stack" for your process, you've run out of virtual memory. To avoid this, you can "pre-allocate" your stack memory with code similar to this:
    void growStack( size_t bytes )
        char *mem = ( char * ) alloca( bytes );
        memset( mem, 0, bytes );
        return;
    }That code, when called, will force the creation of stack memory virtual pages backed by swap, before your server gets into a situation where free memory might be in short supply.
    I also seem to recall that Solaris under certain circumstances will allocate stack memory with the MAP_NORESERVE option, which means swap space won't be reserved for your stack. If your process gets swapped out, its stack(s) will be lost and you'll probably get a SIGSEGV or SIGBUS. See this bug:
    [http://bugs.opensolaris.org/view_bug.do?bug_id=1221729|http://bugs.opensolaris.org/view_bug.do?bug_id=1221729]
    I remember working a similar issue for a customer running large apps on Sun E15Ks, maybe about 5 years ago. To work around this behavoir, I think you'll need to explicitly allocate stack memory for any threads you may be creating. I think that's what we had to do.

  • Multiple HTML-files in one stack / link another HTML-file in a stack

    Hi,
    I want to integrate a webapp (html/js) into a stack of a dps-folio. All the HTML works fine ... all no problem, but at clicking the first link on the initial HTML-document the next (local) HTML-File is opened in a slider with a "ready"/"Fertig"-bar at the top. But I want, that all html files are seamlessly loaded in the same view.
    At this point i found: http://help.adobe.com/en_US/digitalpubsuite/using/WS67cb9e293e2f1f60-8ad81e812b10bfd837-80 00.html and i made the file "NativeOverlays.config" and moved it to the described location. After that, the behaviour was correct in the desktop-preview-app of the DPS, but it still fails on the iPad-Adobe-Viewer.
    How can i link between HTML-files without any interuption or sliding?
    Thank you!
    Christian

    Hi Tim,
    Thanks for replying. I have looked for "PDFBookBinder class" in xml publisher user guide for ver 5.6.2. I didn't get any reference of this text. Can you please guide me to a tutorial/link where i can get more information about this class.
    Also, i originally thought of similar to your second logic, as my design basis. Oracle process generates the xml file in output directory which i can get. What i didn't get is how do i "pick them up and merge" using publisher. Also, is there way to do this merging process using pl/sql ? Can you please give little more information on your second approach.
    My original plan of action is that i will create a report set in which i will call oracle seeded report for all 7 payrolls in a sequential manner. Then using the child requests of the report set i will get to 7 xml files generated by seeded oracle process. Then the piece i am not sure of , i will use those 7 files to generate a single xml file having payroll name as tree top for each output. Once single xml is ready, i can easily design a template and register the process to generate output as Excel.This process will not require me to actually change any data or do any calculation. It will only reformatting the feilds we see and abiity to see all 7 payroll at one time rather then entering these numbers manually into an excel to do analysis.
    Please provide your feedback, if you think above plan is not feasible or need corrections.
    Best Regards,
    Ankur

Maybe you are looking for