WARN kodo.jdbc.Schema - Existing column "JDOID" on table
Sorry, I've posted this before and never got back with some debug.
I'm getting
WARN kodo.jdbc.Schema - Existing column "JDOID" on table "<TABLE NAME
HERE>" is incompatible with the same column in the given schema definition.
I running
kodo.jdbc.meta.MappingTool.main("-a","buildSchema","persistent.class(s)"...
Here my complete trace output (Kodo 3.0.1)
0 [23.01.04 10:04:39,712] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.alert.config.AlertConfiguration" with action
"buildSchema".
2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.alert.config.MonitoredInteractionType" with
action "buildSchema".
2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.alert.config.MonitoredSourceProcessType"
with action "buildSchema".
2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.alert.Alert" with action "buildSchema".
2303 [23.01.04 10:04:42,015] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.ClientConfiguration" with
action "buildSchema".
2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.ClientIdentity" with action
"buildSchema".
2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.ConfigurationOption" with
action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.ConfigurationValue" with
action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.FileTrackingConfiguration"
with action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.GeneralConfiguration" with
action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.InteractionNotification" with
action "buildSchema".
2593 [23.01.04 10:04:42,305] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.NotificationType" with action
"buildSchema".
2603 [23.01.04 10:04:42,315] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.client.PCIdentity" with action
"buildSchema".
2613 [23.01.04 10:04:42,325] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.pc.PCConfiguration" with action
"buildSchema".
2643 [23.01.04 10:04:42,355] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.server.ConsoleAdminUser" with action
"buildSchema".
2693 [23.01.04 10:04:42,405] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.server.SafeArea" with action
"buildSchema".
2723 [23.01.04 10:04:42,435] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.server.ServerConfiguration" with
action "buildSchema".
2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.config.server.TemplateDefinition" with
action "buildSchema".
2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.connection.ConnectCommand" with action
"buildSchema".
2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.interaction.EntityInteraction"
with action "buildSchema".
2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping tool running
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionFileElement" with
action "buildSchema".
2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping tool running
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionFileProperty" with
action "buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionProperty" with
action "buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionSourceIdentity"
with action "buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.Entity" with action
"buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.EntityChronicle" with action
"buildSchema".
2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.EntityLocation" with action
"buildSchema".
2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.EntityLocationFilePath" with
action "buildSchema".
2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.EntityNode" with action
"buildSchema".
2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping tool running
on type "class com.jario.server.entitymodel.EntityProperty" with action
"buildSchema".
2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Recording mapping and
schema changes.
2953 [23.01.04 10:04:42,665] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ALERT".
2983 [23.01.04 10:04:42,695] [main] INFO kodo.jdbc.Schema - Reading column
information for table "alert".
2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALERTCONFIGURATION_JDOID" on table "alert".
2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALERTNAME" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
column "TYPESTR" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
column "TYPE_NULL" on table "alert".
2993 [23.01.04 10:04:42,705] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ALERTCONFIG".
3034 [23.01.04 10:04:42,746] [main] INFO kodo.jdbc.Schema - Reading column
information for table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALERTGRANUALITY_NULL" on table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALERTGRANULARITYLEVEL" on table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
column "CLIENTNOTIFICATIONGROUP_NULL" on table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ENTITYNODE_JDOID" on table "alertconfig".
3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "alertconfig".
3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "alertconfig".
3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "alertconfig".
3064 [23.01.04 10:04:42,776] [main] DEBUG kodo.jdbc.Schema - Found existing
column "TYPESTR" on table "alertconfig".
3064 [23.01.04 10:04:42,776] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ALERTCONFIG_EXTERNPROCTYPE".
3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Reading column
information for table "alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Found existing
column "EXCLUDEDSOURCEPROCESSTYP_JDOID" on table
"alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Found existing
column "EXCLUDEDSOURCEPROCESSTYP_ORDER" on table
"alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name
"ALERTCONFIG_MONINTERACTTYPE".
3084 [23.01.04 10:04:42,796] [main] INFO kodo.jdbc.Schema - Reading column
information for table "alertconfig_moninteracttype".
3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "alertconfig_moninteracttype".
3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Found existing
column "MONITOREDINTERACTIONTYP_JDOID" on table
"alertconfig_moninteracttype".
3094 [23.01.04 10:04:42,806] [main] DEBUG kodo.jdbc.Schema - Found existing
column "MONITOREDINTERACTIONTYP_ORDER" on table
"alertconfig_moninteracttype".
3094 [23.01.04 10:04:42,806] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CLIENTALERTCONFIG".
3104 [23.01.04 10:04:42,816] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALERTTYPE" on table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "clientalertconfig".
3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name
"CLIENTALERTCONFIG_NOTIFYSET".
3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientalertconfig_notifyset".
3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Found existing
column "INTERACTIONNOTIFYSET_JDOID" on table "clientalertconfig_notifyset".
3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Found existing
column "INTERACTIONNOTIFYSET_ORDER" on table "clientalertconfig_notifyset".
3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientalertconfig_notifyset".
3124 [23.01.04 10:04:42,836] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CLIENTCONFIG".
3144 [23.01.04 10:04:42,856] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientconfig".
3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Found existing
column "CLIENTIDENTITY_JDOID" on table "clientconfig".
3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Found existing
column "FILETRACKINGCONFIG_JDOID" on table "clientconfig".
3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Found existing
column "GENERALCONFIGURATION_JDOID" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name
"CLIENTCONFIG_ALLALERTCONFIG".
3184 [23.01.04 10:04:42,896] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientconfig_allalertconfig".
3184 [23.01.04 10:04:42,896] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALLALERTSCONFIGURATION_JDOID" on table
"clientconfig_allalertconfig".
3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ALLALERTSCONFIGURATION_ORDER" on table
"clientconfig_allalertconfig".
3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientconfig_allalertconfig".
3194 [23.01.04 10:04:42,906] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CLIENTFILETRACKINGCONFIG".
3234 [23.01.04 10:04:42,946] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientfiletrackingconfig".
3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Found existing
column "EXCLUDEDFOLDERS_JDOID" on table "clientfiletrackingconfig".
3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Found existing
column "FILETYPES_JDOID" on table "clientfiletrackingconfig".
3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "clientfiletrackingconfig".
3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientfiletrackingconfig".
3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "clientfiletrackingconfig".
3244 [23.01.04 10:04:42,956] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CLIENTGENERALCONFIG".
3264 [23.01.04 10:04:42,976] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientgeneralconfig".
3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "clientgeneralconfig".
3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientgeneralconfig".
3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "clientgeneralconfig".
3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Found existing
column "LANGUAGE_JDOID" on table "clientgeneralconfig".
3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Found existing
column "LOADMESSENGERONSTARTUP_JDOID" on table "clientgeneralconfig".
3284 [23.01.04 10:04:42,996] [main] DEBUG kodo.jdbc.Schema - Found existing
column "LOADVIEWERONSTARTUP_JDOID" on table "clientgeneralconfig".
3284 [23.01.04 10:04:42,996] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CLIENTIDENTITY".
3324 [23.01.04 10:04:43,036] [main] INFO kodo.jdbc.Schema - Reading column
information for table "clientidentity".
3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Found existing
column "DOMAINSTR" on table "clientidentity".
3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "clientidentity".
3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "clientidentity".
3334 [23.01.04 10:04:43,046] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "clientidentity".
3344 [23.01.04 10:04:43,056] [main] DEBUG kodo.jdbc.Schema - Found existing
column "USERNAME" on table "clientidentity".
3354 [23.01.04 10:04:43,066] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CONFIGOPTION".
3384 [23.01.04 10:04:43,096] [main] INFO kodo.jdbc.Schema - Reading column
information for table "configoption".
3384 [23.01.04 10:04:43,096] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
column "MANDATORY" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
column "SELECTED" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
column "VALUESTR" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CONFIGVALUE".
3414 [23.01.04 10:04:43,126] [main] INFO kodo.jdbc.Schema - Reading column
information for table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
column "LOCKED" on table "configvalue".
3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Found existing
column "MULTIOPTION" on table "configvalue".
3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Found existing
column "SAVEDELETEDOPTIONS" on table "configvalue".
3434 [23.01.04 10:04:43,146] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CONFIGVALUE_DELETEOPTIONS".
3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Reading column
information for table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Found existing
column "DELETEDOPTIONS_JDOID" on table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Found existing
column "DELETEDOPTIONS_ORDER" on table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CONFIGVALUE_OPTIONS".
3464 [23.01.04 10:04:43,176] [main] INFO kodo.jdbc.Schema - Reading column
information for table "configvalue_options".
3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "configvalue_options".
3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Found existing
column "OPTIONS_JDOID" on table "configvalue_options".
3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Found existing
column "OPTIONS_ORDER" on table "configvalue_options".
3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CONNECTIONCOMMAND".
3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Reading column
information for table "connectioncommand".
3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "connectioncommand".
3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "connectioncommand".
3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "connectioncommand".
3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Found existing
column "SENDERSPCIDENTITY_JDOID" on table "connectioncommand".
3484 [23.01.04 10:04:43,196] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "CONSOLEADMINUSER".
3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Reading column
information for table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
column "PASSWORD" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
column "USERNAME" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITY".
3544 [23.01.04 10:04:43,256] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entity".
3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ENTITYNODE_JDOID" on table "entity".
3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Found existing
column "HASHCODE" on table "entity".
3554 [23.01.04 10:04:43,266] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entity".
3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entity".
3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entity".
3574 [23.01.04 10:04:43,286] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYCHRONICLE".
3584 [23.01.04 10:04:43,296] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entitychronicle".
3584 [23.01.04 10:04:43,296] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ROOTENTITYNODE_JDOID" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYINTER".
3604 [23.01.04 10:04:43,316] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "EXACTTIMESTAMP" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "FILEELEMENT_JDOID" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "INTERACTIONTYPE_NULL" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
column "OLDFILEELEMENT_JDOID" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
column "SOURCEIDENTITY_JDOID" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
column "SOURCEPROCESSNAME" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
column "TIMESTAMPDATE" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
column "TYPESTR" on table "entityinter".
3624 [23.01.04 10:04:43,336] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYINTERFILEELEMENT".
3634 [23.01.04 10:04:43,346] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityinterfileelement".
3634 [23.01.04 10:04:43,346] [main] DEBUG kodo.jdbc.Schema - Found existing
column "FILESTORAGETYPE_NULL" on table "entityinterfileelement".
3644 [23.01.04 10:04:43,356] [main] DEBUG kodo.jdbc.Schema - Found existing
column "FULLPATH" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
column "HASHCODE" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
column "REMOTELOCALPATH" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
column "TYPESTR" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name
"ENTITYINTERFILEELEMENT_ENTPROP".
3684 [23.01.04 10:04:43,396] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityinterfileelement_entprop".
3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ENTITYINTERACTIONPROPS_JDOID" on table
"entityinterfileelement_entprop".
3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ENTITYINTERACTIONPROPS_ORDER" on table
"entityinterfileelement_entprop".
3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityinterfileelement_entprop".
3694 [23.01.04 10:04:43,406] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYINTERFILEPROPERTY".
3704 [23.01.04 10:04:43,416] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityinterfileproperty".
3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entityinterfileproperty".
3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityinterfileproperty".
3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entityinterfileproperty".
3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Found existing
column "KEYSTR" on table "entityinterfileproperty".
3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Found existing
column "VALUESTR" on table "entityinterfileproperty".
3724 [23.01.04 10:04:43,436] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYINTERPROPERTY".
3734 [23.01.04 10:04:43,446] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
column "KEYSTR" on table "entityinterproperty".
3744 [23.01.04 10:04:43,456] [main] DEBUG kodo.jdbc.Schema - Found existing
column "VALUESTR" on table "entityinterproperty".
3744 [23.01.04 10:04:43,456] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYINTERSOURCEIDENTITY".
3754 [23.01.04 10:04:43,466] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
column "CLIENTIDENTITY_JDOID" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOCLASS" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOVERSION" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
column "PCIDENTITY_JDOID" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYINTER_ENTPROP".
3775 [23.01.04 10:04:43,487] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entityinter_entprop".
3775 [23.01.04 10:04:43,487] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ENTITYINTERACTIONPROPS_JDOID" on table "entityinter_entprop".
3775 [23.01.04 10:04:43,487] [main] DEBUG kodo.jdbc.Schema - Found existing
column "ENTITYINTERACTIONPROPS_ORDER" on table "entityinter_entprop".
3775 [23.01.04 10:04:43,487] [main] DEBUG kodo.jdbc.Schema - Found existing
column "JDOID" on table "entityinter_entprop".
3805 [23.01.04 10:04:43,517] [main] INFO kodo.jdbc.Schema - Reading table
information for schema name "null", table name "ENTITYLOCATION".
3815 [23.01.04 10:04:43,527] [main] INFO kodo.jdbc.Schema - Reading column
information for table "entitylocation".
3815 [23.01.04 10:04:43,527] [main] DEBUG kodo.jdbc.Schema - Found existing
column "CREATORENTITYINTERACTION_JDOID" on table "entitylocation".
3815 [23.01.04 10:04:43,527] [main] DEBUG kodo.jdbc.Schema - Found existing
column "DELETED" on table "entitylocation".
3815 [23.01.04 10:04:43,527] [main] DEBUG kodo.jdbc.Schema - Found existing
column "FILESTORAGETYPE_NULL" on tabl
Any Ideas on the warns I'm getting via running
'kodo.jdbc.meta.MappingTool.main'
For every table I have:
'WARN kodo.jdbc.Schema - Existing column "JDOID" on table "<TABLE NAME
HERE>" is incompatible with the same column in the given schema definition.'
Kind Regards
Graham Cruickshanks
(Now running Kodo 3.0.2)
"Graham Cruickshanks" <[email protected]> wrote in message
news:[email protected]...
Sorry, I've posted this before and never got back with some debug.
I'm getting
WARN kodo.jdbc.Schema - Existing column "JDOID" on table "<TABLE NAME
HERE>" is incompatible with the same column in the given schemadefinition.
>
I running
kodo.jdbc.meta.MappingTool.main("-a","buildSchema","persistent.class(s)"...
>
Here my complete trace output (Kodo 3.0.1)
0 [23.01.04 10:04:39,712] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.alert.config.AlertConfiguration" withaction
"buildSchema".
2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.alert.config.MonitoredInteractionType"with
action "buildSchema".
2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.alert.config.MonitoredSourceProcessType"
with action "buildSchema".
2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.alert.Alert" with action "buildSchema".
2303 [23.01.04 10:04:42,015] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.ClientConfiguration" with
action "buildSchema".
2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.ClientIdentity" with action
"buildSchema".
2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.ConfigurationOption" with
action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.ConfigurationValue" with
action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.FileTrackingConfiguration"
with action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.GeneralConfiguration" with
action "buildSchema".
2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.InteractionNotification"with
action "buildSchema".
2593 [23.01.04 10:04:42,305] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.NotificationType" withaction
"buildSchema".
2603 [23.01.04 10:04:42,315] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.client.PCIdentity" with action
"buildSchema".
2613 [23.01.04 10:04:42,325] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.pc.PCConfiguration" with action
"buildSchema".
2643 [23.01.04 10:04:42,355] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.server.ConsoleAdminUser" withaction
"buildSchema".
2693 [23.01.04 10:04:42,405] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.server.SafeArea" with action
"buildSchema".
2723 [23.01.04 10:04:42,435] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.server.ServerConfiguration" with
action "buildSchema".
2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.config.server.TemplateDefinition" with
action "buildSchema".
2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.connection.ConnectCommand" with action
"buildSchema".
2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.interaction.EntityInteraction"
with action "buildSchema".
2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping toolrunning
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionFileElement"with
action "buildSchema".
2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping toolrunning
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionFileProperty"with
action "buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionProperty" with
action "buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
on type "class
com.jario.server.entitymodel.interaction.EntityInteractionSourceIdentity"
with action "buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.Entity" with action
"buildSchema".
2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.EntityChronicle" with action
"buildSchema".
2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.EntityLocation" with action
"buildSchema".
2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.EntityLocationFilePath" with
action "buildSchema".
2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.EntityNode" with action
"buildSchema".
2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping toolrunning
on type "class com.jario.server.entitymodel.EntityProperty" with action
"buildSchema".
2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Recording mappingand
schema changes.
2953 [23.01.04 10:04:42,665] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ALERT".
2983 [23.01.04 10:04:42,695] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "alert".
2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALERTCONFIGURATION_JDOID" on table "alert".
2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALERTNAME" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "TYPESTR" on table "alert".
2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "TYPE_NULL" on table "alert".
2993 [23.01.04 10:04:42,705] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ALERTCONFIG".
3034 [23.01.04 10:04:42,746] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALERTGRANUALITY_NULL" on table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALERTGRANULARITYLEVEL" on table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "CLIENTNOTIFICATIONGROUP_NULL" on table "alertconfig".
3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ENTITYNODE_JDOID" on table "alertconfig".
3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "alertconfig".
3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "alertconfig".
3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "alertconfig".
3064 [23.01.04 10:04:42,776] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "TYPESTR" on table "alertconfig".
3064 [23.01.04 10:04:42,776] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name"ALERTCONFIG_EXTERNPROCTYPE".
>
3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "EXCLUDEDSOURCEPROCESSTYP_JDOID" on table
"alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "EXCLUDEDSOURCEPROCESSTYP_ORDER" on table
"alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "alertconfig_externproctype".
3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name
"ALERTCONFIG_MONINTERACTTYPE".
3084 [23.01.04 10:04:42,796] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "alertconfig_moninteracttype".
3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "alertconfig_moninteracttype".
3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "MONITOREDINTERACTIONTYP_JDOID" on table
"alertconfig_moninteracttype".
3094 [23.01.04 10:04:42,806] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "MONITOREDINTERACTIONTYP_ORDER" on table
"alertconfig_moninteracttype".
3094 [23.01.04 10:04:42,806] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CLIENTALERTCONFIG".
3104 [23.01.04 10:04:42,816] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALERTTYPE" on table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientalertconfig".
3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "clientalertconfig".
3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name
"CLIENTALERTCONFIG_NOTIFYSET".
3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientalertconfig_notifyset".
3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "INTERACTIONNOTIFYSET_JDOID" on table"clientalertconfig_notifyset".
>
3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "INTERACTIONNOTIFYSET_ORDER" on table"clientalertconfig_notifyset".
>
3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientalertconfig_notifyset".
3124 [23.01.04 10:04:42,836] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CLIENTCONFIG".
3144 [23.01.04 10:04:42,856] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientconfig".
3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "CLIENTIDENTITY_JDOID" on table "clientconfig".
3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "FILETRACKINGCONFIG_JDOID" on table "clientconfig".
3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "GENERALCONFIGURATION_JDOID" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "clientconfig".
3164 [23.01.04 10:04:42,876] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name
"CLIENTCONFIG_ALLALERTCONFIG".
3184 [23.01.04 10:04:42,896] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientconfig_allalertconfig".
3184 [23.01.04 10:04:42,896] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALLALERTSCONFIGURATION_JDOID" on table
"clientconfig_allalertconfig".
3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ALLALERTSCONFIGURATION_ORDER" on table
"clientconfig_allalertconfig".
3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientconfig_allalertconfig".
3194 [23.01.04 10:04:42,906] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CLIENTFILETRACKINGCONFIG".
3234 [23.01.04 10:04:42,946] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientfiletrackingconfig".
3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "EXCLUDEDFOLDERS_JDOID" on table "clientfiletrackingconfig".
3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "FILETYPES_JDOID" on table "clientfiletrackingconfig".
3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "clientfiletrackingconfig".
3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientfiletrackingconfig".
3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "clientfiletrackingconfig".
3244 [23.01.04 10:04:42,956] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CLIENTGENERALCONFIG".
3264 [23.01.04 10:04:42,976] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientgeneralconfig".
3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "clientgeneralconfig".
3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientgeneralconfig".
3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "clientgeneralconfig".
3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "LANGUAGE_JDOID" on table "clientgeneralconfig".
3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "LOADMESSENGERONSTARTUP_JDOID" on table "clientgeneralconfig".
3284 [23.01.04 10:04:42,996] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "LOADVIEWERONSTARTUP_JDOID" on table "clientgeneralconfig".
3284 [23.01.04 10:04:42,996] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CLIENTIDENTITY".
3324 [23.01.04 10:04:43,036] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "clientidentity".
3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "DOMAINSTR" on table "clientidentity".
3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "clientidentity".
3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "clientidentity".
3334 [23.01.04 10:04:43,046] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "clientidentity".
3344 [23.01.04 10:04:43,056] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "USERNAME" on table "clientidentity".
3354 [23.01.04 10:04:43,066] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CONFIGOPTION".
3384 [23.01.04 10:04:43,096] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "configoption".
3384 [23.01.04 10:04:43,096] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "MANDATORY" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "SELECTED" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "VALUESTR" on table "configoption".
3394 [23.01.04 10:04:43,106] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CONFIGVALUE".
3414 [23.01.04 10:04:43,126] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "configvalue".
3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "LOCKED" on table "configvalue".
3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "MULTIOPTION" on table "configvalue".
3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "SAVEDELETEDOPTIONS" on table "configvalue".
3434 [23.01.04 10:04:43,146] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name"CONFIGVALUE_DELETEOPTIONS".
>
3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "DELETEDOPTIONS_JDOID" on table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "DELETEDOPTIONS_ORDER" on table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "configvalue_deleteoptions".
3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CONFIGVALUE_OPTIONS".
3464 [23.01.04 10:04:43,176] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "configvalue_options".
3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "configvalue_options".
3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "OPTIONS_JDOID" on table "configvalue_options".
3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "OPTIONS_ORDER" on table "configvalue_options".
3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CONNECTIONCOMMAND".
3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "connectioncommand".
3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "connectioncommand".
3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "connectioncommand".
3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "connectioncommand".
3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "SENDERSPCIDENTITY_JDOID" on table "connectioncommand".
3484 [23.01.04 10:04:43,196] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "CONSOLEADMINUSER".
3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "PASSWORD" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "USERNAME" on table "consoleadminuser".
3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ENTITY".
3544 [23.01.04 10:04:43,256] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entity".
3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ENTITYNODE_JDOID" on table "entity".
3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "HASHCODE" on table "entity".
3554 [23.01.04 10:04:43,266] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entity".
3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entity".
3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "entity".
3574 [23.01.04 10:04:43,286] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ENTITYCHRONICLE".
3584 [23.01.04 10:04:43,296] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entitychronicle".
3584 [23.01.04 10:04:43,296] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ROOTENTITYNODE_JDOID" on table "entitychronicle".
3594 [23.01.04 10:04:43,306] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ENTITYINTER".
3604 [23.01.04 10:04:43,316] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "EXACTTIMESTAMP" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "FILEELEMENT_JDOID" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "INTERACTIONTYPE_NULL" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "entityinter".
3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "OLDFILEELEMENT_JDOID" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "SOURCEIDENTITY_JDOID" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "SOURCEPROCESSNAME" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "TIMESTAMPDATE" on table "entityinter".
3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "TYPESTR" on table "entityinter".
3624 [23.01.04 10:04:43,336] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ENTITYINTERFILEELEMENT".
3634 [23.01.04 10:04:43,346] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entityinterfileelement".
3634 [23.01.04 10:04:43,346] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "FILESTORAGETYPE_NULL" on table "entityinterfileelement".
3644 [23.01.04 10:04:43,356] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "FULLPATH" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "HASHCODE" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "REMOTELOCALPATH" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "TYPESTR" on table "entityinterfileelement".
3674 [23.01.04 10:04:43,386] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name
"ENTITYINTERFILEELEMENT_ENTPROP".
3684 [23.01.04 10:04:43,396] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entityinterfileelement_entprop".
3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ENTITYINTERACTIONPROPS_JDOID" on table
"entityinterfileelement_entprop".
3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "ENTITYINTERACTIONPROPS_ORDER" on table
"entityinterfileelement_entprop".
3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entityinterfileelement_entprop".
3694 [23.01.04 10:04:43,406] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ENTITYINTERFILEPROPERTY".
3704 [23.01.04 10:04:43,416] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entityinterfileproperty".
3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entityinterfileproperty".
3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entityinterfileproperty".
3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "entityinterfileproperty".
3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "KEYSTR" on table "entityinterfileproperty".
3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "VALUESTR" on table "entityinterfileproperty".
3724 [23.01.04 10:04:43,436] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name "ENTITYINTERPROPERTY".
3734 [23.01.04 10:04:43,446] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOVERSION" on table "entityinterproperty".
3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "KEYSTR" on table "entityinterproperty".
3744 [23.01.04 10:04:43,456] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "VALUESTR" on table "entityinterproperty".
3744 [23.01.04 10:04:43,456] [main] INFO kodo.jdbc.Schema - Readingtable
information for schema name "null", table name"ENTITYINTERSOURCEIDENTITY".
>
3754 [23.01.04 10:04:43,466] [main] INFO kodo.jdbc.Schema - Readingcolumn
information for table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "CLIENTIDENTITY_JDOID" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOCLASS" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Foundexisting
column "JDOID" on table "entityintersourceidentity".
3765 [23.01.04 10:04:43,477] [main] DE
Similar Messages
-
Displaying a non existent column from a Table.
Hi
I have an SQL Query that returns back a count of all the
entities
select count(*)'COUNTER',
id_entity 'ENTITY'
from claim
where id_status = 'O'
group by id_status,id_entity
order by id_entity ASC
Output
COUNTER ENTITY
169 AGL
6 DBC
28 DELI would like to put a non existent column called 'Type' with a counter
of 0,so that the output looks like :
COUNTER ENTITY
0 TYP
169 AGL
6 DBC
28 DELIs this possible ? What do I need to change in my select clause
for this?
Please helpmonalalwani, do you mean something like this?
you have -
1 select count(*) as counter, deptno
2 from emp
3* group by deptno
UT1 > /
COUNTER DEPTNO
5 10
5 20
6 30
-- but want counter = 0 for dept 0
UT1 > select count(*) as counter, deptno
2 from emp
3 group by deptno
4 union
5 select 0, 00
6 from dual
7 /
COUNTER DEPTNO
0 0
5 10
5 20
6 30
HTH -- Mark D Powell -- -
One can create an index on a non-existent column in a table
I am using Oracle 10.2.0.3 on Windows 2003. I wanted to create an index on columnb of
Tablea. When I use statement like:
Create index index1 on tablea (‘columnb’) …
Oracle created index: index1. However, when I looked tat the column in user_ind_columns it had some weird colculn like SYS_NCxxxx. For sometime, I had
No idea what was going on. My index was not being used in queries at all. Then it dawned on me that I should not put single quotes around columnb. Once I removed quotes, things worked as expected.
But why does Oracle allow index on a non-existent column?we cannot create the index on nonexistent column of table We can. Its called a function-based index. Here's how we do it.
Also read Howard's reply, right above yours.
SQL> desc t
Name Null? Type
OWNER NOT NULL VARCHAR2(30)
OBJECT_NAME NOT NULL VARCHAR2(30)
SUBOBJECT_NAME VARCHAR2(30)
OBJECT_ID NOT NULL NUMBER
DATA_OBJECT_ID NUMBER
OBJECT_TYPE VARCHAR2(19)
CREATED NOT NULL DATE
LAST_DDL_TIME NOT NULL DATE
TIMESTAMP VARCHAR2(19)
STATUS VARCHAR2(7)
TEMPORARY VARCHAR2(1)
GENERATED VARCHAR2(1)
SECONDARY VARCHAR2(1)
SQL> create index t_idx on t( substr(object_name, 1, 5));
Index created.
SQL> select column_name from user_ind_columns where index_name = 'T_IDX';
COLUMN_NAME
SYS_NC00014$
SQL> select index_type from user_indexes where index_name = 'T_IDX';
INDEX_TYPE
FUNCTION-BASED NORMAL
SQL> -
Question about modifying the size of an existing column in a table
I am a new DBA. I am being asked to modify a column in an existing table that is populated with data. Our database is a 10g database, and the table name is Contacts. The column name is FName, and it is currently VARCHAR(10). It needs to be increased to VARCHAR(18). Would I use this statement: ALTER TABLE contacts MODIFY COLUMN FName VARCHAR(18)?
I thank everyone who helps me with this question in advance.Hello,
This is how you do it
ALTER TABLE A_ERROR_TABLE MODIFY(TEST VARCHAR2(18)); -- Example
ALTER TABLE contacts MODIFY ( FName VARCHAR2(18));Regards
Edited by: OrionNet on Apr 2, 2009 4:09 PM: Fixed typo -
OIM 9102 Schema - OSI_CHILD_OLD_VALUE column in OSI table
Hello,
OIM 9102 database schema has a table name called OSI which I think holds information about tasks.
There is a column in the OSI table called “OSI_CHILD_OLD_VALUE” (Blob type). Did anyone familiar with the content of this column? What information it contains and which use case will trigger the read on the this table column?
Thanks,Hello,
I want to decrypt this particular column (OSI_CHILD_OLD_VALUE) value (type: CLOB). So, basically i need CLOB to byte [] - note that decrpt methods is overloaded.
My program is working for type: String - it could decrypt other encrypted OIM database fields like USR_UDF_ENCRYPTED_CUSTOM_FIELD, CUSTOM FORM FIELDS, etc...
Snippet:
ResultSet rs = stmt.executeQuery(sql);
while(rs.next()){
Clob osiClob = rs.getClob("OSI_CHILD_OLD_VALUE");
long clobLength = osiClob.length();
// I tried with below clob data extraction methods
<extracted_value_using> = osiClob.getAsciiStream()/osiClob.getCharacterStream()/osiClob.getSubString();
byte[] decryptedVal = com.thortech.xl.crypto.tcCryptoUtil.decrypt(<extracted_value_using>,"DBSecretKey");
System.out.println("Decrypted Value -->" + decryptedVal);
Finding it pretty challenging as it is not working only for CLOB column. Any help will be appreciated.
Thanks, -
JDBC : Fatal Error: Column Doesn't exist error .
Hello all,
I am getting following error in a JDBC adapter monitoring :
Error when executing statement for table/stored proc. 'Purchase_Order' (structure 'STATEMENTNAME'): java.sql.SQLException: FATAL ERROR: Column 'Test' does not exist in table 'Purchase_Order'
But the thing is that, the table do have the 'Test' column and I can update this table using Update SQL statement. There are 8 columns in this table. XI can update all 7 columns except this 'Test' column.
Any idea why? I evern rename this column to something else and no luck.
Regards,
N.SSwamy,
Why dont you try to execute the SQL statement or the Stored procedure at the Database level? If it executes there then you can figure out in XI. If it dont execute there then you have to check the syntax for the query or the stored procedure.
Try this out once.......
---Satish -
Kodo.jdbc.MappingFactory Null Pointer Exception
Hi I got a problem with the kodoworkbench.
I'm trying to save the mapping information into the .jdo file.
So I set
kodo.jdbc.MappingFactory=metadata
in my kodo.properties.
When I try to save the mapping information I get the following exceptions:
Seems that a string value is missing anywhere but i don't now where ?
Thanks
WARN -- Exception raised of type ERROR: java.lang.NullPointerException
java.lang.NullPointerException
at
kodo.jdbc.meta.MetaDataMappingFactory.addExtensions(MetaDataMappingFactory.java:253)
at
kodo.jdbc.meta.MetaDataMappingFactory.addMappingExtensions(MetaDataMappingFactory.java:219)
at
kodo.jdbc.meta.MetaDataMappingFactory.storeMappings(MetaDataMappingFactory.java:162)
at
kodo.jdbc.ide.meta.repos.SavingMappingInfoRepository.save(SavingMappingInfoRepository.java:50)
at
kodo.jdbc.ide.meta.repos.IdeMappingRepository.save(IdeMappingRepository.java:259)
at
kodo.jdbc.ide.meta.editor.MappingInfoTracker.save(MappingInfoTracker.java:53)
at
kodo.jdbc.ide.meta.editor.MappingInfoTracker.save(MappingInfoTracker.java:47)
at kodo.jdbc.ide.meta.editor.MappingEditor.save(MappingEditor.java:161)
at kodo.jdbc.ide.meta.editor.EditingPane.save(EditingPane.java:225)
at kodo.jdbc.ide.meta.editor.EditingPane.access$100(EditingPane.java:24)
at
kodo.jdbc.ide.meta.editor.EditingPane$1.actionPerformed(EditingPane.java:84)
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
at javax.swing.AbstractButton.doClick(AbstractButton.java:269)
at
javax.swing.plaf.basic.BasicMenuItemUI$ClickAction.actionPerformed(BasicMenuItemUI.java:1073)
at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
at
javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(JMenuBar.java:658)
at
javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(JMenuBar.java:666)
at
javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(JMenuBar.java:666)
at javax.swing.JMenuBar.processKeyBinding(JMenuBar.java:642)
at javax.swing.KeyboardManager.fireBinding(KeyboardManager.java:253)
at
javax.swing.KeyboardManager.fireKeyboardAction(KeyboardManager.java:240)
at
javax.swing.JComponent.processKeyBindingsForAllComponents(JComponent.java:2515)
at javax.swing.JComponent.processKeyBindings(JComponent.java:2507)
at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
at java.awt.Component.processEvent(Component.java:4909)
at java.awt.Container.processEvent(Container.java:1569)
at java.awt.Component.dispatchEventImpl(Component.java:3615)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Component.dispatchEvent(Component.java:3477)
at
java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
at
java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
at
java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
at
java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
at
java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
at java.awt.Component.dispatchEventImpl(Component.java:3506)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Window.dispatchEventImpl(Window.java:1606)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)Hi,
No, if I use the file factory I do not get the errors.
Here is the mapping info from an exported .mapping file.
The exception raises when I change the tablename to STUDENT and then I try
to save it.
I stopped working with the workbench and started editing the .mapping by
hand, because I get several NullPointerException without helpful exception
messages.
Thanks
<?xml version="1.0" encoding="UTF-8"?>
<mapping>
<package name="xxx.jdo.business">
<class name="Student">
<jdbc-class-map type="base" table="STUDENT"/>
<jdbc-version-ind type="version-number" column="JDOVERSION"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASS"/>
<field name="hasTaken">
<jdbc-field-map type="blob" column="HASTAKEN"/>
</field>
<field name="xxx.jdo.business.Person.birthDate">
<jdbc-field-map type="value" column="BIRTHDATE"/>
</field>
<field name="xxx.jdo.business.Person.city">
<jdbc-field-map type="value" column="CITY"/>
</field>
<field name="xxx.jdo.business.Person.id">
<jdbc-field-map type="value" column="ID"/>
</field>
<field name="xxx.jdo.business.Person.kidNames">
<jdbc-field-map type="blob" column="KIDNAMES"/>
</field>
<field name="xxx.jdo.business.Person.location">
<jdbc-field-map type="one-one"
column.JDOID="LOCATION_JDOID"/>
</field>
<field name="xxx.jdo.business.Person.name">
<jdbc-field-map type="value" column="NAME0"/>
</field>
<field name="xxx.jdo.business.Person.picture">
<jdbc-field-map type="value" column="PICTURE"/>
</field>
<field name="xxx.jdo.business.Person.state">
<jdbc-field-map type="value" column="STATE"/>
</field>
<field name="xxx.jdo.business.Person.street">
<jdbc-field-map type="value" column="STREET"/>
</field>
<field name="xxx.jdo.business.Person.zipcode">
<jdbc-field-map type="value" column="ZIPCODE"/>
</field>
</class>
</package>
</mapping>
Marc Prud'hommeaux wrote:
Katze-
If you use the "file" mapping factory, do you get the same error? Also,
can you provide any details about the mappings you are trying to create
(e.g., what is the inheritance strategy, etc)?
In article <[email protected]>, katze felix wrote:
Hi I got a problem with the kodoworkbench.
I'm trying to save the mapping information into the .jdo file.
So I set
kodo.jdbc.MappingFactory=metadata
in my kodo.properties.
When I try to save the mapping information I get the following exceptions:
Seems that a string value is missing anywhere but i don't now where ?
Thanks
WARN -- Exception raised of type ERROR: java.lang.NullPointerException
java.lang.NullPointerException
at
kodo.jdbc.meta.MetaDataMappingFactory.addExtensions(MetaDataMappingFactory.java:253)
>>
at
kodo.jdbc.meta.MetaDataMappingFactory.addMappingExtensions(MetaDataMappingFactory.java:219)
>>
at
kodo.jdbc.meta.MetaDataMappingFactory.storeMappings(MetaDataMappingFactory.java:162)
>>
at
kodo.jdbc.ide.meta.repos.SavingMappingInfoRepository.save(SavingMappingInfoRepository.java:50)
>>
at
kodo.jdbc.ide.meta.repos.IdeMappingRepository.save(IdeMappingRepository.java:259)
>>
at
kodo.jdbc.ide.meta.editor.MappingInfoTracker.save(MappingInfoTracker.java:53)
>>
at
kodo.jdbc.ide.meta.editor.MappingInfoTracker.save(MappingInfoTracker.java:47)
>>
at kodo.jdbc.ide.meta.editor.MappingEditor.save(MappingEditor.java:161)
at kodo.jdbc.ide.meta.editor.EditingPane.save(EditingPane.java:225)
at kodo.jdbc.ide.meta.editor.EditingPane.access$100(EditingPane.java:24)
at
kodo.jdbc.ide.meta.editor.EditingPane$1.actionPerformed(EditingPane.java:84)
>>
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
>>
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
>>
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
at javax.swing.AbstractButton.doClick(AbstractButton.java:269)
at
javax.swing.plaf.basic.BasicMenuItemUI$ClickAction.actionPerformed(BasicMenuItemUI.java:1073)
>>
at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
at
javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(JMenuBar.java:658)
at
javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(JMenuBar.java:666)
at
javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(JMenuBar.java:666)
at javax.swing.JMenuBar.processKeyBinding(JMenuBar.java:642)
at javax.swing.KeyboardManager.fireBinding(KeyboardManager.java:253)
at
javax.swing.KeyboardManager.fireKeyboardAction(KeyboardManager.java:240)
at
javax.swing.JComponent.processKeyBindingsForAllComponents(JComponent.java:2515)
>>
at javax.swing.JComponent.processKeyBindings(JComponent.java:2507)
at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
at java.awt.Component.processEvent(Component.java:4909)
at java.awt.Container.processEvent(Container.java:1569)
at java.awt.Component.dispatchEventImpl(Component.java:3615)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Component.dispatchEvent(Component.java:3477)
at
java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
>>
at
java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
>>
at
java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
>>
at
java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
>>
at
java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
>>
at java.awt.Component.dispatchEventImpl(Component.java:3506)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Window.dispatchEventImpl(Window.java:1606)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
>>
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
>>
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Marc Prud'hommeaux
SolarMetric Inc. -
Kodo.jdbc.AutoIncrementConstraints doesn't seem to do anything
I have an app_user table and related entity with an auto-increment
primary key (on MySQL), and a user_role table and related entity with a
FK pointing to the user PK. Both entities are using application
identity. The problem is that the user_role record is written out with a
null value for the FK pointing to the app_user table.
I've set
kodo.jdbc.AutoIncrementConstraints: true
both in the kodo.properties file used for enhancing, and in the
properties use for runtime user (which are fed to JDBCConfigurationImpl
via the fromProperties() method). However, the flag simply seems to do
nothing whether it's set or not...
The user is first created, then the role is added, then either calling
makePersistent or attachCopy has exactly the same effect, the user and
the role are written out, but the role has a null fk... Right now
there's no not-null constraint on the fk, but I believe it would be
triggered if ti existed.
Can anybody confirm that this should work ok?
package.jdo:
<class name="User" objectid-class="com.xxx.dexter.slice.dao.id.UserId">
<extension vendor-name="kodo" key="detachable" value="true"/>
<field name="id" primary-key="true">
</field>
<field name="roles">
<collection element-type="UserRole"/>
<!-- delete all userroles when the user is deleted -->
<extension vendor-name="kodo" key="element-dependent"
value="true"/>
<!-- specify the field that owns this two-sided relation -->
<extension vendor-name="kodo" key="inverse-owner" value="user"/>
</field>
</class>
<class name="UserRole"
objectid-class="com.xxx.dexter.slice.dao.id.UserRoleId">
<extension vendor-name="kodo" key="detachable" value="true"/>
<field name="id" primary-key="true">
</field>
<field name="user">
</field>
</class>
package.mapping:
<class name="User">
<jdbc-class-map type="base" table="app_user"/>
<field name="id" primary-key="true">
<jdbc-field-map type="value" column="user_id"/>
</field>
<field name="roles">
<jdbc-field-map type="one-many" table="user_role"
ref-column.user_id="user_id"/>
</field>
</class>
<class name="UserRole">
<jdbc-class-map type="base" table="user_role"/>
<field name="id" primary-key="true">
<jdbc-field-map type="value" column="id"/>
</field>
<field name="user">
<jdbc-field-map type="one-one" column.user_id="user_id"/>
</field>
</class>
Regards,
ColinPlease ignore the message below. While I was properly using the
jdbc-auto-increment vendor extension for some other tables, it was
somehow left out on these two. Adding it resolved the problem.
Colin Sampaleanu wrote:
I have an app_user table and related entity with an auto-increment
primary key (on MySQL), and a user_role table and related entity with a
FK pointing to the user PK. Both entities are using application
identity. The problem is that the user_role record is written out with a
null value for the FK pointing to the app_user table.
I've set
kodo.jdbc.AutoIncrementConstraints: true
both in the kodo.properties file used for enhancing, and in the
properties use for runtime user (which are fed to JDBCConfigurationImpl
via the fromProperties() method). However, the flag simply seems to do
nothing whether it's set or not...
The user is first created, then the role is added, then either calling
makePersistent or attachCopy has exactly the same effect, the user and
the role are written out, but the role has a null fk... Right now
there's no not-null constraint on the fk, but I believe it would be
triggered if ti existed.
Can anybody confirm that this should work ok?
package.jdo:
<class name="User" objectid-class="com.xxx.dexter.slice.dao.id.UserId">
<extension vendor-name="kodo" key="detachable" value="true"/>
<field name="id" primary-key="true">
</field>
<field name="roles">
<collection element-type="UserRole"/>
<!-- delete all userroles when the user is deleted -->
<extension vendor-name="kodo" key="element-dependent"
value="true"/>
<!-- specify the field that owns this two-sided relation -->
<extension vendor-name="kodo" key="inverse-owner" value="user"/>
</field>
</class>
<class name="UserRole"
objectid-class="com.xxx.dexter.slice.dao.id.UserRoleId">
<extension vendor-name="kodo" key="detachable" value="true"/>
<field name="id" primary-key="true">
</field>
<field name="user">
</field>
</class>
package.mapping:
<class name="User">
<jdbc-class-map type="base" table="app_user"/>
<field name="id" primary-key="true">
<jdbc-field-map type="value" column="user_id"/>
</field>
<field name="roles">
<jdbc-field-map type="one-many" table="user_role"
ref-column.user_id="user_id"/>
</field>
</class>
<class name="UserRole">
<jdbc-class-map type="base" table="user_role"/>
<field name="id" primary-key="true">
<jdbc-field-map type="value" column="id"/>
</field>
<field name="user">
<jdbc-field-map type="one-one" column.user_id="user_id"/>
</field>
</class>
Regards,
Colin -
Kodo.jdbc.meta.MappingInfoNotFoundException:
Hi,
I am getting following error when iam executing my application.
kodo.jdbc.meta.MappingInfoNotFoundException: The "column"
attribute/extension for field
"com.ejgallo.winemanager.domain.impl.equipment.SiteBoImpl._bottling" names
a column whose type (VARCHAR) is not compatible with the type of the field
(BIT).
[5/4/04 13:15:19:274 GMT+05:30] 6c594c92 SystemErr R at
kodo.jdbc.meta.Mappings.invalidMapping(Mappings.java:94)
[5/4/04 13:15:19:274 GMT+05:30] 6c594c92 SystemErr R at
kodo.jdbc.meta.ColumnFieldMapping.fromMappingInfo(ColumnFieldMapping.java:116)
[5/4/04 13:15:19:274 GMT+05:30] 6c594c92 SystemErr R at
kodo.jdbc.meta.ValueFieldMapping.fromMappingInfo(ValueFieldMapping.java:55)
In equipment.jdo mapping is like this
<class name="SiteBoImpl" identity-type="datastore">
<extension vendor-name="kodo" key="table" value="EJGALLO.WMGMT01_SITE"
/>
<extension vendor-name="kodo" key="pk-column" value="SYS_I" />
<extension vendor-name="kodo" key="jdbc-sequence-name"
value="EJGALLO.SITE_SYS_SEQ_N"/>
<extension vendor-name="kodo" key="class-column" value="none" />
<extension vendor-name="kodo" key="lock-column" value="none" />
<field name="_active"/>
<field name="_bottling"/>
<field name="_brandy"/>
<field name="_breweryType"/>
<field name="_changeDate"/>
<field name="_crush"/>
<field name="_description"/>
<field name="_galloOperation"/>
<field name="_galloOwned"/>
<field name="_jdeAddressBookNum"/>
<field name="_limsTestPrefixCode"/>
<field name="_name"/>
<field name="_posting"/>
<field name="_production"/>
<field name="_reorg"/>
<field name="_test"/>
<field name="_transfer"/>
<field name="_userId"/>
</class>
And field mapping in equipment.mapping is
<class name="SiteBoImpl">
<jdbc-class-map type="base" pk-column="SYS_I"
table="EJGALLO.WMGMT01_SITE"/>
<field name="_changeDate">
<jdbc-field-map type="value" column="CHG_S"/>
</field>
<field name="_description">
<jdbc-field-map type="value" column="SITE_D"/>
</field>
<field name="_name">
<jdbc-field-map type="value" column="SITE_N"/>
</field>
<field name="_active">
<jdbc-field-map type="value" column="STAT_X"/>
</field>
<field name="_bottling">
<jdbc-field-map type="value" column="BTL_CAT_X"/>
</field>
<field name="_brandy">
<jdbc-field-map type="value" column="BRANDY_CAT_X"/>
</field>
<field name="_breweryType">
<jdbc-field-map type="value" column="BREWERY_TYP_I"/>
</field>
<field name="_crush">
<jdbc-field-map type="value" column="CRUSH_CAT_X"/>
</field>
<field name="_galloOperation">
<jdbc-field-map type="value" column="GALLO_OPER_CAT_X"/>
</field>
<field name="_galloOwned">
<jdbc-field-map type="value" column="GALLO_OWN_CAT_X"/>
</field>
<field name="_jdeAddressBookNum">
<jdbc-field-map type="value" column="JDE_ADDR_BOOK_I"/>
</field>
<field name="_limsTestPrefixCode">
<jdbc-field-map type="value" column="LIMS_TEST_PRE_I"/>
</field>
<field name="_posting">
<jdbc-field-map type="value" column="POST_CAT_X"/>
</field>
<field name="_production">
<jdbc-field-map type="value" column="PROD_CAT_X"/>
</field>
<field name="_reorg">
<jdbc-field-map type="value" column="REORG_CAT_X"/>
</field>
<field name="_test">
<jdbc-field-map type="value" column="TEST_CAT_X"/>
</field>
<field name="_transfer">
<jdbc-field-map type="value" column="XFER_CAT_X"/>
</field>
<field name="_userId">
<jdbc-field-map type="value" column="USR_I"/>
</field>
</class>
So can anybody help me on this why i a getting this error.Booleans cannot by default be stored as varchars. You have to implemnt
your own ColumnFieldMapping which does the transformation for you (since
Kodo does not know if it should be Y/N, T/F, or something else altogether)
Atul wrote:
Hi,
I am getting following error when iam executing my application.
kodo.jdbc.meta.MappingInfoNotFoundException: The "column"
attribute/extension for field
"com.ejgallo.winemanager.domain.impl.equipment.SiteBoImpl._bottling" names
a column whose type (VARCHAR) is not compatible with the type of the field
(BIT).
[5/4/04 13:15:19:274 GMT+05:30] 6c594c92 SystemErr R at
kodo.jdbc.meta.Mappings.invalidMapping(Mappings.java:94)
[5/4/04 13:15:19:274 GMT+05:30] 6c594c92 SystemErr R at
kodo.jdbc.meta.ColumnFieldMapping.fromMappingInfo(ColumnFieldMapping.java:116)
[5/4/04 13:15:19:274 GMT+05:30] 6c594c92 SystemErr R at
kodo.jdbc.meta.ValueFieldMapping.fromMappingInfo(ValueFieldMapping.java:55)
In equipment.jdo mapping is like this
<class name="SiteBoImpl" identity-type="datastore">
<extension vendor-name="kodo" key="table" value="EJGALLO.WMGMT01_SITE"
/>
<extension vendor-name="kodo" key="pk-column" value="SYS_I" />
<extension vendor-name="kodo" key="jdbc-sequence-name"
value="EJGALLO.SITE_SYS_SEQ_N"/>
<extension vendor-name="kodo" key="class-column" value="none" />
<extension vendor-name="kodo" key="lock-column" value="none" />
<field name="_active"/>
<field name="_bottling"/>
<field name="_brandy"/>
<field name="_breweryType"/>
<field name="_changeDate"/>
<field name="_crush"/>
<field name="_description"/>
<field name="_galloOperation"/>
<field name="_galloOwned"/>
<field name="_jdeAddressBookNum"/>
<field name="_limsTestPrefixCode"/>
<field name="_name"/>
<field name="_posting"/>
<field name="_production"/>
<field name="_reorg"/>
<field name="_test"/>
<field name="_transfer"/>
<field name="_userId"/>
</class>
And field mapping in equipment.mapping is
<class name="SiteBoImpl">
<jdbc-class-map type="base" pk-column="SYS_I"
table="EJGALLO.WMGMT01_SITE"/>
<field name="_changeDate">
<jdbc-field-map type="value" column="CHG_S"/>
</field>
<field name="_description">
<jdbc-field-map type="value" column="SITE_D"/>
</field>
<field name="_name">
<jdbc-field-map type="value" column="SITE_N"/>
</field>
<field name="_active">
<jdbc-field-map type="value" column="STAT_X"/>
</field>
<field name="_bottling">
<jdbc-field-map type="value" column="BTL_CAT_X"/>
</field>
<field name="_brandy">
<jdbc-field-map type="value" column="BRANDY_CAT_X"/>
</field>
<field name="_breweryType">
<jdbc-field-map type="value" column="BREWERY_TYP_I"/>
</field>
<field name="_crush">
<jdbc-field-map type="value" column="CRUSH_CAT_X"/>
</field>
<field name="_galloOperation">
<jdbc-field-map type="value" column="GALLO_OPER_CAT_X"/>
</field>
<field name="_galloOwned">
<jdbc-field-map type="value" column="GALLO_OWN_CAT_X"/>
</field>
<field name="_jdeAddressBookNum">
<jdbc-field-map type="value" column="JDE_ADDR_BOOK_I"/>
</field>
<field name="_limsTestPrefixCode">
<jdbc-field-map type="value" column="LIMS_TEST_PRE_I"/>
</field>
<field name="_posting">
<jdbc-field-map type="value" column="POST_CAT_X"/>
</field>
<field name="_production">
<jdbc-field-map type="value" column="PROD_CAT_X"/>
</field>
<field name="_reorg">
<jdbc-field-map type="value" column="REORG_CAT_X"/>
</field>
<field name="_test">
<jdbc-field-map type="value" column="TEST_CAT_X"/>
</field>
<field name="_transfer">
<jdbc-field-map type="value" column="XFER_CAT_X"/>
</field>
<field name="_userId">
<jdbc-field-map type="value" column="USR_I"/>
</field>
</class>
So can anybody help me on this why i a getting this error.
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com -
Populate data to column frm existing column
Hi,
I need to have 3 more columns and populate data from existing column rows.
For example
I want to have new columns based on int_bckt_1, char-bckt-2 and char_bckt_3
int_bckt_1= raw score
char_bckt_2= Pref
int_bckt_2= Scaled score
Raw score, pref and sacled score columns are new.
The data is populated based on these columns int_bckt_1, char_bckt_2,int_bckt_2
The rule is - i need to populate the data based on sub test id and char-bckt_2. we need to consider sub test id=200
for english
sub test id=200 and char_back_2 =T and subject is english then i need to populate data for all subtestid 500 and subject =english
similar for Perf and Raw score
For Math
sub test id=200 and char_back_2 =T and subject is Math then i need to populate data for all subtestid 500 and subject =Math
i want to do samething for char_bckt_2 =TR too.
I herewith attached my excel sheet for more clear
Raw score, Pref, Scaled score these column is not there in the table i need to have and populate data based on rule
Could you please help me.
Thanks
RamAnother interpretation:
OK, 3 new columns, so they're all null and you want to populate them and your last reply is your desired output.
If that's correct you can use CASE:
SQL> select * from t;
STUD INT_BCKT_1 CHAR_BCK INT_BCKT_2 CHAR_BC SUBJECT SUBTESTID SCALE A_RAW PR
John 38 T 226 NI English 200
John 16 T 218 WF Math 200
John 82 reading 167 poetry English 500
John 82 Language 166 formal English 500
John 83 number 170 compu Math 500
John 83 geometry 172 spatial Math 500
6 rows selected.
SQL>
SQL> update t
2 set scale = case when subject = 'English'
3 then (select int_bckt_2 from t where subject = 'English' and subtestid = 200)
4 when subject = 'Math'
5 then (select int_bckt_2 from t where subject = 'Math' and subtestid = 200)
6 end
7 , a_raw = case when subject = 'English'
8 then (select int_bckt_1 from t where subject = 'English' and subtestid = 200)
9 when subject = 'Math'
10 then (select int_bckt_1 from t where subject = 'Math' and subtestid = 200)
11 end
12 , pref = case when subject = 'English'
13 then (select char_bckt_3 from t where subject = 'English' and subtestid = 200)
14 when subject = 'Math'
15 then (select char_bckt_3 from t where subject = 'Math' and subtestid = 200)
16 end;
6 rows updated.
SQL>
SQL>
SQL> select * from t;
STUD INT_BCKT_1 CHAR_BCK INT_BCKT_2 CHAR_BC SUBJECT SUBTESTID SCALE A_RAW PR
John 38 T 226 NI English 200 226 38 NI
John 16 T 218 WF Math 200 218 16 WF
John 82 reading 167 poetry English 500 226 38 NI
John 82 Language 166 formal English 500 226 38 NI
John 83 number 170 compu Math 500 218 16 WF
John 83 geometry 172 spatial Math 500 218 16 WF
6 rows selected. -
Warning: Index does not exist in database system MSSQL
Hi,
After activating the Index from SE11,
I receive the following Warning:
Index does not exist in database system MSSQL.
What does this mean? Has performance been increased or does the index 1st have to exist in the database system MSSQL?When you create index at SE11 and you need activate database utility.
utilitities-database utility->then click activate and adjust database.
else you can use SE14 and so that Index will create databse level.
Reward Points if it is helpful
Thanks
Seshu -
Query to add a column in between existing cols of a table?
HI All,
I have two questions.
1. Query to add a column in between existing cols of a table? (not at the end. This is view of an order of output fields in a report)
2. How do I swap the contents of two columns in a table. Suppose in a table tab there are 2 cols , col1,col2 populated with some data.
I need a query(probably) to swap the col1 and col2 values . NOT AS A RESULT SET, BUT IT NEEDS TO GET CHANGED IN THE TABLE.
Please help !> 1. Query to add a column in between existing cols of
a table? (not at the end. This is view of an order of
output fields in a report)
Not really sensible ito DBMS - it does not care how you want to view the data. The sequence and formats of columns are what you/the application need to specify in the SQL's projection clause.
Also keep in mind to achieve this, the DBMS will need to rewrite the entire table to fit this new column in-between existing columns. This is not the best of ideas.
The projection of rows is dealt with SQL statements - not with the physical storage implementation.
> 2. How do I swap the contents of two columns in a
table. Suppose in a table tab there are 2 cols ,
col1,col2 populated with some data.
I need a query(probably) to swap the col1 and col2
values . NOT AS A RESULT SET, BUT IT NEEDS TO GET
CHANGED IN THE TABLE.
This seems to work:
SQL> create table foo_tab( c1 varchar2(10), c2 varchar2(10) );
Table created.
SQL> insert into foo_tab select TO_CHAR(rownum), TO_CHAR(object_id) from user_objects where rownum < 11;
10 rows created.
SQL> commit;
Commit complete.
SQL> select * from foo_tab;
C1 C2
1 55816
2 55817
3 55818
4 55721
5 105357
6 105358
7 105359
8 105360
9 105361
10 60222
10 rows selected.
SQL> update foo_tab set c1=c2, c2=c1;
10 rows updated.
SQL> select * from foo_tab;
C1 C2
55816 1
55817 2
55818 3
55721 4
105357 5
105358 6
105359 7
105360 8
105361 9
60222 10
10 rows selected.
SQL> -
The column in the table do not match an existing primary key
I've got two tables tbl_Workshop and tbl_Material
tbl_Workshop has columns workshopID, workshopTitle, materialID
tbl_Material has materialID, name, workshopTitle
when I'm trying to create a relationship between the workshopTitle of tbl1 and tbl2, it gives me an error that says the column in the table do not match an existing primary key.
What could be the reason for this error and how to overcome it.
ps. The datatypes and names of both the table's column match.Have you created primary key on workshopTitle column in tbl_Workshop
You can add foreign key relationship from tbl_Material.workshopTitle
to tbl_Workshop.workshopTitle
only if latter is a primary key of the table.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs -
OBIEE 11.1.1..6.9 Logical Column Derived from existing columns
Hello,
I've just installed the last version 11.1.1.6.9 in my test environment and I already have a problem with the RPD.
I've some logical column derived from existing columns using an expression. (so far, so good)
With Adminsitration Tool (Last Version 11.1.1.6.9), when I launch the Consistency Check Manager I have the following error (I use the SampleAppLite RPD in order to reproduce the problem)
ERRORS:
SampleApp Lite :
[nQSError: 46008] Internal error: File server\objectmodel\Src\SOSecureRpGateway.cpp, line 479.
[nQSError: 23013] An error occurred when extracting the metadata definition for the Attribute '"SampleApp Lite"."D3 Orders (Facts Attributes)"."test"'.
The logical column test on "D3 Orders (Facts Attributes)" :
CASE WHEN "SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date" > "SampleApp Lite"."D0 Time"."Calendar Date" THEN 1 ELSE 0 END
The problem appears only when I use multiple source table in column expression.
Does anyone has the same problem ? I think it's easy to reproduce (I searched on OracleSupport but I didn't find anything yet)
BenjaminI know that there is no relation between "SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date", "SampleApp Lite"."D0 Time"."Calendar Date", it's also the same thing in my own RPD.
But as it's working with the 11.1.1.6.2 BP1 version I don't understand why it's not working with 11.1.1.6.9.
Implicit fact column is not set on my repository, but I don't have any request with only dimensional column, so if my understanding is correct I don't need to use it. Also, the problem appears during the check of the repository not in answers.
thanks anyway -
Add a New Column Before An Existing Column in 10g.
Hi all,
I Want to add column in a table ,before an existing column in Oracle 10G database.
table A:
id number,
name varchar,
job varchar,
status char.
i want to add a column before "JOB".
I.E) USING AFTER OR BEFORE IN ALTER TABLE SYNTAX.887268 wrote:
Hi all,
I Want to add column in a table ,before an existing column in Oracle 10G database.
table A:
id number,
name varchar,
job varchar,
status char.
i want to add a column before "JOB".
I.E) USING AFTER OR BEFORE IN ALTER TABLE SYNTAX.There's no such option, and to be honest there's no real need to do it as Oracle doesn't care what order the columns are in, and you can select out the columns in your queries in whatever order you want. You could use the DBMS_REDEFINITION package (http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_redefi.htm) but unless you're really struggling then that's perhaps a little bit over the top. The simplest way if you really feel you need to do it is to create a new table based on the existing one with your new column in it and selecting the data into it at the same time...
create newtable as
select id, name, cast(null as varchar2(10)) as newcolumn, job, status from tableA;and then drop the original table and rename the new one...
drop table tableA;
rename newtable to tableA;of course you would need to recreate any constraints, indexes, triggers etc., and it could be problematic if you have foreign keys etc. but you have to weigh up what you are wanting to do and why you really need to put a new column in the middle of other columns rather than just putting it on the end.
Maybe you are looking for
-
Error -50...ipod acting strangely...help needed as soon as possible
my dad had bought a second generation i pod shuffle frm tokyo about a month bak.i has bn workin absolutely fine for a month,but now a problem has sprouted.wenever i connect my ipod to the pc,a new drivein "my computer" appears called "my ipod G:".aft
-
Opening New Browser window for click event on an image
hi all, I want someone to help me out solving the problem of opening a new browser window on the mouse click event of an image or a button etc.... The new window would contain the datagrid details from the main window, but in an expanded form. If at
-
Disk util in recovery mode shows invalid disks - fixing merges the disks to a single LVG
Seems another day, another interesting issue in Mac OS which has me stumped a little bit. Background: My setup is the laster Mac Mini server, I have upgraded the root disk to a 256GB SSD and moved the ordered 1TB magnetic drive to the secondary disk.
-
How to insert unicode characters in oracle
hiiii...........i want to add special unicode characters in oracle database......can anyone guide me how to do this. i kno we have nvarchar2 datatype which supports multilingual languages......but im enable to insert the values from sql prompt.......
-
Import data into XMLType tables
I have a document whose root node is MedlineCitationSet. It contains one or more MedlineCitations i.e <MedlineCitationSet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://localhost/schema/medline.xsd"> <Medl