You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[WARNING] SQL exception : Exception while executing meta query: ORA-00904: "AC"."SEARCH_CONDITION_VC": ungültiger Bezeichner
sql
select
ac.OWNER,
ac.TABLE_NAME,
ac.CONSTRAINT_NAME,
ac.SEARCH_CONDITION
from SYS.ALL_CONSTRAINTS ac
where (
ac.CONSTRAINT_TYPE = 'C'
and ac.OWNER in (
'MDC', 'GPM', 'MASTER'
)
and (
ac.GENERATED <> 'GENERATED NAME'
or ac.SEARCH_CONDITION_VC not in (
select (('"' || atc.COLUMN_NAME) || '" IS NOT NULL')
from SYS.ALL_TAB_COLS atc
where (
atc.OWNER = ac.OWNER
and atc.TABLE_NAME = ac.TABLE_NAME
)
)
)
)
[ERROR] Error while generating table MASTER.EXP_MST_MACHINE_MDC_API
java.lang.NullPointerException
at org.jooq.meta.AbstractDatabase.onError (AbstractDatabase.java:2550)
at org.jooq.meta.AbstractDatabase.getRelations (AbstractDatabase.java:2016)
at org.jooq.meta.DefaultColumnDefinition.getPrimaryKey (DefaultColumnDefinition.java:91)
at org.jooq.meta.AbstractTableDefinition.getPrimaryKey (AbstractTableDefinition.java:86)
at org.jooq.codegen.JavaGenerator.generateTable (JavaGenerator.java:3880)
at org.jooq.codegen.JavaGenerator.generateTable (JavaGenerator.java:3874)
at org.jooq.codegen.JavaGenerator.generateTables (JavaGenerator.java:3861)
at org.jooq.codegen.JavaGenerator.generate (JavaGenerator.java:519)
at org.jooq.codegen.JavaGenerator.generate (JavaGenerator.java:473)
at org.jooq.codegen.JavaGenerator.generate (JavaGenerator.java:394)
at org.jooq.codegen.GenerationTool.run0 (GenerationTool.java:845)
at org.jooq.codegen.GenerationTool.run (GenerationTool.java:222)
at org.jooq.codegen.GenerationTool.generate (GenerationTool.java:217)
at org.jooq.codegen.maven.Plugin.execute (Plugin.java:207)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
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:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
at org.codehaus.classworlds.Launcher.main (Launcher.java:47)
When generating jOOQ code with flag includeCheckConstraints enabled using artifact org.jooq.pro-java-8:jooq-codegen-maven:3.13.1 on Oracle Database 11g Release 11.2.0.3.0
Thank you very much for your report. We'll fix this immediately.
Unless you need check constraint information in your code, this can be safely ignored. The exceptions should be merely cosmetic, and can be muted with the new <onError/> flag
Expected behavior and actual behavior:
Column SEARCH_CONDITION_VC does not exist in table SYS.ALL_CONSTRAINTS on RDMS Oracle Database 11g
Because of that the loading of check constraints fails during the jOOQ Code generation.
https://support.oracle.com/knowledge/More%20Applications%20and%20Technologies/2466572_1.html
Steps to reproduce the problem (if possible, create an MCVE: https://github.com/jOOQ/jOOQ-mcve):
When generating jOOQ code with flag includeCheckConstraints enabled using artifact org.jooq.pro-java-8:jooq-codegen-maven:3.13.1 on Oracle Database 11g Release 11.2.0.3.0
Versions:
The text was updated successfully, but these errors were encountered: