Slow running queries on a table partitioned by date

Similar Questions

• Table partitioning/indexing strategy

  Hello
  
  I have a data warehouse containing medical data. Normally, we develop queries against a small number of patients (e.g. where patient_id < 100) and adjust upward to run on a greater number (usually the entire base of 26 000 patients least some due to exclusion criteria).
  
  The largest table contains about 200 million lines, and I'm working on the question of whether I can change the partitioning and indexing in order to improve the performance of queries.
  
  The table contains 'patient_id', 'visit_id', 'item_id', 'chart_time', 'value' and 'valuenum' column and a variety of other columns that are rarely used. The id id columns are integers, pointrefers to the type of value is saved and value (varchar2) and valuenum (number) contain the data. chart_time is a "timestamp with time zone '.
  
  Currently, there are clues on patient_id, visit_id and item_id and a composite index on (visit_id, itemid). There is no partitioning for the moment.
  
  1. is the current index redundent? that is visit_id, item_id and composite (visit_id, item_id) do I need?
  2. we started to run queries of time based for specific patients. that is, we want data for specific items, for a specific set of visits, in the first day. An index on (visit_id, chart_time, item_id) would help with that?
  3. the table of patient_id partitioning help? We "never" queries between patient and therefore the data of each patient are independent. The database is running on 2 raid controllers, one for data, one for the index, perhaps it would be better to put half of patients on a single controller, and the other half on the other?
  
  Thank you
  
  Dan Scott

  Hello

  1. the index on visit_id sounds redundant as it is the main column in the composite index (visit_id, itemid).
  2. added chart_time to the composite index could be useful that the pair of columns (visit_id, item_id) is not quite selective. You must put in place a realistic model of your data distribution, choose some queries that you intend to run often watch their performance. It is not possible to predict performance in function purely thereotical reasoning.
  3 bear partitioning functions: maintenance of data (for example truncating, deleting or moving old partitions) and eliminating the irrelevant data in queries (partition size). You imagine you having to truncate, delete, or move a partition that is defined by a range of patient_id? Probably not. Can you imagine the need to restrict your query to a certain range of patient_id? Unlikely. That answers your question.

  Best regards
  Nikolai

• Characters not visible (caused by hitting the bar space or TAB in PL/SQL developer tool) causing slow running query? and database with low performance?

  Hi all

  I need your help to get this issue resolved its urgent and I'm not able to get to the conclusion. Here is my scenario, I'm getting slow query runs because of some non-visible characters that are copied with the application of the PL/SQL developer tool. Please find below attached screenshot: Oracle_Issue

  

  Note: This non-visible characters are caused when we write the query then us hit the SPACEBAR or press TAB PL/SQL developer tool

  I use the developer tool PL/SQL to write or test the query. Now I take this request copy paste in my application of the company (who takes this query connects to Oracle or any source of data base, catch data and produce PDF reports for customers).

  Now, my client is the Oracle user when I write and you run this query by the PL/SQL Developer, it works fine, but when I paste in my Inbox feature request (reporting system) and run it, it runs slower and jams to the customer database. Now after a little research I found that when I copy the query directly from PL/SQL developer at my request, he copy some characters not visible (introduced when we press SPACE or TAB in PL/SQL developer tool when writing query) with the request, then I copy this query again to my box of the application Notepad and delete these non-visible characters. Now, after removing the non-visible characters again once I copy backup question in my application and run the query, it works normally. Please find below attached screenshot: Oracle_Issue 2

  

  So I think that the cause of slow performance is due to some INVISIBLE CHARACTERS present in the query.

  My application uses SQL server 2008-2012 at the backend to store data from different sources.

  Character set used: SQL_Latin1_General_CP1_CI_AS

  
  

  To write and test queries: PL/SQL developer tool

  My Client use Oracle 11 g

  Character set used: Normal character: NLS_CHARACTER: AL16UTF16

  National Characeter: NLS_NCHAR_CHARACTER: WE8WIN1521

  I just wanted to know the blocking process to the top of the database and the characters not visible how affecting slow running query of query database.

  Please let me know if I'm missing something or you need more information on this issue.

  Thanks in advance,

  HP

  Simple answer. No.

  Spaces and line breaks do not change the execution plan created. Does not plan to run slower or faster.

• Bad performance on a table partitioned range when you use sysdate

  I have a partition table with a DATE partition key column.
  Tables servs as a sliding window this is by adding a new partiotion for each day and dropping out of the older partitions.
  Each week, I generate a weekly report:
  SELECT... FROM MaTable WHERE part-key-column > SYSDATE-7;
  This query runs for about 5 hours
  
  When you use a hardcoded hard 'day' the query is finished about 4 times faster
  SELECT... FROM MaTable WHERE part-key-column > TO_DATE ('20100211', 'YYYYMMDD');
  
  any suggestion?
  
  Qry Plans:
  
  First Qry (poor):

  SQL> explain plan for SELECT * FROM dwh_net1.net_na_messw  WHERE dwh_net1.net_na_messw.mdate > trunc(SYSDATE - 7);
  
  EXPLAIN PLAN ausgeführt.
  
  SQL> select * from table(dbms_xplan.display);
  
  PLAN_TABLE_OUTPUT                                                                                                                                                                                                                                              
  ---------------------------------------------------------------------------------------------------------
  Plan hash value: 1311981634                                                                                                                                                                                                                                    
                                                                                                                                                                                                                                                                 
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                      
  | Id  | Operation                | Name         | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |                                                                                                                                                      
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                      
  |   0 | SELECT STATEMENT         |              |  8479K|  3000M|  1975K (10)| 06:35:11 |       |       |                                                                                                                                                      
  |   1 |  PARTITION RANGE ITERATOR|              |  8479K|  3000M|  1975K (10)| 06:35:11 |   KEY |    61 |                                                                                                                                                      
  |*  2 |   TABLE ACCESS FULL      | NET_NA_MESSW |  8479K|  3000M|  1975K (10)| 06:35:11 |   KEY |    61 |                                                                                                                                                      
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                      
                                                                                                                                                                                                                                                                 
  Predicate Information (identified by operation id):                                                                                                                                                                                                            
  
  PLAN_TABLE_OUTPUT                                                                                                                                                                                                                                              
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                                                                            
                                                                                                                                                                                                                                                                 
     2 - filter("NET_NA_MESSW"."MDATE">TRUNC(SYSDATE@!-7))                                                                                                                                                                                                       

  Second (hardcoded, faster) Qry:

  SQL> explain plan for SELECT * FROM dwh_net1.net_na_messw  WHERE MDATE > to_date('12.02.2010','DD.MM.YYYY');
  
  EXPLAIN PLAN ausgeführt.
  
  SQL> select * from table(dbms_xplan.display);
  
  PLAN_TABLE_OUTPUT                                                                                                                                                                                                                                              
  ---------------------------------------------------------------------------------------------------------
  Plan hash value: 1311981634                                                                                                                                                                                                                                    
                                                                                                                                                                                                                                                                 
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                      
  | Id  | Operation                | Name         | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |                                                                                                                                                      
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                      
  |   0 | SELECT STATEMENT         |              |  8479K|  3000M|   227K (10)| 00:45:30 |       |       |                                                                                                                                                      
  |   1 |  PARTITION RANGE ITERATOR|              |  8479K|  3000M|   227K (10)| 00:45:30 |    54 |    61 |                                                                                                                                                      
  |*  2 |   TABLE ACCESS FULL      | NET_NA_MESSW |  8479K|  3000M|   227K (10)| 00:45:30 |    54 |    61 |                                                                                                                                                      
  ---------------------------------------------------------------------------------------------------------                                                                                                                                                      
                                                                                                                                                                                                                                                                 
  Predicate Information (identified by operation id):                                                                                                                                                                                                            
  
  PLAN_TABLE_OUTPUT                                                                                                                                                                                                                                              
  ---------------------------------------------------------------------------------------------------------
                                                                                                                                                                                                                                                                 
     2 - filter("MDATE">TO_DATE('2010-02-12 00:00:00', 'yyyy-mm-dd hh24:mi:ss'))                                                                                                                                                                                 
                                                                                                                                                                                                                                                                 

  Published by: user10396457 on February 19, 2010 12:27

  Your two says plans are exactly the same. Are you sure that the elapsed time are different. Can you please set autotrace to traceonly and run two statements and send the output.

• Number of rows in each partition is displayed with a NULL value for a table partitioned in user_tab_partitions. Why?

  I created a table and partitioned on the date of the entry and added a local partitioned index.

  Now, I use a query to extract "num_rows" of user_tab_partitions to know the number of rows in each partition.

  Getting this value as null num_rows, wonder why?

  After looking to explain the Plan after interrogation ("select * from my_table1 where entry_date = 1 January 2015" ;))

  to find out if she actually partitioned table and its data in different partitions, I interpreted in effect because the query plan had a line like Partition_range (Single).

  My Question is:

  (a) is actually partitioned data (have I misinterpreted the Explain plan)

  (b) why is the num_rows null column in the query (Pasted below)

  (c) also in addition what difference it would have been if I had created a Global Index instead of the Local Index in my case?

  The following code Snippet:

  ----------------------------------------------------------------------------------------------

  create the table my_table1
  (
  roll_no number constraint my_table1_pk primary key,
  date of entry_date
  )
  partition of range (entry_date)
  (
  PARTITION data_p1 VALUES LESS THAN (TO_DATE (December 31, 2014 ',' DD-MM-YYYY ""));
  PARTITION data_p2 VALUES LESS THAN (MAXVALUE)
  );

  
  create an index only my_table1_indx on my_table1 (entry_date) local;

  ----------------------------------------------------------------------------------------------

  I now insert two lines:
  insert into my_table1 values (1, to_date ('01-01-2015', ' dd-mm-yyyy'));
  insert into my_table1 values (2, to_date('01-02-2015','dd-mm-yyyy'));

  ----------------------------------------------------------------------------------------------

  These have been inserted successfully, now using the query below shows num_rows column as null. I don't know why?

  SELECT table_name, num_rows, high_value, nom_partition
  Of user_tab_partitions
  where table_name = 'MY_TABLE1 '.
  ORDER BY table_name, nom_partition;

  ----------------------------------------------------------------------------------------------

  
  

  (a) is actually partitioned data (have I misinterpreted the Explain plan)

  Yes, it is partitioned. You can query this particular partition SELECT * FROM my_table1 (data_p1) PARTITION to check that.

  (b) why is the num_rows null column in the query (Pasted below)

  As already mentioned that you have not collected statistics.

  (c) also in addition what difference it would have been if I had created a Global Index instead of the Local Index in my case?

  In fact, you have created two types of indexes without knowing (can be)! One is not partitioned (although this column is not partition key) and another is partitioned (LOCAL). They are MY_TABLE1_PK and MY_TABLE1_INDX. You can check that USER_INDEXES.

  You can read this article to get an early jump on the partitioning of decision. Partition: Partition decisions

• DBA_TABLES. NULL for tables partitioned, yet Nom_tablespace DBMS_METADATA. GET_DDL displays a name...

  Hello

  Hence the name of tablespace comes when you make one

  ~ Select DBMS_METATDATA. GET_DDL ('TABLE', 'tname', 'owner')...

  on a table partitioned, where you see things like:

  ~ CREATE TABLE...

  ~ ...

  ~ STORAGE(INITIAL 134217728 NEXT 134217728 MINEXTENTS 1 MAXEXTENTS 2147483645)

  (~ DEFAULT USER_TABLES)

  ~ TABLESPACE "ABCD_LOGD2".

  before all the blocks related to the different partitions of this table, where a

  ~ Select nom_tablespace from dba_tables where table_name = 'TNOM '...

  Returns a null value?

  Whence dbms_metatdata this ABCD_LOGD2 value? (in what dictionary?,)

  DBA_SEGMENTS/extents display only the partitions information...)

  Thank you...

  SEB

  Hello

  What is the value of 'deffered_segment_creation '.

  Take a look of it

  Select def_tablespace_name in the dba_part_tables where table_name = 'tname'--> your table

  Concerning

• I have Ps CS6 running on a MAC Pro partitioned and using Windows 8.1. It was mainly for the resolution of the screen. However, as the Ps work the tiles on my screen and the icons at the top and to the bottom of the face are so small I don't see the correc

  I have Ps CS6 running on a MAC Pro partitioned and using Windows 8.1. It was mainly for the resolution of the screen.

  However, as the Ps work the tiles on my screen and the icons at the top and to the bottom of the face are so small I don't see the correctly.

  Can I enlarge these and the layers on the right to a box size readable?

  My UI elements appear tiny. | Error postal codes of Mylenium

  Mylenium

• Table partitioning

  I have a table in my DB with stored more then 24 million and is growing every day. Growth rate increases with the passage of time. I want this partition table, in such a way that three first partitions such as each partition contains 10 years of data, and the remaining partition such as each partition contains data for 5 years.
  This is the first time that I am any table partitioning, I understand following sql is not correct, I need your help in resolving this issue.
  

  ALTER TABLE cb_pen_pmt_slip_dtl
  ADD
  PARTITION BY range (payment_date)
  INTERVAL (NUMTOYMINTERVAL(5,'YEAR'))
  (PARTITION p1 VALUES LESS THAN (TO_DATE('2000-01-01','YYYY-MM-DD'))
  partition p2 values less than (maxvalue));

  Hello

  This link can help you...
  >

  Kind regards

• Table Partitioned parallelized vs

  Hello
  (11.2 server, OS = OL5)
  
  I have a table that contains more than 50 million lines. I created this table with option 'parallel degree (x).
  
  It seems that the time required to execute a query on this table does not change when I share that, for example partition range dividing the table to 3 partitions.
  
  (access the request a unique index in the table and the query criteria match exactly one of the partitions)
  
  the question:
  1. What is the difference of strategy parallelism between «Parallel degree...» "and the"Division "?
  2. which of them are better in what scenario?
  3. is it better to use PARALLEL_AUTOMATIC_TUNING?
  4 and especially why the performance doesn't change even with a local index on the partitions?
  
  Thank you
  SMSK.

  >
  It seems that the time required to execute a query on this table does not change when I share that, for example partition range dividing the table to 3 partitions
  . . .
  (access the request a unique index in the table and the query criteria match exactly one of the partitions
  . . .
  @Adam Martin: thanks, but I was explained to question 4 that the performance does not change when I toggle locality index.
  >
  I do not see why it would be necessarily change just of partitioning. What is your reason to think so?

  If the index access is used it is basically to get the IDENTIFIER of a line of interest. The line can then be retrieved using the ROWID. The recovery time will be essentially the same way regardless of the line in a partitioned table or non-partitioned table, and regardless of whether the line of partition. This is because the ROWID is (simple explanation here) a FILE ID (which file?), a BLOCK number (relative block in the file) and a LINE NUMBER (which line in the block. It doesn't matter if the segment that is the block is a segment of the table, partitioned table segment, segment index, etc.

  It is the only factor that COULD change the time of the query when the index is used if the access of the index itself is more effective when the table is partitioned when the table is not partitioned.

  Clearly if it is an overall index, there is a change since the index access itself will be the same.

  The only factor now that MIGHT change the time of the request is so if 1) the index is changed locally and 2) the local index has a different structure than the old index that allows to find the best performing required index entries.

  You have not published information on the index of structure, so let me give you an analogy which shows a scenario where it is clear that the access to the index would not change.

  Assume that the overall index is analogous to a catalogue of cards with 26 entries - one for each letter of the alphabet. My query accesses the entries beginning with the letter 'F' As discussed above in table access to aid a ROWID obtained from the index will be the same, if the table is partitioned or not.

  So now I have the partition table and have 26 partitions - one for each letter of the alphabet.

  With the help of the global index of the access to the partition of 'F' will be the same.

  Now, if I create a local index (instead of global) it's almost as if I now 26 index, one for each letter of the alphabet. The first entry for the 'F' in the global index can be found by reading the root node and perhaps one or two other nodes - then that an index scan can be performed.

  The first entry for the 'F' in the local index is at the beginning of the index - no need to jump or to do a binary search to ignore the 'A', 'B', etc. entered.

  This time difference is microscopic.

  Once I found the first entry for the 'F' either in the overall index, or local 'F' remaining entries in the index are consecutive, so access time will be the same.

  I don't know if there is a structural difference between the indices and the that you tried, but the above should show if the structure (order) has not changed it would not be a noticeable difference in access.

• Become table partitioning

  Hi I have a table where about 260 bln + records. and actionaly of infromation inserted. the structure of the table.
  
  CREATE TABLE NUM_CALLS
  (
  NUMBER OF N_BLK
  NUMBER,
  NUMBER OF SRV_A
  NUMBER OF SRV_B
  NUMBER OF IND_B
  START DATE,
  NUMBER OF PTT,
  NUMBER OF AIR,
  NUM VARCHAR2 (2000 BYTE),
  NUMBER OF HARD,
  VARCHAR2 (240 BYTE) SERVICES,
  STATUS VARCHAR2 (1 BYTE),
  VARCHAR2 (240 BYTE) DSC,
  INCOMING NUMBER,
  THE NUMBER LEAVING,
  NUMBER OF BILLPAR
  NUMBER OF AIR_SUB
  NUM_A VARCHAR2 (2000 BYTE),
  NUMBER OF PTT_SUB
  DIR CHAR (1 BYTE).
  YOUR VARCHAR2 (5 BYTE)
  NUMBER OF PTT_TOLL
  NUMBER OF R_ROAMFILE_SEQ
  NUMBER OF INDICATED,
  NUMBER OF SRV_TOLL
  PTT_TOLL2 NUMBER,
  SRV_TOLL2 NUMBER,
  IMEI VARCHAR2 (50 BYTE),
  RTYPE VARCHAR2 (10 BYTE),
  NUMBER OF R_MSCID
  NUMBER OF R_CALLS_LOG
  NUMBER OF UTC,
  NUMBER OF TRANSACTIONS,
  NUMBER OF SRC_SEQN
  NUMBER OF FWD_TYPE
  NUMBER OF TM_EVENTS
  DST VARCHAR2 (20 BYTE),
  ACCUM RAW (2000).
  UTTYPE CHAR (1 BYTE),
  TM_MODIFIERS RAW (2000)
  )
  TABLESPACE CDR
  PCTUSED 40
  PCTFREE 10
  INITRANS 1
  MAXTRANS 255
  STORAGE)
  80K INITIAL
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  PCTINCREASE 0
  FREELISTS 1
  FREELIST GROUPS 1
  DEFAULT USER_TABLES
  )
  LOGGING
  NOCOMPRESS
  NOCACHE
  NOPARALLEL
  NOMONITORING;
  
  There is no primary key on the table, and this table records are not unique.
  
  
  
  I want to become this table partitioning column by TRT (date) by date. is it possible to become the partitioning table after and if this table actionaly used? If possible then how can I do?

  Create the new table with a different name, but same structure as NUM_CALL with no data ex create table new_table in new_table select * from YOUR_TABLE_NAME where 1 = 2;
  or just get ddl for the use of this table:

  SELECT DBMS_METADATA. GET_DDL('TABLE','YOUR_TABLE_NAME') FROM dual;

  Modify this script, create the new table, and then create the partition you want (daily, monthly, annual) of course you can also create a subpartition.

  prepare a few anonymous PLSQL block, and then insert the data into the new partition table, that's all.

  stop the execution of the process, drop old table and rename the new table with the old name (deleted table)

• Question about stored queries in meeting tables

  I'm curious to know how much memory storing queries in meeting tables back. The query results themselves (about 5-6) are small, no more of 100 records. The site traffic is low, not more than 100 k a month but should leap to more 1 million. The web server (primary and failover) are tough systems, I believe than 4gigs of ram. So I don't think, should I be concerned?

  Quote:
  Posted by: CFMXPrGrmR
  Are there benefits to the application.queryname a table? Or is it as well to access the query in the application scope?

  It is already an array.

• Why cannot create the table partitioned successfully?

  Why cannot create the table partitioned successfully?

  SQL> create table hr.gps_log_his
  (id number,
  name varchar2(10),
  time date)
  tablespace ts_log_his
  PARTITION BY RANGE (TIME)
  (PARTITION udp_part09110707 VALUES LESS THAN (TO_DATE('09110708','yymmddhh24')),
  PARTITION udp_part09110708 VALUES LESS THAN (TO_DATE('09110709','yymmddhh24')),
  PARTITION udp_part09110709 VALUES LESS THAN (TO_DATE('09110710','yymmddhh24')),
  PARTITION udp_part09110710 VALUES LESS THAN (maxvalue)
  );
  
  (PARTITION udp_part09110707 VALUES LESS THAN (TO_DATE('09110708','yymmddhh24')),
  Error on line 7: 
  ORA-14120: DATE columns did not specify the complete partitioning limits.

  The detailed error message is as follows:

  ORA-14120: incompletely specified partition bound for a DATE column
  
  Cause: An attempt was made to use a date expression whose format does not fully
  (i.e. day, month, and year (including century)) specify a date as a partition bound
  for a DATE column. The format may have been specified explicitly (using TO_DATE()
  function) or implicitly (NLS_DATE_FORMAT).
  
  Action: Ensure that date format used in a partition bound for a DATE column supports
  complete specification of a date (i.e. day, month, and year (including century)). If
  NLS_DATE_FORMAT does not support complete (i.e. including the century) specification
  of the year, use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully
  express the desired date. 
  

  Action: Change to_date('09110708','yymmddhh24') to
  to_date('2009110708','yyyymmddhh24')

• Export of database so slow running

  Hello
  
  I export our server Oracle 11 GR 2
  

  C:\Documents and Settings\Administrator>exp system/manager@prod1 FULL=Y STATISTICS=NONE
  
  Export: Release 11.1.0.6.0 - Production on Tue Apr 26 09:11:53 2011
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  
  Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit
  Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  Export done in WE8MSWIN1252 character set and UTF8 NCHAR character set
  server uses UTF8 character set (possible charset conversion)
  
  About to export the entire database ...
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  
  Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit
  Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  Export done in WE8MSWIN1252 character set and UTF8 NCHAR character set
  server uses UTF8 character set (possible charset conversion)
  
  About to export the entire database ...
  . exporting tablespace definitions
  . exporting profiles
  . exporting user definitions
  . exporting roles
  . exporting resource costs
  . exporting rollback segment definitions
  . exporting database links
  . exporting sequence numbers
  . exporting directory aliases
  . exporting context namespaces
  . exporting foreign function library names
  . exporting PUBLIC type synonyms
  . exporting private type synonyms
  . exporting object type definitions
  . exporting system procedural objects and actions

  That is why it is hanging from the "export of system procedural objects and actions? He has already stayed here for 5 hours.
  How to count all procedures and actions, so I don't know how big are they?
  How can I speedup this part?
  
  
  Thank you

  Salvation;

  you are at level 11 GR 2 Please use expdp. Please also follow:

  Note to master for data pump [ID 1264715.1]

  Respect of
  HELIOS

• How to select a record in one table to manipulate data in a database?

  Hello community,

  Using 32-bit Labview 2015.

  I created a user interface that runs a query and retrieves my table from a sql database.

  I want to be able to manage only one record at a time by selecting the record in my table and then manipulate the data according to the needs.

  Whenever the user runs a query, I want as the first record in the table to be selected / highlighted.

  I want an indicator that is currently active.

  Then a click of a button, to be able to scroll the actively selected record.

  Once I have the selected record, I want a way to write a query to edit or delete the record.

  Is attached a photo of my query to select all of my table and connect data in my table (results).

  Attached a photo of my painting showing the timeline of my sql database.

  What is the best way to go on a record selection in a table and the modification of data with a query?

  Any help would be greatly appreciated.

  Thank you

  I guess that's not a table, but multi-column listbox.

  Right click, select--> highlight whole line selection Mode

  The value of the multicolumn listbox is the row index - you can write a local variable to highlight the line, the event structure to handle the user clicking on, etc.

  If you enable the property editable ListBox cells, you can allow users to edit the items of the listbox.

  If you want to get the data in row, you hint REF table and work with the array of strings in row - convert it to cluster, etc..

  I don't know, what type of data, it is, how you structure the database looks like, I don't even know if you use the wrapper to work with the database, I can't write queries for you.

  Something like Update Tablica Set Serial = '5' where ID = '22';

• Table 'dbc_user' in the descriptor of the item: 'user' does not exist in a space of accessible table by the data source.

  In my development environment, when I run the production server, I get the following error in the server.log. I have configured the data source for the production. I use ATG 10.1. Please help solve this problem. Here are the logs

  22:46:45, 765 full repository INFO [ProfileAdapterRepository] SQL boot

  22:46:45, 988 full repository INFO [AdminSqlRepository] SQL boot

  22:46:45, 990 Initializing INFO [AdminAccountInitializer] account database/atg/dynamo/security/AdminAccountManager of/atg/dynamo/security/SimpleXmlUserAuthority

  22:46:46, 450 ERROR [ProfileAdapterRepository] Table 'dbc_user' in the descriptor of the item: 'user' does not exist in a space of accessible table by the data source.  DatabaseMetaData.getColumns returns without columns.  Catalog = null Schema = null

  22:46:46, 466 WARN [ProfileAdapterRepository] atg.adapter.gsa.GSARepository-> loadColumnInfo: SQLException in Table.loadColumnInfo.  Try again.

  com MySQL.JDBC.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'atgcoredb.dbc_user' does not exist

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:525)

  at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)

  at com.mysql.jdbc.Util.getInstance(Util.java:382)

  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)

  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3603)

  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3535)

  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1989)

  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)

  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)

  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2570)

  at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1476)

  to com.mysql.jdbc.DatabaseMetaData$ 7.forEach(DatabaseMetaData.java:3966)

  at com.mysql.jdbc.IterateBlock.doForAll(IterateBlock.java:51)

  at com.mysql.jdbc.DatabaseMetaData.getPrimaryKeys(DatabaseMetaData.java:3950)

  at atg.adapter.gsa.Table.loadColumnInfo(Table.java:1926)

  at atg.adapter.gsa.GSARepository.loadColumnInfos(GSARepository.java:7534)

  to atg.adapter.gsa.GSARepository$ 1.run(GSARepository.java:5431)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (ThreadPoolExecutor.java:603)

  at java.lang.Thread.run(Thread.java:722)

  22:46:46, 467 WARN [ProfileAdapterRepository] unknown JDBC type for property: businessAddress, element type: user. Make sure that the column names in the database and match model.  The business_addr column is not found in the set of columns returned by the database: {} for this table.

  22:46:46, 470 ERROR [ProfileAdapterRepository] Table 'dbc_buyer_billing' in the descriptor of the item: 'user' does not exist in a space of accessible table by the data source.  DatabaseMetaData.getColumns returns without columns.  Catalog = null Schema = null

  22:46:46, 470 WARN [ProfileAdapterRepository] atg.adapter.gsa.GSARepository-> loadColumnInfo: SQLException in Table.loadColumnInfo.  Try again.

  com MySQL.JDBC.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'atgcoredb.dbc_buyer_billing' does not exist

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:525)

  at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)

  at com.mysql.jdbc.Util.getInstance(Util.java:382)

  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)

  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3603)

  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3535)

  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1989)

  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)

  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)

  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2570)

  at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1476)

  to com.mysql.jdbc.DatabaseMetaData$ 7.forEach(DatabaseMetaData.java:3966)

  at com.mysql.jdbc.IterateBlock.doForAll(IterateBlock.java:51)

  at com.mysql.jdbc.DatabaseMetaData.getPrimaryKeys(DatabaseMetaData.java:3950)

  at atg.adapter.gsa.Table.loadColumnInfo(Table.java:1926)

  at atg.adapter.gsa.GSARepository.loadColumnInfos(GSARepository.java:7534)

  to atg.adapter.gsa.GSARepository$ 1.run(GSARepository.java:5431)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (ThreadPoolExecutor.java:603)

  at java.lang.Thread.run(Thread.java:722)

  22:46:46, 471 WARN [ProfileAdapterRepository] unknown JDBC type for the property: myBillingAddrs, element type: user. Make sure that the column names in the database and match model.  The addr_id column is not found in the set of columns returned by the database: {} for this table.

  22:46:46, ERROR 611 [ProfileAdapterRepository] Table 'dbc_org_billing' in the descriptor of the item: "organization" does not exist in a space of accessible table by the data source.  DatabaseMetaData.getColumns returns without columns.  Catalog = null Schema = null

  22:46:46, 611 WARN [ProfileAdapterRepository] atg.adapter.gsa.GSARepository-> loadColumnInfo: SQLException in Table.loadColumnInfo.  Try again.

  com MySQL.JDBC.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'atgcoredb.dbc_org_billing' does not exist

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:525)

  at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)

  at com.mysql.jdbc.Util.getInstance(Util.java:382)

  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)

  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3603)

  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3535)

  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1989)

  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)

  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)

  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2570)

  at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1476)

  to com.mysql.jdbc.DatabaseMetaData$ 7.forEach(DatabaseMetaData.java:3966)

  at com.mysql.jdbc.IterateBlock.doForAll(IterateBlock.java:51)

  at com.mysql.jdbc.DatabaseMetaData.getPrimaryKeys(DatabaseMetaData.java:3950)

  at atg.adapter.gsa.Table.loadColumnInfo(Table.java:1926)

  at atg.adapter.gsa.GSARepository.loadColumnInfos(GSARepository.java:7534)

  to atg.adapter.gsa.GSARepository$ 1.run(GSARepository.java:5431)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (ThreadPoolExecutor.java:603)

  at java.lang.Thread.run(Thread.java:722)

  22:46:46, 612 WARN [ProfileAdapterRepository] unknown JDBC type for the property: myBillingAddrs, element type: Organization. Make sure that the column names in the database and match model.  The addr_id column is not found in the set of columns returned by the database: {} for this table.

  You want to run the B2BCommerce module? If so, then you must run the $dynamo_home /... / B2BCommerce/SQL/db_components/MySQL/b2b_user_ddl. SQL ddl because you are missing the B2BCommerce tables. If this isn't the case, you will have to redo without the B2BCommerce module.

  Thank you

  Joe