Disputer suddenly stop after copy SQL data

[Former Member]

i had a problem doing a R3 copy from an old server to a new server. The old server currently running on 4.7x200 sr1 and sql 2000(SP3) on window 2000 server and the new server are using window 2003 server with the same SAP version (i want the new server to be same level of application with the old server because its easier for me to migrate the data) using the exact schema configuration (SAPSID and DB instance) before i can upgrade it to ECC 6.0.When i copied the data to the new server, i can see the old data on SQL Server Enterprise and when i run the SAPmgmt, theres only 2 component that still running except for the disp+work.Here's the error that i get when i open the log in the dev_w7 file :

-

---

trc file: "dev_w7", trc level: 1, release: "640"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, M

*

B

B Tue Jan 09 20:12:32 2007

B create_con (con_name=R/3)

B Loading DB library 'D:\usr\sap\SD4\SYS\exe\run\dbmssslib.dll' ...

B Library 'D:\usr\sap\SD4\SYS\exe\run\dbmssslib.dll' loaded

B Version of 'D:\usr\sap\SD4\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.26)

B New connection 0 created

M systemid 560 (PC with Windows NT)

M relno 6400

M patchlevel 0

M patchno 25

M intno 20020600

M make: multithreaded, ASCII

M pid 3488

M

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 7 3488) [dpxxdisp.c 1160]

I MtxInit: -2 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: JAVA is not active

M DpShMCreate: sizeof(wp_adm) 6624 (828)

M DpShMCreate: sizeof(tm_adm) 2219848 (11044)

M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

M DpShMCreate: sizeof(comm_adm) 192000 (384)

M DpShMCreate: sizeof(vmc_adm) 0 (320)

M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

M DpShMCreate: SHM_DP_ADM_KEY (addr: 05230040, size: 2505416)

M DpShMCreate: allocated sys_adm at 05230040

M DpShMCreate: allocated wp_adm at 052317A8

M DpShMCreate: allocated tm_adm_list at 05233188

M DpShMCreate: allocated tm_adm at 052331B0

M DpShMCreate: allocated wp_ca_adm at 054510F8

M DpShMCreate: allocated appc_ca_adm at 05455748

M DpShMCreate: allocated comm_adm_list at 05456EB8

M DpShMCreate: allocated comm_adm at 05456ED0

M DpShMCreate: allocated vmc_adm_list at 05485CD0

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 05485CF8

M DpShMCreate: allocated wall_adm at 05485D00

X EmInit: MmSetImplementation( 2 ).

X <ES> client 7 initializing ....

X Using implementation std

M <EsNT> Memory Reset enabled as NT default

X ES initialized.

M

M Tue Jan 09 20:12:33 2007

M calling db_connect ...

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'D:\usr\sap\SD4\SYS\exe\run\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 26

C patchcomment MSSQL: GetNextMsst1 error (754819)

C np:(local) connection used on SD4

C Failed to initialize provider SQLNCLI. See note #734034 for more information.

C Using provider SQLOLEDB instead.

C Provider Release:08.10.1830

C Failed to initialize provider SQLNCLI. See note #734034 for more information.

C Using provider SQLOLEDB instead.

C Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes

C Initializing shared procedure name cache SD4_SD4SD4_SD4_MEM.

C procedure cache created/attached

C PnSetup: line 330. hr: 0x80040e09 SELECT permission denied on object 'sysobjects', database 'SD4', owner 'dbo'.

C sloledb.cpp [PnSetup,line 330]: Error/Message: (err 229, sev 0), SELECT permission denied on object 'sysobjects', database 'SD4', owner 'dbo'.

C Procname: [PnSetup - no proc]

C Connected to db server : [SD4] server_used : [np:(local)], dbname: SD4, dbuser: SD4

C pn_id:SD4_SD4SD4_SD4

B Connection 0 opened

B Wp Hdl ConName ConId ConState TX PRM RCT MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE NO YES NO 255 255 20070109 201233 SD4

C The IRow interface is supported by this OLEDB provider

C sloledb.cpp [ParamStmtExec,line 11774]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.

C Procname: [##Y2SD4SD400000034480000000001201233]

C sloledb.cpp [ParamStmtExec,line 11774]: Error/Message: (err 208, sev 16), Invalid object name 'SVERS'.

C Procname: [##Y2SD4SD400000034480000000001201233]

C ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT VERSION AS c FROM SVERS ]

C Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 112156

C DbSlRead - Error 103 (dbcode 208) on open

C DbSlRead - <##Y2SD4SD400000034480000000001201233>

C DbSlRead - Error 103 (dbcode 208) on fetch

C DbSlRead - <##Y2SD4SD400000034480000000001201233>

B ***LOG BZA=> table SVERS does not exist on database [dblink#1 @ 1281] [dblink 1281 ]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 004096) [thxxhead.c 1271]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9379]

M

M Info for wp 7

M

M stat = 4

M reqtype = 6

M act_reqtype = -1

M rq_info = 0

M tid = -1

M mode = 255

M len = -1

M rq_id = 65535

M rq_source = 255

M last_tid = 0

M last_mode = 0

M int_checked_resource(RFC) = 0

M ext_checked_resource(RFC) = 0

M int_checked_resource(HTTP) = 0

M ext_checked_resource(HTTP) = 0

M report = > <

M action = 0

M tab_name = > <

M

M *****************************************************************************

M *

M * LOCATION SAP-Server SD4_SD4_61 on host SD4 (wp 7)

M * ERROR tskh_init: db_connect

M *

M * TIME Tue Jan 09 20:12:33 2007

M * RELEASE 640

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 9555

M * COUNTER 1

M *

M *****************************************************************************

M

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 730]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 246]

M Entering ThSetStatError

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M

M Tue Jan 09 20:12:34 2007

M ***LOG Q02=> wp_halt, WPStop (Workproc 7 3488) [dpnttool.c 357]

can someone help?

[Former Member]

Hi,

It seems to be a problem with permission to Your database. Check following log:

PnSetup: line 330. hr: 0x80040e09 SELECT permission denied on object 'sysobjects', database 'SD4', owner 'dbo'.
C sloledb.cpp [PnSetup,line 330]: Error/Message: (err 229, sev 0), SELECT permission denied on object 'sysobjects', database 'SD4', owner 'dbo'.
C Procname: [PnSetup - no proc]
C Connected to db server : [SD4] server_used : [np:(local)], dbname: SD4, dbuser: SD4
C pn_id:SD4_SD4SD4_SD4

Your user don't have permission on object 'sysobjects'. Check permission for user DBO and database SD4.

Regards,

Marcin Gajewski

[Former Member]

hi Marcin,

when i opened the permission for dbo it doesnt responds. I think this user are from the old server because i didnt import the data accordingly, i just overwrite the .mdf to the default SQL directories. I also cannot drop the user since its a sa user account. Is there any way that i can overwrite the user with the new one?

[Former Member]

Hi,

Check following OSS note 551915 and download attachment (user_restore.zip).

These sql statements help You to add new database logins and owners.

Regards,

Marcin Gajewski

please reward points for helpful answer

[Former Member]

Hi,

please have a look at note 610640. There is a stored procedure attached (sp_check_sap_login) which helps you to analyze your login problems. It is even capable to repair your system.

Regards,

Sven

[Matt_Fraser]

Hazrienne,

After copying the .mdf (and presumably .ndf and .ldf) file(s) to the new server and attaching them, you must run the "SAP Tools for SQL Server" before you try to start the R/3 system. This is described in detail in Notes 683447 and 151603. Note 193816 is also useful, and of course the "Homogeneous and Heterogeneous System Copy" guide, for systems based on WebAS 6.20 or 6.40, which you can find at http://service.sap.com/instguides. Did you miss this step?

Regards,

Matt