Will Analyze create too many redo logs ??

DB : 10gR2
Hello Folks,
Is analyze process creates too many redo log files ?? Is their any other valid option other than no log ?

I guess that's also going to create too many log switches as it's part of DDLHUH?
REDO log switches result from DML.
If you are obsessed with LOG switches, then you need to use LOGMINER to observe the the relative per centage of changed data is from DBMS_STATS
when compared to normal DML activity.
I seriously doubt that DBMS_STATS has any significant impact to redo log switches.

Similar Messages

  • Too many Archive Log

    Hi,
    I have a problem on a production server: our support partner told me that we are creating too many Archive Log files. They are not sure at all of what is happening.
    Please, do you know if there is any System View which we could obtain more information about Archive Logs usage?
    Thanks in advance.
    Best Regards,
    Joan Padilla

    Hi Joan,
    The sensible number of archive logs is determined by your backup and recovery strategy. You can delete them, once you have back-upped the database and the archivelogs. Further info in the Backup and Recovery Concepts manual.
    You can find information on them in v$archived_log.
    If you decide to delete them without having read the aforementioned manual, I will pray for you you don't suffer a hard disk crash.
    You may want to review the relationship with your support partner too.
    Their advice is not exactly professional.
    Sybrand Bakker
    Senior Oracle DBA

  • Create procedure is generating too many archive logs

    Hi
    The following procedure was run on one of our databases and it hung since there were too many archive logs being generated.
    What would be the answer? The db must remain in archivelog mode.
    I understand the nologging concept, but as I know this applies to creating tables, views, indexes and tablespaces. This script is creating procedure.
    CREATE OR REPLACE PROCEDURE APPS.Dfc_Payroll_Dw_Prc(Errbuf OUT VARCHAR2, Retcode OUT NUMBER
    ,P_GRE NUMBER
    ,P_SDATE VARCHAR2
    ,P_EDATE VARCHAR2
    ,P_ssn VARCHAR2
    ) IS
    CURSOR MainCsr IS
    SELECT DISTINCT
    PPF.NATIONAL_IDENTIFIER SSN
    ,ppf.full_name FULL_NAME
    ,ppa.effective_date Pay_date
    ,ppa.DATE_EARNED period_end
    ,pet.ELEMENT_NAME
    ,SUM(TO_NUMBER(prv.result_value)) VALOR
    ,PET.ELEMENT_INFORMATION_CATEGORY
    ,PET.CLASSIFICATION_ID
    ,PET.ELEMENT_INFORMATION1
    ,pet.ELEMENT_TYPE_ID
    ,paa.tax_unit_id
    ,PAf.ASSIGNMENT_ID ASSG_ID
    ,paf.ORGANIZATION_ID
    FROM
    pay_element_classifications pec
    , pay_element_types_f pet
    , pay_input_values_f piv
    , pay_run_result_values prv
    , pay_run_results prr
    , pay_assignment_actions paa
    , pay_payroll_actions ppa
    , APPS.pay_all_payrolls_f pap
    ,Per_Assignments_f paf
    ,per_people_f ppf
    WHERE
    ppa.effective_date BETWEEN TO_DATE(p_sdate) AND TO_DATE(p_edate)
    AND ppa.payroll_id = pap.payroll_id
    AND paa.tax_unit_id = NVL(p_GRE, paa.tax_unit_id)
    AND ppa.payroll_action_id = paa.payroll_action_id
    AND paa.action_status = 'C'
    AND ppa.action_type IN ('Q', 'R', 'V', 'B', 'I')
    AND ppa.action_status = 'C'
    --AND PEC.CLASSIFICATION_NAME IN ('Earnings','Alien/Expat Earnings','Supplemental Earnings','Imputed Earnings','Non-payroll Payments')
    AND paa.assignment_action_id = prr.assignment_action_id
    AND prr.run_result_id = prv.run_result_id
    AND prv.input_value_id = piv.input_value_id
    AND piv.name = 'Pay Value'
    AND piv.element_type_id = pet.element_type_id
    AND pet.element_type_id = prr.element_type_id
    AND pet.classification_id = pec.classification_id
    AND pec.non_payments_flag = 'N'
    AND prv.result_value <> '0'
    --AND( PET.ELEMENT_INFORMATION_CATEGORY LIKE '%EARNINGS'
    -- OR PET.element_type_id IN (1425, 1428, 1438, 1441, 1444, 1443) )
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN PET.EFFECTIVE_START_DATE AND PET.EFFECTIVE_END_DATE
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN PIV.EFFECTIVE_START_DATE AND PIV.EFFECTIVE_END_DATE --dcc
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN Pap.EFFECTIVE_START_DATE AND Pap.EFFECTIVE_END_DATE --dcc
    AND paf.ASSIGNMENT_ID = paa.ASSIGNMENT_ID
    AND ppf.NATIONAL_IDENTIFIER = NVL(p_ssn, ppf.NATIONAL_IDENTIFIER)
    ------------------------------------------------------------------TO get emp.
    AND ppf.person_id = paf.person_id
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN ppf.EFFECTIVE_START_DATE AND ppf.EFFECTIVE_END_DATE
    ------------------------------------------------------------------TO get emp. ASSIGNMENT
    --AND paf.assignment_status_type_id NOT IN (7,3)
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN paf.effective_start_date AND paf.effective_end_date
    GROUP BY PPF.NATIONAL_IDENTIFIER
    ,ppf.full_name
    ,ppa.effective_date
    ,ppa.DATE_EARNED
    ,pet.ELEMENT_NAME
    ,PET.ELEMENT_INFORMATION_CATEGORY
    ,PET.CLASSIFICATION_ID
    ,PET.ELEMENT_INFORMATION1
    ,pet.ELEMENT_TYPE_ID
    ,paa.tax_unit_id
    ,PAF.ASSIGNMENT_ID
    ,paf.ORGANIZATION_ID
    BEGIN
    DELETE cust.DFC_PAYROLL_DW
    WHERE PAY_DATE BETWEEN TO_DATE(p_sdate) AND TO_DATE(p_edate)
    AND tax_unit_id = NVL(p_GRE, tax_unit_id)
    AND ssn = NVL(p_ssn, ssn)
    COMMIT;
    FOR V_REC IN MainCsr LOOP
    INSERT INTO cust.DFC_PAYROLL_DW(SSN, FULL_NAME, PAY_DATE, PERIOD_END, ELEMENT_NAME, ELEMENT_INFORMATION_CATEGORY, CLASSIFICATION_ID, ELEMENT_INFORMATION1, VALOR, TAX_UNIT_ID, ASSG_ID,ELEMENT_TYPE_ID,ORGANIZATION_ID)
    VALUES(V_REC.SSN,V_REC.FULL_NAME,v_rec.PAY_DATE,V_REC.PERIOD_END,V_REC.ELEMENT_NAME,V_REC.ELEMENT_INFORMATION_CATEGORY, V_REC.CLASSIFICATION_ID, V_REC.ELEMENT_INFORMATION1, V_REC.VALOR,V_REC.TAX_UNIT_ID,V_REC.ASSG_ID, v_rec.ELEMENT_TYPE_ID, v_rec.ORGANIZATION_ID);
    COMMIT;
    END LOOP;
    END ;
    So, how could I assist our developer with this, so that she can run it again without it generating a ton of logs ? ?
    Thanks
    Oracle 9.2.0.5
    AIX 5.2

    The amount of redo generated is a direct function of how much data is changing. If you insert 'x' number of rows, you are going to generate 'y' mbytes of redo. If your procedure is destined to insert 1000 rows, then it is destined to create a certain amount of redo. Period.
    I would question the <i>performance</i> of the procedure shown ... using a cursor loop with a commit after every row is going to be a slug on performance but that doesn't change the fact 'x' inserts will always generate 'y' redo.

  • System I/O and Too Many Archive Logs

    Hi all,
    This is frustrating me. Our production database began to produce too many archived redo logs instantly --again. This happened before; two months ago our database was producing too many archive logs; just then we began get async i/o errors, we consulted a DBA and he restarted the database server telling us that it was caused by the system(???).
    But after this restart the amount of archive logs decreased drastically. I was deleting the logs by hand(350 gb DB 300 gb arch area) and after this the archive logs never exceeded 10% of the 300gb archive area. Right now the logs are increasing 1%(3 GB) per 7-8 mins which is too many.
    I checked from Enterprise Manager, System I/O graph is continous and the details show processes like ARC0, ARC1, LGWR(log file sequential read, db file parallel write are the most active ones) . Also Phsycal Reads are very inconsistent and can exceed 30000 KB at times. Undo tablespace is full nearly all of the time causing ORA-01555.
    The above symptoms have all began today. The database is closed at 3:00 am to take offline backup and opened at 6:00 am everyday.
    Nothing has changed on the database(9.2.0.8), applications(11.5.10.2) or OS(AIX 5.3).
    What is the reason of this most senseless behaviour? Please help me.
    Thanks in advance.
    Regards.
    Burak

    Selam Burak,
    High number of archive logs are being created because you may have massive redo creation on your database. Do you have an application that updates, deletes or inserts into any kind of table?
    What is written in the alert.log file?
    Do you have the undo tablespace with the guarentee retention option btw?
    Have you ever checked the log file switch sequency map?
    Please use below SQL to detirme the switch frequency;
    SELECT * FROM (
    SELECT * FROM (
    SELECT   TO_CHAR(FIRST_TIME, 'DD/MM') AS "DAY"
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '00', 1, 0)), '999') "00:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '01', 1, 0)), '999') "01:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '02', 1, 0)), '999') "02:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '03', 1, 0)), '999') "03:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '04', 1, 0)), '999') "04:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '05', 1, 0)), '999') "05:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '06', 1, 0)), '999') "06:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '07', 1, 0)), '999') "07:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '08', 1, 0)), '999') "08:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '09', 1, 0)), '999') "09:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '10', 1, 0)), '999') "10:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '11', 1, 0)), '999') "11:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '12', 1, 0)), '999') "12:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '13', 1, 0)), '999') "13:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '14', 1, 0)), '999') "14:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '15', 1, 0)), '999') "15:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '16', 1, 0)), '999') "16:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '17', 1, 0)), '999') "17:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '18', 1, 0)), '999') "18:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '19', 1, 0)), '999') "19:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '20', 1, 0)), '999') "20:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '21', 1, 0)), '999') "21:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '22', 1, 0)), '999') "22:00"+
    +, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '23', 1, 0)), '999') "23:00"+
    FROM V$LOG_HISTORY
    WHERE extract(year FROM FIRST_TIME) = extract(year FROM sysdate)
    GROUP BY TO_CHAR(FIRST_TIME, 'DD/MM')
    +) ORDER BY TO_DATE(extract(year FROM sysdate) || DAY, 'YYYY DD/MM') DESC+
    +) WHERE ROWNUM < 8+
    Ogan

  • Portal creates too many database sessions. fix doesn't work!!

    Oracle Database 9i, Application Server 9iAS,
    Operating System SUSE Linux 7.2
    CPU - Athlon 1400
    Ram - 1GB
    There is a modification for the http server that aims to eliminate a problem on unix that causes the database to create too many sessions. The script can be found at
    http://portalstudio.oracle.com/servlet/page?_pageid=1787&_dad=ops&_schema=OPSTUDIO
    However the script fails to work. The http server is on port 80 with the redirect on port 7778. However going to http://myhost/pls/ results in a server error - connection refused. Is it possible that there may be an error in the script.
    Thanks in anticipation

    ok so my sound is ok now I can check that off of the list... I just looked around and found some external USB speakers that work just right. My built in computer speakers are just not the best quality.
    As for the microphone, I still haven't been able to find out what is causing it to not work. I notice that it isn't actually broken since if I make a really loud noise right next to the input it will register a little but only a little bit.
    $ arecord -L
    null
    Discard all samples (playback) or generate zero samples (capture)
    pulse
    PulseAudio Sound Server
    default
    Default ALSA Output (currently PulseAudio Sound Server)
    sysdefault:CARD=Intel
    HDA Intel, ALC269 Analog
    Default Audio Device
    front:CARD=Intel,DEV=0
    HDA Intel, ALC269 Analog
    Front speakers
    surround40:CARD=Intel,DEV=0
    HDA Intel, ALC269 Analog
    4.0 Surround output to Front and Rear speakers
    surround41:CARD=Intel,DEV=0
    HDA Intel, ALC269 Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
    surround50:CARD=Intel,DEV=0
    HDA Intel, ALC269 Analog
    5.0 Surround output to Front, Center and Rear speakers
    surround51:CARD=Intel,DEV=0
    HDA Intel, ALC269 Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
    surround71:CARD=Intel,DEV=0
    HDA Intel, ALC269 Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
    $
    here is some additional information about my sound. Also, when I open alsamixer, I find that when I go to "select sound card"(F6) I see default and HDA Intel. If the default is pulseaudio, then is it possible that pulseaudio is causing the problem?

  • 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    

  • Problem in creating database -Missing Redo log file

    I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
    My alert log file is
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:27 2013
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:38 2013
    Setting recovery target incarnation to 2
    Wed Nov 06 10:07:38 2013
    Assigning activation ID 1876274518 (0x6fd5ad56)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
    Successful open of redo thread 1
    Wed Nov 06 10:07:38 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Wed Nov 06 10:07:38 2013
    SMON: enabling cache recovery
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc  (incident=1345):
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
    Wed Nov 06 10:07:46 2013
    Trace dumping is performing id=[cdmp_20131106100746]
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Error 600 happened during db open, shutting down database
    USER (ospid: 5424): terminating the instance due to error 600
    Instance terminated by USER, pid = 5424
    ORA-1092 signalled during: alter database "oracl" open resetlogs...
    ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
    Wed Nov 06 10:07:47 2013
    ORA-1092 : opitsk aborting process
                                                                                                                                   251,1         95%

    >I am try to create a new database using DBCA
    >Please help me to resolve this issue.My redo log file was missing
    DROP and recreate the database.  It is a *new* database without any data.
    Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
    Hemant K Chitale

  • Creat too many instance when writing an oracle database

    Hi
    I want to write Oracle database with database toolkits;
    but..i found there are too many instance or called session(exceed the upper limit) created when the program running .  that makes the Orace server stop responding
    Is there anything  i need to modify?
    Attachments:
    Oracle DB.vi ‏36 KB

    Frankly I have never seen this problem, but then I make a point of never using the database connectivity toolkit. Assuming a Windows platform, Windows implements something called connection pooling so when you "close" a connection the OS inserts it into a pool so If you ask for another connection it doesn't actually open a new one it just gives you back a reference to one of the ones you "closed" before.
    What OS are you running on?
    What version of Oracle?
    Is the instance of Oracle local or on another computer?
    How are you communicating with Oracle (odbc, oledb, etc)?
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Photoshop CS6 creates too many History States withing 1 stroke

    I'm on MAC OSX 10.6.8, Photoshop CS6, using a Wacom Cintiq 12".
    Too often Photoshop remembers way too many History states within one pen stroke. In previous versions I don't remember this behaviour. Previously, each stroke, no matter how long, was registered as only one History state, until I raised the pen from the tablet. Now, totally sporadically without any obvious rule, Photoshop decides to remember even 100 history states within only one stroke.
    Although this is sometimes useful, if you work on really long strokes, but mostly it's highly disturbing, as after using just one tool to paint only one little circle, I loose all my other, much more important History states.
    Can somebody explain to me why???

    Noel Carboni wrote:
    Done with a mouse I get exactly one "Brush Tool" state in the history and one "Use brush" state recorded in an action.
    Could it be that your tablet driver is actually delivering information to Photoshop that makes it think you're lifting the stylus and putting it down many times per stroke?
    -Noel
    Hmmm... could be, but I don't know how to test it, as it happens occasionally... I don't experience it in other software, but I will keep an eye on that.

  • IPhones w ActiveSync creating too many connections on mail server

    Over the past two days, I have started getting 503 errors, indicating too many connections. When I went to look at active connections, I noticed that the vast majority were from the iPhones that connect using ActiveSync. Just in the 45 minutes since I cleared all active connections, my iPhone has created 14 active connections. When you multiply that by the eight iPhones we have at this company the number jumps to 112. It is easy to see why the 503 error is getting generated by the end of the business day. It is as though the iPhone is unable to let go of an active connection, and just starts a new one. This only seems to be happening since the iPhone 3.0 update. Is anyone else experiencing similar issues?

    Yes - I'm having a very similar problem on our server. But in this case the user has a very large mailbox - and imap processes are spawned but never die unless I go in and manually kill them.

  • IWeb re-creates too many pages

    I understand the difference between "Publish" and "Publish All", but what I don't understand is why iWeb re-creates so many pages when I "Publish". If I work on three pages and then simply "Publish", the darn thing spends five minutes re-creating those three and a half-dozen other pages I didn't touch. Not the end of the world, but kind of annoying.
    Is there something I can do to eliminate this, or can someone at least help me understand why I am sitting and watching iWeb spin it's wheels for so long?
    Thanks,
    Bryan

    The strange thing is that:
    Even when the new page you are working on is in another site in iWeb the publish feature goes through some long process. While no files in the other sites are changed they are 'checked one by one,' making the publish process more tedious than it has to be.
    Since the nav bar is a part of the html code all pages in the site you add a page to must be modified. If you don't wish this to happen uncheck the checkboxes in the Inspector:
    1. Select the page and Open the Inspector
    2. Click on the page icon.
    3. uncheck 'include this page in the navigation menu.' and 'display navigation menu'
    iWeb makes it very easy to create your own nav menu. Just type in some text and select it. Then open the Inspector and click on the hyperlink icon. (Arrow icon) and select 'enable as hyperlink' From the pull down menu choose one of your pages in your site.
    Kurt

  • Too many archived logs when trying a backup

    Hello all,
    I'm having a bit of trouble running a backup script on an Oracle instance (10g1, on Solaris).
    As a normal DBA practice, I guess the backup should be scheduled and run from the very beginning of using a DB. Sometimes, from various reasons, this does not happen. In this case, before running the first (full) backup of the DB, there might be tens or hundreds of archived logs waiting to be backed up, and the flash recovery area might just not be able to handle all of them (at least that's how I see it, I might be wrong, I'm still fighting my way through Oracle's Backup and Recovery issues). In that case, a backup script containing the following RMAN sequence:
    run{
    allocate channel ch1 type disk;
    backup
    incremental
    level = 0
    database;
    release channel ch1;
    fails with the error message ORA-19804 (cannot reclaim disk space from the DB_RECOVERY_FILE_DEST_SIZE limit).
    After this, the archived logs that were backed up are marked as obsolete, and I can delete them from RMAN with "delete obsolete". The script I'm using for backup runs fine afterwards. Before attempting a backup, however, no logs are reported as obsolete.
    The retention policy is the default "redundancy 1" and the archivelog deletion policy is none.
    How could I prevent the backup script from crashing? If I'm changing the archivelog deletion policy, will I be able to restore the DB properly from my backup set? (as earlier logs will be deleted before making a backup)
    Thank you for any suggestions, your help is very much appreciated,
    Adrian

    I am having an impression that you are not using scheduled backups and let client decided when to take backup. Well this is not good, in this case you won't be able to get rid of this error bcz you never know when the next or even first backup is going to occur and without that you can't even think of deleting your logs. If you are not using tape drives then your archivelogs and backups both will sit in recovery area and you should have enough available space to hold both of them. I would say to schedule your backups and use DELETE INPUT clause of RMAN backup to delete the archivelogs after backing them up. And also delete the obsolete backups according to your recovery window. This is the proper way to manage recovery area space. You really need to tune the recovery area space by testing the amount of redo generation, backup size, retention policy etc etc and then come up with a figure of recovery area size which is suitable for your env to hold all of the required files for required time (recover window).
    Daljit Singh

  • SDDM 3.1 PROD: Engineer to Relational creates too many new objects

    After upgrading to DM 3.1 production I am seeing many dublicates of my relational tables. It seems that when I perform "Engineer to Relational", some of the tables are recreated even though they already existed in the relational model.
    Currently, I have the following tables in my relational model:
    PARTIES
    PARTIESv1
    PARTIESv2
    PARTIESv3
    PARTIESv4
    PARTIESv5
    PARTIESv1-v5 have a created date of Februrary 15 or later, so they have all be created after my upgrade to DM 3.1 production.
    Is this a known bug, and will it be fixed by the upcoming patch?
    Regards,
    Marc de Oliveira

    Marc,
    I have not been able to reproduce this problem.
    I assume that the problem occurred on a model you had migrated from an earlier release? If so, was the migration from 3.0 or from 3.1 EA1, EA2 or EA3? And was this where the model was initially created, or had it been migrated previous to this latest migration?
    I assume that the Entities had been Engineered to Relational prior to the migration?
    Is it happening to all your Tables? If not, are there any obvious similarities between the Tables that have the problem?
    Any other information that might help us reproduce this problem would be appreciated. Do you use any special options in your Engineer operation?
    David

  • Too Many Table logs in DBTABLOG, RSTBPDEL is taking too much time

    Hi Experts,
    In one of our CRM system, DBTABLOG table is logging one table which is having 1 Billion entries right now. Business dont want to switch off the logging at this moment. But the table is increasing rapidly 42 Gb per month. RSTBPDEL program is running from weeks to delete them, but no control on increment.
    Can you please suggest any way to delete them quickly at first, so that my house keeping job will run daily and finish soon.
    Regards,
    Mohan.

    Hello Mohan,
    The DBTABLOG table does get large, the best is to switch off logging. If that's not possible, increase the frequency of your delete job, also explore one more alternative have a look at the archival object: BC_DBLOGS, you could archive old records (in accordance with your customer's data retention policies) to reduce the size of the table.
    Also, have a look at the following notes, they will advise you on how to improve the performance of your delete job:
    Note 531923 - Audit Trail: Indexes on table DBTABLOG
    Note 579980 - Table logs: Performance during access to DBTABLOG
    Regards,
    Siddhesh

  • Airports are creating too many separate networks, how to fix?

    Here's a picture of my current setup.  I have 1 Airport extreme that creates a 2ghz and 5ghz network.  It travels via ethernet to a airtport express 2G that creates  2ghz and 5ghz networks of the same name as the Airport etreme.
    Within that whole setup I have 2 Airport express' extending the 2ghz network which I believe is creating my problem.....
    With this whole setup some sections of my home get these results:
    It's quite annoying especially when streaming airplay because my iphone or such device will jump back and forth between the two networks making the music stream choppy.
    How would I make both the networks merge as one?  Is there a way to extend a network using ethernet as the connection instead of wifi??

    Oh wow, I feel like a fool, how did i not catch that >.<
    Also one last question, should I allow the 2nd gen express' network to be extended whil I'm already allowing the airport extreme as well?
    Thanks I'm pretty sure you fixed this

Maybe you are looking for

  • How to use '|' delimited as seprator in GUI_DOWNLOAD ? Plz suggest me ,,

    how to use '|' delimited as seprator in GUI_DOWNLOAD ? Plz suggest me ,, i want the output should be seprated by '|' delimited when i download the file.

  • Question: Which iMovie .plist do you delete?

    I'm confused sometimes as to which .plists to delete when iMovie is having problems. I've been noticing as I help people out on the iMovie Discussion group there are a lot of different preferences folders lying around on the Macintosh. For instance:

  • Events from my MAC are out of order on my iPAD

    This is NOT an IOS iPhoto issue, but since I cannot find a forum for the IOS Photo "app" I post it here anyway. I sync my photos from my MAC via iTunes to several IOS devices. This has been working fine (order of the events on my IOS device are the s

  • CS6 DCS 2.0 Channel Color Issue

    Hello! I'm creating a DCS 2.0 EPS file in photoshop CS6, and when I assign PANTONE colors to the channels, it glitches out when I print it from illustrator CS6.  Certain colors randomly will not print any data. So I renamed the channels in the DCS EP

  • Moving to Japan

    We are moving to Japan in a few months and will be there for 3 years. I just recently upgraded to the iPhone 6 plus and the thought of cancelling my cell phone and no longer having the same phone number that I've had for 11 years really bothers me; I