"Error when adding column to database"

luico14

Hi:

I am having a big problem in RapidMiner. Basically I have a decision tree model that is loaded through a ModelLoader then it is applied to a DataBaseExampleSource, which is checked work_on_database=true, since I need the results of the ModelApplier operator to be saved in the database. But an error ocurrs. This is my XML.










@73.20.0.67:1521:DWDB"/>














And this is the error:

2009年5月19日,11:08:24吗AM: [NOTE] Process starts
P May 19, 2009 11:08:24 AM: Process:
Root[1] (Process)
+- ModelLoader[1] (ModelLoader)
+- DatabaseExampleSource[1] (DatabaseExampleSource)
+- ModelApplier[1] (ModelApplier)
P May 19, 2009 11:08:59 AM: [Warning] Tree: The number of regular attributes of the given example set does not fit the number of attributes of the training example set, training: 12, application: 13
G May 19, 2009 11:08:59 AM: [Fatal] RuntimeException occured in 1st application of ModelApplier (ModelApplier)
G May 19, 2009 11:08:59 AM: [Fatal] Process failed: operator cannot be executed (Error while adding a column 'prediction(CHURN)'to database: java.sql.SQLException: ORA-00904: : invalid identifier
). Check the log messages...
Root[1] (Process)
+- ModelLoader[1] (ModelLoader)
+- DatabaseExampleSource[1] (DatabaseExampleSource)
here ==> +- ModelApplier[1] (ModelApplier)


Please can anybody provide some help to solve this?

Thanks, in advance,

haddock

Hola,

I'm not sure this will help, but here goes anyway...

it is applied to a DataBaseExampleSource, which is checked work_on_database=true, since I need the results of the ModelApplier operator to be saved in the database.

You don't actually need to work directly on the database, you could extract an example set from the database, apply the model, and then write anewtable. I do this on an MS database and all works fine. What occurs to me is that it isadding the columnthat is messing up. Just my two cents..

Good luck anyway

keith

Another possible issue could be whether the username you are connecting to the database with has been granted permission to modify the table structure.

But the real solution is as haddock mentions. Generate the prediction results from the Model Applier in RM, then write the Example Set created to a new table in the database. That way you don't clobber your original table if something screws up either. I do almost all of my RM work by interacting with databases, and haven't needed to use work_on_database yet.