Severe error(s) occurred in phase PREP_EXTRACT/PREIMP! Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'

[Former Member]

Hi All,

I am trying to update the support pack in solman sp9 to sp14, During that Extraction phase shows some error. Before, i have de installed the solman 7.1.

I have attached the error shot below and log file . Anybody know the solution for this issue.

Log files

4 EPU201XBEGIN OF SECTION BEING ANALYZED LASTOFFSET                 2923 NOW BEGIN OF PREIMP ===================

4 ETW000 F:\usr\sap\SMR\SYS\exe\uc\NTAMD64\R3trans.EXE version 6.24 (release 721 - 31.07.15 - 14:39:42).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 09.03.2016 - 12:43:06

4 ETW000 control file: F:\usr\sap\SMR\SUM14\SUM\abap\tmp\PREIMPTRANS.CTL

4 ETW000 > import

4 ETW000 > file='F:\usr\sap\SMR\SUM14\SUM\abap\bin\R710VPE.SAP'

4 ETW000 > safeandslow=yes

4 ETW000 > buffersync =yes

4 ETW000 > commit     =1048576

4 ETW000 > importtruncated =yes

4 ETW000 R3trans was called as follows: F:\usr\sap\SMR\SYS\exe\uc\NTAMD64\R3trans.EXE -w F:\usr\sap\SMR\SUM14\SUM\abap\tmp\R710VPE.SMR -u 1 F:\usr\sap\SMR\SUM14\SUM\abap\tmp\PREIMPTRANS.CTL

4 ETW000 active unconditional modes: 1

4 ETW000 INFO: no trace information stored

2EETW169 no connect possible: "DBMS = SYBASE --- "

4 EPU202X====MARK ANALYZED SECTION==== END OF PREIMP ================== BEGIN OF PREIMP ====================

4 ETW000 F:\usr\sap\SMR\SYS\exe\uc\NTAMD64\R3trans.EXE version 6.24 (release 721 - 31.07.15 - 14:39:42).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 09.03.2016 - 12:43:24

4 ETW000 control file: F:\usr\sap\SMR\SUM14\SUM\abap\tmp\PREIMPTRANS.CTL

4 ETW000 > import

4 ETW000 > file='F:\usr\sap\SMR\SUM14\SUM\abap\bin\R710VPE.SAP'

4 ETW000 > safeandslow=yes

4 ETW000 > buffersync =yes

4 ETW000 > commit     =1048576

4 ETW000 > importtruncated =yes

4 ETW000 R3trans was called as follows: F:\usr\sap\SMR\SYS\exe\uc\NTAMD64\R3trans.EXE -w F:\usr\sap\SMR\SUM14\SUM\abap\tmp\R710VPE.SMR -u 1 F:\usr\sap\SMR\SUM14\SUM\abap\tmp\PREIMPTRANS.CTL

4 ETW000 active unconditional modes: 1

4 ETW000 INFO: no trace information stored

2EETW169 no connect possible: "DBMS = SYBASE --- "

4 EPU202X====MARK ANALYZED SECTION==== END OF PREIMP ================== BEGIN OF PREIMP ====================

4 ETW000 F:\usr\sap\SMR\SYS\exe\uc\NTAMD64\R3trans.EXE version 6.24 (release 721 - 31.07.15 - 14:39:42).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 09.03.2016 - 13:21:02

4 ETW000 control file: F:\usr\sap\SMR\SUM14\SUM\abap\tmp\PREIMPTRANS.CTL

4 ETW000 > import

4 ETW000 > file='F:\usr\sap\SMR\SUM14\SUM\abap\bin\R710VPE.SAP'

4 ETW000 > safeandslow=yes

4 ETW000 > buffersync =yes

4 ETW000 > commit     =1048576

4 ETW000 > importtruncated =yes

4 ETW000 R3trans was called as follows: F:\usr\sap\SMR\SYS\exe\uc\NTAMD64\R3trans.EXE -w F:\usr\sap\SMR\SUM14\SUM\abap\tmp\R710VPE.SMR -u 1 F:\usr\sap\SMR\SUM14\SUM\abap\tmp\PREIMPTRANS.CTL

4 ETW000 active unconditional modes: 1

4 ETW000 INFO: no trace information stored

2EETW169 no connect possible: "DBMS = SYBASE --- "

4 EPU202XEND OF SECTION BEING ANALYZED END OF PREIMP =======================================================

********************************************************************************************************************************************************************************

[Former Member]

Hallo,

please check the connection to your database as indicated by:

2EETW169 no connect possible: "DBMS = SYBASE --- "

Regards

Thomas

[Former Member]

Hi Thomas.

Database is not connecting in OS level. ISQL utility also is not working . How do connect it.

[Former Member]

Hi Thomas,

I have open the isql utility but isql tool not connecting to database.

Regards

Rajesh

[Former Member]

Hi Thomas,

isql error showing see below

[Former Member]

Hallo,

I am not familiar with ASE.

The only thing I can suggest is to excute "isql -Usa -S <SID>" to get more details on the error and start searching with that error code.

Is the database running?

Regards

Thomas