Table selection after deletion

Given that i have a Jtable with four rows. if that i deleted the last(4th) row, how can i set the next(3rd) row to be selected?
thanks in advance!

:P
http://www.magiksafe.com

Similar Messages

Tree Table Selection after deletion

Hi,
We have a tree table where we are displaying hierarchy of information. We have a "Delete" operation. This operation is available in the context menu associated to each node. When user selects "Delete" operation, the selected row is deleted and the next node is automatically selected. We have implemented a selection listener on this table but when this automatic selection happens after deletion this event is not triggered. How do we trigger the selection event after deletion? We require the selection event because, we are keeping track of the selected nodes. Even for delete, we are identifying the item to be deleted from the list of tracked nodes. When this auto selection happens and the user clicks delete menu, the auto selected row it is not available in the tracked list as the selection listener is not fired for the auto selection.
Can any throw some light on how to address this?
thanks,

Hi,
what if - after deleting a node - you call for the selectedRowKeys on the tree to get the new selected row. This way you can update what otherwise the listener does.
Frank

How to reduce table size after deleting data in table

In one of the environment, we have 300 GB tabe which contains 50 columns. some of the columns are large object columns. This table contains data for the past one year and every month it is growing by 40 gb data. Due to this we have space issues. we would like to reduce the table size by keeping only recent two months data. What are the posiible ways to reduce the table size by keeping only 2 months data. Database version 10.2.04 on rhel 4.

kumar wrote:
Finally we dont have down time to do by exp/imp method.You have two problems to address:
<ul>
How you get from where you are now to where you want to be
Figuring out what you want to do when you get there so that you can stay there.
</ul>
Technically a simple strategy to "delete all data more than 64 days old" could be perfect - once you've got your table (and lob segments) down to the correct size for two months of data. If you've got the licencing and can use local indexing it might be even better to use (for example) daily partitioning by date.
To GET to the 2-month data set you need to do something big and nasty - this will probably give you the choice between blocking access for a while and getting the job done relatively quickly (e.g. CTAS) or leaving the system run slowly for a relatively long time while generating huge amounts of redo. (e.g. delete 10 months of data, then shrink / compact). You also have a choice between using NO extra space to get the job done (shrink/compact) or doing something which effectively copies the last two months of data.
Think about the side effects you're prepared to run with, then we can tell you which options might be most appropriate.
Regards
Jonathan Lewis

Sending email after deleting the records in a table

Hi
I am deleting the records in a table. After deleting the records,
i want to send an email to another person. I am planning to follow this steps.
1. Create a trigger on the table(AFTER DELETE ON table FOR EACH ROW)
to copy the deleted records to temporary table.
2. Read the temporary table and send an email.
Is there any other way we can do with out creating temporary table ?.
Govind

I don't know what you plan to use to send the mail but here's a solution that would work.
-- Create a send mail procedure
create or replace procedure send_mail (
sender      IN VARCHAR2,
recipient   IN VARCHAR2,
message     IN VARCHAR2)
IS
mailhost VARCHAR2(30) := 'localhost';
mail_conn utl_smtp.connection;
BEGIN
mail_conn := utl_smtp.open_connection(mailhost, 25);
utl_smtp.helo(mail_conn, mailhost);
utl_smtp.mail(mail_conn, sender);
utl_smtp.rcpt(mail_conn, recipient);
utl_smtp.data(mail_conn, message);
utl_smtp.quit(mail_conn);
END;
/-- Create the trigger to email deleted rows
create or replace trigger email_del_rows
after delete on <table>
for each row
declare
msg varchar2(2000);
begin
msg := 'COL1 COL2 COMPANY NAME DATE'||chr(10);
msg := msg||:old.col1||'    '||:old.col2||'    '||:old.company_name||'       '||:old_date|| chr(10);
msg := msg||'END OF FILE';
send_mail('SENDER','[email protected]',msg);
end;
/You can make it look pretty but you get the basic idea.

Shrink Oracle Table after Deletion

A few database tables are very big. An Oracle table still holds the disk space occupied by deleted records according to http://stackoverflow.com/questions/6540546/oracle-10g-table-size-after-deletion-of-multiple-rows. Re: shrink table after delete teaches the following commands to release the idle space from the table.
ALTER TABLE TABLE1 DEALLOCATE UNUSED;
ALTER TABLE TABLE1 ENABLE ROW MOVEMENT;
ALTER TABLE TABLE1 SHRINK SPACE;
ALTER TABLE TABLE1 MOVE;
1. Are the commands feasible?
2. Are they safe?
3. What will be the impacts of running the commands?
4. Is there any other workable safe approach shrinking a table?

Hi,
I advise using shrink table operation.
The tablespace which belong to your table must be in ASSM (Automatic segment space management) to use shrink.
Shrink is safe but you need to run two commands :
1)ALTER TABLE TABLE1 SHRINK SPACE COMPACT; (This is long operation which moves data, but can be done online)
2)ALTER TABLE TABLE1 SHRINK SPACE; (this is quick if you run SHRINK SPACE COMPACT before, it only shift the High Water Mark. Be carreful if you don't run SHRINK SPACE COMPACT before your table will be locked for a long time)
Another point, is that execution plans are calculed using the HWM so SHRINK the table (The 2nd command) will invalidate all the cursors in shared pool where the table is in. So execution plan need to be recalculated (often not a problem).
Regards,

TABLE SIZE NOT DECREASING AFTER DELETION. BLOCKS NOT BEING RE-USED

Hi ,
Problem:
Table size before deletion: 40GB
Total rows before deletion: over 200000
Rows deleted=190000 rows
Table size after deletion is more (as new data was inserted meanwhile).
Purpose of table:
This table is a sort of transaction table.
Whenever an SR is raised by CSR, data gets inserted into this table and is removed when the status is cleared.
So there is constant insertion and purging will happen on this table.
We are using ASSM and tablespace is LOCAL.
This Table has a LONG column also.
Is this problem because of LONG column ?
So here there are 2 problems.
1) INSERTs are not using the space created by DELETE.
2) New INSERTs are taking much more space then expected ?
Let me have your suggestion
Thanks,

I think when you do DELETE it removes the data but
it's not releasing any used space and it's still
marked as used space. I think reorganizing would help
to compress and pack all block and relase any unused
space in blocks. Why do you think that? Deleting data will create space that can be reused by subsequent insert/ update operations. It is not going to release space back to the tablespace to make it available for inserts into other tables in the tablespace, but that's not generally an issue unless you are permanently decreasing the size of a table, which is pretty rare.
Would you also please explain about different about
LOB and LONG ? or point me to any link which explain
baout it.From the Oracle Concepts manual's section on the LONG data type
"Note:
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases."
LONG was a very badly implemented solution to storing large amounts of data. LOBs are a much, much better designed solution-- you should always be using LOBs.
Justin

ADF Table need to be refresh after deleting row

In the table.
After deleting the row use the VO,
ViewObject reqVO = getRequestVO("Requests");
reqVO.clearCache();
reqVO.executeQuery();
then refresh the table to display rows.
AdfUtil.addPartialTarget("tableID");
The table seems to be refreshed, but the row already be deleted still in the table.
If leave the table page, and go back the table page,then the table display rows correct, can't the row that already be deleted.
What is the wrong with the refreshing table?

Can you try refreshing the iterator before setting the partial target as below?
DCBindingContainer bindings =
*(DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();*
DCIteratorBinding iteratorBinding =
*(DCIteratorBinding)bindings.get("<ITERATOR_NAME_IN_PAGEDEF>");*
*if (iteratorBinding != null) {*
iteratorBinding.executeQuery();
Thanks,
Navaneeth

Space reusage after deletion in compressed table

Hi,
Some sources tell, that free space after DELETE in compressed table is not reused.
For example, this http://www.trivadis.com/uploads/tx_cabagdownloadarea/table_compression2_0411EN.pdf
Is it true?
Unfortunatly I cannot reproduce it.

Unfortunatly the question is still open.
In Oracle 9i space, freed after DELETE in compressed block, was not reused in subsequent inserts.
Isn't it?
I saw many evidences from other people. One link I gave above.
But in Oracle 10g I see another figures. After delete rows in compressed blocks, and subsequent insert into that block, block defragmented!
Please, if who know any documentation about change in this behavior, please post links.
p.s.
in 10g:
1. CTAS compress. Block is full.
2. after, deleted every 4 from 5 rows.
avsp=0x3b
tosp=0x99e
0x24:pri[0]     offs=0xeb0
0x26:pri[1]     offs=0xea8 -- deleted
0x28:pri[2]     offs=0xea0 -- deleted
0x2a:pri[3]     offs=0xe98 -- deleted
0x2c:pri[4]     offs=0xe90 -- deleted
0x2e:pri[5]     offs=0xe88 -- live
0x30:pri[6]     offs=0xe80 -- deleted
0x32:pri[7]     offs=0xe78 -- deleted
0x34:pri[8]     offs=0xe70 -- deleted
0x36:pri[9]     offs=0xe68 -- deleted
0x38:pri[10]     offs=0xe60 -- live
0x3a:pri[11]     offs=0xe58 -- deleted
0x3c:pri[12]     offs=0xe50 -- deleted
0x3e:pri[13]     offs=0xe48 -- deleted
0x40:pri[14]     offs=0xe40 -- deleted
0x42:pri[15]     offs=0xe38 -- live
0x44:pri[16]     offs=0xe30 -- deleted
0x46:pri[17]     offs=0xe28 -- deleted
0x48:pri[18]     offs=0xe20 -- deleted
0x4a:pri[19]     offs=0xe18 -- deleted
0x4c:pri[20]     offs=0xe10 -- live
...3. insert into table t select from ... where rownum < 1000;
Inserted rows were inserted in a several blocks. Total number of not empty blocks was not changed. Chains did not occure.
Block above looks as follow:
avsp=0x7d
tosp=0x7d
0x24:pri[0]     offs=0xeb0
0x26:pri[1]     offs=0x776 - new
0x28:pri[2]     offs=0x84b - new
0x2a:pri[3]     offs=0x920 - new
0x2c:pri[4]     offs=0x9f5 - new
0x2e:pri[5]     offs=0xea8 - old
0x30:pri[6]     offs=0xaca - new
0x32:pri[7]     offs=0xb9f - new
0x34:pri[8]     offs=0x34d - new
0x36:pri[9]     offs=0x422 - new
0x38:pri[10]     offs=0xea0 - old
0x3a:pri[11]     offs=0x4f7 - new
0x3c:pri[12]     offs=0x5cc - new
0x3e:pri[13]     offs=0x6a1 - new
0x40:pri[14]     sfll=16
0x42:pri[15]     offs=0xe98 - old
0x44:pri[16]     sfll=17
0x46:pri[17]     sfll=18
0x48:pri[18]     sfll=19
0x4a:pri[19]     sfll=21
0x4c:pri[20]     offs=0xe90 -- old
0x4e:pri[21]     sfll=22
0x50:pri[22]     sfll=23
0x52:pri[23]     sfll=24
0x54:pri[24]     sfll=26As we see, that old rows were defragmented, and repacked, and moved to the bottom of block.
New rows (inserted after compressing of table) fill remaining space.
So, deleted space was reused.

Release of space after delete/truncate table

Hello,
How does release of space after delete/truncate table works? Is the space used before deletion released once delete is complete or not? Will I see the space occupied by deleted table as free in dba_segments or will I need to reorganize the table (drop and recreate again?). Reason why I am asking is that I can see table with 0 rows, but in dba_segment I can see it is occupying few gigabytes....
Thank you

Here is a little illustration for you;
SQL> conn ogan/password
Connected.
SQL> create table ogan_deneme as select * from all_objects;
Table created.
SQL> select count(*) from ogan_deneme;
COUNT(*)
    228470
SQL> set line 1000
SQL> set pagesize 1000
SQL> select * from dba_segments where owner='OGAN';
OWNER    SEGMENT_NAME        PARTITION_NAME           SEGMENT_TYPE       TABLESPACE_NAME                HEADER_FILE HEADER_BLOCK      BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS RELATIVE_FNO BUFFER_
OGAN      OGAN_DENEME          TABLE              SYSTEM                                 854       319981   *30408704*       *1856*         *44*          65536                       1 2147483645                       1               1          854 DEFAULT
SQL> truncate table ogan_deneme;
Table truncated.
SQL> select * from dba_segments where owner='OGAN';
OWNER    SEGMENT_NAME        PARTITION_NAME           SEGMENT_TYPE       TABLESPACE_NAME                HEADER_FILE HEADER_BLOCK      BYTES     BLOCKS    EXTENTS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUPS RELATIVE_FNO BUFFER_
OGAN      OGAN_DENEME           TABLE              SYSTEM                                 854       319981      *65536*          *4*          *1*          65536                       1 2147483645                       1               1          854 DEFAULT
SQL>Hope it Helps,
Ogan

Table grows to 6 GB with 6k records only after Delete ORA-01653:

Hello,
I have a Table that i delete data from using
DELETE FROM DJ_20255_OUTPUT a where trunc(a.LOADED_DATE) <trunc(sysdate -7);
COMMIT;
the issue i have is when i want to repopulate the table i get the Error ORA-01653: unable to extend table.
The table grows to over 6gb but if i truncate that table and in both cases there is no data left in the table after either action the table will only grow to 0.8 Mb once populated.
so with truncate table size is 0.8MB and if i use delete from.... the table grows to 6GB
The repopulation of the table uses mutiple insert statments commiting after each one.
is this a bug or is there an action i should perform onece I have deleted the data?
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi

Is this an Index Organized table ? (select IOT_TYPE from user_tables where table_name = 'DJ_20255_OUTPUT' ;)
Are you saying that you use this sequence :
DELETE .... in one single call to delete all the rows
INSERT ... in multiple calls with COMMIT after each row
Hemant K Chitale

Data Error in the Query/Report after selective data deletion for infocube

Hi Experts,
Please advise what i was missing and what went wrong...
I got a Query (Forecast) on a Multicube...which is based on 2 Infocubes with Aggregates...
As i identified some data discrepency..yesteraday i performed selective data deleation on one of the Infocube
and executed report yesteraday and the results in the query are correct...
When today i executed the same report i am getting different results..
When i compared the results of the report with that of data in cube they are not matching
The report is not displaying the data in cube..for some rows it is displaying the data in the cube but for some rows it is just displaying same as the above row
there is no data loaded into info cube after selective deleation
Do i need to perform request compression and fill the aggregated after selective deleation
Please advise what went wrong

Hi Venkat,
No i haven't done anything on aggregates before or after selective delete
As there is not data load after the selective delete according to SAP Manual we don't need to perform any thing on aggregates...as selective data deletion on cube will delete data from aggregates as well
Please update how to identify error

Table space not reduce after delete in oracle 11G

Hi Team,
I have a DB 11.1.0.7 on unix.
I have execute delete tables on tablespace, but this not reduce.
Thanks

935299 wrote:
What segment space management type is defined for the tablespace in question?
MANUAL
Then you should check out the documentation some more.
But even if you shrink the table segement what is that going to do for the data file size?
I don't undertand you.
ThanksYour thread is titled "Table space not reduce after delete in oracle 11G" which implies to me that you are interested in reducing the size of a tablespace (which really means reducing the size of the underlying datafile(s)).
So, if you shrink the size of the sys.aud$ table, will that cause the datafile(s) to become smaller? Will it accomplish your goal? What else, if anything, needs to happen?

Table size not reducing after delete

The table size in dba_segments is not reducing after we delete the data from the table. How can i regain the space after deleting the data from a table.
Regards,
Natesh

I think when you do DELETE it removes the data but
it's not releasing any used space and it's still
marked as used space. I think reorganizing would help
to compress and pack all block and relase any unused
space in blocks. Why do you think that? Deleting data will create space that can be reused by subsequent insert/ update operations. It is not going to release space back to the tablespace to make it available for inserts into other tables in the tablespace, but that's not generally an issue unless you are permanently decreasing the size of a table, which is pretty rare.
Would you also please explain about different about
LOB and LONG ? or point me to any link which explain
baout it.From the Oracle Concepts manual's section on the LONG data type
"Note:
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases."
LONG was a very badly implemented solution to storing large amounts of data. LOBs are a much, much better designed solution-- you should always be using LOBs.
Justin

Restoring the data from table after deletion

Hi,
If I delete the data from the database (using delete command) , is there anyway to restore that data. I know it looks bit weird but I'm checking whether there is any technique in abap by which we can restore the data.
Your help would be appreciated.
Thanks,
Kranthi.

Hi Kranthi,
When you delete lines of a database table using the DELETE command, the process is only complete after a database commit. Before the commit, any database change can be reset using a database rollback.To be able to perform a database rollback, a database system must generate a copy of each database object before making a change. These copies are kept in a rollback log until the end of an LUW. An overflow of the rollback log always results in the termination of the transaction which caused it. For example, attempting to remind a large number of defaulting customers in the same transaction could trigger such an error. You can only solve this problem by dividing the set of database updates into several smaller units ( LUWs) for the database system. You use this statement if you cannot be certain that all the database changes have been executed correctly.
For your information :
An LUW begins each time you start a transaction,when the database changes of the previous LUW have been confirmed (database commit) or when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends when the database changes have been confirmed (database commit) or when the database changes have been canceled (database rollback). Within an LUW, database changes are not made until after a database commit. Prior to this, any database change can be canceled by a database rollback.
Cheers
Nishanth

Percentage of used table space not reduce after deletion

Hi..
This is my query to delete data from database:-
delete from $tb_data where to_char(partition_dt,'MON') = '$mm';
The $tb_data and $mm is variable and the $tb_data will be read input table name (as example backup_nx160, backup_ngn and etc) and the $mm will be capture the input month.
My question is why the percentage of used table space is not reduce after delete query was executed. Could somebody help me..
Please help me..
Thank you,
Baharin

baharin wrote:
Hi..
Is it the deleted space will be reused by the system ?Yes.
.. How could i check the real free tablespace or real usage table space ?If you have gathered statistics on the schema recently, then sum (avg_row_len*num_rows) should give you the exact number of bytes that are being consumed - assuming all tables are in a single tablespace under consideration. You can subtract this value from sum (dba_data_files.bytes) figure for the tablespace, to know exact free space.

Table selection after deletion

Similar Messages

Maybe you are looking for