Difference between DB CPU and DB Time

Hi,
What is the difference between DB CPU and DB TIME in AWR report?
Br,
Raj

Hi,
Thanks for your valuable reply.
1,DB CPU is time spent on CPU. It means only ACTIVELY working on CPU. WAIT TIME is not includeed.
In 10 Minute interval with four CPU, Is the Maximum DB CPU 40 Minutes?
2,I read the below document about DB time. http://www.perfvision.com/docs/JB_AAS.pdf
I unable to understand at page 6.
It says that DB Time = Includes CPU Time + IO Time + Wait Time
I understand about Wait time.
CPU also involved to do I/O Time? Is it RIGHT?.Hence, Why did seperate CPU Time and I/O time in the document?What is the purpose of it?
Is it possbile to further divided the CPU TIME ? Like parse etc.....Which view provide it?
3,If you had four sessions actively working or actively waiting 100% of the time in that 10 minute period, then your DB time would be 40 minutes.
In a given interval,Where can i find NON Idle wait time in AWR?
Plese help me out it
Br,
Raj

Similar Messages

DIFFERENCES between BASIC SCHEDULING and LEAD-TIME SCHEDULING.

Hello SAP Gurus,
Kindly let me know the differences between BASIC SCHEDULING and LEAD-TIME SCHEDULING.
Looking for your early feedback.
Warm regards,
Kaushik.

Hi,
Basic scheduling :
1.Basic dates are calculated.
2.Exact to day.
3.No cap reqmts are generated.
4.uses the inhouse production time from material master.
5.carried out automatically during planning run.
In basic date calculation ( order start date/ order finish date ) the system always
calculates backward scheduling.
1. From the reqmts date the system subtracts the GR processing time to
calculate the order fininsh date.
2. From the order finish date the system subtracts the inhouse production time to calculate the order start date.
3. From the order start date the system subtracts the opening period given in scheduling margin key to calculate the order opening date.
Lead time scheduling :
1.Exact to second
2.ie production start date /time and finish date and time are calculated.
3. cap reqmts are generated.
4. uses times from routing.
5. carried out only if the scheduling mode in MD02 screen is kept with indicator 2.
From the order finish date the system subtracts the float after production to calculate the production finish date.
From the production finish date the individual operations in the routing are scheduled backwards to calculate production start date.
From the production start date the system subtracts the float before production
to calculate order start date.
Regards,
nandha

What is the difference between an archive and a time machine backup?

I would like to save a lot of video to an external hard drive and have the drive fill up until it is full and then I'll use another drive to continue to save video. I do not want to backup my entire hd on my mac, just the video. Then when I want to access the video I want to be able to fetch it off the external drive and view/edit it in imovie.
How do I do that?

If you want the videos directly available to iMovie, do the move within iMovie.
Open the Event Library if it is not already, then click on the Hard Drive icon (highlighted in blue on the screen shot).
Then drag your events from the iMovie Events that are under your Macintosh HD onto your external hard drive in the Event Library list. There is some more information in the iMovie Help, under Lesson 7, for organizing your event library.
When you import video from a camera, you can choose to store it on the external hard drive instead of the internal.
Be careful not to select the external hard drive when you are looking for clips. Nothing bad will happen, but iMovie will load all of the video on the drive into the clip window. That takes a bit of time if the drive is full.
Now, you should back up that external in some way since you don't want to lose all your video if the drive crashes. I have been considering a RAID setup with mirrored drives, but I haven't looked that deeply into the idea. Right now, I just copied from one drive to the another as a stopgap solution until I implement a better, incremental backup system.

Exchange Rate difference between PO , GR and IR

Hi All,
I have a question, Does anyone know how to handle the PO exchange rate difference between PO , GR and IR time.
For example
1. PO creation on Jan 2009 - exchange rate = 1.2
2. GR creation on Feb 2009 - exchange rate = 1.5
3. IR creation on March 2009 - exchange rate = 1.7
Should GR and IR use the PO exchange rate # 1 for posting or use the current exchange # 2 for GR and #3 for IR ?
Thank you
Alex

Hi Alex,
The exchange rates in PO and GR and IR will be different as if you have are updating the rates per month in system so it will changed.
Regards,
Ninad Kshirsagar

Difference between Req with insufficient lead time and lead time const

Hi ,
1) Can anyone explain the difference between Requirement with insufficient lead time and Requirement lead time constraint exception messages. Both seems to be similar for me with the compressed time.Also at what situations these exceptions are generated.
2) what is minimum lead time required ,actual lead time and its calculation.
Thanks...

Check out
http://help.sap.com/saphelp_scm50/helpdata/en/99/ed3a981d0f11d5b3fc0050dadf0791/content.htm
particularly the section "Which functions of the operations relevant to scheduling are supported?"
It will give you a flavour of what can lead to difference in planning.

Diffrence between cpu and elapse time in tkprof

Hi All
i found huge diffrence between cpu and elapsed time in tkprof. can you please advice me on this issue.
>call count cpu elapsed disk query current rows
==================================================
Parse 1 0.12 1.36 2 11 0 0
Execute 1 14.30 720.20 46548 190520 205 100
Fetch 0 0.00 0.00 0 0 0 0
======================================================
total 2 14.42 721.56 46550 190531 205 100
Misses in library cache during parse: 1
Optimizer goal: CHOOSE
Parsing user id: 173 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times waited Max. Wait Total Waited
===========================================
db file sequential read 46544 0.49 632.12
db file scattered read 1 0.00 0.00
my select statement
SELECT cst.customer_id> ,DECODE(COUNT(cr.deposit_date), 0, 0, ROUND(SUM(cr.deposit_date - ps.trx_date) / COUNT(cr.deposit_date))) avgdays
> ,DECODE(COUNT(cr.deposit_date), 0, 0, ROUND(SUM(cr.deposit_date - ps.due_date) / COUNT(cr.deposit_date))) avgdayslate
> ,NVL(SUM(DECODE(SIGN(cr.deposit_date - ps.due_date),1, 1, 0)), 0) newlate
> ,NVL(SUM( DECODE(SIGN(cr.deposit_date - ps.due_date),1, 0, 1)), 0) newontime
>
> FROM ar_receivable_applications_all ra
> ,ar_cash_receipts_all cr
> ,ar_payment_schedules_all ps
> ,zz_ar_customer_summary_all cst
> WHERE ra.cash_receipt_id = cr.cash_receipt_id
> AND ra.apply_date BETWEEN ADD_MONTHS(SYSDATE, -12) AND SYSDATE
> AND ra.status = 'APP'
> AND ra.display = 'Y'
> AND ra.applied_payment_schedule_id = ps.payment_schedule_id
> AND ps.customer_id = cst.customer_id
> AND NVL(ps.receipt_confirmed_flag,'Y') = 'Y'
> group by cst.customer_id ;
Thanks,
Anu

user653066 wrote:
Hi All
i found huge diffrence between cpu and elapsed time in tkprof. can you please advice me on this issue.
call     count       cpu    elapsed       disk      query    current        rows
================================================================================
Parse        1      0.12       1.36          2         11          0           0
Execute      1     14.30     720.20      46548     190520        205         100
Fetch        0      0.00       0.00          0          0          0           0
================================================================================
total        2     14.42     721.56      46550     190531        205         100
Misses in library cache during parse: 1
Optimizer goal: CHOOSE
Parsing user id: 173     (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on                      Times waited   Max. Wait Total Waited
===========================================================================
db file sequential read                     46544        0.49        632.12
db file scattered read                          1        0.00          0.00
SELECT cst.customer_id
         ,DECODE(COUNT(cr.deposit_date), 0, 0, ROUND(SUM(cr.deposit_date - ps.trx_date) / COUNT(cr.deposit_date))) avgdays
         ,DECODE(COUNT(cr.deposit_date), 0, 0, ROUND(SUM(cr.deposit_date - ps.due_date) / COUNT(cr.deposit_date))) avgdayslate
         ,NVL(SUM(DECODE(SIGN(cr.deposit_date - ps.due_date),1, 1, 0)), 0) newlate
         ,NVL(SUM( DECODE(SIGN(cr.deposit_date - ps.due_date),1, 0, 1)), 0) newontime
          FROM ar_receivable_applications_all ra
              ,ar_cash_receipts_all           cr
              ,ar_payment_schedules_all       ps
              ,zz_ar_customer_summary_all cst
          WHERE ra.cash_receipt_id                 = cr.cash_receipt_id
          AND   ra.apply_date                BETWEEN ADD_MONTHS(SYSDATE, -12) AND SYSDATE
          AND   ra.status                          = 'APP'
          AND   ra.display                         = 'Y'
          AND   ra.applied_payment_schedule_id     = ps.payment_schedule_id
          AND   ps.customer_id                     = cst.customer_id
          AND   NVL(ps.receipt_confirmed_flag,'Y') = 'Y'
          group by cst.customer_id    ;           Toon Koppelaars seems to have pinpointed the problem. Where are the 74 seconds unaccounted for seconds (I might have calculated it incorrectly, but I arrived at 88.08 seconds of unaccounted for time: 721.56 total - 1.36 parse - 632.12 db file sequential reads)?
It is interesting that the maximum wait for a single block read reported by TKPROF is 0.49 seconds - this might be an indication of excessive competition for the server's CPU - processes are waiting in the CPU run queue, and therefore not on the CPU. As Toon indicated, 632.12 of the 721.56 seconds were spent waiting for single block reads to complete with 46,544 blocks read. Note also that the query executed at dep=1, and TKPROF may be providing misleading information about what actually happened during those executions. An example of misleading information:
CREATE TABLE T11 (
C1 NUMBER,
C2 VARCHAR2(30));
CREATE TABLE T12 (
C1 NUMBER,
C2 VARCHAR2(30));
CREATE TABLE T13 (
C1 NUMBER,
C2 VARCHAR2(30));
CREATE TABLE T14 (
C1 NUMBER,
C2 VARCHAR2(30));
CREATE OR REPLACE TRIGGER HPM_T11 AFTER
INSERT OR DELETE OR UPDATE OF C1 ON T11
REFERENCING OLD AS OLDDATA NEW AS NEWDATA FOR EACH ROW
BEGIN
IF INSERTING THEN
    INSERT INTO T12
    SELECT
      ROWNUM,
      DBMS_RANDOM.STRING('A',25)
    FROM
      DUAL
    CONNECT BY
      LEVEL <= 100;
END IF;
END;
CREATE OR REPLACE TRIGGER HPM_T12 AFTER
INSERT OR DELETE OR UPDATE OF C1 ON T12
REFERENCING OLD AS OLDDATA NEW AS NEWDATA FOR EACH ROW
BEGIN
IF INSERTING THEN
    INSERT INTO T13
    SELECT
      ROWNUM,
      DBMS_RANDOM.STRING('A',25)
    FROM
      DUAL
    CONNECT BY
      LEVEL <= 100;
END IF;
END;
CREATE OR REPLACE TRIGGER HPM_T13 AFTER
INSERT OR DELETE OR UPDATE OF C1 ON T13
REFERENCING OLD AS OLDDATA NEW AS NEWDATA FOR EACH ROW
BEGIN
IF INSERTING THEN
    INSERT INTO T14
    SELECT
      ROWNUM,
      DBMS_RANDOM.STRING('A',25)
    FROM
      DUAL
    CONNECT BY
      LEVEL <= 100;
END IF;
END;
ALTER SESSION SET TRACEFILE_IDENTIFIER = 'MY_TEST_FIND_ME2';
ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT FOREVER, LEVEL 8';
SET TIMING ON
INSERT INTO T11 VALUES (1,'MY LITTLE TEST CASE');
ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT OFF';The partial TKPROF output:
INSERT INTO T11
VALUES
(1,'MY LITTLE TEST CASE')
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          8          0           0
Execute      1      0.00       0.00          0       9788         29           1
Fetch        0      0.00       0.00          0          0          0           0
total        2      0.00       0.00          0       9796         29           1
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56
Rows     Row Source Operation
      0 LOAD TABLE CONVENTIONAL (cr=9788 pr=7 pw=0 time=0 us)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
SQL*Net message to client                       1        0.00          0.00
SQL*Net message from client                     1        0.00          0.00
SQL ID : 6asaf110fgaqg
INSERT INTO T12 SELECT ROWNUM, DBMS_RANDOM.STRING('A',25) FROM DUAL CONNECT
BY LEVEL <= 100
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.04       0.09          0          2        130         100
Fetch        0      0.00       0.00          0          0          0           0
total        2      0.04       0.09          0          2        130         100
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56     (recursive depth: 1)
Rows     Row Source Operation
      0 LOAD TABLE CONVENTIONAL (cr=9754 pr=7 pw=0 time=0 us)
    100   COUNT (cr=0 pr=0 pw=0 time=0 us)
    100    CONNECT BY WITHOUT FILTERING (cr=0 pr=0 pw=0 time=0 us)
      1     FAST DUAL (cr=0 pr=0 pw=0 time=0 us cost=2 size=0 card=1)
SQL ID : db46bkvy509w4
INSERT INTO T13 SELECT ROWNUM, DBMS_RANDOM.STRING('A',25) FROM DUAL CONNECT
BY LEVEL <= 100
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute    100      1.31       1.27          0         93      10634       10000
Fetch        0      0.00       0.00          0          0          0           0
total      101      1.31       1.27          0         93      10634       10000
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56     (recursive depth: 2)
Rows     Row Source Operation
      0 LOAD TABLE CONVENTIONAL (cr=164 pr=0 pw=0 time=0 us)
    100   COUNT (cr=0 pr=0 pw=0 time=0 us)
    100    CONNECT BY WITHOUT FILTERING (cr=0 pr=0 pw=0 time=0 us)
      1     FAST DUAL (cr=0 pr=0 pw=0 time=0 us cost=2 size=0 card=1)
SQL ID : 6542yyk084rpu
INSERT INTO T14 SELECT ROWNUM, DBMS_RANDOM.STRING('A',25) FROM DUAL CONNECT
BY LEVEL <= 100
call     count       cpu    elapsed       disk      query    current        rows
Parse        2      0.00       0.00          0          0          0           0
Execute 10001     41.60      41.84          0       8961      52859     1000000
Fetch        0      0.00       0.00          0          0          0           0
total    10003     41.60      41.84          0       8961      52859     1000000
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56     (recursive depth: 3)
Rows     Row Source Operation
      0 LOAD TABLE CONVENTIONAL (cr=2 pr=0 pw=0 time=0 us)
    100   COUNT (cr=0 pr=0 pw=0 time=0 us)
    100    CONNECT BY WITHOUT FILTERING (cr=0 pr=0 pw=0 time=0 us)
      1     FAST DUAL (cr=0 pr=0 pw=0 time=0 us cost=2 size=0 card=1)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
log file switch completion                      2        0.07          0.07
********************************************************************************In the above note that the "INSERT INTO T11" is reported as completing in 0 seconds, but it actually required roughly 42 seconds - and that would be visible by manually reviewing the resulting trace file. Also note that the log file switch completion wait was not reported for the "INSERT INTO T11" even though it impacted the execution time.
Back to the possibility of CPU starvation causing lost time. Another test with an otherwise idle server, followed by a second test with the same server having 240 other processes fighting for CPU resources (a simulated load).
ALTER SYSTEM FLUSH BUFFER_CACHE;
ALTER SESSION SET TRACEFILE_IDENTIFIER = 'MY_TEST_QUERY_NO_LOAD';
ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT FOREVER, LEVEL 8';
SET TIMING ON
SELECT
COUNT(*)
FROM
T14;
SELECT
SYSDATE
FROM
DUAL;
SQL> SELECT
2    COUNT(*)
3 FROM
4    T14;
COUNT(*)
   1000000
Elapsed: 00:00:01.37With no load the COUNT(*) completed in 1.37 seconds. The TKPROF output looks like this:
SQL ID : gy8nw9xzyg3bj
SELECT /* OPT_DYN_SAMP */ /*+ ALL_ROWS IGNORE_WHERE_CLAUSE
NO_PARALLEL(SAMPLESUB) opt_param('parallel_execution_enabled', 'false')
NO_PARALLEL_INDEX(SAMPLESUB) NO_SQL_TUNE */ NVL(SUM(C1),:"SYS_B_0"),
NVL(SUM(C2),:"SYS_B_1")
FROM
(SELECT /*+ NO_PARALLEL("T14") FULL("T14") NO_PARALLEL_INDEX("T14") */
:"SYS_B_2" AS C1, :"SYS_B_3" AS C2 FROM "T14" SAMPLE BLOCK (:"SYS_B_4" ,
:"SYS_B_5") SEED (:"SYS_B_6") "T14") SAMPLESUB
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      0.01       0.84        523        172          1           1
total        3      0.01       0.84        523        172          1           1
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56     (recursive depth: 1)
Rows     Row Source Operation
      1 SORT AGGREGATE (cr=172 pr=523 pw=0 time=0 us)
   8733   TABLE ACCESS SAMPLE T14 (cr=172 pr=523 pw=0 time=0 us cost=2 size=12 card=1)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file sequential read                         3        0.02          0.04
db file parallel read                           1        0.31          0.31
db file scattered read                         52        0.03          0.47
SQL ID : 96g93hntrzjtr
select /*+ rule */ bucket_cnt, row_cnt, cache_cnt, null_cnt, timestamp#,
sample_size, minimum, maximum, distcnt, lowval, hival, density, col#,
spare1, spare2, avgcln
from
hist_head$ where obj#=:1 and intcol#=:2
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      0.00       0.06          2          2          0           0
total        3      0.00       0.06          2          2          0           0
Misses in library cache during parse: 0
Optimizer mode: RULE
Parsing user id: SYS   (recursive depth: 2)
Rows     Row Source Operation
      0 TABLE ACCESS BY INDEX ROWID HIST_HEAD$ (cr=2 pr=2 pw=0 time=0 us)
      0   INDEX RANGE SCAN I_HH_OBJ#_INTCOL# (cr=2 pr=2 pw=0 time=0 us)(object id 413)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file sequential read                         2        0.02          0.04
SELECT
COUNT(*)
FROM
T14
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          1          1          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        2      0.03       0.43       6558       6983          0           1
total        4      0.03       0.44       6559       6984          0           1
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56
Rows     Row Source Operation
      1 SORT AGGREGATE (cr=6983 pr=6558 pw=0 time=0 us)
1000000   TABLE ACCESS FULL T14 (cr=6983 pr=6558 pw=0 time=0 us cost=1916 size=0 card=976987)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file sequential read                         1        0.02          0.02
SQL*Net message to client                       2        0.00          0.00
db file scattered read                        111        0.02          0.38
SQL*Net message from client                     2        0.00          0.00Note that TKPROF reported that it only required 0.44 seconds for the query to execute while the SQL*Plus timing indicate that it required 1.37 seconds for the SQL statement to execute. The SQL optimization (parse) with dynamic sampling query accounted for the remaining time, yet TKPROF provided no indication that this was the case.
Now the query with 240 other processes competing for CPU time:
ALTER SYSTEM FLUSH BUFFER_CACHE;
ALTER SESSION SET TRACEFILE_IDENTIFIER = 'MY_TEST_QUERY_WITH_LOAD';
SELECT COUNT(*) FROM T14;
SELECT
SYSDATE
FROM
DUAL;
SQL> SELECT COUNT(*) FROM T14;
COUNT(*)
   1000000
Elapsed: 00:00:59.03The query this time required just over 59 seconds. The TKPROF output:
SQL ID : gy8nw9xzyg3bj
SELECT /* OPT_DYN_SAMP */ /*+ ALL_ROWS IGNORE_WHERE_CLAUSE
NO_PARALLEL(SAMPLESUB) opt_param('parallel_execution_enabled', 'false')
NO_PARALLEL_INDEX(SAMPLESUB) NO_SQL_TUNE */ NVL(SUM(C1),:"SYS_B_0"),
NVL(SUM(C2),:"SYS_B_1")
FROM
(SELECT /*+ NO_PARALLEL("T14") FULL("T14") NO_PARALLEL_INDEX("T14") */
:"SYS_B_2" AS C1, :"SYS_B_3" AS C2 FROM "T14" SAMPLE BLOCK (:"SYS_B_4" ,
:"SYS_B_5") SEED (:"SYS_B_6") "T14") SAMPLESUB
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      0.00       0.28        423         69          0           1
total        3      0.00       0.28        423         69          0           1
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 56     (recursive depth: 1)
Rows     Row Source Operation
      1 SORT AGGREGATE (cr=69 pr=423 pw=0 time=0 us)
   8733   TABLE ACCESS SAMPLE T14 (cr=69 pr=423 pw=0 time=0 us cost=2 size=12 card=1)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file scattered read                         54        0.01          0.27
db file sequential read                         2        0.00          0.00
SQL ID : 7h04kxpa13w1x
SELECT COUNT(*)
FROM
T14
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.03          1          1          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        2      0.06      58.71       6551       6983          0           1
total        4      0.06      58.74       6552       6984          0           1
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 56
Rows     Row Source Operation
      1 SORT AGGREGATE (cr=6983 pr=6551 pw=0 time=0 us)
1000000   TABLE ACCESS FULL T14 (cr=6983 pr=6551 pw=0 time=0 us cost=1916 size=0 card=976987)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file sequential read                         1        0.02          0.02
SQL*Net message to client                       2        0.00          0.00
db file scattered read                        110        1.54         58.59
SQL*Net message from client                     1        0.00          0.00Note in the above that the max wait for the db file scattered read is 1.54 seconds due to the extra CPU competition - about 3 times longer than your max wait for a single block read. On your database platform with single block reads, it might be possible that the time in the CPU run queue is not always counted in the db file sequential read wait time or the CPU wait time - what if your operating system is slow at returning timing information to the database instance due to CPU saturation - this might explain the 74 (or 88) lost seconds.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.
Edited by: Charles Hooper on Aug 28, 2009 10:26 AM
Fixing formatting problems

Difference between Bucket capacity and Time continuous capacity

Can somebody explain the difference in functionality between "Bucket capacity" and "Time continuous capacity" as used in field "Finite capacity" in "PP/DS bucket capacity" tab in Resource?
How will above above two settings work when you have "Block planning" in "Bucket definition" tab in same tab?
Thanks,
Srini

Hello,
The difference between Bucket capacity and Time continuous capacity are:
Time continuous capacity is basically the capacity which is infinite continuous duration in time and you can define the shift intervals and breaks to adjust as per business process e.g. everyday 8 hrs or 16 hrs capacity with lunch time and breaks in between whereas bucket capacity is a discrete capacity and is specified bucket wise. Bucket capacity can be in PPDS as well as SNP. In PPDS it is used specifically for CDP planning or block planning. In SNP it can be used for bucket capacity references as Transport resources, storage resources , bucket planning etc
With respect to Block Planning:
You maintain the blocks using the entire validity of the available capacity of the resource. If you defined buckets from block planning for validity periods in which no blocks are defined, the buckets correspond to technical intervals in which the system schedules on a time-continuous basis.
You can check out the below link for the Block planning with Bucket capacity:
http://help.sap.com/saphelp_scm41/helpdata/en/e5/90bb3b6070bf38e10000000a11402f/content.htm
Hope the information is useful
Regards

Difference between wait event and timed event

Hi,
Anyone has idea that what is the difference between wait events and timed events in Statspack report. I couldn't find it over google.
Thanks.

It's 10.2.0.1 on Linux
(Couldn't do a query, because Linux is inside VM Ware. And it is not being accessed from Base windows machine.)
Top 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time
db file scattered read 9,750,617 34,611 4 44.7
CPU time 14,248 18.4
read by other session 1,532,282 8,984 6 11.6
db file sequential read 4,514,494 5,588 1 7.2
latch: cache buffers lru chain 277,245 4,823 17 6.2
Wait Events DB/Inst: ABCD/ABCD Snaps: 1-2
-> s - second, cs - centisecond, ms - millisecond, us - microsecond
-> %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
-> Only events with Total Wait Time (s) >= .001 are shown
-> ordered by Total Wait Time desc, Waits desc (idle events last)
Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
db file scattered read 9,750,617 0 34,611 4 24.2
read by other session 1,532,282 0 8,984 6 3.8
db file sequential read 4,514,494 0 5,588 1 11.2
latch: cache buffers lru chain 277,245 0 4,823 17 0.7
latch free 121,466 0 3,291 27 0.3
----------------------------------------------------------------------------------------------------

What is difference between sy-index and sy-tabix and where both are using ?

what is difference between sy-index and sy-tabix and where both are using ?

hi nagaraju
sy-tabix is in Internal table, current line index. So it can only be used while looping at the internal table.
sy-index is in Loops, number of current pass. This you can use in other loop statements also (like do-enddo loop, while-endwhile)
SY-INDEX is a counter for following loops: do...enddo, while..endwhile
SY-TABIX is a counter for LOOP...ENDLOOP, READ TABLE...
Here is an example from which you can understand the difference between sy-tabix and sy-index.
Itab is an internal table with the following data in it.
id Name
198 XYZ
475 ABC
545 PQR.
loop at itab where id > 300.
write :/ itab-id, itab-name , sy-tabix, sy-index.
endloop.
My output will be :
475 ABC 2 1
545 PQR 3 2
Sy-tabix is the index of the record in internal table.
sy-index gives the no of times of loop passes.
So, for the first record in the output (475 ABC), 2 is the index of the record in internal table and as it is first time loop pass occured, sy-index value is 1.
Regards,
navjot
award points

The difference between system restore and last good known configuration

hi,
what is the difference between system restore and last good known configuration.
in which situation you use system restore ,and in which situation you use last good known configuration.
very short answer wil be enough.
thanks
johan
h.david

Last Known Good Configuration deals only with Starting Windows eg. a bad registry or incorrect driver is preventing Windows to start.It recovers the registry settings of HKEY_LOCAL_MACHINE\System\CurrentControlSet
While System Restore uses restore points to return your system files and settings to an earlier point in time without affecting personal files. Restore points are created automatically every week, and just before significant system events, such as the installation
of a program or device driver. You can also create a restore point manually.You can undone system restore but there is no such option in Last Known Good Configuration.
Last Known Good Configuration is disabled in Windows 8 or,Windows 8.1 by default.
Try using Last Known Good Configuration if you can't start Windows, but it started correctly the last time you turned on the computer.
Try using System Restore to return the system to an earlier point in time when things worked correctly.
S.Sengupta, Windows Entertainment and Connected Home MVP

Difference between sy-datum and sy-datlo

difference between sy-datum and sy-datlo

hi,
The GET TIME statement synchronizes the time on the application server with the time on the database server and writes it to the field SY-UZEIT. SY-DATUM and the system fields for the local timezone (SY-TIMLO, SY-DATLO, and SY-ZONLO) are also reset.
SY-DATLO
Users local date, for example 19981129, 19990628,
SY-DATUM
Current application server date, for example 19981130, 19990627,
SY-DAYST
X during summertime, otherwise space.
SY-FDAYW
Factory calendar day of the week: Monday = 1 Friday = 5.
SY-TIMLO
Users local time, for example 154353, 225312,
SY-TZONE
Time difference in seconds between local time and Greenwich Mean Time (UTC), for example,
360, 10800.
SY-UZEIT
Current application server time. for example 164353, 215312,
SY-ZONLO
Users time zone, for example, EST, UTC,
reward points if useful

What is the difference between Topic Keywords and Index File Keywords?

What is the difference between Topic Keywords and Index File Keywords? Any advantages to using one over the other? Do they appear differently in the generated index?
RH9.0.2.271
I'm using Webhelp

Hi there
When you create a RoboHelp project you end up with many different ancillary files that are used to store different bits of information. Many of these files bear the name you assigned to the project at the time you created it. The index file has the project name and it ends with a .HHK file extension. (HHK meaning HTML Help Keywords)
Generally, unless you change RoboHelp's settings, you add keywords to this file and associate topics to the keywords via the Index pod. At the time you compile a CHM or generate other types of output, the file is consulted and the index is built.
As I said earlier, the default is to add keywords to the Index file until you configure RoboHelp to add the keywords to the topics themselves. Once you change this, any keyword added will become a META tag in the topic code. If your keyword is BOFFO, the META tag would look like this:
<meta name="MS-HKWD" content="BOFFO" />
When the help is compiled or generated, the Index (.HHK) file is consulted as normal, but any topics containing keywords added in this manner are also added to the Index you end up with. From the appearance perspective, the end user woudn't know the difference or be able to tell. Heck, if all you ever did was interact with the Index pod, you, as an author wouldn't know either. Well, other than the fact that the icons appear differently.
Operationally, keywords added to the topics themselves may hold an advantage in that if you were to import these topics into other projects, the Index keywords would already be present.
Hopefully this helps... Rick

Disk Utilty - what is difference between single volume and single partition

In Disk Utility I can, should I wish, format a drive by using Erase to create a single volume. Also in Disk Utility, I have the option to use Partition to create one (or more) partition.
What is the difference between a volume and a single partition?
What are their relative merits?
In what circumstances would I want to create a single partition instead of a volume?
Disk Utility also prompts me to name the volume or partition. From experience, what would you suggest as a suitable name and where is this information subsequently used?

A "volume" or "partition" are the same thing. The subject of using partitions has been covered many times on the forums. Do some searching and you'll find quite a lot of information. Also try doing some Google searching.

What is difference between bex analyser and bex browser

what is difference between bex analyser and bex browser . please explain what are use of both and what we do in both.

hi
Bex Browser
The Business Explorer Browser (BEx Browser) makes it possible for you to access all document types of the Business Information Warehouse that are assigned to your role or that you have stored in your favorites. You can select and open documents assigned to you in the BEx Browser or store and manage new documents in the BEx Browser.
Document types that you can work with in the BEx Browser are:
· BW workbooks
· Documents that are stored in the Business Document Service (BDS)
· Links (references to file system, shortcuts)
· Links to internet sites (URLs)
· SAP transaction calls.
· Web applications and Web templates
· Crystal Reports
Bex Analyser
The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel.
Features
You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries. Subsequently, you can analyze the selected InfoProvider data by navigation to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or for different queries to a work book and save them there. You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer.
Beyond that, you can precalculate the workbook and distribute it by e-mail to recipeients or you can export it to the Enterprise Portal and make it accessible to other employees in the company.
You can start queries in a standard view (with a Standard Web Template set up in Customizing) in the Web browser and forward the URL or continue to navigate on the Web. Similarly, you can export the Web query to MS Excel 2000.
Overview of the Functional Area of the BEx Analyzer:
·        BEx toolbar
You access the functions of the BEx Analyzer from the BEx toolbar, which takes you to the BEx Open dialog box where you can open existing queries, or to the BEx Query Designer where you can create new queries or change existing queries.
·        Evaluating Query Data
The BEx Analyzer offers convenient functions for evaluating and presenting InfoProvider data interactively. In the BEx Analyzer, you can add queries to workbooks, navigate within them and refresh the data. You can also process the queries further in Microsoft Excel or display them in the Web browser in a default view.
Navigation of a query allows you, for example, to filter characteristics on a single value, drilldown on all values for a characteristic, regroup characteristics and key figures in the rows and columns of the results area, or hide key figures. Navigation results in different views of the InfoProvider data. In addition, a range of further functions is available which allow you to edit a query interactively (for example, sorting, cumulated output, among others). In addition, you can use the editing functions in Microsoft Excel in order to set up individual format templates, to print results areas, or to create graphics.
·        Queries in Workbooks
Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the InfoProvider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server).
When inserting a query into the workbook, a VBA routine is automatically generated in the workbook. You can also connect the Business Explorer with your own VBA programs (Visual Basic for Applications).
You can create workbook templates, into which you can insert your queries. Workbook templates can contain pre-determined items for the area of the query, formatting settings, logos, VBA macros, and so on.
·        Precalculating workbooks
You can precalculate and distribute workbooks with the BEx Broadcaster, which is a Web application you get to form the BEx toolbar. The system generates MS Excel workbooks with historical data. You determine the time for precalculation yourself: You can have workbooks precalculated at a predefined time or they can be precalculated whenever data in the underlying InfoProvider changes. You can have the precalculated workbooks sent by e-mail or you can export them into the Enterprise Portal, where you can make them available to employees within your company.
Activities
To start the BEx Analyzer, choose Start ® Programs ® SAP Front-end Business Information Warehouse ® SAP Business Explorer Analyzer.
You can also access the BEx Analyzer via SAP Easy Access ® SAP Business Information Warehouse ® SAP Menu ® Business Explorer ® Analyzer or in the Business Explorer Browser using the Business Explorer Analyzer symbol in the menu bar.
Hope this will solve your issu
nagarjuna

What is difference between local variable and property node ?

What is difference between local variable and property node ?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview

To make things clear, here are two small examples that show how nasty locals and value properties can be to the naive programmer.
- Open the diagram of the race condition.vi before running it and try to predict what will be the values of the two counters after the third run.
- Use the Compare Locals Properties and Wires.vi to find out how slow locals and value properties can be (times 1000+).
This being demonstrated, I must add that I use globals and value properties quite often, because they are often very convenient
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Race condition.vi ‏9 KB
Compare Locals Properties and Wires.vi ‏18 KB

Difference between DB CPU and DB Time

Similar Messages

Maybe you are looking for