Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

ActiveRecord producting core dumps in Oracle apparently when accessing multiple partitions

#5902

Due to the large amount of data we are processing, and driven by archiving requirements, we create a separate database partition for each day of raw data in our Oracle 10.2.0 databases (Linux and SunOS).

When we use an ActiveRecord database connection to perform SQL processing over data which spans these partitions:

'SELECT ''PN'' || MIN(SUBSTR(partition_name, 3)) FROM user_tab_partitions

     WHERE table_name = ''EVENT'' and SUBSTR(partition_name, 3) >=
         (SELECT /*+ PARALLEL(e, ' || la_tbl_deg(2) || ') */ TO_CHAR(MIN(occurred_at), ''YYYYMMDD'') FROM event e WHERE aggregated = ''N'') '
    into lv_pn_to_agg;

We encounter Oracle core dumps both on Linux and SunOs. These are examples of the Linux errors:

Thu Oct 28 16:56:15 2010
Errors in file /app/oracle/10.2.0/server/admin/LOCAL/bdump/local_p015_2784.trc:
ORA-07445: exception encountered: core dump [lnxsni()+123] [SIGSEGV] [Address not mapped to object] [0x000000002] [] []
Thu Oct 28 16:56:15 2010
Errors in file /app/oracle/10.2.0/server/admin/LOCAL/bdump/local_p011_2776.trc:
ORA-07445: exception encountered: core dump [lnxsni()+123] [SIGSEGV] [Address not mapped to object] [0x000000002] [] []
Thu Oct 28 16:57:11 2010
Errors in file /app/oracle/10.2.0/server/admin/LOCAL/bdump/local_p010_2827.trc:
ORA-07445: exception encountered: core dump [lnxsni()+123] [SIGSEGV] [Address not mapped to object] [0x000000002] [] []
...

We do not encounter these errors when we access the ojdbc14.jar (10.2.0.4.0) driver via DBI or Sequel.

Reported by Neil Brennan · November 1st, 2010 @ 12:57 AM

State: stale
Milestone: none
Assigned to: nobody
Importance: none

Activity

  1. Santiago Pastorino
    Santiago Pastorino
    • State changed from new to open

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

    February 2nd, 2011 @ 04:20 PM

  2. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:20 PM