Enormous acount of archive log produced for inserts

Question

Hi there,
This is my first post on a forum ever. I have set up a test database that we will be installing on a customer site soon. One table is going to be very large (about 520 million rows). It is partitioned by range (on date) 53 ways (one for every week of the year + 1). I have written a PL/SQL script to load the table with about 1 million rows but I am baffled by the amount of archive log produced. Here is the PL/SQL script :
declare
TYPE hash_a IS TABLE OF VARCHAR2(15) INDEX BY VARCHAR(15);
TYPE array_a IS TABLE OF VARCHAR2(15) INDEX BY PLS_INTEGER;
min_to_meid hash_a;
min_array array_a;
temp VARCHAR2(20);
begin_time TIMESTAMP(0);
end_time TIMESTAMP(0);
begin
-- Initialise
FOR i IN 1..3000 LOOP
temp := TO_CHAR(6162500000 + i);
min_array(i) := temp;
-- Convert to hex char :
SELECT TO_CHAR(130791510000+i, 'xxxxxxxxx') INTO min_to_meid(temp) FROM DUAL;
END LOOP;
SELECT SYSTIMESTAMP INTO begin_time FROM DUAL;
begin_time := begin_time - interval '1' year;
end_time := begin_time + interval '1' minute;
FOR i IN 1..365 LOOP
FOR j IN 1..3000 LOOP
INSERT INTO SESSIONTAB (ms_msid, session_type, start_time, finish_time, call_type, error_type, cm_instance, term_state)
VALUES (min_array(j), 21, begin_time, end_time, 'OTAPA', 0, 1, 'ok');
END LOOP;
begin_time := begin_time + interval '1' day;
end_time := end_time + interval '1' day;
END LOOP;
end;
Essentially it is putting 3000 entries for each day into the table. Each partition increases in size by about 2,5MB -- ie 130MB in total. Yet the amount of archive log produced is crazy -- about 1GB (and that is multiplexed two ways meaning 2GB appear on disk!). All tablespaces for the table and its indexes are LOGGING. Surely this amount is excessive though? Any ideas what is going on??

Answer 1

Thanks for getting back so quickly.
Here are the index creation statements :
rem #--
rem # Indexes for sessiontab
rem #--
CREATE INDEX session_ms_msid_index ON sessiontab(ms_msid) LOCAL;
CREATE INDEX session_device_id_index ON sessiontab(device_id) LOCAL;
CREATE INDEX session_new_ms_msid_index ON sessiontab(new_ms_msid) LOCAL;
CREATE INDEX session_new_mdn_index ON sessiontab(new_mdn) LOCAL;
And here is the table creation. Note that the partition there is a hack. The real partitions are created later in this sql script. As you can see there are quite a few indexes, and as they are local they reside in each partitions tablespace. The only index that resides in its own tablespace is the primary key index. As I understand it, changing the tablespace to NOLOGGING wouldn't make a difference anyway because insert statements always cause redo logs to be written to.
rem #---
rem # Session Table
rem #---
CREATE TABLE sessiontab (
record_id number(38),
ms_msid VARCHAR2(15) NOT NULL,
session_type NUMBER(3) NOT NULL,
start_time TIMESTAMP(0) NOT NULL,
finish_time TIMESTAMP(0) NOT NULL,
call_type CHAR(5) NOT NULL,
error_type NUMBER(3) NULL,
error_data NUMBER(3) NULL,
sms_acc_den_reason NUMBER(2) NULL,
otaf_id VARCHAR2(32) NULL,
cm_instance NUMBER(2) NULL,
term_state VARCHAR2(64) NOT NULL,
trn CHAR(8) NULL,
activation_ms_msid VARCHAR2(15) NULL,
csc_id VARCHAR2(64) NULL,
msc_addr VARCHAR2(12) NULL,
mdn VARCHAR2(15) NULL,
device_id VARCHAR2(15) NULL,
msc_id NUMBER(8) NULL,
job_id NUMBER(10) NULL,
nam_download CHAR(1) NULL,
succ_name CHAR(1) NULL,
new_ms_msid VARCHAR2(15) NULL,
new_mdn VARCHAR2(15) NULL,
home_sid_changed CHAR(1) NULL,
old_home_sid NUMBER(5) NULL,
new_home_sid NUMBER(5) NULL,
sspr_download CHAR(1) NULL,
old_prl_id NUMBER(5) NULL,
new_prl_id NUMBER(5) NULL,
sspr_p_rev NUMBER(5) NULL,
unlocked_phone CHAR(1) NULL,
old_spc CHAR(6) NULL,
changed_spc CHAR(1) NULL,
new_spc CHAR(6) NULL,
generated_akey CHAR(1) NULL,
ssd_updated CHAR(1) NULL,
re_auth CHAR(1) NULL,
succ_ms_commit CHAR(1) NULL,
succ_akey_commited CHAR(1) NULL,
succ_spasm CHAR(1) NULL,
succ_spasm_init CHAR(1) NULL,
succ_welcom_msg CHAR(1) NULL,
extra0 VARCHAR2(64) NULL,
extra1 VARCHAR2(64) NULL,
extra2 VARCHAR2(64) NULL,
CONSTRAINT sessiontab_pk PRIMARY KEY (record_id) USING INDEX TABLESPACE sessiontab_indexes
PARTITION BY RANGE (start_time)(
PARTITION DEFAULT_PART VALUES LESS THAN (TO_DATE('31/12/2000','DD/MM/YYYY'))
);