Loading data from a table to another

Question

This question is continuation of my earlier thread
Re: query help
The last thread was answered by experts and was closed. But I have another problem, I'll put the whole scenario here:
I have a table with data as
id          status_code  emp_id
1           a                10
2           b                10
3           a                20
4           c                30
5           k                10
6           k                10
7           a                10
8           a                20
9           z                20
10           k                30
11           k                30
12           m                20
13           k                10
14           k                30and scripts are:
CREATE TABLE TEST
(id NUMBER,
status_code VARCHAR2(5),
emp_id NUMBER
INSERT INTO test VALUES (1,'a',10);
INSERT INTO test VALUES (2,'b',10);
INSERT INTO test VALUES (3,'a',20);
INSERT INTO test VALUES (4,'c',30);
INSERT INTO test VALUES (5,'k',10);
INSERT INTO test VALUES (6,'k',10);
INSERT INTO test VALUES (7,'a',10);
INSERT INTO test VALUES (8,'a',20);
INSERT INTO test VALUES (9,'z',20);
INSERT INTO test VALUES (10,'k',30);
INSERT INTO test VALUES (11,'k',30);
INSERT INTO test VALUES (12,'m',20);
INSERT INTO test VALUES (13,'k',10);
INSERT INTO test VALUES (14,'k',30);Here's the query that experts gave me in last thread, to fetch desired records:
The requirement was to fetch records of those emp ids where a given emp_id consectively gets same status code.
Each emp id gets a status code and at times it gets same status code as its previous status code. And I am interested in such scenarios.
For example,
emp_id=20 gets status_code=a in id=3 and its next status_code is also =a at id=8,
emp_id=10 gets status_code=k in id=5 and gets same status_code again in id=6,
emp_id=30 gets status_code=k in id=10 and gets same status code in id=11 and id=14.
And the answer was:
select *
from
select
  id,
  status_code,
  emp_id,
  lag(status_code) over (partition by emp_id order by id asc) as last_status,
  lead(status_code) over (partition by emp_id order by id asc) as next_status 
from test
where status_code = last_status
or status_code = next_status
  / But now the new issue is that the records of the table TEST are to be loaded into another table TEST_REVISED . For each ID of table TEST, there will be one or more records in table TEST_REVISED.
ALTER TABLE TEST ADD (CONSTRAINT id_pk  PRIMARY KEY(id));
CREATE TABLE TEST_REVISED
(TR_ID NUMBER PRIMARY KEY,
ID     NUMBER REFERENCES TEST(ID),
NEW_STATUS_CODE VARCHAR2(5)
);This is what I want to see in table TEST_REVISED
TR_ID,     ID,        NEW_STATUS_CODE
100,        1,          'test-code'
200,        2,'         'test-code'
300,        3,         'test-code'
400,        4,          'test-code'
500,        5,          'test-code'
600,        5,           'test-code'--notice here: EMP_ID=10 had same status consecutively in table TEST, so when that record is loaded to TEST_REVISED, ID=5 is used                instead of  id=6
700,        7,          'test-code'
800,        3,           'test-code'--notice here: EMP_ID=20 had same status  consecutively in table TEST, so when that record is loaded to TEST_REVISED, ID=3 is used  instead of id=8
900,        9,           'test-code'
1000,      10,         'test-code'
1100,      10,           'test-code'--notice here: EMP_D=30 had same status  consecutively in table TEST, so when that record is loaded to TEST_REVISED, ID=10 is used  instead of id=11
1200,      12,             'test-code'
1300,      13,             'test-code'
1400,      10,             'test-code'--notice here: EMP_ID=30 had same status  consecutively in table TEST, so when that record is loaded to TEST_REVISED, ID=10 is used  instead of id=14 or id=11Ignore the value of the column NEW_STATUS_CODE here.
How can I load data in table TEST_REVISED from table TEST keeping in view the requirement I mentioned? Table TEST has around 1 million records.
Once this achieved, I want to delete records from table TEST with following ids :
ID=6,8,11,14.
Thanks a lot!
Edited by: user5406804 on Dec 5, 2010 5:49 PM
Edited by: user5406804 on Dec 5, 2010 5:50 PM

Answer 1

OK, i still don't see how this is all supposed to fit together.
You haven't said it, but i'm assuming when you have a series like
id   emp status_code
1    30   k
2    30   k
3    10   a
4    30  k
5    30  kYou actually want the output to be
id   emp status_code   new_id
1    30   k                   1
2    30   k                   1
3    10   a                   3
4    30  k                    4
5    30  k                    4Which presents a bit of a problem using simply analytic functions.
So here's the modified query that picks up just the rows you want 'changed'.
TUBBY_TUBBZ?
select
  id,
  emp_id,
  status_code,
  connect_by_root(id) as new_id
from
  select
    id,
    emp_id,
    status_code,
    lag(status_code)  over (partition by emp_id, status_code order by id asc) as last_status,
    row_number()      over (partition by emp_id, status_code order by id asc) as rn
  from
    select
      id,
      emp_id,
      status_code,
      lead(status_code) over (partition by emp_id order by id asc) as next_code,
      lag(status_code) over (partition by emp_id order by id asc) as last_code,
      row_number() over (partition by emp_id order by id asc) as rn
    from test
  where status_code in (last_code, next_code)
start with last_status is null
connect by prior emp_id = emp_id
and prior status_code = status_code
and prior rn = rn - 1
     ID     EMP_ID STATU     NEW_ID
      5        10 k           5
      6        10 k           5
      3        20 a           3
      8        20 a           3
     10        30 k          10
     11        30 k          10
     14        30 k          10
7 rows selected.
TUBBY_TUBBZ?You say you have a lot of rows in the TEST table, and i'm hoping and praying this is a one time requirement and not an on-going process that needs to occur so your best bet (performance wise) would probably be to use the above query to create a temporary table.
Use that temporary table to control the rest of the process (inserting into TEMP_REVISED and deleting from TEST).
That's the best i can think of based on what i believe your requirement is ... and i honestly don't think that's going to perform overly well (the connect by functionality specifically).