SPAM Problem Importing SAPKNA7007-SAPKNA7012 (IDES ERP6-SR2 / SQL2005x64)

[Former Member]

Hello Everybody!

I am facing the following error during the IMPORT_PROPER phase of SP SAPKNA7012 and I am stuck at this point.

I am looking forward for your valuable help and assistance.

-Error in phase: IMPORT_PROPER

-Reason for error: TP_STEP_FAILURE

-Return code: 0008

-Error message: OCS Package SAPKNA7012, tp step "I", return code

-0008

Import Log

Start import R3TRSXCIPRT_GENERATOR_EXIT ...

0 entries from TADIR deleted

0 entries from CLS_ASSIGNMENT deleted

0 entries from CLS_LINKED_OBJ deleted

0 entries from TADIR (R3TRSXCIPRT_GENERATOR_EXIT ) deleted.

0 entries from ENHOBJ (SXCIPRT_GENERATOR_EXIT

0 entries from SXC_ATTR (PRT_GENERATOR_EXIT ) deleted.

Syslog: k CQ3 : UMGSETTING& rscpexcc 12

GetDBMigrateCodePagesLangs uses TCP0D, TCPDB, TCP0C.

[dev trc ,00000] Thu Oct 30 09:03:19 2008 11700121 11.700121

[dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13241]: Error/Message: (err 601, sev 0), Could not continue scan with NOLOCK

56 11.700177

[dev trc ,00000] Procname: [##Y4NETWEAVEecc00000007040000000089090307]

24 11.700201

[dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 99. stmt:

38 11.700239

[dev trc ,00000] SELECT COUNT(*) FROM SXC_ATTRT 14 11.700253

[dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000

25 11.700278

[dev trc ,00000] dbdsmss: DBSL99 SQL601 29 11.700307

[dev trc ,00000] Could not continue scan with NOLOCK due to data movement.

25 11.700332

[dbds ,00482] ***LOG BY2=>sql error 601 performing OPC [dbds#1 @ 482]

4889 11.705221

[dbds ,00482] ***LOG BY0=>Could not continue scan with NOLOCK due to data movement. [dbds#1 @ 482]

26 11.705247

SQL error 601 occured: Could not continue scan with NOLOCK due to data movement.

End import R3TRSXCIPRT_GENERATOR_EXIT (with warnings)

[Former Member · Accepted solution]

Thank you Gaurav:

I trust the follwoing details are needed for the analysis of this issue.

Latest Patches

SAPKD70029 SPAM/SAINT Update - Version 700/0029 Imported on 24.10.2008 at 13:16:43

+SAPKA70017 ABA Support Package 17 for 7.00 Imported on 27.10.2008 at 23:32:48 +

SAPKB70017 Basis Support Package 17 for 7.00 Imported on 27.10.2008 at 23:07:37

+SAPKITLQI6 ST-PI 2005_1_700: Patch 0006 Imported on 28.10.2008 at 00:00:36 +

SAPKIPYJ7H PI_BASIS 2005_1_700: patch 0017 Imported on 28.10.2008 at 00:20:16

SAPKW70019 BW Support Package 19 for 7.00 Imported on 28.10.2008 at 07:54:49

SAPKIBHD06 LCAPPS 2005_700: patch 0006 Imported on 28.10.2008 at 08:02:00

SAP Kernel Information

SAP Kernel : 700_REL

Database Client Library : SQL_Server_8.00

created in : NT 5.2 3790 Service Pack 1 x86 MS VC+ 14.00+

created on : Oct 5 2008 23:03:26

Support Level : 0

Kernel Patch number : 180

Source ID : 0.180

DBSL Patch No. : 180

ICU Version : 3.0 Unicode Version 4.0.1

libsapu16 Version : 2.0025 Oct 5 2008 19:14:24

Supported Environment

SAP Database Version

700

Database

MSSQL 7.00.699 or higher

MSSQL 8.00.194

Operating System

windows nt 5.0

windows nt 5.1

windows nt 5.2

windows nt 6.0

[Former Member · Accepted solution]

Hi,

Your kernel level is too low.. the latest available kernel is

PL175 for windows/MSSql/32bit/Unicode. The latest R3trans is

PL183 and TP is PL179. Please make a backup copy of your

existing kernel and update your latest kernel. if you want to

know how to upgrade kernel just let me know.

Cheers!!!

Gaurav

[Former Member · Accepted solution]

Hi Ali,

Go through this note 965530 , which discuss about the same error Error/Message: (err 601, sev 0), Could not continue scan with NOLOCK 56 11.700177. Hope you will get some idea after reading this note.

Regards

KVR

[Former Member · Accepted solution]

Thanks a lot KVR...

I have already gone through the notes and there is a tangible progress.

I will deeply look into it and I will soon give my feedback.

Best regards,

[Former Member · Accepted solution]

Hi Ali,

Have you tried patching the TP in sap kernel?

Regards,

Pandu

[Former Member · Accepted solution]

Terrific!

The root cause of the issue has been defined as shown below and the issue is closed with the last resort (dbcc checkdb(<SID>, REPAIR_ALLOW_DATA_LOSS) with ALL_ERRORMSGS).

The recovery is in process.

Thanks for the hint.

Sincerely,

Product: Windows Operating System

ID: 52

Source: Disk

Version: 5.2

Symbolic Name: IO_WRN_FAILURE_PREDICTED

Message: The driver has detected that device %1 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.

[Former Member · Accepted solution]

Thank you Pandu.

According to the information provided, I think the latest UC-Kernel patches including tp_179-20001354.sar for Windows Server2003x64 are already installed as Basis and ABAP patch level 17 are already imported.

Your cooperation is appreciated.

Regards,

[Former Member]

.

[Former Member]

Thanx pandu.

Just to make it clear, are you suggesting to re-import the OCS SAPKNA7012 Files (CSR0120031469_0029605.*)?

Well, the process is at the IMPORT_PROPER phase of SPAM and I can not move a head or back forward. However, I need to complete the IMPORT of this patch.

Regards,

[Former Member]

Hi,

I agree with you. You cant move when it is in

IMPORT_PROPER phase. Have you upgraded your kernel and

tp /R3trans because most of the time it resolve the problem.

Best of luck,

Gaurav

[Former Member]

Hi,

you downloaded patch from service marketplace to your server it self right. then try to extract that patch using command SAPCAR u2013xvf SAPKNA7012.CAR extract.

then go to path cd /usr/sap/trans there u can see in folder with in in folder u can see .ATT and .PAT 2files will be extracted then restart the server.

Now go to SPAM there you can see ur SAPKNA7012 Patch will be there u try to extract that.

by doing this procedure your problem will be solved......