Instalation rhq-server-3.0.0.B03

[joaoantunes87]

Hi,

I'm trying install the last version of rhq (3.0.0.B03). But when start the instalation appear this error:

Failed to save properties and fully deploy - RHQ Server will not function properly Cause: java.sql.SQLException:Failed to create table [RHQ_ALERT_NOTIF_LOG] [ErrorCode=[910]; SQLState=[42000]; Message=[ORA-00910: specified length too long for its datatype ]; Type=[java.sql.SQLException]][SQLException=Failed to create table [RHQ_ALERT_NOTIF_LOG] [ErrorCode=[910]; SQLState=[42000]; Message=[ORA-00910: specified length too long for its datatype ]; Type=[java.sql.SQLException]]] -> java.sql.SQLException:ORA-00910: specified length too long for its datatype [SQLException=ORA-00910: specified length too long for its datatype

I'm using the same database used to install Jopr 2.3 . I cleaned this database and tryed install the rhq, but something is wrong with the database, i think. Any idea?

PS: Another Warn that appear:

INFO  [STDOUT] Conditions on indexes are not supported for database oracle10

Thanks,

João Antunes

[pilhuhn]

This error tells you that you should use Postgres :-))

Seriously: in B03 we added new fields to the alert notification log table, where one is probably too long for oracle (or better where the DB-independent definition gets translated into a type that is not big enough). Anyway, I've opened a BZ for this Bug 570453 . This will be fixed in the upcoming B04 community build.

I am not sure if there is an easy solution to this from the B03 side - perhaps opening up the rhq-core-dbutils jar within the installer war and fixing the data type. for

    <table name="RHQ_ALERT_NOTIF_LOG" tablespace="@@@LARGE_TABLESPACE_FOR_DATA@@@"

....

        <column name="ALL_EMAILS" required="false" size="4000" type="VARCHAR2"/>

        <column name="EMAILS_FAILED" required="false" size="4000" type="VARCHAR2"/>

    </table>

This is my mistake as I put 4096 in :-/

The warning

INFO  [STDOUT] Conditions on indexes are not supported for database oracle10

is nothing to worry about it just informs that it is not possible on Oracle to do

create index foo on bar where bar.xyz = 13  (at least not like on Postgres)

Fix is in git in 'b9e910b'