cancel
Showing results for 
Search instead for 
Did you mean: 

Error in ABAP import

Former Member
0 Kudos

Hi Experts,

During SAP ECC6-EHP6 installation ,i am getting error at ABAP Import phase .

After completion of 141 jobs  successfully , one job got strucked & got cancelled .

Kindly find the attached screen shot for details.

Thanks & Regards,

Santosh Kumar Sahu

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member185239
Active Contributor
0 Kudos

Hi Santosh,

While Running the abap import , job get failed due to the following reason

1. tp , R3trans , are of lower version , so replace the tp and R3trans to higher version than the current version.

2. Sometimes the job failed due to inconsistency between the SAP<package>.TSK and SAP<Package>.TSK.bck file . In this scenario you need to repair the .TSK file. To repair it you need to run the command

R3load -make_only <package>.TSK file and retry the installation.

Can you tell me the package name?

With Regards

Ashutosh Chaturvedi

With Regards

Former Member
0 Kudos

Hi Ashutosh ,

Thanks for your reply.

The package name is SAPSSEXC_15.

After executing the R3load -make_only SAPSSEXC_15.TSK command ,it is showing the below error .

'R3load' is not recognized as an internal or external command,operable program or batch file .

Kindly help how to execute the above command along with the location .

Thanks & Regards ,

Santosh Kumar Sahu

Former Member
0 Kudos

Hi ,

Please don't merge the TSK Files.

You should need to do merging only when R3load has termainted abnormally.

Like system crash, or R3load crash...

DONT MERGE THE TSK FILES.

THanks and Regards,

Vimal

former_member185239
Active Contributor
0 Kudos

Hi vamal,

What will be the issue in merging the TSK file?

Can you please explain?

With Regards

Ashutosh Chaturvedi

former_member185239
Active Contributor
0 Kudos

Hi Santosh,

Can you please run the R3trans -d by logging with sidadm and paste the trans.log.

To run the above command

<goto the installation directory>D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load -make_only SAPSSEXC_15.TSK

Please provide the trans.log

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi,

Sometimes it could be due to memory related  issues too. Restart the Installation and continue. If the issue persists then post the sapinst error logs for further analysis.

Regards,

Mudasir

Former Member
0 Kudos

Hi,

Please go to C:\program files\sapinst_instdir\ERPEHP6\AS-ABAP\ORA\CENTRAL folder.

There you can see a file called import_monitor.properties . Open that file... You can see many packages like SAPAPPL=+..

Search for the package which has "=-"  symbol..

Again come back to C:\program files\sapinst_instdir\ERPEHP6\AS-ABAP\ORA\CENTRAL folder.. You can see a log file for the package which has =- symbol in the import_monitor.properties file.

Attach that file so that we an analysis and let you know the solution for the issue.

If you find difficult, attach the import_monitor.properties file.. We will let you know the package that has the error.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi Vimal ,

Thanks for your quick response.

Actually there is no file named import_monitor.properties at the location mentioned by you.May be the file is missing.

There are two import_monitor related file at that location as mentioned below .

1.import_monitor                                       Text Document

2.import_monitor_cmd.properties         Properties file

Kindly help me , how to find the above file so that i can share with you.

Thanks & Regards,

Santosh Kumar Sahu


Former Member
0 Kudos

Hi Santhosh,

I am sorry.

You should be able to find the file name import_state.properties

Open that file and check under which package you are seeing the status as error . I mean which package shows =-

Attach the packagename.log so that we will be able to help you with a possible solution.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi Vimal,

I check the above file & found the same on SAPSSEXC_15=- .

I forwarded the same along with some other error files to your mail id which may be required for analysis .

Kindly check & revert .

Thanks & Regards,

Santosh Kumar Sahu

Former Member
0 Kudos

Hi,

   I am sorry. I didnt get any email from you.

You can also paste the contents of SAPSSEXC_15.log  here

Can you please attach the log in this forum or can you send the log to mjvimalan@gmail.com

?

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi Vimal,

Kindly find below SAPSSEXC_15.log file & also i again resend the other files to your mail id .

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130215082911

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -ctf I D:\ECC6-EHP6\Exports\51044815_part01\51044815_1\DATA_UNITS\EXPORT_1\DATA\SAPSSEXC_15.STR C:\Program Files\sapinst_instdir\ERPEhP6\AS-ABAP\ORA\CENTRAL\DDLORA.TPL SAPSSEXC_15.TSK ORA -l SAPSSEXC_15.log

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job completed

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130215082911

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130215082911

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(SQL) INFO: Searching for SQL file SQLFiles.LST

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file D:\ECC6-EHP6\Exports\51044815_part01\51044815_1\DATA_UNITS\EXPORT_1\DB/SQLFiles.LST

(SQL) INFO: D:\ECC6-EHP6\Exports\51044815_part01\51044815_1\DATA_UNITS\EXPORT_1\DB/SQLFiles.LST not found

(SQL) INFO: Searching for SQL file SSEXC.SQL

(SQL) INFO: SSEXC.SQL not found

(SQL) INFO: Searching for SQL file D:\ECC6-EHP6\Exports\51044815_part01\51044815_1\DATA_UNITS\EXPORT_1\DB/ORA/SSEXC.SQL

(SQL) INFO: D:\ECC6-EHP6\Exports\51044815_part01\51044815_1\DATA_UNITS\EXPORT_1\DB/ORA/SSEXC.SQL not found

(DB) INFO: INDTEXT created #20130215082913

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216034601

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216034605

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216034702

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216034702

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216034844

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216034844

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216035239

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216035239

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216035320

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216035320

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216040027

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216040030

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216040103

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216040104

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216040142

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216040142

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216040224

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216040224

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216040305

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216040305

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216040747

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216040747

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130216083814

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130216083818

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130217014033

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130217014037

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130217015105

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130217015105

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130217111709

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130217111712

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130217115521

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130217115524

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20130217120247

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Oct 20 2010 02:35:52

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_15.cmd -dbcodepage 4103 -l SAPSSEXC_15.log -stop_on_error

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20130217120250

Thanks & Regards ,

Santosh Kumar Sahu

former_member185239
Active Contributor
0 Kudos

Hi Santosh,

Is your database is up and running ?

Provide the status

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Santhosh,

  CONNECT failed with sql error '12541'  error usually occurs when the connectivity between SAP & DB is not happening.. There could be many reasons for this issue... Like maximum number of processes has reached and so on .. Listener might got restarted or manythings.

I would suggest you to perform the following.

1.Check whether listener is running or not... If not, please start the listener.

2.Check what is the status of Oracle.. If it is not running, please start it

3.Start the import now...

It should run fine now.

Try to ping to the DB server and also make sure that it is pinging...

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi Ashutosh,

Database is up & running.

Thanks & Regards ,

Santosh Kumar Sahu

Former Member
0 Kudos

Hi Vimal,

I followed all the steps as mentioned above,but still i am getting the same error.

Thanks & Regards ,

Santosh Kumar Sahu

Former Member
0 Kudos

Hi,

 
Please login to sidadm and start -> Run-> cmd -> sqlplus "/as sysdba"

select status from v$instance.

If you get the output as open then  your DB is running... If you get connected to idle instance , then that means your DB is down.. Try to start it using startup command and retry the installation

I strongly suspect that either sapinst can't connect to DB or DB is down,

Have you maintained the host entry of your DB server in your host file.. Even if DB & CI are in same node, please maintain the entry and check.

Please check the below link for more information.

http://scn.sap.com/thread/3200739

http://www.stechno.net/sap-notes.html?view=sapnote&id=491174

Thanks and Regards,

Vimal

Former Member
0 Kudos

Those screenshots do not help troubleshooting the problem. Attach relevant logs from sapinst_dir.