Diagnosic Question
So I was checking my system profiler for some info and came across a Diagnostic error message. it said the following
Power On Self-Test:
Last Run: 5/19/07 6:19 PM
Result: Failed
Failure type: Memory
Memory slot: SODIMM0/J25LOWER
Can anyone tell me what this means? I haven't had any problems yet, but I'm not sure what this means.
Here's some helpful laptop sites.
Fix It Guides for Mac Laptops & Mini
http://www.ifixit.com/Guide/
The guides can be viewed on-line or you can download a PDF file.
How to Upgrade, Repair, Disassemble an Apple/Macintosh Laptop or Notebook
http://repair4laptop.org/disassembly_apple.html
PowerBookTech
http://www.powerbooktech.com/
(Note - PowerBookTech has some good info, however, some Mac users in other forums were having difficulty getting delivery on parts from them.)
How to Upgrade, Repair, Disassemble an Apple/Macintosh Laptop or Notebook
http://repair4laptop.org/disassembly_apple.html
Laptop Repair Guides
http://www.applerepairmanuals.com/#portables
Cheers, Tom
Similar Messages
-
My fan is starting to frequently grind. I've tried vacuuming it thinking that it's a question of loose debris that may have been sucked up and stuck along the track but that isn't working. I'm not sure if I should try opening the computer and cleaning it manually or what. Suggestions?
(P.S. If you are an employee of HP, please do not post a diagnosis question, disclaim your help as being from the company, then not reply when I post an answer.)
Thank you.Hi:
I'm thinking the fan bearings are going out and the fan will need to be replaced.
Getting to that part is moderately difficult.
Here is the link to the 6910p service manual. Parts list with part numbers is in Chapter 3, and component R & R procedures in Chapter 4.
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01566975/c01566975.pdf
Instead of a vacuum, use a can of compressed air to clean the fan intake and exhaust. Put a toothpick or something in to keep the fan from pinwheeling.
Paul -
Can you please resend me the link as something went wrong when I tried to update the plugins.
Save the iDVD project as a disk image first (File ➙ Save as Disk Image menu option), mount the disk image and play with DVD Player to verify the encoding was successful and all media is good. Once you've confirmed the encoding was good burn to disk with Disk Utility at the slowest speed available to assure the best burn quality. Always use top quality media: Verbatium, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
If the disk image doesn't play correctly then you need to troubleshoot the media used in the project.
OT -
Hi Friends,
I was face some Interview.
Please send answers to the questions?
How many data Fields and key fields we can create in DSO?
You can overwrite key fields or Data Fields?
Which up date we use in Delta queue extraction( v1 or v2 or v3)
Which message we get when transported request is failed?
what is the Structural difference between Infoucbe and DSO
Data Loading is taking huge time when we extract data from source system to BI system/ how to solve?(Before it took 3-4 Hours now data loading takes 4 days)What is the difference between Display Attribute and
Navigational Attribute? How to make display attribute and navigational
attribute?
How to load flat file data?
How to load Hierarchy file data?
What is HACR?
How to maintain HACR?
If any issue in HACR then how to resolve the issue?
What is Baby Cube?
Why we are creating Aggregates?
What is the use of Aggregates?
Is there
any particular field on that we can create Aggregates or we can maintain
Aggregate on any field?
What is
the different DSO available? And what is the difference between those DSO?
What is
replacement path?
What are
the extractor types?
• Application Specific
o BW Content FI, HR, CO, SAP CRM, LO Cockpit
o Customer-Generated Extractors
LIS, FI-SL, CO-PA
• Cross Application (Generic Extractors)
o DB View, InfoSet, Function Module
2. What are the steps involved in LO Extraction?
• The steps are:
o RSA5 Select the DataSources
o LBWE Maintain DataSources and Activate Extract Structures
o LBWG Delete Setup Tables
o 0LI*BW Setup tables
o RSA3 Check extraction and the data in Setup tables
o LBWQ Check the extraction queue
o LBWF Log for LO Extract Structures
o RSA7 BW Delta
Queue Monitor
3. How to create a connection with LIS InfoStructures?
• LBW0 Connecting LIS InfoStructures to BW
4. What is the difference between ODS and InfoCube and MultiProvider?
• ODS: Provides granular data, allows overwrite and data is in transparent
tables, ideal for drilldown and RRI.
• CUBE: Follows the star schema, we can only append data, ideal for primary
reporting.
• MultiProvider: Does not have physical data. It allows to access data from
different InfoProviders (Cube, ODS, InfoObject). It is also preferred for
reporting.
5. What are Start routines, Transfer routines and Update routines?
• Start Routines: The start routine is run for each DataPackage after the data
has been written to the PSA and before the transfer rules have been executed.
It allows complex computations for a key figure or a characteristic. It has no
return value. Its purpose is to execute preliminary calculations and to store
them in global DataStructures. This structure or table can be accessed in the
other routines. The entire DataPackage in the transfer structure format is used
as a parameter for the routine.
• Transfer / Update Routines: They are defined at the InfoObject level. It is
like the Start Routine. It is independent of the DataSource. We can use this to
define Global Data and Global Checks.
6. What is the difference between start routine and update routine, when, how
and why are they called?
• Start routine can be used to access InfoPackage while update routines are
used while updating the Data Targets.
7. What is the table that is used in start routines?
• Always the table structure will be the structure of an ODS or InfoCube. For
example if it is an ODS then active table structure will be the table.
8. Explain how you used Start routines in your project?
• Start routines are used for mass processing of records. In start routine all
the records of DataPackage is available for processing. So we can process all
these records together in start routine. In one of scenario, we wanted to apply
size % to the forecast data. For example if material M1 is forecasted to say
100 in May. Then after applying size %(Small 20%, Medium 40%, Large 20%, Extra
Large 20%), we wanted to have 4 records against one single record that is
coming in the info package. This is achieved in start routine.
9. What are Return Tables?
• When we want to return multiple records, instead of single value, we use the
return table in the Update Routine. Example: If we have total telephone expense
for a Cost Center, using a return table we can get
expense per employee.
10. How do start routine and return table synchronize with each other?
• Return table is used to return the Value following the execution of start
routine
11. What is the difference
between V1, V2 and V3 updates?
• V1 Update: It is a Synchronous update. Here the Statistics update is carried
out at the same time as the document update (in the application
tables).
• V2 Update: It is an Asynchronous update. Statistics update and the Document
update take place as different tasks.
o V1 & V2 don't need scheduling.
• Serialized V3 Update: The V3 collective update must be scheduled as a job
(via LBWE). Here, document data is collected in the order it was created and
transferred into the BW as a batch job. The transfer sequence may not be the
same as the order in which the data was created in all scenarios. V3 update
only processes the update data that is successfully processed with the V2
update.
12. What is compression?
• It is a process used to delete the Request IDs and this saves space.
13. What is Rollup?
• This is used to load new DataPackages (requests) into the InfoCube
aggregates. If we have not performed a rollup then the new InfoCube data will
not be available while reporting on the aggregate.
14. What is table partitioning and what are the benefits of partitioning in an
InfoCube?
• It is the method of dividing a table which would enable a quick reference.
SAP uses fact file partitioning to improve performance. We can partition only
at 0CALMONTH or 0FISCPER. Table partitioning helps to run the report faster as
data is stored in the relevant partitions. Also table maintenance becomes
easier. Oracle,
Informix, IBM DB2/390 supports table partitioning while SAP DB, Microsoft SQL
Server, IBM DB2/400 do not support table portioning.
15. How many extra partitions are created and why?
• Two partitions are created for date before the begin date and after the end
date.
16. What are the options available in transfer rule?
• InfoObject
• Constant
• Routine
• Formula
17. How would you optimize the dimensions?
• We should define as many dimensions as possible and we have to take care that
no single dimension crosses more than 20% of the fact table size.
18. What are Conversion Routines for units and currencies in the update rule?
• Using this option we can write ABAP
code for Units / Currencies conversion. If we enable this flag then unit of Key
Figure appears in the ABAP code as an additional parameter. For example, we can
convert units in Pounds to Kilos.
19. Can an InfoObject be an InfoProvider, how and why?
• Yes, when we want to report on Characteristics or Master Data. We have to
right click on the InfoArea and select "Insert characteristic as data
target". For example, we can make 0CUSTOMER as an InfoProvider and report
on it.
20. What is Open Hub Service?
• The Open Hub Service enables us to distribute data from an SAP BW system into
external Data Marts, analytical applications, and other applications. We can
ensure controlled distribution using several systems. The central object for
exporting data is the InfoSpoke. We can define the source and the target object
for the data. BW becomes a hub of an enterprise data warehouse.
The distribution of data becomes clear through central monitoring from the
distribution status in the BW system.
21. How do you transform Open
Hub Data?
• Using BADI we can transform Open Hub Data according to the destination
requirement.
22. What is ODS?
• Operational DataSource is used for detailed storage of data. We can overwrite
data in the ODS. The data is stored in transparent tables.
23. What are BW Statistics and what is its use?
• They are group of Business Content InfoCubes which are used to measure
performance for Query and Load Monitoring. It also shows the usage of
aggregates, OLAP and Warehouse management
http://www.ittestpapers.com/articles/713/3/SAP-BW-Interview-Questions---Part-A/Page3.html
Communication Structure and Transfer
rules
• Create and InfoPackage
• Load Data
25. What are the delta options available when you load from flat file?
• The 3 options for Delta Management with Flat Files:
o Full Upload
o New Status for Changed records (ODS Object only)
o Additive Delta (ODS Object & InfoCube)
Q) Under which menu path is the Test Workbench to be found, including in
earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
Q) I want to delete a BEx query that is in Production system through request. Is
anyone aware about it?
A) Have you tried the RSZDELETE transaction?
Q) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many
process types, for example after loading data into Info Cube, you rollup data
into aggregates, now this rolling up of data into aggregates is a process type
which you keep after the process type for loading data into Cube. This rolling
up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another
process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data
packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything
OK ---- Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You
have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource
delta enabled. While creating datasource from RSO2, after entering datasource
name and pressing create, in the next screen there is one button at the top,
which says generic delta. If you want more details about this there is a
chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views,
SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta
attribute
Q) Workbooks, as a general rule, should be transported with the
role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the
role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has
never been transported, and then you have a choice of transporting the role
(recommended) or just the workbook. If only the workbook is transported, then
an additional step will have to be taken after import: Locate the WorkbookID
via Table RSRWBINDEXT (in Dev and verify the same exists in the target system)
and proceed to manually add it to the role in the target system via Transaction
Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both
the role and workbook. Keep in mind that a workbook is an object unto itself
and has no dependencies on other objects. Thus, you do not receive an error
message from the transport of 'just a workbook' -- even though it may not be
visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into
an infocube?
A. This depends, if you have complex coding in update rules it will take longer
time, or else it will take less than 30 minutes.
Q) What are the five ASAP Methodologies?
A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase, decision makers define clear project
objectives and an efficient decision making process ( i.e. Discussions with the
client, like what are his needs and requirements etc.). Project managers
will be involved in this phase (I guess).
A Project Charter is issued and an implementation strategy is outlined in this
phase.
2. Business Blueprint: It is a detailed documentation of your company's
requirements. (i.e. what are the objects we need to develop are modified
depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development
of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing,
conducting pre-go-live, end user training etc.
End user training is given that is in the client site you train them how to
work with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production.
The Project team will be supporting the end users.
Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not
sure.
Then Landscape of b/w: u have the development system, testing system, production system
Development system: All the implementation part is done in this sys. (I.e.,
Analysis of objects developing, modification etc) and from here the objects are
transported to the testing system, but before transporting an initial test
known as Unit testing
(testing of objects) is done in the development sys.
Testing/Quality system: quality check is done in this system and integration
testing is done.
Production system: All the extraction part takes place in this sys.
Q) How do you measure the size of infocube?
A: In no of records.
Q). Difference between infocube and ODS?
A: Infocube is structured as star schema (extended) where a fact table is
surrounded by different dim table that are linked with DIM'ids. And the data
wise, you will have aggregated data in the cubes. No overwrite functionality
ODS is a flat structure (flat table) with no star schema concept and which will
have granular data (detailed level). Overwrite functionality.
Flat file
datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
Q) Difference between display attributes and navigational attributes?
A: Display attribute is one, which is used only for display purpose in the
report. Where as navigational attribute is used for drilling down in the
report. We don't need to maintain Navigational attribute in the cube as a
characteristic (that is the advantage) to drill down.
Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete
it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use
different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources
on the transactional system needs to be replicated on BW side and attached to
infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER
RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN
WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append
fields). Refer white paper
on LO-Cockpit extractions.
Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
A) Initially we don't delete the setup tables but when we do change in extract
structure we go for it. We r changing the extract structure right, that means
there are some newly added fields in that which r not before. So to get the
required data ( i.e.; the data which is required is taken and to avoid
redundancy) we delete n then fill the setup tables.
To refresh the statistical data.
The extraction set up reads the dataset that you want to process such as,
customers orders with the tables like VBAK, VBAP) & fills the relevant communication
structure with the data. The data is stored in cluster
tables from where it is read when the initialization is run. It is important
that during initialization phase, no one generates or modifies application
data, at least until the tables can be set up.
Q) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the
information has to be updated online. For designing the Virtual cube you have
to write the function module that is linking to table, Virtual cube it is like
a the structure, when ever the table is updated the virtual cube will fetch the
data from table and display report Online... FYI.. you will get the information
: https://www.sdn.sap.com/sdn
/index.sdn and search for Designing Virtual Cube and you will get
a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes &
Characteristic values.
Variable Types are
Manual entry /default value
Replacement path
SAP exit
Customer exit
Authorization
Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump
targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION
WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev---àQ and Dev-------àP
Q) What types of partitioning are there for BW?
There are two Partitioning Performance aspects for BW (Cube & PSA)
Query Data Retrieval
Performance Improvement:
Partitioning by (say) Date Range improves data retrieval by making best use of
database [data range] execution plans and indexes (of say Oracle database engine).
B) Transactional Load Partitioning Improvement:
Partitioning based on expected load volumes and data element sizes. Improves
data loading into PSA and Cubes by infopackages (Eg. without timeouts).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta
loads? Are there any standard procedures for checking them or matching the
number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the
number of records extracted. Then go to BW Monitor to check the number of
records in the PSA and check to see if it is the same & also in the monitor
header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out
extracts problems in R/3. It is simple to use, but only really tells you if the
extractor works. Since records that get updated into Cubes/ODS structures are
controlled by Update Rules, you will not be able to determine what is in the
Cube compared to what is in the R/3 environment. You will need to compare
records on a 1:1 basis against records in R/3 transactions for the functional
area in question. I would recommend enlisting the help of the end user community
to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute
and you will see the record count, you can also go to display that data. You
are not modifying anything so what you do in RSA3 has no effect on data quality
afterwards. However, it will not tell you how many records should be expected
in BW for a given load. You have that information in the monitor RSMO during
and after data loads. From RSMO for a given load you can determine how many
records were passed through the transfer rules from R/3, how many targets were
updated, and how many records passed through the Update Rules. It also gives
you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and
writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data
target its better u write in transfer rules because u can assign one InfoSource
to more than one data target & and what ever logic u write in update rules
it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a
routine in the tab strip key figure calculation, by choosing checkbox Return
table. The corresponding key figure routine then no longer has a return value,
but a return table. You can then generate as many key figure values, as you
like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose
you want to restrict (delete) some records based on conditions before getting
loaded into data targets, then you can specify this in update rules-start
routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the
condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent
navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation
attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no:
of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the
delta queue and that have not yet been confirmed. The number includes the LUWs
of the last delta request (for repetition of a delta request) and the LUWs for
the next delta request. A LUW only disappears from the RSA7 display when it has
been transferred to the BW System and a new delta request has been received
from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description
and creation data of a particular Reports. Reports that are created using BEx
Analyzer.
A) There is no such table in BW if you want to know such details while you are
opening a particular query press properties button you will come to know all
the details that you wanted.
You will find your information about technical names and description about
queries in the following tables. Directory of all reports (Table RSRREPDIR) and
Directory of the reporting component elements (Table RSZELTDIR) for workbooks
and the connections to queries check Where- used list for reports in workbooks
(Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table
RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual
document, a group of documents from a collective run or a whole data packet of
an application
extractor.
Q) Why does the number in the 'Total' column in the overview screen of
Transaction RSA7 differ from the number of data records that is displayed when
you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also
first question) that were written to the qRFC queue and that have not yet been
confirmed. The detail screen displays the records contained in the LUWs. Both,
the records belonging to the previous delta request and the records that do not
meet the selection conditions of the preceding delta init requests are filtered
out. Thus, only the records that are ready for the next delta request are
displayed on the detail screen. In the detail screen of Transaction RSA7, a
possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after
successful delta loading?
A) Only when a new delta has been requested does the source system learn that
the previous delta was successfully loaded to the BW System. Then, the LUWs of
the previous delta may be confirmed (and also deleted). In the meantime, the
LUWs must be kept for a possible delta request repetition. In particular, the
number on the overview screen does not change when the first delta was loaded
to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the
delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has
also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to
the BW System via the delta queue but directly via the extractor (delta for
master data using ALE change pointers). Such a DataSource should not be
displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the
loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading
process from the delta queue, then refer to the application-specific notes (for
example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as
effective for the delta queue as for a full update. Please note, however, that
LUWs are not split during data loading for consistency reasons. This means that
when very large LUWs are written to the DeltaQueue, the actual package size may
differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example
approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of
defining the amount of data to be displayed, to restrict it, to selectively
choose the number of a data record, to make a distinction between the 'actual'
delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in
RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in
the delta queue. It is comparable to deleting an InitDelta in the BW System and
should preferably be executed there. You do not only delete all data of this
DataSource for the affected BW System, but also lose the entire information
concerning the delta initialization. Then you can only request new deltas after
another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding
target system are confirmed. Physical deletion only takes place in the qRFC
outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System,
from which the delta initialization was originally executed, no longer exists
or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a
day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during
deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the
logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the
delta initialization was not successful. A successful delta initialization (the
corresponding request must have QM status 'green' in the BW System) is a
prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction
SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal
queue name must be used for selection on the initial screen of the qRFC
monitor. This is made up of the prefix 'BW, the client and the short name of
the DataSource. For DataSources whose name are 19 characters long or shorter,
the short name corresponds to the name of the DataSource. For DataSources whose
name is longer than 19 characters (for delta-capable DataSources only possible
as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs.
Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the
delta queue (RSA7). This happens in particular during automatic goods receipt
posting (MRRS). There is no duplicate transfer of records to the BW system. See
Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show
data loaded into BW during the last delta but also data that were newly added,
i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both
actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the
delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a
delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or
single values), you can make up to about 100 delta inits. It should not be
more.
With complicated selection conditions, it should be only up to 10-20 delta
inits.
Reason: With many selection conditions that are joined in a complicated way,
too many 'where' lines are generated in the generated ABAP
source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will
happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas
have been fetched from the DeltaQueue into BW and that no delta is pending.
After the client copy, an inconsistency might occur between BW delta tables and
the OLTP delta tables as described in Note 405943. After the client copy, Table
ROOSPRMSC will probably be empty in the OLTP since this table is
client-independent. After the system copy, the table will contain the entries
with the old logical system name that are no longer useful for further delta
loading from the new logical system. The delta must be initialized in any case
since delta depends on both the BW system and the source system. Even if no
dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you
should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of
processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW
queues only after informing the BW Support or only if this is explicitly
requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the
collective run (V3 update), it does not contain all documents. Only another
delta request loads the missing documents into BW. What is the cause for this
"splitting"?
A) The collective run submits the open V2 documents for processing to the task
handler, which processes them in one or several parallel update processes in an
asynchronous way. For this reason, plan a sufficiently large "safety time
window" between the end of the collective run in the source system and the
start of the delta request in BW. An alternative solution where this problem
does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the
DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always
be carried out at a time when no posting takes place. Otherwise, buffer
problems may occur: If a user started the internal mode at a time when the
delta initialization was still active, he/she posts data into the queue even
though the initialization had been deleted in the meantime. This is the case in
your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some
entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What
do these statuses mean? Which values in the field 'Status' mean what and which
values are correct and which are alarming? Are the statuses BW-specific or
generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read
once either in a delta request or in a repetition of the delta request.
However, this does not mean that the record has successfully reached the BW
yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that
the record has been written into the DeltaQueue and will be loaded into the BW
with the next delta request or a repetition of a delta. In any case only the
statuses READ, READY and RECORDED in both tables are considered to be valid.
The status EXECUTED in TRFCQOUT can occur temporarily. It is set before
starting a DeltaExtraction for all records with status READ present at that
time. The records with status EXECUTED are usually deleted from the queue in
packages within a delta request directly after setting the status before
extracting a new delta. If you see such records, it means that either a process
which is confirming and deleting records which have been loaded into the BW is
successfully running at the moment, or, if the records remain in the table for
a longer period of time with status EXECUTED, it is likely that there are
problems with deleting the records which have already been successfully been
loaded into the BW. In this state, no more deltas are loaded into the BW. Every
other status is an indicator for an error or an inconsistency. NOSEND in SMQ1
means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards
new delta records were written to the DeltaQueue. When loading the delta into
the PSA, it shows that some fields were moved. The same result occurs when the
contents of the DeltaQueue are listed via the detail display. Why are the data
displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the
database and that all servers are synchronized. We recommend to reset the
buffers using Transaction $SYNC. If the extract structure change is not
communicated synchronously to the server where delta records are being created,
the records are written with the old structure until the new structure has been
generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request
is RED, the next load will be of type 'Repeat'. If you need to repeat the last
load for certain reasons, set the request in the monitor to red manually. For
the contents of the repeat see Question 14. Delta requests set to red despite
of data being already updated lead to duplicate records in a subsequent repeat,
if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update
methods. Which update method is recommended in logistics? According to which
criteria should the decision be made? How can I choose an update method in
logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the
DeltaQueue may grow to without facing the danger of a read failure due to
memory problems?
A) There is no strict limit (except for the restricted number range of the
24-digit QCOUNT counter in the LUW management table - which is of no practical
importance, however - or the restrictions regarding the volume and number of
records in a database table).
When estimating "smooth" limits, both the number of LUWs is important
and the average data volume per LUW. As a rule, we recommend to bundle data
(usually documents) already when writing to the DeltaQueue to keep number of
LUWs small (partly this can be set in the applications, e.g. in the Logistics
Cockpit). The data volume of a single LUW should not be considerably larger
than 10% of the memory available to the work process for data extraction
(in a 32-bit architecture with a memory volume of about 1GByte per work
process, 100 Mbytes per LUW should not be exceeded). That limit is of rather
small practical importance as well since a comparable limit already applies
when writing to the DeltaQueue. If the limit is observed, correct reading is
guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions,
you should at least make sure that the data are fetched from all connected BWs
as quickly as possible. But for other, BW-specific, reasons, the frequency
should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than
1 million LUWs are read and fetched from the database per DeltaRequest. If this
limit is reached within a request, the DeltaQueue must be emptied by several
successive DeltaRequests. We recommend, however, to try not to reach that limit
but trigger the fetching of data from the connected BWs already when the number
of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the
report. Usually, we load the transactional data nightly. Is there any easy way
to include this information on the report for users? So that they know the
validity of the report.
A) If I understand your requirement correctly, you want to display the date on
which data was loaded into the data target from which the report is being
executed. If it is so, configure your workbook to display the text elements in
the report. This displays the relevance of data field, which is the date on which
the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it
possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if
it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY
AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS.
THROUGH WHICH NETWORK.
a) VPN…………….Virtual
Private Network, VPN is nothing but one sort of network
where we can connect to the client systems sitting in offshore through RAS
(Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management
Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE
CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and
goto sm12
TCode then unlock it this is happened when lock errors are occurred when u
scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in
the rows?
A) Expand dimension under left side panel (that is infocube panel) select than
navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former
have an improved write access performance level. Standard InfoCubes are
technically optimized for read-only access and for a comparatively small number
of simultaneous accesses. Instead, the transactional InfoCube was developed to
meet the demands of SAP Strategic Enterprise Management (SEM), meaning that,
data is written to the InfoCube (possibly by several users at the same time)
and re-read as soon as possible. Standard Basic cubes are not suitable for
this.
Q) Is there any way to delete cube contents within update rules from an ODS
data source? The reason for this would be to delete (or zero out) a cube record
in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only
possible to avoid that some content is updated into the InfoCube using the
start routine. Loop at all the records and delete the record that has the
condition. "If the open order quantity was 0" You have to think also
in before and after images in case of a delta upload. In that case you may
delete the change record and keep the old and after the change the wrong
information.
Q) I am not able to access a node in hierarchy directly using variables for
reports. When I am using Tcode RSZV it is giving a message that it doesn't
exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other
options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards,
it's possible in the Query Designer (BEx) itself. Just right click on the
InfoObject for which you want to use as variables and precede further selecting
variable type and proce -
Grey Screen with Flashing Folder with Question Mark
Hi,
I need some help with an issue I'm having on my Mid-2012 Macbook Pro (13"; OSX 10.9.2; 8GB RAM). I've had issues with this Macbook for the past year. I've worked with Apple Support and had it into the Mac Store prior to the warranty expiring (Dec 2013). I have the exact same model with all of the same specs that my employer purchased at the same time for work as my work computer, and I haven't had any issues with that one.
Previously, the system would slow down excessively and eventually start hanging. Occasionally the screen would start flashing. Apple phone support had me wipe the hard drive and re-install the OS and all of my file, apps, and setting from my Time Machine backup. That worked for about four months, and then it started again. Since it was getting close to the warranty expiration, I took it to an Apple Store. They ran a bunch of diagnostics, said the hardware was all fine but the OS needed to be re-installed. They did that in early Dec, and everything was cool again until about three days ago. Three days ago, it started slowing down and freezing again (even when doing non-memory intensive tasks such as broswing the web with only a couple of tabs open and no other applications open). Last night, it froze hard and wouldn't shut down, so I had to cold boot it. When I tried to power it back on, it came to the grey screen with the flashing folder with the question mark (which I know means it can't find the boot sector). I waited until this morning, and it stil wouldn't boot. I then rebooted into Startup Manager, and the HDD was there. I selected the HDD, and it booted fine and ran fine for a couple of hours (I was able to do a Time Machine backup). Then it froze up solid again. I waited for an hour or so before cold booting (don't like doing that), and when I tried rebooting, I got the flashing folder with the question mark. I tried booting into the Startup Manager again, but this time, my HDD wasn't listed. I then booted into the OSX Recovery utility (CMD R on boot), went into the Disk Utility hoping to do a disk repair, but my HDD wasn't listed. I have an external SATA to USB adapter, so I pulled the HDD, hooked it to a USB port on my other (identical except it doesn't have problems) Macbook Pro. Once my other Macbook booted, the HDD from the bad Macbook Pro showed up fine. I ran a verify and repair disk on the HDD from the bad Macbook, and it didn't show any issues.
So I figured I'd be really brave. I took the HDD from the bad Macbook Pro and put it in my work (good) Macbook Pro (I took the HDD out of my working work Macbook Pro). It booted fine. I then did the verify and repair disk (again no errors) and verify and repair permissions (it found a few, but no more than it has in the past). I ran it that way for about an hour with no issues. That led me to believe that the HDD for my personal Macbook was fine, and it must be an issue with the SATA cable or the mainboard.
Here's where it gets odd. I put the HDD from my work Macbook Pro into the bad Macbook Pro thinking it wouldn't even recognize it. It did recognize it, and it booted fine. I ran it like that for about 30 minutes. It did have a couple of short freeze ups, but it didn't lock up solid. I didn't want to push my luck and possibly damage the HDD for my work Macbook, so I shut down the bad Macbook Pro ended the experiment at that point.
I put the original HDD back in the Macbooks where they originally came from. I then ran the Apple Hardware Test (press and hold D on startup) on the bad Macbook Pro; I did the extended testing option. It ran for about an hour, but it didn't find any issues with the bad Macbook Pro.
I put the HDD from the bad Macbook back in my working Macbook and wiped the disk and reinstalled OSX from a Time Machine Backup from last week (before the problems occured). Put it back in the bad Macbook and still no luck. Finally I tried resetting the PRAM because I saw that as one of the options on this discussion board.
I've searched and read everything I can find related to this, but I can't find anything that works, and I'm at my wits end. Can anyone point me in a direction of what might be wrong and what else to try?
Thanks!
MikeYou performed thorough and methodical troubleshooting, and this appears to be the most important result:
I put the HDD from my work Macbook Pro into the bad Macbook Pro thinking it wouldn't even recognize it. It did recognize it, and it booted fine. I ran it like that for about 30 minutes. It did have a couple of short freeze ups, but it didn't lock up solid.
Given compatible hardware, you ought to be able to swap hard disk drives in exactly that manner, so it shouldn't surprise you that it worked. However, installing the "known good" HDD in the problem machine should not have resulted in any freeze-ups at all.
You can conclude the hard disks (both of them) are serviceable and whatever fault exists probably lies elsewhere. Often the SATA cable is damaged or not seated properly, and is likely to fail more than anything on the logic board. Inspect the logic board's SATA connections and make sure there are no contaminants or damage. The two drives and two logic boards are going to have slightly different component tolerances, so perhaps the defective one is simply exceeding some limit.
Apple Hardware Test is very cursory and essentially tests for the presence of operable hardware. It is far from an exhaustive test, and only a report of a failure can be relied upon for accuracy. For a more thorough test you would need to have Apple evaluate it using the time-consuming Apple Service Diagnostics. Even then, they may come up without a clue, and eventually someone will suggest a logic board replacement which can be expensive.
It is an unusual problem, and I don't know how much time Apple would invest in diagnosing it before they conclude you really ought to buy a new Mac instead. They might surprise you though in that a "depot repair", if yours is eligible, is a very cost effective option so consider it.
Given your ability you might also consider purchasing a replacement logic board from PowerbookMedic, or even sending it to them for a flat rate repair. -
Time Machine- Frequently Asked Questions
This post contains answers to many common, general questions about Time Machine.
It does not, however, cover diagnosis and correction of specific problems or errors. See the Time Machine - Troubleshooting *User Tip* at the top of this forum for such help.
General problems with Time Capsules are covered in the separate TimeCapsule forum, in the +Digital Life+ section, including the Using TIME MACHINE with a TIME CAPSULE *User Tip* also at the top of that forum.
*C o n t e n t s*
*1. How big a drive do I need for Time Machine?*
*2. What can TM back up, and where can it put it's backups?*
*3. Can I use my TM disk for other stuff?*
*4. Can I use one TM disk to back up 2 or more Macs?*
*5. I just bought an external drive. How do I get it to work with Time Machine?*
*6. Can I use a drive with other data already on it?*
*7. How can I tell what Time Machine is doing during (or after) a backup?*
*8. How can I tell what Time Machine is backing-up?*
*9. Why are my backups so large?*
*10. Can I tell Time Machine not to back up certain things?*
*11. What should I exclude, and what should I not exclude?*
*12. Should I delete old backups? If so, How?*
*13. How can I change TM's schedule of hourly backups?*
*14. How do I restore my entire system?*
*15. How do I restore selected items?*
*16. How can I restore a file/folder to an alternate location?*
*17. How can I see my backups, or the backups for a different Mac, via +Time Machine+ ?*
*18. How can I copy my TM backups to a different location?*
*19. How do I set up a new Mac from my old Mac's backups?*
*20. Once my Mac is backed-up, can I delete some stuff to save space?*
*21. How do I set up Time Machine to an internal or directly-connected external HD?*
*22. How do I set up Time Machine to a shared drive on another Mac?*
*23. How do I set up Time Machine to a Time Capsule or Airport Extreme?*
*24. What do the Time Machine icons in my Menubar and Dock do?*
_*1. How big a drive do I need for Time Machine?*_
A general "rule of thumb" is, TM needs 2 to 3 times as much space as the data it's backing-up (not necessarily the entire size of your internal HD).
But this varies greatly, depending on how you use your Mac. If you frequently add/update lots of large files, then even 3 times may not be enough. If you're a light user, 1.5 times might do. Unfortunately, it's rather hard to predict, so if in doubt, get a bigger one!
Also, there are some OSX features and 3rd-party applications that take up large amounts of backup space, for various reasons. See question #9 for details.
This is a trade-off between space and how long TM can keep it's backups, since TM will, by design, eventually use all the space available. But it won't just quit backing-up when it runs out: It starts deleting the oldest backups so it can keep making new ones. Thus, the more space it has, the longer it can keep your backups.
+Go to Top+
_*2. What can TM back up, and where can it put it's backups?*_
|
_*Time Machine can back up FROM*_ any internal or +directly connected+ drive/partition formatted with any variation of *Mac OSX Extended* (HFS+). Thus it cannot back up a +Boot Camp+ partition.
It cannot back up any network drive, including a Time Capsule, or a USB drive connected to a Time Capsule or Airport.
It will back-up your entire system (OSX, configuration, applications, user data, settings, preferences, etc. (less most caches, logs, trash, etc.), unless you specifically exclude things (see items 10 and 11).
In fact, by default, it will back up any such drive/partition (except the disk/partition where it's putting backups), unless you specifically exclude it.
|
_*Time Machine can back up TO:*_
_*Local Drives:*_
|
A directly-connected external disk (USB or FireWire)
A secondary internal disk or partition (but not your boot/OSX partition)
_*Network Drives:_*
|
A Time Capsule
A USB disk connected to a Time Capsule
A "shared" disk/partition connected directly to another Mac running Leopard or Snow Leopard on the same local network
An available Mac OS X Server version 10.5 or 10.6 volume
Any such drive must have either the +Apple Partition Map+ or GUID *Partition Map Scheme,* and either the +Mac OS Extended (Journaled)+ or +Mac OS Extended (Case-sensitive, journaled)+ Format (except a Time Capsule, which has a fixed format).
Time Machine may back up to some 3rd-party network drives (NAS or Network Attached Storage devices), but only those that meet the criteria specified by Apple: Disks that can be used with Time Machine.
Be very careful here: just because a 3rd-party vendor claims to support Time Machine doesn't necessarily mean that Apple supports that configuration, or that it will work in all circumstances.
In some cases, Time Machine may back up to a USB drive connected to an Airport Extreme, but it's often unreliable and is not supported, as specified in the link above.
|
You may find some "hacks" that might make other things work, in some cases, to a degree. But use them at your own risk.
First, since it's *unsupported by Apple,* there's nowhere to go when there's trouble.
Second, you're risking a future update preventing it from working, and perhaps rendering your backups useless just when you need them the most.
|
*_Step-by-step setup instructions for:_*
An internal or directly-connected external HD: Question 21.
A shared drive on another Mac: Question 22.
A Time Capsule: #Q1 in the Using TIME MACHINE with a TIME CAPSULE *User Tip,* also at the top of the +Time Capsule+ forum.
A USB drive connected to a Time Capsule: #Q2 in the Using TIME MACHINE with a TIME CAPSULE *User Tip.*
A USB drive connected to an Airport Extreme: #Q2 in the Using Time Machine with a USB drive connected to an Airport Extreme *User Tip,* also at the top of the +Airport Extreme+ forum.
+Go to Top+
_*3. Can I use my TM disk for other stuff?*_
Yes. TM will not delete anything you put there.
But it's much, much better to partition an external drive into 2 (or more) parts, also called volumes. Assign one to TM, for it's exclusive use for backups; use the other partition(s) however you want. To use a new drive, or one you don't mind erasing, see question #5. To add a partition to an existing drive that already has data on it, see question #6.
(Unfortunately, though, you can't partition a Time Capsule's internal disk. See #Q3 in the Using TIME MACHINE with a TIME CAPSULE *User Tip,* also at the top of the +Time Capsule+ forum.)
There are two reasons for this: first, TM will, eventually, fill all the empty space available to it before it begins deleting old backups. When it gets near full, you may not be able to put anything else there.
Second, if you ever want or have to delete all your old backups and start over (when you get a new Mac, or have certain problems), you can just erase the partition via Disk Utility; if there's other data there, it would be erased too. It is possible to delete individual backups via the TM interface, but it's one-at-a-time, so rather tedious (see question #12). But don't be tempted to just delete them via the Finder -- that can take a very long time, and hopelessly corrupt them.
For most purposes, each partition is treated as if it were a separate disk drive: each will be shown separately on your desktop and/or Finder sidebar, for example, using the name you assign to it.
Note that TM can be used to back-up any internal or directly-connected disk/partition that's formatted Mac OS Extended, including any "other" partitions on it's drive (but no network drives). But it's usually not a good idea to have your originals and backups on the same physical drive. If you don't want it to do that, exclude those disks/partitions from TM via TM's System Preferences > Options. (see question #10).
+Go to Top+
_*4. Can I use one TM disk to back up 2 or more Macs?*_
Yes, if it's big enough (see question #1). TM keeps track of which computer is which (by a hardware identifier, not computer name), so it will always keep it's backups for each Mac separate from each other.
It is advisable, though, to partition an external disk that will be connected to your Macs into one volume for each Mac (see question #5 or #6 for instructions). You can't partition a Time Capsule's disk, but each Mac will have a separate +sparse bundle+ on a Time Capsule, so it's not as big an issue.
There are two reasons for this:
|
First, TM will, eventually, fill all the space available to it before it begins deleting old backups. When multiple Macs are "competing" for the same backup space, TM might have room for several months of backups for one, but only a few weeks for another. This is especially likely to happen if you start backing-up a new Mac to a drive that already has a lot of backups from another Mac. TM on the new Mac will not delete backups from the other Mac, so when it needs space for new backups, it will delete the oldest backups from the new Mac instead.
Second, if you ever want or have to delete all the old backups for one Mac and start over, you can just erase the partition via Disk Utility; if there are other Mac's backups there, they would be erased also. If you replace one of the Macs, TM on the new one won't delete the backups from the old one. And sometimes it's advisable after certain problems.
|
If you're backing-up to a USB disk connected to a Time Capsule or Airport Extreme, you can use separate partitions if desired, but it's less of an issue, since the backups for each Mac will be in separate +sparse bundles.+ Those can be deleted via the Finder if necessary.
If you're backing-up to a shared disk connected to another Mac on the same local network, there should be a separate partition for the Mac that the disk is connected to directly; the other Macs can share a partition or have their own, as you desire, since these will each be in separate +sparse bundles.+
It is possible to delete individual backups via the TM interface, but it's one-at-a-time, so rather tedious. See question #12. (And don't be tempted to just delete them via the Finder -- all sorts of things may go very wrong.)
See question #17 for how to view/restore from another Mac's backups.
+Go to Top+
_*5. I just bought an external drive. How do I get it to work with Time Machine?*_
First decide if you're going to put other data on the drive. If so, see question #3 before proceeding. If you're making two or more partitions, it's usually a good idea to put your TM partition first, so you can adjust it later.
Second, consider whether your backups should be case-sensitive. That is the default if Time Machine formats it for you (and if you're backing up to a Time Capsule or other network device, TM will use a case-sensitive +sparse bundle,+ which you can't change.)
If any disk being backed-up is case-sensitive, then your backups must be case-sensitive also. There's no choice: TM can only back up that way. So if you think you might add a case-sensitive disk in the future, make your backup disk case-sensitive now.
But if all the disks/partitions being backed-up are case-ignorant, you may want your backups to be the same. If the backups are case-sensitive, TM can't restore an item if there's an item already in the same location with a conflicting name.
Example: you save a file named MYFILE, then later on change it to Myfile. You cannot restore the older MYFILE to replace the newer Myfile. Worse, if this happens, TM will not provide a list or log of the conflicting item(s)-- it just says "some items cannot be restored" and gives you the option to stop or continue.
|
Most new disks come with various things on them that you don't need, and may even conflict with Time Machine. So even if the drive says "Mac Ready" or the like, you should erase and format it with the Disk Utility app (in your Applications/Utilities folder):
a. When Disk Utility starts, select the new drive in the sidebar (the line with the size and make/ID).
b. Select the Erase tab, then confirm. This will erase the entire disk. (If you want, you can select +Security Options,+ then +Zero-Out Data+ to physically erase the entire disk by writing over everything. This will take quite a while, and shouldn't be necessary, especially on a new disk. This may not work if the drive is already set up with a non-Apple *Partition Map Scheme,* such as is used on Windows. If that happens, just continue with item c.
c. Select the Partition tab, then set the number of partitions from the drop down menu (use 1 partition unless you wish to make more). Sometimes you can't change a MBR drive to GUID or APM and change the number of partitions at the same time; if that happens, make a single partition with GUID or APM first, then re-format with the desired number.
d. Click Options, then choose either GUID or +Apple Partition Map.+ For Time Machine, either will work, but GUID is usually preferred for other purposes on an Intel Mac; +Apple Partition Map+ for a PPC Mac.
e. For each partition, click on it (it will then be outlined in blue), then supply a name (this is the name that will appear on your desktop and/or Finder sidebar) and size (either by typing in the box or dragging the dividers in the diagram), and set the *Format type* for your Time Machine partition to either +Mac OS Extended (Journaled)+ or +Mac OS Extended (Case-sensitive, Journaled)+ as you decided above. Set any other partitions to the desired format.
f. When you've got everything the way you want it, click Apply and wait a few moments for the process to complete.
+Go to Top+
_*6. Can I use a drive with other data already on it?*_
Maybe. First, verify that it has the correct *Partition Map Scheme* using Disk Utility (in your Applications/Utilities folder). Select the top line of your drive (with the size and make). Down towards the bottom of the panel will be the *Partition Map Scheme.* It should be either GUID or +Apple Partition Map.+ If this is not correct, the only way to use this disk for TM backups is to copy the data off somewhere else temporarily and reformat it into at least 2 partitions with the correct Partition Map Scheme per question #5 above, then copy the data back.
Also, partitions must use contiguous physical space on a disk, so just because your disk has enough total available space on it, there may not be enough contiguous space available for a new partition. The only way to tell is by trying -- if there isn't enough space, the partitioning will just fail without actually changing anything.
Before doing this, back-up the data you want to keep, just in case.
Here's how to partition without erasing:
a. When Disk Utility starts, select the drive in the sidebar (the line with the size and make/ID).
b. Click the Partition tab. DU will show a chart of the current partition(s), with the amount used in each shaded in light blue.
c. Click the partition you want to split. DU will outline it in blue.
d. Click the plus sign at the bottom. DU will split the partition into two parts, and name the new one the same as the old, but with "_2" appended.
e. Click the new partition; DU will outline it in blue.
f. Give it a name (this is the name that will appear on your desktop/Finder sidebar).
g. Adjust it's size, either by dragging the divider between the new and old partitions, or typing the desired size into the box.
h. Set the Format to +Mac OS Extended (Journaled)+ or +Mac OS Extended (Case-sensitive, journaled).+ See the pink box in question #5 to determine which you need.
i. When you have it the way you want it, click Apply.
j. The drive will be re-partitioned, unless DU can't get enough contiguous space; then it will send you an error message, and not change anything.
|
There are some 3rd-party apps that will move data around so you can do the partition even when Disk Utility can't. But they all strongly recommend that you back-up the data first, "just in case" something goes wrong. Well, if you're going to do that, you might as well simply do the copy, then erase and reformat the disk, then copy the data back.
+Go to Top+
_*7. How can I tell what Time Machine is doing during (or after) a backup?*_
If you press the TM icon in your Menubar, or right-click the TM icon in your Dock, and select +TM preferences,+ you may see "Preparing" (Leopard) or "Calculating Changes" (Snow Leopard); or a progress message ("xxx MB/GB of yyy MB/GB"), or a number of other messages; plus a progress bar (Preferences pane only; sometimes there's also a separate window with a progress bar).
For more detail, click here to download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. (If it doesn't seem to work, see #A1 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.)
See the yellow box in #C2 in the Time Machine - Troubleshooting *User Tip,* for explanations of common messages.
If you see messages that seem to indicate an error, or if your backup fails, you should be able to find the message there, or in the Contents, along with one or more possible fixes. If that doesn't help, post a new thread in this forum with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
+Go to Top+
_*8. How can I tell what Time Machine is backing-up?*_
Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup, except the first (excluding some hidden/system files, etc.).
Some prefer the BackupLoupe application.
+Go to Top+
_*9. Why are my backups so large?*_
There are some OSX features and 3rd-party applications that cause large Time Machine backups. Some common ones are any virtualization software, P2P or Torrent-type apps, and the Directory Protection feature of Tech Tools.
FileVault (System Preferences > Security) converts your entire Home Folder into a single, encrypted disk image. So any change to anything in your Home Folder is treated as a change to the encrypted image, and the whole thing is backed-up. TM minimizes the impact, though, by only backing it up when you log out, but it's still going to eat up a lot of space on your TM disk. Also, you can't view or restore individual items from your Home Folder via Time Machine; just the whole thing.
Some apps, such as Entourage, sometimes use a single file, often a database, to store their data. With Entourage, for example, every time you send or receive a single message, the whole database is changed, and will be backed-up the next time. Apple mail, of course, stores messages individually, so this doesn't happen.
If in doubt, use the +Time Tracker+ app to see what's taking-up the space. See question #8.
One solution is to simply exclude the item from TM so it isn't backed-up regularly, then when you do want it backed-up, just copy it somewhere that's not excluded. See question #10.
+Go to Top+
_*10. Can I tell Time Machine not to back up certain things?*_
Sure. Go to TM's Preferences and click Options.
In the next panel, click the plus sign at the bottom.
In the sidebar of the next panel, select your computer, drive, or home folder as appropriate; then navigate to the file/folder you want to exclude. If you can't find it, and it's name starts with a dot (period), or it's in a top-level folder that doesn't appear when you click your internal HD in the sidebar, it's a hidden item. Click the +Show invisible items+ box to make it show up.
Select it, click Exclude, then Done.
+Go to Top+
_*11. What should I exclude, and what should I not exclude?*_
First, TM automatically excludes most caches, work files, logs, trash, etc., so you don't need to worry about those (see below for the gory details).
You may want to exclude some special files/folders that cause extra-large backups (see question #9.)
Some folks exclude their Desktop and/or Downloads folders, as they use these for "working storage" and put the finished product in a permanent location that does get backed-up.
If you do a lot of step-by-step processing of large files, such as video processing, you might want to do it on a "scratch" disk, partition, or folder that you exclude from TM, so the intermediate steps won't all be backed-up. When done, be sure to put the finished product somewhere it will be backed-up.
Some people exclude their /System and/or /Library and/or /Applications folders, to save space. Generally this is unwise, as it won't save very much disk space, but will make recovery from a disk failure *very, very* tedious and time-consuming. You'd have to install OSX from your disc; migrate or restore your data; download and install the "combo" Software Update to bring your OS current; and reinstall all 3rd-party software and re-enter any license codes; then hope you didn't miss anything. Major hassle for minor space saving (usually 14-20 GB).
|
*Details of automatically-excluded items:*
|
Sometimes, changes to your iPhoto and/or Aperture libraries may not be backed-up if those apps are open.
Most things omitted are listed in a special "plist" on your system. See this file:
/System/Library/CoreServices/backupd.bundle/Contents/Resources/StdExclusions.pli st
A few others are excluded via special "extended attributes" on certain items, mostly in the iTunes and iPhoto libraries. These are automatically rebuilt or re-indexed when restored, so don't need to be backed-up.
To see which ones are excluded, open the Terminal app (in your Applications/Utilities folder). Be *very careful* with this app. It's a direct link into UNIX, the underpinnings of OSX, but without the protections of OSX.
In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
(where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
Copy the following after the prompt exactly, then press Return.
sudo mdfind "comapple_backupexcludeItem = 'com.apple.backupd'"
You'll be prompted to enter your Admin password (it won't be displayed). That will list the items excluded this way.
If you use Xcode, the "build" folders are not backed-up.
|
+Go to Top+
_*12. Should I delete old backups? If so, How?*_
Under normal circumstances, you shouldn't have to. TM automatically "thins" (deletes) backups every time it does a new backup, on the following schedule:
"Hourly" backups after 24 hours (except the first of the day, which is a "Daily" backup).
"Daily" backups after a month (except the first of each week, which is a "Weekly" backup.)
"Weekly" backups are kept until TM needs the space for new backups; then one or more of the oldest weeklies will be deleted.
However, TM will never delete the backup copy of anything that was on the disk being backed-up at the time of any remaining backup. So all that's actually deleted are copies of items whose originals were changed or deleted before the next remaining backup.
But if you want or need to, you can delete either all backups of a particular file or folder, or an entire backup (sort of). Do not attempt this via the Finder. First, if you're on Leopard, be sure you have the "action" or "gear" icon in your Finder's toolbar +(Finder > View > Customize Toolbar).+ If there's no toolbar, click the lozenge at the upper-right of the Finder window's title bar.
Use the TM interface: +Enter Time Machine.+ (To delete backups for a different Mac, see question #17).
|
Locate the backup or item you want to delete via the "cascade" of Finder windows.
If you want to delete all backups of a particular item, select it in the window.
Right-click the item (if you're on Leopard, Click the "gear" icon in the toolbar) and select either +Delete Backup+ (the entire backup) or +Delete all Backups of <item selected>.+
|
You'll see a confirmation prompt, then one for your Administrator's password. This may take a while, especially over a network.
If you delete an entire backup, it will disappear from the timeline and the "cascade" of Finder windows, but it will not actually delete the backup copy of any item that was present at the time of any remaining backup. Thus you may not gain much space. This is usually fairly quick, but sometimes quite lengthy (if you exit TM, you may see a progress bar for it). Unfortunately, you cannot predict which will be fast and which won't.
|
If you're backing-up over a network, there's an additional complication: Those backups are in a +sparse bundle,+ not a normal folder. A sparse bundle doesn't shrink automatically when things are removed from it, so you won't see how much space you've gained. TM will automatically "compact" a sparse bundle when it needs room for new backups, but you can do it manually via a command in the Terminal app (in your Applications/Utilities folder.
Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
(where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
At the prompt, type +*hdiutil compact+* followed by a space.
Then drag the Sparse Bundle to the Terminal window, and press Return.
|
If you delete all backups of an item, TM will not back it up again unless/until it's changed, or TM does a "deep traversal" (see the yellow box in #C2 in theTime Machine - Troubleshooting *User Tip,* also at the top of this forum).
+Go to Top+
_*13. How can I change TM's schedule of hourly backups?*_
It's usually best to let TM do it's hourly backups. It was designed to protect you best that way.
If they're using too much time or disk space, see item #9.
If they're slow or hanging, see item #D2 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
If you still want to do this, you can use the free Time Machine Editor.
It may change the following files, in your /System/Library/LaunchDaemons folder:
com.apple.backupd-attach.plist
com.apple.backupd-auto.plist
com.apple.backupd-wake.plist
com.apple.backupd.plist
It's a good idea to copy these somewhere safe before using the Editor. Then if there's a problem, you can delete the corrupted ones and put the copies back. Do not attempt to edit these yourself.
Also note that if you ever want to resume hourly backups, use Time Machine Editor to change back to that schedule before deleting the app. Otherwise, Time Machine will keep using the last schedule set by Time Machine Editor.
+Go to Top+
_*14. How do I restore my entire system?*_
You can restore your entire system from it's backups, unless you excluded System folders (see item #11).
But do not try this full system restore from a *different Mac's* backups. If it boots at all, many things will likely go wrong. See these Apple articles for details: http://support.apple.com/kb/HT2186 and http://support.apple.com/kb/TS3243 Instead, boot from your Install disc, erase your internal HD, install OSX, then use +Setup Assistant+ (see item #19 ).
To restore your entire system, you need the Leopard or Snow Leopard Install disc that came with your Mac (gray), or any retail Leopard (black) or Snow Leopard (white) disc. It doesn't matter what version it is (and doesn't violate the license if you borrow one), since you won't be loading OSX from it, just using the Installer utility. You can use either a Leopard or Snow Leopard disc to restore a Leopard backup, but only a Snow Leopard disc to restore a Snow Leopard backup.
If you backed-up multiple drives/partitions, note that this procedure will restore one OSX drive/partition at a time. Use the normal Time Machine "Star Wars" interface to restore data-only drives or partitions (see item #15).
If your backups are on a Time Capsule, connect to it via an Ethernet cable if possible; it will be much faster than WIFI. If your backups are on a disk connected to a Time Capsule or Airport Extreme, or a shared drive on another Mac on the same local network, connect it directly to your Mac if possible. It will be much faster than Ethernet or WIFI.
|
a. Boot from the Leopard/Snow Leopard disc. Insert it and either wait for the +Mac OS X Install DVD+ window and double-click the "Install" icon; or power down, then start up normally while holding down the "C" key. That takes a few minutes.
b. Select your language from the list shown. On the next screen, select Utilities from the top menubar.
c. If you're restoring to a new disk, or one that may not be formatted properly, select +Disk Utility+ from the list of Utilities in the menubar, and format the drive: Select the top line (with the make and size), click the Partition tab and select +1 Partition+ from the the pop-up menu under *Volume Scheme.*
Give it a name (probably +Macintosh HD)+ under *Volume Information,* and select +Mac OS Extended (Journaled)+ for the Format unless you're certain you need +Mac OS Extended (Case-sensitive, Journaled).+ Click the Options button below the box, and select GUID for an Intel Mac, or +Apple Partition Map+ for a PPC Mac and click the OK button, then Apply. That should only take a few moments. Quit Disk Utility and you should see the Utilities menu again.
d. Select +Restore from Backups+, and follow the on-screen instructions:
e. You'll be prompted to select the disk where your TM backups are (or search for a Time Capsule). If you're restoring from a network drive (instead of connecting it directly), click the Airport icon in the Menubar and join the network.
f. You'll next be prompted to select which of the backups you want, and, if you backed-up multiple OSX drives/partitions, which one to restore from. There will be a list showing the date & time of each completed backup of the disk selected, and the version of OSX on that backup. Note that the times on the list may not match your current time zone: they may be shown in *U.S. Pacific Time.*
g. You're also prompted to select a destination (probably your internal HD), then a confirmation, then the process starts.
h. If you want to monitor the installation, select Window, then +Show Log+ and +Show All logs+ from the menubar.
|
This is, naturally, a lengthy process, but your Mac will be restored exactly as it was at the time of the backup you selected (unless, of course, you excluded things from TM backups). Then your Mac will start up normally.
When it does, you should immediately turn Time Machine off, as it's next backup will probably be a full one -- everything it just restored is considered changed and will be backed-up again. You cannot prevent this, only delay it. It will of course take quite a while, and a lot of space on your TM disk, so you may wish to wait until you're sure your system is the way you want it, or even erase your TM disk with Disk Utility and let your backups start anew.
+Go to Top+
_*15. How do I restore selected items?*_
Time Machine has special handling for the data in these Apple applications: *Address Book, Mail,* and iPhoto. See below.
All other data (including apps) is handled via the Finder. There's a demonstration of two ways in the Time Machine Tutorial. With a Finder window open, +Enter Time Machine.+ Locate the item you want to restore in the "cascade" of Finder windows, select it, click Restore in the lower right, and TM will put the selected version in the same place it was saved from.
Note that what you see once you're in Time Machine depends on how your Finder window appeared before you clicked the TM icon. If you were on your Desktop, you'll see a Finder window showing only your desktop; if on your home folder, when you get into TM, that's what you'll see. Once there, you cannot add a sidebar for other selections, or the toolbar (you may need the "gear" icon) by clicking the lozenge in the upper right. If you need these, select them before entering Time Machine.
|
*Address Book*
Start with the +Address Book+ application, then click the Time Machine icon in your Dock.
Navigate to the desired backup, select whatever you want to restore, and click the Restore button.
Note that you cannot restore Address Book data to an alternate location via this method.
*Apple Mail*
Start with the Mail application, then click the Time Machine icon in your Dock.
Navigate to the desired backup, select the mailbox you want to restore from (and individual messages if desired), and click the Restore button.
TM will make a new folder named +Time Machine+ in the +On My Mac+ section, containing a +Recovered Messages+ mailbox. This avoids duplicating messages in the selected mailbox; you can move or delete individual messages wherever you wish.
If you restore additional mailboxes or messages, Time Machine will make a separate +Recovered Messages-n+ mailbox for them.
Note that you cannot restore Mail data to an alternate location via this method.
iPhoto
Start with the iPhoto application, then click the Time Machine icon in your Dock (or +File > Browse Backups+ from the menubar.
Navigate to the desired backup. Select the photo(s) you want to restore , and click the Restore button (or, to restore them all, click +Restore All).+
Note that you cannot restore iPhotos to an alternate location via this method.
|
In most cases, if you +Enter Time Machine+ with an item selected that wasn't present (or was excluded) when some of the backups were done, those backups will be grayed-out in the Timeline on the right, and you can't select them. For example, if you recently created a new mailbox, and +Enter Time Machine+ from Mail with that mailbox selected, only backups made since that mailbox was created will appear normally; earlier ones will be grayed-out.
+Go to Top+
_*16. How can I restore a file/folder to an alternate location?*_
First, if you're on Leopard, be sure you have the "action" or "gear" icon in your Finder's toolbar +(Finder > View > Customize Toolbar).+ If there's no toolbar, click the lozenge at the upper-right of the Finder window's title bar.
Then locate and select the desired item as above, click the "gear" icon in the Finder window (or, on Snow Leopard, right-click it), then +Restore <item selected> to ...".+
Then you'll see a prompt where you can select a location, and TM will place it there.
To use the backups from a different Mac, see item #17.
+Go to Top+
_*17. How can I see my backups, or the Backups for a different Mac, via +Time Machine+ ?*_
TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on the same disk/partition.
Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac.
To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by right-clicking the TM icon in your Dock.
You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" display, where you should see all the backups on that disk/partition.
If the backups you want were made over a network, you may have to manually mount the +sparse bundle+ they're in, by double-clicking it via the Finder, for them to show up in the selection screen.
You may not be able to restore such items normally, to their original location; you'll need to restore them to an +alternate location+ per item #16.
+Go to Top+
_*18. How can I copy my TM backups to a different location?*_
In many cases, you can copy your Time Machine backups to a new location, with some restrictions:
If your backups were made to an internal or directly-connected USB or FireWire disk or partition, you must copy all the backups for all the Macs that were backed-up to the same disk/partition that way.
You cannot pick and choose a group of individual backups to copy -- it's "all or nothing."
You cannot merge two or more sets of backups, even for the same Mac.
|
Part of the complexity here is because Time Machine stores it's backups differently depending on how they were made:
+*Local backups+* (made to an internal disk or a USB or FireWire disk connected directly to a Mac) are stored in a folder named "Backups.backupdb", at the top level of the drive/partition.
+*Network backups+* (made over a network, whether via WIFI or Ethernet) are stored inside a +*sparse bundle+* at the top level of the drive, in a folder named "Backups.backupdb".
Normally, you cannot just switch from one method to the other.
|
The method of copying is different for Leopard and Snow Leopard; how the backups were made; and whether you're changing from local to network, or vice-versa.
Note that below, a "volume" is either an entire disk drive or a partition on a disk drive.
Unless the new volume is a Time Capsule's internal HD (which is pre-formatted), it must be formatted per item #5, especially the pink box there (with a couple of exceptions noted below).
Before starting to copy, de-select the old destination via TM Preferences (select "none"). When done, select the new destination.
Copying backups will take a long time under the best of circumstances; even a small set of backups will contain +several hundred thousand+ files; a large one may number in the millions.
If the copy fails, and everything else seems correct, try Repairing the old backups, per #A5 in the Time Machine - Troubleshooting *User Tip.*
|
_*To copy LOCAL BACKUPS from one volume to another LOCAL VOLUME:_*
*SNOW LEOPARD:* See the *Mac OS X v10.6: How to transfer your back ups from your current hard drive to a new hard drive* section, towards the bottom of this Apple article: http://support.apple.com/kb/HT1427 Note that if the old volume is formatted +Mac OS Extended (case-sensitive, journaled),+ the new one must be formatted the same.
Or, use the procedure for Leopard:
LEOPARD: You cannot copy +*local backups+* properly from one volume to another via the Leopard Finder. But you can duplicate the backups to a different volume via Disk Utility (in your Applications/Utilities folder).
Note that you must duplicate an *entire volume* to another *entire volume* -- if you have other items on the old volume, they will be copied, too (this is a bad idea: see question #3 above). Also, any data already on the new volume will be erased.
|
a. Via Time Machine Preferences, de-select the volume (select "none"). Quit System Preferences.
b. Be sure to format the new drive correctly. See item #5 for instructions.
c. Connect both drives to your Mac, via separate ports if possible, then open a Finder window. Make sure both volumes are shown in the sidebar (if not, from the Menubar select Preferences > Sidebar, and check the box to show +External disks+ in the sidebar). Leave the Finder window open.
d. Start Disk Utility, select either volume (indented under the main drive line), and click the Restore tab.
e. Drag the old volume to the Source box, and the new volume to the Destination box.
f. Check the +Erase destination+ box, then the Restore button. This may take a long time.
g. When the duplication is complete, note that Disk Utility has *+changed the name+* of the destination volume to be the same as the source. You do not want to leave it that way, so immediately rename one of them. In the sidebar of the Finder window opened above, right-click the one you want to rename. When done, look back at the Disk Utility display to be sure you renamed the right one, then quit Disk Utility.
|
_*To copy TIME CAPSULE BACKUPS to ANOTHER TIME CAPSULE:_*
See the *Time Capsule and Mac OS X v10.6: How to transfer your back up from an existing Time Capsule to a new one* section towards the bottom of this Apple article: http://support.apple.com/kb/HT1427
_*To copy NETWORK BACKUPS to a USB drive to be used on a NETWORK (or to a Time Capsule):_*
*SNOW LEOPARD:* First, configure Time Machine to back up to the new network location, and start a backup. As soon as the +sparse bundle+ is created, cancel the backup. Then, if possible, connect the new drive directly to your Mac (or the Time Capsule via Ethernet). Use the Finder to mount the new sparse bundle, and delete the Backups.backupdb folder inside it. Then drag the Backups.backupdb folder from the old +sparse bundle+ to the new +sparse bundle.+
LEOPARD: If possible, connect the new drive directly to your Mac (or the Time Capsule via Ethernet). Use the Finder to drag the +sparse bundle+ from the old volume to the new one. The problem here is, the copied sparse bundle will have the same +maximum size+ as the old one, so it may not be able to use the entire volume for backups.
_*To copy NETWORK BACKUPS to be used LOCALLY:_*
*SNOW LEOPARD:* Connect the old drive directly to your Mac if possible. Use the Finder to mount the old sparse bundle, then drag the Backups.backupdb folder from the sparse bundle to the top level of the new volume. Note that in this case, the new volume must be formatted +Mac OS Extended (case-sensitive, journaled).+
LEOPARD: Network backups cannot be copied to be used locally.
_*To copy LOCAL BACKUPS to be used on a NETWORK:_*
*SNOW LEOPARD:* First, configure Time Machine to back up to the network location, and start a backup. As soon as the +sparse bundle+ is created, cancel the backup. Then, if possible, connect the new drive directly to your Mac. Use the Finder to mount the new sparse bundle, and delete the Backups.backupdb folder inside it. Then drag the Backups.backupdb folder from the old volume to the new +sparse bundle.+
LEOPARD: Local backups cannot be copied to be used on a network.
+Go to Top+
_*19. How do I set up a new Mac from my old Mac's backups?*_
The easiest way to set up a new Mac if you already have a Mac, is to use +Setup Assistant,+ which starts automatically when you start up your shiny new Mac.
There's a little demonstration of this towards the end of the Time Machine Tutorial.
First, you'll see a Welcome video in many languages, then a screen to select your Country, then one to select your Keyboard.
The next screen says "Do you already own a Mac?" and "Would you like to transfer" followed by four options:
From another Mac
From another volume on this Mac
From another Mac's Time Machine Backups
Do not transfer
To transfer directly from another Mac, you must connect them via FireWire cable, Ethernet cable, or an Airport; and start up the other Mac in +Target Disk+ mode (start up while holding down the T key).
To transfer from Time Machine backups, they can be on an external FireWire or USB drive, or a Time Capsule. If they're on a Time Capsule, connect to it via Ethernet cable if possible. If they were made on a USB drive connected to a Time Capsule or Airport, connect the drive directly to your Mac if possible. If the backups are on an internal HD on another Mac, connect that Mac in +Target Disk+ mode as above.
If you have a "clone" of your old Mac on an external HD, made via CarbonCopyCloner, SuperDuper, or the like, it's the equivalent of the old Mac: select +From Another Mac+ and connect the drive.
If you selected +Time Machine backups,+ then select your TM backups on the next screen. (If they're not shown, connect the drive, or click Join if they're on a Time Capsule).
Next is the selection for what you want to transfer. You'll see four checkboxes:
Users
Applications
Settings
Other Files and Folders
These are "yes" or "no" selections: you can select which users to transfer, but otherwise you can't pick and chose individual items in those categories.
In nearly all cases, select all four and click the Transfer button (as soon as it completes calculating all the sizes). +Setup Assistant+ will then transfer everything; when you restart, your Mac will be just like the old one: users, passwords, configuration, etc.
Note that +Setup Assistant+ is smart enough not to replace newer Apple apps that came with the new Mac with older versions from the backups.
In some cases, there may be a few exceptions:
If transferring from a PPC Mac to an Intel Mac, some PPC applications may not work properly, or at all. See this Apple article: http://support.apple.com/kb/TS1963?viewlocale=en_US
You may have to re-enter serial numbers/purchase codes for some 3rd-party applications.
Very rarely, complex 3rd-party apps that were installed with special installers, and put files in unexpected places, may need to be reinstalled (using their installer) to work properly.
+Go to Top+
_*20. Once my Mac is backed-up, can I delete some stuff to save space?*_
+*NO, NO, NO !+* That is a +*terrible idea !+*
First, the whole point of a good backup strategy is to have (at least) two copies of everything important, in (at least) two separate places. If you delete the originals, you no longer have backups! When your TM drive fails (and all disk drives fail, sooner or later), you risk losing your +*only remaining copy.+*
Second, Time Machine will, eventually, delete the backup copies of anything that's no longer on your system. The timing varies, depending on how long things were on your system before being deleted, how often backups were run, and how much space is on your TM drive: it may be as long as your oldest backup, or as short as 24 hours.
+Go to Top+
_*21. How do I set up Time Machine to an internal or directly-connected external HD?*_
If you connect an external drive to your Mac, and Time Machine is not set up, OSX will ask if you want to use the drive for Time Machine backups. If you click the +Use as Backup Disk+ button, it will set up Time Machine automatically.
But there may be some problems with that, so we recommend doing it this way:
First, set up the drive for use with Time Machine. See item #5 for instructions on setting up a new drive, or one without any data you want to keep. See item #6 to add a partition for Time Machine to an existing drive that already has data that you want to keep.
Next, if the +Time Machine+ application isn't already in your Dock, drag it there from your Applications folder.
Right-click it and select +(Open) Time Machine Preferences.+ Check the box to +Show Time Machine status in the menu bar+ and click the +Select Disk+ button (on Leopard, this will be either +Choose Backup Disk+ or +Change Disk.)+ Select the desired drive/partition from the list and click the +Use for Backup+ button.
In the +Next Backup+ area of the TM Preference panel there should be a 120-second countdown until the backup starts.
Note that the first backup will copy the entire contents of your system, except for a few things that are skipped automatically, such as system work files, most caches, your logs, trash, etc., and anything else you may have excluded (see item #10 and item #11) so it will be rather lengthy, depending on how much data is on your system, how your Time Machine disk is connected, and how busy your Mac is.
You can continue to use your Mac while TM is backing-up, and you can even cancel a backup if necessary, but to make the first full backup as fast as possible, try not to overload your Mac or cancel the backup.
See item #24 for information on the two Time Machine icons you just added.
+Go to Top+
_*22. How do I set up Time MachiHi, Nubz!
Yes, I just saw that, and am still chuckling.
Maybe that will mollify the Jive gods?
Thanks again,
Jim -
Useful Interview Questions and Answere
Hi All
Some of the Real time question.
Q) Under which menu path is the Test Workbench to be found, including in earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
Q) I want to delete a BEx query that is in Production system through request. Is anyone aware about it?
A) Have you tried the RSZDELETE transaction?
Q) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many process types, for example after loading data into Info Cube, you rollup data into aggregates, now this rolling up of data into aggregates is a process type which you keep after the process type for loading data into Cube. This rolling up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything OK -
Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource delta enabled. While creating datasource from RSO2, after entering datasource name and pressing create, in the next screen there is one button at the top, which says generic delta. If you want more details about this there is a chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views, SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta attribute
Q) Workbooks, as a general rule, should be transported with the role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has never been transported, and then you have a choice of transporting the role (recommended) or just the workbook. If only the workbook is transported, then an additional step will have to be taken after import: Locate the WorkbookID via Table RSRWBINDEXT (in Dev and verify the same exists in the target system) and proceed to manually add it to the role in the target system via Transaction Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both the role and workbook. Keep in mind that a workbook is an object unto itself and has no dependencies on other objects. Thus, you do not receive an error message from the transport of 'just a workbook' -- even though it may not be visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into an infocube?
A. This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
Q) What are the five ASAP Methodologies?
A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase, decision makers define clear project objectives and an efficient decision making process (i.e. Discussions with the client, like what are his needs and requirements etc.). Project managers will be involved in this phase (I guess).
A Project Charter is issued and an implementation strategy is outlined in this phase.
2. Business Blueprint: It is a detailed documentation of your company's requirements. (i.e. what are the objects we need to develop are modified depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing, conducting pre-go-live, end user training etc.
End user training is given that is in the client site you train them how to work with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production. The Project team will be supporting the end users.
Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not sure.
Then Landscape of b/w: u have the development system, testing system, production system
Development system: All the implementation part is done in this sys. (I.e., Analysis of objects developing, modification etc) and from here the objects are transported to the testing system, but before transporting an initial test known as Unit testing (testing of objects) is done in the development sys.
Testing/Quality system: quality check is done in this system and integration testing is done.
Production system: All the extraction part takes place in this sys.
Q) How do you measure the size of infocube?
A: In no of records.
Q). Difference between infocube and ODS?
A: Infocube is structured as star schema (extended) where a fact table is surrounded by different dim table that are linked with DIM'ids. And the data wise, you will have aggregated data in the cubes. No overwrite functionality
ODS is a flat structure (flat table) with no star schema concept and which will have granular data (detailed level). Overwrite functionality.
Flat file datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
Q) Difference between display attributes and navigational attributes?
A: Display attribute is one, which is used only for display purpose in the report. Where as navigational attribute is used for drilling down in the report. We don't need to maintain Navigational attribute in the cube as a characteristic (that is the advantage) to drill down.
Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append fields). Refer white paper on LO-Cockpit extractions.
Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
A) Initially we don't delete the setup tables but when we do change in extract structure we go for it. We r changing the extract structure right, that means there are some newly added fields in that which r not before. So to get the required data (i.e.; the data which is required is taken and to avoid redundancy) we delete n then fill the setup tables.
To refresh the statistical data. The extraction set up reads the dataset that you want to process such as, customers orders with the tables like VBAK, VBAP) & fills the relevant communication structure with the data. The data is stored in cluster tables from where it is read when the initialization is run. It is important that during initialization phase, no one generates or modifies application data, at least until the tables can be set up.
Q) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the information has to be updated online. For designing the Virtual cube you have to write the function module that is linking to table, Virtual cube it is like a the structure, when ever the table is updated the virtual cube will fetch the data from table and display report Online... FYI.. you will get the information : https://www.sdn.sap.com/sdn/index.sdn and search for Designing Virtual Cube and you will get a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes & Characteristic values.
Variable Types are
Manual entry /default value
Replacement path
SAP exit
Customer exit
Authorization
Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev-àQ and Dev-----àP
Q) What types of partitioning are there for BW?
There are two Partitioning Performance aspects for BW (Cube & PSA)
Query Data Retrieval Performance Improvement:
Partitioning by (say) Date Range improves data retrieval by making best use of database execution plans and indexes (of say Oracle database engine).
B) Transactional Load Partitioning Improvement:
Partitioning based on expected load volumes and data element sizes. Improves data loading into PSA and Cubes by infopackages (Eg. without timeouts).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. It is simple to use, but only really tells you if the extractor works. Since records that get updated into Cubes/ODS structures are controlled by Update Rules, you will not be able to determine what is in the Cube compared to what is in the R/3 environment. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. I would recommend enlisting the help of the end user community to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute and you will see the record count, you can also go to display that data. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. However, it will not tell you how many records should be expected in BW for a given load. You have that information in the monitor RSMO during and after data loads. From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3, how many targets were updated, and how many records passed through the Update Rules. It also gives you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data target its better u write in transfer rules because u can assign one InfoSource to more than one data target & and what ever logic u write in update rules it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a routine in the tab strip key figure calculation, by choosing checkbox Return table. The corresponding key figure routine then no longer has a return value, but a return table. You can then generate as many key figure values, as you like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose you want to restrict (delete) some records based on conditions before getting loaded into data targets, then you can specify this in update rules-start routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no: of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. A LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer.
A) There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted.
You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.
Q) Why does the number in the 'Total' column in the overview screen of Transaction RSA7 differ from the number of data records that is displayed when you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also first question) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both, the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. Thus, only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7, a possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
A) Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor (delta for master data using ALE change pointers). Such a DataSource should not be displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update. Please note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the DeltaQueue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of defining the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. You do not only delete all data of this DataSource for the affected BW System, but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding target system are confirmed. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name are 19 characters long or shorter, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show data loaded into BW during the last delta but also data that were newly added, i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits.
Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing the BW Support or only if this is explicitly requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
A) The collective run submits the open V2 documents for processing to the task handler, which processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If a user started the internal mode at a time when the delta initialization was still active, he/she posts data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards new delta records were written to the DeltaQueue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the DeltaQueue are listed via the detail display. Why are the data displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend to reset the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the DeltaQueue may grow to without facing the danger of a read failure due to memory problems?
A) There is no strict limit (except for the restricted number range of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
When estimating "smooth" limits, both the number of LUWs is important and the average data volume per LUW. As a rule, we recommend to bundle data (usually documents) already when writing to the DeltaQueue to keep number of LUWs small (partly this can be set in the applications, e.g. in the Logistics Cockpit). The data volume of a single LUW should not be considerably larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1GByte per work process, 100 Mbytes per LUW should not be exceeded). That limit is of rather small practical importance as well since a comparable limit already applies when writing to the DeltaQueue. If the limit is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data are fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than 1 million LUWs are read and fetched from the database per DeltaRequest. If this limit is reached within a request, the DeltaQueue must be emptied by several successive DeltaRequests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs already when the number of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the report. Usually, we load the transactional data nightly. Is there any easy way to include this information on the report for users? So that they know the validity of the report.
A) If I understand your requirement correctly, you want to display the date on which data was loaded into the data target from which the report is being executed. If it is so, configure your workbook to display the text elements in the report. This displays the relevance of data field, which is the date on which the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS. THROUGH WHICH NETWORK.
a) VPN .Virtual Private Network, VPN is nothing but one sort of network where we can connect to the client systems sitting in offshore through RAS (Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and goto sm12
TCode then unlock it this is happened when lock errors are occurred when u scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in the rows?
A) Expand dimension under left side panel (that is infocube panel) select than navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former have an improved write access performance level. Standard InfoCubes are technically optimized for read-only access and for a comparatively small number of simultaneous accesses. Instead, the transactional InfoCube was developed to meet the demands of SAP Strategic Enterprise Management (SEM), meaning that, data is written to the InfoCube (possibly by several users at the same time) and re-read as soon as possible. Standard Basic cubes are not suitable for this.
Q) Is there any way to delete cube contents within update rules from an ODS data source? The reason for this would be to delete (or zero out) a cube record in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only possible to avoid that some content is updated into the InfoCube using the start routine. Loop at all the records and delete the record that has the condition. "If the open order quantity was 0" You have to think also in before and after images in case of a delta upload. In that case you may delete the change record and keep the old and after the change the wrong information.
Q) I am not able to access a node in hierarchy directly using variables for reports. When I am using Tcode RSZV it is giving a message that it doesn't exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards, it's possible in the Query Designer (BEx) itself. Just right click on the InfoObject for which you want to use as variables and precede further selecting variable type and processing types.
Q) Wondering how can I get the values, for an example, if I run a report for month range 01/2004 - 10/2004 then monthly value is actually divide by the number of months that I selected. Which variable should I use?
Q) Why is it every time I switch from Info Provider to InfoObject or from one item to another while in modeling I always get this message " Reading Data " or "constructing workbench" in it runs for minutes.... anyway to stop this?
Q) Can any one give me info on how the BW delta works also would like to know about 'before image and after image' am currently in a BW project and have to write start routines for delta load.
Q) I am very new to BW. I would like to clarify a doubt regarding Delta extractor. If I am correct, by using delta extractors the data that has already been scheduled will not be uploaded again. Say for a specific scenario, Sales. Now I have uploaded all the sales order created till yesterday into the cube. Now say I make changes to any of the open record, which was already uploaded. Now what happens when I schedule it again? Will the same record be uploaded again with the changes or will the changes get affected to the previous record.
A)
Q) In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
A) Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics). I hope this helps.
We used ABAP Routines for example:
To convert to Uppercase (transfer structure)
To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure)
To select only a part of the data for from an infosource updating the InfoCube (Start Routine) etc.
Q) What is ODS?
A) An ODS object acts as a storage location for consolidated and cleaned-up transaction data (transaction data or master data, for example) on the document (atomic) level.
This data can be evaluated using a BEx query.
Standard ODS Object
Transactional ODS object:
The data is immediately available here for reporting. For implementation, compare with the Transactional ODS Object.
A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions ((new) delta, active, (change log) modified), where as a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application. In BW, you can use a transaction ODS object as a data target for an analysis process.
The transactional ODS object is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object is accessed transactionally, that is, data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible.
It offers no replacement for the standard ODS object. Instead, an additional function displays those that can be used for special applications.
The transactional ODS object simply consists of a table for active data. It retrieves its data from external systems via fill- or delete- APIs. The loading process is not supported by the BW system. The advantage to the way it is structured is that data is easy to access. They are made available for reporting immediately after being loaded.
Q) What does InfoCube contains?
A) Each InfoCube has one FactTable & a maximum of 16 (13+3 system defined, time, unit & data packet) dimensions.
Q) What does FACT Table contain?
A FactTable consists of KeyFigures.
Each Fact Table can contain a maximum of 233 key figures.
Dimension can contain up to 248 freely available characteristics.
Q) How many dimensions are in a CUBE?
A) 16 dimensions. (13 user defined & 3 system pre-defined )
Q) What does SID Table contain?
SID keys linked with dimension table & master data tables (attributes, texts, hierarchies)
Q) What does ATTRIBUTE Table contain?
Master attribute data
Q) What does TEXT Table contain?
Master text data, short text, long text, medium text & language key if it is language dependent
Q) What does Hierarchy table contain?Hi DST
This is a great effort and gesture. thank you on behalf of all the newbies.
PJ -
Questions on installtion and ram please help! Pc tech with new Job!
Im a Pc tech with a new job Im am in charg with a new Mac network . So Im great at PC.s just fuzzy on Macs.
Here is my problem.
IMac 17" flat panel.
New Hard drive , new cable (IDE), Tryed to install New OS ( just OS X) got throught the first 5 mins in the installer , the it stoped and told me that it had encountered an error and to restart.
Now I get an error 139 installer has unexspetanly stopped.
Press return to reboot.
Now pressing return never works have to hold start button to reboot.
Ran hardware test of cd Im gettting a a mem_/2/4 error.
I assusm that is a bad stick of memory? There is only 1 stick in there.
I belive that its using pc133 256meg for memory.
I have put a few pc133 sticks in the mac but none will work eather get a bad memory beep or no display .
Does it have to mac memory or special latency ?
Have opened the firmware and reset -all -nvram and defaults
Have remove Air Port card and all other stuff , onlly keyboard and mouse and power cord .
Does that sound right? If you need more info let me know.
Any other clues?
Any book that an tech like me (6 years fixing pcs) should read for macs? thanks for all your help in advance.
James
G5 Mac OS X (10.2.x)Another thing to consider, a free to use download (donationware) is
MacTracker; a small data base of Apple and Macintosh product specs.
If you don't already have it, see: http://www.mactracker.ca to download.
Some online manual sites had unauthorized copies of protected works
and those sites were pulled from the internet; but they had service
manuals in pdf for many models of computers. You may be able to get
the official versions of pdf manuals through a subscription service for
an annual fee; this may require searching and asking questions. It may
also require an IT budget you may not have, to get a Mac-only archive.
At one point I was given some technical support information to trouble-
shoot my own ailing under warranty Apple computer(s) and the information
is very helpful, when you have a need for the details they contain.
I was careful to use them for non-invasive troubleshooting only.
One older online source appears to have ftp:// links, but I was never
able to make them work. The site may not have valid content or could
be somehow blocked; so if you find such a site by searching for older
Apple Manuals online, it may not yield anything. Or it may be illegal.
Some of the low-end RAM chips can be problematic; I found at least
one to add major issues in my iMacG4 and made it hard to diagnose
another major hardware problem. Tossing the cheaper RAM (at retail
was higher cost than decent RAM) was the best thing; got a better one.
There should be a little information on boot ROM (firmware) per model in
the MacTracker database you can use offline. You may need to know more
about the use of Open Firmware in Macs. Hope this helps some.
PS: for a time, you could get tech manuals on CD from places
such as http://www.applerescue.com/ (they have OS installers
on disc for sale there, primarily) and also a search of the web
may get you a source of tech books for repair service. -
Hy Gurus
I am new to BW.
Can u please let me know the answers for the following Qs.
1. What is a Data warehouse? List Few Properties of a Data warehouse.
2. What are the major challenges of any Data Warehouse design?
3. Data loading issues, Reporting, Production support issues?
4. Data Modeling, Info cube, ODS obj creation?
5. SAP Batch process in BW side?
6. How to schedule the Background jobs in ABAP, & BW?
7. Variables in Query? User exit variables? How do u create user exit variable? And wt u have used?
8. Structures in Query Reporting? What are structures?
9. Transportation steps?
10. How to compress the Info cube? What happens when you compress the info cube?
11. Performance issues in Reporting? How can you improve the performance of the query?
12. Where the ABAP routines are used in BW side?
13. How to create Primary index & secondary indexes on ODS?
14. How to prevent the duplicate records at the data target level?
15. Issues regarding double records?
16. Info sets and multiprovider differences?
17. Issues faced in Delta loading? Why it happened?
Enhancements to the Data sources?
18. Issues in loading the data from Flat files? Delta load issues? Which will u suggest for flat file loading is it delta or full load?
19. How to prevent the Replication Errors? What happens when you replicate the Data Sources?
20. Process chain steps? Which process type is used to delete the last request when loading the data?
21. What is virtual cube? Characteristics? Its significance?
22. Diff. methods for Generic Data Sources?
23. What is Extract structure? Where it is used?
24. Data Modeling design issues, Tech specifications, Modeling , Reporting, Testing, Transportation
25. Extraction on R/3 side steps?LOs
26. How do you setup LIS?
27. SAP Batch process? /.where does u setup batch process?
28. Reconstruction tab in Info cube? Why it is used?
29. Suppose Info cube (A) having 10 records.
We want to take the some records say 4-7 from Info cube (A) -- Info cube (B).
How does u handle the situation?
30. Suppose ODS contains 5 records and the Info cube shows 12 records. How to solve it?
31. Landscape
32. Tell me typical BW Team & How u work?
33. How to Maintain the Master data at Client Server architecture?
34. Query performance problems? How does u improve the performance?
35. How does u improve the Info cube design performance?
36. How do you improve the Dimension & fact table performance?
37. How to push data from PSA to ODS?
38. How to postpone daily load?
39. The functions of Administrator Workbench are
40. What is RECORD MODE
41. What is partition? How to partition the Info cube & PSA. ?..
42. How to filter single records when uploading into an ods object?
43. How can u connect a new data target to an existing data flow?
44. When it is advantageous to create secondary indexes for ODS field?
45. Purpose of setup tables?
46. What is Delta mechanism?
47. Will u create an infosourse for every data souse? How many infosourse can we connect to a Data Sources?
48. What is a Star Schema? What is the Differences between a Classic Star Schema & Extended Star schema.
49. What is an Attribute? Difference between Display Attribute & Navigational Attribute?
50. What is Transfer Rule? List the methods used in Transfer Rules.
51. Why we need ODS? /List a few of the technical settings that can be defined when building/modifying an ODSObject?
52. What is ODS? What are the three tables associated with an ODS object? What are the two types of ODS.
53. Name the two tables that provide detailed information about data sources.
54. What are two data transfer methods? Which is the preferred method and why?
55. Where will the development take place?& Who will do the development testing.
56. Who will be responsible for long-term support?
57. What is a Slowly Changing Dimension?
58. What is namespace for SAP BW?
59. What are nine decision points of Data warehouse
60. How does u install BW Statistics? How you enable monitoring using BW Statistics.
61. How do u rate u r self in Modeling, Reporting & Extraction.
62. What are the advantages with LO Extraction.
63. What are the steps in General to enhance data?
64. What are Phases in ASAP Methodology?
65. What is the 90 Day rule?
66. What is the demo content use?
67. What is the use of RSRAJ Transaction?
68. What is the use of RSSU53 Transaction?
69. Can u repeat the Master Data Source?
70. What is diff. b/w DW and BW?
71. Will u use idol methods in BW?
72. What does the number in the 'Total' column in Transaction RSA7 mean?
73. The extract structure was changed when the Delta Queue was empty. Afterwards new delta records were written to the Delta Queue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the Delta Queue are listed via the detail display. Why are the data displayed differently? What can be done?
74. How and where can you control whether a repeat delta is requested?
75. Can I use several clients within SAP BW?
Thanks in Advance
muraliHi
I have few questions and answer u can check it out which would be more helpful
Solution
Questions and answers.
Question 1:
What does the number in the 'Total' column in Transaction RSA7 mean?
Answer:
The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repeating a delta request) and the LUWs for the next delta request. An LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
Question 2:
What is an LUW in the delta queue?
Answer:
An LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet from an application extractor.
Question 3:
Why does the number in the 'Total' column, in the overview screen of Transaction RSA7, differ from the number of data records that are displayed when you call up the detail view?
Answer:
The number on the overview screen corresponds to the total number of LUWs (see also question 1) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. This means that only the records that are ready for the next delta request are displayed on the detail screen. The detail screen of Transaction RSA7 does not take into account a possibly existing customer exit.
Question 4:
Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
Answer:
Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded into the BW System. The LUWs of the previous delta may then be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change if the first delta is loaded into the BW System.
Question 5:
Why are selections not taken into account when the delta queue is filled?
Answer:
Filtering according to selections takes place when the system reads from the delta queue. This is necessary for performance reasons.
Question 6:
Why is there a DataSource with '0' records in RSA7 if delta exists and has been loaded successfully?
Answer:
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor . You can display the current delta data for these DataSources using TA RSA3 (update mode ='D')
Question 7:
Do the entries in Table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
Answer:
The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area, and so on).
Caution: As of PlugIn 2000.2 patch 3, the entries in Table ROIDOCPRMS are as effective for the delta queue as for a full update. Note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the delta queue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
Question 8:
Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
Answer:
With PlugIn 2001.1 the display was changed: you are now able to define the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition, and so on.
Question 9:
What is the purpose of the function 'Delete Data and Meta Data in a Queue' in RSA7? What exactly is deleted?
Answer:
You should act with extreme caution when you use the delete function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. Not only do you delete all data of this DataSource for the affected BW System, but you also lose all the information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
When you delete the data, this confirms the LUWs kept in the qRFC queue for the corresponding target system. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
The delete function is intended for example, for cases where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
Question 10:
Why does it take so long to delete from the delta queue (for example half a day)?
Answer:
Import PlugIn 2000.2 patch 3. With this patch the performance during deletion improves considerably.
Question 11:
Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
Answer:
It is most likely that a delta initialization had not yet run or that the the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data to be written to the delta queue.
Question 12:
What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
Answer:
The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name is shorter than 20 characters, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in Table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
Question 13:
Why is there data in the delta queue although the V3 update has not yet been started?
Answer:
You posted data in the background. This means that the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
Question 14:
Why does the 'Repeatable' button on the RSA7 data details screen not only show data loaded into BW during the last delta but also newly-added data, in other words, 'pure' delta records?
Answer:
It was programmed so that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
Question 15:
I loaded several delta inits with various selections. For which one
is the delta loaded?
Answer:
For delta, all selections made via delta inits are summed up. This
means a delta for the 'total' of all delta initializations is loaded.
Question 16:
How many selections for delta inits are possible in the system?
Answer:
With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits.
Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code which may exceed the memory limit.
Question 17:
I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
Answer:
Before you copy a source client or source system, make sure that your deltas have been fetched from the delta queue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.
Question 18.
Am I permitted to use the functions in Transaction SMQ1 to manually control processes?
Answer:
Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing BW Support or only if this is explicitly requested in a note for Component 'BC-BW' or 'BW-WHM-SAPI'.
Question 19.
Despite the delta request only being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
Answer:
The collective run submits the open V2 documents to the task handler for processing. The task handler processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
Question 20.
Despite deleting the delta init, LUWs are still written into the DeltaQueue
Answer:
In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If you started the internal mode at a time when the delta initialization was still active, you post data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
Question 21.
In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the Table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
Answer:
Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this still does not mean that the record has successfully reached the BW. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the delta queue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a delta extraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which confirms and deletes records loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status indicates an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903). However the value 'U' in field 'NOSEND' of table TRFCQOUT is of concern.
Question 22.
The extract structure was changed when the delta queue was empty. Afterwards new delta records were written to the delta queue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the delta queue are listed via the detail display. Why is the data displayed differently? What can be done?
Answer:
Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend resetting the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta. When the problem occurs, the delta needs to be re-initialized.
Question 23. How and where can I control whether a repeat delta is requested?
Answer:
Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for any reason, manually set the request in the monitor to red. For the contents of the repeat, see Question 14. Delta requests set to red when data is already updated lead to duplicate records in a subsequent repeat, if they have not already been deleted from the data targets concerned.
Question 24.
As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
Answer:
See the recommendation in Note 505700.
Question 25.
Are there particular recommendations regarding the maximum data volume of the delta queue to avoid danger of a read failure due to memory problems?
Answer:
There is no strict limit (except for the restricted number area of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
When estimating "soft" limits, both the number of LUWs and the average data volume per LUW are important. As a rule, we recommend bundling data (usually documents) as soon as you write to the delta queue to keep number of LUWs low (this can partly be set in the applications, for example in the Logistics Cockpit). The data volume of a single LUW should not be much larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1 GByte per work process, 100 MByte per LUW should not be exceeded). This limit is of rather small practical importance as well since a comparable limit already applies when writing to the delta queue. If the limit is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data is fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not exceed one delta request per hour.
To avoid memory problems, a program-internal limit ensures that no more than 1 million LUWs are ever read and fetched from the database per delta request. If this limit is reached within a request, the delta queue must be emptied by several successive delta requests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs as soon as the number of LUWs reaches a 5-digit value.
THANKS =POINTS in SDN
SANJEEV -
How do i diagnose a network access error with Gracenote or other sites??
Ok, this is not strictly itunes but here goes.
Since i upgraded to 7.2 about 3 weeks ago, i have had only 50% success in accessing gracenote when i put a cd in (ie this morning around 10am no problem, now at 5pm can't get to it). My internet connection is AT&T DSL. It comes with a connection diagnosing tool which never says there is a problem, windows xp connection diagnosing tool says no problem, and yet there are certain websites i can now no longer get to not just gracenote via itunes. using ie or firefox i can't get to discussions.apple.com ironically (i can get to www.apple.com), so is gracenote, and occasionally the weather channel desktop, and yahoo email. i turned off all firewalls and there is no change. however. i then access my work vpn (via the at&t dsl connection, not dial up) and hey presto i can get to all these sites i couldn't before. so if i go through vpn i can always get to gracenote if i use native dsl connection i can't. i think at&T is preventing access through it's own network to parts of the web because of bandwidth issues ( i have emailed them and they say there is no problem in my area), but won't admit it, and i can't prove it. so my question is how do i prove where the network bottleneck is in accessing these sites since the tools i get say there is no problem??? or could it be a dns problem???
plz if anyone can help offline i would be so happy, it is so frustrating not being able to load cd's into itunes whenever i feel like it.How did you set up chroot?
FYI, you don't need to chroot to use pacman with a not root filesystem.
man pacman wrote:-r, --root <path>
Specify an alternative installation root (default is /). This should not be used as a way to install software into /usr/local instead of /usr. This option is used if you want to install a package on a temporary mounted partition that is "owned" by another system. NOTE: if database path or logfile are not specified on either the command line or in pacman.conf(5), their default location will be inside this root path. -
does any one know how to fix a problem with my book pro that has a gray screen with a folder with a question mark on it?
Hello Mokhtary123 and welcome to Apple Support Communities,
It will help us diagnose your problem to know the exact model, size, year built, RAM installed and OS you're running.
But basically your system can't find the boot disk. Usually this is a symptom of a dead/dying/corrupted hard drive;
A flashing question mark or globe appears when you start your Mac - Apple Support
OS X Recovery
http://support.apple.com/en-us/HT4718 -
How to diagnose flickering exported JS animations from Flash CC?
Quick stats on my system:
Macbook Pro Retina 2012 running OSX 10.9.3
Flash CC 13.1.0.226
I'm not experiencing an error so much as a lack of understanding about how to diagnose Flash CC JS export issues. Here's the backstory:
In 2012, my company started working with an contract sprite artist. I was using the CS5.5 Creative Suite, and we were exporting normal png sequences from Flash for use in the game. After about 8 months, my cofounders and I realized that we could both reduce the load time for the game and also allow our artwork to be dynamically scalable by switching to JS exports of our art rather than the raster sprite sheets. Here's the blog post we wrote about it: http://blog.codecombat.com/hacking-our-way-to-vector-artwork-in-html5
At the time, I didn't have Flash CC, and was reliant upon the CreateJS plugin to export the required JS files: CreateJS Developer Center | Adobe Developer Connection After another month or so, our contractor upgraded their version of Flash and we started having compatibility issues reading FLA files, so I upgraded as well. After doing some reading, I concluded that the CreateJS plugin was now incorporated into Flash CC as the HTML5 doc type, which was confirmed when I checked out the publish settings and resulting files.
This is all a rather long winded way of saying that we have legacy artwork created with an older version of Flash but are now importing all of our artwork from JS files.
Fast forward to today and we have two big issues:
1) We can't figure out how to reduce the filesize of JS exports. As discussed in our blog post, vector artwork has upsides and downsides. One of the downsides we've found is that complex art that uses a lot of shapes ends up being substantially larger (in terms of filesize) than the appearance might otherwise suggest. Raster exports skirt this because a pixel is a pixel, but vector exports scale with the complexity of the source FLA. I'm not a Flash expert, and when we get files that are particularly complex, Flash either runs out of memory exporting them to JS files or we get files that are far too large to reasonably use. To be clear, the "out of memory" error isn't a problem because even if Flash finished the export, the resulting files would be too large for us to use (plus, I've done some digging and found a tutorial for correcting the out of memory error). Our artist is not familiar with the intricacies of the JS Flash exporter, so when we get a file that's too big or breaks the export, neither of us can really figure out a way to correct the problem. We have three questions in particular:
a) Where can you view shape data that Flash is going to write to the JS files?
b) Is there any way to edit said shape data inside the Flash CC interface?
c) Is there any way to optimize shape data in Flash? For instance, in Photoshop, you can flatten images and export a psd with 500 layers as a single JPEG, is there any way to do something similar to shape data in Flash?
2) Exports frequently break in weird ways. Many of the sprites that we created a year ago haven't needed to be re-imported into our game engine for some time. But every once in a while, I need to go back and fix, improve, or tweak an existing sprite, and then I run smack into the issue of reconciling files that were created without thought to JS exports with our current system. Just last week I was running into this issue in a big way and I made a screencast for our artist (since we work remotely) that I hoped might give him a better idea of the problem: Flash Errors - Treasure Chest, Flippable Tile - YouTube
The two files mentioned in that screencast are both old (treasure chest) and new (flippable land tile). We have a few questions:
a) Why are the treasure chest frames "flickering" in the html5 preview? The problem doesn't appear inside Flash and is inconsistent between files. There are two FLA files: one in which the treasure chest is empty, and one in which it's full. The empty animation doesn't throw any errors, either when converting to the HTML5 doc type or on export, but the resulting animation flickers. The full treasure, on the other hand gives me 21 lines of these errors when I do the conversion (not when I export): "Blend Modes(Layer) is not supported in HTML5 Canvas document, and has been converted to Normal in an instance of Movieclip <Path>." The result in both cases is the same: the animations flicker, and neither our artist nor us can figure out why, or for that matter, even begin to troubleshoot it. This SO issue seems to describe the problem, but was never resolved, and I can't find anything else that seems to address it: CreateJS Publish of Flash Project Flickers - Stack Overflow
I've uploaded the files involved to a public dropbox folder which I think you'll be able to access (Dropbox seems to be having some problems at the moment): Dropbox - flash_debugging
Since my questions are fairly involved, and my goal is to gain a better understanding of the UI, not simply resolve an error, I'd be happy to pay for someone's expertise/time in getting me up to speed. You can get in touch with me at george [at] codecombat.comHi George,
I have taken a look at the files full_treasure_chest.fla and flippable_land.fla that you have shared via drop box and found that they both uses blank keyframe(s) followed by Keyframe(s). This was an issue and has been addressed in the latest release Flash CC 2014 (released on 18 June, 2014). Can you please install the latest build 14.0.0.110 and try this out?
Thanks!
Mohan -
Question about CPU usage for video playback
I've asked a related question already on the Safari forum, but would like some clarification, please.
The speed of this iMac is 400 MHZ and whenever I go to YouTube or almost any other site that requires video I see that the CPU usage can peak way up at 80% or more. I have Flash 9 installed which has a minimum of 500 MHZ, so I get pretty choppy video, but that's not the issue here. I can live with that. I keep any other applications closed. I'm often running a small fan over the top of the iMac to help vent the buildup of heat. I can monitor the temperature at the Hard Drive and I suppose that gives me an idea, of sorts, about general temperature conditions inside.
The answer I got was that this kind of CPU usage could be detrimental to the processor as it builds up excessive heat and to keep this kind of video to a minimum.
My question is can anyone roughly suggest what a maximum time on YouTube, for example, would be, 2 minutes, 5 minutes, is 10 minutes too long? I have plenty of RAM at 768. Some guidelines?
Thanks.Hey WZZZ,
Thanks for the star and kind words.
I'm the de facto Mac guy at my kids' school and we have around 25 iMac Slot Loaders working there. You can imagine they get abused quite a bit. There are 10 running Garage Band in the Music Department. That puts a tremendous strain on the CPU and I'm actually surprised that they run it so well. My son had a 600 iMac running GarageBand, he was complaining that it was getting jumpy and when I looked at it he was running 10 unlocked tracks simultaneously! So now he has an eMac G4 800 and that of course runs a lot better.
So to sum up, with all the abuse of those machines in terms of the CPUs the problems I have with them have nothing to do with that. The problems have more to do with parts of the OS that they toss, headphone jacks abused, CDs jammed in the slots, and the like.
A couple of other related things. I've got Hardware Monitor, demo, installed and I think it reported it could only find the hard drive sensor, if I'm not mistaken - nothing else on this Mac with a sensor. Is that right?
I see references to CPU sensors on 400 iMacs but on the 400 I have here for repair Temperature Monitor reports no sensors. Perhaps there were different versions of the 400.
But very good to hear that the fan is a good idea for CRT related things. Should I keep the fan running-mostly for that hard core CRT stuff- even if the computer is sleeping and the room temp. is only around 62-64 F.? (We need to put on warm clothes to sit in front of this thing now, but worth it to keep this old machine happy).
On the one I did the fan pushed the airflow in the direction of the passive flow of the iMac - in at the bottom and out the grill by the handle.
One more question, more out of curiosity than anything else: If I move this small clip-on fan close to the case - right now it's about 3 feet away and the image is stable - the screen begins to flicker and flutter quite a lot. My theory is that that's happening not necessarily because of electro-magnetic interference from the fan motor, but rather, because the back of the tube is getting cooled unevenly. What do you think?
Well the classic failures that I see in the iMac are in this order:
1) Dielectric breakdown of the flyback transformers internal insulation. This is heat/age related and a common problem with CRTs in general.
2) Breakdown of high voltage electolytic capacitors and regular high voltage capacitors on the neck board and PAV supply.
3) Solder problems with the flyback itself. This is diagnosed by the upside down boot technique.
I used to repair these problems but now it's easier for me to swap the Firewire boards into working 350s. I've got 12 of those in the basement currently.
Richard -
A few questions about replacing a PSU with few variations.
So I've spent a lot of time the last few weeks browsing these forums, searching the web, watching eBay, and asking around locally. I am still torn between forking over the $150-$200 for an eBay replacement or trying one of the adapters (http://atxg4.com/mdd.html) with an ATX PSU.
First off, I would like to get a little insight into my problem, to make sure I'm diagnosing it correctly. Two weeks ago I went to turn on my trusty 1GHz FW800 to type a quick document for work. I have been using this machine for over 6 years, without a single problem. The only modifications I made to the machine in the first few years (besides OS updates) was 3 sticks of memory, and another 60gig HD. Two years ago, I wanted to update my vid card to try and squeeze a few more years out of the machine. I went with the ATI 9800pro 128mb card. In order to use my Studio Display with this new card, I had to purchase the DVI to ADC Adapter with it's own power supply. Everything was peachy.
The other night, I pushed my power button, like I've done thousands of times before, and the button lit up like usual, but I didn't hear a fan or any noise coming from the machine, and the power button slowly faded. I then proceeded to push it again, and this time nothing...no light, no noise. And this is how it currently sits...
I've done pretty much everything I can think of to figure out what's wrong. I've tried unplugging and re-plugging, replacing and testing the power cord, using a different surge protector, using a different outlet, resetting the PMU, replacing and testing the battery, and reseating my memory sticks and graphics card. When the machine is plugged in, there are no red lights that glow. So, I followed the PSU test using a multimeter. I removed the black connector cover and stuck the probes in as best I could to get a reading, and I could not get a single reading from the first step of the PSU test. Am I safe to say my PSU is shot? Or...should I get some kind of a reading even if it is shot?
Lastly, I've read that one of the drawbacks of using an ATX PSU is that I will not be able to use my Cinema Display. With my current setup, using the DVI to ADC Adapter with it's own power, will it be possible for me to continue using my Apple Cinema Display if I were to use an ATX PSU? Thanks in advance for any insight/advice anyone can give!The power Supply adapter page says you won't have the 25V for the Cinema Display. Your other power just may work. Hopefully, someone else who has done the ATX mod & has a cinema display will respond.
Suggest you also post your question in the cimena display forum at http://discussions.apple.com/category.jspa?categoryID=111
Cheers, Tom -
My mac book pro does not connect but shows an error message with a question mark on the screen.I took it to a retailer that said it was not reconizing the hard drive.He said i needed a new hard drive but it may be something else as well but he was sure a new hard drive would fix it.So putting faith in someone who deals with them i purchased a new hard drive to find it was still not working although he said the computer did know reconize the hard drive and i may have to send it away to get it checked .After already paying 120 pounds for a new hard drive and they wanting another 80.00 pounds to diagnose it i am a little sceptical.
That's why i am interested on anyone's help.Welcome to the Apple Support Communities
I think that your Mac detects your hard disk, but the problem is that your new hard disk doesn't contain any operating system, so your Mac doesn't find any bootable partition and you see a question mark.
If your Mac came with DVDs, insert the Mac OS X Install DVD and hold the C key while your Mac is starting. Then, just install Mac OS X. If the hard disk isn't prepared to install Mac OS X, you will have to erase it using "Mac OS Extended (Journaled)". See > http://pondini.org/OSX/DU1.html
Maybe you are looking for
-
Unable to print from my wireless x2 allow printer
I have a HP laptop and am running Windows 7. I have printed off this laptop many times in the past. Occasionally we have had problems with communication but it has been easily resolved. This week however, I can print from my desktop, my phone but not
-
Sender SysId, Sender ObjectType or Sender payload is missing.
Hello Experts, i'm currently trying to learn about B1i. I installed the current version of B1i (Version B1iSN2007.P11.3.46 ) and started with the B12B1 example, presented here. I managed to follow the instructions without too much problems, but I'm a
-
please help me!
-
Oracle SQL - Extracting clob value from XML with repeating nodes
Hi All, I am attempting to run SQL on a table (called test_xml with a column xml_data [data type xmltype]). The column contains xml with repeating nodes (description). The following statement runs successfully when the node contains data of a non clo
-
Hi Gurus, I have maintained Tax Code in Infor record This got copied to PO as expected when i go to MIRO, system by-default bringing diff tax code [at header], i had to manually change to the tax entered in PO I could see in line item [in MIRO] tax c