How much Redo log is being generated by a user sesssion?

How can find which user session is creating the highest redolog entries and how much rego log is being generated?

1) Query V$SESS_IO. This view contains the column BLOCK_CHANGES which indicates how much blocks have been changed by the session. High values indicate a session generating lots of redo.
The query you can use is:
SQL> SELECT s.sid, s.serial#, s.username, s.program,
2 i.block_changes
3 FROM v$session s, v$sess_io i
4 WHERE s.sid = i.sid
5 ORDER BY 5 desc, 1, 2, 3, 4;
Run the query multiple times and examine the delta between each occurrence of BLOCK_CHANGES. Large deltas indicate high redo generation by the session.
2) Query V$TRANSACTION. This view contains information about the amount of undo blocks and undo records accessed by the transaction (as found in the USED_UBLK and USED_UREC columns).
The query you can use is:
SQL> SELECT s.sid, s.serial#, s.username, s.program,
2 t.used_ublk, t.used_urec
3 FROM v$session s, v$transaction t
4 WHERE s.taddr = t.addr
5 ORDER BY 5 desc, 6 desc, 1, 2, 3, 4;
Run the query multiple times and examine the delta between each occurrence of USED_UBLK and USED_UREC. Large deltas indicate high redo generation by the session.
You use the first query when you need to check for programs generating lots of redo when these programs activate more than one transaction. The latter query can be used to find out which particular transactions are generating redo.

Similar Messages

  • How can I turn off archive logs are being generated by system? (ugrent)

    Dear all,
    How can I turn off archive logs are being generated by system?
    Best Regards,
    Amy

    Sorry not to you @kamran its to OP.accidently it reply button pressed for you
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area  171966464 bytes
    Fixed Size                   787988 bytes
    Variable Size             145750508 bytes
    Database Buffers           25165824 bytes
    Redo Buffers                 262144 bytes
    Database mounted.
    SQL> alter database noarchivelog
      2  /
    Database altered.
    SQL> Khurram

  • Too much redo log files...

    Hi,
    I have a very light application in Oracle 9.2.0.7 in Linux-32bits that is generating 400 logfiles a day. I can´t find why those logs are being generated!
    The only thing relevant in that application is a big table that serves only for insert command (1000 per hour) for audit reasons. But this table was created with NOLOGGING option.
    Redo Size: 4 groups of 40 Mb each.
    The insert statement uses a sequence to generate a unique key. Is this sequence causing my big logfile generation?
    Thanks,
    Paulo.

    Here is the statspack:
    STATSPACK report for
    DB Name         DB Id    Instance     Inst Num Release     Cluster Host
    DB             378381468 DB                  1 9.2.0.7.0   NO      host
                Snap Id     Snap Time      Sessions Curs/Sess Comment
    Begin Snap:      12 28-Jun-07 11:05:11       26   1,198.7
      End Snap:      13 28-Jun-07 12:05:24       29   1,077.2
       Elapsed:               60.22 (mins)
    Cache Sizes (end)
    ~~~~~~~~~~~~~~~~~
                   Buffer Cache:       512M      Std Block Size:         8K
               Shared Pool Size:       512M          Log Buffer:     5,120K
    Load Profile
    ~~~~~~~~~~~~                            Per Second       Per Transaction
                      Redo size:            281,252.38              2,073.48
                  Logical reads:             73,113.76                539.02
                  Block changes:              3,133.29                 23.10
                 Physical reads:                  3.24                  0.02
                Physical writes:                 21.39                  0.16
                     User calls:                 26.12                  0.19
                         Parses:                145.64                  1.07
                    Hard parses:                  0.81                  0.01
                          Sorts:                138.33                  1.02
                         Logons:                  0.69                  0.01
                       Executes:                443.27                  3.27
                   Transactions:                135.64
      % Blocks changed per Read:    4.29    Recursive Call %:    98.97
    Rollback per transaction %:    0.13       Rows per Sort:    17.26
    Instance Efficiency Percentages (Target 100%)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                Buffer Nowait %:   99.99       Redo NoWait %:  100.00
                Buffer  Hit   %:  100.00    In-memory Sort %:   99.99
                Library Hit   %:   99.66        Soft Parse %:   99.44
             Execute to Parse %:   67.14         Latch Hit %:   99.93
    Parse CPU to Parse Elapsd %:   55.03     % Non-Parse CPU:   99.22
    Shared Pool Statistics        Begin   End
                 Memory Usage %:   91.06   91.23
        % SQL with executions>1:   44.54   39.78
      % Memory for SQL w/exec>1:   43.09   33.89
    Top 5 Timed Events
    ~~~~~~~~~~~~~~~~~~                                                     % Total
    Event                                               Waits    Time (s) Ela Time
    CPU time                                                        3,577    84.73
    log file parallel write                           854,726         359     8.51
    row cache lock                                     56,780         104     2.47
    process startup                                       172          91     2.16
    SQL*Net message from dblink                         5,001          22      .53
    Wait Events for DB: DB  Instance: DB  Snaps: 12 -13
    -> 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
                                                         Total Wait   wait    Waits
    Event                               Waits   Timeouts   Time (s)   (ms)     /txn
    log file parallel write           854,726          0        359      0      1.7
    row cache lock                     56,780          0        104      2      0.1
    process startup                       172          4         91    530      0.0
    SQL*Net message from dblink         5,001          0         22      4      0.0
    log file sync                       3,015          3         19      6      0.0
    enqueue                               471          1          9     20      0.0
    buffer busy waits                  20,290          0          8      0      0.0
    db file sequential read             3,853          0          6      2      0.0
    SQL*Net more data from dblin       88,584          0          5      0      0.2
    control file parallel write         1,704          0          5      3      0.0
    latch free                          1,404        748          4      3      0.0
    single-task message                   134          0          4     27      0.0
    LGWR wait for redo copy             8,230          1          2      0      0.0
    log file switch completion             60          0          2     32      0.0
    log file sequential read            1,333          0          2      1      0.0
    control file sequential read        4,530          0          1      0      0.0
    db file scattered read                246          0          0      1      0.0
    SQL*Net more data to client         7,292          0          0      0      0.0
    SQL*Net break/reset to clien           72          0          0      1      0.0
    db file parallel write              4,568          0          0      0      0.0
    log file single write                  62          0          0      0      0.0
    async disk IO                       3,410          0          0      0      0.0
    SQL*Net message to dblink           5,001          0          0      0      0.0
    direct path read (lob)                 84          0          0      0      0.0
    direct path read                      318          0          0      0      0.0
    direct path write                     312          0          0      0      0.0
    buffer deadlock                       115        115          0      0      0.0
    SQL*Net message from client        86,475          0     27,758    321      0.2
    jobq slave wait                     4,594      4,532     13,455   2929      0.0
    SQL*Net more data from clien          602          0          1      2      0.0
    SQL*Net message to client          86,481          0          0      0      0.2
    Background Wait Events for DB: DB  Instance: DB  Snaps: 12 -13
    -> ordered by wait time desc, waits desc (idle events last)
                                                                       Avg
                                                         Total Wait   wait    Waits
    Event                               Waits   Timeouts   Time (s)   (ms)     /txn
    log file parallel write           854,744          0        359      0      1.7
    control file parallel write         1,704          0          5      3      0.0
    LGWR wait for redo copy             8,230          1          2      0      0.0
    log file sequential read            1,333          0          2      1      0.0
    control file sequential read        1,849          0          1      1      0.0
    db file parallel write              4,567          0          0      0      0.0
    latch free                             74          0          0      0      0.0
    rdbms ipc reply                        65          0          0      0      0.0
    log file single write                  62          0          0      0      0.0
    async disk IO                       3,410          0          0      0      0.0
    db file sequential read                 1          0          0      8      0.0
    buffer busy waits                       5          0          0      0      0.0
    direct path read                      248          0          0      0      0.0
    direct path write                     248          0          0      0      0.0
    rdbms ipc message                 868,357      6,776     30,095     35      1.8
    pmon timer                          1,204      1,204      3,529   2931      0.0
    smon timer                            154          0      3,514  22816      0.0
    Instance Activity Stats for DB: DB  Instance: DB  Snaps: 12 -13
    Statistic                                      Total     per Second    per Trans
    active txn count during cleanout               2,844            0.8          0.0
    background checkpoints completed                  31            0.0          0.0
    background checkpoints started                    31            0.0          0.0
    background timeouts                            7,956            2.2          0.0
    branch node splits                                15            0.0          0.0
    buffer is not pinned count               324,721,116       89,875.8        662.6
    buffer is pinned count                   308,901,876       85,497.3        630.3
    bytes received via SQL*Net from c          8,048,130        2,227.6         16.4
    bytes received via SQL*Net from d        181,575,342       50,256.1        370.5
    bytes sent via SQL*Net to client          33,964,494        9,400.6         69.3
    bytes sent via SQL*Net to dblink             933,170          258.3          1.9
    calls to get snapshot scn: kcmgss          9,900,434        2,740.2         20.2
    calls to kcmgas                              985,222          272.7          2.0
    calls to kcmgcs                               11,669            3.2          0.0
    change write time                              9,910            2.7          0.0
    cleanout - number of ktugct calls             18,903            5.2          0.0
    cleanouts and rollbacks - consist                 33            0.0          0.0
    cleanouts only - consistent read                 932            0.3          0.0
    cluster key scan block gets                  289,955           80.3          0.6
    cluster key scans                            101,840           28.2          0.2
    commit cleanout failures: block l                  0            0.0          0.0
    commit cleanout failures: buffer                 113            0.0          0.0
    commit cleanout failures: callbac                 96            0.0          0.0
    commit cleanout failures: cannot               3,095            0.9          0.0
    commit cleanouts                           1,966,376          544.3          4.0
    commit cleanouts successfully com          1,963,072          543.3          4.0
    commit txn count during cleanout             309,283           85.6          0.6
    consistent changes                         5,245,452        1,451.8         10.7
    consistent gets                          242,967,989       67,248.3        495.8
    consistent gets - examination            135,768,580       37,577.8        277.0
    CPU used by this session                     357,659           99.0          0.7
    CPU used when call started                   344,951           95.5          0.7
    CR blocks created                                768            0.2          0.0
    current blocks converted for CR                    0            0.0          0.0
    cursor authentications                           886            0.3          0.0
    data blocks consistent reads - un              1,760            0.5          0.0
    db block changes                          11,320,580        3,133.3         23.1
    db block gets                             21,192,200        5,865.5         43.2
    DBWR buffers scanned                               0            0.0          0.0
    DBWR checkpoint buffers written               69,649           19.3          0.1
    DBWR checkpoints                                  31            0.0          0.0
    DBWR free buffers found                            0            0.0          0.0
    DBWR lru scans                                     0            0.0          0.0
    DBWR make free requests                            0            0.0          0.0
    DBWR revisited being-written buff                  0            0.0          0.0
    DBWR summed scan depth                             0            0.0          0.0
    DBWR transaction table writes                  2,070            0.6          0.0
    DBWR undo block writes                        44,323           12.3          0.1
    deferred (CURRENT) block cleanout            745,333          206.3          1.5
    dirty buffers inspected                            1            0.0          0.0
    enqueue conversions                            8,193            2.3          0.0
    enqueue deadlocks                                  1            0.0          0.0
    enqueue releases                           2,002,960          554.4          4.1
    enqueue requests                           2,002,963          554.4          4.1
    enqueue timeouts                                   3            0.0          0.0
    enqueue waits                                    451            0.1          0.0
    Instance Activity Stats for DB: DB  Instance: DB  Snaps: 12 -13
    Statistic                                      Total     per Second    per Trans
    exchange deadlocks                               115            0.0          0.0
    execute count                              1,601,528          443.3          3.3
    free buffer inspected                             30            0.0          0.0
    free buffer requested                      1,196,628          331.2          2.4
    hot buffers moved to head of LRU              26,707            7.4          0.1
    immediate (CR) block cleanout app                965            0.3          0.0
    immediate (CURRENT) block cleanou             10,817            3.0          0.0
    index fast full scans (full)                       0            0.0          0.0
    index fetch by key                       131,028,270       36,265.8        267.4
    index scans kdiixs1                       17,868,907        4,945.7         36.5
    leaf node splits                               4,528            1.3          0.0
    leaf node 90-10 splits                         3,017            0.8          0.0
    logons cumulative                              2,499            0.7          0.0
    messages received                            859,631          237.9          1.8
    messages sent                                859,631          237.9          1.8
    no buffer to keep pinned count                21,253            5.9          0.0
    no work - consistent read gets            87,667,752       24,264.5        178.9
    opened cursors cumulative                    528,984          146.4          1.1
    OS Involuntary context switches                    0            0.0          0.0
    OS Page faults                                     0            0.0          0.0
    OS Page reclaims                                   0            0.0          0.0
    OS System time used                                0            0.0          0.0
    OS User time used                                  0            0.0          0.0
    OS Voluntary context switches                      0            0.0          0.0
    parse count (failures)                             7            0.0          0.0
    parse count (hard)                             2,928            0.8          0.0
    parse count (total)                          526,209          145.6          1.1
    parse time cpu                                 2,778            0.8          0.0
    parse time elapsed                             5,048            1.4          0.0
    physical reads                                11,690            3.2          0.0
    physical reads direct                          6,698            1.9          0.0
    physical reads direct (lob)                      102            0.0          0.0
    physical writes                               77,270           21.4          0.2
    physical writes direct                         7,620            2.1          0.0
    physical writes direct (lob)                       0            0.0          0.0
    physical writes non checkpoint                33,360            9.2          0.1
    pinned buffers inspected                           0            0.0          0.0
    prefetched blocks                                799            0.2          0.0
    prefetched blocks aged out before                  0            0.0          0.0
    process last non-idle time                     3,630            1.0          0.0
    recursive calls                            9,053,277        2,505.8         18.5
    recursive cpu usage                          255,973           70.9          0.5
    redo blocks written                        2,572,625          712.1          5.3
    redo buffer allocation retries                    50            0.0          0.0
    redo entries                               3,074,994          851.1          6.3
    redo log space requests                           60            0.0          0.0
    redo log space wait time                         193            0.1          0.0
    redo ordering marks                                0            0.0          0.0
    redo size                              1,016,164,852      281,252.4      2,073.5
    redo synch time                                1,956            0.5          0.0
    redo synch writes                              5,317            1.5          0.0
    redo wastage                             259,689,040       71,876.3        529.9
    redo write time                               37,488           10.4          0.1
    redo writer latching time                        242            0.1          0.0
    redo writes                                  854,744          236.6          1.7
    rollback changes - undo records a              1,098            0.3          0.0
    Instance Activity Stats for DB: DB  Instance: DB  Snaps: 12 -13
    Statistic                                      Total     per Second    per Trans
    rollbacks only - consistent read                 747            0.2          0.0
    rows fetched via callback                117,908,375       32,634.5        240.6
    session connect time                               0            0.0          0.0
    session cursor cache count                        16            0.0          0.0
    session cursor cache hits                    484,372          134.1          1.0
    session logical reads                    264,160,020       73,113.8        539.0
    session pga memory                        16,473,320        4,559.5         33.6
    session pga memory max                    16,914,080        4,681.5         34.5
    session uga memory                    17,216,514,728    4,765,157.7     35,130.3
    session uga memory max                 1,865,036,296      516,201.6      3,805.6
    shared hash latch upgrades - no w         17,251,803        4,774.9         35.2
    shared hash latch upgrades - wait             24,671            6.8          0.1
    sorts (disk)                                      32            0.0          0.0
    sorts (memory)                               499,747          138.3          1.0
    sorts (rows)                               8,626,333        2,387.6         17.6
    SQL*Net roundtrips to/from client             80,069           22.2          0.2
    SQL*Net roundtrips to/from dblink              5,001            1.4          0.0
    summed dirty queue length                          0            0.0          0.0
    switch current to new buffer                       1            0.0          0.0
    table fetch by rowid                     238,882,317       66,117.4        487.4
    table fetch continued row                  4,436,670        1,228.0          9.1
    table scan blocks gotten                   5,066,302        1,402.2         10.3
    table scan rows gotten                   134,679,712       37,276.4        274.8
    table scans (direct read)                          0            0.0          0.0
    table scans (long tables)                        447            0.1          0.0
    table scans (short tables)                   152,382           42.2          0.3
    transaction rollbacks                            530            0.2          0.0
    transaction tables consistent rea                  0            0.0          0.0
    transaction tables consistent rea                  0            0.0          0.0
    user calls                                    94,382           26.1          0.2
    user commits                                 489,423          135.5          1.0
    user rollbacks                                   653            0.2          0.0
    write clones created in backgroun                 11            0.0          0.0
    write clones created in foregroun                878            0.2          0.0
    Tablespace IO Stats for DB: DB  Instance: DB  Snaps: 12 -13
    ->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)
    T1_UNDO
                31       0    0.0     1.0       46,535       13        344    0.4
    T1       
                31       0    0.0     1.0       13,754        4      3,657    0.4
    T2     
             3,308       1    0.8     1.1        2,973        1          0    0.0
    T3       
                31       0    0.0     1.0        5,710        2     16,240    0.4
    T4     
               555       0    4.0     1.0          600        0          0    0.0
    SYSTEM
               429       0    3.9     2.5          280        0         49    0.2
    TEMP
               134       0    0.4    48.1          238        0          0    0.0
    T1_16K          
                31       0    0.0     1.0           31        0          0    0.0
    T2_16K     
                31       0    0.0     1.0           31        0          0    0.0
    Buffer Pool Statistics for DB: DB  Instance: DB  Snaps: 12 -13
    -> Standard block size Pools  D: default,  K: keep,  R: recycle
    -> Default Pools for other block sizes: 2k, 4k, 8k, 16k, 32k
                                                               Free    Write  Buffer
         Number of Cache      Buffer    Physical   Physical  Buffer Complete    Busy
    P      Buffers Hit %        Gets       Reads     Writes   Waits    Waits   Waits
    D       49,625 100.0 263,975,320       4,909     69,666       0        0  20,290
    16k      7,056 100.0          30           0          0       0        0       0
    Instance Recovery Stats for DB: DB  Instance: DB  Snaps: 12 -13
    -> B: Begin snapshot,  E: End snapshot
      Targt Estd                                    Log File   Log Ckpt   Log Ckpt
      MTTR  MTTR   Recovery    Actual     Target      Size     Timeout    Interval
       (s)   (s)   Estd IOs  Redo Blks  Redo Blks  Redo Blks  Redo Blks  Redo Blks
    B     0     0                 10518      10000      73728     186265      10000
    E     0     0                 13189      10000      73728     219498      10000
    Buffer Pool Advisory for DB: DB  Instance: DB  End Snap: 13
    -> Only rows with estimated physical reads >0 are displayed
    -> ordered by Block Size, Buffers For Estimate
            Size for  Size      Buffers for  Est Physical          Estimated
    P   Estimate (M) Factr         Estimate   Read Factor     Physical Reads
    D             32    .1            3,970        205.60      4,726,309,734
    D             64    .2            7,940        111.86      2,571,419,284
    D             96    .2           11,910         59.99      1,379,092,849
    D            128    .3           15,880         32.24        741,224,090
    D            160    .4           19,850         16.05        369,050,333
    D            192    .5           23,820          1.28         29,352,221
    D            224    .6           27,790          1.05         24,077,507
    D            256    .6           31,760          1.03         23,723,389
    D            288    .7           35,730          1.02         23,518,434
    D            320    .8           39,700          1.01         23,328,106
    D            352    .9           43,670          1.01         23,193,257
    D            384   1.0           47,640          1.00         23,064,957
    D            400   1.0           49,625          1.00         22,987,576
    D            416   1.0           51,610          1.00         22,927,325
    D            448   1.1           55,580          0.99         22,824,032
    D            480   1.2           59,550          0.99         22,713,509
    D            512   1.3           63,520          0.99         22,649,147
    D            544   1.4           67,490          0.98         22,605,489
    D            576   1.4           71,460          0.98         22,525,897
    D            608   1.5           75,430          0.97         22,407,418
    D            640   1.6           79,400          0.96         22,022,381
    16k           16    .1            1,008          1.00        139,218,299
    16k           32    .3            2,016          1.00        139,211,699
    16k           48    .4            3,024          1.00        139,207,678
    16k           64    .6            4,032          1.00        139,202,581
    16k           80    .7            5,040          1.00        139,198,339
    16k           96    .9            6,048          1.00        139,193,448
    16k          112   1.0            7,056          1.00        139,188,446
    16k          128   1.1            8,064          1.00        139,183,808
    16k          144   1.3            9,072          1.00        139,179,598
    16k          160   1.4           10,080          1.00        139,175,656
    16k          176   1.6           11,088          1.00        139,170,607
    16k          192   1.7           12,096          1.00        139,166,491
    16k          208   1.9           13,104          1.00        139,162,487
    16k          224   2.0           14,112          1.00        139,158,197
    16k          240   2.1           15,120          1.00        139,153,797
    16k          256   2.3           16,128          1.00        139,149,365
    16k          272   2.4           17,136          1.00        139,144,252
    16k          288   2.6           18,144          1.00        139,140,121
    16k          304   2.7           19,152          1.00        139,135,435
    16k          320   2.9           20,160          1.00        139,130,845
    Buffer wait Statistics for DB: DB  Instance: DB  Snaps: 12 -13
    -> ordered by wait time desc, waits desc
                                     Tot Wait    Avg
    Class                    Waits   Time (s) Time (ms)
    data block              19,912          8         0
    undo header                343          0         0
    segment header              34          0         0
    undo block                   1          0         0
    Enqueue activity for DB: DB  Instance: DB  Snaps: 12 -13
    -> Enqueue stats gathered prior to 9i should not be compared with 9i data
    -> ordered by Wait Time desc, Waits desc
                                                            Avg Wt         Wait
    Eq     Requests    Succ Gets Failed Gets       Waits   Time (ms)     Time (s)
    TM      981,781      981,773           0           7      1,365.43           10
    TX      983,944      983,906           0         412           .59            0
    HW        4,645        4,645           0          32           .09            0
    Rollback Segment Stats for DB: DB  Instance: DB  Snaps: 12 -13
    ->A high value for "Pct Waits" suggests more rollback segments may be required
    ->RBS stats may not be accurate between begin and end snaps when using Auto Undo
      managment, as RBS may be dynamically created and dropped as needed
            Trans Table       Pct   Undo Bytes
    RBS No      Gets        Waits     Written        Wraps  Shrinks  Extends
         0          155.0    0.00               0        0        0        0
         1      202,561.0    0.00      31,178,710       40        2        3
         2      191,044.0    0.00      30,067,156       23        2        6
         3      195,891.0    0.00      30,470,548       39        1        3
         4      203,928.0    0.00      31,822,638       38        2        5
         5      196,386.0    0.00  -4,264,350,168       38        1        3
         6      204,125.0    0.00      32,081,200       24        1        7
         7      192,169.0    0.00      33,732,012       45        3        6
         8      195,819.0    0.00      30,503,550       40        2        2
         9      202,905.0    0.00      31,595,438       40        2        4
        10      195,796.0    0.00      30,566,652       29        4        9
    Rollback Segment Storage for DB: DB  Instance: DB  Snaps: 12 -13
    ->Optimal Size should be larger than Avg Active
    RBS No    Segment Size      Avg Active    Optimal Size    Maximum Size
         0         385,024               0                         385,024
         1      12,705,792         944,176                   2,213,732,352
         2      11,657,216       1,548,937                   2,214,715,392
         3      13,754,368         832,465                     243,392,512
         4      13,754,368         946,902                     235,069,440
         5      12,705,792         964,352                   2,195,374,080
         6      20,045,824       1,232,438                   2,416,041,984
         7      12,705,792         977,490                   3,822,182,400
         8      10,608,640         875,068                     243,392,512
         9      11,657,216         878,119                     243,392,512
        10      18,997,248       1,034,104                   2,281,889,792
    Undo Segment Summary for DB: DB  Instance: DB  Snaps: 12 -13
    -> Undo segment block stats:
    -> uS - unexpired Stolen,   uR - unexpired Released,   uU - unexpired reUsed
    -> eS - expired   Stolen,   eR - expired   Released,   eU - expired   reUsed
    Undo           Undo        Num  Max Qry     Max Tx Snapshot Out of uS/uR/uU/
    TS#         Blocks      Trans  Len (s)   Concurcy  Too Old  Space eS/eR/eU
       1         44,441 ##########       47          2        0      0 0/0/0/0/0/0
    Undo Segment Stats for DB: DB  Instance: DB  Snaps: 12 -13
    -> ordered by Time desc
                         Undo      Num Max Qry   Max Tx  Snap   Out of uS/uR/uU/
    End Time           Blocks    Trans Len (s)    Concy Too Old  Space eS/eR/eU
    28-Jun 11:56        7,111 ########      47        1       0      0 0/0/0/0/0/0
    28-Jun 11:46       10,782 ########      18        2       0      0 0/0/0/0/0/0
    28-Jun 11:36        6,170 ########      42        1       0      0 0/0/0/0/0/0
    28-Jun 11:26        4,966 ########      13        1       0      0 0/0/0/0/0/0
    28-Jun 11:16        6,602 ########      40        1       0      0 0/0/0/0/0/0
    28-Jun 11:06        8,810 ########      10        1       0      0 0/0/0/0/0/0
    Latch Activity for DB: DB  Instance: DB  Snaps: 12 -13
    ->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
      willing-to-wait latch get requests
    ->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
    ->"Pct Misses" for both should be very close to 0.0
                                               Pct    Avg   Wait                 Pct
                                  Get          Get   Slps   Time       NoWait NoWait
    Latch                       Requests      Miss  /Miss    (s)     Requests   Miss
    active checkpoint queue           9,585    0.0    0.0      0            0
    alert log latch                     158    0.0             0            0
    archive control                     220    0.0             0            0
    archive process latch               220    0.5    1.0      0            0
    cache buffer handles            264,718    0.0    0.0      0            0
    cache buffers chains        416,051,175    0.0    0.0      4      401,018    0.0
    cache buffers lru chain       1,285,963    0.0    0.0      0    1,206,550    0.0
    channel handle pool latc          4,927    0.0             0            0
    channel operations paren         10,788    0.0             0            0
    checkpoint queue latch          528,319    0.0    0.0      0       69,506    0.0
    child cursor hash table          35,371    0.0             0            0
    Consistent RBA                  854,833    0.0    0.0      0            0
    dml lock allocation           1,963,007    0.9    0.0      0            0
    dummy allocation                  4,995    0.0             0            0
    enqueue hash chains           4,014,593    0.5    0.0      0            0
    enqueues                         94,666    0.0    0.0      0            0
    event group latch                 2,340    0.0             0            0
    FAL request queue                    72    0.0             0            0
    FIB s.o chain latch                 310    0.0             0            0
    FOB s.o list latch                6,769    0.0             0            0
    global tx hash mapping           10,388    0.0             0            0
    hash table column usage              16    0.0             0          479    0.0
    job workq parent latch                0                    0          316    0.0
    job_queue_processes para            116    0.0             0            0
    ktm global data                     200    0.0             0            0
    lgwr LWN SCN                    855,008    0.0    0.0      0            0
    library cache                 5,836,900    0.4    0.0      0        8,926    0.6
    library cache load lock             468    0.0             0            0
    library cache pin             3,510,695    0.0    0.0      0            0
    library cache pin alloca      1,402,523    0.0    0.0      0            0
    list of block allocation          6,115    0.0             0            0
    loader state object free            620    0.0             0            0
    message pool operations             262    0.0             0            0
    messages                      2,664,950    0.4    0.0      0            0
    mostly latch-free SCN           856,000    0.1    0.0      0            0
    multiblock read objects           3,184    0.0             0            0
    ncodef allocation latch              57    0.0             0            0
    object stats modificatio              8    0.0             0            0
    post/wait queue                   6,183    0.0             0        3,082    0.0
    process allocation                4,677    0.0             0        2,340    0.0
    process group creation            4,677    0.0             0            0
    redo allocation               4,784,936    0.5    0.0      0            0
    redo copy                             0                    0    3,081,261    0.3
    redo writing                  2,576,299    0.0    0.2      0            0
    row cache enqueue latch       3,017,144    0.0    0.0      0            0
    row cache objects             5,049,552    0.8    0.0      0           92    0.0
    sequence cache                  984,824    0.0    0.1      0            0
    session allocation              110,417    0.0    0.0      0            0
    session idle bit                205,319    0.0             0            0
    session switching                    57    0.0             0            0
    Latch Activity for DB: DB  Instance: DB  Snaps: 12 -13
    ->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
      willing-to-wait latch get requests
    ->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
    ->"Pct Misses" for both should be very close to 0.0
                                               Pct    Avg   Wait                 Pct
                                  Get          Get   Slps   Time       NoWait NoWait
    Latch                       Requests      Miss  /Miss    (s)     Requests   Miss
    session timer                     1,204    0.0             0            0
    shared pool                   2,409,725    0.1    0.1      0            0
    simulator hash latch          7,439,429    0.0    0.0      0            0
    simulator lru latch                 202    0.0             0      128,961    0.2
    sort extent pool                  1,053    0.0             0            0
    SQL memory manager worka             67    0.0             0            0
    temp lob duration state             187    0.0             0            0
    transaction allocation            7,290    0.0             0            0
    transaction branch alloc          5,668    0.0             0            0
    undo global data              3,002,808    0.4    0.0      0            0
    user lock                         8,642    0.0             0            0
    Latch Sleep breakdown for DB: DB  Instance: DB  Snaps: 12 -13
    -> ordered by misses desc
                                          Get                            Spin &
    Latch Name                       Requests      Misses      Sleeps Sleeps 1->4
    cache buffers chains          416,051,175     197,296         750 196776/298/2
                                                                      15/7/0
    row cache objects               5,049,552      42,368          38 42330/38/0/0
                                                                      /0
    redo allocation                 4,784,936      24,766          77 24697/61/8/0
                                                                      /0
    library cache                   5,836,900      23,477         276 23207/264/6/
                                                                      0/0
    enqueue hash chains             4,014,593      21,061          26 21035/26/0/0
                                                                      /0
    dml lock allocation             1,963,007      17,887          16 17872/14/1/0
                                                                      /0
    undo global data                3,002,808      12,350           8 12342/8/0/0/
                                                                      0
    messages                        2,664,950      10,131           5 10126/5/0/0/
                                                                      0
    shared pool                     2,409,725       1,362         189 1175/185/2/0
                                                                      /0
    row cache enqueue latch         3,017,144         470           7 463/7/0/0/0
    mostly latch-free SCN             856,000         434           1 433/1/0/0/0
    library cache pin               3,510,695         345           4 341/4/0/0/0
    sequence cache                    984,824          53           4 49/4/0/0/0
    library cache pin allocati      1,402,523          35           1 34/1/0/0/0
    redo writing                    2,576,299           5           1 4/1/0/0/0
    archive process latch                 220           1           1 0/1/0/0/0
    Latch Miss Sources for DB: DB  Instance: DB  Snaps: 12 -13
    -> only latches with sleeps are shown
    -> ordered by name, sleeps desc
                                                         NoWait              Waiter
    Latch Name               Where                       Misses     Sleeps   Sleeps
    archive process latch    kcrrpa                           0          1        0
    cache buffers chains     kcbgtcr: fast path               0        346      188
    cache buffers chains     kcbgtcr: kslbegin excl           0        163      239
    cache buffers chains     kcbrls: kslbegin                 0         86      170
    cache buffers chains     kcbget: pin buffer               0         53       49
    cache buffers chains     kcbgcur: kslbegin                0         44       20
    cache buffers chains     kcbnlc                           0         38       22
    cache buffers chains     kcbget: exchange                 0          8       16
    cache buffers chains     kcbchg: kslbegin: call CR        0          3       21
    cache buffers chains     kcbget: exchange rls             0          3        2
    cache buffers chains     kcbnew                           0          3        0
    cache buffers chains     kcbbxsv                          0          2        0
    cache buffers chains     kcbchg: kslbegin: bufs not       0          1       23
    dml lock allocation      ktaiam                           0         13        1
    dml lock allocation      ktaidm                           0          3       15
    enqueue hash chains      ksqgtl3                          0         22        2
    enqueue hash chains      ksqrcl                           0          4       24
    library cache            kglic                            0         55        4
    library cache            kglhdgn: child:                  0         42       86
    library cache            kglobpn: child:                  0         26       32
    library cache            kglpndl: child: after proc       0         14        0
    library cache            kglpndl: child: before pro       0         13       73
    library cache            kglpin: child: heap proces       0         12       29
    library cache            kgllkdl: child: cleanup          0         11        4
    library cache            kglupc: child                    0          4        7
    library cache            kgldti: 2child                   0          2        4
    library cache            kglpnp: child                    0          1        4
    library cache pin        kglpnal: child: alloc spac       0          3        3
    library cache pin        kglpndl                          0          1        1
    library cache pin alloca kglpnal                          0          1        0
    messages                 ksaamb: after wakeup             0          3        2
    messages                 ksarcv                           0          2        2
    mostly latch-free SCN    kcslcu3                          0          1        1
    redo allocation          kcrfwr                           0         74        8
    redo allocation          kcrfwi: more space               0    

  • How much memory are actually being used? db_32k_cache_size

    Hi everyone,
    Using Oracle 10g on RHEL 5.3.
    I've been asked to check how much memory are actually being used by our db cache's. Currently we are using the parameters db_32k_cache_size (user-defined) and db_8k_cache_size (default) both allocated with 12gb. Now I want to know if there is any way to find out how much of the 12gb are actually being used by the cache.
    Is this possible?
    Thanks

    Thanks Guys,
    Okay, so it is using the whole 12gb. I guess the next question would be, is 12gb really needed? You see, we are trying to increase memory where possible as this database has performance issues. Now we are thinking of taking some of the 12gb that is allocated to the 32k cache and assign it to the sga for instance.
    Does this make any sense?
    Regards

  • How long redo logs keep the transactions?

    I learn Oracle and decide to do an experiment. There was a table in the test database. I deleted the file that contained this table via OS. And then I added transactions to this table.
    I did 'insert' several times, then 'commit', then 'alter system switch logfile' several times, 'alter system flush buffer_cache', 'alter system flush shared_pool' and nothing happened. I could add and take data from this table successfully. Alert log showed the error only when I shutdown the database.
    SQL> shutdown immediate
    ORA-01116: error in opening database file 13
    ORA-01110: data file 13: '/oracle/oradata/test5/POSTEMPTEST2.dbf'
    ORA-27041: unable to open file
    Linux Error: 2: No such file or directory
    Additional information: 3
    I understand that transactions are put in the redo logs at first, and then are transferred to the datafile on disk. I thought that command 'ALTER SYSTEM CHECKPOINT' writes transactions from redo logs to datafile on disk, but I was wrong. How long redo logs keep transactions? Is there the way to push data from redo logs to datafile?
    I use Oracle 10.2.0.1.0.

    i believe this time you will see the error message during your SQLsWRONG!probably you did not read the complete post of mine before saying WRONG. You tell me, if data file containing a table is deleted at OS level (in *nix), and then you try to insert data in this table and want to retrieve the data from the table (If data is not in db cache or cache has been flushed), from where data will come? Or if you want to insert some data into this table for which new extent are required to be allocated, where it will be allocated? Will your SQLs succeed or will return some error? Either SQL should return you data (which is not possible as data file is no there to fetch the data), or SQL should fail with some error message.
    I mimicked the situation on IBM AIX, following is the outcome.
    Enter user-name: system/salman
    Connected to:
    Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
    SQL> create table test as select * from dba_tables;
    Table created.
    SQL> alter table test move tablespace users;
    Table altered.
    SQL> insert into test select * from dba_tables;
    2500 rows created.
    SQL> /
    2500 rows created.
    SQL> /
    2500 rows created.
    SQL> commit;
    Commit complete.Now i deleted the users01.dbf file at OS level and then execute following INSERT
    SQL> insert into test select * from test;
    insert into test select * from test
    ERROR at line 1:
    ORA-01565: error in identifying file '/oracle/oradata/test/users01.dbf'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3Salman

  • How much of logging is too much of logging?

    Hi All,
    OK, that was my question, how much of logging is too much of logging?
    Recently one of my co-worker (not me, not me at all) had written about 100 classes and after getting the framework right, he has now been asked to log all those bunch of classes and methods.
    He is damn bored and fed up with logging and he needs to log it in a ratio of 1 line of logging per 10 lines of code (approximately). And he also must log "ENTERING", "EXITING" in each method whenever he enters and exits a method.
    I personally like to log as little as possible, although we don't log everything in INFO and we do log a lot of things in DEBUG logging level, logging every method doesn't feel correct to me.
    And I hate too much of logging because to me it makes the code unreadable. Many of you will disagree this point, but I feel the important log statements often get messed up with those "ENTERING" and "EXITING" kind of log statements.
    And another question, when is the right time to log? Logging as and when we are writing the code or logging it after everything is done (like how the pure dude is doing now). The former seems to be the better.
    Your thoughts??
    Thank you

    Hi All,
    OK, that was my question, how much of logging is too
    much of logging?Too general for a one size fits all answer.
    And he also must log
    "ENTERING", "EXITING" in each method whenever he
    enters and exits a method.Sounds fine, especially if it logs the parameters passed to the method, as well as what it returned (if not void) or if it returned via exception.
    >
    I personally like to log as little as possible,
    although we don't log everything in INFO and we do
    log a lot of things in DEBUG logging level, logging
    every method doesn't feel correct to me.It's reasonable. During development, logging may be very verbose, but it can be useful. During production, you can configure the logging to not log at the DEBUG level, so you wouldn't see these log messages anyway and it shouldn't impact performance enough to be a concern.
    And I hate too much of logging because to me it makes
    the code unreadable. Many of you will disagree this
    point, but I feel the important log statements often
    get messed up with those "ENTERING" and "EXITING"
    kind of log statements.This is a perfect fit for AOP (Aspect Oriented Programming). Rather than clutter the code with these log messages, these can be "woven" into the bytecode at compile-time or run-time.
    Aspect-J is one popular AOP framework.
    http://www.eclipse.org/aspectj/

  • How much Redo

    Hii
    How can I which session or sql created most redo in past ?
    I could not find any awr table that releated about v$sesstat or is there any v$ view That I calculate redo size of sql that has point to past
    Best Regards

    Hi,
    have a look there
    http://www.adp-gmbh.ch/ora/concepts/redo_log.html
    or there
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96521/onlineredo.htm
    or on forum
    http://forums.oracle.com/forums/search.jspa?objID=f61&q=how+much+redo
    regards,
    Tom

  • Finding which table generated how much redo

    I'm wondering if we can find from any view that during this period a particular table generated how much amount of redo log , other than logminer ?
    We have a particular application and want to know which tables are generating most of the redo.

    from asktom
    see
    http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:477221446020
    and
    http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:366018048216
    Nologging only affects very very specific operations. For exmaple, from the
    alter index syntax statement in the SQL reference:
    LOGGING|NOLOGGING
    LOGGING|NOLOGGING specifies that subsequent Direct Loader (SQL*Loader) and
    direct-load INSERT operations against a nonpartitioned index, a range or hash
    index partition, or all partitions or subpartitions of a composite-partitioned
    index will be logged (LOGGING) or not logged (NOLOGGING) in the redo log file.
    In NOLOGGING mode, data is modified with minimal logging (to mark new extents
    invalid and to record dictionary changes). When applied during media recovery,
    the extent invalidation records mark a range of blocks as logically corrupt,
    because the redo data is not logged. Therefore, if you cannot afford to lose
    this index, you must take a backup after the operation in NOLOGGING mode.
    If the database is run in ARCHIVELOG mode, media recovery from a backup taken
    before an operation in LOGGING mode will re-create the index. However, media
    recovery from a backup taken before an operation in NOLOGGING mode will not
    re-create the index.
    An index segment can have logging attributes different from those of the base
    table and different from those of other index segments for the same base table.
    That also explains why the truncate above generated redo -- The statement
    "minimal logging (to mark new extents invalid and to record dictionary
    changes)." explains where that redo comes from. The blocks that were truncated
    were not logged HOWEVER the changes to the data dictionary itself were.
    .

  • When & how much redo record will be produced?

    oracle tech is so hard to study !!! uh uh uh!!
    to be first , i knowe DML operations will cause to redo action. to this ,except for dml ,and when , can cause to redo ??
    online redo log file is stored redo records , then how to store it ? can i put my sight into the log file to learn how do redo file organise and manage so much redo records .
    secondly , it is right that insert operate (noindex) bring 1 redo record ,
    and update will bring 2 redo record ?
    thanks a lot

    secondly , it is right that insert operate (noindex) bring 1 redo record ,and update will bring 2 redo record ?
    Your question confuses. However, when you update value and the columns has the index, its 2 transactions for index, update in index = delete+insert.
    to be first , i knowe DML operations will cause to redo action. to this ,except for dml ,and when , can cause to redo ??Oracle recursive sqls + sometime due to block cleaouts, a select statement also generates redo.
    Jaffar

  • Logs not being generated

    I have two wfe servers, in one server the logs file are being generated but another server no log files only usage files
    what could be the reason. Under central admin monitoring uls logs have been already enabled.

    Hi Rizzk,
    Have you solved this issue?
    Have you checked and added the service account for SharePoint Services Tracing in local group Performance Log Users or Administrators on SharePoint server, then restart this service?
    http://www.justinkobel.com/post/2013/06/07/Solving-ULS-Log-Files-Being-Created-But-Empty-(0-Kb).aspx
    http://sharepointinsight.wordpress.com/2010/04/05/solution-for-zero-byte-sharepoint-2010-log-files/
    Thanks
    Daniel Yang
    TechNet Community Support

  • How to modify the SQL being generated from BC, to fix the issue

    Hi,
    We have seen a strange issue in our implementation.The issue is also reproducible in Vanilla environment.
    In Contact List Applet, if we Query in First Name or Last Name fields in UI, the Query being generated is,showing that, Siebel is Querying for first name in S_POSTN_CON.CON_FST_NAME. This is a normalized column for S_CONTACT.FST_NAME.
    This is causing the performance issue.
    When I check the configuration in Tools for Contact BC's First Name field, it is configured as follows.
    Join = S_CONTACT
    Column = FST_NAME.
    I do not understand, Why it is still querying in S_POSTN_CON.
    Any suggestions on how to fix this issue to make the Query to be performed on S_CONTACT.FST_NAME?
    Regards
    Vamshi

    Hi Vamshi,
    As Robert mentioned, there just happens to be a number of things that need to be analyzed prior to changing the shape of the buscomp that triggers that sql.
    If this siebel performance issue occurs on a production environment, you should certainly look at the performance trend/characteristics of that sql over time and assess its the impact on your business community (...), then carefully identify its -true- root-cause, implement a fix and validate it against a production-like environment in order to verify there is no regression associated with it; once the fix is deployed on your production system, you want to monitor its benefit overtime and on a 24x7 basis…all this may sound very generic yet good practices.
    If you are looking at -effectively- solving this siebel peformance issue (and others...) in a timely manner, best is to have your Siebel Teams 1)use a Siebel-specific performance monitoring software technology built by Siebel Architects (like GMT v1.8.5, more info @ www.germainsoftware.com) that is able to collect 24x7 all the data needed for root-cause analysis(and more..), and 2)have senior siebel architects (like Robert's team) that have successfully solved tones and severe performance and scalability issues for many years, provide technical guidance to your team throughout the resolution process.
    Siebel CRM is a great CRM software solution that is very complex. Every "switch you turn on/off", every customization you built into it may generate performance issues if it is not carefully implemented, optimized, tested...and monitored 24x7 once it is deployed onto your production system.
    Good luck w/ this..
    Regards,
    Yannick Germain
    CEO & Founder
    GERMAIN SOFTWARE llc
    Complete Siebel Performance Monitoring Tool
    21 Columbus Avenue, Suite 221
    San Francisco, CA 94111, USA
    Cell: +1-415-606-3420
    Fax: +1-415-651-9683
    [email protected]
    http://www.germainsoftware.com

  • Online redo log files being removed physically

    Grid Infra version: 11.2.0.4
    RDBMS Version: 11.2.0.4
    Although this is a RAC DB, this is not a RAC-specific question. Hence posting it here.
    Few months back, I remember issuing a command similair to below (DROP LOGFILE GROUP ...) and the redo log files were still physically present in the diskgroup.
    If I remember correctly, the file is not deleted physical so that we can use the REUSE functionality (ALTER DATABASE ADD LOGFILE MEMBER '+REDO/orcl/onlinelog/redo1b.log' reuse to group 11; ) ie. you can use the REUSE command to add the logfile of the same name which is physically present in OS Filesystem/Diksgroup to redo log group.
    But today, after I issued the below command, I checked the diskgroup location from ASMCMD
    SQL> alter database drop logfile group 31;
    Database altered.
    From ASMCMD, I can that the file has disappeared physically. Is this a new feature with 11.2.0.4 or am I missing something here ?
    ASMCMD> ls +DATA/msblprd/onlinelog/group_31.548.833154995
    ASMCMD-8002: entry 'group_31.548.833154995' does not exist in directory '+DATA/msblprd/onlinelog/'

    Just to add to what Aman has said.
    It is a bad practice not to let OMF decide the placement of Online redo logs because of this issue especially when you use ASM.
    Executing rm command in Linux/Unix is easy but Dropping ASM aliases in the disk group can be a hassle.
    This is documented.
    "When a redo log member is dropped from the database, the operating system file is not deleted from disk. Rather, the control files of the associated database are updated to drop the member from the database structure. After dropping a redo log file, ensure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped redo log file."
    http://docs.oracle.com/cd/E11882_01/server.112/e25494/onlineredo.htm#ADMIN11324
    BTW . You don't even need to set  db_create_online_log_dest_n to enable OMF for ORLs.
    SQL> show parameter log_dest
    NAME                                 TYPE        VALUE
    db_create_online_log_dest_1          string
    db_create_online_log_dest_2          string
    db_create_online_log_dest_3          string
    db_create_online_log_dest_4          string
    db_create_online_log_dest_5          string
    SQL> show parameter db_create_file_dest
    NAME                                 TYPE        VALUE
    db_create_file_dest                  string      +MBL_DATA
    alter database add logfile thread 4
    group 31 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 32 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 33 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 34 ('+MBL_DATA','+MBL_FRA') size 4096M ;
    Database altered.
    And redo logs will be neatly placed as shown below
       INST     GROUP# MEMBER                                             STATUS           ARC
             4         31 +MBL_DATA/bsblprd/onlinelog/group_31.276.832605441 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_31.297.832605445  UNUSED           YES
                       32 +MBL_DATA/bsblprd/onlinelog/group_32.547.832605451 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_32.372.832605457  UNUSED           YES
                       33 +MBL_DATA/bsblprd/onlinelog/group_33.548.832605463 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_33.284.832605469  UNUSED           YES
                       34 +MBL_DATA/bsblprd/onlinelog/group_34.549.832605475 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_34.359.832605481  UNUSED           YES

  • PROBLEMS WITH HOW MUCH SPACE IS ACTUALLY BEING USED

    Hello,
    I've just recently purchased a Toshiba Dual Core laptop (225 gigs + 3 gig memory.) It works pretty well, but I've had to reload the windows and programs again. The reason is that after reloading I have about 203 gigs of space, but then I install flash CS3 (550 mgs and photoshop 200+) After I've installed all the doc files and everything I end up with about 200 gigs of space which is great. However, I've unistalled norton and installed AVG Professional. My space amount has gone down from 200 to about 193 gigs. I don't get it; it doesn't make sense because this is isn't how much space I've actually used. I've deleted temp files and all the install files of these other programs and what's even more crazy is that when I go ahead and run scan disk to deleted unecessary files, my space goes down in size and it shows that I have even less space! Has anyone else run into this problem? Let me know, perhaps there's a solution. 
    Thanks,
    Tseyigai

                                              PSLE8U02PO1
    Maybe that part number is PSLE8U-02P01D?  If so, you have this model:  Satellite L355D-S7901
    How much space would be reasonable for me to cut back on?
    I've set the shadow storage on the computers around here to 10 GB. Suit yourself.
    You can save quite a bit of hard drive space by turning hibernation off. Check the size of that file. It's c:\hiberfil.sys.
    And look through the stuff Disk Cleanup cites for more savings.
    But if you really can't get along without more space, you should add external drives or upgrade this one.
    -Jerry

  • How to copy Log text (with Date, Time stamp ) User IDfrom BP to Transaction

    Hi Experts,
                     Can someone guide us how  to copy Log text (with Date ,Time & User ID) fron Business partner  (Prospect) to transactions by text detrmination procedure.
    Regards,
    Basavaraj Patil

    save text
    Fill out following parameters of SAVE_TEXT function module:
    HEADER
    TDOBJECT C 10 BUT000
    TDNAME C 70 10 digit BP number
    TDID C 4 Z001
    TDSPRAS C 1 Language
    INSERT = ’X’
    LINES
    TDFORMAT TDLINE
    |
    |testtttttttttttttttttttttttt( Your text)
    I would suggest you to use some other BAPI that would attach your text to BP than SAVE_TEXT.
    If you still wanted to use SAVE_TEXT then first make sure how the TDNAME is generated. It depends on the text determination procedure. For examples, it can be guid of BP, GUID followed by date or time or else the BP number itself.
    Just go to BP transaction, double click on the text pad, it will open you the SAP Script editor. Click on menu GOTO and select Header which will give you info about your TDID, TDOBJECT, TDNAME....
    Hope this helps.

  • How much does it cost to get an additional user on my CC account?

    I work in a design studio, I have a yearly account & would like to license Adobe CC to another user, how much would this cost? And which plan should I select?

    If you are not under any promotional offer price purchase, then it is 49.99$ per seat per month for an year of contract for Team CC.
    Cloud technology | Adobe Creative Cloud for small & medium business
    If you have Individual Cc then you can not add seat, it can be activated twice with the same ID.
    Regards
    Rajshree

Maybe you are looking for

  • Cannot create 'download' page for inline PDF viewing with IE

    Description of Problem: Typically, when you want to transfer a file to the client via code (cuz the file is in a db, for example), you create a page that will change the response headers and then spit out the file for them to download. This works, ho

  • Graphic card/display driver on X100e is inadequate for Dell U2311 1900 x 1080 monitor

    I have an x100e laptop that I bought in late 2010 that came with ATI Radeon HD 3200 Graphics. It is able to support ThinkPad display 1366 x 768. I just hooked it up to a Dell U2311 23" monitor - which offers a 1920 x 1080. I looking to get this level

  • Skip unwanted segment - but required?

    Hi, if I dont want an Idoc segment to be created in my mapping, that is required (1..9999), what should I do?

  • HT2638 iPhoto crashes

    After trying pretty much all of the above and thinking my problem was solve, iPhoto (8.1.2) still crashes whist trying to rebuild the "miniature-cache". It's quite a large library – is there a maximum size? (It is ca 117 GB) Any more / different appr

  • DV9930us Hlep

    Hi,  I have an HP Pavilion DV9930us that failed and I could use some direction.   The machine flashed a blue screen and said I had a hardware malfunction then fade to black.  The machine glows grey and appears ot have intelegence but that is it.   I