cancel
Showing results for 
Search instead for 
Did you mean: 

error create DDLOG table

yonghun_lee
Explorer
0 Kudos
199


I am trying SAP installation on MS 2012 Server and MSS Server 2012.

I encountered an error during installation.

When I checked in SAPSPROT.log file, I found below message.

(DB) ERROR: DDL statement failed

(CREATE TABLE [DDLOG] ( [SEQNUMBER] int NOT NULL default 0 , [TIMESTAMP] nvarchar(26) NOT NULL default N' ' , [SYSTEMID] nvarchar(22) NOT NULL default N' ' , [NBLENGTH] smallint NOT NULL default 0 , [NOTEBOOK] varbinary(MAX) NULL  )  WITH ( DATA_COMPRESSION = ROW ) )

DbSlExecute: rc = 99

  (SQL error 1754)

When I executed above SQL sentence, create table is OK.

But SAPInst program pop up below message.

   


      An error occurred while processing option SAP NetWeaver 7.3 > MS SQL
      Server > SAP Systems > Application Server ABAP > Standard System >
      Standard System( Last error reported by the step: Program 'Migration
      Monitor' exits with error code 103. For details see log file(s)
      import_monitor.java.log, import_monitor.log.)
. You can now:
   

       Choose Retry to repeat the current step.
       Choose Log Files to get more information about the error.
     

        Stop the option and be able to continue later.
        

       Log files are written to C:\Program
      Files/sapinst_instdir/NW730/MSS/INSTALL/STD/ABAP
.
   

So, After I execute MS-SQL Profiler function , I retried installation.

and I found create SQL sentence likes below.

CREATE TABLE [DDLOG] ( [SEQNUMBER] int IDENTITY(1,1) NOT NULL default 0 , [TIMESTAMP] nvarchar(26) NOT NULL default N' ' , [SYSTEMID] nvarchar(22) NOT NULL default N' ' , [NBLENGTH] smallint NOT NULL default 0 , [NOTEBOOK] varbinary(MAX) NULL  )  WITH ( DATA_COMPRESSION = ROW )

I found out that two SQL sentence in log file and real SQL is difference. and MS-SQL couldn't understand above SQL sentence because IDENTITY can't use with DEFAULTS Value in SQL.

I wondering that the SQL sentence was generated by SAP installer is wrong sentence.

I want to solve this problem as soon as possible.

Please let me know the solution!!!

Thanks in advance~~

Accepted Solutions (0)

Answers (1)

Answers (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Park,

Can you share full logs for this stage and import monitor logs. Also, which kernel are you using.

yonghun_lee
Explorer
0 Kudos

KERNEL VERSION : SAP NETWEAVER 7.3 OS/DB dependent Components Number 51044252


Belows is Import Monitor.Log file
----------------------------------------------------------------------------------------------------------------------

INFO: 2014-08-17 15:00:18
Import Monitor is started.

CONFIG: 2014-08-17 15:00:18
Application options:
collectLogicalPackages=false
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=D:\BACK_UP_TEST\NW_ABAP_Installatoin_Export\51043284\DATA_UNITS\EXP1;D:\BACK_UP_TEST\NW_ABAP_Installatoin_Export\51043284\DATA_UNITS\EXP2;D:\BACK_UP_TEST\NW_ABAP_Installatoin_Export\51043284\DATA_UNITS\EXP3
installDir=C:\Program Files\sapinst_instdir\NW730\MSS\INSTALL\STD\ABAP
jobNum=3
loadArgs=-loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\BAK\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes

CONFIG: 2014-08-17 15:00:18
List of packages with table structure: 'SAP0000'.

CONFIG: 2014-08-17 15:00:18
List of packages with views: 'SAPVIEW'.

TRACE: 2014-08-17 15:00:18 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\NW730\MSS\INSTALL\STD\ABAP\DDLMSS.TPL' template file is started.

INFO: 2014-08-17 15:00:18 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\NW730\MSS\INSTALL\STD\ABAP\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.

INFO: 2014-08-17 15:00:18
Data codepage 1100 is determined using TOC file 'D:\BACK_UP_TEST\NW_ABAP_Installatoin_Export\51043284\DATA_UNITS\EXP1\DATA\REPOSRC.TOC' for package 'REPOSRC'.

INFO: 2014-08-17 15:00:18
Version table 'SVERS' is found in STR file 'D:\BACK_UP_TEST\NW_ABAP_Installatoin_Export\51043284\DATA_UNITS\EXP3\DATA\SAPNTAB.STR' from package 'SAPNTAB'.

INFO: 2014-08-17 15:00:18
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\BACK_UP_TEST\NW_ABAP_Installatoin_Export\51043284\DATA_UNITS\EXP3\DATA\SAPNTAB.STR' from package 'SAPNTAB'.

INFO: 2014-08-17 15:00:18 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 1, completed 27, failed 0, total 29  Package Group  max threads: 3 current running threads : 0 processing package: SAPSPROT

TRACE: 2014-08-17 15:00:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.

TRACE: 2014-08-17 15:00:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' starting import package into database:
D:\usr\sap\BAK\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast

INFO: 2014-08-17 15:00:19 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 1, completed 27, failed 1, total 29  error processing of package SAPSPROT

ERROR: 2014-08-17 15:00:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is interrupted with R3load error.
Process 'D:\usr\sap\BAK\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSPROT.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: 2014-08-17 15:00:48
Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2014-08-17 15:00:48
1 error(s) during processing of packages.

INFO: 2014-08-17 15:00:48
Import Monitor is stopped.

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Park.

Have a look at any oher details hat you can post in other logs.

Options - what you can do

1. Update kernel patch with DBSL.

2. Check package size - SAPSPROT - check if the is not inconsistent - compare bits on your disk and marketplace.

Regards,

Divyanshu