Closed clarktrip1 closed 8 years ago
nromanetti
commented
8 years ago It says Caused by: java.sql.SQLException: Invalid argument(s) in call The line in the code is: MetadataExtractor.java:239
ResultSet resultSet = databaseMetaData.getIndexInfo(configuration.getCatalog(), configuration.getSchemaName(), table.getName(), retreiveOnlyUniques, useApproximation);
Have you specified a catalog in your jdbc conf ?
clarktrip1
commented
8 years ago No. I’m running it again right now and this is in the log: [INFO] Loading with catalog=[] schemaPattern=[PROD] tableNamePattern=[%] types=[TABLE]
Thanks, Cary Sr Application Developer
Note: my email address has changed to caclark@trueblue.commailto:caclark@trueblue.com
www.trueblue.comhttp://www.trueblue.com/
staff management | smx a TrueBlue company
Find us on: Webhttp://www.staffmanagement.com/ | Bloghttp://blog.staffmanagement.com/ | Twitterhttps://twitter.com/StaffManagement | LinkedInhttp://www.linkedin.com/company/14336
2014 Best of Staffing Winner—9X Greater Customer Satisfaction Score than Industry Averagehttp://www.staffmanagement.com/UserFiles/Award%20Winning%20Service_Staff%20Management%20SMX.pdf
2014 HRO Today MSP Baker's Dozen Winner—5 Years Runninghttp://www.staffmanagement.com/UserFiles/Award%20Winning%20Service_Staff%20Management%20SMX.pdf
From: Nicolas Romanetti [mailto:notifications@github.com] Sent: Friday, January 22, 2016 11:53 AM To: jaxio/celerio celerio@noreply.github.com Cc: Clark, Cary caclark@trueblue.com Subject: Re: [celerio] stacktrace from metadata phase (#2)
It says Caused by: java.sql.SQLException: Invalid argument(s) in call The line in the code is: MetadataExtractor.java:239
ResultSet resultSet = databaseMetaData.getIndexInfo(configuration.getCatalog(), configuration.getSchemaName(), table.getName(), retreiveOnlyUniques, useApproximation);
Have you specified a catalog in your jdbc conf ?
— Reply to this email directly or view it on GitHubhttps://github.com/jaxio/celerio/issues/2#issuecomment-173991712.
nromanetti
commented
8 years ago Please try again with latest Celerio release, version 4.0.4, it should be fixed...
clarktrip1
commented
8 years ago That indeed fixed it.
Thanks, Cary Sr Application Developer
Note: my email address has changed to caclark@trueblue.commailto:caclark@trueblue.com
www.trueblue.comhttp://www.trueblue.com/
staff management | smx a TrueBlue company
Find us on: Webhttp://www.staffmanagement.com/ | Bloghttp://blog.staffmanagement.com/ | Twitterhttps://twitter.com/StaffManagement | LinkedInhttp://www.linkedin.com/company/14336
2014 Best of Staffing Winner—9X Greater Customer Satisfaction Score than Industry Averagehttp://www.staffmanagement.com/UserFiles/Award%20Winning%20Service_Staff%20Management%20SMX.pdf
2014 HRO Today MSP Baker's Dozen Winner—5 Years Runninghttp://www.staffmanagement.com/UserFiles/Award%20Winning%20Service_Staff%20Management%20SMX.pdf
From: Nicolas Romanetti [mailto:notifications@github.com] Sent: Monday, January 25, 2016 3:15 PM To: jaxio/celerio celerio@noreply.github.com Cc: Clark, Cary caclark@trueblue.com Subject: Re: [celerio] stacktrace from metadata phase (#2)
Please try again with latest Celerio release, version 4.0.4, it should be fixed...
— Reply to this email directly or view it on GitHubhttps://github.com/jaxio/celerio/issues/2#issuecomment-174665364.
I connected to an Oracle schema as a simple user - not the schema owner. When reverse engineering I got this: [INFO] Extracting only unique indexes for table: DR$CIDX_OFF_APP_JOB_REQS_TXT$I [ERROR] Error while talking to database org.apache.maven.plugin.MojoExecutionException: Error while talking to database at com.jaxio.celerio.maven.plugin.dbmetadata.DbMetadataMojo.extract(DbMetadataMojo.java:186) at com.jaxio.celerio.maven.plugin.dbmetadata.DbMetadataMojo.process(DbMetadataMojo.java:168) at com.jaxio.celerio.maven.plugin.dbmetadata.DbMetadataMojo.execute(DbMetadataMojo.java:150) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: java.sql.SQLException: Invalid argument(s) in call at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70) at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445) at oracle.jdbc.OracleDatabaseMetaData.getIndexInfo(OracleDatabaseMetaData.java:3804) at com.jaxio.celerio.configuration.database.support.MetadataExtractor.loadIndexes(MetadataExtractor.java:239) at com.jaxio.celerio.configuration.database.support.MetadataExtractor.extract(MetadataExtractor.java:81) at com.jaxio.celerio.configuration.database.support.MetadataExtractor.extract(MetadataExtractor.java:59) at com.jaxio.celerio.maven.plugin.dbmetadata.DbMetadataMojo.extract(DbMetadataMojo.java:179)
I was wrong in my email the other day. DR$CIDX_OFF_APP_JOB_REQS_TXT$I is a table used by the Oracle Text feature that has an index on it named DR$CIDX_OFF_APP_JOB_REQS_TXT$X which is an Oracle CTXSYS.CONTEXT index. This index should not be reverse engineered.