Load several cubes are different
Hi
I have a problem with loads.
I have a DSO, it has 15 millon records, and i am trying to load the data to 2 different cubes, filtering by period range (ie. 1 to 3), and both load extract different quantity of records.
For example, the extraction from 001.2007 to 003.2007 is
DSO->Cube1 = 756128 records
DSO->Cube2 = 12464 records
As you can see the quantity or records taken are very different. The loads are full and the extraction is from Active table (without archive),
If I see the active table of DSO, with the filter it is 756128, as the records taken in the load of the Cube1.
But what is it happening with the load of Cube2?
The Start routines are not configured.
The system is version 7 with support package 5.
Regards, Fede
Because of the Key differences from Cube 1 to cube 2, there might be less number of records.
Take the keys and put it in the DSO and see how many records you are getting with that time period
Thanks
Kalyan
Similar Messages
-
my internet isn't working anymore, its not the wifi but the actual computer safari and google chrome. Its not loading particular websites, and if it is loading them, they are different to how they use to be. Computer was slow yesterday as well and took about 4 hours to finally be able to shut down and close everything. Does anyone know how to fix this? Im going into exams and need my internet to work
ThanksI dont know if your allowed to show images here but if you are then these pictures will show you what happens.
This is what happens when I turn on my iMac (normal)
This is what happens a few seconds after I turn on my iMac
Here it is up close
Hopefully these pictures will help you understand what's been hapening on my iMac when I turn it on.
Thanks -
CUBE - Are different pay as you grow license types stackable?
Hi.
I'd like to know if Redundant licences are stackable with single use licenses. Perhaps someone could kindly assist.
Do I need to buy enough RED licenses for the total session count, thus wasting the bundled licenses that are supplied with the device. Or should I take the bundled licenses into account when ordering RED the licenses?
Eg. for total sessions = 100 on a router pair supplied with 25 licenses each, I order 1 x FL-CUBEE-100-RED or 3 x FL-CUBEE-25-RED.
Thanks in advance.You would add them up... that's how you'd get anything in between 50 and 100 sessions for example.
FYI they're honor based as well, so there's no technical/licensing portal hoops to jump through.
Aaron -
Goods issue dates are different in sales order & delivery
Hi,
We have a situation where in sales order schedule line tab goods issue date is 21.30.2011
but in delivery the planned GI date is 28.03.2011.
There are two line item in the sales order & in both the line items all the dates are same.
Same route is there in sales order & delivery.
In delivery Item category avalability check Off is Y(Do not check avail. when reporting results of pick.request)
All the dates(delivery,loading,Transportation planning) are different .
waiting for responce.
Thanks In advence
Susrikantgoods issue date is 21.30.2011
What was the Actual GI date in delivery?? This should be the same as schedule line date.
thanks
G. Lakshmipathi -
Data in cube is different from what I loaded
A strange problem just happened... I loaded a cube from a flat file and everything looked OK. PSA has correct data. Update and transfer rules are direct assignments. nevertheless one of the characteristics change its value. I do not think a conversion routine has any influence on this although I could be wrong. For example I loaded a flat file with A = '050501' and the cube table gets loaded with '500005'. I've debugged up to update rules and the value is always correct.
If I load the cube through SEM the same thing happens. I write a value and a different value is written in the infocube.
Have any of you experienced the same issue?How do you see the data in master data? Do you see 050501 or 50005.
Conversion may have an influence. Do you mind to delete the data in the cube, remove the conversion routine of the info object, and reload.
When you say i also loaded thru SEM, what that means?
Ravi Thothadri -
What are different ways to load a class
what are different ways to load a class??
manoj.java wrote:
I am preparing for something and exploring the java.
want to know in regard of the same.
Please help me out.And this means essentially nothing.
Essentially there is only one way. Through a ClassLoader, and it's loadClass method. Now, there are multiple ways of invoking this, however, either directly or indirectly.
Edit: There is, of course, other things, such as defineClass in ClassLoader, that lets you manually read a class defintion from somewhere, anywhere, and define, which, logically, also "loads" it.
Now, once again, What are you trying to do? "something" and "exploring the java" are meaningless in this form. If you tell us what, exactly you are trying to do, we could actually help you do it! -
When I open firefox i am getting a new small browser window opening with some kind of ad (different ad each time). McAfee blocks the ad after about 10 - 15 seconds. I also noticed that while looking at ads on craigslist, a few of the words are different colors and they take you to another website when clicked on. How do I get rid of this problem?
This just started todayHave you got Firefox set to block popups? Look in Options > Content and see if anything is whitelisted in the exceptions.
You can block most of the advertising stuff if you use Adblock Plus with an Easylist subscription. There is also an auxiliary addon for Adblock Plus to block more popups.
There is a site textsrv.com that adds links to sites to redirect to other sites that you can block with Adblock Plus (if it is not already blocked) by adding that to the custom block list. -
How will u know that a dimension can b a lineitem Dim b4 loading into Cube
Hi, Im new to this. My qury is how will u know that a dim will b a LineItem dimension bfore loading in to cube , are there anystandard to b followed. Ca u give me some realtime detailed scenarious.
Hi,
When compared to a fact table, dimensions ideally have a small cardinality. However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic Document is used, in which case almost every entry in the fact table is assigned to a different Document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension.
Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
1. Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
A table- having a very large cardinality- is removed from the star schema. as a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
We recommend that you use DataStore objects, where possible, instead of InfoCubes for line items. See Creating DataStore Objects.
2. High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
Activities
When creating dimensions in the InfoCube maintenance, flag the relevant dimension as a Line Item/ having High Cardinality.
Define lots of small dimensions rather than a few large dimensions.
The size of the dimension tables should account for less than 10% of the fact table.
If the size of the dimension table amounts to more than 10% of the fact table, mark the dimension as a line item dimension.
To attain good performance for a query on non-cumulative InfoCubes, you should take note of the following:
Compression:
Compress all requests in the non-cumulative InfoCube, or at least most of them.
The performance of a query based on a non-cumulative InfoCube depends heavily on how the InfoCube is compressed. If you want to improve the performance of a query of this type, first check in so far as this is possible - whether the data in the InfoCube should be compressed. You should always compress data when you are sure that the request affected will not need to be deleted from the InfoCube.
Validity Table
Use as few validity-determining characteristics as possible.
The number and cardinality of the validity-determining characteristics heavily influences performance. Therefore, you should only define characteristics as validity-determining characteristics when it is really necessary.
Time Restrictions in the Query
As far as possible, restrict queries based on non-cumulative InfoCubes to time characteristics.
The stricter the time-based restriction, the faster the query is generally executed, as the non-cumulative is reconstructed if the number of times is smaller.
Time Drilldown in the Query
If you no longer need the average, split a query on a non-cumulative InfoCube (which contains both key figures with LAST aggregation and key figures with AVERAGE aggregation) into two queries.
With non-cumulative key figures with the exception aggregation LAST, the time characteristic included in the drilldown makes a difference to performance. If, for example, both Calendar Day and Calendar Month are included in the InfoCube, drilldown by month is faster than drilldown by day, because the number of times for which a non-cumulative has to be calculated is smaller.
For the other types of exception aggregation (average, average weighted with factory calendar, minimum and maximum), this rule is not valid as in these cases, the data is always calculated on the level of the most detailed time characteristic first before exception aggregation is performed.
Totals Rows
Hide the totals row in the query when not required.
Depending on the type of aggregation being used, the calculation of totals rows can be very time-consuming.
When selecting MDC dimensions, proceed as follows:
Select dimensions for which you often use restrictions in queries.
Select dimensions with a low cardinality.
The MDC dimension is created in the column with the dimension keys (DIMID). The number of different combinations in the dimension characteristics determines the cardinality. Therefore, select a dimension with either one, or few characteristics and with only a few different characteristic values.
Line item dimensions are not usually suitable, as they normally have a characteristic with a high cardinality.
If you specifically want to create an MDC dimension for a characteristic with a low cardinality, you can define this characteristic as a line item dimension in the InfoCube. This differs from the norm that line item dimensions contain characteristics with a very high cardinality. However, this has the advantage for multidimensional clustering that the fact table contains the SID values of the characteristic, in place of the dimension keys, and the database query can be restricted to these SID values.
You cannot select more than three dimensions, including the time dimension.
Assign sequence numbers, using the following criteria:
Sort the dimensions according to how often they occur in queries (assign the lowest sequence number to the InfoObject that occurs most often in queries).
Sort the dimensions according to selectivity (assign the lowest sequence number to the dimension with the most different data records).
Note: At least one block is created for each value combination in the MDC dimension. This memory area is reserved independently of the number of data records that have the same value combination in the MDC dimension. If there is not a sufficient number of data records with the same value combinations to completely fill a block, the free memory remains unused. This is so that data records with a different value combination in the MDC dimension cannot be written to the block.
If for each combination that exists in the InfoCube, only a few data records exist in the selected MDC dimension, most blocks have unused free memory. This means that the fact tables use an unnecessarily large amount of memory space. Performance of table queries also deteriorates, as many pages with not much information must be read.
Example
The size of a block depends on the PAGESIZE and the EXTENTSIZE of the tablespace. The standard PAGESIZE of the fact-table tablespace with the assigned data class DFACT is 16K. Up to Release SAP BW 3.5, the default EXTENTSIZE value was 16. As of Release SAP NetWeaver 2004s the new default EXTENTSIZE value is 2.
With an EXTENTSIZE of 2 and a PAGESIZE of 16K the memory area is calculated as 2 x 16K = 32K, this is reserved for each block.
The width of a data record depends on the number of dimensions and the number of key figures in the InfoCube. A dimension key field uses 4 bytes and a decimal key figure uses 9 bytes. If, for example an InfoCube has 3 standard dimensions, 7 customer dimensions and 30 decimal key figures, a data record needs 10 x 4 bytes + 30 x 9 bytes = 310 bytes. In a 32K block, 32768 bytes / 310 bytes could write 105 data records.
If the time characteristic calendar month (0CALMONTH) and a customer dimension are selected as the MDC dimension for this InfoCube, at least 100 data records should exist for each InfoPackage, for each calendar month and for each dimension key of the customer dimension. This allows optimal use of the memory space in the F fact table. In the E fact table, this is valid for each calendar month and each dimension key of the customer dimension,dimension contains a characteristic whose value already uniquely determines the values of all other characteristics from a business-orientated viewpoint, then the dimension is named after this characteristic.
The customer dimension could, for example, be made up of the customer number, the customer group and the levels of the customer hierarchy.
The sales dimension could contain the characteristics sales person, sales group and sales office.
The time dimension could be given using the characteristics day (in the form YYYYMMDD), week (in the form YYYY.WW), month (in the form YYYY.MM), year (in the form YYYY) and period (in the form YYYY.PPP).
Use
When defining an InfoCube, characteristics for dimensions are grouped together to enable them to be stored in a star schema table (dimension table). The aforementioned business-orientated grouping can be the basis for this. With the aid of a simple foreign key dependency, dimensions are linked to one of the key fields of the fact table.
When you create an InfoCube, the dimensions data package, time and unit are already defined by default. The data package dimension contains technical characteristics. Time characteristics and units are automatically assigned to the corresponding dimensions. When you activate the InfoCube, only those dimensions that contain InfoObjects are activated.
From a technical viewpoint several characteristic values are mapped to an abstract dimension key (DIM ID), to which the values in the fact table refer. The characteristics chosen for an InfoCube are divided up among InfoCube-specific dimensions when creating the InfoCube.
Also refer to the following for specific cases arising when defining dimensions:
Line Item and High Cardinality
The methods for setting and getting data from a named range use the separation between the description of the range and the data itself. Note that the sequence must be observed both in the range description (structure soi_range_list ) and in the data (structure soi_generic_table ). This means that you must list all data from the first range before you can insert data into the second range.
Structure soi_range_list
Field
Type
Description
name
C
Name of the range
rows
C
Number of rows
columns
C
Number of columns
code
C
Function in the range:
SPREADSHEET->SPREADSHEET_CLEAR : Deletes range
SPREADSHEET->SPREADSHEET_COLUMNSHIDE : Hides columns
SPREADSHEET->SPREADSHEET_ROWSHIDE : Hides rows
SPREADSHEET->SPREADSHEET_PROTECT : Range is protected
SPREADSHEET->SPREADSHEET_UNPROTECT : Range is not protected
SPREADSHEET->SPREADSHEET_COLUMNSSHOW : Columns are displayed.
SPREADSHEET->SPREADSHEET_ROWSSHOW : Rows are displayed.
SPREADSHEET->SPREADSHEET_INSERTALL : The entire table is inserted, regardless of the size of the area
SPREADSHEET->SPREADSHEET_NEWRANGE : Creates a new range
The name identifies the range in the worksheet. This is, in effect, the key with which you always access the range. The size of the range is always given in columns and rows.
Some functions allow you to access a specific area in a worksheet. You can see from the table which functions are implemented.
Description of Data Type soi_generic_table
In this table, you can save data from the range and use the Data Provider to transfer it to or retrieve it from the frontend. The data is transferred directly as a string with no type information.
Structure soi_generic_table
Field
Type
Description
row
C(4)
Row
column
C(4)
Column
value
C(256)
Value
The sequence of the data must correspond to the sequence of the range description, for example, range1 before range2 . The data table must then contain the data for the ranges in the sequence range1 range2 .
Description of Data Type soi_format_table
Use this table to specify the format of a range. The format consists of various attributes, all of which can be set in a single line. Each variable attribute corresponds to a column of the structure.
To create a work area for this table, use the structure soi_format_item as a reference.
The entry "-1" always indicates that the existing attribute value for the range should not be changed.
Structure soi_format_table
Field
Type
Description
name
C(256)
Name of the range
front
I
Font color (see color palette)
back
I
Background color (see color palette)
font
C(256)
Name of the font family. The following values are permitted:
'Arial'
'Courier New'
'Times New Roman'
size
I
Font size
'-1' : Unchanged
bold
I
'1' : Bold
'0' : Normal
'-1' : Unchanged
italic
I
'1' : Italic
'0' : Normal
'-1' : Unchanged
align
I
Alignment:
'-1' : Unchanged
'0' : Right-justified
'1' : Centered
'2' : Left-justified
frametype
I
Control byte for setting the frame
'-1' : Unchanged
framecolor
I
Frame color (see color palette)
'-1' : Unchanged
currency
C(3)
ISO standard currency code
number
I
Specifies the format of a cell in a range.
1: Display as a simple number
2: Scientific display
3: Display as a percentage
The control byte type contains the following bits. If a bit is set, its corresponding line is drawn. You can set the thickness of the line to one of four levels using bits 6 and 7.
Bit
Description
0
Sets the left margin
1
Sets the top margin
2
Sets the bottom margin
3
Sets the right margin
4
Horizontal line
5
Sets the left margin
6
Thickness
7
Thickness
Description of Data Type soi_full_range_table
Each line of a table with the type soi_full_range_table specifies the full definition of a range. The individual lines have the data type soi_full_range_item .
Structure soi_full_range_table
Field
Type
Description
name
C(128)
Name of the range
top
I
Top row of the range
left
I
Leftmost column of the range
rows
I
Number of rows in the range
columns
I
Number of columns in the range
sheets
C(128)
Worksheet on which the range is defined
Description of Data Type soi_cell_table
Each line of a table with the type soi_cell_table specifies the attributes of a range of cells. However, no range name is used. Instead, the cell area is defined by its starting position and the number of rows and columns it contains.The individual lines have the data type soi_cell_item .
Structure soi_cell_table
Field
Type
Description
top
I
Top row of the range
left
I
Leftmost column of the range
rows
I
Number of rows in the range
columns
I
Number of columns in the range
front
I
Font color (see color palette)
back
I
Background color (see color palette)
font
C(256)
Font. The following are permitted:
Arial
Courier New
Times Roman
size
I
Font size
Use -1 if the font size is to remain unchanged.
bold
I
'1' : Bold
'0' : Normal
'-1' : Unchanged
italic
I
'1' : Italic
'0' : Normal
'-1' : Unchanged
align
I
Alignment:
'-1' : Unchanged
'0' : Right-justified
'1' : Centered
'2' : Left-justified
frametype
I
Control byte for setting the frame
'-1' : Unchanged
framecolor
I
Frame color (see color palette)
'-1' : Unchanged
currency
C(3)
ISO standard currency code
number
I
Specifies the format of a cell in a range.
1: Display as a simple number
2: Scientific display
3: Display as a percentage
decimals
I
Number of decimal places
input
I
'0' : Input off
'1' : Input on
Description of Data Type soi_dimension_table
You can use an internal table with this type to identify a range by specifying the coordinates of its top left-hand corner, its length, and its width. The lines of soi_dimension_table have the line type soi_dimension_item .
Structure soi_dimension_item
Field
Type
Decription
top
I
Topmost row of the range
left
I
Leftmost column of the range
rows
I
Number of rows
columns
I
Number of columns
Term
Definition
Board
A tabbed area in the workspace used to manipulate the model and its elements: Design board, Layout board and Source board.
Characteristic
A type of InfoObject in SAP BI systems that provides a classification such as company code, product, customer group, fiscal year, period, or region. Related to the OLAP-standard term dimension.
Component
A reusable model element, such as a UI component or a data service.
Cube
A set of data organized as a multidimensional structure defined according to dimensions and measures.
Related SAP BI terms include InfoCube and query.
Data binding
A connection between two UI components (or between a web service and a UI component) that channels identical data from the output port of one UI component to the input port of the other UI component.
Data flow
The means by which data is channeled between a data service and connected UI components, or between two UI components whose connection was changed from Data binding to Data flow.
Data mapping
Connection between two model elements, describing, for example, the data that is input to an element or the fields that are output from another element.
Data service
Any function call, business object or query imported into the model. At runtime, the data service is called and returns results.
Data store
A central data container where data of a model can be temporarily stored for future use.
Dimension
In OLAP-standard systems:
A collection of similar data which, together with other such collections, forms the structure of a cube. Typical dimensions include time, product, and geography. Each dimension may be organized into a basic parent-child hierarchy or, if supported by the data source, a hierarchy of levels. For example, a geography dimension might include levels for continent, country, state, and city.
The related term in SAP BI systems is characteristic.
In SAP BI systems:
A grouping of those evaluation groups (characteristics) that belong together under a common superordinate term.
With the definition of an InfoCube, characteristics are grouped together into dimensions in order to store them in a star schema table (dimension table).
Element
A general term indicating any item used to create a model, including: components, connectors and operators.
Enterprise service
A Web service defined to perform functions of an SAP system. Web services are published to and stored within a repository.
Field
An element of a table that contains a single piece of data. Fields are organized into rows, which contain all the data relevant for one specific entry in the table. In some databases, field is a synonym for column.
Filter
A set of criteria that restricts the set of records returned as the result of a query. With filters, you define which subset of data appears in the result set.
Hierarchy
A logical tree structure that organizes the members of a dimension into a parent-child relationship. If supported by the data source, the hierarchy consists of levels, where the top level is an aggregate of all members and each subsequent level has zero or more child members.
InfoArea
An element for grouping meta-objects in the Business Information Warehouse. Each InfoProvider is assigned to an InfoArea. The resulting hierarchy is displayed in the Administrator Workbench.
InfoCube
An SAP BI system that consists of a quantity of relational tables created according to the star schema: a large fact table in the center, with several dimension tables surrounding it. It provides a self-contained dataset which can be used for analysis and reporting.
Similar to the OLAP-standard term cube.
InfoObject
A business evaluation object (for example, customer or quantity) in SAP BI systems. Types of InfoObjects include characteristics, key figures, units, time characteristics, and technical characteristics (such as request numbers).
JDBC
Java Database Connectivity, which provides an API that lets you access relational databases using the Java programming language. This enables connectivity to a wide range of SQL databases, and also provides access to tabular data sources such as spreadsheets or flat files. The BI JDBC Connector accesses data from JDBC-compliant systems.
Join
A relationship between two tables that produces a result set that combines their contents. You create a join by indicating how selected fields in one table are related to selected fields in the other table.
Key figure
A value or quantity in SAP BI systems. Related to the OLAP-standard term measure. You may also define calculated key figures, which are derived using a formula.
Layer
A collection of UI elements that are all visible at the same time at runtime.
Level
A set of nodes (members) in a tree hierarchy in supporting data sources that are at the same distance from the root of the tree. For example, in a geography hierarchy, the top level might be all places, the second level might be continents, the third level might be countries, and the fourth level might be cities.
MDX
Multidimensional Expressions, a query language used to retrieve and manipulate multidimensional data.
Measure
One category of values usually numeric used to define a cube. These values are derived from one or more columns in the cube's fact table and are the basis for aggregation and analysis.
Related SAP BI terms include key figure and structure element.
Member
An element of a dimension that represents one or more occurrences of data. A member can be unique (it occurs only once) or non-unique (it may occur more than once in its dimension). For example, in a geography dimension that includes cities in the US, the member Portland could be non-unique, since there is a city called Portland in the state of Oregon and in the state of Maine.
In SAP BI systems, members are referred to as instances of characteristics.
Model
An object created in Storyboard. Models may contain packages, pages, iViews and any other model elements.
Multidimensional data
Data in dimensional models suitable for business analytics. In this documentation, we use the term multidimensional data synonymously with OLAP data.
Navigation line
A connection that provides event annotation, running between model layers. The source element raises the event that can be handled by the connected element. By default, a navigation line is curved.
ODBO
OLE DB for OLAP Microsofts set of objects and interfaces that extend the ability of OLE DB to provide access to multidimensional data sources on the Windows platform. Providers of OLAP data can implement the interfaces described with OLE DB for OLAP to allow all OLAP clients to access their data. The BI ODBO Connector accesses data from ODBO-compliant systems.
OLAP
Online analytical processing a system of organizing data in a multidimensional model that is suitable for decision support. SAP BI systems are OLAP systems.
Operation
A functionality provided by a Web service.
Operator
A mechanism used to manipulate data returned from the data service before it is displayed in the iView.
Package
A high-level container; it can contain any number of pages, iViews or other packages.
Port
A defined point of interface into and out of a component.
Query
In SAP BI systems, a collection of selected characteristics and key figures (InfoObjects) used together to analyze the data of an InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you like for each InfoProvider.
Query view
In SAP BI systems, a view of a query after navigation, saved in an InfoCube. You can use this saved query view as a basis for data analysis and reporting.
Relational database
A repository for typically large amounts of information, structured in accordance with the relational model, in tables with columns. A relational database is created and administered by a relational database management system (RDBMS).
Row
A set of fields within a table that contains the data for one specific entry in the table. Each row in a given table has the same structure, predefined for a particular table. In some databases, row is a synonym for record.
SAP Query
A component that allows you to create custom reports without any ABAP programming knowledge. The BI SAP Query Connector uses SAP Query to access data from such SAP operational applications.
Storyboard
The Visual Composer client from which you design models.
Table
A set of rows, also known as a relation. The table is the central object of the relational model.
Task panel
A work area of the Visual Composer Storyboard desktop that displays a specific set of tools for building a model.
Toolbar
The horizontal row of buttons under the main menu (main toolbar) or the vertical row of buttons in the task panel (task-panel toolbar).
Toolbox
A set of board-specific tools that assist in performing tasks in the Visual Composer workspace.
Value help
The offering, typically in a pop-up dialog box, of possible valid values for an input field. Also known as input help, selection help, or F4 help.
Web service
An interface between two or more software applications that is implemented with the industry standards SOAP, WSDL and UDDI.
Workspace
The main grid area of Visual Composer that displays the model as it is built and modified. The workspace consists of boards.
XMLA
XML for Analysis, an XML-messaging-based protocol specified by Microsoft for exchanging analytical data between client applications and servers (for example, OLAP providers) using HTTP and SOAP as a service on the Web. The BI XMLA Connector accesses data from XMLA-compliant systems.
Clustering allows you to save sorted data records in the fact table of an InfoCube. Data records with the same dimension keys are saved in the same extents (related database storage unit). This means that same data records are not spread across a large memory area and thereby reduces the number of extents that the system has to read when it accesses tables. This greatly accelerates read, write and delete access to the fact table.
Prerequisites
Currently the function is only supported by the database platform DB2 for Linux, UNIX, and Windows. You can use partitioning to improve the performance of other databases. For more information, see Partitioning.
Features
Two types of clustering are available: Index clustering and multidimensional clustering (MDC).
Index Clustering
Index clustering organizes the data records of a fact table according to the sort sequence of an index. Organization is linear and corresponds to the values of the index field.
If a data record cannot be inserted in accordance with the sort sequence because the relevant extent is already full, the data record is inserted into an empty extent at the end of the table. For this reason, the system cannot guarantee that the sort sequence is always correct, particularly if you perform many insert and delete operations. Reorganizing the table restores the sort sequence and frees up memory space that is no longer required.
The clustering index of an F fact table is, by default, the secondary index in the time dimension. The clustering index of an E fact table is, by default, the acting primary index (P index).
As of release SAP BW 2.0, index clustering is standard for all InfoCubes and aggregates.
Multidimensional Clustering (MDC)
Multidimensional clustering organizes the data records of a fact table in accordance with one or more fields that you define freely. The selected fields are also marked as MDC dimensions. Only data records that have the same values in the MDC dimensions are saved in an extent. In the context of MDC, an extent is called a block. The system can always guarantee that the sort sequence is correct. Reorganizing the table is not necessary, even with many insert and delete operations.
Block indexes from within the database, instead of the default secondary indexes, are created for the selected fields. Block indexes link to extents instead of data record numbers and are therefore much smaller. They save memory space and the system can search through them more quickly. This accelerates table requests that are restricted to these fields.
You can select the key fields of the time dimension or any customer-defined dimensions of an InfoCube as an MDC dimension. You cannot select the key field of the package dimension; it is automatically added to the MDC dimensions in the F fact table.
You can also select a time characteristic instead of the time dimension. In this case, the fact table has an extra field. This contains the SID values of the time characteristic. Currently only the time characteristics Calendar Month (0CALMONTH) and Fiscal Year/Period (0FISCPER) are supported. The time characteristic must be contained in the InfoCube. If you select the Fiscal Year/Period (0FISCPER) characteristic, a constant must be set for the Fiscal Year Variant (0FISCVARNT) characteristic.
Clustering is applied to all the aggregates of the InfoCube. If an aggregate does not contain an MDC dimension of the InfoCube, or if all the InfoObjects of an MDC dimension are created as line item dimensions in the aggregate, the aggregates are clustered using the remaining MDC dimensions. Index clustering is used for the aggregate if the aggregate does not contain any MDC dimensions of the InfoCube, or if it only contains MDC dimensions.
Multidimensional clustering was introduced in Release SAP NetWeaver 2004s and can be set up separately for each InfoCube.
For procedures, see Definition of Clustering.
Screen capture input to SAP Business Graphics must adhere to certain format rules in order to be recognized correctly.
SAP Business Graphics assumes that your screen data resembles the basic SAP table structure. This structure is somewhat flexible, but the table must obey the format rules listed in this section.
Restrictions on the Format of the Data
If you use the screen capture facility to input graphics data, the input table can contain either a single list of values, or rows and columns. If the data is a single list, you can include the values themselves and labels for each value. If the data has rows and columns, you can include a label for each row, a label for each column, and the table values themselves.
You cannot use the screen capture facility to input data in multiple tables. If you want to graph data occurring in multiple tables, you must write the input values to a file using ABAP programming tools. See SAP Graphics: Programming Interfaces for more information.
Format Rules for Numerical Values
Numerical values must obey the following rules:
Within a numerical value, the screen capture recognizes only the minus sign (hyphen), the comma, and the decimal point (period) as legitimate punctuation. Exponential notation and other variations are not recognized.
Note that the functions of the period and the comma in the English system are exactly opposite to their functions in some European systems. If your numbers are not being interpreted correctly, check with the system administrator to determine how these characters should be used.
The minus sign must occur after the number, with no intervening spaces.
All numbers in a row must be separated by spaces.
A column of numbers is right-justified and identified by the position of its right-most character. Each number belonging to this column must have its right-most character in the correct position.
If you have values partially or entirely out of alignment with the given right-most character position, they will not be interpreted as belonging to the proper column. In most cases, the screen capture program assumes these are values for an entirely new column.
You may leave out values for a given row or column.
Format Rules for Text Strings
You can include labels in the table to name the rows and columns. You can also provide a title for the set of rows, for the set of columns, and for the graph as a whole.
SAP Business Graphics does not accept more than 32 elements per dimension. As a result, you cannot have more than 32 rows or 32 columns in your table.
Any string of characters not identifiable as a number is assumed to be a label. Labels may occur at the beginnings of a row, at the head of a column, as a title for the rows or columns, or as the graph main title. A non-numeric item placed in among the data values is ignored by the graphics program.
A legitimate number occurring where a label should be is interpreted as a number. If you want to use labels that look like numbers, you must modify them to contain at least one non-numeric character.
Placement of labels for row-names or column-names:
Row-names can occur only at the beginning (left side) of a row.
Column-names should line up above the columns they are heading, but do not necessarily need to begin in the same column. They should be separated by at least two spaces.
If you don't adhere to these requirements, the screen capture program attempts to pick out the labels anyway. However, the results may not be what you expect. (Check the selection bars in the Selection view to see if your headers were correctly identified.)
Placement of titles for rows or columns as a set:
The title for the rows as a set should be placed directly above the column of row-names.
The title for the columns as a set should occur directly above the first of the column-names, and begin in exactly the same position.
The main title for the graph should occur in the very first line of the highlighted area. If you have more text there than just the title, the screen capture program attempts to pick out the string in the center of the line. The longest string in the center of the line separated from other text by double spaces is assumed to be the title.
The maximum length for a text string cannot be specified exactly since this depends on the size of your window, the resolution of your monitor, and other factors.
Many strings too long for a small window are displayed correctly when you enlarge the window to full-screen size. In general, you must experiment to find the optimal length for text strings. -
Cube with different reports data
Hi
We have 3 different Reports based on a Multi which has only one Infocube.
We have new design policy that any New different report that needs to be created should be based only on this Multi and all data should be loaded only into this only infocube on which this Multi is based.
So for the existing 3 reports,we have three different database views in source database.Fullload will be done from source every weekend(previous week's request will be deleted every week) of snapshot data into three different DSOs from these three different datasources.(Its new policy that every report should have its own DSO ).All these 3 DSOs should be connected to only one cube on which our reporting Multiprovider is based.So from these 3 DSOs,data will be loaded into cube in fullload every weekend(previous week's request will be deleted)
Now my question is:
1.when all the data is going to cube from three different views and DSOs(with different keyfigures but some same characteristics in 3 DSOs),how can our 3 different reports pick data that is relevant for it when all data is pooled together in one big cube?Doesnot aggregation happens?
(When a report is run,does OLAP processor goes into cube and picks only those keyfigures and characteristics in cube thats relevant for that report and by that way,avoids other data??)
2.I need to create one new report.For this I need to create one new view and one new DSO.So,data will be loaded from view to DSO and this DSO will be connected to existing cube(new dataflow until cube from source view).But our cube doesnot contain one keyfigure.It contains all other characteristics and keyfigures from DSO.
a)How can I add this new keyfigure from new DSO to cube without disturbing existing data in cube.I donot need to load historical data for this new keyfigure and new report.
b)I am going to transport this from development.So what care do I need to take while transporting changes to Production cube which contains lots of data and many reports running on it?
Thanks.*1.when all the data is going to cube from three different views and DSOs(with different keyfigures but some same characteristics in 3 DSOs),how can our 3 different reports pick data that is relevant for it when all data is pooled together in one big cube?Doesnot aggregation happens?
(When a report is run,does OLAP processor goes into cube and picks only those keyfigures and characteristics in cube thats relevant for that report and by that way,avoids other data??)*
It will depend on what Key Figures you are displaying in your report. If a KF is coming from only 2 DSOs, data from those 2 DSOs will be displayed. And you are right in saying that OLAP processor will pick only releavnt KFs and Characteristics but it will not filter based on characteristic value e.g. if a characteristis is coming only from DSO 1 and not from DSO2, but KF is coming from both, so for the data in DSO 2 that characteristic will be displayed as #. If you want to filter data, you can put filters in the report.
Another good option can be to store the DSO name as a characeteristic in your cube, it might be helpful if you want to make a reprot based on data from a particular DSO, then you can put the filter based on DSO name.
*2.I need to create one new report.For this I need to create one new view and one new DSO.So,data will be loaded from view to DSO and this DSO will be connected to existing cube(new dataflow until cube from source view).But our cube doesnot contain one keyfigure.It contains all other characteristics and keyfigures from DSO.
a)How can I add this new keyfigure from new DSO to cube without disturbing existing data in cube.I donot need to load historical data for this new keyfigure and new report.
b)I am going to transport this from development.So what care do I need to take while transporting changes to Production cube which contains lots of data and many reports running on it?*
You are adding a new KF which is coming only from new DSO, so you do not need to worry about a lot of things, you can move your changes to procudtion and load data from this new DSO. Data which is already there in the cube will not be impacted.
Regards,
Gaurav -
I recently started using an iPad. I up loaded several apps. Evernote, cloudon, Goodreader, Drop Box and lots of others.
It crashes when I down load pictures and then try to use them. Converting a jpg to a pdf usually triggers a crash.
Is there a "hitch" in my "giddy up?"
Help.
Process: iPhoto [345]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.4.2 (9.4.2)
Build Info: iPhotoProject-710042000000000~2
App Item ID: 408981381
App External ID: 11723545
Code Type: X86 (Native)
Parent Process: launchd [183]
Date/Time: 2013-04-26 13:53:18.305 -0700
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report: 405039 sec
Crashes Since Last Report: 7
Per-App Interval Since Last Report: 318933 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: 5073147D-D214-4BD3-B7FA-9A9E6A158ABA
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000c8fc0000
VM Regions Near 0xc8fc0000:
CG backing stores 00000000c8ea6000-00000000c8f19000 [ 460K] rw-/rw- SM=SHM
--> CG backing stores 00000000c8fc0000-00000000c92f7000 [ 3292K] r--/rw- SM=SHM
Submap 00000000ffff0000-00000000ffff2000 r-x/r-x process-only submap
Application Specific Information:
objc[345]: garbage collection is OFF
Performing @selector(doSaveAsPDF:) from sender NSMenuItem 0x6da8c240
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreGraphics 0x93976aec blt_pattern_blend_XXXX32 + 686
1 com.apple.CoreGraphics 0x93976def blt_bitmap_blend_AXXX32 + 105
2 com.apple.CoreGraphics 0x9355894c argb32_mark_pixelshape + 19824
3 com.apple.CoreGraphics 0x93485293 argb32_mark + 279
4 com.apple.CoreGraphics 0x9349c915 argb32_image + 1037
5 libRIP.A.dylib 0x90afec75 ripd_Mark + 279
6 libRIP.A.dylib 0x90afcc67 ripl_BltImage + 1368
7 libRIP.A.dylib 0x90afc497 ripc_RenderImage + 269
8 libRIP.A.dylib 0x90b08a8c ripc_DrawImages + 6467
9 com.apple.CoreGraphics 0x935593be CGContextDrawImages + 239
10 com.apple.coreui 0x94680a79 CUIPenCG::DrawImages(void*, CGRect const*, CGImage**, CGRect const*, unsigned long) + 45
11 com.apple.coreui 0x94671fc5 CUIRenderer::DrawWindowFrameDark(CUIDescriptor const*) + 4531
12 com.apple.coreui 0x9465ce0d CUIRenderer::Draw(CGRect, CGContext*, __CFDictionary const*, __CFDictionary const**) + 5701
13 com.apple.coreui 0x9467dde5 CUIDraw + 206
14 com.apple.AppKit 0x912a52e4 _NSDrawThemeBackground + 1429
15 com.apple.AppKit 0x9145edeb -[NSThemeFrame _drawUnifiedToolbar:] + 874
16 com.apple.AppKit 0x9145e7f3 -[NSThemeFrame _drawTitleBar:] + 673
17 com.apple.AppKit 0x912a11cf -[NSThemeFrame _drawFrameInterior:clip:] + 125
18 com.apple.AppKit 0x912a0dd9 -[NSThemeFrame drawFrame:] + 119
19 com.apple.AppKit 0x9145e515 -[NSFrameView drawRect:] + 765
20 com.apple.AppKit 0x9145dc5f -[NSThemeFrame drawRect:] + 107
21 com.apple.AppKit 0x9126f6c9 -[NSView _drawRect:clip:] + 3717
22 com.apple.AppKit 0x9129eae6 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1958
23 com.apple.AppKit 0x9126d026 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 708
24 com.apple.AppKit 0x9126c627 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 259
25 com.apple.AppKit 0x91267caa -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4817
26 com.apple.AppKit 0x91260bd9 -[NSView displayIfNeeded] + 1365
27 com.apple.AppKit 0x9138081b -[NSThemeFrame handleSetFrameCommonRedisplay] + 233
28 com.apple.AppKit 0x913220b8 -[NSWindow _setFrameCommon:display:stashSize:] + 2253
29 com.apple.AppKit 0x913217e6 -[NSWindow setFrame:display:] + 71
30 com.apple.AppKit 0x913c5049 -[NSWindow _setFrameAfterMove:] + 496
31 com.apple.AppKit 0x913c4e3f -[NSWindow _windowMovedToRect:] + 261
32 com.apple.AppKit 0x9195152d -[NSWindow _getPositionFromServer] + 100
33 com.apple.AppKit 0x919542a8 -[NSWindow _initFromGlobalWindow:inRect:styleMask:] + 350
34 com.apple.RemoteViewServices 0x94640ff9 -[NSRemoteWindowController _remoteHostDidGrantRights:] + 335
35 com.apple.RemoteViewServices 0x946409a4 __58-[NSRemoteWindowController _handleReplySetupSharedWindow:]_block_invoke_0 + 43
36 com.apple.CoreGraphics 0x935c740b _WindowRightsGrantOfferedNotificationHandler + 678
37 com.apple.CoreGraphics 0x93400a3b CGSPostLocalNotification + 218
38 com.apple.CoreGraphics 0x934cdcfd notifyDatagramHandler + 265
39 com.apple.CoreGraphics 0x934cda25 CGSDispatchDatagramsFromStream + 316
40 com.apple.CoreGraphics 0x934cd594 snarfEvents + 481
41 com.apple.CoreGraphics 0x934cd247 CGSGetNextEventRecordInternal + 127
42 com.apple.CoreGraphics 0x93520180 CGEventCreateNextEvent + 40
43 com.apple.HIToolbox 0x9b5a744e _ZL38PullEventsFromWindowServerOnConnectionjh + 69
44 com.apple.CoreFoundation 0x9585ad0a __CFMachPortPerform + 346
45 com.apple.CoreFoundation 0x9585ab91 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 49
46 com.apple.CoreFoundation 0x9585a7bb __CFRunLoopDoSource1 + 155
47 com.apple.CoreFoundation 0x95893e01 __CFRunLoopRun + 2193
48 com.apple.CoreFoundation 0x958931dc CFRunLoopRunSpecific + 332
49 com.apple.CoreFoundation 0x958a3f01 CFRunLoopRun + 129
50 com.apple.RemoteViewServices 0x9463b7c8 -[NSRemoteSavePanel runModal] + 322
51 com.apple.RemoteViewServices 0x9463ef05 -[NSRemoteSavePanel runModalForDirectory:file:types:] + 110
52 com.apple.RemoteViewServices 0x9463ec94 -[NSRemoteSavePanel runModalForDirectory:file:] + 55
53 com.apple.print.framework.Print.Private 0x1990afa3 AskUserForFile + 420
54 com.apple.print.framework.Print.Private 0x1991977d 0x198f7000 + 141181
55 com.apple.print.framework.Print.Private 0x1991ea91 0x198f7000 + 162449
56 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
57 com.apple.AppKit 0x91329663 -[NSApplication sendAction:to:from:] + 232
58 com.apple.AppKit 0x9141ccaf -[NSMenuItem _corePerformAction] + 536
59 com.apple.AppKit 0x9141c92c -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 171
60 com.apple.AppKit 0x9141bfb5 -[NSMenu _performActionWithHighlightingForItemAtIndex:sendAccessibilityNotification:] + 79
61 com.apple.AppKit 0x916f7ef7 -[NSMenu performActionForItemAtIndex:] + 65
62 com.apple.AppKit 0x916f7f2a -[NSMenu _internalPerformActionForItemAtIndex:] + 45
63 com.apple.AppKit 0x916fc15b -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 106
64 com.apple.AppKit 0x91562670 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 172
65 com.apple.AppKit 0x91392246 NSSLMMenuEventHandler + 452
66 com.apple.HIToolbox 0x9b71cc0c _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
67 com.apple.HIToolbox 0x9b598313 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1602
68 com.apple.HIToolbox 0x9b597790 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 482
69 com.apple.HIToolbox 0x9b5ac571 SendEventToEventTarget + 76
70 com.apple.HIToolbox 0x9b71d0d0 _ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 482
71 com.apple.HIToolbox 0x9b71d13a SendMenuCommandWithContextAndModifiers + 70
72 com.apple.HIToolbox 0x9b78898d SendMenuItemSelectedEvent + 275
73 com.apple.HIToolbox 0x9b5e8d79 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 129
74 com.apple.HIToolbox 0x9b778752 _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttmS4_S4_PK10__CFStringPP13 OpaqueMenuRefPt + 1898
75 com.apple.HIToolbox 0x9b778a20 _HandlePopUpMenuSelection7 + 639
76 com.apple.AppKit 0x91565aa2 _NSSLMPopUpCarbonMenu3 + 4532
77 com.apple.AppKit 0x9198ab4c _NSPopUpCarbonMenu3 + 107
78 com.apple.AppKit 0x91563754 -[NSCarbonMenuImpl popUpMenu:atLocation:width:forView:withSelectedItem:withFont:withFlags:withOpti ons:] + 425
79 com.apple.AppKit 0x91787b78 -[NSPopUpButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 610
80 com.apple.AppKit 0x91327243 -[NSControl mouseDown:] + 943
81 com.apple.AppKit 0x912f0dcd -[NSWindow sendEvent:] + 7533
82 com.apple.AppKit 0x91289f77 -[NSApplication sendEvent:] + 4788
83 com.apple.iLifeKit 0x0201dc9b -[iLifeKit sendEvent:] + 55
84 com.apple.iPhoto 0x0012c344 0xac000 + 525124
85 com.apple.AppKit 0x914f1662 -[NSApplication _modalSession:sendEvent:] + 550
86 com.apple.AppKit 0x914f122c -[NSApplication _realDoModalLoop:peek:] + 638
87 com.apple.AppKit 0x914ec481 -[NSApplication _doModalLoop:peek:] + 69
88 com.apple.AppKit 0x914f0f08 -[NSApplication runModalForWindow:] + 258
89 com.apple.AppKit 0x91794a93 -[NSPrintPanel runModalWithPrintInfo:] + 621
90 com.apple.AppKit 0x917929ec -[NSConcretePrintOperation runOperation] + 333
91 com.apple.iPhoto 0x00363141 0xac000 + 2847041
92 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
93 com.apple.AppKit 0x91329663 -[NSApplication sendAction:to:from:] + 232
94 com.apple.AppKit 0x91329540 -[NSControl sendAction:to:] + 102
95 com.apple.AppKit 0x91329443 -[NSCell _sendActionFrom:] + 160
96 com.apple.AppKit 0x91328800 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 2295
97 com.apple.AppKit 0x913aba95 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 501
98 com.apple.AppKit 0x91327243 -[NSControl mouseDown:] + 943
99 com.apple.AppKit 0x912f0dcd -[NSWindow sendEvent:] + 7533
100 com.apple.AppKit 0x91289f77 -[NSApplication sendEvent:] + 4788
101 com.apple.iLifeKit 0x0201dc9b -[iLifeKit sendEvent:] + 55
102 com.apple.iPhoto 0x0012c344 0xac000 + 525124
103 com.apple.AppKit 0x9121bb21 -[NSApplication run] + 1007
104 com.apple.AppKit 0x914acac5 NSApplicationMain + 1054
105 com.apple.iPhoto 0x000bbc99 0xac000 + 64665
106 com.apple.iPhoto 0x000bb2e5 0xac000 + 62181
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9a596b5e __select_nocancel + 10
1 libdispatch.dylib 0x96b4ecbd _dispatch_mgr_invoke + 642
2 libdispatch.dylib 0x96b4d853 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.RedRock 0x023e748f -[RKAsyncImageRenderer _backgroundRenderThread:] + 173
7 com.apple.CoreFoundation 0x958fb1aa -[NSObject performSelector:] + 58
8 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
9 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
10 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
11 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
12 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
13 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
14 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
15 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
16 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
17 libsystem_c.dylib 0x994596de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9a595e12 __accept + 10
1 com.apple.iPhoto 0x004a424d 0xac000 + 4162125
2 com.apple.iPhoto 0x004ee651 0xac000 + 4466257
3 com.apple.iPhoto 0x004ee5be 0xac000 + 4466110
4 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
5 libsystem_c.dylib 0x994596de thread_start + 34
Thread 11:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9a596b42 __select + 10
1 com.apple.CoreFoundation 0x958e1e15 __CFSocketManager + 1557
2 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
3 libsystem_c.dylib 0x994596de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x9970fbe8 -[NSCondition wait] + 304
4 com.apple.iPhoto 0x000fda64 0xac000 + 334436
5 com.apple.iPhoto 0x000fd672 0xac000 + 333426
6 com.apple.CoreFoundation 0x958f5a9d __invoking___ + 29
7 com.apple.CoreFoundation 0x958f59d9 -[NSInvocation invoke] + 137
8 com.apple.RedRock 0x0240385b -[RKInvoker _invokeTarget:] + 33
9 com.apple.RedRock 0x024145f4 -[RKInvoker _invokeTargetWithPool:] + 68
10 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
11 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
12 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
13 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
14 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
15 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
16 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
17 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
18 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
19 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
20 libsystem_c.dylib 0x994596de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x9279e3a7 TSWaitOnConditionTimedRelative + 178
4 com.apple.CoreServices.CarbonCore 0x9279e11d TSWaitOnSemaphoreCommon + 490
5 com.apple.CoreServices.CarbonCore 0x9279df2e TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x9736a16a 0x96d7d000 + 6213994
7 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
8 libsystem_c.dylib 0x994596de thread_start + 34
Thread 14:: CVDisplayLink
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreVideo 0x97f120cd CVDisplayLink::runIOThread() + 945
4 com.apple.CoreVideo 0x97f11d05 _ZL13startIOThreadPv + 160
5 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
6 libsystem_c.dylib 0x994596de thread_start + 34
Thread 15:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9940182a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x9748c467 0x96d7d000 + 7402599
4 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
5 libsystem_c.dylib 0x994596de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x99459f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x997403c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x997067d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x997066a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01dace12 -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01dabefa -[XTThread run:] + 412
8 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
9 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
11 libsystem_c.dylib 0x994596de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.iPhoto 0x005acdd1 0xac000 + 5246417
4 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
5 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
6 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
7 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
8 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
9 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
10 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
11 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
12 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
13 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
14 libsystem_c.dylib 0x994596de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.iPhoto 0x00175872 0xac000 + 825458
4 com.apple.CoreFoundation 0x958f5a9d __invoking___ + 29
5 com.apple.CoreFoundation 0x958f59d9 -[NSInvocation invoke] + 137
6 com.apple.RedRock 0x0240385b -[RKInvoker _invokeTarget:] + 33
7 com.apple.RedRock 0x024145f4 -[RKInvoker _invokeTargetWithPool:] + 68
8 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
9 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
10 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
11 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
12 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
13 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
14 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
15 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
16 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
17 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
18 libsystem_c.dylib 0x994596de thread_start + 34
Thread 19:: Dispatch queue: com.apple.root.default-priority
0 libsystem_kernel.dylib 0x9a594c76 semaphore_timedwait_trap + 10
1 libdispatch.dylib 0x96b50a55 _dispatch_semaphore_wait_slow + 274
2 libdispatch.dylib 0x96b50ab4 dispatch_semaphore_wait + 36
3 com.apple.RemoteViewServices 0x9463a725 __54-[NSRemoteSavePanel _runOrderingOperationWithContext:]_block_invoke_0345 + 79
4 libdispatch.dylib 0x96b4cfbd _dispatch_call_block_and_release + 15
5 libdispatch.dylib 0x96b4e01c _dispatch_worker_thread2 + 231
6 libsystem_c.dylib 0x99457b24 _pthread_wqthread + 346
7 libsystem_c.dylib 0x994596fe start_wqthread + 30
Thread 20:
0 libsystem_kernel.dylib 0x9a59702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x99457ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x994596fe start_wqthread + 30
Thread 21:
0 libsystem_kernel.dylib 0x9a59702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x99457ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x994596fe start_wqthread + 30
Thread 22:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.iPhoto 0x005acdd1 0xac000 + 5246417
4 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
5 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
6 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
7 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
8 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
9 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
10 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
11 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
12 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
13 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
14 libsystem_c.dylib 0x994596de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.iPhoto 0x00175872 0xac000 + 825458
4 com.apple.CoreFoundation 0x958f5a9d __invoking___ + 29
5 com.apple.CoreFoundation 0x958f59d9 -[NSInvocation invoke] + 137
6 com.apple.RedRock 0x0240385b -[RKInvoker _invokeTarget:] + 33
7 com.apple.RedRock 0x024145f4 -[RKInvoker _invokeTargetWithPool:] + 68
8 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
9 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
10 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
11 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
12 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
13 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
14 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
15 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
16 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
17 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
18 libsystem_c.dylib 0x994596de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x9a59683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x99459e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9940a42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.iPhoto 0x001bb758 0xac000 + 1111896
4 com.apple.CoreFoundation 0x958f5a9d __invoking___ + 29
5 com.apple.CoreFoundation 0x958f59d9 -[NSInvocation invoke] + 137
6 com.apple.RedRock 0x0240385b -[RKInvoker _invokeTarget:] + 33
7 com.apple.RedRock 0x024145f4 -[RKInvoker _invokeTargetWithPool:] + 68
8 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
9 com.apple.proxtcore 0x01db5df9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 167
10 com.apple.CoreFoundation 0x958f2d11 -[NSObject performSelector:withObject:] + 65
11 com.apple.proxtcore 0x01dae22c -[XTSubscription postMessage:] + 191
12 com.apple.proxtcore 0x01dadaef -[XTDistributor distributeMessage:] + 681
13 com.apple.proxtcore 0x01dad313 -[XTThread handleMessage:] + 515
14 com.apple.proxtcore 0x01dabf10 -[XTThread run:] + 434
15 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
16 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
17 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
18 libsystem_c.dylib 0x994596de thread_start + 34
Thread 25:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x9a596bb2 __semwait_signal + 10
1 libsystem_c.dylib 0x9940a7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x9940a558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x914646da -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x9970de25 -[NSThread main] + 45
5 com.apple.Foundation 0x9970ddd5 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x99455ed9 _pthread_start + 335
7 libsystem_c.dylib 0x994596de thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x9a59702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x99457ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x994596fe start_wqthread + 30
Thread 27:
0 libsystem_kernel.dylib 0x9a59702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x99457ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x994596fe start_wqthread + 30
Thread 28:
0 libsystem_kernel.dylib 0x9a59702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x99457ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x994596fe start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000540 ebx: 0x15675480 ecx: 0x00000150 edx: 0x00000004
edi: 0x0000ffff esi: 0xc8fc0000 ebp: 0xc009f508 esp: 0xc009f460
ss: 0x00000023 efl: 0x00010246 eip: 0x93976aec cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0xc8fc0000
Logical CPU: 0
Binary Images:
0xac000 - 0xd98feb com.apple.iPhoto (9.4.2 - 9.4.2) <3AC6405B-33E2-3184-9F20-4C9CC5256A3A> /Applications/iPhoto.app/Contents/MacOS/iPhoto
0xf2a000 - 0x100afe7 org.python.python (2.6.7 - 2.6.7) <61DBA92A-C39A-3A52-86F2-59CF9D310CB4> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
0x1056000 - 0x105efff com.apple.PhotoFoundation (1.0 - 10.17) <D48FDC95-21FC-328C-9F4F-89C28A260C2D> /Applications/iPhoto.app/Contents/Frameworks/PhotoFoundation.framework/Versions /A/PhotoFoundation
0x10cf000 - 0x12abffb com.apple.geode (1.5.3 - 270.7) <DFD97416-FD86-3AF1-BFF0-79A47DADE257> /Applications/iPhoto.app/Contents/Frameworks/Geode.framework/Versions/A/Geode
0x133a000 - 0x133fff7 com.apple.iLifePhotoStreamConfiguration (3.4 - 2.5) <65A74F18-5020-31EC-B7E9-EBC14E2D9CA1> /Applications/iPhoto.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fram ework/Versions/A/iLifePhotoStreamConfiguration
0x1347000 - 0x1376ff7 com.apple.iLifeAssetManagement (2.7 - 40.34) <2B65BA8A-2C25-360D-B50E-0A9EECA1CE57> /Applications/iPhoto.app/Contents/Frameworks/iLifeAssetManagement.framework/Ver sions/A/iLifeAssetManagement
0x139b000 - 0x13c2ff3 com.apple.iPhoto.Tessera (1.1 - 70.18) <F190FD9B-9CC9-3D4D-9744-113F7CA36097> /Applications/iPhoto.app/Contents/Frameworks/Tessera.framework/Versions/A/Tesse ra
0x13d6000 - 0x13faffb com.apple.iPhoto.Tellus (1.3 - 70.18) <768463A7-60B4-3D50-B36B-D6E5AFA43DC9> /Applications/iPhoto.app/Contents/Frameworks/Tellus.framework/Versions/A/Tellus
0x1411000 - 0x141cfff com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <86E53BF3-BCAD-36F9-999B-013E359EF079> /Applications/iPhoto.app/Contents/Frameworks/AccountConfigurationPlugin.framewo rk/Versions/A/AccountConfigurationPlugin
0x1427000 - 0x143cffb com.apple.iLifeFaceRecognition (1.0 - 30.11) <4A781CBF-9764-3531-91E0-94C5B4DFCFDF> /Applications/iPhoto.app/Contents/Frameworks/iLifeFaceRecognition.framework/Ver sions/A/iLifeFaceRecognition
0x1448000 - 0x1474ffb com.apple.DiscRecordingUI (6.0.4 - 6040.4.1) <F3EDDD79-611F-3ECC-9B78-0AB8BAC0D446> /System/Library/Frameworks/DiscRecordingUI.framework/Versions/A/DiscRecordingUI
0x1490000 - 0x1492fff com.apple.ExceptionHandling (1.5 - 10) <6CA9446C-7EF9-35EE-BDF2-AA8D51E93E9E> /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x149b000 - 0x14a6ff7 com.apple.UpgradeChecker (9.2 - 9.2) <D34CC218-8200-34D7-816C-B747EE4BF5F7> /Applications/iPhoto.app/Contents/Frameworks/UpgradeChecker.framework/Versions/ A/UpgradeChecker
0x14b2000 - 0x184bff3 com.apple.iLifeSlideshow (3.1 - 1151.4) <B03978EF-A395-30D4-833B-7C474E1F5F12> /Applications/iPhoto.app/Contents/Frameworks/iLifeSlideshow.framework/Versions/ A/iLifeSlideshow
0x1948000 - 0x1bd9ff3 com.apple.iLifePageLayout (1.3 - 200.9) <067ACE80-5B73-39EE-850B-E392F6573AAC> /Applications/iPhoto.app/Contents/Frameworks/iLifePageLayout.framework/Versions /A/iLifePageLayout
0x1cb5000 - 0x1d4cff7 com.apple.MobileMe (13 - 1.0.4) <5E6C6DEC-1F48-358F-8117-40FAAEB8AFAD> /Applications/iPhoto.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mobi leMe
0x1da8000 - 0x1e10ff3 com.apple.proxtcore (1.4.1 - 250.56) <BBADA727-FB78-32AF-8D45-4498F68343A7> /Applications/iPhoto.app/Contents/Frameworks/ProXTCore.framework/Versions/A/Pro XTCore
0x1e52000 - 0x1f50ff7 com.apple.iLifeSQLAccess (1.7.1 - 60.5) <845C6292-8EC2-3B4A-8E2E-8D98986148C2> /Applications/iPhoto.app/Contents/Frameworks/iLifeSQLAccess.framework/Versions/ A/iLifeSQLAccess
0x1f99000 - 0x1fc4ffb com.apple.ProUtils (1.1 - 200.36) <E286BD1F-0BE8-3151-B758-89870AB4AC89> /Applications/iPhoto.app/Contents/Frameworks/ProUtils.framework/Versions/A/ProU tils
0x1fde000 - 0x2049fff com.apple.iLifeKit (1.3.1 - 156.11) <F93283F4-046D-3653-9607-8B0F850E6318> /Applications/iPhoto.app/Contents/Frameworks/iLifeKit.framework/Versions/A/iLif eKit
0x208e000 - 0x22b6ff7 com.apple.prokit (7.2.3 - 1823) <0FEDF2D7-F31A-36F2-91A9-C03877B0CB46> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x23c4000 - 0x28f0ffb com.apple.RedRock (1.9.4 - 310.33) <548258F5-3AE9-3AD4-B986-A9674D131164> /Applications/iPhoto.app/Contents/Frameworks/RedRock.framework/Versions/A/RedRo ck
0x2aee000 - 0x2b04ffb com.apple.AOSAccounts (1.0.2 - 1.0.71) <13763832-1B2B-32E8-95BC-C23A627E6DD4> /System/Library/PrivateFrameworks/AOSAccounts.framework/Versions/A/AOSAccounts
0x2b19000 - 0x2b53ff3 com.apple.Ubiquity (1.1 - 210.2) <F8426ABA-BB3F-3A48-BF4E-9A0F6C12634F> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
0x2b6e000 - 0x2b6eff6 com.apple.SafariDAVNotifier (1.1.1 - 1) <DE95A56E-E2C8-3D96-B628-4DC6FA6CDD39> /System/Library/PrivateFrameworks/BookmarkDAV.framework/Versions/A/Frameworks/S afariDAVNotifier.framework/Versions/A/SafariDAVNotifier
0x2b74000 - 0x2b95ff7 com.apple.ChunkingLibrary (1.0 - 127.2) <8C1C8488-71E4-3C13-AF75-95CF06C040A3> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/Chunking Library
0x2ba1000 - 0x2ba3fff com.apple.LibraryRepair (1.0 - 1) <8D2DE423-2226-395A-9D90-3C43911F8613> /System/Library/PrivateFrameworks/LibraryRepair.framework/Versions/A/LibraryRep air
0x2bab000 - 0x2c05fff com.apple.proapps.MIO (1.0.6 - 512) <8321DF77-4AD8-376B-9465-83F471AA61D2> /ApplicationsIt crashes when I down load pictures and then try to use them. Converting a jpg to a pdf usually triggers a crash.
Are you using the "Print to PDF" dialogue to convert your jpegs to pdf?
In addition to OT's test, you might also check, if using a different "Theme" for printing will avoid the crash:
14 com.apple.AppKit 0x912a52e4 _NSDrawThemeBackground + 1429
15 com.apple.AppKit 0x9145edeb -[NSThemeFrame
You crashlog shows, that iPhoto crashes, when trying to draw the "Print" theme background. There could be a problem wit the installed themes. Can you convert any jpegs to pdf, not only the jpegs downloaded from your iPad?
Léonie -
I am loading a cube from a cube. There is data which meets my info package selection criteria in the source cube but I get 0 records transferred, added to the cube. There is no delete in start routines.
Just before loading I have selectively deleted all records from the target cube so as to not disturb existing delta mechanism
The load I am making is full repair
Can someone assist
ThanksHi Akreddy
I am not sure "Repair full to Cube"...!
Still the following is my opninon abt your issue...
It seems there is some miss map ..Just one quick check in the DTP monitor in which step your getting 0 records . Is it Data package level or transformation level or routine level..
Identify the step where the transfered records is nullifying then dig through the step..or post the waning or message in this forum so that its pretty easier to get answered..
Hope its clear a little..!
Thanks
K M R
"Impossible Means I 'M Possible"
Winners Don't Do Different things,They Do things Differently...!.
>
akreddy wrote:
> I am loading a cube from a cube. There is data which meets my info package selection criteria in the source cube but I get 0 records transferred, added to the cube. There is no delete in start routines.
>
> Just before loading I have selectively deleted all records from the target cube so as to not disturb existing delta mechanism
>
> The load I am making is full repair
>
> Can someone assist
>
> Thanks
Edited by: K M R on Aug 16, 2010 2:01 PM -
How i said on the question. I tried to upgrade the ios on the phone and I was asked for my icloud user and password. I don’t remember these exactly and I tried several times with different options but unsuccessfully. I also forget my email used to configurate the phone. I have the phone box and the bill. I sent you an email with my problem and attachments with the box informations, the bill and the reset request. What to do? You said to me:
Your request comes from an unrecognized email domain. Apple accepts email requests only from email domains for Apple-authorized carriers.
Please re-submit your request using your official carrier domain.
but this email is authorized, what to do??
respectfully, BebaIf you have forgotten then these links are the only way to resolve
http://www.apple.com/support/appleid/
As long as you have owned the iPhone from new and your Apple id is the one used to activate when new
OR have you recently purchased the iPhone secondhand ? -
Can i use one interface to load data into 2 different tables
Hi Folks,
Can i use one interface to load data into 2 different tables(same schema or different schemas) from one source table with same structure ?
Please give me advice
Thanks
Raj
Edited by: user11410176 on Oct 21, 2009 9:55 AMHi Lucky,
Thanks for your reply,
What iam trying is ...Iam trying to load the data from legacy tables(3) into oracle staging tables.But i need to load the same source data into two staging tables(these staging tables are in two different schemas)
can i load this source data into two staging tables by using single standard interface(some business logic is there)
If i can then give me some suggestion how to do that
Thanks in advance
Raj -
All records loaded to cube successfully but the request is in red status
All the records are loaded from r3 to target, but the status of the request is still in RED, what is the reason and how to resolve it?
Hi,
If you find the records are loaded to cube and request is still red, Follow any one of the following options.
1. Make the request to green manually
2. Check the extraction monitor settings in SPRO -
> SAP Customizing Implementation Guide ---> Business Intelligence --->
Automated Processes -
> Extraction Monitor Settings. Check how the settings are done if you are authorized.
3. Go to Manage of the target ---> Environment ---> Automatic Request processing ---> Check the option Set Quality Status to OK
Hope this helps,
Regards,
Rama Murthy.
Edited by: Rama Murthy Pvss on May 11, 2010 7:39 AM -
Staging area different from target
I am using oracle 10g as target database. I want to upload a flat data file into oracle table.
I uploaded sucessfully using LKM Oracle (SQL Loader) in Interface. In this case i am using oracle database as a staging area. So all load transferred to my database at the timing of processing.
I want to create staging area at my file server. So please help me out to resolve this problem.A staging area must accept SQL syntax.
A File server won't accept SQL syntax.
So if you speak about Physical Server where you got your file and if there is a RDBMS installed in maybe but else I don't really know how you can...
You can specify another data server for your staging area or use the SUNOPSIS_MEMORY_ENGINE which use the cache I think but it's not optimized I think...
For this in the Definition Tab of your Interface choose Staging Area different from the Target and then select in the list box SUNOPSIS_MEMORY_ENGINE.
Maybe you are looking for
-
ABAP dump coming at the time of displaying error message.
Hi to all I have written a code in user exit . At the time of saving ABAP dump is coming instead of showing error message. Error analysis The program attempted to issue a " " message during "Exit Command" processing. This is an illegal operation.
-
More than 1 variable in query possible?
hi friends, how are you, can i use more than 1 variable in 1 query, if possible , can u give me 1 scenerio ple?
-
Query tuning for search within blob content.
Hi, I ve got a query which searches across 3 tables. When I include a search condition : (CONTAINS(CF.blob_content,''{''||:P146_TEXT||''}'',1)>0 AND CF.REF_ID = CR.REF_ID) the query takes really long time to execute. Is there a way to reduce the exec
-
Return Stock transport Order referring to original Stock transport order
Hi, We have a standard stock transport order process which involves PO creation and all relevant processes. Now in case items received via STO are damaged or not good, then we create a return stock transfer order. Is there anyway available in the sys
-
Satellite A200-25Z: trouble with display driver
Hi, I'm trying to install WIN XP on a A200 25Z. At first all seemed to work fine but now I constantly get a bluescreen before xp loaded completeley saying something like memory problem on ati2mtag.dll driver Sometimes, it does start but then when I h