cancel
Showing results for 
Search instead for 
Did you mean: 

SAP ERP 6.0 EHP5Installation Error:ABAP Import phase error at SEOSUBCODF.TSK error

Former Member
0 Kudos

Dear Members

I am facing the issue while installation of SAP ERP 6.0 EHP5 in AWS cloud at the import abap phase please find below about error:-

ERROR: 2016-12-12 05:15:29 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is interrupted with R3load error.
Process '/usr/sap/<SID>/SYS/exe/run/R3load -i SEOSUBCODF.cmd -dbcodepage 4103 -l SEOSUBCODF.log -nolog -c 50000 -force_repeat -loadprocedure dbsl' exited with return code 2.
For mode details see 'SEOSUBCODF.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: 2016-12-12 05:15:41
Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2016-12-12 05:15:41
1 error(s) during processing of packages.

INFO: 2016-12-12 05:15:41
Import Monitor is stopped

This is the error log i am getting while installation please help me out as sson as possible.

Thanks in Advance.

In need of your valuable solutions.

Regards,

Sanjeev

Accepted Solutions (1)

Accepted Solutions (1)

alichtenau
Advisor
Advisor
0 Kudos

Dear Sanjeev,

please provide us the database logs as follows:

If the Installed version is lower than 7.7:

All files contained in the /sapdb/data/wrk/<SID> folder.
Please also attach the xserver_* and dbm* files from /sapdb/data/wrk/.
Please ensure to provide the 'lcinit.log' file if available.

If Installed version is 7.7. or higher:

In database server, please execute the command:

 'dbmcli -d <dbname> -u <dbm>, <dbm> diag_pack' 

The archive 'diagpkg.tgz' is generated at /sapdb/data/wrk/<SID> for 7.7 or at /sapdb/<SID>/data/wrk/<SID> as of 7.8.

Cheers,
Andreas

Answers (5)

Answers (5)

hendrikweise
Employee
Employee

Dear Sanjeev,

since you also created a support incident for that problem, watch my replies in there too.

The used installation material in general is very old and must be replaced as I wrote. It's not only the kernel that needs

to be updated.


Regards,

Hendrik

Reagan
Advisor
Advisor
0 Kudos

>>(DB) ERROR: db_connect rc = 256 DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[1] database not accesssible: pipe open (6:N)) (DB) ERROR: DbSlErrorMsg rc = 99<<

It says connect to database failed. Install MaxDB Database Studio and connect to the database. Check if the database is running fine. As this is a new installation check the MaxDB log area and data area and see if they are OK. If there are space related issues, you need to fix them before you can continue further.

alichtenau
Advisor
Advisor
0 Kudos

One question I also asked: Is the database up and running?

There were problems in the past with the tools and dbsl patch, but if the DB is running fine has not yet been answered

Former Member
0 Kudos

Dear Andreas,

Database is running and everything looks good in database level.

Regards,

Sanjeev

Former Member
0 Kudos

Hi Reagan

MaxDB log area and data area are sufficient and Ok .

And Database is also Running fine.

Regards,

Sanjeev

alichtenau
Advisor
Advisor
0 Kudos

Hi Sanjeev,

according to the logfile your error is below one:

/usr/sap/SHD/SYS/exe/run/R3load: version R7.20/V1.4 [UNICODE]
Compiled May  6 2010 20:24:58/usr/sap/SHD/SYS/exe/run/R3load -i SEOSUBCODF.cmd -dbcodepage 4103 -l SEOSUBCODF.log -nolog -c 50000 -force_repeat -loadprocedure dbsl 
DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[1] database not accesssible: pipe open (6:N)) (DB) ERROR: db_connect rc = 256 DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[1] database not accesssible: pipe open (6:N)) (DB) ERROR: DbSlErrorMsg rc = 99 

Please check SAP Note 2362647 in order to resolve the issue.

Best regards,
Andreas

Former Member
0 Kudos

Dear Andreas,

Thank you for the response.

Accordingly what are the possible solutions and note you mentioned almost everything fulfilled but still issue not yet resolved.

Regards,

Sanjeev

alichtenau
Advisor
Advisor
0 Kudos

Hey Sanjeev,

when I see the logs I can also see that there is an old R3load in use (/usr/sap/SHD/SYS/exe/run/).

Is it possible that you change the kernel to the latest 721/722 and repeat the SWPM and attach the new logs if it should fail again?

Also: Is the database up and running?

Best regards,
Andreas

Former Member
0 Kudos

Hey Andreas,

I will look into your steps.

One thing i need to get clarification

If i need to change kernel again i need to start installation from first step from SWPM i cannot start from where i left ,can you confirm me about this?

Or else can i upgrade only R3load app in kernel?

Regards,

Sanjeev

Former Member
0 Kudos

Dear Andres,

Thank you for your quick response.

I am working On SAP MAXDB database,Please find attchment of the log with this comment.

Regards,

Sanjeev seosubcodf.txt

alichtenau
Advisor
Advisor
0 Kudos

Hi Sanjeev,

you only posted the warnings, but not the errors.

In the past there were known errors because of an old DBSL file (check SAP Note 1642058). If this is the case then please install a newer DBSL patch and proceed in SWPM.

If this is not helpful then please attach the file "SEOSUBCODF.log".


Best regards,
Andreas

Former Member
0 Kudos

Dear Andreas,

Can you please let me know the steps to attach DBSL file.I am using Maxdb database

Regards,

Sanjeev