On Fri, Mar 11, 2011 at 7:31 AM, Matthew R. <[email protected]> wrote:
> I am having a problem getting Redmine to run with Oracle (11.2) backend.
> I get this error (below) because Oracle table names are limited to 30
> characters. Does anyone around here know of a fix or workaround? I'm
> wondering if I can simple change the table name, or if that will break
> the application.
>
> When doing a db migrate to an Oracle db this creates the error below.
>
>
> I'm so close, but now when I do:
>
> RAILS_ENV=production rake db:migrate --trace
>
> I get:
>
> AddOpenIdAuthenticationTables: migrating
> ================================
> -- create_table(:open_id_authentication_associations, {:force=>true})
> rake aborted!
> An error has occurred, all later migrations canceled:
>
> OCIError: ORA-00972: identifier is too long: CREATE TABLE
> "OPEN_ID_AUTHENTICATION_ASSOCIATIONS" ("ID" NUMBER NOT NULL PRIMARY KEY,
> "ISSUED" NUMBER, "LIFETIME" NUMBER, "HANDLE" VARCHAR2, "ASSOC_TYPE"
> VARCHAR2, "SERVER_URL" BLOB, "SECRET" BLOB)
>
> /opt/redmine-1.1.2/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:219:in
> `log'
>
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-oracle_enhanced-adapter-1.3.2/lib/active_record/connection_adapters/oracle_enhanced_adapter.rb:1077:in
> `log'
>
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-oracle_enhanced-adapter-1.3.2/lib/active_record/connection_adapters/oracle_enhanced_adapter.rb:493:in
> `execute'
>
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-oracle_enhanced-adapter-1.3.2/lib/active_record/connection_adapters/oracle_enhanced_schema_statements.rb:84:in
> `create_table'
>
>
> Any help is greatly appreciated!
>
>
Changing the name is what you will need to do to get it to run under Oracle
11. There will be issues with the application since you are changing a table
name. You are going to have to rework your code so that all the
relationships are correctly work or else they will be looking for a table
that is not in the database.
If you are the author of the code that uses that table then you have some
work ahead of you. If you are not, then you need to send it back to your
developers explaining that the table name is too long for Oracle 11 and they
will need to rework the code. Good luck.
B.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
