Problem with Importing Basis SP of PI 7.1

[Former Member]

Hi!

I don´t know if this is the right forum. If not please feel free to move it to another one.

I have the following problem with a PI 7.1 System and a SP.

It´s a fresh installed system!

Post-Installation stepps finished.

We imported alle Java SPs including the Kernel (up to 7.10.123.0).

Now we wanted to start with patching the ABAP stack with SP SAP Basis KB71005 to KB71006.

But during the phase IMPORT_PROPER there is an Error stop.

Import Log of queue:

sap_dext called with msgnr 1:
   db call info
function:   db_report_interface
fcode:      OPEN_LINE_UPDATE
tabname:    SOURCE
len (char): 40
key:        RSALEXTI
retcode:    1
SQL error 1205 accessing 1205: [Microsoft][SQL Native Client][SQL Server]Transact
Main import
End date and time : 20081001220633
Ended with return code:  ===> 12 <===

In the detailed log file is:

[dev trc     ,00000]  Wed Oct 01 22:06:33 2008                         677927921  681.628631
4 ETW000  [dev trc     ,00000]  ERROR: -1 in function ExeNormalModify (execute) [line 12383]
4 ETW000                                                                             275  681.628906
4 ETW000  [dev trc     ,00000]  (1205) [40001] [Microsoft][SQL Native Client][SQL Server]Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
4 ETW000                                                                              86  681.628992
4 ETW000  [dev trc     ,00000]  pid[4612] Deadlock in ExeNormalModify - slodbc.c line 12383 [Microsoft][SQL Native Client][SQL Server]Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
4 ETW000                                                                              81  681.629073
4 ETW000  [dev trc     ,00000]  DBREPO: report table: 'REPOSRC                                 '
4 ETW000                                                                           11297  681.640370
4 ETW000  [dev trc     ,00000]  DBREPO: program: 'RSALEXTI                                '
4 ETW000                                                                              57  681.640427
4 ETW000  [dev trc     ,00000]  DBREPO: state: A, lang = D, mach = 16427              28  681.640455
4 ETW000  [dbrepo      ,00000]  ***LOG BY4=>sql error 1205   performing UPD on table REPOSRC   
4 ETW000                                                                           11199  681.651654
4 ETW000  [dbrepo      ,00000]  ***LOG BY0=>[Microsoft][SQL Native Client][SQL Server]Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
4 ETW000                                                                              67  681.651721
2EETW000 sap_dext called with msgnr "1": 
2EETW000 ---- db call info ----
2EETW000 function:   db_report_interface
2EETW000 fcode:      OPEN_LINE_UPDATE
2EETW000 tabname:    SOURCE
2EETW000 len (char): 40
2EETW000 key:        RSALEXTI                                
2EETW000 retcode:    1
2EETW125 SQL error "1205" during "1205" access: "[Microsoft][SQL Native Client][SQL Server]Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."
1 ETP154 MAIN IMPORT
1 ETP110 end date and time   : "20081001220633"
1 ETP111 exit code           : "12"
1 ETP199 ######################################

I have no idea about this error because the last time we didn´t get it with another maschine.

Does anyone has an advice??

Thanks in advance!

[Former Member]

Hi Geraldine,  We are faced with the same situation.  Would you please share the fix with us?  Thank you!

[Former Member]

Hi Geraldine,

I have read OSS messages with the same problem,

there are special instructions which only SAP

active global support is allowed to use.

Please open an OSS message on component BC-UPG-OCS

- the more information you initially provide the quicker

the solution process will be.

Hope this helps.

kr,

andreas

[Former Member]

Hi Andreas!

There are or were no other activities. We upgraded the Kernel with JSPM.

SGEN ran last night.

We restarted the Instance. But now the Java Server isn´t startint anymore and when continue the import in spam we get an runtime error:

Syntax error in program "SAPLTMSP ".

What happened?
    Error in the ABAP application program.

    The current ABAP program "SAPLSTPA" had to be interrupted because it contains
    a statement that cannot be executed.

    In the include "LTMSPTOP " in the line 5 of program "SAPLTMSP " the following
     syntax
    errors occur:
    "TYPE-POOL "CTSC" is unknown"
    " "
    " "
    " "

    Author and last person to change the include are:
    Author "SAP "
    Last changer "SAP "

Error analysis
    The following syntax error was found in the program SAPLTMSP :
    "TYPE-POOL "CTSC" is unknown"
    " "
    " "
    " "

Trigger Location of Runtime Error
    Program                                 SAPLSTPA
    Include                                 LSTPAU10
    Row                                     17
    Module type                             (FUNCTION)
    Module Name                             TRINT_TP_GET_PROFILE_NAME

Line  SourceCde

    1 FUNCTION TRINT_TP_GET_PROFILE_NAME.
    2 *"----------------------------------------------------------------------
    3 *"*"Lokale Schnittstelle:
    4 *"       EXPORTING
    5 *"             VALUE(EV_TPPARAM) LIKE  STPA-FILE
    6 *"             VALUE(EV_VERSION) LIKE  STPA-VERSION
    7 *"       EXCEPTIONS
    8 *"              TMS_PM_NOT_ACTIVE
    9 *"----------------------------------------------------------------------
   10
   11 DATA: LS_PVERS               LIKE TMSPVERS.
   12
   13 * set default profile name
   14   EV_TPPARAM = GC_TPPARAM.
   15
   16 * get tp profile name from TMS profile manager
>>>>>   CALL FUNCTION 'TMS_PM_READ_PROFILE_NAME'
   18        IMPORTING
   19             EV_PROFILE_NAME  = LS_PVERS-PRONAM
   20             EV_VERSION       = LS_PVERS-VERSION
   21        EXCEPTIONS
   22             PM_NOT_ACTIVE    = 1
   23             OTHERS           = 99.
   24   IF SY-SUBRC <> 0.
   25     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
   26             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
   27             RAISING TMS_PM_NOT_ACTIVE.
   28   ENDIF.
   29
   30 * fill export variables
   31   IF LS_PVERS-PRONAM <> SPACE.
   32     EV_TPPARAM = LS_PVERS-PRONAM.
   33     EV_VERSION = LS_PVERS-VERSION.
   34   ENDIF.
   35
   36 ENDFUNCTION.

So what to do?

[Former Member]

Hi Geraldine,

seems to be a database deadlock on table

REPOSRC, which holds the sap report sources.

Are there any other activites on the system ? Sometimes

when you have been doing a kernel upgrade, after

restart of the sap instances, the report sources have

to be newly generated - this is done automatically.

I suggest you run transaction SGEN and then start

the import of packages again.

Kind regards,

Andreas