Entered DATA missing from the Database ( SEM CUBE )

Hi,
We are in the process of compiling the Annual Budget for 2011- 12. We
are using BW-BPS for capturing the data.
The Problem, is that we are not able see the Data entered in last two
days. The users have entered the data in SEM-BPS layouts and saved it.
Also they have executed the Queries through the Bex Analyzer which had
the data till yesterday evening, but today if the user tries to refresh
the query then the data is missing.
The name of BW SEM-CUBE is "ZUCOPA_TC".
Please suggest some solution.
Thanks
Nilesh

Nilesh,
someone might have run a delete function or another incorrectly configured planning function that deleted the data (or set records to zero).
First, STOP any compression jobs on your planning InfoCubes. (If any compression job with zero eliminiation ran the past two days, the data is probably lost for good).
Second, check in LISTCUBE if the data is still in the InfoCube. Make sure to select ALL fields for the output (including request id). If you are lucky, you will find all the deltas of changes that happened in the past days. If there was a delete (or similar) you should find these deltas, too. Now you can recreate the original data again (it's tedious but can be done).
Whatever the outcome, you should implement some operational improvements to your planning applications:
1) Create backup InfoCubes of your planning InfoCubes (fill with nightly DTP for example)
2) Implement audit log of planning activities (see how-to guides)
Both will give you a much better chance of recovering data in such cases.
Good luck,
Marc
SAP Techology RIG

Similar Messages

Can I use stored procedures to improve data retrieval from the database?

I have been requested to get multiple pieces of data from multiple tables and return the output in an array for use in a Java program.
Eliminating multiple calls to the database. Currently, the data is retrieved from the database in multiple steps but to eliminate
possible bottlenecks in the future, I created several complex sql statements.
For instance,
In the first table there are 20 columns of data. has a column named type which can have the one of these values: line, inn, or bsc
In the second table there are 6 columns of data. has the additional data for type line
In the third table there are 7 columns of data. has the additional data for type inn
In the fourth table there are 2 columns of data. has data regardless of type
etc...
Depending on a specific column value retrieved (inn) from the first table:
I need to collect all 20 columns in the first table and get all the columns in third table and the columns in the fourth table, etc.
Question: How can I remove the duplicate primary key columns without specifying for each table the column names to be returned?
I used the wildcard SELECT * because I didn't want to have to update the retrieval methods if additional columns are added to these
secondary tables.
example of my sql for type inn data:
select * from first_table f, third_table s, fourth_table t
where (f.column1='xxxx' and f.column2='xxxx') (the 'xxxx' are passed into the sql statement)
and
((s.column1=f.column1 and s.column2=f.column2)
and
(f.column3=t.column1));
Currently, I've duplicated the separate sqls for each valid type found in the first table (at least a dozen types). The only difference is
the table name. Instead of the third table I use the second table, etc.
The MAIN Question: How can I set this up to have one sql to handle each type? I want to eliminate having over a dozen duplicated sqls. Can I
incorporate this into a stored procedure or something? If so, how? Can anyone provide sample coding?
Your help is very much appreciated. Thank you.
GD

Hi, Salah.
Use "Exec" in your query to run procedures.
SAPbobsCOM.Recordset oRS;
oRS = (SAPbobsCOM.Recordset)pCmp.GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset);
oRS.DoQuery ("EXEC YourStoredProcName");
Triggers are not supported in SDK.
Regards,
Aleksey

How to get the date fromat from the database?

I am using Oracle9i database and i want to get the format of the date that is stored in the database.
How do i do that?
Thanks,
Shrimon

concatenate sy-datum0(2) '01' sy-datum4(4) into v_firstdate.
or yo ucan use the fm:
HR_JP_MONTH_BEGIN_END_DATE
usage:
    call function 'HR_JP_MONTH_BEGIN_END_DATE'
         exporting
              iv_date             = sy-datum
         importing
              ev_month_begin_date = gv_begda
              ev_month_end_date   = gv_endda.
Regards,
Ravi
Message was edited by:
        Ravi Kanth Talagana

How to modify data recieved from the database and displayed in a DG

Hello, it's me again with a simple question :
i've got the SQLi request who returns multiples rows.
In this row i have for example :
Reward --> 1
How to, instead of displaying 1 in the datagrid, change this value to "YES"
I follow this lead :
private function onResultStats(event:ResultEvent):void
 ServerStatsArr = new ArrayCollection(event.result.source);
 for (var i:int=0; i < ServerStatsArr.length;i++)
 if (ServerStatsArr[i].abonnement == 304){
 ServerStatsArr[i].abonnement = 'Premium';
 }else{
 ServerStatsArr[i].abonnement = 'Non';
 if (ServerStatsArr[i].transparence == 1) {
 ServerStatsArr[i].transparence = 'Oui' ;
 }else{
 ServerStatsArr[i].transparence = 'Non' ;
 ServerStatsArr.refresh();
Why this method is working for abonnement when (ServerStatsArr[i].abonnement == 304) it displays Premium but it's NOT working for transparence ?
i tested (ServerStatsArr[i].transparence == 1) and (ServerStatsArr[i].transparence == '1')
Thank you

hi Again,
private function setLabel(item:Object,column:DataGridColumn):String
switch(column.dataField)
case "transparence":
if (item.transparence == "1")
return ("yes")
else
return ("no")
break;
case "abonnement":
if (item.abonnement == "304")
return ("premium")
else
return ("none")
break;
default:
return("");
and the adjustments to your grid - add the labelfunction to the following columns
<mx:DataGridColumn headerText="transparence" dataField="transparence" labelFunction="setLabel"/>
<mx:DataGridColumn headerText="abonnement" dataField="abonnement" labelFunction="setLabel" />
I hope we get a distinction credit for this assignment ...
David.

How to retrieve the large data from the database

in my program, I want to operate the data retrieved from the database. but there are too many rows in the ResultSet . so when I try to get the ReusltSet from the database, the error of "java.lang.OutOfMemoryError
" will appear . because there are two million rows contained in the ResultSet, So I want to know whether there are some methods to deal with this problem.
anyone can give me some tips or recommend some papers and books to me.
thanks!!!!

the program is developed for the data warehourse, you know there is a large number of data in data warehourse. so I think I have to deal with the very large ResultSet in my program, this code is a example for my problem :
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class Untitled1 {
    String user = "";
    String password = "";
    public void createTable() {
        try {
            Class.forName("com.sybase.jdbc3.jdbc.SybDriver");
            System.out.println("Good to go");
            String url = "jdbc:sybase:Tds:59.64.137.240:5000/TJ";
            Connection conn = DriverManager.getConnection(url, user, password);
            System.out.println("connect successfully!");
//            Statement st1 = conn.createStatement();
            String sqlsentence2 = "SELECT DISTINCT caller FROM upcdr";
            PreparedStatement st2 = conn.prepareStatement(sqlsentence2);
            PreparedStatement st3 = conn.prepareStatement("INSERT INTO callerTable VALUES(?)");
            System.out.println("createstatement successfully!");
//            String sqlsentence1 = "CREATE TABLE callerTable (caller CHAR(18))";
//            st1.executeUpdate(sqlsentence1);
//            System.out.println(sqlsentence1);
//            st1.close();
            ResultSet rs = st2.executeQuery();
            while (rs.next()) {
                st3.setString(1, rs.getString("caller"));
                st3.executeUpdate();
                System.out.println(rs.getString("caller"));
            st2.close();
            st3.close();
        } catch (SQLException e) {
            e.printStackTrace();
            System.out.println(e.getMessage());
           System.out.println( e.getSQLState());
           System.out.println( e.getErrorCode());
        } catch (ClassNotFoundException e) {
            e.printStackTrace();
    public static void main(String args[]) {
        Untitled1 cct = new Untitled1();
        cct.createTable();
}at here, the table "upcdr" is very large, it has two million rows. when I run this program , the error will happen. someone told me that if I use the cursor, because it will retrieve one row from the database every time, so it will not produce a very large ResultSet, then the memory would not be used out. but I am not familiar with that aspect. so I think if anyone can give me some advice.
thanks!!!!

How to select the data efficiently from the table

hi every one,
i need some help in selecting data from FAGLFLEXA table.i have to select many amounts from different group of G/L accounts
(groups are predefined here which contains a set of g/L account no.).
if i select every time for each group then it will be a performance issue, in order to avoid it what should i do, can any one suggest me a method or a smaple query so that i can perform the task efficiently.

Hi ,
1.select and keep the data in internal table
2.avoid select inside loop ..endloop.
3.try to use for all entries
check the below details
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

I wish to generate reports from the database an out put it but i need to enter a date from and to ina html input box

i wish to generate reports from the database an out put it
but i need to enter a date from and to ina html input box
in the input box a data of range will be input from a start
to latest
latest being the default as today's date.
any help tips snipplets, concepts , turot=rails.
thanks

easycfm.com has tutorials for people who are brand new.
If you don't know much about sql, I have heard good things
about the book, Teach Yourself SQL in 10 Minutes by Ben
Forta.

Automated data load from APO to SEM transactional cube

Hi ,
We have BW-SEM system integrated with APO system.
I could see automated data loads from APO to SEM transactional cube ..
Infopackage name as "Request loaded using the APO interface without monitor log" ..
I don't see any infopackage by this name in both the systems ( APO & SEM )..
I am not sure how it configured ..
Appreciate any inputs on how its happens .....
Thanks in advance

Hi,
As I mentioned the starting point will be the tcode BPS0. There will be 2 planning areas created (if I am correct) one for SEM cube and the other for APO cube. The better way to find it will be goto tcode se16 and enter UPC_BW_AREA and key in the cube names in the cube field. this will give you the planning area names now look for a multiplanning area which has the 2 areas included in them (this is available in table UPC_AREAM).
then goto BPS0 and you will have to find which function is being used to post the data.
thanks

Suddenly getting UserNotFoundException: User Not Found: Could not load profile data from the database

Starting yesterday (I believe) we are suddenly receiving a "User not found" error when trying to view a user's profile page when clicking on their name (in search or elsewhere) via the url
https://www.contoso.org/Person.aspx?accountname=contoso%255Cmyuserlogin
This is happening for all users. (but profiles exist and seem ok, and sync with AD is running fine) When looking in the logs I see the error (full ULS log is later below)
Exception in LoadRequestedUserProfile: (Microsoft.Office.Server.UserProfiles.UserNotFoundException: User Not Found: Could not load profile data from the database.
The only clue of what MAY be going on is just before that I see the following two lines which came up after I changed the Database logging to Verbose:
ConnectionString: 'Data Source=INSTANCE;Initial Catalog=UPAPROFILEDB;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][3][UPAPROFILEDB]' Partition:
NULL ConnectionState: Closed ConnectionTimeout: 15
SQL connection time: 0.0456 for Data Source=INSTANCE;Initial Catalog=UPAPROFILEDB;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][3][HNet3_Svc_Prod_UPA_Profile]
If I am reading that correctly, does it mean the connection to the database is timing out instantly? I am able to use powershell to pull up profiles and print them to the screen while on the webservers. And it's only the one specific page that is not
working.
What sort of tests or further debugging can I do for the error above?
We are on premise, SharePoint 2013 sp1, sql2012, server 2012, claims using the full SharePoint Profiile Sychronization against AD. Farm has been running since last august. Last week the admin team did run windows update on all servers, I can't be sure
if it was broken for 5 days and no one noticed or if it broke yesterday.
I already did the following:
Verified the profiles do exist in central admin.
I can still access their personal sites directly via
https://www.contoso.org/personal/myuserlogin
I checked the ProfileDB database and made sure the service accounts for the UPA has dbowner, so does the farm account, and the web application pool has SPDataAccess.
Verified the AD sync account has proper rights in AD.
I reran a full synchronization which ran with no errors.
File systems on the webservers and appserver have plenty of free space.
Rebooted every server in farm
I even checked the bin directory of the mysite webapplication, (since once I had a weird problem where access to bin was removed.) WSS_ADMIN_WPG, WSS_RESTRICTED_WPG_W4 have full control and WSS_WPG,IIS_IUSRS all have read and execute.
I opened powershell on the webserver I can indeed load profiles and print their values.
Timestamp Area Category EventID Level Message Correlation
07/25/2014 14:11:08.43 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (GET:https://my.hungernet.org:443/Person.aspx?accountname=FA%255Ccbuchholz)). Parent No
07/25/2014 14:11:08.43 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:https://my.hungernet.org:443/Person.aspx?accountname=FA%255Ccbuchholz) be11a89c-fbe8-a08d-57d2-afa6a4948743
07/25/2014 14:11:08.43 SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq be11a89c-fbe8-a08d-57d2-afa6a4948743
07/25/2014 14:11:08.43 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:https://my.hungernet.org:443/Person.aspx?accountname=FA%255Ccbuchholz)). Execution Time=1.3859 be11a89c-fbe8-a08d-57d2-afa6a4948743
07/25/2014 14:11:08.47 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (GET:https://my.hungernet.org:443/Person.aspx?accountname=FA%255Ccbuchholz)). Parent No
07/25/2014 14:11:08.47 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:https://my.hungernet.org:443/Person.aspx?accountname=FA%255Ccbuchholz) be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.49 SharePoint Foundation General ajji6 High Unable to write SPDistributedCache call usage entry. be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|fa\cbuchholz, ClaimsCount=167 be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50 SharePoint Foundation Files ak8dj High UserAgent not available, file operations may not be optimized. at Microsoft.SharePoint.SPFileStreamManager.CreateCobaltStreamContainer(SPFileStreamStore spfs, ILockBytes ilb, Boolean copyOnFirstWrite, Boolean disposeIlb) at Microsoft.SharePoint.SPFileStreamManager.SetInputLockBytes(SPFileInfo& fileInfo, SqlSession session, PrefetchResult prefetchResult) at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedStreamBufferFactory.CreateFromDocumentRowset(Guid databaseId, SqlSession session, SPFileStreamManager spfstm, Object[] metadataRow, SPRowset contentRowset, SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres) at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(Int32 rowOrd, Object ospFileStmMgr, SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...) at Microsoft.SharePoint.Library.SPRequestInternalClass.GetFileAndMetaInfo(String bstrUrl, Byte bPageView, Byte bPageMode, Byte bGetBuildDependencySet, String bstrCurrentFolderUrl, Int32 iRequestVersion, Byte bMainFileRequest, Boolean& pbCanCustomizePages, Boolean& pbCanPersonalizeWebParts, Boolean& pbCanAddDeleteWebParts, Boolean& pbGhostedDocument, Boolean& pbDefaultToPersonal, Boolean& pbIsWebWelcomePage, String& pbstrSiteRoot, Guid& pgSiteId, UInt32& pdwVersion, String& pbstrTimeLastModified, String& pbstrContent, UInt32& pdwPartCount, Object& pvarMetaData, Object& pvarMultipleMeetingDoclibRootFolders, String& pbstrRedirectUrl, Boolean& pbObjectIsList, Guid& pgListId, UInt32& pdwItemId, Int64& pllListFlags, Boolean& pbAccessDenied, Guid& pgDocid, Byte& piLevel, UInt64& ppermMask, ... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...Object& pvarBuildDependencySet, UInt32& pdwNumBuildDependencies, Object& pvarBuildDependencies, String& pbstrFolderUrl, String& pbstrContentTypeOrder, Guid& pgDocScopeId) at Microsoft.SharePoint.Library.SPRequestInternalClass.GetFileAndMetaInfo(String bstrUrl, Byte bPageView, Byte bPageMode, Byte bGetBuildDependencySet, String bstrCurrentFolderUrl, Int32 iRequestVersion, Byte bMainFileRequest, Boolean& pbCanCustomizePages, Boolean& pbCanPersonalizeWebParts, Boolean& pbCanAddDeleteWebParts, Boolean& pbGhostedDocument, Boolean& pbDefaultToPersonal, Boolean& pbIsWebWelcomePage, String& pbstrSiteRoot, Guid& pgSiteId, UInt32& pdwVersion, String& pbstrTimeLastModified, String& pbstrContent, UInt32& pdwPartCount, Object& pvarMetaData, Object& pvarMultipleMeetingDoclibRootFolders, String& pbst... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...rRedirectUrl, Boolean& pbObjectIsList, Guid& pgListId, UInt32& pdwItemId, Int64& pllListFlags, Boolean& pbAccessDenied, Guid& pgDocid, Byte& piLevel, UInt64& ppermMask, Object& pvarBuildDependencySet, UInt32& pdwNumBuildDependencies, Object& pvarBuildDependencies, String& pbstrFolderUrl, String& pbstrContentTypeOrder, Guid& pgDocScopeId) at Microsoft.SharePoint.Library.SPRequest.GetFileAndMetaInfo(String bstrUrl, Byte bPageView, Byte bPageMode, Byte bGetBuildDependencySet, String bstrCurrentFolderUrl, Int32 iRequestVersion, Byte bMainFileRequest, Boolean& pbCanCustomizePages, Boolean& pbCanPersonalizeWebParts, Boolean& pbCanAddDeleteWebParts, Boolean& pbGhostedDocument, Boolean& pbDefaultToPersonal, Boolean& pbIsWebWelcomePage, String& pbstrSiteRoot, Guid& pgSiteId, UInt32& pdwVersion,... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ... String& pbstrTimeLastModified, String& pbstrContent, UInt32& pdwPartCount, Object& pvarMetaData, Object& pvarMultipleMeetingDoclibRootFolders, String& pbstrRedirectUrl, Boolean& pbObjectIsList, Guid& pgListId, UInt32& pdwItemId, Int64& pllListFlags, Boolean& pbAccessDenied, Guid& pgDocid, Byte& piLevel, UInt64& ppermMask, Object& pvarBuildDependencySet, UInt32& pdwNumBuildDependencies, Object& pvarBuildDependencies, String& pbstrFolderUrl, String& pbstrContentTypeOrder, Guid& pgDocScopeId) at Microsoft.SharePoint.SPWeb.GetWebPartPageContent(Uri pageUrl, Int32 pageVersion, PageView requestedView, HttpContext context, Boolean forRender, Boolean includeHidden, Boolean mainFileRequest, Boolean fetchDependencyInformation, Boolean& ghostedPage, String& siteRoot, Guid& siteId, Int64& bytes, ... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...Guid& docId, UInt32& docVersion, String& timeLastModified, Byte& level, Object& buildDependencySetData, UInt32& dependencyCount, Object& buildDependencies, SPWebPartCollectionInitialState& initialState, Object& oMultipleMeetingDoclibRootFolders, String& redirectUrl, Boolean& ObjectIsList, Guid& listId) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.FetchWebPartPageInformationForInit(HttpContext context, SPWeb spweb, Boolean mainFileRequest, String path, Boolean impersonate, Boolean& isAppWeb, Boolean& fGhostedPage, Guid& docId, UInt32& docVersion, String& timeLastModified, SPFileLevel& spLevel, String& masterPageUrl, String& customMasterPageUrl, String& webUrl, String& siteUrl, Guid& siteId, Object& buildDependencySetData, SPWebPartCollectionInitialState& initialState, ... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...String& siteRoot, String& redirectUrl, Object& oMultipleMeetingDoclibRootFolders, Boolean& objectIsList, Guid& listId, Int64& bytes) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetFileForRequest(HttpContext context, SPWeb web, Boolean exclusion, String virtualPath) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.InitContextWeb(HttpContext context, SPWeb web) at Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.GetContextWeb(HttpContext context) at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object oSender, EventArgs ea) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IEx... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...ecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompl... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50* SharePoint Foundation Files ak8dj High ...etion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50 SharePoint Foundation Files aiv4w Medium Spent 0 ms to bind 4224 byte file stream be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.50 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=11.7341 be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.52 SharePoint Portal Server User Profiles aj2aw Verbose GetPartitionPropertiesCache :: ApplicationId = c604ddac-b9f9-4661-b31f-44cdcf2b78dc be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.52 SharePoint Portal Server User Profiles aj2ax Verbose GetPartitionPropertiesCache :: Trying to find existing cache be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.52 SharePoint Portal Server User Profiles aj2az Verbose GetPartitionPropertiesCache :: Getting Cached object be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Portal Server User Profiles aj2aw Verbose GetPartitionPropertiesCache :: ApplicationId = c604ddac-b9f9-4661-b31f-44cdcf2b78dc be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Portal Server User Profiles aj2ax Verbose GetPartitionPropertiesCache :: Trying to find existing cache be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Portal Server User Profiles aj2ay Verbose GetPartitionPropertiesCache :: Found existing cache in httpcontext be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Server Database tzku Verbose ConnectionString: 'Data Source=HungerNet3;Initial Catalog=HNet3_Svc_Prod_UPA_Profile;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][3][HNet3_Svc_Prod_UPA_Profile]' Partition: NULL ConnectionState: Closed ConnectionTimeout: 15 be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Server Database ahjqp Verbose SQL connection time: 0.0583 for Data Source=HungerNet3;Initial Catalog=HNet3_Svc_Prod_UPA_Profile;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][3][HNet3_Svc_Prod_UPA_Profile] be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Foundation General adyrv High Cannot find site lookup info for request Uri http://www.hungernet.org/. be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Foundation General adyrv High Cannot find site lookup info for request Uri http://www.hungernet.org/. be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.54 SharePoint Foundation General adyrv High Cannot find site lookup info for request Uri http://lnkd.in/bb6rsHj. be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Server Database tzku Verbose ConnectionString: 'Data Source=HungerNet3;Initial Catalog=HNet3_Svc_Prod_UPA_Profile;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][3][HNet3_Svc_Prod_UPA_Profile]' Partition: NULL ConnectionState: Closed ConnectionTimeout: 15 be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Server Database ahjqp Verbose SQL connection time: 0.0456 for Data Source=HungerNet3;Initial Catalog=HNet3_Svc_Prod_UPA_Profile;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][3][HNet3_Svc_Prod_UPA_Profile] be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Portal Server User Profiles ajw8l High Exception in LoadRequestedUserProfile: (Microsoft.Office.Server.UserProfiles.UserNotFoundException: User Not Found: Could not load profile data from the database. at Microsoft.Office.Server.UserProfiles.UserProfile.Load(SqlDataReader myReader, Boolean bFirstRead, Boolean firstReaderIsViewerRights, Boolean includeColleagueRecords, Boolean includeLanguageAndRegionalSettings, Boolean shouldCloseReader) at Microsoft.Office.Server.UserProfiles.UserProfile.RetrieveUser(String strAcct, Guid gAcct, Byte[] bSid, Nullable`1 recordId, Boolean doNotResolveToMasterAccount, Boolean loadFullProfile, Boolean loadColleagueRecordIds, String strEmail) at Microsoft.Office.Server.UserProfiles.UserProfile..ctor(UserProfileManager objManager, String strAcct, Boolean doNotResolveToMasterAccount, Boole... be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55* SharePoint Portal Server User Profiles ajw8l High ...an forceUserIsSelf, Boolean loadFullProfile, Boolean loadColleagueRecordIds, String strEmail) at Microsoft.Office.Server.UserProfiles.UserProfileManager.GetUserProfile(String strAccountName, Boolean doNotResolveToMasterAccount, Boolean loadFullProfile, Boolean loadColleagueRecordIds) at Microsoft.SharePoint.Portal.WebControls.ProfilePropertyLoader.LoadRequestedUserProfile(String& redirectionUrl)) be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Foundation General aat87 Monitorable be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Foundation General ajji6 High Unable to write SPDistributedCache call usage entry. be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,20 ajji6,3 agb9s,10 ak8dj,1 b4ly,25 adyrv,1 adyrv,4 adyrv,3 ajw8l,1 aat87,3 ajji6 be11a89c-ebeb-a08d-57d2-a513d117e184
07/25/2014 14:11:08.55 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:https://my.hungernet.org:443/Person.aspx?accountname=FA%255Ccbuchholz)). Execution Time=78.9958 be11a89c-ebeb-a08d-57d2-a513d117e184

Have Windows Updates been applied? See my note about this
https://twitter.com/imorrish/status/491020435039854592
Look at the URL in the search results. It may have invalid character in which case you can use this fix
http://blogs.msdn.com/b/spses/archive/2014/06/30/sharepoint-2013-the-search-results-with-5c-the-character-will-become-double-encoded-and-causes-broken-links.aspx
Regards,
Ian
http://sps.cloudapp.net
Regards, Ian Internet Sites running on SharePoint 2013 http://j.mp/sp2013sites

Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.

Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.
I have dropped and recreated a fact table to refresh the data as the table is having identity columns. So not able to directly insert data. After that cube is throwing above error.
Please suggest.

Hi Md,
It hard to analyse the issue base on the limited information, Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could be different for your server), there are 3 log files that are generated:
msmdrrv.log
FlightRecorderCurrent.trc
FightRecorderBack.trc
The msmdrrv.log simply points to the other two logs. There might be some detail information for this error. Please provide us the detail information about it, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Failure to retrieve data from the database (Vendor Code 6550)

I am having a trouble with two of the 6 reports that I have created. I am using Crystal XI and Oracle 10g. The underlying database object is a stored procedure that accepts as input a start time as a TIMESTAMP, an end time as a TIMESTAMP and a furnace number as a number. I have a cursor ref as a return parameter.
When I run the stored procedure in Oracle I get the selected records and can view them on the screen.
When I refresh data on the report in Crystal XI developer, the designer asks me for the start and end time and furnace number. When I input these values the report displays properly.
When I launch the report from my VB .NET 2005 application I am asked for the username and the password for the database (this is another problem I need to solve as this information I put into the program seems to be ignored in my program) then I receive the following failure message:
Failure to retrieve data from the database (Vendor Code 6550)
When I launch the other reports, they only ask me for the username and password then they display the proper data.
The main difference between my other reports and the two that are returning the above failure code is that the other reports are to either tables or views. The two that don't work are tied to stored procedures. I there any way that I can solve this problem or at least get more information?
Any help would be greatly appreciated. Let me know if you need any other information.

I have a similar problem, the only difference is that the crystal report error is only thrown when I try to load the sub reports at my web application. When I deploy my report to the Web application the main report loads up fine but when I try to launch the sub reports from the main report it can no longer load.
But when I use the Crystal report developer I am able to load the main report and it's associated sub reports without any issues.
My issue only occurs when I try to load the sub report in the web application. The following sections shows how my reports look like both in my .NET web application and also at the Crystal Report Development IDE.
Failure: Loading my Reports from .NET Web Application
1) When I load from the web application I am able to load the main report as per the print screen below.
2) When I try to click on the hyper links to enter the sub reports I am now able to load them, both sub reports cannot load and will throw the same error "
Failed to retrieve data from the database. Details: [Database Vendor Code:
6550 ] Failed to retrieve data from the database. Details: [Database Vendor
Code: 6550 ] Failed to retrieve data from the database. Error in File OAWR3011A
{CEC8A94A-4490-4640-95FB-2739A679978B}.rpt: Failed to retrieve data from the
database. Details: [Database Vendor Code: 6550 ] "
Success: Loading my Reports from Crystal Report Development Tool
1) This is my Main Report Loaded from the Crystal Report Development Tool, the first two hyperlinked fields are links to my sub reports, step number 2 and number 3 shows my sub reports when I load it using Crystal Report Developer
2) Sub Report 1 Loaded Successfully, when I click on the fields in the first link
3) Sub Report 2 loaded successfully when I click the second field hyper link

Can I restore the deleted statistical data from the database tables?

Hi all,
I have deleted the statistical data from the database tables like(Ex: RSDDSTAT, RSDDSTATWHM,..) by mistake through RSA1> Tools> BW Statistics for Infoproviders--> Delete.
Is there any way to restore the deleted data back? Thanks in advance.

Now I'm really confused-
Your first post said
"I have deleted the statistical data from the database tables like(Ex: RSDDSTAT, RSDDSTATWHM,..) by mistake through RSA1> Tools> BW Statistics for Infoproviders--> Delete."
but your last respsonse said
"I have deleted the BW Statistics data, not the actual data in RSDDSTAT tables through
RSA1 -> Tools -> BW Statistics for InfoProviders -> clicked 'Delete' bin to delete data."
If you used the RSA1 -> Tools -> BW Statistics for InfoProviders -> clicked 'Delete' - then you deleted the data from the RSDDSTAT tables. This assumes you accepted the default date range that would have popped up after the clicking on the Delete button which specified to delete thru the current date. If this is what you did, the data is gone. Your only hope is be to recover from a DB backup.
The data in the RSDDSTAT tables is what is used to feed the BW Statistics cubes, generally on a daily basis.

Error while retriving the data from the database

morning we shutdown and start up the server.after that when i am retreving the data from the database it is giving the following error.
ora-04030: out of process memory when trying to allocate 64512 bytes(sort subheap,sort key)
pga_aggregate_target details are as follows
value=2147483648
display value=2g
is default=false
is sesmodifiable=false
hash=2184567208

Please look at the following link :
how solve ORA-04030: out of process memory when trying to allocate
Cheers!

Crystal Reports - Failed to retrieve data from the database

Hi There,
I'm hoping that somebody can help me.
I've developed a crystal report from a stored procedure which I wrote. I can execute the stored procedure within SQL Server and within the Crystal Reports designer without any errors. Furthermore, I have imported the report into sap and can run it within SAP from the server without any errors. SAP version 8.81 PL5
The issue is that when it's run from a client machine, I get the following error: "Failed to retrieve data from the database. Details: Database Vendor Code: 156. Error in the File RCR10010 {tempfile location}
Here's a list of things which I have tried, all to no avail:
- Checked user permissions to ensure that they have proper authorizations
- Re-set the datasource connection and re-imported the report to SAP.
- Exported the report and reviewed the datasource connection and re-imported to SAP.
- Tried to run the report on multiple machines to ensure that it's not machine specific
- Tried to run the report using different users to ensure it's not user specific.
- Tested other reports built from stored procedures on client machines to ensure that they work.
Any assistance in this would be GREATLY appreciated.
Thank you

After further testing, we found that the report could be run within SAP on any work station which had the CR designer installed on it.
As it turns out, the procedure which I wrote has temp tables in it. The runtimes built into the SAP client install do not support creating temp tables when executing the report from within SAP. Which is why the report could not retreive data.
To work around this, I installed external runtimes which were the same version of the Crystal Report and now the report can be run within SAP from any workstation which has the external runtimes (and not just the runtimes within the SAP client).
I hope this makes sense.

Failed to retrieve data from the database crystal reports 2008 in SAP B1

Hello friends,
I am using Crystal report 2008 with SAP B1 PL 8.8. When I run any report, it runs correctly from Crystal Report. But whenever I try to open the same report through SAP ( Tools -> Preview External Crystal Report ), it prompts the parameters for that report and then open up the crystal report window and throws an Error message ("failed to retrieve data from the database. Details [Database Vendor Code: 156]").
Please any one suggest me the corrective solution.
Thanks in Advance,
Keyur Raval.

I had the same problem in SAP B1 2007. Report worked fine except when it was open from B1. Generally there may be different problems. In my case the same problem was caused by using some procedure which was in a specific schema. Changing the schema into "dbo" solved the problem.
Radoslaw Blaniarz

Entered DATA missing from the Database ( SEM CUBE )

Similar Messages

Maybe you are looking for