Performance optimization during upgrade

Please help to understand the use of the below max processes parameters during upgrade and the value should be based on what ?
1) CRR
2) Batch --> based on SM50 background processes ? , if yes do we need to have that many processes available in shadow or main instance ?
3) SQL
4) R3Load
5) Parallel

Hi,
Please read the below note and i think that your douts would be clear.
1616401 - Understanding parallelism during the Upgrades, EhPs and Support Packages implementations
Thanks
Rishi Abrol

Similar Messages

Performance optimization during database selection.

hi gurus,
pls any explain about this...
Strong knowledge of performance optimization during database selection.
regards,
praveen

Hi Praveen,
Performance Notes
1.Keep the Result Set Small
You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
Using the WHERE Clause
Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
Using the HAVING Clause
After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
Effect
If you use the WHERE and HAVING clauses correctly:
     There are no more physical I/Os in the database than necessary
     No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
     The CPU usage of the database host is minimize
     The network load is reduced, since only the data that is required by the application is transferred to the application server.
Minimize the Amount of Data Transferred
Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
Restrict the Number of Lines
If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
Restrict the Number of Columns
You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
Use Aggregate Functions
If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
Following an aggregate expression, only its result is transferred from the database.
Data Transfer when Changing Table Lines
When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers
In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
Multiple Operations Instead of Single Operations
When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
Avoid Repeated Access
As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
Avoid Nested SELECT Loops
A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
ABAP Dictionary Views
You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
Joins in the FROM Clause
You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
Subqueries in the WHERE and HAVING Clauses
Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
Using Internal Tables
It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
Using a Cursor to Read Data
A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead
You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
Database Indexes
Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
Formulating Conditions for Indexes
You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
Check for Equality and Link Using AND
The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
Use Positive Conditions
The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
Using OR
The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
Using Part of the Index
If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
Checking for Null Values
The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
Avoid Complex Conditions
Avoid complex conditions, since the statements have to be broken down into their individual components by the database system.
Reduce the Database Load
Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
Buffer Tables on the Application Server
You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
     Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
     Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
     Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
When you read from buffered tables, the following happens:
1.     An ABAP program requests data from a buffered table.
2.     The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
3.     If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
4.     The database server passes the data to the application server, which places it in the table buffer.
5.     The data is passed to the program.
When you change a buffered table, the following happens:
1.     The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
2.     All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
3.     Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
You should buffer the following types of tables:
     Tables that are read very frequently
     Tables that are changed very infrequently
     Relatively small tables (few lines, few columns, or short columns)
     Tables where delayed update is acceptable.
Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
The SELECT statement bypasses the buffer when you use any of the following:
     The BYPASSING BUFFER addition in the FROM clause
     The DISTINCT addition in the SELECT clause
     Aggregate expressions in the SELECT clause
     Joins in the FROM clause
     The IS NULL condition in the WHERE clause
     Subqueries in the WHERE clause
     The ORDER BY clause
     The GROUP BY clause
     The FOR UPDATE addition
Furthermore, all Native SQL statements bypass the buffer.
Avoid Reading Data Repeatedly
If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
Sort Data in Your ABAP Programs
The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
Use Logical Databases
SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
Work Processes
Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
Structure of a Work Process
Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
Each work process contains two software processors and a database interface.
Screen Processor
In R/3 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. The screen flow logic controls a large part of the user interaction. The R/3 Basis system 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 - SAPs 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 R/3 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 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 the R/3 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 the R/3 System 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 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. Where an R/3 System is distributed across more than one 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. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis 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 the Basis system. 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
Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. 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 application servers.
The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
Dialog Work Process
Dialog work processes deal with requests from an active user to execute dialog steps.
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 the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
Spool Work Process
The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
The services offered by an application server are determined by the types of its work processes. One 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 R/3 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.
ABAP Application Server
R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
Structure of an ABAP Application Server
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
The following diagram shows the structure of an application server:
The individual components are:
Work Processes
An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
Dispatcher
Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
Gateway
Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
Shared Memory
All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running. A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
Database Connection
When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
Dispatching Dialog Steps
The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
The following diagram is an example of how this might happen:
       1.      The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
       2.      The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
       3.      While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
       4.      After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
       5.      While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
From this example, we can see that:
        A dialog step from a program is assigned to a single work process for execution.
        The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
        A work process can execute dialog steps of different programs from different users.
The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
Dispatching and the Programming Model
The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
Happy Reading...
shibu

Performance Issues during Upgrade of EBS from 11.5.10.2 to 12.1.1

Hi,
We're upgrading our EBS , from Rel 11.5.10.2 to 12.1.1.
We're stuck , while running script ar120bnk.sql (ran more than 20 Hours) :
Regarding the tables involved in this Process :
select owner , table_name,num_rows,last_analyzed,sample_size
from dba_tables
where table_name in
'RA_CUSTOMER_TRX_ALL',
'RA_CUST_TRX_LINE_GL_DIST_ALL',
'XLA_UPGRADE_DATES',
'AR_SYSTEM_PARAMETERS_ALL',
'RA_CUST_TRX_TYPES_ALL',
'RA_CUST_TRX_LINE_GL_DIST_ALL',
'XLA_TRANSACTION_ENTITIES_UPG')
AR RA_CUSTOMER_TRX_ALL 55,540,740 04/02/2012 12:41:56 5554074
AR RA_CUST_TRX_LINE_GL_DIST_ALL 380,513,830 04/02/2012 13:54:12 38051383
AR RA_CUST_TRX_TYPES_ALL 90 04/02/2012 14:04:54 90
AR AR_SYSTEM_PARAMETERS_ALL 6 04/02/2012 12:19:49 6
XLA XLA_UPGRADE_DATES 4 05/02/2012 17:12:57 4
As you can see: RA_CUST_TRX_LINE_GL_DIST_ALL is more tan 380 million rows !
and RA_CUSTOMER_TRX_ALL is more than 55 million rows.
We have more huge tables in the AR schema , and we would like to know if we are unique customer
with huge AR schema objects , and if NOT how come that we are getting stuck on threed statment in
AR schema.
Bellow an output of all the objects that have more than 10 million rows in AR schema :
select owner , table_name,to_char(num_rows,'999,999,999') ,last_analyzed
from dba_tables
where owner = 'AR'
and num_rows > 10000000
order by num_rows desc nulls last
AR AR_DISTRIBUTIONS_ALL 408,567,520 04/02/2012 11:49:57
AR RA_CUST_TRX_LINE_GL_DIST_ALL 380,513,830 04/02/2012 13:54:12
AR MLOG$_AR_CASH_RECEIPTS_ALL 310,777,690 04/02/2012 12:30:33
AR RA_CUSTOMER_TRX_LINES_ALL 260,211,090 04/02/2012 13:30:26
AR AR_RECEIVABLE_APPLICATIONS_ALL 166,834,930 04/02/2012 12:16:54
AR MLOG$_RA_CUSTOMER_TRX_ALL 150,962,980 04/02/2012 12:33:23
AR AR_CASH_RECEIPT_HISTORY_ALL 145,737,410 04/02/2012 11:40:31
AR RA_CUST_TRX_LINE_SALESREPS_ALL 130,287,580 04/02/2012 14:03:54
AR AR_PAYMENT_SCHEDULES_ALL 108,652,480 04/02/2012 12:05:32
AR RA_CUSTOMER_TRX_ALL 55,540,740 04/02/2012 12:41:56
AR AR_CASH_RECEIPTS_ALL 53,182,340 04/02/2012 11:29:53
AR AR_DOC_SEQUENCE_AUDIT 52,865,150 04/02/2012 11:52:46
AR RA_MC_TRX_LINE_GL_DIST 17,317,730 04/02/2012 14:05:18
AR AR_MC_DISTRIBUTIONS_ALL 13,037,030 04/02/2012 11:53:35
AR AR_MC_RECEIVABLE_APPS 12,672,050 04/02/2012 11:53:57
AR AR_TRX_SUMMARY 12,457,560 04/02/2012 12:20:16
AR RA_CUST_RECEIPT_METHODS 11,105,750 04/02/2012 13:35:38
AR HZ_ORGANIZATION_PROFILES 10,271,640 04/02/2012 12:24:44
How to Upgrade AR tables whith Huge amount of Datas ( > 50 Millions Rows ) ?

Hi,
Dont worry, you are not the only one even we have one customer whose AR_DISTRIBUTIONS_ALL table is 80 GB now and i can even do select count(*) for this table.
We had to keep this much data for business requirements, but i wonder if this is a bug or users mistake.
Due to this we are facing seruios performance issues for AR reports and raised SRs but no resolution yet. And this guy who is assigned to us is reall ynot been helpful to fix the issue.
Although we did not upgrade for this customer, but we migrated from 11.5.9 to R12.1.1 by re-implementation. But all these increasing size of these tables happened after migration.
And i believe most of the time in your upgrade is going to building the indexes. You can ask Oracle if they can edit the driver file to skip building the indxes and rebuild them after upgrade. But again it will also take time.
Another option for you is to "Archive and Purge the data" as per chapter 10 of
11i Receivables user guide.
http://docs.oracle.com/cd/B25284_01/current/acrobat/115arug.zip
Thanks
Edited by: EBSDBA on Feb 8, 2012 10:04 PM

Performance Optimization during the Data Archiving Initial runs

Dear Experts,
We are running archiving jobs (Write Job & Preprocessing Jobs) which are running for nearly 56hrs. It is writting and analyzing nearly 4 million records.
Any suggestions to improve the performance for running these jobs to complete in less time. Its ISU Archiving.
I have gone through Many SAP Notes, but i'm unable to find related to improving performance during the archival runs. These are initial runs.
Thank You,
Mahesh C

You should check the sql statements that are being executed by these runs.. Possibly by adding additional indexes you can speedup the process.
Kind regards,
Mark

Disck Space not enough during upgrade CUCM 9.1(2)SU1 to 9.1(2)SU2a

Hi,
I face an issues during upgrade my current CUCM 9.1(2)SU1 to 9.1(2)SU2a, it show with this error message "There is not enough disk space in the common partition to perform the upgrade, for steps to resolve this condition please refer to CUCM 9.1(1) release notes or view defect CSCuc63312 in bug toolkit on Cisco.com". I had check the bug id and got 2 way to do it:-
1. reduce the amount of traces on the system, but I not ready want to do this
2. install a COP file name: ciscocm.free_common_space_v1.0.cop.sgn
If I select option 2, will it have any risk? Is it mean 9.1(2) - inactive version will be clear out from disk space or it will clear out 2 version - active and inactive version from disk space?
I need have some advice on this before I perform.
Thanks.

Hi,
As per the following link
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_011.html
You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version."
Additionally, regarding the first option, if you do not want to reduce the tracing levels you can still delete some old traces using RTMT which gives you an option of deleting the traces from the server as well as transferring / downloading them to your pc simultaneously by checking the 'delete from server' option on last page of log file collection option.
HTH
Manish

Errors in DDIC Activation phase during upgrade.

Hi,
Title: Errors in DDIC Activation phase during upgrade.
During preprocessing phase (phase ACT_UPG) we got many DDIC activation errors such as:
SAPup broke during phase ACT_UPG in module MAIN_SHDRUN / Shadow System Operations: SPDD and Activation.
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCI702.CPE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EEDO519 "Data Element" "/BI0/OICH_AT" could not be activated
1EEDO519 "Data Element" "/BI0/OICREA_TIME" could not be activated
1 ETP111 exit code           : "8"
We have searched the SDN, many posts say that we have to just activate them. But my question is where - in source system OR in Shadow system?
We assumed it is Source system (please correct if it is wrong), unlocked the system and logged in as normal user and tried to activate the Data Element. Now, it says "Search Help /BI0/OICH_AT is not active or contains no parameter".   How to go about it?
If it is Shadow System, how can i unlock the system?
Many thanks,
Mohan.

Dear Mohan,
There are search helps configured for the dataelements in ACTUPG.ELG. These search helps were created by mistake by the system.
The search helps can be deleted manually in the shadow instance.
In this case you should remove these fields in se11 (in your shadow instance) as the Search help shouldn't exist.
You should do this step for all data elements shown in the log ACTUPG.ELG:
For example: SE11 -> /BI0/OICH_AT -> Change -> Tab "Further characteristics"
1. Goto SE11:
2. Select Data type and fill "/BI0/OICH_AT" and display
3. Select the tab "Further Characteristics" and
4. Remove the values for fields "Name" and "Parameters"
   then click on icon "Activate"
Please do the same for the other object.
But before performing above steps you need to unlock the shadow instance by the following command:
SAPup unlockshd <SID>
(if using SAPup)
SAPehpi unlockshd <SID>
(if using SAPehpi)
Also do not forget to lock the shadow system again after performing the steps and continuing the upgrade by the following command:
SAPup lockshd <SID>
(if using SAPup)
SAPehpi lockshd <SID>
(if using SAPehpi)
You can logon to your shadow system with any different user than DDIC.
Best Regards,
Abhishek
Edited by: Abhishek Srivastava on Oct 17, 2011 6:26 PM

Archivelog mode during upgrade

HI All,
During upgrading the database from 10g to 11g... I will put my database from noarchivelog mode to archivelog mode to save the disk space.
Does this task improves or speedsup the process of upgradation or any impact.
Suggestions please.
regards,
TEJAS

when DB is archivelog mode and you put DB in startup upgrade mode.. and execute catupgrd.sql script it starts updating dictionary objects and generates archivelogs ..
Hence i put the DB in noarchive log mode..
Any performance impact by putting the upgrade process in noarchivelog mode in terms of time duration the backup is performed.No performance impact, But recommended to put in Archivelog mode, even though if you have good backup.
Also apart from this thread, have a question, The catupgrd.sql script execution duration depends upon the data disctionary contents right not on the DB size ? i am having this question. plz answer.The upgrade script creates and alters certain data dictionary tables. It also upgrades or installs the following database components in the new Oracle Database 11g Release 2 (11.2) database:
Source:-
Answer is here in detail.. http://docs.oracle.com/cd/E11882_01/server.112/e10819/upgrade.htm#sthref184

Restoring variants during upgrade

Hi All,
We are in process of upgrade from 4.6c to ECC 6.0.
I would like to know the tools used to handle variants issues while upgrading to ECC.
It would be of great help if you can tell the different activities to be carried out for restoring variants (Display variants and Variants for Background jobs)
Before upgrade
During Upgrade
After upgrade.
We are looking for specific technical learnings and observations, like performance issue and other issues observed while upgrading.
Please mail me, if anyone as such specific learnings or observations while doing upgrade project
Thanks in advance

See if standard SAP program RSVARDOC_610 (or something like it) exists in your system.
Rob

Replacing development system with copy of production system during upgrade

Hello Guru,
We are planning to replace our development ECC 5.0 system with a copy of production system, and to perform upgrade to ECC 6.0.
SAP upgrade guide stating that:
"If you have modified SAP objects, make sure that you keep your development sysetem. Do not copy your production system to your development system for test purpose."
If we are planning to "Reset to original" for majority of SAP's objects during SPAU, are there other reasons we need to consider the impact of replacing development system with a copy of production system?
Thanks in advance!

Thanks for your response.
When we first implemented SAP system 3 and half years ago, the consultants and the developers were using the development system like a sandbox system, they tried out features or developed programs for learning purpose.
Hence, the development system and production system are very different.
There are many repair transport requests that will never transport into production.
Also, we developed client strategy (different client numbers for each system u2013 Dev, QA, Prod) during the initial implementation.
We were told by the upgrade consultant, it is standard that the development system replaced by a copy of production system during upgrade. The client number in development system will be the same as the production system after upgrade. If I want to avoid confusion for the developer & testing users, I would have to create a new client using the previous development client number, and then perform client copy.
As I review the SAP upgrade guide, I saw the statement about not to replace development system with production system, I would like to know the reasons behind SAP's statement.
By the way, we will replace our QA system with a copy of production system during the upgrade.

Performance issues since upgrade

I am on a late 2011 MacBook Pro and am having severs performance issues since upgrading to Mavericks. I fear my issues may be related to company installed anti-virus (which I cannot remove), but I was hoping someone could look over my EtreCheck for other potential solutions.
One really odd issue I am having, which I cannot seem to find good information for on Google, is at least 4-5 times a day my Mac just stops. No beach ball, no anything, for about 1-5 minutes. Then it's fine. Maybe just me grasping at straws, but it seems related to a when webpage loads a bunch of images? I always use Safari btw, but testing other browsers, like Chrome & Firefox, it happens as well.
I have also removed TotalFinder and have noticed no improvement and still have the above issue.
Thanks in advance!
Here is my EtreCheck:
Problem description:
slow performance on Mavericks
EtreCheck version: 2.0.11 (98)
Report generated November 11, 2014 at 8:51:26 AM EST
Hardware Information: ℹ️
MacBook Pro (17-inch, Late 2011) (Verified)
MacBook Pro - model: MacBookPro8,3
1 2.5 GHz Intel Core i7 CPU: 4-core
8 GB RAM Upgradeable
BANK 0/DIMM0
4 GB DDR3 1333 MHz ok
BANK 1/DIMM0
4 GB DDR3 1333 MHz ok
Bluetooth: Old - Handoff/Airdrop2 not supported
Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
Intel HD Graphics 3000 - VRAM: 512 MB
AMD Radeon HD 6770M - VRAM: 1024 MB
Color LCD 1920 x 1200
LED Cinema Display 1920 x 1200
System Software: ℹ️
OS X 10.9.5 (13F34) - Uptime: 0:46:22
Disk Information: ℹ️
APPLE HDD HTS727575A9E362 disk0 : (750.16 GB)
S.M.A.R.T. Status: Verified
EFI (disk0s1) <not mounted> : 210 MB
Macintosh HD (disk0s2) / [Startup]: 749.30 GB (256.69 GB free)
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
MATSHITADVD-R   UJ-8A8
USB Information: ℹ️
Apple Inc. FaceTime HD Camera (Built-in)
Fitbit Inc. Fitbit Base Station
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad
Apple, Inc. Keyboard Hub
Apple, Inc Apple Keyboard
Tablet PTZ-630
Logitech Logitech USB Headset
Apple Inc. Display iSight
Apple Inc. Apple LED Cinema Display
Apple Inc. Display Audio
Apple Computer, Inc. IR Receiver
Firewire Information: ℹ️
Iomega HDD unknown_device 800mbit - 800mbit max
S.M.A.R.T. Status: Verified
disk1s1 (disk1s1) <not mounted> : 32 KB
Iomega HDD (disk1s3) /Volumes/Iomega HDD : 500.04 GB (22.88 GB free)
Files (disk1s5) /Volumes/Files : 499.90 GB (416.87 GB free)
Thunderbolt Information: ℹ️
Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
Anywhere
Kernel Extensions: ℹ️
/Library/Application Support/Symantec/Protector
[not loaded] com.symantec.kext.protector.panther (1.0f5) Support
[not loaded] com.symantec.kext.protector.tigerplus (1.0f5) Support
/Library/StartupItems/SymAutoProtect
[loaded] com.Symantec.kext.SAVAPComm (11.0.6) Support
/System/Library/Extensions
[loaded] com.Cycling74.driver.Soundflower (1.5.1) Support
[loaded] com.InnovationTechnology.driver.ComputerAudio (1.01 - SDK 10.7) Support
[not loaded] com.cisco.nke.ipsec (2.0.1) Support
[not loaded] com.wacom.kext.wacomtablet (6.3.7 - SDK 10.8) Support
Startup Items: ℹ️
CiscoVPN: Path: /System/Library/StartupItems/CiscoVPN
NortonMissedTasks: Path: /Library/StartupItems/NortonMissedTasks
SMC: Path: /Library/StartupItems/SMC
SymAutoProtect: Path: /Library/StartupItems/SymAutoProtect
SymProtector: Path: /Library/StartupItems/SymProtector
Startup items are obsolete and will not work in future versions of OS X
Launch Agents: ℹ️
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[loaded] com.adobe.CS5ServiceManager.plist Support
[loaded] com.google.keystone.agent.plist Support
[running] com.jamfsoftware.jamf.agent.plist Support
[loaded] com.oracle.java.Java-Updater.plist Support
[running] com.symantec.quickmenu.application.plist Support
[running] com.wacom.wacomtablet.plist Support
[running] net.juniper.pulsetray.plist Support
Launch Daemons: ℹ️
[loaded] com.adobe.fpsaud.plist Support
[running] com.fitbit.fitbitd.plist Support
[running] com.fitbit.galileod.plist Support
[loaded] com.google.keystone.daemon.plist Support
[running] com.jamfsoftware.jamf.daemon.plist Support
[not loaded] com.jamfsoftware.startupItem.plist Support
[loaded] com.jamfsoftware.task.1.plist Support
[loaded] com.microsoft.office.licensing.helper.plist Support
[loaded] com.oracle.java.Helper-Tool.plist Support
[loaded] com.oracle.java.JavaUpdateHelper.plist Support
[loaded] com.rogueamoeba.instanton-agent.plist Support
[running] net.juniper.AccessService.plist Support
[loaded] net.juniper.UninstallPulse.plist Support
User Launch Agents: ℹ️
[loaded] com.valvesoftware.steamclean.plist Support
[running] ws.agile.1PasswordAgent.plist Support
User Login Items: ℹ️
gfxCardStatus Application (/Users/[redacted]/Downloads/gfxCardStatus.app)
Dropbox Application (/Applications/Dropbox.app)
Microsoft Database Daemon Application (/Applications/Microsoft Office 2011/Office/Microsoft Database Daemon.app)
cdn Volume (/Volumes/cdn)
TotalFinder Application (/Applications/TotalFinder.app)
SAVDiskMountNotify Application (/Library/Application Support/Symantec/AntiVirus/SAVDiskMountNotify.app)
ScanNotification Application (/Library/Application Support/Symantec/AntiVirus/ScanNotification.app)
SymSecondaryLaunch Application (/Library/Application Support/Norton Solutions Support/Scheduler/SymSecondaryLaunch.app)
Internet Plug-ins: ℹ️
OfficeLiveBrowserPlugin: Version: 12.3.6 Support
Flash Player: Version: 15.0.0.189 - SDK 10.6 Mismatch! Adobe recommends 15.0.0.223
AdobePDFViewer: Version: 10.0.2 Support
Unity Web Player: Version: UnityPlayer version 4.5.4f1 - SDK 10.6 Support
googletalkbrowserplugin: Version: 5.38.6.0 - SDK 10.8 Support
AdobeExManDetect: Version: AdobeExManDetect 1.1.0.0 - SDK 10.7 Support
iPhotoPhotocast: Version: 7.0
DirectorShockwave: Version: 11.5.9r620 Support
QuickTime Plugin: Version: 7.7.3
FlashPlayer-10.6: Version: 15.0.0.189 - SDK 10.6 Support
Silverlight: Version: 4.0.60310.0 Support
MeetingJoinPlugin: Version: (null) - SDK 10.6 Support
net.juniper.DSSafariExtensions: Version: (null) Support
Default Browser: Version: 537 - SDK 10.9
Flip4Mac WMV Plugin: Version: 2.3.1.2 Support
o1dbrowserplugin: Version: 5.38.6.0 - SDK 10.8 Support
WacomTabletPlugin: Version: WacomTabletPlugin 2.1.0.2 Support
SharePointBrowserPlugin: Version: 14.4.5 - SDK 10.6 Support
JavaAppletPlugin: Version: Java 7 Update 71 Check version
WacomNetscape: Version: 2.1.0-1 - SDK 10.8 Support
User Internet Plug-ins: ℹ️
SOEWebInstaller: Version: 1.0 - SDK 10.5 Support
Aspera Web 3.1.2.72265: Version: (null) - SDK 10.6 Support
Safari Extensions: ℹ️
1Password
Adblock Plus
Reddit Enhancement Suite
3rd Party Preference Panes: ℹ️
Flash Player Support
Flip4Mac WMV Support
Java Support
MacFUSE Support
SymAutoProtect
Symantec\nQuickMenu Support
WacomTablet Support
Time Machine: ℹ️
Skip System Files: NO
Mobile backups: ON
Auto backup: YES
Destinations:
Iomega HDD [Local]
Total size: 500.04 GB
Total number of backups: 37
Oldest backup: 2014-10-14 14:11:11 +0000
Last backup: 2014-11-11 13:27:48 +0000
Size of backup disk: Excellent
Backup size 500.04 GB > (Disk size 0 B X 3)
Top Processes by CPU: ℹ️
      36% com.apple.WebKit.Plugin.64
      34% SymAutoProtect
      13% WindowServer
      9% Unity
      4% Activity Monitor
Top Processes by Memory: ℹ️
455 MB Safari
361 MB com.apple.WebKit.Plugin.64
292 MB Unity
77 MB com.apple.WebKit.Networking
77 MB com.apple.WebKit.WebContent
Virtual Memory Information: ℹ️
2.08 GB Free RAM
2.39 GB Active RAM
1.34 GB Inactive RAM
1.40 GB Wired RAM
1.11 GB Page-ins
5.54 GB Page-outs

Activity Monitor - Mavericks also Yosemite
Activity Monitor in Mavericks has significant changes
Performance Guide
Why is my computer slow
Why your Mac runs slower than it should
Slow Mac After Mavericks
Things you can do to resolve slowdowns see post by Kappy

Error while runnning autoconfig on apps tier during upgrade

Hi,
Error while runnning autoconfig on apps tier during upgrade from 11.5.9 to 11.5.10.2
below is the error message.
Enter the APPS user password :
The log file for this session is located at: /u01/app/tinst/tinstappl/admin/TINST_dba5/log/05031134/adconfig.log
AutoConfig is configuring the Applications environment...
AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u01/app/tinst/tinstappl
Classpath : /u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/jre/lib/rt.jar:/u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/lib/dt.jar:/u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/lib/tools.jar:/u01/app/tinst/tinstcomn/java/appsborg2.zip:/u01/app/tinst/tinstcomn/java
Using Context file : /u01/app/tinst/tinstappl/admin/TINST_dba5.xml
Context Value Management will now update the Context file
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
at oracle.apps.ad.util.DBUtil.registerDriver(DBUtil.java:153)
at oracle.apps.ad.util.DBUtil.<init>(DBUtil.java:102)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.getDBConnection(FileSysDBCtxMerge.java:759)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.initializeParams(FileSysDBCtxMerge.java:147)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.setParams(FileSysDBCtxMerge.java:128)
at oracle.apps.ad.context.CtxValueMgt.mergeCustomInFiles(CtxValueMgt.java:1762)
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1579)
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:709)
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 8 more
ERROR: Context Value Management Failed.
Terminate.
The logfile for this session is located at:
/u01/app/tinst/tinstappl/admin/TINST_dba5/log/05031134/adconfig.log
Please let me know your suggestions to resolve this issue.
Regards,
Sreenivasulu.

Hi,
DB tier autoconfig was successfully completed.
We have already checked the above mentioned metalink ID's, but still the issue is same.
Can you please advice any other solutions.
Regards,
Sreenivasulu.

Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query

Hi All,
There is a Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query in a report painter.
This query is working fine when executed in 4.7 system where as it is running for more time in ECC6.0.
Select query is on the table COSP.
SELECT (FIELD_LIST)
        INTO CORRESPONDING FIELDS OF TABLE I_COSP PACKAGE SIZE 1000
        FROM COSP CLIENT SPECIFIED
        WHERE GJAHR IN SELR_GJAHR
          AND KSTAR IN SELR_KSTAR
          AND LEDNR EQ '00'
          AND OBJNR IN SELR_OBJNR
          AND PERBL IN SELR_PERBL
          AND VERSN IN SELR_VERSN
          AND WRTTP IN SELR_WRTTP
          AND MANDT IN MANDTTAB
        GROUP BY (GROUP_LIST).
   LOOP AT I_COSP      .
     COSP                           = I_COSP      .
     PERFORM PCOSP       USING I_COSP-_COUNTER.
     CLEAR: $RWTAB, COSP                          .
     CLEAR CCR1S                         .
   ENDLOOP.
ENDSELECT.
I have checked with the table indexes, they were same as in 4.7 system.
What can be the reson for the difference in execution time. How can this be reduced without adjusting the select query.
Thanks in advance for the responses.
Regards,
Dedeepya.

Hi,
ohhhhh....... lots of problems in select query......this is not the way you should write it.
Some generic comments:
1. never use SELECT
                   endselect.
   SELECT
into table
   for all entries in table
where.
   use perform statment after this selection.
2. Do not use into corresponding fields. use exact structure type.
3. use proper sequence of fields in the where condition so that it helps table go according to indexes.
    e.g in your case
          sequence should be
LEDNR
OBJNR
GJAHR
WRTTP
VERSN
KSTAR
HRKFT
VRGNG
VBUND
PARGB
BEKNZ
TWAER
PERBL
sequence should be same as defined in table.
Always keep select query as simple as possible and perform all other calculations etc. afterwords.
I hope it helps.
Regards,
Pranaya

Error in transaction KEA0 during upgrade

Dear All,
During upgrading the custmer system from 4.7 to ECC 6.0 we found some error in the transaction KEA0 while trying to activate the cross client for an operating concern.
The activation logs says that there are the syntax errors in the gereted subroutine pool: RK2O0100.
I however corrected the error and activated the code but again when I am trying to execute the same it gave me the same error and when I go to the sub routine pool I found that the changes are again undone and the previos version is activated. This happens repeatedly that the code is corrected and activated by me and says no error and ones I log off and login again it says the same error.
Help will be appriciated.
Thanks iin advance....
Abhi...

Dear Raymond,
Thankds for your help..........
I tring to run RKEAGENV it shows the error message with STOP button saying that the field WTGBTR not contained in the nametab for table CE1E_B1 and when Io run RKEAGENF it gives a short dump saying that entry for CE10100 is not allowed for TTABS.....
Please help.

Encounter a problem during upgrade sap r/3 4.7 to ecc6

Hi expert:
i encounter a problem during upgrade sap r/3 4.7 to ecc6
in START_SHDI_FIRST step.
here is the error msg~
MSSCRESPDEFN.LOG
Msg 2812, Level 16, State 62, Server Jack, Line 6
Could not find stored procedure 'dbo.sap_upg_getrelease'.
setuser
i checked MS SQL DB and found out that i only got 'erp.sap_upg_getrelease' but not dbo owner.
can any one tell me how to solve this problem?~
thanks.
Regards
Jack Lee

It's the kernel for the shadow the correct?.
Regards,
Alfredo.

Performance optimization during upgrade

Similar Messages

Maybe you are looking for