Database Crashes

I am using Appleworks 6.2.9 on a MacBook Pro. It was working fine at first. Now, when I try to add text in a database field, the program crashes. I can create new records, but I can't type into fields. If a field has a checkbox, I can check and uncheck the box. But as soon as I try to type in a text or number field, down it goes.
I deleted the preference files, and now I can type one character. As soon as I type the second character, the program crashes.
This happens with previous databases that I created on my previous Macs and when I try to create new databases.
MBP   Mac OS X (10.4.7)  

Have you recently updated to OS X 10.4.7, or changed your Keyboard layout?
The 10.4.7 update appears to defualt to "US Extended" as the keyboard of choice. This is a Unicode layout, and AppleWorks chokes on any Unicode coded keyboard layout.
Go to System Preferences > International > Input Menu, and choose one of the Roman encoded keyboard layouts.
Regards,
Barry

Similar Messages

  • ORACLE 9I DATABASE - CRASH & RECOVER

    I AM USING ORACLE 9I FOR LINUX IN A DUAL XEON PROCESSOR SERVER. NOW DATABASE DOES NOT OPEN PROPERLY AND SHOW FOLLOWING MESSAGES:-
    1) for SYSDBA user message for startup database
    SQL*Plus: Release 9.2.0.1.0 - Production on Thu Aug 21 18:49:14 2003
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Enter user-name: sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 621875780 bytes
    Fixed Size 451140 bytes
    Variable Size 335544320 bytes
    Database Buffers 285212672 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL>
    2) Then we reset the logs the message is:
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/C/app/oracle9ir2/oradata/tepiapp/system01.dbf'
    SQL>
    3) When connecting with different user the message is :
    Enter user-name: mis-dba
    Enter password:
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
    0;oracle@tepiapp:~[oracle@tepiapp oracle]$
    Please guide me for detail solutions for this problem
    Regards,
    FSL

    hmmm ok, so it seems that you dont use RMAN to backup your database...
    It seems there that your have a controlfile problem after a disk crash. I hope your database is on ARCHIVELOG mode.
    Does your database crashed during activity or was idle ?
    1. Mount the database
    2. set autorecovery on ;
    recover database using backup controlfile ;
    media recovery complete <= this means that all is ok now
    3. alter database open resetlogs ;
    if #2 doesnt work cause of redo log problem such as corrupted redo log, or some transactions "blocked" in theses redo log cause of a big crash during the database activity, Oracle will tell you that a redo log is corrupted and will give you the hour of the redo log log entry that Oracle need to recover.
    So you will have to make an incomplete recovery (that means you will lose some datas, no much but some) until time.
    For example, your redo entry has been corrupted at 12:00:50
    1. recover database until time '2003-08-25:12:00:00' ;
    2. alter database open resetlogs ;
    3. Make a full backup of your database !
    Fred

  • Location of oracle database crash date time

    Hi,
    After system crash happens and oracle database is recovered from system crash where can i find the entry in oracle which shows the time of system crash?
    I tried the following to get the system crash date and time:
    When i start auditing a user by logon and the user is logged on to system oracle creates an entry in dba_audit_session table for user logontime in TIMESTAMP column, but if the system crashes in between when the user is logged in to the system then no entry is made in LOGOFF_TIME column of dba_audit_session table.
    in followin example orcl user is being audited by logon.
    orcl logsin the system at time 11:36 am and my system crashes.
    when orcl logsin again after instance recovery logoff_time is blank, and shows a new entry of orcl.
    SQL > select username,to_char(timestamp,'dd-mm-yyyy hh:mi:ss'),to_char(logoff_time,'dd-mm-yyyy hh:mi:ss') from dba_audit_session where username like 'TMS' order by timestamp;
    USERNAME TO_CHAR(TIMESTAMP,' TO_CHAR(LOGOFF_TIME
    ORCL 16-10-2012 11:36:16
    ORCL 16-10-2012 11:46:33
    My aim is to get the date & time of database crash.

    Hi;
    As mention here the only way to check alert.log, If Asm avaliable you need also check asmlog and related log files.
    If you have OSwatcher on your system you can also check what process or wha happend on your server too
    PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
    Regard
    Helios

  • Production Database Crashed

    Dear Members
    let see a scneario
    i have a primary database and a standby database
    my production database crashed
    how can i recover my standby database until last comitted transaction. how can i get imy transactions from online redo logs which were on primary database
    now my primary database server is crashed i cant login to primary database.
    is standby database's redo logs synched with primary database's online redo logs?
    please help me out
    regards

    Hi,
    You need to check first whether all online Redo Logs till the point of time - are applied to DB.
    Check for logs still need to apply or not - If all the logs are applied then you can stop the real time apply on standby and the cancel the recovery on standby and try to Open the DB in read write mode for access
    Is there any other standby apart from this . ??
    If not first take the backup of this standby immediately, then recover the DB on primary DB till the point of time of crash and try to mount the DB on primary.
    then you can make it as standby.
    - Pavan Kumar N
    Oracle 9i/10g - OCP
    http://oracleinternals.blogspot.com/

  • Can anyone tell me the senarios in which database crashes

    hi
    can anyone tell me the senarios in which database crashes other then backup recovery concepts.when the databse goes live
    regards,
    swapna.s

    Those sort of errors would mostly be TNS errors when the database server runs out of memory (memory configured for Oracle, swapping, number of network connections limit) etc...
    Other than that, if the application is written badly (which I hope is not the case), then users may face deadlock situations but those would be handled by Oracle automatically.
    Of course, these errors can be handled by properly tuning the database or the application.

  • Database crash simulator (for training)?

    Hi All
    I would like to prepare for OCP (from 10g) exam. I there any software (free or commercial) to simulate some typical database crashes (lost redologs, lost datafile, lost controlfile and many other.). So that user should detect what has happened and correct the issue. Of course I can do it myself, but when you know what is exactly wrong, it is easy to correct as well.
    Regards
    Groxy

    You can do it by yourself
    I advice you to install VMware on your PC, install Oracle on it. SHutdown and copy whole Vmware folder to another directory.
    THen open vmware and start your testing. If you'll do something that you can't recover, (of course, you have to do your best to recover crashed database) just close the vmware and delete it. And open another vmware and do your testings there
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com

  • TABLESPACE BACKUP - Database crash

    Hello guys,
    i got a little question about "Online / Hot Backup" and a crashing instance.
    The following worst case happen:
    1) Alter Tablespace TABSP_USER01 in backup mode at 03:00 am
    2) There is a problem, while copying the datafiles and the backup modus for the tablespace TABSP_USER01 exists all the time
    3) Database crashes at 04:30 am and the tablespace TABSP_USER01 is still in backup mode
    4) While the whole online/hot backup was run, an archive log backup runs at 04:00 am and the saved archive log files are deleted from disk
    I know what happen to the datafiles while the "online backup". The SCN is frozen when the "backup modus" is set... and in the redo log files a complete block-image is written.
    All dirty blocks are written to the datafiles, while the "backup modus" is on, but the SCN is not updated.
    But my question is now:
    1) If i restart my crashed instance at 05:03 am .. are the archive logs needed for checking (which were already back upped and deleted) at a startup?
    2) Does Oracle verify the data in the redo/archive logs with the ones in the datafiles?
    3) Or does Oracle only set the actual SCNs to the header of the datafiles (the actual scn is get from the controlfile)?
    Thanks and Regards
    Stefan

    #1) If i restart my crashed instance at 05:03 am .. are the archive logs needed for checking (which were already back upped and deleted) at a startup? ##
    Yes it will ask for the recovery needed in the mount stage.you need to backup again...
    # 2) Does Oracle verify the data in the redo/archive logs with the ones in the datafiles? &3) Or does Oracle only set the actual SCNs to the header of the datafiles (the actual scn is get from the controlfile)? ###
    The asnwer is yes and no...It checks both header and information..
    Since it is asking for the recocvery it is understandable that it checks for header is not in synch and will apply all the changes...to make it synch.(.all the sequenced are captured in redo-log and archived logs.)
    kindly go through this document for clarifications..
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#i1007289
    Thanks
    -- Raman

  • Is OAE H-A? Can it sustain a database crash?

    A recent database crash caused HTMLDB 1.6 to crash, showing "Service unavailable" even after the database was back up.
    Is it designed to sustain a brief database outage? Can it be configured to recover, failback, failover, without a restart of the application server? We are running htmldb on oAS 10.1.2. The J2EE part is designed to use DataSource that retries the connections and therefore can sustain a connection outage.

    HTML DB does not need/utilize Oracle Application Server. All it needs is Apache and the database.
    It is as H-A as Oracle itself since it "lives" inside the database.
    If your database goes down, HTML DB goes down. When the database comes up, HTML DB is back up. [Provided, of course, Apache is up and running all the time]
    Not that I don't believe you, but when you got ""Service unavailable" even after the database was back up", what did the Apache logs show?

  • Estimation/Indication of Database Crash

    OS Information:Any version
    OS Information:Windows and/or Linux
    Estimation/Indication of Database Crash
    Hello,
    Its an open question that can you tell me the errors/warnings (at least 3) which are exists in alert log at present, whose meaning is that your database will be crashed in next one hour. I mean which ORA-NNNNN or other in alert log; whose indication is same that your database (not instance) is going to be crash within next one hour definately, so that i may get backup or export. Please let me know that question is clear or not.
    If you can please elaborate in view of different oracle version and/or OS, it will additional helpful reply to question.
    Regards
    Girish Sharma

    "there is already a service disruption"
    If the archiver stops, then there is no service disruption until all redo log groups are full, so you do have time to fix the problem before then database hangs.
    Most archiver hangs are due to disk full which you can avoid if you monitor disk usage, flashback area usage, and have automatic jobs to backup and purge archivelogs.
    Archiver hung also happens due to bugs, controlfile locks, disk errors (NFS etc) or network errors (Dataguard), and in these cases you can't predict them with monitoring, so you won't know about them until you get alert log errors.
    Another error with a similar result would be ORA-19809 :-
    ARC0: Error 19809 Creating archive log file to '/oraexport/d1122/DB1122/archivelog/2010_01_06/o1_mf_1_240_%u_.arc'
    Wed Jan 06 16:05:00 2010
    Errors in file /opt/oracle/product/diag/rdbms/db1122/db1122/trace/db1122_arc2_3408.trc:
    ORA-19815: WARNING: db_recovery_file_dest_size of 104857600 bytes is 100.00% used, and has 0 remaining bytes available.
    You have following choices to free up space from recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
       then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
       BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
       reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
       system command was used to delete files, then use RMAN CROSSCHECK and
       DELETE EXPIRED commands.
    Errors in file /opt/oracle/product/diag/rdbms/db1122/db1122/trace/db1122_arc2_3408.trc:
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 35865088 bytes disk space from 104857600 limit

  • If ur database crash u have only export of database how u create database f

    if ur database crash u have only export of database how u create database from starting with help of export give steps

    What is an "export give steps?"
    If ur's database crashes, how is it u's responsibility to restore it?
    Now, if my database crashes, I just restart it in crash recovery mode and not even worry about the backup or export. It is not needed.

  • Database crash, CPU Starvation

    hi, i am using 11.2.0.3 version of oracle. We have recently migrated to 11g, after 1 month of smooth and comparatively better performance, we are suddenly facing performance issues with our database and it got crashed twice within 5 days. even we didnt push any new code to our database in recent past, atleast after the 11G migration. And after getting feedback from the ORACLE corporation guys , they pointed out about the default database stats gathering job, which was eating most of the CPU, because of the default degree mentioned So it was running in 160 parallel threads causing resource starvation.so we reduce the degree of the stats gathering job to 8 .
    But the database crashed again two days back, and rebooted within 3 mins to back to normal, even after this default degree changed to 8. And i am observing around some specific time its happening,dont know if its just a coincidence!!! So if you can provide some help , how to dig down to the base , if this is happening due to any specific application related sql or anything else.

    Actually we have got below sql reported by Oracle corporation guys, which was consuming much the database resources and cause of resource starvation.
    I have Changed some of the table names/aliases. Now the issue is that, this query is taking ~14hrs for complete execution resulting into 1027 records for company-1.
    So then i tried executing the query for a different company - 2, it resulted into 3 records and completed within few seconds. Then i tried forcing the same plan with company-1, and it completes within ~20 minutes. So ideally the optimizer should follow the optimal path for company-1 too, but its not doing somehow due to some reason. Less optimal plan ,using index id2 for scanning table IV rather Id1. i want to identify the reason. given below is the query + test details. Here xmvl is the views. having below inline query.  Id1 is on column (companypk,c2,inorg,dt1) of IV. and Id2 is on column (payeeid,companypk).
    --Query for inline view xmvl
    SELECT *
         FROM XMVL_B XB, CP CC
        WHERE XB.bcmpnypk = CC.pcmpnypk
              OR XB.bcmpnypk = CC.ccmpnypk;
    Below is the stats for both the indexes: Id1 and Id2:
    leaf_blocks, blevel,   distinct_keys, avg_leaf_blocks_per_key, avg_data_blocks_per_key, clustering_factor,num_rows
    445090       3        4018676             1                  18                     42811230       83166160
    869410       4        141335             24                  1239                 43912510        82126740
    Column Companypk of IV is having frequency histogram on it.
    -- Below is the sql query causing issue    
    SELECT
           IV.pk,
             IV.PN pid,
             IV.IPK,
             IV.INUM,
             IV.IDT,
             IV.VDNM,
             IV.ivst1 ivstat,
             IV.ivgvl,
             IV.ivnpk ivnpk1,
             IV.intc,
             IV.sc
        FROM IV IV
       WHERE     IV.COMPANYPK = 1
             AND IV.intc NOT IN ('C')
             AND IV.INORG IN ('APP', 'IMG')
             AND IV.pk IS NULL
             AND IV.INUM LIKE '147%'
             AND IV.ivnpk IN
                    ('J1',
                     'J2',
                     'J3',
                     'J4',
                     'J5',
                     'j6')
             AND EXISTS
                    (SELECT 1
                       FROM xmvl xsl, pi pi
                      WHERE     xsl.suplpk = pi.paypk
                            AND xsl.supplstpk = IV.stpk
                            AND xsl.bcmpnypk = IV.companypk
                            AND pi.pid = IV.payeeid
                            AND pi.payn = IV.payeen)
    ORDER BY IDT DESC;
    1027 rows selected.
    Elapsed: 14:25:26.44
    SQL> set termout on
    SQL>  spool plan.lst
    SQL>  select * from table(dbms_xplan.display_cursor(null, null, 'ALLSTATS LAST'));
    Plan hash value: 3052094360
    | Id  | Operation                            | Name                   | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  | Writes |  OMem |  1Mem | Used-Mem | Used-Tmp|
    |   0 | SELECT STATEMENT                     |                        |      1 |        |   1027 |00:06:12.65 |      17M|     13M|   2400 |       |       |          |         |
    |   1 |  SORT ORDER BY                       |                        |      1 |      1 |   1027 |00:06:12.65 |      17M|     13M|   2400 |   178K|   178K|  158K (0)|         |
    |   2 |   NESTED LOOPS                       |                        |      1 |        |   1027 |13:22:51.84 |      17M|     13M|   2400 |       |       |          |         |
    |   3 |    NESTED LOOPS                      |                        |      1 |      1 |     40M|00:29:57.97 |    2323K|    657K|   2400 |       |       |          |         |
    |   4 |     VIEW                             | VW_SQ_1                |      1 |   2516 |    214K|00:00:06.15 |     457K|   2400 |   2400 |       |       |          |         |
    |   5 |      HASH UNIQUE                     |                        |      1 |   2516 |    214K|00:00:05.87 |     457K|   2400 |   2400 |    23M|  4152K| 3731K (1)|   20480 |
    |   6 |       CONCATENATION                  |                        |      1 |        |    214K|00:00:02.53 |     457K|      0 |      0 |       |       |          |         |
    |   7 |        NESTED LOOPS                  |                        |      1 |        |    214K|00:00:02.40 |     457K|      0 |      0 |       |       |          |         |
    |   8 |         NESTED LOOPS                 |                        |      1 |   2434 |    214K|00:00:01.50 |     242K|      0 |      0 |       |       |          |         |
    |   9 |          NESTED LOOPS                |                        |      1 |   2434 |    214K|00:00:00.55 |    3599 |      0 |      0 |       |       |          |         |
    |  10 |           TABLE ACCESS BY INDEX ROWID| CP                     |      1 |      1 |      1 |00:00:00.01 |       3 |      0 |      0 |       |       |          |         |
    |* 11 |            INDEX UNIQUE SCAN         | CP_p1                  |      1 |      1 |      1 |00:00:00.01 |       2 |      0 |      0 |       |       |          |         |
    |  12 |           TABLE ACCESS BY INDEX ROWID| XMVL_B                 |      1 |   2434 |    214K|00:00:00.47 |    3596 |      0 |      0 |       |       |          |         |
    |* 13 |            INDEX RANGE SCAN          | ID_BCOMPNYPK           |      1 |   2434 |    214K|00:00:00.15 |     552 |      0 |      0 |       |       |          |         |
    |* 14 |          INDEX UNIQUE SCAN           | PI_P1                  |    214K|      1 |    214K|00:00:00.72 |     239K|      0 |      0 |       |       |          |         |
    |  15 |         TABLE ACCESS BY INDEX ROWID  | pi                     |    214K|      1 |    214K|00:00:00.68 |     214K|      0 |      0 |       |       |          |         |
    |  16 |        NESTED LOOPS                  |                        |      1 |        |      0 |00:00:00.05 |     555 |      0 |      0 |       |       |          |         |
    |  17 |         NESTED LOOPS                 |                        |      1 |     82 |      0 |00:00:00.05 |     555 |      0 |      0 |       |       |          |         |
    |  18 |          NESTED LOOPS                |                        |      1 |     82 |      0 |00:00:00.05 |     555 |      0 |      0 |       |       |          |         |
    |  19 |           TABLE ACCESS BY INDEX ROWID| CP                     |      1 |      1 |      1 |00:00:00.01 |       3 |      0 |      0 |       |       |          |         |
    |* 20 |            INDEX UNIQUE SCAN         | CP_p1                  |      1 |      1 |      1 |00:00:00.01 |       2 |      0 |      0 |       |       |          |         |
    |  21 |           TABLE ACCESS BY INDEX ROWID| XMVL_B                 |      1 |     82 |      0 |00:00:00.05 |     552 |      0 |      0 |       |       |          |         |
    |* 22 |            INDEX RANGE SCAN          | ID_BCOMPNYPK           |      1 |   2434 |      0 |00:00:00.05 |     552 |      0 |      0 |       |       |          |         |
    |* 23 |          INDEX UNIQUE SCAN           | PI_P1                  |      0 |      1 |      0 |00:00:00.01 |       0 |      0 |      0 |       |       |          |         |
    |  24 |         TABLE ACCESS BY INDEX ROWID  | pi                     |      0 |      1 |      0 |00:00:00.01 |       0 |      0 |      0 |       |       |          |         |
    |* 25 |     INDEX RANGE SCAN                 | id2                    |    214K|      3 |     40M|00:29:24.10 |    1865K|    655K|      0 |       |       |          |         |
    |* 26 |    TABLE ACCESS BY GLOBAL INDEX ROWID| IV                     |     40M|      1 |   1027 |13:54:31.57 |      15M|     12M|      0 |       |       |          |         |
    Predicate Information (identified by operation id):
      11 - access("CC"."ccmpnypk"=1)
      13 - access("XB"."bcmpnypk"="CC"."ccmpnypk")
      14 - access("XB"."suplpk"="PI"."PAYPK")
      20 - access("CC"."ccmpnypk"=1)
      22 - access("XB"."bcmpnypk"="CC"."pcmpnypk")
           filter(LNNVL("XB"."bcmpnypk"="CC"."ccmpnypk"))
      23 - access("XB"."suplpk"="PI"."PAYPK")
      25 - access("ITEM_3"="IV"."payeeid" AND "ITEM_2"="IV"."COMPANYPK")
           filter("IV"."COMPANYPK"=1)
      26 - filter(("IV"."pk" IS NULL AND "IV"."INUM" LIKE '147%' AND INTERNAL_FUNCTION("IV"."INORG") AND
                  INTERNAL_FUNCTION("IV"."ivnpk") AND "IV"."intc"<>'C' AND "ITEM_1"="IV"."stpk" AND "ITEM_4"="IV"."payeen"))
    68 rows selected.
    --- Below is the plan for a different company - companypk -- 2   
    Execution Plan
    Plan hash value: 1295920100
    | Id  | Operation                            | Name                   | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
    |   0 | SELECT STATEMENT                     |                        |     1 |   182 |     6  (17)| 00:00:01 |       |       |
    |   1 |  SORT ORDER BY                       |                        |     1 |   182 |     6  (17)| 00:00:01 |       |       |
    |   2 |   NESTED LOOPS SEMI                  |                        |     1 |   182 |     5   (0)| 00:00:01 |       |       |
    |*  3 |    TABLE ACCESS BY GLOBAL INDEX ROWID| IV                     |     1 |   174 |     2   (0)| 00:00:01 | ROWID | ROWID |
    |*  4 |     INDEX RANGE SCAN                 | id1                    |     2 |       |     1   (0)| 00:00:01 |       |       |
    |   5 |    VIEW PUSHED PREDICATE             | VW_SQ_1                |     1 |     8 |     3   (0)| 00:00:01 |       |       |
    |   6 |     NESTED LOOPS                     |                        |     1 |   107 |     3   (0)| 00:00:01 |       |       |
    |   7 |      NESTED LOOPS                    |                        |     1 |    84 |     2   (0)| 00:00:01 |       |       |
    |   8 |       TABLE ACCESS BY INDEX ROWID    | pi                     |     1 |    68 |     1   (0)| 00:00:01 |       |       |
    |*  9 |        INDEX UNIQUE SCAN             | PI_UQ                  |     1 |       |     1   (0)| 00:00:01 |       |       |
    |  10 |       TABLE ACCESS BY INDEX ROWID    | CP                     |     1 |    16 |     1   (0)| 00:00:01 |       |       |
    |* 11 |        INDEX UNIQUE SCAN             | CP_p1                  |     1 |       |     1   (0)| 00:00:01 |       |       |
    |* 12 |      INDEX RANGE SCAN                | IDX_SPLLLIST           |     1 |    23 |     1   (0)| 00:00:01 |       |       |
    Predicate Information (identified by operation id):
       3 - filter("IV"."pk" IS NULL AND "IV"."INUM" LIKE '147%' AND
                  ("IV"."ivnpk"='j6' OR "IV"."ivnpk"='J2' OR
                  "IV"."ivnpk"='J1' OR "IV"."ivnpk"='J5' OR
                  "IV"."ivnpk"='J3' OR "IV"."ivnpk"='J4') AND
                  "IV"."intc"<>'C')
       4 - access("IV"."COMPANYPK"=2)
           filter("IV"."INORG"='APP' OR "IV"."INORG"='IMG')
       9 - access("PI"."pid"="IV"."payeeid" AND "PI"."payn"="IV"."payeen")
      11 - access("CC"."ccmpnypk"="IV"."COMPANYPK")
      12 - access("XB"."suplpk"="PI"."PAYPK" AND "XB"."supplstpk"="IV"."stpk")
           filter("XB"."bcmpnypk"="CC"."pcmpnypk" OR "XB"."bcmpnypk"="CC"."ccmpnypk")
    -- Then i force the plan outline for company-1 , and got the below result.
    SELECT      /*+
          BEGIN_OUTLINE_DATA
          IGNORE_OPTIM_EMBEDDED_HINTS
          OPTIMIZER_FEATURES_ENABLE('11.2.0.3')
          DB_VERSION('11.2.0.3')
          OPT_PARAM('query_rewrite_enabled' 'false')
          OPT_PARAM('_optimizer_use_feedback' 'false')
          OPT_PARAM('optimizer_index_cost_adj' 30)
          OPT_PARAM('optimizer_index_caching' 90)
          ALL_ROWS
          OUTLINE_LEAF(@"SEL$38CB8147")
          PUSH_PRED(@"SEL$629EDCDD" "VW_SQ_1"@"SEL$F5A55792" 10 9 8 7)
          OUTLINE_LEAF(@"SEL$629EDCDD")
          UNNEST(@"SEL$335DD26A")
          OUTLINE(@"SEL$833EDA65")
          OUTLINE(@"SEL$629EDCDD")
          UNNEST(@"SEL$335DD26A")
          OUTLINE(@"SEL$F5A55792")
          OUTLINE(@"SEL$335DD26A")
          MERGE(@"SEL$3")
          OUTLINE(@"SEL$1")
          OUTLINE(@"SEL$2")
          OUTLINE(@"SEL$3")
          INDEX_RS_ASC(@"SEL$629EDCDD" "IV"@"SEL$1" ("IV"."COMPANYPK" "IV"."INVOICESOURCE"
                  "IV"."INORG" "IV"."AUDIT_CREATE_DATE"))
          NO_ACCESS(@"SEL$629EDCDD" "VW_SQ_1"@"SEL$F5A55792")
          LEADING(@"SEL$629EDCDD" "IV"@"SEL$1" "VW_SQ_1"@"SEL$F5A55792")
          USE_NL(@"SEL$629EDCDD" "VW_SQ_1"@"SEL$F5A55792")
          INDEX_RS_ASC(@"SEL$38CB8147" "PI"@"SEL$2" ("pi"."pid" "pi"."payn"))
          INDEX_RS_ASC(@"SEL$38CB8147" "CC"@"SEL$3" ("CP"."ccmpnypk"))
          INDEX(@"SEL$38CB8147" "XB"@"SEL$3" ("XMVL_B"."suplpk" "XMVL_B"."supplstpk"
                  "XMVL_B"."bcmpnypk"))
          LEADING(@"SEL$38CB8147" "PI"@"SEL$2" "CC"@"SEL$3" "XB"@"SEL$3")
          USE_NL(@"SEL$38CB8147" "CC"@"SEL$3")
          USE_NL(@"SEL$38CB8147" "XB"@"SEL$3")
          END_OUTLINE_DATA
      */      /* xign.buyerwebinvclient.search.InvoiceCloneSearchData */
            IV.pk,
             IV.PN pid,
             IV.IPK,
             IV.INUM,
             IV.IDT,
             IV.VDNM,
             IV.ivst1 ivstat,
             IV.ivgvl,
             IV.ivnpk ivnpk1,
             IV.intc,
             IV.sc
        FROM IV IV
       WHERE     IV.COMPANYPK = 1
             AND IV.intc NOT IN ('C')
             AND IV.INORG IN ('APP', 'IMG')
             AND IV.pk IS NULL
             AND IV.INUM LIKE '147%'
             AND IV.ivnpk IN
                    ('J1',
                     'J2',
                     'J3',
                     'J4',
                     'J5',
                     'j6')
             AND EXISTS
                    (SELECT 1
                       FROM xmvl xsl, pi pi
                      WHERE     xsl.suplpk = pi.paypk
                            AND xsl.supplstpk = IV.stpk
                            AND xsl.bcmpnypk = IV.companypk
                            AND pi.pid = IV.payeeid
                            AND pi.payn = IV.payeen)
    ORDER BY IDT DESC;
    1031 rows selected.
    Elapsed: 00:19:14.60
    Plan hash value: 1295920100
    | Id  | Operation                            | Name                   | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  |  OMem |  1Mem | Used-Mem |
    |   0 | SELECT STATEMENT                     |                        |      1 |        |   1031 |00:13:31.14 |    1132K|    628K|       |       |          |
    |   1 |  SORT ORDER BY                       |                        |      1 |      1 |   1031 |00:13:31.14 |    1132K|    628K|   160K|   160K|  142K (0)|
    |   2 |   NESTED LOOPS SEMI                  |                        |      1 |      1 |   1031 |00:13:31.13 |    1132K|    628K|       |       |          |
    |*  3 |    TABLE ACCESS BY GLOBAL INDEX ROWID| IV                     |      1 |     29 |   1031 |00:13:26.26 |    1127K|    627K|       |       |          |
    |*  4 |     INDEX RANGE SCAN                 | id1                    |      1 |     15M|    938K|00:02:01.25 |     208K|    205K|       |       |          |
    |   5 |    VIEW PUSHED PREDICATE             | VW_SQ_1                |   1031 |      1 |   1031 |00:00:04.87 |    5748 |    881 |       |       |          |
    |   6 |     NESTED LOOPS                     |                        |   1031 |      1 |   1031 |00:00:04.86 |    5748 |    881 |       |       |          |
    |   7 |      NESTED LOOPS                    |                        |   1031 |      1 |   1031 |00:00:03.71 |    3918 |    583 |       |       |          |
    |   8 |       TABLE ACCESS BY INDEX ROWID    | pi                     |   1031 |      1 |   1031 |00:00:03.70 |    2878 |    583 |       |       |          |
    |*  9 |        INDEX UNIQUE SCAN             | PI_UQ                  |   1031 |      1 |   1031 |00:00:01.70 |    1847 |    326 |       |       |          |
    |  10 |       TABLE ACCESS BY INDEX ROWID    | CP                     |   1031 |      1 |   1031 |00:00:00.01 |    1040 |      0 |       |       |          |
    |* 11 |        INDEX UNIQUE SCAN             | CP_p1                  |   1031 |      1 |   1031 |00:00:00.01 |       9 |      0 |       |       |          |
    |* 12 |      INDEX RANGE SCAN                | IDX_SPLLLIST           |   1031 |      1 |   1031 |00:00:01.15 |    1830 |    298 |       |       |          |
    Predicate Information (identified by operation id):
       3 - filter(("IV"."pk" IS NULL AND "IV"."INUM" LIKE '147%' AND INTERNAL_FUNCTION("IV"."ivnpk") AND
                  "IV"."intc"<>'C'))
       4 - access("IV"."COMPANYPK"=1)
           filter(("IV"."INORG"='APP' OR "IV"."INORG"='IMG'))
       9 - access("PI"."pid"="IV"."payeeid" AND "PI"."payn"="IV"."payeen")
      11 - access("CC"."ccmpnypk"="IV"."COMPANYPK")
      12 - access("XB"."suplpk"="PI"."PAYPK" AND "XB"."supplstpk"="IV"."stpk")
           filter(("XB"."bcmpnypk"="CC"."pcmpnypk" OR "XB"."bcmpnypk"="CC"."ccmpnypk"))
    51 rows selected.
    Elapsed: 00:00:01.58
    SQL>  spool off
    SQL>

  • SAP oracle database crash with errore:ORA-00490: PSP process terminated

    Hi ALL,
    Our oracle database crash with errore code in trace : ORA:00490; i started database again and it  working fine; but could not fine reason of down and what is this erroe all about
    can some help me
    Errors in file /oracle/SRD/saptrace/background/srd_pmon_28096.trc:
    ORA-00490: PSP process terminated with error
    Tue Nov 25 09:00:57 2008
    PMON: terminating instance due to error 490
    Instance terminated by PMON, pid = 28096
    Thanks,
    Dinesh

    Hi stefen,
    please find the trace file as below
    /oracle/SRD/saptrace/background/srd_pmon_28096.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning and Data Mining options
    ORACLE_HOME = /oracle/SRD/102_64
    System name:    SunOS
    Node name:      nzlsfn23
    Release:        5.10
    Version:        Generic_137111-01
    Machine:        sun4u
    Instance name: SRD
    Redo thread mounted by this instance: 1
    Oracle process number: 2
    Unix process pid: 28096, image: oracle@nzlsfn23 (PMON)
    2008-11-25 09:00:57.497
    SERVICE NAME:(SYS$BACKGROUND) 2008-11-25 09:00:56.210
    SESSION ID:(24.1) 2008-11-25 09:00:56.194
    Background process PSP0 found dead
    Oracle pid = 6
    OS pid (from detached process) = 28098
    OS pid (from process state) = 28098
    dtp = 38000afd8, proc = 497000860
    Dump of memory from 0x000000038000AFD8 to 0x000000038000B020
    38000AFD0                   00000005 00000000          [........]
    38000AFE0 00000004 97000860 00000000 00000000  [.......`........]
    38000AFF0 00000000 50535030 00020000 00000000  [....PSP0........]
    38000B000 00006DC2 00000000 00000000 48E50DA4  [..m.........H...]
    38000B010 00000001 000E3273 00040081 00000000  [......2s........]
    Dump of memory from 0x0000000497000860 to 0x0000000497001048
    497000860 02010000 00000000 00000000 00000000  [................]
    497000870 00000000 00000000 00000000 00000000  [................]
    497000880 00000004 97042570 00000004 97047810  [......%p......x.]
    497000890 00000004 97028E68 00000004 97045BE8  [.......h......[.]
    4970008A0 00000000 00000000 00000004 97045C70  [..............\p]
    4970008B0 00000004 97045C70 00000004 97047800  [......\p......x.]
    4970008C0 01060000 00000000 00000004 97025ED8  [..............^.]
    4970008D0 00000004 97028E68 00000006 00000000  [.......h........]
    4970008E0 00000000 00000000 00000000 00000000  [................]
    4970008F0 00000000 00000000 00000004 97042490  [..............$.]
    497000900 00000004 970425A0 00000000 00000000  [......%.........]
    497000910 00000000 00000000 00000000 00000000  [................]
            Repeat 3 times
    497000950 00000003 00000000 00000000 00000000  [................]
            Repeat 1 times
    497000970 00000000 00000000 00000000 00000000  [................]
    497000980 00000004 00000000 00000000 00000000  [................]
    497000990 00000003 00000000 00000000 00000000  [................]
            Repeat 1 times
    4970009B0 00000004 00000000 00000000 00000000  [................]
    4970009C0 00000005 00000000 00000000 00000000  [................]
    4970009D0 00000003 00000000 00000000 00000000  [................]
    4970009E0 00000000 00000000 00000000 00000000  [................]
            Repeat 8 times
    497000A70 00000000 00000000 00000004 97000A78  [...............x]
    497000A80 00000004 97000A78 00000000 00000000  [.......x........]
    497000A90 00000000 00000000 00000004 97000A98  [................]
    497000AA0 00000004 97000A98 00000000 00000000  [................]
    497000AB0 00000000 00000000 00000000 00000000  [................]
            Repeat 2 times
    497000AE0 00000000 00000000 00000018 00000030  [...............0]
    497000AF0 00000001 00000B3D 00000004 970037D0  [.......=......7.]
    497000B00 00000004 580096B0 00000001 00000000  [....X...........]
    497000B10 00000000 00000000 00000000 00000000  [................]
            Repeat 2 times
    497000B40 00006DC2 00000000 00000000 00000000  [..m.............]
    497000B50 00000000 00000000 00000000 00000000  [................]
            Repeat 2 times
    497000B80 00000004 97000860 00000000 00000000  [.......`........]
    497000B90 00000000 00000000 00000000 00000000  [................]
            Repeat 7 times
    497000C10 00000004 97000C10 00000004 97000C10  [................]
    497000C20 00000000 00000000 00010000 00000000  [................]
    497000C30 00000000 00000117 0000000A 00000000  [................]
    497000C40 00006DC2 00000000 00000000 48E50DA4  [..m.........H...]
    497000C50 00000001 00000000 00000000 00000000  [................]
    497000C60 00000000 00000000 00000000 00000000  [................]
            Repeat 2 times
    497000C90 00000000 00000000 00000003 FFFFFFFF  [................]
    497000CA0 00000000 00000000 00000000 00000000  [................]
            Repeat 13 times
    497000D80 73726461 646D0000 00000000 00000000  [srdadm..........]
    497000D90 00000000 00000000 00000000 00000000  [................]
    497000DA0 00000000 00000006 6E7A6C73 666E3233  [........nzlsfn23]
    497000DB0 00000000 00000000 00000000 00000000  [................]
            Repeat 2 times
    497000DE0 00000000 00000000 00000000 00000008  [................]
    497000DF0 554E4B4E 4F574E00 00000000 00000000  [UNKNOWN.........]
    497000E00 00000000 00000000 00000000 00000000  [................]
    497000E10 00000000 00000008 32383039 38000000  [........28098...]
    497000E20 00000000 00000000 00000000 00000000  [................]
    497000E30 00000000 00000005 6F726163 6C65406E  [........oracle@n]
    497000E40 7A6C7366 6E323320 28505350 30290000  [zlsfn23 (PSP0)..]
    497000E50 00000000 00000000 00000000 00000000  [................]
    497000E60 00000000 00000000 00000000 00000016  [................]
    497000E70 00000000 00000002 00000000 00000000  [................]
    497000E80 00000000 00000000 00000000 00000000  [................]
            Repeat 8 times
    497000F10 00000000 00000000 00000000 00020000  [................]
    497000F20 00000000 00000000 00000000 00000000  [................]
    497000F30 00000000 00000000 00000003 9E1F6748  [..............gH]
    497000F40 00000004 97001728 00000004 97000758  [.......(.......X]
    497000F50 00000000 00000000 00000003 9E26B5B0  [.............&..]
    497000F60 00000000 00000000 00000000 00000000  [................]
            Repeat 1 times
    497000F80 00000004 97000F80 00000004 97000F80  [................]
    497000F90 00000000 00040000 00000000 00000000  [................]
    497000FA0 00000000 00031A55 00000000 0004D7DD  [.......U........]
    497000FB0 00000000 00071A55 00000000 00000000  [.......U........]
    497000FC0 00000000 00000000 00000000 00000000  [................]
    497000FD0 00000000 00000828 00000000 000000E0  [.......(........]
    497000FE0 00000000 00000828 00000000 00000000  [.......(........]
    497000FF0 00000000 00000000 00000000 00000000  [................]
            Repeat 4 times
    497001040 00000002 00000000                    [........]
    error 490 detected in background process
    ORA-00490: PSP process terminated with error

  • Difference between Instance Crash and Database Crash in Standalone and RAC?

    I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
    RAC_".+
    Oracle Version: 11.1.0.7.0
    O.S Version: HP-UX B.11.31 U

    Sivaprasad S wrote:
    I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
    RAC_".+That depends on your definitions of database crash versus instance crash.
    Literally, database crash means that the database itself is damaged in some way. A disk is no more. Data files are corrupted. Etc. The database itself thus causes the crash - and a database crash will also cause all database instances (RAC or single) for that database to crash too.
    An instance crash will therefore mean that the crash occurs in the instance due to an Oracle bug or similar. In other words a s/w error and not a database error. The database is still "fine", but the instance not. Instance crashes. However, any other instance on that same (RAC) database will still be fine as the database itself is unaffected by that s/w error in the crashed instance.
    If you mean something different, please enlighten us. Not all crashes are equal. {noformat};-){noformat}

  • Rman with commvault mml: database crash while delete obsolete

    Hello!
    I have a problem concerning RMAN, delete obsolete and CommVault media management library: Every night at 23:00 we run a RMAN "Backup" to delete the obsolete backup files from tape. Since the update to CommVault agent 8 (from version 7) the database crashes while the delete obsolete command. The normal backup (incremental 0/1) works without problem.
    After restarting the database i tried the delete obsolete via shell -> same result: CRASH.
    The CommVault support says that there is an Oracle bug with different MML's, that causes this behaviour - but i can't find anything at Metalink.
    This is the output of RMAN (tell me which other logs can be helpful):
    RMAN-Sperr-Policy wird f³r den Befehl angewendet
    RMAN-Sperr-Policy ist auf ein Recovery-Fenster von 0 Tagen festgelegt
    Die folgenden veralteten Backups und Kopien werden gel÷scht:
    Typ Schl³ssel Abschlusszeit Dateiname/Handle
    Backup Set 7 01.09.10
    Backup Piece 12 01.09.10 c-190884945-20100901-01
    Backup Set 9 01.09.10
    Backup Piece 17 01.09.10 c-190884945-20100901-02
    M÷chten Sie die obigen Objekte wirklich l÷schen (geben Sie YES oder NO ein)? yes
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: Abbruchfehler bei der Ausf³hrung des Befehls
    ORA-12514: TNS: Listener kann in Connect-Deskriptor angegebenen Service aktuell nicht aufl÷sen -> listener can not resolve service name
    RMAN-03009: Fehler bei delete Befehl in ORA_MAINT_SBT_TAPE_1 Kanal auf 09/02/2010 08:57:37 -> error at delete command
    ORA-03135: connection lost contact
    Recovery Manager nicht kompatibel mit TARGET Datenbank: RMAN 14155912.14155908.14312748.1 bis 1651797107.0.27143.0 erforderlich -> recovery not compatible with TARGET database
    Best regards,
    Christian

    Hi,
    show parameter plsq
    plsql_code_type           string     INTERPRETED
    plsql_compiler_flags          string     INTERPRETED, NON_DEBUG
    That database is in interpreted mode.
    Check also the pacakages:
    select OWNER, OBJECT_NAME , PARAM_NAME ||'='||PARAM_VALUE param from DBA_STORED_SETTINGS where OBJECT_NAME in ( 'DBMS_RCVCAT','DBMS_RCVMAN' )and param_name = 'plsql_code_type'
    OWNER               OBJECT_NAME
    PARAM
    SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
    SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
    If it is native you have an issue!
    François,

  • Data Loss when a database crashes

    Hi Experts,
    I was asked the question of "how much data is lost when you pull the plug off an oracle database all of a sudden".. and my answer was "all the data in the buffers that have not been committed". We know that you can have committed data sitting in the redo logs (that have not been written to the datafiles) that the instance will use for recovery once the instance is restarted again; however, this got me thinking and asking the question of how much uncommitted data is actually sitting in memory that potentially can be lost if the instance goes down all of a sudden?
    With the use of sga_target and sga_max_size, the memory allocation for the cache buffer will vary from time to time.. So, is it possible to quantify the amount of lost data at all (in byts, kb, mb..etc)?
    For example if the sga is set to 1gb (sga_max_size=1000mb), check point every 15mins (as we can't predict/know how often the app commits).. assume a basic transaction size for any small to medium size database. Redo logs set to 50mb (even though this doesn't come into play at this stage).
    I would be really interested in your thoughts and ideas please.
    Thanks

    All Oracle Data Manipulation Language (DML) and Date Definition Language (DDL) statements must record an entry in the Redo log buffer before they are being executed.
    The Redo log buffer is:
    •     Part of the System Global Area (SGA)
    •     Operating in a circular fashion.
    •     Size in bytes determined by the LOG_BUFFER init parameter.
    Each Oracle instance has only one log writer process (LGWR). The log writer operates in the background and writes all records from the Redo log buffer to the Redo log files.
    Well, just to clarify, log writer is writing committed and uncommitted transactions from the redo log buffer to the log files more or less continuously - not just on commit (when the log buffer is 10mb full, 1/3 full, every 3 seconds or every commit - whichever comes first - those all trigger redo writes).
    The LGWR process writes:
    •     Every 3 seconds.
    •     Immediately when a transaction is committed.
    •     When the Redo log buffer is 1/3 full.
    •     When the database writer process (DBWR) signals.
    Crash and instance recovery involves the following:
    •     Roll-Forward
    The database applies the committed and uncommitted data in the current online redo log files.
    •     Roll-Backward
    The database removes the uncommitted transactions applied during a Roll-Forward.
    What also comes into play in the event of a crash is MTTR, for which there is a advisory utility as of Oracle 10g. Oracle recommends using the fast_start_mttr_target initialization parameter to control the duration of startup after instance failure.
    From what I understand, uncommitted transactions will be lost, or more precisely undone after an instance crash. That's why it is good practice to manually commit transactions, unless you plan to use SQL rollback. Btw, every DDL statement and exit from sqlplus implies an automatic commit.
    Edited by: Markus Waldorf on Sep 4, 2010 10:56 AM

Maybe you are looking for