cancel
Showing results for 
Search instead for 
Did you mean: 

import ABAP taking too much time

Former Member
0 Kudos

hi all,

we are installing sap PRD server with system copy using export of DEV (EHP4) with MAXDB 7.7.

For last 2 days it is at import ABAP step with completed 10 job, 3 running , 35 waiting.

Plz guide .

Best Regards

Khan

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> we are installing sap PRD server with system copy using export of DEV (EHP4) with MAXDB 7.7.

> For last 2 days it is at import ABAP step with completed 10 job, 3 running , 35 waiting.

It seems you used only 3 import processes in parallel. Since ERP 6.0 EHP4 is huge using only three processes will take a lot of time.

How big is your database CacheSize? How many CPUs do you have in that machine?

Markus

hannes_kuehnemund
Active Contributor
0 Kudos

As Markus said, only 3 import processes is not much. My rule of thumb is: take no. of CPU and multiply by 2. CPU wise this has been always OK for me, however, the storage much be capable of writing that much data. Also, make sure that you have enough MaxDB DataDevs for more than 3 import processes.

Also, when you export you might want to sprint large tables (like the DD* ones) to have a mich higher degree of parallelization.

Best, Hannes

Former Member
0 Kudos

Hi,

Now for last 6 days it is at the step, log size is not increasing.

server detail is given below

fdisk -l

Disk /dev/sda: 598.8 GB, 598879502336 bytes
255 heads, 63 sectors/track, 72809 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       68602   551045533+  83  Linux
/dev/sda2           68603       72809    33792727+  82  Linux swap / Solaris

CPU 4 quardcore

[root@prdsap ~]# cat /proc/cpuinfo | grep processor | wc -l
16

Database CacheSize is default we have change it.

Best Regards

Imran Khan

Former Member
0 Kudos

RAM size 16 GB

Former Member
0 Kudos

hi,

please guide me , the server is at the same step.

1) stop & rety with with old installation ?

2) uninstall sap & then install with system copy of expoted DEV (EHP4) ?

if we go with 2), then what r the pre requisite for new installation ?

Regards

Imran

Former Member
0 Kudos

hi,

we have stop installation and restarted it , showing error below

/

usr/sap/PRD/SYS/exe/run/R3load: START OF LOG: 20110510165905

/usr/sap/PRD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PRD/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Oct 29 2010 23:58:03
/usr/sap/PRD/SYS/exe/run/R3load -ctf I /sap_dumps/db_export1/ABAP/DATA/SAPSSEXC_7.STR /tmp/sapinst_instdir/ERPEhP4/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/DDLADA.TPL SAPSSEXC_7.TSK ADA -l SAPSSEXC_7.log 


/usr/sap/PRD/SYS/exe/run/R3load: job completed
/usr/sap/PRD/SYS/exe/run/R3load: END OF LOG: 20110510165905

/usr/sap/PRD/SYS/exe/run/R3load: START OF LOG: 20110510165905

/usr/sap/PRD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PRD/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Oct 29 2010 23:58:03
/usr/sap/PRD/SYS/exe/run/R3load -i SAPSSEXC_7.cmd -dbcodepage 4103 -k 1W5fd5M50Dh01eqteAY91Qm4 -l SAPSSEXC_7.log -nolog -c 50000 

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running: no request pipe))

(DB) ERROR: db_connect rc = 256
DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running: no request pipe))

(DB) ERROR: DbSlErrorMsg rc = 99

/usr/sap/PRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/PRD/SYS/exe/run/R3load: END OF LOG: 20110510165905

/usr/sap/PRD/SYS/exe/run/R3load: START OF LOG: 20110511171632

/usr/sap/PRD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/PRD/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Oct 29 2010 23:58:03
/usr/sap/PRD/SYS/exe/run/R3load -i SAPSSEXC_7.cmd -dbcodepage 4103 -k 1W5fd5M50Dh01eqteAY91Qm4 -l SAPSSEXC_7.log -nolog -c 50000 

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[-907] POS(1) Space for user session exhausted))

(DB) ERROR: db_connect rc = 256
DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[-907] POS(1) Space for user session exhausted))

(DB) ERROR: DbSlErrorMsg rc = 99

/usr/sap/PRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/PRD/SYS/exe/run/R3load: END OF LOG: 20110511171633

Plz guide

Regards

Khan

markus_doehr2
Active Contributor
0 Kudos

your database is not running...

Markus

Former Member
0 Kudos
prdsap:sqdprd 1> dbmcli -d prd -u control,Sap00Prd
dbmcli on prd>db_state
OK
State
ONLINE

---
dbmcli on prd>

Db is running

markus_doehr2
Active Contributor
0 Kudos

Can you check KnlMsg (using protconv or better DBStudio) for any hints?

Markus

Former Member
0 Kudos

hi master,

how we execute it on bdmcli

Former Member
0 Kudos

prdsap:sqdprd 16> protconv /var/opt/sdb/data/wrk/PRD/KnlMsg

Thread  0x1D5 Task     66  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     25  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task      6  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task      8  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     10  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task      9  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     24  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     23  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     11  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     12  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     22  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     13  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     14  2011-05-11 23:12:01 WNG FBM        20004:  No more free blocks on data volumes available
Thread  0x1D5 Task     21  2011-05-11 23:12:01 WNG FBM        20004:  No more fr

markus_doehr2
Active Contributor
0 Kudos

Seems your database is full (probably because of temporary pages building up a huge index).

Add a volume.

Markus

Former Member
0 Kudos

hi master ,

we have did below

dbmcli on prd>param_put MAXDATAVOLUMES 64
OK

---
dbmcli on prd>param_commitsession
OK

is it ok.

Best Regards

Imran

markus_doehr2
Active Contributor
0 Kudos

> we have did below

>

>

dbmcli on prd>param_put MAXDATAVOLUMES 64
> OK
> 
> ---
> dbmcli on prd>param_commitsession
> OK

So you enable the system for more volumes - but did you actually add the volume (a new database file)?

Markus

Former Member
0 Kudos

hi master,

we have added new volume , now import is at the end only 2 jobs are remaining. but now it is showing error.

SAPSSEXC_2.log

(DB) INFO: DD01L deleted/truncated#20110513215006

(DB) INFO: Savepoint on database executed#20110513215009

(IMP) INFO: import of DD01L completed (81173 rows) #20110513215009

(DB) ERROR: DDL statement failed
 (DROP INDEX "DD01L~1" ON "DD01L")
 DbSlExecute: rc = 103
  (SQL error -4011)
  error message returned by DbSl:
POS(13) Unknown index name:DD01L~1
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DD01L~1 created#20110513215009

ERROR : Execute for create index STERM_LINK~001 on STERM_LINK failed (dbrc=102).
  (SQL error -955)
  error message returned by DbSl:
SQL-Statement: CREATE  INDEX "STERM_LINK~001" ON "STERM_LINK" ( "OBJECT"  )  
POS(1) Duplicate name

/usr/sap/PRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/PRD/SYS/exe/run/R3load: END OF LOG: 20110513215009

Regards

Khan

Former Member
0 Kudos

(DB) INFO: DD01L deleted/truncated#20110513215006

(DB) INFO: Savepoint on database executed#20110513215009

(I

MP) INFO: import of DD01L completed (81173 rows) #20110513215009
 
(DB) ERROR: DDL statement failed
 (DROP INDEX "DD01L~1" ON "DD01L")
 DbSlExecute: rc = 103
  (SQL error -4011)
  error message returned by DbSl:
POS(13) Unknown index name:DD01L~1
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DD01L~1 created#20110513215009
 
ERROR : Execute for create index STERM_LINK~001 on STERM_LINK failed (dbrc=102).
  (SQL error -955)
  error message returned by DbSl:
SQL-Statement: CREATE  INDEX "STERM_LINK~001" ON "STERM_LINK" ( "OBJECT"  )  
POS(1) Duplicate name
 
/usr/sap/PRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/PRD/SYS/exe/run/R3load: END OF LOG: 20110513215009

Former Member
0 Kudos

master we have done this

sqlcli PRD=> DROP INDEX "STERM_LINK~001" ON "STERM_LINK"
0 rows affected (12.804 msec)

and then retry but error is same

(DB) ERROR: DDL statement failed
 (DROP INDEX "DD01L~1" ON "DD01L")
 DbSlExecute: rc = 103
  (SQL error -4011)
  error message returned by DbSl:
POS(13) Unknown index name:DD01L~1
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DD01L~1 created#20110517154519

ERROR : Execute for create index STERM_LINK~001 on STERM_LINK failed (dbrc=102).
  (SQL error -955)
  error message returned by DbSl:
SQL-Statement: CREATE  INDEX "STERM_LINK~001" ON "STERM_LINK" ( "OBJECT"  )  
POS(1) Duplicate name

/usr/sap/PRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/PRD/SYS/exe/run/R3load: END OF LOG: 20110517154519

please guide we are stuck.

Best Regards

Khan

Former Member
0 Kudos

we are closing this it and creating new message

Answers (1)

Answers (1)

Former Member
0 Kudos
import_monitor.java.log

Import Monitor jobs: running 1, waiting 47, completed 0, failed 0, total 48.

Import Monitor jobs: running 2, waiting 46, completed 0, failed 0, total 48.

Import Monitor jobs: running 3, waiting 45, completed 0, failed 0, total 48.

Loading of 'DOKCLU' import package: OK

Import Monitor jobs: running 2, waiting 45, completed 1, failed 0, total 48.

Import Monitor jobs: running 3, waiting 44, completed 1, failed 0, total 48.

Loading of 'SAPAPPL1_1' import package: OK

Import Monitor jobs: running 2, waiting 44, completed 2, failed 0, total 48.

Import Monitor jobs: running 3, waiting 43, completed 2, failed 0, total 48.

Loading of 'DYNPSOURCE' import package: OK

Import Monitor jobs: running 2, waiting 43, completed 3, failed 0, total 48.

Import Monitor jobs: running 3, waiting 42, completed 3, failed 0, total 48.

Loading of 'SAPNTAB' import package: OK

Import Monitor jobs: running 2, waiting 42, completed 4, failed 0, total 48.

Import Monitor jobs: running 3, waiting 41, completed 4, failed 0, total 48.

Loading of 'REPOSRC' import package: OK

Import Monitor jobs: running 2, waiting 41, completed 5, failed 0, total 48.

Import Monitor jobs: running 3, waiting 40, completed 5, failed 0, total 48.

Loading of 'SAPAPPL2_1' import package: OK

Import Monitor jobs: running 2, waiting 40, completed 6, failed 0, total 48.

Import Monitor jobs: running 3, waiting 39, completed 6, failed 0, total 48.

Loading of 'DD03L' import package: OK

Import Monitor jobs: running 2, waiting 39, completed 7, failed 0, total 48.

Import Monitor jobs: running 3, waiting 38, completed 7, failed 0, total 48.

Loading of 'SAPSSEXC_5' import package: OK

Import Monitor jobs: running 2, waiting 38, completed 8, failed 0, total 48.

Loading of 'SAPAPPL2_2' import package: OK

Import Monitor jobs: running 1, waiting 38, completed 9, failed 0, total 48.

Import Monitor jobs: running 2, waiting 37, completed 9, failed 0, total 48.

Import Monitor jobs: running 3, waiting 36, completed 9, failed 0, total 48.

Loading of 'SAPAPPL0_3' import package: OK

Import Monitor jobs: running 2, waiting 36, completed 10, failed 0, total 48.

Import Monitor jobs: running 3, waiting 35, completed 10, failed 0, total 48.

former_member182034
Active Contributor
0 Kudos

Dear Imran,

the current log is OK.

first check the log of Import packages(specially that which is currently executing) and if the size of log is increasing then you still have to wait and if not then you vl restart the the installation.

please send log of import_monitor.log.

Regards,