Partition Table

[laxmi_etl]

Hi-

I am trying to load data into a Oracle table which is partioned by week.

I choose Index mode as maintenance. And when I run the Job the data loads correctly but the job status is aborted.

The error gives Oracle log file reference. And the log file does not show any errors.

Any thoughts.


Thanks

[ArndW]

...The error gives Oracle log file reference. And the log file does not show any errors. ...Any thoughts.

Sure, my thoughts are that you haven't posted the exact error message, so there isn't much to work with yet.

[laxmi_etl]

ora.974848.772490.0.log

[laxmi_etl]

"ora.974848.772490.0.log" 170 lines, 9371 characters

SQL*Loader: Release 10.2.0.2.0 - Production on Sat Feb
17 17:40:33 2007

Copyright (c) 1982, 2005, Oracle. All rights
reserved.

Control File: ora.974848.772490.0.ctl
Character Set WE8ISO8859P1 specified for all input.

Data File: ora.974848.772490.fifo.0
File processing option string: "FIX 479"
Bad File: ora.974848.772490.0.log.bad
Discard File: none specified

(Allow all discards)

Number to load: ALL
Number to skip: 0
Errors allowed: 50
Continuation: none specified
Path used: Direct

Table XXXX, partition YYYY, loaded from
every logical record.
Insert option in effect for this partition: APPEND
The following index(es) on table XXXX were
processed:
index AAAA partition YYY
was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested
index BBBB partition
YYYY was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested
index CCCC partition
YYYY was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested
index DDD partition YYYY
was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested

Table SLS_SBC_LW_DM, partition YYYY:
999999 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were
failed.
0 Rows not loaded because all fields were null.

Date cache:
Max Size: 1000
Entries : 332
Hits : 999667
Misses : 0

Bind array size not used in direct path.
Column array rows : 5000
Stream buffer bytes: 256000
Read buffer bytes: 1048576

Total logical records skipped: 0
Total logical records read: 999999
Total logical records rejected: 0
Total logical records discarded: 0
Total stream buffers loaded by SQL*Loader main thread:
861
Total stream buffers loaded by SQL*Loader load thread:
0

Run began on Sat Feb 17 17:40:33 2007
Run ended on Sat Feb 17 17:44:24 2007

Elapsed time was: 00:03:51.65
CPU time was: 00:00:26.52

[ArndW]

You are right, the Oracle log shows no errors.

The error gives Oracle log file reference...

That is the error message whose contents could help.

[laxmi_etl]

"ora.974848.772490.0.log" 170 lines, 9371 characters

SQL*Loader: Release 10.2.0.2.0 - Production on Sat Feb
17 17:40:33 2007

Copyright (c) 1982, 2005, Oracle. All rights
reserved.

Control File: ora.974848.772490.0.ctl
Character Set WE8ISO8859P1 specified for all input.

Data File: ora.974848.772490.fifo.0
File processing option string: "FIX 479"
Bad File: ora.974848.772490.0.log.bad
Discard File: none specified

(Allow all discards)

Number to load: ALL
Number to skip: 0
Errors allowed: 50
Continuation: none specified
Path used: Direct

Table XXXX, partition YYYY, loaded from
every logical record.
Insert option in effect for this partition: APPEND
The following index(es) on table XXXX were
processed:
index AAAA partition YYY
was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested
index BBBB partition
YYYY was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested
index CCCC partition
YYYY was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested
index DDD partition YYYY
was made unusable due to:
SKIP_INDEX_MAINTENANCE option requested

Table SLS_SBC_LW_DM, partition YYYY:
999999 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were
failed.
0 Rows not loaded because all fields were null.

Date cache:
Max Size: 1000
Entries : 332
Hits : 999667
Misses : 0

Bind array size not used in direct path.
Column array rows : 5000
Stream buffer bytes: 256000
Read buffer bytes: 1048576

Total logical records skipped: 0
Total logical records read: 999999
Total logical records rejected: 0
Total logical records discarded: 0
Total stream buffers loaded by SQL*Loader main thread:
861
Total stream buffers loaded by SQL*Loader load thread:
0

Run began on Sat Feb 17 17:40:33 2007
Run ended on Sat Feb 17 17:44:24 2007

Elapsed time was: 00:03:51.65
CPU time was: 00:00:26.52

Anybody has any solution on the above problem

[ArndW]

I give up.

p.s. Why did you quote your oringal post?

[laxmi_etl]

Sorry, i did not get you.

[narasimha]

ArndW meant, that there is no need to quote your posts, just makes information redundant.

Now if you are not getting any errors in the log file, we might get some clues from the job log messages.
Post the warning/error messages around the job abort message.
If there are none try doing a job reset, see if any new messages get revealed.

[laxmi_etl]

Thank for your reply narasimha.

I got the same error.

[ArndW]

laxmi_etl - you still haven't given us any error message with which to work. Please, post those details.