AWM mapping : "SCHEMA.TABLE_NAME.COLUMN" invalid
Hi,
I have Views in my database that I use as dimensions .
In AWM, I create dimensions, I try to map with my views ... And I get the following error :
*"SCHEMA.TABLE_NAME.COLUMN" invalid*
I chekked the database, everything seems to be okey ! And I can't find a clue
Any Idea ? Thanks all !
Are you able to query from the database View without the error, and as the same login you use in AWM? Is the View valid/compiled?
Edited by: Dave O on Dec 18, 2012 4:59 PM
Similar Messages
-
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 tablAny 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 -
How to create a dynamic form with bind variables :schema & :table_name
My application has two LOV's, one to select a schema, and the next to select a table within that schema. I then have a button which passes me to a report which displays the data in that table.schema.
I now want to create a link to a form where I can edit the record based on the rowid of that table.schema, but it doesn't appear that I can create a dynamic form where I pass the schema.table_name and rowid. Is this possible? Can anyone advise how I can do this? The form builder only wants a fixed schema/table name.
Thanks in advance.
Stuart.Hi Stuart,
In this sort of situation, you will need to be a bit creative.
I would suggest a pipeline function called as if it was a report.
Then you can pipe out the required fields.
Since you will have a variable number of fields, you could use two of the multi row field names for your field names and values.
Then after submit, you can create your own procedure to loop through the fields (stored for you in the Apex package) and update the table as required.
Not very specific I'm afraid, but it should work.
Regards
Michael -
Partition Map Schemes: HFS+ and FAT32 partitions with OSX and Windows
OK so I know this question has been practically beaten to death, but I keep finding conflicting information. I am using a 2011 MacBook Pro, on which I will set up Windows through Boot Camp. I recently purchased a 750 GB WD external hard drive to use with time machine for a backup on my Mac. However, I also need to be able to use part of this for Windows files. SO.. I intend to use the HFS+ partition for the the Mac (500GB) and create a FAT 32 partition (250GB) to use for backing up windows files (using it for solely computer modeling and need to be able to transfer/share files with Mac users who use Parallels as well as copying to PC desktops). My question is what to use as the partition map scheme. I have heard that when using these two partition types, a Master Boot Record is needed (so Windows can recognize the FAT32 partition) and also that a GUID partition map is required for use with time machine, meaning windows would no longer be able to read the FAT32 partition. Is there a way to reconcile this? Either using Time Machine with HFS+ partition that is set to MBR or uisng FAT32 on Windows with a GUID partition map? Also if I were to use Parallels (with a GUID setup) instead of Boot Camp, could that be the way to save the windows files to the FAT32 Partition and avoid problems with Time Machine not working with MBR? Thanks for any expertise, as I have heard that both setups that I have mentioned both will work and both will not work. Any experience with a similar situation?
Wow. Thanks for the extremely quick responses. Just for a few points of clarification.. I'm a complete newb at backing up strategies.
Steve, you would recommend to not backup files from my Mac OSX and files from Windows (also on my Mac) on the same drive, correct?
I appreciate the strategy of using it only as a backup, that makes quite a bit of sense. However, if I want to only backup my OSX files, and also store (solely as backup copies) say, a number of computer models (Rhino, Revit, etc.) that were created in Windows programs (not needing to store the entire Windows disk), would it not make sense to store these on the same drive in a different partition, creating the need for two different partition formats? And if I were to do this, maybe I should use NTFS instead of FAT32 (and reformat to GUID since that seems to be a standard for Apple and Windows 7 recognizes it..?) to keep them completely separate since the computer model files cannot be opened unless running the Windows programs.
How do you use your drive with HFS+ and NTFS if not for backups? I will not need to access the HFS+ backup files in Windows, nor need to access files from an NTFS partition in OSX, so that seems to simplify things in that, at least at the moment, I will not need any Paragon software.
Currently my drive is partitioned as HFS+ and FAT32 as MBR, with the HFS+ partition set up with Time Machine. It appears to be successful, I see my files in Mac HD -> "users" and all my docs, desktop items, etc. are listed. Seems that there is in fact no limit on TM's use of MBR maps, or else it is way above 160GB.
Third, are you using CarbonCopyClone in place of Time Machine or in addition to it? If in addition would it create the bit-wise clone on the same HFS+ partition as TM is backing up to? Or a separate drive? I'd like to only have one external that I am backing up to for simplicity's sake. I've never used TM before, so this is all new to me. Also, I suppose I have been missing the distinction between storing copies of files, and making a complete backup of a disk image... just now realizing the difference. Thanks so much. -
2 Different Partition Map Scheme's for one external hard drive
Is it possible to have one external hard drive with 2 different Partition Map Scheme's?
One of them will be used to externally boot tiger on a powerpc, and the other for use on my macbook pro?And this drive is currently not partitioned I take it ?
You need to make a backup of the data on the drive then partition it, the first partition must be set under Disc Utility / Partition / Options as Mac GUI Bootable so it installs the drivers, then install Tiger onto the first partition and move your current data back onto the second one.
You will then be able to Boot Tiger on the older PowerBook by holding down 'option' at start up, if you just have it connected to the MacBook Pro and start up normally then it will appear as two volumes on your Desktop, the Tiger Boot Volume and your Data Volume. -
Row to column mapping and combining columns
Hi
I have one issue i want to concatenating some columns and map row as columns like below.I am giving one ex and have more than 1000 employees like this
Example
{Srno Eno Ename job datestart}
{1 01 jack------clerk------01-Jan-2008}
{ 2 01 jack-----snrclerk----01-Jun-2009}
{ 3 01 jack ---- officer------- 01-Jan-2010}
I want to display the row to columan mapping like first row concatenated as col2 and second row for col2 column etc
{eMpno------- col1 ------------------co12----------------------------------col3}
{0101 jackclerk 01-Jan-2008---jacksnrclerk01-Jun-2009------01jackofficer01-Jan-2010}
rgds
ramya
Edited by: user11243021 on Sep 7, 2010 5:21 AMwith t as (
select 1 srno,'01' eno,'jack' ename,'clerk' job,to_date('01-Jan-2008','dd-mon-yyyy') datestart from dual union all
select 2 srno,'01' eno,'jack' ename,'snrclerk' job,to_date('01-Jun-2009','dd-mon-yyyy') datestart from dual union all
select 3 srno,'01' eno,'jack' ename,'officer' job,to_date('01-Jan-2010','dd-mon-yyyy') datestart from dual
) -- end of data sample
select eno,
max(
case srno
when 1 then ename || ' ' || job || to_char(datestart,' dd-Mon-yyyy')
end
) col1,
max(
case srno
when 2 then ename || ' ' || job || to_char(datestart,' dd-Mon-yyyy')
end
) col2,
max(
case srno
when 3 then ename || ' ' || job || to_char(datestart,' dd-Mon-yyyy')
end
) col3
from t
group by eno
EN COL1 COL2 COL3
01 jack clerk 01-Jan-2008 jack snrclerk 01-Jun-2009 jack officer 01-Jan-2010
SQL> SY. -
Finding exception with the read-write-backing-map-scheme configuration.
Finding exception with the <read-write-backing-map-scheme> configuration, that is setup against a simple database cache store implementation. The class SimpleCacheEventStoreImpl implements CacheStore interface.
Exception in thread "main" java.lang.UnsupportedOperationException: configureCache: read-write-backing-map-scheme
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:995)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:277)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:689)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:667)
at Sample.SimpleEventStoreConsumer.main(SimpleEventStoreConsumer.java:10)
The cache store is interfaced to the program SimpleEventStoreConsumer(where I have a put and get operation) through the following cache configuration descriptor. On running the SimpleEventStoreConsumer, the exception happens on trying to get the Named cache from the cache factory
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>Evt*</cache-name>
<scheme-name>SampleDatabaseScheme</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<read-write-backing-map-scheme>
<scheme-name>SampleDatabaseScheme</scheme-name>
<internal-cache-scheme>
<local-scheme>
<scheme-ref>SampleMemoryScheme</scheme-ref>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>com.emc.srm.cachestore.SimpleCacheEventStoreImpl</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>{cache-name}</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
</read-write-backing-map-scheme>
<local-scheme>
<scheme-name>SampleMemoryScheme</scheme-name>
</local-scheme>
</caching-schemes>
</cache-config>you are missing <backing-map-scheme>. Do like following:
<caching-schemes>
<distributed-scheme>
<scheme-name>distributed-scheme</scheme-name>
<service-name>DistributedQueryCache</service-name>
<backing-map-scheme>
<read-write-backing-map-scheme>
<scheme-ref>rw-bm</scheme-ref>
</read-write-backing-map-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<read-write-backing-map-scheme>
<scheme-name>rw-bm</scheme-name>
<internal-cache-scheme>
<local-scheme>
</local-scheme>
</internal-cache-scheme>
</read-write-backing-map-scheme>
</caching-schemes> -
Unable to fetch columns; Invalid state/No Suitable Driver
Hi!
I'm trying to populate a combo box with data from a MySQL database (or any other database for that matter), I create a JDBC connection source, and set the following:
URL = jdbc:mysql://localhost:3306/test
Driver = org.mysql.jdbc.Driver (i have also tried org.gjt.mm.mysql.Driver)
Username = anonymous
Password = <blank>
Next I create a NBJdbcRowSet and set:
Command = SELECT * FROM foo
Connection Provider = connectionSource1 (the above connection source)
Now if I click the elipses next to Default Column Values, I get the message 'Unable to fetch columns; Invalid State'
If I replace the NBJDBCRowSet with a NBCachedRowSet, the error becomes 'Unable to fetch columns; No Suitable Driver'.
The database is browseable in the runtime tab, and the table exists (I can run SQL queries and get the expected results). The anonymous account exists and has access to the tables in question (the same setup is used in a few different applications, all of which work fine). Using the root account gives the same results. Using the PointBase example database gives the same results:
Driver: com.pointbase.jdbc.jdbcUniversalDriver
URL: jdbc:pointbase:server://localhost:9092/sample
Details of setup:
OS: Windows XP Pro SP2
IDE: Sun Java Studio Enterprise 7 2004Q4
Java version in use: 1.4.2_05 (as packaged with the studio)
MySQL: v5.0.7-beta-nt
Connector: MySQL Connector/J 3.0.17-ga
PointBase: As came with Studio Enterprise
I should mention that I can get DB connectivity in my app, I can create a comboBox and set the model to 'nBCachedRowSet1: name' and the contents of that field appears in my comboBox, however I need to create about a dozen tables and I don't relish the thought of manually creating models for each one ;)
Any suggestions are appreciated!
Cheers!
DarrenHi Thanks for your reply.
I've retried with PointBase and the Sample DB:
* New project. New JFrame.
* Create ConnectionSource, NBJdbcRowSet, ComboBox
* Config ConnectionSource:
- Driver: com.pointbase.jdbc.jdbcUniversalDriver
- URL: jdbc:pointbase:server://localhost:9092/sample
- Username/pass: as per PointBase setup
* Config NBJdbcRowSet
- ConnectionProvider: connectionSource1
- Command: SELECT * FROM CUSTOMERINFO
- Default Column Values: <open GUI>, <Fetch Columns>, "Unable to fetch columns; Invalid State"
So this is where I get the problem, I'm not sure if i've buggered it up though, so I continue to see if I can get data:
- Add Column: NAME
- OK, Close
* Config ComboBox
- Open Model dialog
- Select Mode: ComboBoxEditor
- RowSet: nBJdbcRowSet1 (this throws the error again)
- Column: NAME (entered manually, dropdown is empty)
- OK, Close
* Run app
Errors!
Seems like the GUI builder did something wrong - it generated a bunch of functions for each thing i added, like this:
public void setJComboBox1(JComboBox val) {
this.jComboBox1 = val;
and the project won't compile. I figure out it should be like this:
public void setJComboBox1(javax.swing.JComboBox val) {
this.jComboBox1 = val;
but the functions aren't doing anything anyway, so I delete them all. I'm starting to think my installation is borked.
Project now compiles and runs, but there's no data, and I get:
ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
At this point i should probably find the jar with that driver in it and mount this/add it to the classpath, but the boss has decided we'll use Borland Delphi 2005 .NET anyways, so I won't take this any further...
Thanks for your help guys!
Darren -
just bough OSX Mountain Lion, my laptop operating with v10.6.8. Can't install OSX Mountain Lion, on the disk selection screen i cant select the Macintosh HD to install OSX giving a message (This disk cannot be used to start up your computer).only have one disk to select and my partition map scheme is GUID partition table. 24.44gb disk available.
Verify your computer can run Mountain Lion:
Upgrading to Mountain Lion
To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
OS X Mountain Lion - System Requirements
Macs that can be upgraded to OS X Mountain Lion
1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
7. Xserve (Early 2009) - Model Identifier 3,1 or later
To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
Open Disk Utility and verify the drive is partitioned using GUID and formatted Mac OS Extended, Journaled. If it is then do this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Now try installing Mountain Lion. -
Why can't a backing-map-scheme be specified in caching-schemes?
Most other types of schemes except backing-map-scheme can be specified in the caching-schemes section of the cache configuration XML file and after that be reused in other scheme definitions. What is the motivation for excluding the backing-map-scheme?
/MagnusHi Magnus,
you can specify an "abstract" service-type scheme (e.g. distributed-scheme) containing the backing map scheme instead of the backing map scheme itself.
I know it is not as flexible as having a backing map scheme separately, but it is almost as good.
Best regards,
Robert -
Could you explain how the read-write-backing-map-scheme is configured in...
Could you explain how the read-write-backing-map-scheme is configured in the following example?
<backing-map-scheme>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<class-scheme>
<class-name>com.tangosol.util.ObservableHashMap</class-name>
</class-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>coherence.DBCacheStore</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>CATALOG</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
<read-only>false</read-only>
<write-delay-seconds>0</write-delay-seconds>
</read-write-backing-map-scheme>
</backing-map-scheme>
...Edited by: qkc on 30-Nov-2009 10:48Thank you very much for reply.
In the following example, the cachestore element is not specified in the <read-write-backing-map-scheme> section. Instead, a class-name ControllerBackingMap is designated. What is the result?
If ControllerBackingMap is a persistence entity, is the result same with that of cachestore-scheme?
<distributed-scheme>
<scheme-name>with-rw-bm</scheme-name>
<service-name>unlimited-partitioned</service-name>
<backing-map-scheme>
<read-write-backing-map-scheme>
<scheme-ref>base-rw-bm</scheme-ref>
</read-write-backing-map-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<read-write-backing-map-scheme>
<scheme-name>base-rw-bm</scheme-name>
<class-name>ControllerBackingMap</class-name>
<internal-cache-scheme>
<local-scheme/>
</internal-cache-scheme>
</read-write-backing-map-scheme> -
Behaviour of read-write-backing-map-scheme in combination with local-scheme
Hi,
I have the following questions related to the distributed cache defined below:
1. If I start putting unlimited number of entries to this cache, will I run out of memory or the local-scheme has some default size limit?
2. What is default eviction policy for the local-scheme?
<distributed-scheme>
<scheme-name>A</scheme-name>
<service-name>simple_service</service-name>
<backing-map-scheme>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<local-scheme></local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>SomeCacheStore</class-name>
</class-scheme>
</cachestore-scheme>
</read-write-backing-map-scheme>
</backing-map-scheme>
</distributed-scheme>
Best regards,
JarekHi,
The default value for expiry-delay is zero which implies no expiry.
http://wiki.tangosol.com/display/COH34UG/local-scheme
Thanks,
Tom -
Hi,
BizTalk WCF Custom Adapter - is send in a solicit response port. It works with a http address.
However, I need to point it to a Https location.
I imported the bindings, and changed the address to https. I was able to re-import the bindings. The send port gets started. But, when we try send a message via the send port, it throws an error:
Error Description: System.ArgumentException: The provided URI scheme 'https' is invalid; expected 'http'.
Parameter name: via
Any help is appreciated.
Regards,
SharmishthaThe error logs do not give any other information.
Also, security is TransportCredentialOnly, with Basic - Client Credential Type.
Regards,
Sharmishtha
Hi Sharmishtha,
TransportCredentialOnly mode
does not provide message integrity and confidentiality. It provides HTTP-based client authentication. You need to use either of the below security mode :
Transport
TransportWithMessageCredential
Rachit
Please mark as answer or vote as helpful if my reply does -
Backing Map Scheme with storage disabled
I've been playing around with Cache Servers and Cache Clients. If I have a distributed cache, the coherence-cache-config.xml for the client still requires a backing map scheme entry. If the client doesn't physically store data then why does it need a backing map scheme?
I'm interested to know if I'm understanding the concept of the cache client correctly.
Is Coherence just expecting to read in the XML but will ignore it because I've set local storage to false, and therefore it doesn't actually matter what is in the backing map sheme?
Cheers
MikeHi Mike,
You are right - storage disabled nodes do not instantiate backing map. Coherence reads XML during initial cohfiguration validation, and on cache clients 'backing-map-scheme' element is not used.
In general it is cleaner, less error prone and easier to maintain a single configuration file and let Coherence worry about what to instantiate on different nodes.
Regards,
Dimitri -
Formatting HDs to Mac OS Extended: Does Partition Map Scheme need altering as well?
Most people know that third party hard drives need reformatting to Mac OS Extended before use but nobody seems to mention the Partition Map Scheme which is somewhat hidden away in Disk Utility.
When reformatting a drive is it sufficient to just set it to Mac OS Extended or does the Partition Map Scheme need to be reset to GUID or another of the Apple ones? (I believe GUID has to be used if you want to make the drive bootable . . . but most of the time you don't).
What problems, if any, will arise if the PMS is not altered?I frequently use FAT for externals, and there are no problems. You are right that GUID is required for booting, but that's about it. If I recall correctly though, a GUID partition map is much more efficient, so whenever I can use it I do.
One thing to note is that Windows XP and prior versions of Windows do not like GUID, and any version of Windows, including current Windows 7, will only see the first partition on a GUID formatted drive.
Maybe you are looking for
-
How do i sync my iPhone with my itunes?
How do I sync my iPhone to my itunes? I already have an itunes set up with music from my ipod touch but when i plug in my iphone nothing happens.
-
Can I use a TIme Machine drive of my Macbook to transfer data to a new IMac
Hi everyone I currently have a 2.6GHz Intel Core 2 Duo Macbook Pro as my main machine, using System 10.6.4. I'm keen add a second computer which will allow me to run both systems at the same time. My day job is a music producer, so I have plenty of a
-
Your urgent help will be very much appreciated
I have a problem whenever I connect my database and need your urgent help. the sample source code is below import java.sql.*; import javax.swing.*; import java.awt.*; import java.awt.event.*; import java.util.*; public class Table extends JFrame priv
-
C++ Dynamic Library, iostream: No such file
Hi, I'm trying to build a dynamic library in Xcode and running into a compilation error finding iostream. The library code is written in C++ and compiles on linux. When compiling in Xcode (2.4.1), I created the project as a C++ Standard Dynamic Libra
-
Can't transfer files to wife's iPod
Got a new computer. No problem managing files with my iPod using iTunes, but I can't transfer files from Library onto my wife's iPod anymore. When I connect her iPod, iTunes DOES seem to recognize the iPod--it displays her iPod and allows me to delet