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
Similar Messages
-
Yet another question about setting the size of a JTextField
Hello,
yep, I already looked at the other posts & the API.
I have tried the following (& other code) to try to set the width of the display. Nothing works so far.
percent_CO2 = new JTextField();
percent_CO2.setColumns(8);
percent_CO2.setToolTipText("The % Carbon Dioxide relates to ...");
percent_CO2.setPreferredSize(new Dimension(10,20));
percent_CO2.setMaximumSize (new Dimension(10,20)); This is one of several JTextField's on a Jpanel defined as :
jcommonCharPanel.setLayout( new GridLayout(8, 2, 2, 4) );
//8 rows, 2 columns, vertical & horizontal gaps of 2 & 4Any ideas why it is so difficult to set the size of the JTextField?
Should I try to limit the size of the JPanel instead?
thanks,
-- HSC --http://forum.java.sun.com/thread.jsp?forum=54&thread=379656
-
Question about modifying the Packet-based link into ASK modulation
Hello everybody,
Recently I learned the Packet-based link and I modified it into ask scheme. But after I test the modified code, I find that it doesn't work as I image.
I don't know why, can anybody help me about it?
Thanks very much.
Attachments:
Packet-based Link(ASK).zip 445 KBI have a couple of questions that may seem silly, but...
USB A = Windows DaRT 7.0 x86 for Windows 8 ISO burned
USB B = Windows DaRT 7.0 x64 for Windows 8 ISO burned
Is this a typo? You have it correctly above that where you list all 4 DaRT images, but not in the section I quoted.
This TechNet article lists compatibility of DaRT versions:
DaRT 8.1 supports Windows 8.1 and Windows Server 2012 R2.
DaRT 8.0 supports Windows 8 and Windows Server 2012.
DaRT 7.0 supports Windows 7 and Windows Server 2008 R2.
DaRT 6.5 supports Windows 7 and Windows Server 2008 R2.
DaRT 6.0 supports Windows Vista and Windows Server 2008.
DaRT 5.0 supports Windows 2000, Windows XP, and Windows Server 2003.
Also, did you use a Windows 8 ISOs with both DaRT versions? You need Windows 7 disks to create the DaRT 7 recovery disk.
Let us know,
Thanks
David -
Hi! Question about setting default size when opening existing PDF's.
The pdf documents i download all seem to open up at 202% size. Is there a way to set my default size (for opening and reading documents) to something smaller, so I don't have to always use the magnifying tool to shrink them? Thanks!
Under Preferences | Page Display, set Zoom to 100% or whatever you would like to open it with.
-
Question about modifying the boot order for Lenovo Yoga
I created a bootable USB for crash recovery. How do I configure the Lenovo Yoga 2 Pro boot order so that it boots from USB first? Is there some function key I need to press while the laptop is booting up to get some kind of boot screen?
Solved!
Go to Solution.I had used the "Create a recovery drive" option. You find this tool by pressing the windows key and typing in recovery drive, and clicking on the Settings category. This launches the Create a recovery drive application. This tool apparently copies over the recovery partition from the hard drive. Thanks a lot for your help. I will try to press the button on top of the power button and see if I can set it up to boot from the recovery usb drive.
-
How to modify the size of the view which invoked presentModalViewController
the value of the modalPresentionSytle is UIModalPresentationFormSheet, after invoking the presentModalViewController, the new view will appear, but the size is fixed, so I want to modify the size, how can I do?
, thanks.
I sought the answer to this question from developer who has several years dev experience for iPhone, he told me that the apple didn't support this. -
I am wondering if apple could make an ipad about half the size? It would be easier to carry and would be easier to read than an Iphone.
Apple's engineers have apparently decided that the iPhone/touch/iPad and MacBook fit the most popular needs.
Did you have a developer related question? -
How to limiting the size of an existing Sparse Bundle for Time Machine?
There seems to be a solution for locking the size of a new sparse bundle to be used for Time Machine backups (see https://discussions.apple.com/thread/2383738?tstart=0). However, I have a Time Machine sparse bundle with a year's worth of history that is getting very large and I would like to limit its size. Is there a way to constrain the size of an existing sparse bundle without trashing it.
Appying the suggested techniques"
hdiutil resize -size 300g xyz.sparsebundle
and
SetFile -a L PATHTOSPARSEBUNDLE/Info.*
on an existing sparse bundle somehow corrupts it and TM wants to start from scratch.
A method for constraining the size of a TM sparse bundle without trashing it would be very appreciated.budden10, please try this:
Disconnect the external drive to simulate it not working or having failed
Open Time Machine on your Mac and wait a few minutes for your backups to load fully
Go back in time and select a date when you were backing up the external drive
Now look at the Finder window and locate your Mac on the left side of the window under DEVICES
Click on your Mac
What do you see in the window there just to the right? -
The garage window band has remained me too great and I cannot accede from any way to the corner to modify the size. Due to this I cannot accede to the red button to initiate a recording.
Two things to try:
with some Applications it helps to hold down the the "Option Key" while pressing the green "maximize Window" button.
If that does not help try this Apple Script:
--Open the AppleScript editor (in Applications -> Utilities), paste the following and run it:
tell application "Finder"
set {d1, d2, d3, d4} to (get bounds of window of desktop)
end tell
tell application "GarageBand"
set margins to {d1 + 10, d2 + 54, d3 - 10, d4 - 148}
set bounds of window 1 to margins
end tell
Good Luck
Léonie -
Modifying the size of cells in calendar
All:
Is it even possible to modify the size of the cells?. The cells are too narrow and all my contents are wrapped and looks cluttered. Any thoughts?.
Thanks
RajeshHello,
The specific layout of a calendar is almost totally controlled by css. Just find out what the CSS controlling your specific template is, by looking at the template HTML itself or using something like Firebug and then adjust accordingly.
You don't need to change the CSS that is shipped with APEX, in fact I discourage that, but just override it by including in a custom css file or snippet after the standard one is included.
If you don't know CSS here is a good place to start http://www.w3schools.com/css/default.asp it's well worth the time to spend an hour or two learning at least the basics, it will save you countless hours later in any web development environment.
Regards,
Carl -
Can I increase the size of a Long column to 4000 characters?
Can I increase the size of a Long column to 4000 characters?
maximum sizeof 4 GB -1 byte RTFM there: Datatypes(click)
extracted: LONG: Character data of variable length up to 2 gigabytes, or 231 -1 bytes.
Not 4Gb. Or also, read Paul M post.
Regards,
Yoann. -
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 retrieve the data type of a column of a table?
Hi,
I want to retrieve the data type of a column of a table. At the moment I am querying "OCI_ATTR_DATA_TYPE" attribute but it is returning SQLT_CHR for both varchar2 and nvarchar2 data type columns. I need to distinguish between these two data types columns separately. Is there any API through which I could get the exact data type of a column i.e. "nvarchar2"?
Thanks in advance.
HashimHi,
This is the Oracle C++ Call Interface (OCCI) forum - I'm not sure if you are using OCCI or OCI (Oracle Call Interface - the C interface) since you reference "OCI_ATTR_DATA_TYPE" which is more of an OCI focus than OCCI.
In any case, you might take a look at "OCI_ATTR_CHARSET_FORM" which takes the following values:
#define SQLCS_IMPLICIT 1 /* for CHAR, VARCHAR2, CLOB w/o a specified set */
#define SQLCS_NCHAR 2 /* for NCHAR, NCHAR VARYING, NCLOB */So, if you have a datatype of SQLT_CHR and OCI_ATTR_CHARSET_FORM is SQLCS_IMPLICIT then you have a varchar2 if it is SQLCS_NCHAR then you have an nvarchar2.
If you are using OCCI and not OCI then take a look at MetaData::ATTR_DATA_TYPE and MetaData::ATTR_CHARSET_FORM which expose OCI_ATTR_DATA_TYPE and OCI_ATTR_CHARSET_FORM respectively.
Perhaps that will get you what you want.
Regards,
Mark -
How do I modify the size limitation on images in PSE 12?
I frequently use panorama tools in Photoshop CS6 & CC and PSE 12 to generate large images (several sunsets/sunrises reach as much as 370 MB or more --- PNG or TIF without layers). It apears that PSE 12 (and previous) have a limit less than a tenth of that. I also understand that there is a registry fix which would allow for larger images to be displayed.
A) Is that so?
B) What is the patch?
C) What are the (unintended) consequences?
I use Win 7 Pro. One machine is 32 bit; the primary production machine, 64 bit. ThanksEverything you need to know about PSE maximum sizes is in http://helpx.adobe.com/photoshop-elements/kb/maximum-image-size-limits-photoshop.html.
The registry fix you are thinking of affects the Organizer only. The Editor has an absolute limit of 30,000 x 30,000 pixels. File size itself is not the constraining factor.
Cheers,
Neale
Insanity is hereditary, you get it from your children
If this post or another user's post resolves the original issue, please mark the posts as correct and/or helpful accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks. -
Question about Domain file size...
I have a dot Mac account, and my iDisk capacity is 1 Gb.
As I regularly back-up my Domain file from my G5 iMac to a FW external drive that sits on my desk, I have just noticed that the file size is now just over 1 Gb.
Can someone please explain to me why I still have almost 700Mb left on my iDisk, yet my Domain file size is over 1 Gb?? Obviously, there must be 'internal' files that aren't copied to the iDisk.
Thanks,
Rachel.Wow, that's quite a discrepancy. 1gb Domain vs. 300mb site? Well suffice it to say that the Domain file contains all the information that is needed to generate your site. But it makes me curious too why you have such a large discrepancy. Do you have a lot of video on your site?
My site is only about 50-60mb and my Domain is roughly the same size. When I first started using iWeb, I used to poke around inside the Domain file quite a bit more than I do now. You can open up your Domain file by Control-clicking it and selecting "Show Package Contents." At one point early on when I was blithely dragging and dropping stuff into iWeb and publishing just for experimentation, I noticed that even after I deleted images or EVEN WHOLE PAGES, that sometimes the Domain file would still contain images and quicktime movies left over from the deleted pages. I didn't know what was going on and actually tried to delete the "old" items from the Domain file, but I ended up with a non-functional Domain file...lots of error messages saying it was missing this and that. So I started over completely with a new Domain file. I also noticed at the time that my Domain file was several megabytes larger than my site.
Since then, I have been very careful only to drag items to iWeb that will actually be used. The Domain-to-site size ratio has stayed pretty much 1:1. So I chalked up my earlier experience as a fluke. I don't know. Maybe there is an inconsistency somewhere. In fact, do a search here on "Domain file optimizing" or "Domain file bloat" and you may be able to find my questions about the issue. I never did get any responses, though.
Maybe you are looking for
-
How can I execute a java program from a Servlet?
Thank You [email protected]
-
It seems I cannot use Sky Go even if I use Firefox. The only one that works is IE 11.
I was using Google Chrome, but it seems they do not support Silverlight which Sky Go use. I was told that Firefox would work. It doesn't. The only one that works is Internet Explorer 11, which is very slooow. Why can't I use Firefox to view Sky Go?
-
Install Oracle client 9.2.0.1 on AIX 5L
Hell'o, I have a problem while I try to install the client client 9.2.0.1 on AIX 5L. I first installed (custom installation): - network utilities - database utilities - sqlplus - jdbc/oci interface the installation is ok with thisThen I want to add:
-
FM : BAPI_OUTB_DELIVERY_CREATENOREF
I used this Function Module to create Outbound Delivery . System gave me sucessfull mesaage that OutboundDelivery 80001122 has been created. External reference: But when I got to VL03N , No Outbound delivery Exisits with this number . Can any body he
-
Hello I am looking to set up an HP4015x LaserJet printer with an additional wireless JetDirect 690n card to provide users with either wired/wireless network access the ability to print to the same printer. Could someone confirm whether this is possi