Loading of ‘SAPDFACT’ import package: ERROR

Symptom

You are doing a system copy activity and during the system import phase – below error coming out,

import_monitor

ERROR: 2014-10-11 14:38:12 com.sap.inst.migmon.LoadTask run
Loading of ‘SAPDFACT’ import package is interrupted with R3load error.
Process ‘E:\usr\sap\SID\SYS\exe\nuc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 1100 -l SAPDFACT.log -stop_on_error’ exited with return code 2.
For mode details see ‘SAPDFACT.log’ file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

WARNING: 2014-10-11 14:38:41
Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2014-10-11 14:38:41
1 error(s) during processing of packages.

INFO: 2014-10-11 14:38:41
Import Monitor is stopped.

ImportMonitor.console

Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.
Loading of ‘SAPDFACT’ import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.

import_monitor.java

java version “1.6.0_75”
Java(TM) SE Runtime Environment (build 6.1.068)
SAP Java Server VM (build 6.1.068 24.55-b13, Jun 22 2014 00:31:35 – 61_REL – optU – windows amd64 – 6 – bas2:220276 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.
Loading of ‘SAPDFACT’ import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.

Solution

There are multiple causes for this error. You can find the root cause from the SAPDFACT.log file. So, here’s the error that causing the import of SAPDFACT to be failed (for our case),

SAPDFACT.log

(SQL) INFO: DFACT.SQL not found
(SQL) INFO: Searching for SQL file H:\EXPORT_DATA\ABAP\DB/ORA/DFACT.SQL
(SQL) INFO: H:\EXPORT_DATA\ABAP\DB/ORA/DFACT.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX “/BI0/E0ALM_C01~P”)
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 1408 in exec_immediate() from oci_execute_stmt(), orpc=0

DbSl Trace: ORA-01408 occurred at SQL stmt (parse error offset=55)

(DB) ERROR: DDL statement failed
(CREATE INDEX “/BI0/E0ALM_C01~P” ON “/BI0/E0ALM_C01” ( “KEY_0ALM_C01P” , “KEY_0ALM_C01T” , “KEY_0ALM_C01U” , “KEY_0ALM_C011” , “KEY_0ALM_C012” , “KEY_0ALM_C013” ) TABLESPACE PSAPSR3 STORAGE (INITIAL 0000000016K NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB

Based on the SAP Note 885441, the error is occurred during the index creation. Here is the solution,

1. Open the SAPDFACT.TSK file and look up for index with err (meaning error) at the front. Change to ign (meaning ignore). Save and resume the execution again. Do the same steps if the error popping up again.

Example,

/BI0/E0ALM_C01~P err to /BI0/E0ALM_C01~P ign

2. Once the execution is completed. Login to the SAP system and execute report SAP_INFOCUBE_INDEXES_REPAIR using transaction code SE38. The report will repair all the cubes in bulk.

Note

You will be getting below message notification after all ABAP loads been imported. Click on OK because you will be executing the report SAP_INFOCUBE_INDEXES_REPAIR once the system copy is completed.