Performance Check - ABAP and Database color bars

Hello everyone,
When i go for the performance check of my object, i see Database in red bar and ABAP in green bar.
The smaller the difference between these two bars, the better.
But what does the color mean ? ( Somethimes the smaller bar is Red )
Thanks

Here is the explanation (depends % of total) in [sap library - SE30|http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617d2ae68c11d2b2ab080009b43351/frameset.htm]
>
shalaxy s wrote:
> The smaller the difference between these two bars, the better.
NO, it depends completely of what does your program!

Similar Messages

  • Performance with MySQL and Database connectivity toolbox

    Hi!
    I'm having quite some problems with the performance of MySQL and Database connectivity toolbox. However, I'm very happy with the ease of using database connectivity toolbox. The background is:
    I have 61 variables (ints and floats) which I would like to save in the MySQL-database. This is no problem, however, the loop time increases from 8ms to 50ms when using the database. I have concluded that it has to do with the DB Tools Insert Data.vi and I think that I have some kind of performance issue with this VI. The CPU never reach more the 15% of its maximum performance. I use a default setup and connect through ODBC.
    My questions are:
    1. I would like to save 61 variables each 8-10ms, is this impossible using this solution?
    2. Is there any way of increasing the performance of the DB Tools Insert Data.vi or use any other VI?
    3. Is there any way of adjusting the MySQL setup to achieve better performance?
    Thank you very much for your time.
    Regards,
    Mattias

    First of all, thank you very much for your time. All of you have been really good support to me.
    >> Is your database on a different computer?  Does your loop execute 61 times? 
    Database is on the same computer as the MySQL server.
    The loop saves 61 values at once to the database, in one SQL-statement.
    I have now added the front panel and block diagram for my test-VI. I have implemented the queue system and separate loops for producer and consumer. However, since the queue is building up faster then the consumer loop consumes values, the queue is building up quite fast and the disc starts working.
    The test database table that I add data to is created by a simple:
    create table test(aa int, bb char(15));
    ...I'm sure that this can be improved in some way.
    I always open and close the connection to the database "outside the loop". However, it still takes some 40-50 ms to save the data to the database table - so, unfortunatly no progress to far. I currently just want to save the data.
    Any more advise will be gratefully accepted.
    Regards,
    Mattias
    Message Edited by mattias@hv on 10-23-2007 07:50 AM
    Attachments:
    front panel 2.JPG ‏101 KB
    block diagram.JPG ‏135 KB

  • How to check ABAP and Portal connections

    Hi
    I was told to check ABAP and Portal connections. What does that mean? And what and where to check?
    Thanks
    Annie

    Hi
    Thanks for your reply.
    We are on BI 7. SP16.
    When i run that in se38, i am getting the following information: No default in RSPOR_T_PORTAL and no user parameter RSPOR_DEFAULT_PORTAL" when i clicked on yes(tickmark), view BI_Content of web template 0ANALYSIS_PATTERN(A) is displayed
    There are two options with check box are present 1. 30 template present (Unchecked) 2. BI- Template Present (checked), and a big XML code is displayed.
    When i executed in browser mode, it says Windows cannot find'/irj/servlet/prt/portal............... make sure you typed the name correctly and then try again. to serch for a file, click the start button, and then click search"
    What does that mean?
    Regards
    Annie
    Edited by: Annie on Nov 17, 2008 5:38 AM

  • % of load on abap and database in se30

    Hi,
      I have created a report for vendor balance, it is working fine and also i am getting data in very short time  i want to know about performance analysis with SE30
      When i am running report of only one month then on abap  it is taking   85 %  and on database  12% and on system 3 %
    ans same report when i am running for 6 to 8 months  it is taking   65 %  and on database  33% and on system 2 %, i sit ok ,    can you give some tips how to do it and how to reduce load from particular like abap or database or system  or whatever i am getting is right.
    regards,
      zafar

    Hi Zafar,
    First of all, the relative usages of the three components depends on the amount of data; for different loads on the system and the DB, the output will be different.
    Now, if you check the output of SE30 carefully (the graph screen), you will see two buttons on top, one of them is the List Display button. Click that button to see a list of statements / code blocks.
    Here, if you sort by the "Gross %" or the "Net %" columns, you'll get to know which statement is consuming maximum system resources. If you double-click on any line, the system takes you directly to that code block (there is also another button on this screen to show you the actual code). Try to optimise these code segments for better performance.
    Typically, there will be entries like "Fetch <DBTable>" which will show a high system usage. These are your SELECT statements which access the database. Optimise your SELECT queries as far as possible.
    Hope this is useful! Please revert if you need anything else.
    Cheers,
    Shailesh.
    Always provide feedback for useful answers

  • ABAP AND DATABASES

    Hi Experts..
    I would like to know how to create a databases in SQL and have access from ABAP.. to Modify, Consult and do the basic operations like insert information, drop and modify in the respective tables.
    I'm ussing MiniSap Minigui 6.2 on Windows XP and the BCUSER
    Thank you very much for your help
    REGARDS

    HI Araceli,
    Database Access using Advanced Business Application Programming (ABAP)
    Basics :
    Accessing the Database in the R/3 System is performed through the interface provided by the SAP System, which in the SAP System is referred to as the Database Interface. A user can access the database from his/her program through Open SQL and Native SQL depending upon the circumstances.
    About SQL
    The Structured Query Language (SQL) is a largely standardized language, which is used for accessing relational databases. It can be divided as follows:
    Data Manipulation Language (DML)
    These statements are for reading and changing data in database tables.
    Data Definition Language (DDL)
    These statements are for creating and administering database tables.
    Data Control Language (DCL)
    These statements are used for authorization and consistency checks.
    So  each database has a programming interface. This programming interface allows the user to access the database tables by using SQL statements. But, these SQL statements in the programming interfaces are not fully standardized. So, you must refer to the documentation of that system for a list of the SQL statements available and also their correct syntax in order to access a specific database system.
    Interface thru data base
    Each work process on an application server must have a database interface if you want to make the R/3 system independent of the database system, and also to use it correctly despite the differences in the SQL syntax between various databases. By means of this interface only, the R/3 system can communicate with the database. All of the database requests from the R/3 system are converted into the correct Standard SQL statements for the database system by the database interface. In order to perform this function, it has to use a database-specific component, which shields the differences between database systems from the rest of the database interface. You have to choose the appropriate layer when installing the R/3 system. A user can access a database from a program through Open SQL and Native SQL.
    Open SQL
    Open SQL are statements that make up a subset of Standard SQL which is fully integrated in ABAP. Open SQL consists of Data Manipulation Language (DML) which is a part of Standard SQL.
    One of the ways to access the database from a program is Open SQL. These Open SQL statements are nothing but a subset of Standard SQL, which is fully integrated in ABAP. Irrespective of which database system the R/3 installation is using, they allow you to access data. When I said that, Open SQL consists of the Data Manipulation Language (DML). I meant that it allows you to read (i.e. to SELECT) and change (For example  to INSERT, UPDATE, DELETE) data.
    Moreover, Open SQL also goes beyond Standard SQL. This is to provide statements that can simplify or speed up database access in conjunction with other ABAP constructions. Apart from that, it also gives you the freedom to buffer certain tables on the application server, thereby enabling you to save excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. As far as buffer storage is concerned, they may be stored in two parts: the working memory of the current work process, and the shared memory for all work processes on an application server. The data in the various buffers is synchronized at set intervals by buffer management where an R/3 system is distributed across more than one application server. It should be noted that data in the buffer is not always up to date when you are buffering the database. That is why you should only use the buffer for data which does not change often. You can specify whether a table can be buffered in its definition in the ABAP Dictionary.
    Open SQL consists of a set of ABAP statements. These statements perform operations on the central database in the R/3 system. The results of the operations and any error messages which come out of it are independent of the current database system. Thus, uniform syntax and semantics for all of the database systems supported by SAP is provided by Open SQL. Regardless of the current database system, the ABAP programs, which use Open SQL statements only, will work in any R/3 system. Moreover, Open SQL statements work only with database tables that have been created in the ABAP Dictionary.
    You have the freedom to combine columns belonging to different database tables to a database view (or view for short) in the ABAP Dictionary. Views are also handled in exactly the same way as database tables in Open SQL statements.
    Some Open SQL keywords are as follows:
    SELECT - It reads data from database tables.
    INSERT - It adds rows to database tables.
    UPDATE - It changes the contents of rows of database tables.
    MODIFY - It inserts rows into database tables or changes the content of existing rows.
    DELETE - It deletes rows from database tables.
    OPEN CURSOR, FETCH, CLOSE CURSOR - It reads rows of database tables using the cursor.
    Return Codes
    The following two system fields are filled with return codes by all Open SQL statements:
    SY-SUBRC: The system field SY -SUBRC contains the value 0 after every Open SQL statement if the operation was successful. When a value is other than 0, then it is unsuccessful.
    SY-DBCNT: The system field SY-DBCNT contains the number of database lines processed after an open SQL statement.
    Native SQL
    The other possible way to access the database from a program is Native SQL. It is only loosely integrated into ABAP. It allows access to all of the functions contained in the programming interface of the respective database system. Native SQL statements are not checked and converted as compared to Open SQL statements. Unlike Open SQL, these are sent directly to the database system. The function of the database-dependent layer remains minimal when you use Native SQL. The Programs which use Native SQL are written specifically for a database system. You should avoid using Native SQL wherever possible when writing R/3 applications. However, you can use it in some parts of the R/3 Basis System, for instance, for creating or changing table definitions in the ABAP Dictionary.
    Regardless of the database platform that your R/3 system is using, Open SQL allows you to access database tables, which are declared in the ABAP Dictionary. Native SQL allows you to use database specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary. Aside from that, you can also integrate data that is not part of the R/3 system.
    As a rule, an ABAP program that contains database-specific SQL statements will not run under different database systems. You have to use Open SQL statements only, if your program is used on more than one database platform.
    You must proceed with the EXEC SQL statement, and follow the ENDEXEC statement to use a: Native SQL statement. For example
    Listing 1
    EXEC SQL [PERFORMING
    ENDEXEC.There is no period after Native SQL statements. Also, using quotation marks (") or an asterisk (*) at the beginning of a native SQL statement's line does not introduce a comment as it would in normal ABAP syntax. You need to know if the table and field names are case-sensitive in your chosen database.
    The data is transported between the database table and the ABAP program using host variables in Native SQL statements. These are preceded in a Native SQL statement by a colon ( and are declared in the ABAP program. The elementary structures can be used as host variables. The structures of an INTO clause are treated exceptionally, as though all of their fields are listed individually. If the selection in a Native SQL SELECT statement is a table, then you can pass it to ABAP line by line using the PERFORMING addition. For each line read, the program calls a subroutine
    . Further, you can process the data within the subroutine. 
    After the ENDEXEC statement, SY-DBCNT contains the number of lines processed as it does in Open SQL. In almost all cases, SY-SUBRC contains the value a after the ENDEXEC statement. Cursor operations form an exception: after FETCH, SY-SUBRC is 4 if no more records could be read. This is also applied when you read a result set using EXEC SQL PERFORMING.
    Native SQL Scope 
    Native SQL is very important as it allows you to execute nearly all available statements through the SQL programming interface (usually known as SQL Call Interface or similar) for directly executing SQL program code (using EXEC IMMEDIATE or a similar command). The statements that are not supported are listed in the following section:
    ·         Native SQL and the Database Interface,
    ·         Native SQL and Transactions
    ·         Native SQL and the Database Interface
    Native SQL statements bypass the R/3 database interface. With the database buffer on the application server, there is no table logging, and no synchronization. Therefore, you should use Open SQL to change database tables declare in the ABAP dictionary wherever possible. Since the columns contain extra database specific length information for the column tables declared in the ABAP dictionary, containing long columns with the type LCHAR or LRAW should only be addressed using Open SQL. Native SQL may not produce the correct result, as it does not take this information into account. Native SQL does not support automatic client handling. Instead, you must treat a client field like any other field
    Native SQL and Transactions
    One should not use any transaction control statement such as COMMIT, ROLLBACK WORK, or any statements that set transaction parameters using Native SQL to ensure that transaction in the R/3 System are consistent.
    ABAP Dictionary
    The ABAP Dictionary is nothing but a part of the ABAP Workbench. It allows you to create and administer database tables. There are no statements from the DDL part of Standard SQL in Open SQL. It should be noted that normal application programs should not create or change their own database tables.
    To create and change database tables, the ABAP Dictionary has to use the DDL part of Open SQL. Besides this, it also administers the ABAP Dictionary in the database. In addition, the ABAP Dictionary contains meta-descriptions of all database tables in the R/3 system. Here, only database tables appears in the Dictionary, which you have created using the ABAP Dictionary. Open SQL statements can only access tables, which exists in the ABAP Dictionary.
    Authorization and Consistency Checks
    With regard to authorization and consistency checks, the DCL part of Standard SQL is not used in R/3 programs. Whereas, the work processes which are within the R/3 system are logged into the database system as users with full rights. By using the R/3 authorization concept, the authorizations of programs or users to read or change database tables is administered within the R/3 system. In addition, transactions must equally ensure their own data consistency using the R/3 locking concept.
    The R/3 lock concept allows you to monitor your system with regards to lock logics. The R/3 lock concept works closely together with the R/3 updates.
    As an example, say that a travel agent wants to book a flight for a customer who wants to fly to a particular city with a certain airline on a certain day. If there are still available seats on the flight, then the booking will be possible, otherwise it will lead to overbooking. Hence, the database entry corresponding to the flight must be locked against access from other transactions to avoid the possibility of overbooking. This is because two agents might both be doing this same thing at the same time, and we need to make sure that we don't overbook.
    Lock Mechanisms 
    When the database system receives change statements (INSERT, UPDATE, MODIFY, DELETE) from a program, it automatically sets database locks. Database locks are locks on the database entries affected by statements to prevent problems. Since the lock mechanism uses a, lock flag in the entry, you can only set a lock for an existing database entry. After each database commit, these flags are automatically deleted. This means that database locks can never be set for longer than a single database LUW, a single dialog step in an R/3 application program.
    Therefore, physical locks in the database system are insufficient for the requirements of an R/3 transaction. Locks in the R/3 system must remain set for the duration of a whole SAP LUW, that is, over several dialog steps. They must also be capable of being handled by different work processes and application servers. As a result, each lock must apply on all servers in that R/3 system.
    Database Accesses of the NetWeaver AS ABAP
    The NetWeaver AS ABAP stores long-term data in a central relational database table. In a relational database model, the real world is represented by tables. A table is a two-dimensional matrix, consisting of lines and columns (fields). The smallest possible combination of fields that can uniquely identify each line of the table is called the key. Each table must have at least one key, and each table has one key that is defined as its primary key. Relationships between tables are represented by foreign keys.
    Standard SQL
    SQL (Structured Query Language) is a largely standardized language for accessing relational databases. It can be divided into three areas:
    ·        Data Manipulation Language (DML)
    Statements for reading and changing data in database tables.
    ·        Data Definition Language (DDL)
    Statements for creating and administering database tables.
    ·        Data Control Language (DCL)
    Statements for authorization and consistency checks.
    Each database has a programming interface that allows you to access the database tables using SQL statements. The SQL statements in these programming interfaces are not fully standardized. To access a specific database system, you must refer to the documentation of that system for a list of the SQL statements available and their correct syntax.
    The Database Interface
    To avoid incompatible situations between different database tables and to make the NetWeaver AS ABAP system independent of the database system in use, each work process on an ABAP application server contains a database interface. The NW AS communicates with the database solely through the database interface. The database interface converts all of the database requests from the NW AS into the correct Standard SQL statements for the database system in use. To do this, it uses a database-specific component that shields the differences between database systems from the rest of the database interface. You choose the this component when you install NetWeaver AS ABAP in accordance with the database in use.
    ABAP programs have two options for accessing the database interface: Open SQL and Native SQL.
    Open SQL
    Open SQL statements are a fully integrated subset of Standard SQL within ABAP. They enable the ABAP programs to access data irrespective of the database system installed. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data.
    Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. In SAP systems that are distributed across more than one application server, the data in the various buffers is synchronized at set intervals by buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change. You specify whether a table can be buffered in its definition in the ABAP Dictionary.
    Native SQL
    Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. When you use Native SQL, the function of the database-dependent layer is minimal. Programs that use Native SQL are specific to the database system for which they were written. When developing generally valid ABAP applications, you should – as far as possible – avoid using Native SQL. In some components of the SAP System, Native SQL is used – for example, in the ABAP Dictionary for creating or changing tables.
    The ABAP Dictionary
    The ABAP Dictionary, part of the ABAP Workbench, allows you to create and administer database tables. Open SQL contains no statements from the DDL part of Standard SQL. Normal application programs should not create or change their own database tables.
    The ABAP Dictionary uses the DDL part of Open SQL to create and change database tables. It also administers the ABAP Dictionary in the database. The ABAP Dictionary contains meta descriptions of all database tables in the NetWeaver AS ABAP system. Only database tables that you create using the ABAP Dictionary appear in the Dictionary. Open SQL statements can only access tables that exist in the ABAP Dictionary.
    Authorization and Consistency Checks
    The DCL part of Standard SQL is not important in ABAP programs. The work processes within the ABAP application server are logged on to the database system as users with full authorization. The authorizations of programs or program users to read or change database tables is managed by the authorization concept. Equally, transactions must ensure their own data consistency in the database using the SAP locking concept. For more information, refer to the chapter Data Consistency.
    Work Processes
    Work processes execute the individual dialog steps of ABAP application programs. They are components of ABAP application servers. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in NetWeaver AS ABAP.
    Structure of a Work Process
    The following diagram shows the components of a work process:
    Screen Processor
    In ABAP application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic, which controls a large part of the user interaction. NetWeaver AS ABAP contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
    ABAP Processor
    The actual processing logic of an application program is written in ABAP - SAP’s own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
    Database Interface
    The database interface provides the following services:
    ·        Establishing and terminating connections between the work process and the database.
    ·        Access to database tables
    ·        Access to Repository objects (ABAP programs, screens and so on)
    ·        Access to catalog information (ABAP Dictionary)
    ·        Controlling transactions (commit and rollback handling)
    ·        Table buffer administration on the ABAP application server.
    The following diagram shows the individual components of the database interface:
    The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
    Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that your installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in NetWeaver AS ABAP by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
    Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the ABAP application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an ABAP application server. Where NetWeaver AS ABAP is distributed across more than one ABAP application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
    Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. In Native SQL, you can primarily use database-specific SQL statements. The Native SQL interface sends them as is to the database system where they are executed. You can use the full SQL language scope of the respective database which makes all programs using Native SQL specific for the database system installed. In addition, there is a small set of SAP-specific Native SQL statements which are handled in a special way by the Native SQL interface. ABAP applications contain as little Native SQL as possible. In fact, it is only used in a few components (for example, to create or change table definitions in the ABAP Dictionary).
    The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install NetWeaver AS ABAP. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
    Types of Work Process
    Before you start NetWeaver AS ABAP, you determine how many work processes each ABAP application server will have, and what their types will be. Since all work processes have the same structure (see preceding section), the type of work process does not determine the technical attrributes of the ABAP application server but the type of tasks to be performed on it. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your ABAP application servers.
    The following diagram shows again the structure of an ABAP application server, but this time, includes the various possible work process types:
    Dialog Work Process
    Dialog work processes deal with requests from an active user to execute dialog steps (see also Dialog Programming).
    Update Work Process
    Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
    Background Work Process
    Background work processes process programs that can be executed without user interaction (background jobs).
    Enqueue Work Process
    The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for NetWeaver AS ABAP and is an important part of the SAP LUW concept. In NW AS, you may only have one lock table. You may therefore also only have one ABAP application server with enqueue work processes. Normally, a single enqueue work process is sufficient to perform the required tasks.
    Spool Work Process
    The spool work process passes sequential datasets to a printer or to optical archiving. Each ABAP application server may contain only one spool work process.
    Role of Work Processes
    The types of its work processes determine the services that an ABAP application server offers. The application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
    You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an SAP System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
    thanks
    karthik
    reward me points if usefull

  • Need to Perform Check again and again in Oracle Workflow

    Hi All,
    I have one requirement in Oracle Workflow where if there is any hold applied on any Invoice and if the hold is released then workflow should get cancel immediately.
    I have one workflow activity which can check the current status on workflow by querying AP_HOLDS_ALL table.
    How I can perform the same check again and again to check the current status so that I can immediately cancel the workflow?? Please suggest if anybody has any idea like do-while Loop etc to achieve the requirement.
    Thanks.
    Viswas

    WF Definition loops are expensive for the background process and take good amount of data in wf_item_activity_statuses and wf_item_activity_statuses_h. I would recommend defining a business event to be raised from the form/module where the base table is updated. Then you create a subscription to that event and the function associated to that subscription can abort the workflow process.
    So there would not be a need to constantly check for a condition.
    Regards,
    Alejandro

  • View past transation performance of ABAP and portal

    I would like to know where I can find past statistics on transaction performance for both an ABAP stack and a java like a portal system.
    I am familiar with NWA on java but I don't know where to find a performance period for inbound transaction and how many seconds it tooks to process.
    Also I would like to know the transaction where I can find how long it took for a transaction for a particular period or a particular user.
    I know under admin--> workload there is a large bunch of information but I need to find transaction performance and I can't seem to find it under this tcode.
    Thanks
    Weyland Y.

    Weyland,
    You need to enable Portal Activity Report for Enterprise Portal 7.0 and then you will be able to see it.
    Check this link and SAP Note 1084379
    [http://help.sap.com/saphelp_nw04/helpdata/en/48/6aa9429b930b31e10000000a1550b0/content.htm]
    Thanks,
    Digesh
    Edited by: digeshjoshi on Dec 15, 2009 4:32 PM

  • Print to Tape color bars and black order

    Hello. i'm about to print a videoclip for a tape. my question is the following, in the print to video setup theres is the option for color bars and black.. but the color bars come first and then the black. i would like to have the black first for 2 minutes and then color bars for 30 seconds..how can i do that?

    I want full control over how things happen. As an added benefit, by keeping everything in the sequence timeline, I have the ability to use a custom countdown clock.
    x

  • Color Bars play instead of Black Video

    I created black video from FILE>NEW>Black Video
    I placed it on the time line and when I play it I get color bars
    Any Ideas
    Thanks
    Dennis

    Dennis,
    The only thing even remotely like this is some problems that QT has with "synthetic" Video, like Black Video and Transparent Video, but nothing like what you are getting.
    So I imported some old black video that I had output before I had up graded to CS4 that was .avi video. I dropped it on the time line and I got Black Video.
    This was basically the solution to the QT issues - Export the "synthetic Video" as the proper format/CODEC for the Project and all was good - still, we're talking Rendering/Transcoding issues, and not Color Bars there. In those cases, it was the lack of synthetic Video, and was not version-specific. Once this material was Exported to Video, it worked fine. While this could get your Project finished, there has got to be some reason for what you're seeing. You should be able to Export from a Sequence, the Black Video to match your Project Presets and then Import that .AVI, etc., into the Project, to replace the synthetic Video. I do not think that you'll have any problem doing this from a Sequence in CS4, or you could use the old material.
    I'm thinking, but can't come up with any new tests to make you run. Thanks for trying the stuff I've thrown at you, and sorry that we're not any closer to the cause, than when you posted.
    Good luck,
    Hunt

  • Recently my iPhone 5 started rebooting to a messed up screen that would flash and show different bars and colors. I would either have to wait a bit to restart it and fix it. But now, it got to the point where I can't even get past the Apple splash screen

    My iphone 5 was working fine until it recently started to reboot to a messed up splash screen that would flash and have bars across it. When this happened, I couldn't do anything and had to restart it. I was able to start up the phone sometimes, until just recently. Everytime I started up the phone, it would load up the splash screen and then become distorted, flashy, and sometimes colorful and I could not use my phone. To try and fix this, I put it into recovery mode to do a factory restore, but iTunes can't even restore my phone. I even tried DFU mode.. Any help would be greatly appreciated!

    Check this support document for SIM issues http://support.apple.com/kb/TS4148. No one here is Apple, we are users like you. We can only recommend you try Apple again, unless you are close to an Apple store and can make an appointment to go in there.

  • Performance problems, do we need to upgrade. Server and Database level

    Problem:
    I'm a Java programmer and a Transact SQL DBA. So i have knowledge about databases. Nowwe have a database who performs very bad and got much deadlock problems and so on. It's an Oracle Database.
    We have Oracle version 9 and an application in Delphi. The bad performance is only since a while. We have cleaned the archive.
    My suggestion is why not migrate to a newer version of Oracle. Change some hardware specs get up to date.Then i think we will have less problems.
    But ofcourse this is more trail on error. That why i hope there is an Oracle specialist here who can help me with a few questions.
    Users and Specs
    I got 150 till 180 users
    i got a server with 1 processor XEON 233 GHZ
    4 gig memory, constant use 1,5 gig
    Questions
    1. Is it a good idea to upgrade? Maybe not to solve al the problems, but version 9 is old, there is version 10 or 11.
    2. Which version we should use 10 or 11? 11 is in use for a while so this sounds like a good idea.
    3. Are the specs OK or must i do something about the server to?
    Maybe dual core, or Enterprise (64 bit). Memory upgrade?
    4. Maybe for 64 bit i need Oracle version 11 to have good support on it?
    I hope somebody can help me a bit.
    Thanks,
    Kind regards,
    André

    Hi Andre,
    . Is it a good idea to upgrade? Maybe not to solve al the problems, but version 9 is old, there is version 10 or 11.
    2. Which version we should use 10 or 11? 11 is in use for a while so this sounds like a good idea.I suggest you to upgrade to latest available 11.2.0.2.
    But do complete testing your upgraded database before you move to PRODUCTION.
    . Are the specs OK or must i do something about the server to?It all depends on the usage and concurrent users :)
    4. Maybe for 64 bit i need Oracle version 11 to have good support on it?Regardless of bit version all Oracle Versions has good support.
    Refer MOS tech notes:
    *How to Perform a Full Database Export Import during Upgrade, Migrate, Copy, or Move of a Database [ID 286775.1]*
    *Minimizing Downtime During Production Upgrade [ID 478308.1]*
    *Different Upgrade Methods For Upgrading Your Database [ID  419550.1]*
    thanks,
    X A H E E R

  • Can I get my Macbook Pro just checked out and tuned up at the genius bar?

    I'm having a hard time getting my questions answered. Basically I've had my Macbook Pro for four and a half years, but it's still doing mostly fine. It's just showing it's age slightly I think, with more spinning wheels than usual and odd things like the date is usually set to 1999 when I turn the computer on, but it rights itself in a few minutes. Also most the time when I plug it in it says it's not charging and I have to try multiple times. None of this is a huge deal, it's just that I really need the computer to last me preferably at least another year, so I worry about it a bit. I do take good care of it though. I'm about to move out of the country for a year, so I'd like to get it just checked out and perhaps tuned up a bit so that any problems are taken care of and it's in the best shape before I move away. I'd like to make a genius bar appointment, but the closest Apple store is a two hour drive from my home, so I don't want to go into it not having any idea how much it will cost or if they'll even be able to do what I'm hoping in the span of a single workday. I really don't want to have to drive back later to pick it up or have it sent off somewhere to be repaired, although if it does have serious problems I'd be willing to do that. I'd just like to know going in to it what the price range is likely to be like. I don't want to make the drive to the Apple store and have them tell me it's going to be a few hundred dollars just to have my computer looked over. And I don't even know if they offer that service, let alone if they can do it in a single afternoon. I've tried calling the store and conversations with the automated person really are not helpful. He just tells me to go online and make a reservation, and I can't figure out how to get my questions about cost and service answered.
    Also, am I being foolish hoping my four and a half year old Macbook will last at least another year or two? I have no idea what the "life expectancy" is for these things. I know nothing really about computers at all, so forgive my ignorance.
    Any help and insight is very much appreciated.

    The genius bar technicians can check your MBP for possible hardware problems and specific software issues that you may have.  The diagnosis will be free.  Any extensive repairs will not be free.
    If you have minor software problems, you essentially will have to deal with them yourself.  Examine these two comprehensive documents for possible problem definition and solutions.  If you encounter problems that you are unable to cope with, start a new discussion and there will be persons willing to assist you in solving them.
    https://discussions.apple.com/docs/DOC-3521
    https://discussions.apple.com/docs/DOC-3353
    Ciao.

  • I synced my iTunes with my iPhone 5. Some of the titles don't match the songs. When I checked the iTunes database, yes it is the latest version, the titles and songs matched correctly. so how do I fix this on my phone?

    I synced my iTunes with my iPhone 5. some of the titles on't match the songs. I checked my iTunes database, it is the latest version, and the titles and songs all match. So how do I fix this on my iPhone?

    Sounds like you may need to re-download the entire albums from iTunes. See this KB article for how to download past purchases: http://support.apple.com/kb/HT2519.
    I'd suggest doing it one album at a time. Delete one, download it from your purchase histor, then the next, etc.

  • Color Bars and tone in FCP X?

    Just downloaded FC"P" X and having a look around I cant find Color Bars or Tone anywhere...?
    Did a quick search on the help... but couldn't find anything.
    Surely I must be missing something here - they must be available right!!?
    I know I could output some from my deck or earlier version of FCP but thats not the point really is it. What possible reason on God's green earth could there be for omitting something so simple. Sorry but most del specs (even for digital tapeless) require bars and tone.
    Can someone point me in the right direction - they must be in here somewhere.
    Thanks in advance
    J

    If I were to use FC X for a delivery then that would be the way to go I suppose.
    Or generate b+t on the deck and ingest to the computer and then import to fcp.
    Dont think I'll be using FC X for anything in the short term though. Just playing around. See where it goes.
    So many odd decisions - why get rid of a perfectly good, simple feature like "make freeze frame" - I know you can do it using the retime tool now but its a round about way of doing things.
    Sorry if sounded rude - there are so many crazy Apple fan boys willing to jump on people here at the slightest hint of criticism :-)
    Thanks
    J

  • Performing check and potential update for status control table

    Cheers Experts,
    I searched in the forum, but I didn't find an answer.
    I'm working on a 3.0B BW system.
    After updating from PSA to an ODS, in the log I see the following line:
    "Performing check and potential update for status control table" and double clicking on it, it says:
    If data is loaded into an InfoCube, or existing data is edited (aggregated/compressed/deleted/got from a DataMart), then there is a change in  the potential reportability of the data , or the possibility of deleting data by request, or of aggregating or compressing.
    This status of each one of these Cubes is stored in a status table, that is updated when there is any change to the status of a request in the Cube.
    The system now analyzes the requests in the Cube and compares the calculated status with the status table.
    If deviations from the status table arise then you are given the option of adjusting the status table.                                         
    I have 2 questions:
    1) What is BW doing, mainly because I'm working on an ODS and not an Infocube?
    2) What can I do to reduce its execution time, since it lasts several minutes?
    Thanks and greetings.
    Roberto

    Roberto, did you ever find an answer to your question?  We also are experiencing long runtimes during this particular process running 3.x deltas from ODS to ODS and cubes.

Maybe you are looking for