Time Model

Hi,
I have a question about "time model" statistics.
Assume that the instance is open for 138 days and "db time" in v$sys_time_model view is 36 days. By only comparing these days can we understand instance doesn't need hardware changes?
SQL> select round((sysdate-t.STARTUP_TIME)) as days_open from v$instance t;
DAYS_OPEN
138
SQL> select t.STAT_NAME, round(t.VALUE/1000000/60/60/24) days_db_time from v$sys_time_model t where lower(t.STAT_NAME)= 'db time' ;
STAT_NAME DAYS_DB_TIME
DB time 36
Thank You..

It would be wrong to arrive at a conclusion regarding hardware changes with this information. It could be that these 138 days have been normal days for your database and the days to follow may need some higher levels of processing power.

Similar Messages

Variances Using Crossover Time Model

I'm sure this is a standard problem but am unable to find a solution:We're using a crossover time model where three fiscal years, quarters, months and weeks are all descendants of time (there is no year in scenarios).How do we build a member that computes a variance? For example, we'd like the variance for any measure between 2002_Q1 and 2001_Q1.Any help would be appreciated, even if it's just to point me at some appropriate documentation.Thanks.

To be able to calculate a variance between a selected year/month/quarter and the prior year, you could do it a number of ways:1) Create members in the time dimension to represent the possible variances (that could be a lot of extra members.2) Create a new dimension to store the variances.3) Split the years out of the model and do variances within that dimension.Of course, you could always have the front end tool do the variance for you, but if you want to have it come out of Essbase, those are the choices.You could use an existing dimension to store the variances, but you will have some limitations. For example, if you choose to use the accounts dimension, you will have to select an account on which to do the variance.Are there specific values for which you want to see the variance, or could it be anything?Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Time model/event

Hi,
what is time model stats in AWR and time event in 10g?
What is the difference between two?
Thanks

Hi,
Below is a description for Time model statistics in AWR. I do not understand what you mean by time waits in AWR - Pls clarify!
Note: Below text is a blatant copy of what Don has to sya on this in his website. This is the simplest description I have got. To look for further info, kindly look into the good old Oracle documentation.
Time Model Statistics
The time model statistics give insight about where the processing time is actually spent during the snapshot interval.
Time Model Statistics DB/Inst: LSQ/lsq Snaps: 1355-1356
-> ordered by Time (seconds) desc
                                                       Time      % Total
Statistic Name                                     (seconds)     DB Time
DB time                                         7,274.60      100.00
sql execute elapsed time                        7,249.77       99.66
background elapsed time                           778.48       10.70
DB CPU                                            150.62        2.07
parse time elapsed                                 45.52         .63
hard parse elapsed time                            44.65         .61
PL/SQL execution elapsed time                      13.73         .19
background cpu time                                 8.90         .12
PL/SQL compilation elapsed time                     3.80         .05
connection management call elapsed time              .15         .00
Java execution elapsed time                          .05         .00
hard parse (bind mismatch) elapsed time              .00         .00
hard parse (sharing criteria) elapsed time           .00         .00
sequence load elapsed time                           .00         .00
failed parse (out of shared memory) elapsed          .00         .00
inbound PL/SQL rpc elapsed time                      .00         .00
failed parse elapsed time                            .00         .00
In the sample output of the AWR Time Model Statistics Report shown above, it can be seen that the system spends the most processing time on actual SQL execution but not on parsing.Thanks,
Suddhasatwa

Database tuning with Time Model Statistics

How can we use V$SESS_TIME_MODEL and V$SYS_TIME_MODEL or DB_TIME to daignose/tune the database

Tnx Jaffar,
I know the description of each column for dynamic performance views.
My question is how can we get any meaningful information which can help interpreting problem or possible solution in the DB.
For instance look at the output from V$SYS_TIME_MODEL from one of the production Database.How can I use that information to good use.
3649082374 DB time                                                             855657150735
2748282437 DB CPU                                                              270642990896
4157170894 background elapsed time                                             511263826646
2451517896 background cpu time                                                 128007010158
4127043053 sequence load elapsed time                                             102151062
1431595225 parse time elapsed                                                  105369068246
372226525 hard parse elapsed time                                              91457461637
2821698184 sql execute elapsed time                                            694544980733
1990024365 connection management call elapsed time                                933285066
1824284809 failed parse elapsed time                                             3890881196
4125607023 failed parse (out of shared memory) elapsed time                               0
3138706091 hard parse (sharing criteria) elapsed time                             113740639
268357648 hard parse (bind mismatch) elapsed time                                  8999669
2643905994 PL/SQL execution elapsed time                                        32792584918
290749718 inbound PL/SQL rpc elapsed time                                        122796155
1311180441 PL/SQL compilation elapsed time                                        103310315
751169994 Java execution elapsed time                                                    0
1159091985 repeated bind elapsed time                                              45211144
2411117902 RMAN cpu time (backup/restore)                                      100789016188

Unable to connect to multiple computers at time; Model WRT110

Only the laptop with the software has wireless access. Other laptop is stuck on "acquiring network address." Any suggestions on how to fix?

Check the Wireless Settings on the Router...
See this , Once you have checked the Settings go to the Laptop that is stuck on "acquiring network address." Go to the control panel and open network connections,
right click on wireless network connection and click on properties.
Now on this window, click on the second tab Wireless network and give a check mark on "Use windows to configure my wireless ....."
and then remove all the network names from the preferred networks window. Then click on OK. ..
Click on View Available Wireless Networks and try to re-connect to your network...
Now it will give you the opportunity to put the network/wep key, make sure you enter the correct network key and confirm it...It will connect...

How to tell how many times a method has executed?

Hi, all
I've got a main class (Model.java) that repeatedly calls a step() method in a sub class (Ocean.java). I want Ocean.java to execute its step() method following one set of rules for the first time it is called by Model.java, and a different set of rules for all executions 2++. I was just going to use an if/else in Ocean.java's step() method to make it switch based on a boolean haveIExecutedThisStepOnce, or something like that. Is there some way to tell Ocean.java how many times it has executed the step() method? I'm using the RePast code libraries; Model.java uses a method called getTickCount(). It returns a double value of number of times Model.java's step() method has been executed, in which Model.java tells Ocean.java to execute its step() method. Should I pry that getTickCount() value out of Model.java and get it over to Ocean.java's step() method--and if so, how? Or, is there a better way to do this that I'm not aware of?

Why do you think that this field has to be public?
Arguably if there's some functionality that is tightly associated with this counted method, then it should be part of the same class.
Alternatively, think about the counting variable. It should be with the thing that uses it.
So if class A wants to invoke class B method c once, do something else, and then invoke c some more, then that counting is really more an aspect of A than of B, and in that case the state should be in A. In that case the field really counts the number of times that A has invoked B.c, not the number of times that B.c has been invoked overall. Maybe that's what you want.
On the other hand if you really want to count the number of times that B.c has been invoked overall, then it's an aspect of B (or more likely an instance of B). In that case, rather than expose the counting state and the counted method, it would probably be better to create a new method d(). d() would invoke c(), doing something extra depending on the counting state. Make c() private. Like this:
class B {
private boolean c_has_been_called = false;
public void d() {
    c();
    if (!c_has_been_called) {
      doWhateverYouNeedInThisCase();
      c_has_been_called = true;
private void c() {
    // and c() does whatever it normally does
}

Performance Degradated Possibly due to CPU Time

Hi Gurus,
There is a utility in our application with which we can upload an excel sheet containing data and schedule the timing of the job, now when the job is executed, each row in the excel sheet leads to dml operations on multiple tables finally leading to generation of a transaction no. Now at the start around 100-120 transaction nos were generated which goes down drastically to around 30-35 after 6-7 hours. AWR report at the two instances shows that CPU time has decreased considerably in the 2nd case.
I would like you experts to check the awr reports and suggest me the probable reason for the decrease in performance.
Brief AWR Report When Performance was OK
Snap Id Snap Time Sessions Curs/Sess
Begin Snap: 2151 14-Dec-10 16:32:57 26 3.7
End Snap: 2152 14-Dec-10 17:31:04 40 16.7
Elapsed: 58.13 (mins)
DB Time: 55.37 (mins)
Cache Sizes
~~~~~~~~~~~ Begin End
Buffer Cache: 436M 444M Std Block Size: 8K
Shared Pool Size: 120M 120M Log Buffer: 6,968K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 27,541.56 1,747.07
Logical reads: 49,830.97 3,160.97
Block changes: 181.79 11.53
Physical reads: 1,270.12 80.57
Physical writes: 2.81 0.18
User calls: 119.95 7.61
Parses: 200.94 12.75
Hard parses: 29.29 1.86
Sorts: 91.80 5.82
Logons: 0.03 0.00
Executes: 457.16 29.00
Transactions: 15.76
% Blocks changed per Read: 0.36 Recursive Call %: 96.36
Rollback per transaction %: 0.01 Rows per Sort: 270.64
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 100.00
Buffer Hit %: 97.45 In-memory Sort %: 100.00
Library Hit %: 90.18 Soft Parse %: 85.42
Execute to Parse %: 56.05 Latch Hit %: 100.00
Parse CPU to Parse Elapsd %: 98.04 % Non-Parse CPU: 94.98
Shared Pool Statistics Begin End
Memory Usage %: 72.65 84.55
% SQL with executions>1: 71.49 75.08
% Memory for SQL w/exec>1: 84.79 85.25
Top 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
CPU time 2,541 76.5
db file scattered read 284,992 410 1 12.3 User I/O
log file parallel write 31,188 145 5 4.4 System I/O
TCP Socket (KGAS) 24 131 5459 3.9 Network
log file sync 8,617 46 5 1.4 Commit
Time Model Statistics DB/Inst: ABCTEST/abctest Snaps: 2151-2152
-> Total time in database user-calls (DB Time): 3322.4s
-> Statistics including the word "background" measure background process
time, and so do not contribute to the DB time statistic
-> Ordered by % or DB time desc, Statistic name
Statistic Name Time (s) % of DB Time
sql execute elapsed time 3,176.8 95.6
DB CPU 2,541.1 76.5
PL/SQL execution elapsed time 288.5 8.7
parse time elapsed 278.7 8.4
hard parse elapsed time 254.6 7.7
PL/SQL compilation elapsed time 28.9 .9
failed parse elapsed time 4.9 .1
hard parse (sharing criteria) elapsed time 1.3 .0
sequence load elapsed time 1.1 .0
repeated bind elapsed time 1.1 .0
connection management call elapsed time 0.7 .0
hard parse (bind mismatch) elapsed time 0.3 .0
DB time 3,322.4 N/A
background elapsed time 197.1 N/A
background cpu time 5.6 N/A
Wait Class DB/Inst: ABCTEST/abctest Snaps: 2151-2152
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc
Avg
%Time Total Wait wait Waits
Wait Class Waits -outs Time (s) (ms) /txn
User I/O 292,720 .0 427 1 5.3
System I/O 37,408 .0 190 5 0.7
Network 272,062 .0 132 0 4.9
Commit 8,617 .0 46 5 0.2
Configuration 4 .0 2 593 0.0
Application 3,212 .0 0 0 0.1
Other 280 .4 0 0 0.0
Concurrency 247 .0 0 0 0.0
Wait Events DB/Inst: ABCTEST/abctest Snaps: 2151-2152
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by 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 284,992 .0 410 1 5.2
log file parallel write 31,188 .0 145 5 0.6
TCP Socket (KGAS) 24 .0 131 5459 0.0
log file sync 8,617 .0 46 5 0.2
db file parallel write 4,215 .0 29 7 0.1
db file sequential read 7,634 .0 16 2 0.1
control file parallel write 1,202 .0 16 13 0.0
Streams AQ: enqueue blocked 1 .0 2 2055 0.0
control file sequential read 795 .0 1 1 0.0
Data file init write 48 .0 0 9 0.0
SQL*Net message to client 266,802 .0 0 0 4.9
log file switch completion 3 .0 0 106 0.0
SQL*Net break/reset to clien 3,212 .0 0 0 0.1
SQL*Net more data to client 4,789 .0 0 0 0.1
direct path write 23 .0 0 3 0.0
rdbms ipc reply 67 .0 0 1 0.0
kksfbc child completion 1 100.0 0 47 0.0
latch: shared pool 213 .0 0 0 0.0
latch: library cache 26 .0 0 1 0.0
log file single write 4 .0 0 7 0.0
log file sequential read 4 .0 0 5 0.0
db file single write 3 .0 0 5 0.0
os thread startup 3 .0 0 4 0.0
enq: JS - queue lock 4 .0 0 3 0.0
LGWR wait for redo copy 207 .0 0 0 0.0
library cache pin 1 .0 0 6 0.0
SQL*Net more data from clien 447 .0 0 0 0.0
library cache load lock 1 .0 0 2 0.0
latch: cache buffers chains 1 .0 0 0 0.0
latch: row cache objects 1 .0 0 0 0.0
direct path read 20 .0 0 0 0.0
latch free 1 .0 0 0 0.0
cursor: mutex S 1 .0 0 0 0.0
SQL*Net message from client 266,789 .0 64,143 240 4.9
Streams AQ: qmn slave idle w 124 .0 3,488 28127 0.0
Streams AQ: qmn coordinator 257 51.4 3,488 13571 0.0
virtual circuit status 116 100.0 3,480 29999 0.0
Streams AQ: waiting for time 5 60.0 745 148902 0.0
jobq slave wait 52 96.2 155 2987 0.0
PL/SQL lock timer 16 100.0 16 995 0.0
class slave wait 1 100.0 5 4995 0.0
Background Wait Events DB/Inst: ABCTEST/abctest Snaps: 2151-2152
-> ordered by wait time desc, waits desc (idle events last)
Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
log file parallel write 31,188 .0 145 5 0.6
db file parallel write 4,215 .0 29 7 0.1
control file parallel write 1,193 .0 16 13 0.0
Streams AQ: enqueue blocked 1 .0 2 2055 0.0
control file sequential read 691 .0 0 1 0.0
db file sequential read 66 .0 0 5 0.0
direct path write 23 .0 0 3 0.0
log file single write 4 .0 0 7 0.0
log file sequential read 4 .0 0 5 0.0
events in waitclass Other 211 .0 0 0 0.0
os thread startup 3 .0 0 4 0.0
db file scattered read 1 .0 0 13 0.0
latch: shared pool 5 .0 0 0 0.0
direct path read 20 .0 0 0 0.0
latch: library cache 1 .0 0 0 0.0
rdbms ipc message 34,411 32.3 30,621 890 0.6
Streams AQ: qmn slave idle w 124 .0 3,488 28127 0.0
Streams AQ: qmn coordinator 257 51.4 3,488 13571 0.0
pmon timer 1,235 100.0 3,486 2822 0.0
smon timer 19 47.4 3,460 182099 0.0
Streams AQ: waiting for time 5 60.0 745 148902 0.0
class slave wait 1 100.0 5 4995 0.0
Operating System Statistics DB/Inst: ABCTEST/abctest Snaps: 2151-2152
Statistic Total
AVG_BUSY_TIME 81,951
AVG_IDLE_TIME 266,698
AVG_SYS_TIME 10,482
AVG_USER_TIME 71,389
BUSY_TIME 328,163
IDLE_TIME 1,067,144
SYS_TIME 42,281
USER_TIME 285,882
RSRC_MGR_CPU_WAIT_TIME 0
VM_IN_BYTES 1,625,600,000
VM_OUT_BYTES 145,162,240
PHYSICAL_MEMORY_BYTES 3,755,851,776
NUM_CPUS 4
NUM_CPU_CORES 1
Brief AWR Report When Performance* Deteriorated.
Snap Id Snap Time Sessions Curs/Sess
Begin Snap: 2168 15-Dec-10 08:31:05 32 18.4
End Snap: 2169 15-Dec-10 09:30:56 32 18.3
Elapsed: 59.85 (mins)
DB Time: 17.97 (mins)
Cache Sizes
~~~~~~~~~~~ Begin End
Buffer Cache: 448M 448M Std Block Size: 8K
Shared Pool Size: 116M 116M Log Buffer: 6,968K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 10,503.58 1,792.02
Logical reads: 17,583.21 2,999.87
Block changes: 68.60 11.70
Physical reads: 472.37 80.59
Physical writes: 1.54 0.26
User calls: 39.12 6.67
Parses: 53.32 9.10
Hard parses: 7.99 1.36
Sorts: 13.84 2.36
Logons: 0.00 0.00
Executes: 130.30 22.23
Transactions: 5.86
% Blocks changed per Read: 0.39 Recursive Call %: 94.39
Rollback per transaction %: 0.00 Rows per Sort: 691.64
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 100.00
Buffer Hit %: 97.31 In-memory Sort %: 100.00
Library Hit %: 92.41 Soft Parse %: 85.02
Execute to Parse %: 59.08 Latch Hit %: 100.00
Parse CPU to Parse Elapsd %: 100.28 % Non-Parse CPU: 95.35
Shared Pool Statistics Begin End
Memory Usage %: 88.40 88.48
% SQL with executions>1: 76.15 80.48
% Memory for SQL w/exec>1: 86.82 88.85
Top 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
CPU time 918 85.1
db file scattered read 113,003 127 1 11.7 User I/O
log file parallel write 11,978 52 4 4.8 System I/O
db file parallel write 3,089 16 5 1.4 System I/O
control file parallel write 1,217 15 13 1.4 System I/O
Time Model Statistics DB/Inst: ABCTEST/abctest Snaps: 2168-2169
-> Total time in database user-calls (DB Time): 1078.1s
-> Statistics including the word "background" measure background process
time, and so do not contribute to the DB time statistic
-> Ordered by % or DB time desc, Statistic name
Statistic Name Time (s) % of DB Time
sql execute elapsed time 1,032.1 95.7
DB CPU 917.6 85.1
parse time elapsed 71.8 6.7
hard parse elapsed time 52.4 4.9
PL/SQL execution elapsed time 7.2 .7
PL/SQL compilation elapsed time 6.2 .6
failed parse elapsed time 1.8 .2
sequence load elapsed time 0.4 .0
repeated bind elapsed time 0.3 .0
connection management call elapsed time 0.1 .0
hard parse (sharing criteria) elapsed time 0.0 .0
hard parse (bind mismatch) elapsed time 0.0 .0
DB time 1,078.1 N/A
background elapsed time 89.4 N/A
background cpu time 6.4 N/A
Wait Class DB/Inst: ABCTEST/abctest Snaps: 2168-2169
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc
Avg
%Time Total Wait wait Waits
Wait Class Waits -outs Time (s) (ms) /txn
User I/O 122,810 .0 133 1 5.8
System I/O 17,013 .0 83 5 0.8
Commit 3,129 .0 14 5 0.1
Network 90,186 .0 0 0 4.3
Configuration 2 .0 0 63 0.0
Application 1,120 .0 0 0 0.1
Other 112 .0 0 0 0.0
Concurrency 2 .0 0 6 0.0
Wait Events DB/Inst: ABCTEST/abctest Snaps: 2168-2169
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by 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 113,003 .0 127 1 5.4
log file parallel write 11,978 .0 52 4 0.6
db file parallel write 3,089 .0 16 5 0.1
control file parallel write 1,217 .0 15 13 0.1
log file sync 3,129 .0 14 5 0.1
db file sequential read 9,753 .0 6 1 0.5
control file sequential read 725 .0 0 0 0.0
Data file init write 32 .0 0 7 0.0
SQL*Net message to client 88,906 .0 0 0 4.2
log file switch completion 2 .0 0 63 0.0
SQL*Net break/reset to clien 1,120 .0 0 0 0.1
rdbms ipc reply 4 .0 0 8 0.0
direct path write 10 .0 0 3 0.0
SQL*Net more data to client 1,120 .0 0 0 0.1
db file single write 2 .0 0 6 0.0
os thread startup 2 .0 0 6 0.0
log file single write 2 .0 0 4 0.0
log file sequential read 2 .0 0 3 0.0
SQL*Net more data from clien 160 .0 0 0 0.0
LGWR wait for redo copy 108 .0 0 0 0.0
direct path read 10 .0 0 0 0.0
SQL*Net message from client 88,906 .0 55,500 624 4.2
virtual circuit status 120 100.0 3,588 29900 0.0
Streams AQ: qmn slave idle w 127 .0 3,550 27949 0.0
Streams AQ: qmn coordinator 260 51.2 3,550 13652 0.0
class slave wait 2 100.0 10 4994 0.0
SGA: MMAN sleep for componen 9 22.2 0 4 0.0
Background Wait Events DB/Inst: ABCTEST/abctest Snaps: 2168-2169
-> ordered by wait time desc, waits desc (idle events last)
Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
log file parallel write 11,978 .0 52 4 0.6
db file parallel write 3,089 .0 16 5 0.1
control file parallel write 1,211 .0 15 13 0.1
db file scattered read 175 .0 0 1 0.0
control file sequential read 33 .0 0 2 0.0
db file sequential read 53 .0 0 1 0.0
direct path write 10 .0 0 3 0.0
os thread startup 2 .0 0 6 0.0
log file single write 2 .0 0 4 0.0
log file sequential read 2 .0 0 3 0.0
events in waitclass Other 108 .0 0 0 0.0
direct path read 10 .0 0 0 0.0
rdbms ipc message 19,991 57.4 31,320 1567 0.9
pmon timer 1,208 100.0 3,590 2972 0.1
Streams AQ: qmn slave idle w 127 .0 3,550 27949 0.0
Streams AQ: qmn coordinator 260 51.2 3,550 13652 0.0
smon timer 12 100.0 3,302 275149 0.0
SGA: MMAN sleep for componen 9 22.2 0 4 0.0
Operating System Statistics DB/Inst: ABCTEST/abctest Snaps: 2168-2169
Statistic Total
AVG_BUSY_TIME 30,152
AVG_IDLE_TIME 328,781
AVG_SYS_TIME 4,312
AVG_USER_TIME 25,757
BUSY_TIME 120,981
IDLE_TIME 1,315,433
SYS_TIME 17,612
USER_TIME 103,369
RSRC_MGR_CPU_WAIT_TIME 0
VM_IN_BYTES 353,361,920
VM_OUT_BYTES 163,041,280
PHYSICAL_MEMORY_BYTES 3,755,851,776
NUM_CPUS 4
NUM_CPU_CORES 1
Request you to help me.
Thanks in Advance,
Rajesh

Hi CKPT,
Thanks for your reply.
The main finding that I have got from addm report (in both the cases i.e when performance was good initially vis a vis when performance deteriorated is the same -
FINDING 1: 100% impact (3234 seconds)
Significant virtual memory paging was detected on the host operating system.
RECOMMENDATION 1: Host Configuration, 100% benefit (3234 seconds)
ACTION: Host operating system was experiencing significant paging but no
particular root cause could be detected. Investigate processes that
do not belong to this instance running on the host that are consuming
significant amount of virtual memory. Also consider adding more
physical memory to the host.
I still am unable to find out the reasons ... pls help.
Thanks
Rajesh

PerfMon reporting dramatic disk access time increase on Oracle startup

Hi,
My oracle 10g (10.2.0.4) database is hosted on a windows 2003 server.
The datafiles are stored on a RAID1 disk array, on a dedicated partition : currently 30 gigs free out of 180, wich should not be a concern unless i'm wrong, because the datafiles were created as 10 Go files with no autogrowth. I add a new datafile whenever i need more room for my tables (alerts when 80% used).
Since 2 days i experience a dramatic performance loss :
The EM console reports nothing special (no alarms related to storage) apart from the need for more paginated memory.
I issue a reorg when the segmentation advisor suggests it.
My optimizer statistics are calculated by the default scheduled job.
The weird thing I noticed is that as soon as I start the database, there's a huge increase in disk activity even though no query at all is submitted to the database.
PerfMon reports Current Disk Queue Length > 1000 and disk access time > 3000 ms
CPU is 2% activity on the 4-cpus server.
I have plenty of spare memory (currently 3 Go used out of 16).
This is only a dev server for ETL processes, it has very few concurrent connections.
Any suggestions welcome.
AWR report is available here
http://min.us/mqnXQhd5Z
Edited by: user10799939 on 22 mars 2012 09:30

Cache Sizes
~~~~~~~~~~~                       Begin        End
               Buffer Cache:     1,296M     1,296M Std Block Size:         8K
           Shared Pool Size:       160M       160M      Log Buffer:    14,364K
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                  Redo size:            460,955.72 ;         2,477,358.63
              Logical reads:              3,392.16 ;            18,230.80
              Block changes:              6,451.93 ;            34,675.22
             Physical reads:                  2.92 ;                15.67
            Physical writes:                394.52 ;             2,120.28
                 User calls:                  1.69 ;                 9.08
                     Parses:                  3.31 ;                17.81
                Hard parses:                  0.17 ;                 0.90
                      Sorts:                  1.32 ;                 7.09
                     Logons:                  0.06 ;                 0.31
                   Executes:                  7.01 ;                37.68
               Transactions:                  0.19
% Blocks changed per Read: 190.20 ;   Recursive Call %:    96.23
Rollback per transaction %:    0.30 ;      Rows per Sort:    14.41
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            Buffer Nowait %:   99.98 ;      Redo NoWait %:   99.86
            Buffer Hit   %:   99.92 ;   In-memory Sort %: 100.00
            Library Hit   %:   96.30 ;       Soft Parse %:   94.96
         Execute to Parse %:   52.74 ;        Latch Hit %:   99.07
Parse CPU to Parse Elapsd %:    0.35 ;    % Non-Parse CPU:   99.30
Shared Pool Statistics        Begin    End
             Memory Usage %:   75.48 ; 75.51
    % SQL with executions>1:   79.92 ; 85.03
% Memory for SQL w/exec>1:   77.07 ; 70.09
Top 5 Timed Events                                         Avg %Total
~~~~~~~~~~~~~~~~~~                                        wait   Call
Event                                 Waits    Time (s)   (ms)   Time Wait Class
db file sequential read               9,052      17,688   1954   51.3 ; User I/O
log file switch (checkpoint in        5,303       4,649    877   13.5 Configurat
log file switch completion            4,245       4,023    948   11.7 Configurat
wait for a undo record               32,393       3,531    109   10.3 ;     Other
db file parallel write               18,771       3,437    183   10.0 System I/O Havent seen this much wait on average. For example 877ms for "log file switch" is over threshold. And other wait events too..
Time Model Statistics                DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> Total time in database user-calls (DB Time): 34446.5s
-> Statistics including the word "background" measure background process
   time, and so do not contribute to the DB time statistic
-> Ordered by % or DB time desc, Statistic name
Statistic Name                                       Time (s) % of DB Time
sql execute elapsed time                              4,008.5 ;        11.6
parse time elapsed                                      352.9 ;         1.0
hard parse elapsed time                                 352.7 ;         1.0
PL/SQL compilation elapsed time                         120.1 ;          .3
DB CPU                                                   61.8 ;          .2
failed parse elapsed time                                21.3 ;          .1
PL/SQL execution elapsed time                             8.0 ;          .0
connection management call elapsed time                   0.0 ;          .0
hard parse (sharing criteria) elapsed time                0.0 ;          .0
repeated bind elapsed time                                0.0 ;          .0
hard parse (bind mismatch) elapsed time                   0.0 ;          .0
DB time                                              34,446.5 ;         N/A
background elapsed time                              14,889.7 ;         N/A
background cpu time                                      39.0 ;         N/A
Wait Class                            DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> s - second
-> cs - centisecond -     100th of a second
-> ms - millisecond -    1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc
                                                                  Avg
                                       %Time       Total Wait    wait     Waits
Wait Class                      Waits -outs         Time (s)    (ms)      /txn
User I/O                       10,515     .1           17,785    1691      15.8
Configuration                  10,186   79.5 ;           8,865     870      15.3
System I/O                     27,619     .0            8,774     318      41.6
Other                          57,768   98.3 ;           6,915     120      87.0
Commit                          2,634   88.6 ;           2,481     942       4.0
Concurrency                     2,847   75.4 ;           2,240     787       4.3
Application                       219    2.3 ;              23     105       0.3
Network                         4,790     .0                0       0       7.2
          ------------------------------------------------------------- again seen, there is very high wait on User IO
Wait Events                          DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> s - second
-> cs - centisecond -     100th of a second
-> ms - millisecond -    1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc (idle events last)
                                                                   Avg
                                             %Time Total Wait    wait     Waits
Event                                 Waits -outs    Time (s)    (ms)      /txn
db file sequential read               9,052     .0      17,688    1954      13.6
log file switch (checkpoint           5,303   78.0 ;      4,649     877       8.0
log file switch completion            4,245   89.2 ;      4,023     948       6.4
wait for a undo record               32,393   99.8 ;      3,531     109      48.8
db file parallel write               18,771     .0       3,437     183      28.3
wait for stopper event to be         24,203   99.8 ;      2,634     109      36.5
log file sync                         2,634   88.6 ;      2,481     942       4.0
control file sequential read          7,356     .0       2,431     330      11.1
buffer busy waits                     2,513   83.1 ;      2,173     865       3.8
log file parallel write                 520     .0       1,566    3012       0.8
control file parallel write             840     .0       1,334    1588       1.3
rdbms ipc reply                         172   91.3 ;        330    1916       0.3
enq: CF - contention                    309   23.0 ;        268     867       0.5
log buffer space                        638   28.5 ;        192     301       1.0
enq: PS - contention                     52   23.1 ;         71    1362       0.1
db file scattered read                  113     .0          67     590       0.2
os thread startup                        76   77.6 ;         63     834       0.1
reliable message                         57   78.9 ;         50     878       0.1
enq: RO - fast object reuse              22   22.7 ;         23    1038       0.0
latch free                              537     .0          16      30       0.8
Streams AQ: qmn coordinator               3 100.0 ;         15    5005       0.0 Overstepping
Background Wait Events               DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> ordered by wait time desc, waits desc (idle events last)
                                                                   Avg
                                             %Time Total Wait    wait     Waits
Event                                 Waits -outs    Time (s)    (ms)      /txn
db file parallel write               18,772     .0       3,437     183      28.3
events in waitclass Other            24,367   99.5 ;      3,010     124      36.7
control file sequential read          6,654     .0       2,333     351      10.0
log file parallel write                 520     .0       1,566    3012       0.8
control file parallel write             840     .0       1,334    1588       1.3
buffer busy waits                       899   94.2 ;        884     984       1.4
log file switch (checkpoint             206   82.0 ;        185     898       0.3
os thread startup                        76   77.6 ;         63     834       0.1
log file switch completion               46   93.5 ;         45     982       0.1
log buffer space                        158   31.0 ;         12      77       0.2
db file sequential read                  62     .0           7     111       0.1
db file scattered read                   20     .0           6     318       0.0
direct path read                        660     .0           5       7       1.0
log file sequential read                 66     .0           4      65       0.1
log file single write                    66     .0           1      16       0.1
enq: RO - fast object reuse               2     .0           0      38       0.0
latch: cache buffers chains               3     .0           0       6       0.0
direct path write                       660     .0          -5      -8       1.0
rdbms ipc message                     9,052   87.5 ;     21,399    2364      13.6
pmon timer                            1,318   90.4 ;      3,562    2703       2.0
Streams AQ: qmn coordinator             633   97.6 ;      3,546    5602       1.0
Streams AQ: waiting for time             77   61.0 ;      3,449   44795       0.1
PX Deq: Join ACK                         21     .0           0       0       0.0 Again overshooting
Tablespace IO Stats                  DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> ordered by IOs (Reads + Writes) desc
Tablespace
                 Av      Av     Av                       Av     Buffer Av Buf
         Reads Reads/s Rd(ms) Blks/Rd       Writes Writes/s      Waits Wt(ms)
UNDOTBS1
           914       0 ######     1.0 ;   1,368,515      383      2,534 863.2
MDMREF_INDICES
         6,918       2 ######     1.0 ;      11,086        3          0    0.0
SYSAUX
           626       0 ######     1.1 ;       1,804        1          0    0.0
SYSTEM
           850       0 ######     1.7 ;         296        0          0    0.0
MDMREF_DATA
           293       0 712.3 ;    1.0 ;         274        0          0    0.0
MDMPRJ_ODS
           198       0   72.1 ;    1.0 ;         198        0          0    0.0
FEU_VERT
            33       0   61.5 ;    1.0 ;          33        0          0    0.0
USERS
            33       0   31.5 ;    1.0 ;          33        0          0    0.0
          ------------------------------------------------------------- Now have a serious look at it. Av Rd(ms). Now for some tablespace value cannot event fit in window thats why its showing ##
According to oracle recommendation Av Rd(ms) shouldn't be greater then 20, if its goes over 20 then its considered to be an issue with IO subsystem. But as its seen that in your case its overshooting.
Now the question from my side
Have done any configuration changes?
I would suggest you to revert these changes asap and contact storage admin guys...
Hope this helps

Cluster multi-block requests were consuming significant database time

Hi,
DB : 10.2.0.4 RAC ASM
OS : AIX 5.2 64-bit
We are facing too much performance issues and CPU idle time becoming 20%.Based on the AWR report , the top 5 events are showing that problem is in cluster side.I placed 1st node AWR report here for your suggestions.
WORKLOAD REPOSITORY report for
DB Name DB Id Instance Inst Num Release RAC Host
PROD 1251728398 PROD1 1 10.2.0.4.0 YES msprod1
Snap Id Snap Time Sessions Curs/Sess
Begin Snap: 26177 26-Jul-11 14:29:02 142 37.7
End Snap: 26178 26-Jul-11 15:29:11 159 49.1
Elapsed: 60.15 (mins)
DB Time: 915.85 (mins)
Cache Sizes
~~~~~~~~~~~ Begin End
Buffer Cache: 23,504M 23,504M Std Block Size: 8K
Shared Pool Size: 27,584M 27,584M Log Buffer: 14,248K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 28,126.82 2,675.18
Logical reads: 526,807.26 50,105.44
Block changes: 3,080.07 292.95
Physical reads: 962.90 91.58
Physical writes: 157.66 15.00
User calls: 1,392.75 132.47
Parses: 246.05 23.40
Hard parses: 11.03 1.05
Sorts: 42.07 4.00
Logons: 0.68 0.07
Executes: 930.74 88.52
Transactions: 10.51
% Blocks changed per Read: 0.58 Recursive Call %: 32.31
Rollback per transaction %: 9.68 Rows per Sort: 4276.06
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.87 Redo NoWait %: 100.00
Buffer Hit %: 99.84 In-memory Sort %: 99.99
Library Hit %: 98.25 Soft Parse %: 95.52
Execute to Parse %: 73.56 Latch Hit %: 99.51
Parse CPU to Parse Elapsd %: 9.22 % Non-Parse CPU: 99.94
Shared Pool Statistics Begin End
Memory Usage %: 68.11 71.55
% SQL with executions>1: 94.54 92.31
% Memory for SQL w/exec>1: 98.79 98.74
Top 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
CPU time 18,798 34.2
gc cr multi block request 46,184,663 18,075 0 32.9 Cluster
gc buffer busy 2,468,308 6,897 3 12.6 Cluster
gc current block 2-way 1,826,433 4,422 2 8.0 Cluster
db file sequential read 142,632 366 3 0.7 User I/O
RAC Statistics DB/Inst: PROD/PROD1 Snaps: 26177-26178
Begin End
Number of Instances: 2 2
Global Cache Load Profile
~~~~~~~~~~~~~~~~~~~~~~~~~ Per Second Per Transaction
Global Cache blocks received: 14,112.50 1,342.26
Global Cache blocks served: 619.72 58.94
GCS/GES messages received: 2,099.38 199.68
GCS/GES messages sent: 23,341.11 2,220.01
DBWR Fusion writes: 3.43 0.33
Estd Interconnect traffic (KB) 122,826.57
Global Cache Efficiency Percentages (Target local+remote 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer access - local cache %: 97.16
Buffer access - remote cache %: 2.68
Buffer access - disk %: 0.16
Global Cache and Enqueue Services - Workload Characteristics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg global enqueue get time (ms): 0.6
Avg global cache cr block receive time (ms): 2.8
Avg global cache current block receive time (ms): 3.0
Avg global cache cr block build time (ms): 0.0
Avg global cache cr block send time (ms): 0.0
Global cache log flushes for cr blocks served %: 11.3
Avg global cache cr block flush time (ms): 1.7
Avg global cache current block pin time (ms): 0.0
Avg global cache current block send time (ms): 0.0
Global cache log flushes for current blocks served %: 0.0
Avg global cache current block flush time (ms): 4.1
Global Cache and Enqueue Services - Messaging Statistics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg message sent queue time (ms): 0.1
Avg message sent queue time on ksxp (ms): 2.4
Avg message received queue time (ms): 0.0
Avg GCS message process time (ms): 0.0
Avg GES message process time (ms): 0.0
% of direct sent messages: 6.27
% of indirect sent messages: 93.48
% of flow controlled messages: 0.25
Time Model Statistics DB/Inst: PROD/PROD1 Snaps: 26177-26178
-> Total time in database user-calls (DB Time): 54951s
-> Statistics including the word "background" measure background process
time, and so do not contribute to the DB time statistic
-> Ordered by % or DB time desc, Statistic name
Statistic Name Time (s) % of DB Time
sql execute elapsed time 54,618.2 99.4
DB CPU 18,798.1 34.2
parse time elapsed 494.3 .9
hard parse elapsed time 397.4 .7
PL/SQL execution elapsed time 38.6 .1
hard parse (sharing criteria) elapsed time 27.3 .0
sequence load elapsed time 5.0 .0
failed parse elapsed time 3.3 .0
PL/SQL compilation elapsed time 2.1 .0
inbound PL/SQL rpc elapsed time 1.2 .0
repeated bind elapsed time 0.8 .0
connection management call elapsed time 0.6 .0
hard parse (bind mismatch) elapsed time 0.3 .0
DB time 54,951.0 N/A
background elapsed time 1,027.9 N/A
background cpu time 518.1 N/A
Wait Class DB/Inst: PROD/PROD1 Snaps: 26177-26178
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc
Avg
%Time Total Wait wait Waits
Wait Class Waits -outs Time (s) (ms) /txn
Cluster 50,666,311 .0 30,236 1 1,335.4
User I/O 419,542 .0 811 2 11.1
Network 4,824,383 .0 242 0 127.2
Other 797,753 88.5 208 0 21.0
Concurrency 212,350 .1 121 1 5.6
Commit 16,215 .0 53 3 0.4
System I/O 60,831 .0 29 0 1.6
Application 6,069 .0 6 1 0.2
Configuration 763 97.0 0 0 0.0
Second node top 5 events are as below,
Top 5 Timed Events
Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
CPU time 25,959 42.2
db file sequential read 2,288,168 5,587 2 9.1 User I/O
gc current block 2-way 822,985 2,232 3 3.6 Cluster
read by other session 345,338 1,166 3 1.9 User I/O
gc cr multi block request 991,270 831 1 1.4 Cluster
My RAM is 95GB each node and SGA is 51 GB and PGA is 14 GB.
Any inputs from your side are greatly helpful to me ,please.
Thanks,
Sunand

Hi Forstmann,
Thanks for your update.
Even i have collected ADDM report, extract of Node1 report as below
FINDING 1: 40% impact (22193 seconds)
Cluster multi-block requests were consuming significant database time.
RECOMMENDATION 1: SQL Tuning, 6% benefit (3313 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"59qd3x0jg40h1". Look for an alternative plan that does not use
object scans.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Inter-instance messaging was consuming significant database
time on this instance. (55% impact [30269 seconds])
SYMPTOM: Wait class "Cluster" was consuming significant database
time. (55% impact [30271 seconds])
FINDING 3: 13% impact (7008 seconds)
Read and write contention on database blocks was consuming significant
database time.
NO RECOMMENDATIONS AVAILABLE
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Inter-instance messaging was consuming significant database
time on this instance. (55% impact [30269 seconds])
SYMPTOM: Wait class "Cluster" was consuming significant database
time. (55% impact [30271 seconds])
Any help from your side , please?
Thanks,
Sunand

Binding model nodes - seeming repetition?

Hello,
When creating a WD app using Adaptive RFC Model (or any model I assume), it is necessary to create a data link between the Model and Component Controller. Visually, the fields of the nodes of the Model and the fields of the model nodes of the Controller are linked. Why, then, is it necessary to again bind the model node of the Controller to the model object using the ".bind" method?
Code as shown here is a classic example:
     Bapi_Usr01Dohr_Getemployee_Input bapiInput = new Bapi_Usr01Dohr_Getemployee_Input();
     wdContext.nodeBapi_Usr01Dohr_Getemployee_Input().bind(bapiInput);
     bapiInput.setId("MY_USERID");
     try {
          bapiInput.execute();
     } catch (Exception exc) {
          IWDMessageManager msgManager = wdComponentAPI.getMessageManager();
          msgManager.raiseException(exc.getMessage(), true);
Clearly the visual binding in the diagram view of the component controller and the programmatic binding using the .bind method of the model node are doing different things. My question is, what is the difference? Why are both required?

Michael,
There are actually 3 activity types, and sadly one of them has not the best name:
1. Map at run-time / design-time model to context node (make metadata structure, that mimics model structure, possibly with renaming of target attributes / sub-nodes)
2. Map at run-time / design-time (or as you say "link") 2 nodes in different controllers (make metadata structure, that mimics structure of node's metadata in another controller, possibly with renaming of target attributes / sub-nodes)
3. "Bind" at run-time-only data to node, that was previously described as metadata either using IDE at design-time or at run-time.
So, there is no repetition: you create metadata once (ok, more logically "once" then physically), then you may assign different data to resulted node via bind several times.
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

Db Time in Statspack report...

Hi ,
I generated a statspack report of 22 minutes duration.
In the Instance Activity Stats DB/Inst portion of the report , there are the following figures , regarding the Db Time statistic:
Total Per Second Per Transaction
530,488 400.7 1,449.4
whereas in the Time Model System Stats DB/Inst portion of the report , there is the following:
Time (s)
Db Time 94.2
When the report was generated , there were a typical number of sessions that Oracle creates (sys , system , e.t.c.) and just one application user who has been runnning some forms -developed in Oracle Forms 10g.
How the above figures can be explained..?????
Thanks , a lot
Simon
Message was edited by:
sgalaxy

The figure 530,488 shows the total amount of time since the instance startup.
The question is in which metric the Per Second Instance Activity Stats DB/Inst is calculated (i.e. the value of 400.7)- in seconds , milliseconds ...????
Simon

Statspackの「CPU time」と「DB CPU」の違い

お世話になっております。
Statspackを取得し調査しているのですが、
下記の二つ項目のtime(s)がまったく一致しません。（桁が異なるほど）
①「Top 5 Timed Events」の「CPU time」
②「Time Model System Stats,SQL ordered by CPU」等の「DB　CPU」
この二つの項目はSQLに使用したCPU時間だと考えていました。
定義の違いをご存知の方がいらっしゃいましたら、教えていただけないでしょうか。
以上、宜しくお願い致します。

こんにちは。
英語記事ですが･･･
http://www.dba-oracle.com/m_db_cpu.htm
元ネタ
https://kr.forums.oracle.com/forums/thread.jspa?threadID=665376

Is there any issue in scheduling GATHER_STATS_JOB during peak load times?

Hi All,
The default DBMS_STATS job(GATHER_STATS_JOB) is running during our peak load time.
Will it have any performance impact on normal database transactions?
Is it better to reschedule that window?
What all problems can we expect during the job's run(Object locks, High I/O due to table/index reads, High CPU usage etc)?
Please help me in getting the answer. I could not find relevant information from net.
Thanks and regards
Satish

Satish V C wrote:
I am struggling to find an appropriate period to run the job as this database is active 24*7 globally.
I want to know how the activity should be measured. Should it be based on no of sessions or number of transactions or number of cursors or net I/O or a combination of all above?Satish,
if you have the AWR license you could check the AWR reports to find out when your database is most idle. In the 10g time model the most significant aspect is the DB time spent, so the period where the DB time is least might be a good candidate.
You can also check the number of logical/physical I/Os performed per second, the number of sessions, and other ratios that are shown in the top part of the AWR report (e.g. section "Load Profile").
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Modeling critique requested...

i'm doing a small java-based project that involves creating a class (let's call it Experiment).
the class Experiment itself contains a number of objects .
(e.g. GregorianCalendar holds the value for when an instance of the Experiment class was begun)
Experiment also contains a collection of instances of the class Bacteria
Experiment also contains a collection of instances of the class Antibiotic
etc. etc.
during the running of the program, instances of the Experiment class may be saved to a file in serialized form for later use.
the issue that i'm running up against is that in the process of building this program, the requirements of what I think belongs in the Experiment class changes (e.g. I forgot that the experiment antibiotic class needs to hold information about the molecular weight of the antibiotic). Now it's not a big deal to change the class Antibiotic to incorporate methods and a variable that holds/returns molecular weight, but in doing so, I make all of my old serialized files obsolete.
I'm guessing that at some level this is a common issue, but how do you minimize the creation of obsolete object classes?
is it just a matter of me not having spent enough time modeling the issue (i find this a little hard to believe simply because requirements must change from time-to-time for everyone who programs)?
or is it a matter that i'm setting up the Experiment class improperly ?
or is it an issue of "you just have to deal with it, and write small programs that convert your 'legacy'
serialized objects into the new form"?
or something else entirely?
anyway...I'm curious as to any opinions that might be out there.
thanks in advance.

Yeah. If you think it'll work for you. You store all
of the variables of the experiment in the Properties
(or Map) and add new ones on-the-fly.yeah, i'm still not sure i like this approach...it seems like all it does is turn the Experiment object into a giant Map and other objects interacting with Experiment must then bear the burden of figuring out what all of its map properties mean.
again...maybe i'm wrong here, but it seems to me that the Experiment object should by itself be able to determine how many antibiotics are present in it, and tell you what the molecular weights are for those antibiotics.
if you just make a gigantic map with one generic method the experiment object can't really do that anymore...unless of course you upgrade the # of methods every time you make an improvement to the Experiment class...but if you do this, then you still wind up with a bunch of obsolete serialized objects.

Copying data between models

Hi Gurus,
I need help in copying data between models. Below is the scenario.
Model A (Source model)
It contains plan data:
Important dimensions: Facility, Product, Time
Model B (Target model)
Important dimensions: Facility, Product, Time; Additional dimensions: Cost Center, Cost Element
Model C (For lookup while copying data)
Important Dimensions: Facility, Product, Time, Cost Center, Cost Element
Task:
Copy data from A to B and populate cost center and cost element in B by lookup C (key for lookup is Facility, Product, Time)
Please let me know the required steps to do the job.
Can we do it using logic script and avoid BADI?
Which data package should I use?
Thanks.

Hi Vadim,
It seems like I can move the data from A to B while data gets saved in A using input screen.
So far I have written below which is working fine. For now I am hard coding the cost center, now I need to know how to lookup to the other model. Please review and let me know. Thanks.
*XDIM_MEMBERSET P_ACCOUNT = VOLUME, REVENUE
*XDIM_MEMBERSET P_CATEGORY = Forecast
*DESTINATION_APP = PLANNING_RETRACTION
*ADD_DIM COST_CENTER = 3000011
*WHEN P_ACCOUNT
*IS "VOLUME", "REVENUE"
*REC(EXPRESSION = %VALUE%)
*ENDWHEN

Time Model

Similar Messages

Maybe you are looking for