A little late, but always helpful.

First, we couldn't find dbupgrade in logs folder (Wind2008 + JDK 1.6.0_10). So, we installed Jopr 2.3.0 on another machine (WinXP + JDK 1.6.0_03) and it had better results! All the tables were created and dbupgrade file was right there.

However, when we tried to run Jopr Server, we got

java.lang.IllegalArgumentException: Not supported: indent-number

Caused by: java.lang.IllegalArgumentException: Plugin [Augeas] is required by plugins [[Apt]] but it does not exist in the dependency graph yet

GRANT SELECT ON sys.dba_pending_transactions TO jon;
GRANT SELECT ON sys.pending_trans$ TO jon;
GRANT SELECT ON sys.dba_2pc_pending TO jon;
GRANT EXECUTE ON sys.dbms_system TO jon;

Well, good and bad news....

Installing Jopr 2.3.0 from scratch worked like a charm. However, minutes after everything was configured, we realized version 2.3.1 was just released. So, we decided to upgrade from 2.3.0 to 2.3.1 and, for the sake of Murphy, it didn´t work.

Failed to save properties and fully deploy - Jopr Server will not function properly Cause: java.lang.RuntimeException:Cannot run ANT on script [D:\jopr-server-2.3.1\logs\db-upgrade.xml]. Cause: D:\jopr-server-2.3.1\logs\db-upgrade.xml:32: Failed to upgrade - error in spec version [2.58]. Cause: Error executing the task [org.rhq.core.db.ant.dbupgrade.SST_AddColumn] in schema spec version [2.58]. Cause: Failed to add the new column. Cause: java.sql.SQLException: ORA-01430: column being added already exists in table -> org.apache.tools.ant.BuildException:Failed to upgrade - error in spec version [2.58]. Cause: Error executing the task [org.rhq.core.db.ant.dbupgrade.SST_AddColumn] in schema spec version [2.58]. Cause: Failed to add the new column. Cause: java.sql.SQLException: ORA-01430: column being added already exists in table -> org.apache.tools.ant.BuildException:Failed to upgrade - error in spec version [2.58]. Cause: Error executing the task [org.rhq.core.db.ant.dbupgrade.SST_AddColumn] in schema spec version [2.58]. Cause: Failed to add the new column. Cause: java.sql.SQLException: ORA-01430: column being added already exists in table -> org.apache.tools.ant.BuildException:Error executing the task [org.rhq.core.db.ant.dbupgrade.SST_AddColumn] in schema spec version [2.58]. Cause: Failed to add the new column. Cause: java.sql.SQLException: ORA-01430: column being added already exists in table -> org.apache.tools.ant.BuildException:Failed to add the new column. Cause: java.sql.SQLException: ORA-01430: column being added already exists in table -> java.sql.SQLException:ORA-01430: column being added already exists in table [SQLException=ORA-01430: column being added already exists in table ]

Oh gosh.

Except the schema upgrade thing, is there any other issue censuring 2.3.0? I've spent the whole morning installing it on an empty database and setting everything up. If there is nothing else disapproving 2.3.0, I'd rather keep it working instead of spend another day reconfiguring everything again on 2.3.1.

thanks