R3trans error in MS-SQL

Hi SAP Gurus,

We are trying to do a system refresh for the first time in our landscape and do not have any documentation to support the same.

We are through with the restore of the database from the source onto the target.

Now,the database is up and running but however, SAP is not able to connect to the database and subsequently the SAP system is not running.

When we do R3trans -d, we are getting the following error:

This is R3trans version 6.14 (release 700 - 29.05.07 - 13:40:00).

unicode enabled version

2EETW000 sap_dext called with msgnr "2":

2EETW000 -

db call info -

2EETW000 function: db_ntab

2EETW000 fcode: NT_RDTDESCR

2EETW000 tabname: TADIR

2EETW000 len (char): 5

2EETW000 key: TADIR

2EETW000 retcode: 2

R3trans finished (0012).

Can anyone please guide me with the steps to be performed at the database level post-restore?

In ORACLE, I am aware that we need to re-create control files,re-create OPS$users etc.But I am not familiar with MS-SQL 2005.

Would be great of any one of you can guide on the same.

Regards,

Santosh Bhat

SAP Managed Tags:
Microsoft SQL Server

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Hi,

check Note 151603 :Copying an SQL Server database (homogeneous system copy)

you have to execute script attached to following note.

Note 551915 - R/3 won't start after database restore or database copy

regards,

kaushal

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Kaushal,

thanks for your help.

I am aware of the scripts and have managed to changed the schema and owner of the tables back to the original one.

My main concern now is that R3trans -d is not working.It gives the following result:

C:\Documents and Settings\bq0adm>R3trans -d

This is R3trans version 6.14 (release 700 - 29.05.07 - 13:40:00).

unicode enabled version

2EETW000 sap_dext called with msgnr "2":

2EETW000 -

db call info -

2EETW000 function: db_ntab

2EETW000 fcode: NT_RDTDESCR

2EETW000 tabname: TADIR

2EETW000 len (char): 5

2EETW000 key: TADIR

2EETW000 retcode: 2

R3trans finished (0012).

would be great of anyone could suggest what is possibly wrong now.

I feel that once R3trans -d works then my SAP system will be up.

Regards,

Santosh

Hi,

check the environment variable of user bq0adm.

MSSQL_SCHEMA=<sid>

MSSQL_DBNAME=<SID>

MSSQL_SERVER=<sql_server_name>

DBMS_TYPE=mss

regards,

kaushal

Hi Kaushal,

I have checked the same and they seem to be correct.

MSSQL_SCHEMA=bq0

MSSQL_DBNAME=BQ0

MSSQL_SERVER=ALBE0566

DBMS_TYPE=mss

Regards,

Santosh

HI,

provide default.pfl from profile directory.

try to start sap server, if sap server is failed to start then provide dev_w0 from /usr/sap/SDI/<instance>/work directory

regards,

kaushal

Hi Kaushal,

Default profile is as follows:

#.******************************************************************************************************************************

#.* *

#.* Default profile DEFAULT *

#.* *

#.* Version = 000002 *

#.* Generated by user = KONS122 *

#.* Generated on = 16.09.2007 , 20:01:18 *

#.* *

#.******************************************************************************************************************************

SAPDBHOST = ALBE0566

dbms/type = mss

dbs/mss/server = ALBE0566

dbs/mss/dbname = BQ0

dbs/mss/schema = bq0

SAPSYSTEMNAME = BQ0

SAPGLOBALHOST = ALBE0566

rdisp/bufrefmode = sendoff,exeauto

#----

SAP Messaging Service for ABAP

#----

rdisp/mshost = ALBE0566

rdisp/msserv = sapmsBQ0

rdisp/msserv_internal = 3925

#----

INIT: Maintained parameters

#----

#old_value: 001 changed: KONS122 16.09.2007 19:59:32

zcsa/installed_languages = DEK

#parameter created by: KONS122 16.09.2007 20:00:42

zcsa/system_language = K

zcsa/second_language = E

DIR_TRANS =
ALBE0575\sapmnt\trans

DIR_EPS_ROOT =
ALBE0575\sapmnt\trans\EPS

Following is dev_w0 file:

trc file: "dev_w0", trc level: 1, release: "700"

ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ

B Thu Jun 05 14:00:55 2008

B create_con (con_name=R/3)

B Loading DB library 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll' ...

B Library 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll' loaded

B Version of 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll' is "700.08", patchlevel (0.109)

B New connection 0 created

M sysno 25

M sid BQ0

M systemid 562 (PC with Windows NT)

M relno 7000

M patchlevel 0

M patchno 115

M intno 20050900

M make: multithreaded, Unicode, 64 bit, optimized

M pid 4368

M kernel runs with dp version 230000(ext=109000) (@(#) DPLIB-INT-VERSION-230000-UC)

M length of sys_adm_ext is 576 bytes

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4368) [dpxxdisp.c 1301]

I Thu Jun 05 14:00:56 2008

I MtxInit: 30000 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M DpShMCreate: sizeof(wp_adm) 29600 (1480)

M DpShMCreate: sizeof(tm_adm) 5613536 (27928)

M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

M DpShMCreate: sizeof(comm_adm) 552080 (1088)

M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M DpShMCreate: sizeof(slock_adm) 0 (104)

M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M DpShMCreate: sizeof(file_adm) 0 (72)

M DpShMCreate: sizeof(vmc_adm) 0 (1864)

M DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)

M DpShMCreate: sizeof(gw_adm) 48

M DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000F1E0050, size: 6314432)

M DpShMCreate: allocated sys_adm at 000000000F1E0050

M DpShMCreate: allocated wp_adm at 000000000F1E2150

M DpShMCreate: allocated tm_adm_list at 000000000F1E94F0

M DpShMCreate: allocated tm_adm at 000000000F1E9550

M DpShMCreate: allocated wp_ca_adm at 000000000F743D30

M DpShMCreate: allocated appc_ca_adm at 000000000F749AF0

M DpShMCreate: allocated comm_adm at 000000000F74BA30

M DpShMCreate: system runs without slock table

M DpShMCreate: system runs without file table

M DpShMCreate: allocated vmc_adm_list at 000000000F7D26C0

M DpShMCreate: allocated gw_adm at 000000000F7D2740

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 000000000F7D2770

M DpShMCreate: allocated wall_adm at 000000000F7D2780

X EmInit: MmSetImplementation( 2 ).

X MM global diagnostic options set: 0

X <ES> client 0 initializing ....

X Using implementation view

X <EsNT> Using memory model view.

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

M Thu Jun 05 14:00:58 2008

M ThInit: running on host ALBE0566

M Thu Jun 05 14:00:59 2008

M calling db_connect ...

C Thread ID:4308

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 116

C patchcomment MSSQL: Transaction inconsistencies HOTNEWS (1067103)

C np:(local) connection used on ALBE0566

C CopyLocalParameters: dbuser is 'bq0'

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C Provider Release:9.00.2047.00

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C CheckCodepageType: line 24429. hr: 0x80040e37 Invalid object name 'DBPROPERTIES'.

C sloledb.cpp [CheckCodepageType,line 24429]: Error/Message: (err 208, sev 16), Invalid object name 'DBPROPERTIES'.

C Procname: [CheckCodepageType -- no proc]

C Cache sizes: header 104 bytes, 20000 names (32960000 bytes), 500 dynamic statements (2876000 bytes), total 35836104 bytes

C Using shared procedure name cache ALBE0566_BQ0BQ0_BQ0_MEM initialized by another process.

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

C pn_id:ALBE0566_BQ0BQ0_BQ0

C Using MARS (on sql 9.0)

B Connection 0 opened (DBSL handle 0)

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

B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20080605 140059 ALBE0566

C Thu Jun 05 14:01:00 2008

C The IRow interface is supported by this OLEDB provider

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

C Procname: [##Y4ALBE0566bq000000043680000000001140059]

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

C Procname: [##Y4ALBE0566bq000000043680000000001140059]

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

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

C DbSlRead - Error 103 (dbcode 208) on open

C DbSlRead - <##Y4ALBE0566bq000000043680000000001140059>

C DbSlRead - Error 103 (dbcode 208) on fetch

C DbSlRead - <##Y4ALBE0566bq000000043680000000001140059>

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

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

M in_ThErrHandle: 1

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

M Info for wp 0

M stat = WP_RUN

M waiting_for = NO_WAITING

M reqtype = DP_RQ_DIAWP

M act_reqtype = NO_REQTYPE

M rq_info = 0

M tid = -1

M mode = 255

M len = -1

M rq_id = 65535

M rq_source =

M last_tid = 0

M last_mode = 0

M semaphore = 0

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M control_flag = 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 req.vm = no VM

M attachedVm = no VM

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

M *

M * LOCATION SAP-Server ALBE0566_BQ0_25 on host ALBE0566 (wp 0)

M * ERROR ThInit: db_connect

M *

M * TIME Thu Jun 05 14:01:00 2008

M * RELEASE 700

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 10490

M * COUNTER 1

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 724]

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

M Entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 4368) [dpnttool.c 327]

Regards,

Santosh

Hello,

please check if the <sid> Login is part of the sysadmin server role (right click on the login). If this is the case, remove it from this role. It should be part of dbcreator, bulkadmin and serveradmin, but not sysadmin.

Regards

Clas Hortien

Hi,

if solution provide by Mr. Clas Hortien not work then

try to upgrade lib_dbsl patch i.e upgrade kernel patch.

regards,

kaushal

Hi Clas,

Can you please elaborate from where I check these settings?

I am not very familiar with MS-SQL.

I have worked on ORACLE till now.

Regards,

Santosh

Open the SQL Server Management Stuido and connect to your DB server.

Expand Security -> Logins

DoubleClick on the login <sid> (your SAP Systemname in lowercase)

Select the page 'Server Roles' on the left

Check the setting..

Regards

Clas Hortien

Hi Clas,

After connection to my database,I have an option: security->users->bq0

In bq0, i dont have options dbcreator, bulkadmin and serveradmin,sysadmin.

There are options like db_accessadmin,db_backupoperator,db_datareader etc.

Kaushal, Do u mean to say that i should do kernel upgrade on my SAP system?

regards,

Santosh

Hi,

you are looking at the user, but you have to look at the login. Go to the top level branch security -> logins, not into the database.

Regards

Clas Hortien

Hi Clas,

Ok,got it!

Do I need to check the properties for the login which I am using to connect to the database?

I am using the login FALCKDK\bqoadm where FALCKDK is my domain and bq0 is my SID.

There is one more login called 'bq0'.

This 'bq0' is a part of dbcreator, bulkadmin and serveradmin, but not sysadmin.

However, FALCKDK\bq0adm is currently only part of sysadmin,nothing else.

Just let me know if I need to change anything?Or this is perfectly fine.

Regards,

Santosh

Hi,

i have some query.

-> is this your local sap installation or you perform domain installation

-> are you using named instance for sql server or default sql instance

i suggested you to upgrade kernel.

regards,

kaushal

Hi,

this is a domain installation,not local.

Regarding your 2nd query,i think its named instance and not default.I am not too sure abt this one though.

regards,

Santosh

Hi,

thats ok. Under which account is your SAP service (SAPBQ0_00) running ?

Has this user a login in SQL Server ?

Regards

Clas

Hi,

can you please send me the output of

use BQ0

select * from sys.schemas

select schema_id,count(*) from sys.objects group by schema_id

select name,schema_id from sys.objects where name = 'SVERS'

Regards

Clas

HI,

i have doubt about kernel.

from log at starting.

B Loading DB library 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll' ...

B Library 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll' loaded

B Version of 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll' is "700.08", patchlevel (0.109)

dbmssslib.dll' patchno is 109

and in middle of log

M calling db_connect ...

C Thread ID:4308

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'E:\usr\sap\BQ0\DVEBMGS25\exe\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 116

dbmssslib.dll' patchno is 116

i suggest you to upgrade kernel patch.

you get following when you execute r3trans -d

EETW000 sap_dext called with msgnr "2":

2EETW000 -

db call info -

2EETW000 function: db_ntab

2EETW000 fcode: NT_RDTDESCR

2EETW000 tabname: TADIR

2EETW000 len (char): 5

2EETW000 key: TADIR

2EETW000 retcode: 2

R3trans finished (0012).

i found similar error in Note 534765 - db connect fails because of wrong db schema in environment

but is it for oracle and asking to set environment variable for schema user.

one more thing if you used named instance for SQL server

in default profile dbs/mss/server should have following value

dbs/mss/server = <dbservername>\<instance_name>

regards,

kaushal

Hi Klas,

My SAPBQ0_25 service is running under the ID FALCKDK\SAPServiceBQ0 and it has a login in SQL.

Please find the result of the queries:

select * from sys.schemas

NAME SCHEMA_ID PRINCIPAL_ID

dbo 1 1

guest 2 2

INFORMATION_SCHEMA 3 3

sys 4 4

bd0 5 5

bq0 6 6

db_owner 16384 16384

db_accessadmin 16385 16385

db_securityadmin 16386 16386

db_ddladmin 16387 16387

db_backupoperator 16389 16389

db_datareader 16390 16390

db_datawriter 16391 16391

db_denydatareader 16392 16392

db_denydatawriter 16393 16393

select schema_id,count(*) from sys.objects group by schema_id

SCHEMA_ID (NO COLUMN NAME)

6 50540

1 4

4 44

select name,schema_id from sys.objects where name = 'SVERS'

NAME SCHEMA_ID

SVERS 6

Kaushal, we will decide on kernel upgrade on getting Klas's reply.

Since this is not a new installation, kernel upgrade should be an issue.

The test(BQ0) system was running fine before the backup of development system(BD0) was restored on it.

Regards,

Santosh

Hi,

everything looks good so far.

Can you please send me the output of

use master

exec sp_helplogins

use BQ0

exec sp_helpuser

Regards

Clas

Hi,

Result is as follows:

##MS_AgentSigningCertificate## 0x010600000000000901000000CD64A04D2EFC3C572CCDB738322E9D7C27671EE7 master us_english yes no

##MS_SQLAuthenticatorCertificate## 0x010600000000000901000000D22E3279284D08C7BF5EE0CE6529091DDFD9CA17 master NULL NO no

##MS_SQLReplicationSigningCertificate## 0x0106000000000009010000001DEB49CB082EAEBD366A04774B0F3DA4748F4A70 master NULL NO no

##MS_SQLResourceSigningCertificate## 0x0106000000000009010000003F60DEE7193458D3D190E51C09BEDE59E274DDF2 master NULL NO no

ALBE0566\SAP_BQ0_LocalAdmin 0x01050000000000051500000071CF7945F91FF261C7082038F3030000 BQ0 us_english NO no

ALBE0566\SQLServer2005MSFTEUser$ALBE0566$MSSQLSERVER 0x01050000000000051500000071CF7945F91FF261C7082038F0030000 master us_english yes no

ALBE0566\SQLServer2005MSSQLUser$ALBE0566$MSSQLSERVER 0x01050000000000051500000071CF7945F91FF261C7082038EF030000 master us_english NO no

ALBE0566\SQLServer2005SQLAgentUser$ALBE0566$MSSQLSERVER 0x01050000000000051500000071CF7945F91FF261C7082038EE030000 master us_english NO no

BUILTIN\Administrators 0x01020000000000052000000020020000 master us_english NO no

FALCKDK\SAPServiceBQ0 0x010500000000000515000000EB4AEE19A219BA7F2A4F91001C800000 BQ0 us_english NO no

FALCKDK\SQLadmins 0x010500000000000515000000EB4AEE19A219BA7F2A4F9100E4650000 master us_english NO no

FALCKDK\Service_SQL 0x010500000000000515000000EB4AEE19A219BA7F2A4F910055820000 master us_english NO no

FALCKDK\bq0adm 0x010500000000000515000000EB4AEE19A219BA7F2A4F910006800000 BQ0 us_english NO no

NT AUTHORITY\SYSTEM 0x010100000000000512000000 master us_english NO no

bq0 0x8D1925DEFA038241994BF83132DA73B6 BQ0 us_english yes no

sa 0x01 master us_english yes no

##MS_AgentSigningCertificate## master ##MS_AgentSigningCertificate## User

ALBE0566\SQLServer2005MSFTEUser$ALBE0566$MSSQLSERVER master ALBE0566\SQLServer2005MSFTEUser$ALBE0566$MSSQLSERVER User

bq0 BQ0 bq0 User

bq0 master bq0 User

bq0 master db_owner MemberOf

bq0 msdb bq0 User

bq0 msdb db_owner MemberOf

sa master db_owner MemberOf

sa master dbo User

sa model db_owner MemberOf

sa model dbo User

sa msdb db_owner MemberOf

sa msdb dbo User

sa tempdb db_owner MemberOf

sa tempdb dbo User

Regards,

Santosh

Hi,

did you really executed sp_helpuser ? The resultset looks totally different to my one.

The bq0 user is not member of the db_owner role. Please add it by this script:

use BQ0

exec sp_addrolemember 'db_owner','bq0'

Try to start your R/3 then.

Furthermore please send the output of:

use master

exec sp_helpsrvrolemember

use BQ0

exec sp_helprolemember

Best regards

Clas

Hi,

I am agree with Mr. Clas Hortien .

I think you are not successfully execute user_change.sql script attached to sap note 551915

regards,

kaushal

Hi,

I am sorry may there was something wrong earlier.

The result of

use BQ0

exec sp_helpuser is as follows:

INFORMATION_SCHEMA public NULL NULL NULL 3 NULL

bd0 db_owner NULL NULL bd0 5 0x35820750FAE1D845B9754C002A2F4CEB

bq0 public bq0 BQ0 dbo 6 0x8D1925DEFA038241994BF83132DA73B6

dbo db_owner NULL NULL dbo 1 0x0105000000000005150000000E67264DD4D4AC566FBAD89FED030000

guest public NULL NULL guest 2 0x00

sys public NULL NULL NULL 4 NULL

The result of

use master

exec sp_helpsrvrolemember

use BQ0

exec sp_helprolemember

is:

sysadmin sa 0x01

sysadmin BUILTIN\Administrators 0x01020000000000052000000020020000

sysadmin NT AUTHORITY\SYSTEM 0x010100000000000512000000

sysadmin ALBE0566\SQLServer2005MSSQLUser$ALBE0566$MSSQLSERVER 0x01050000000000051500000071CF7945F91FF261C7082038EF030000

sysadmin ALBE0566\SQLServer2005SQLAgentUser$ALBE0566$MSSQLSERVER 0x01050000000000051500000071CF7945F91FF261C7082038EE030000

sysadmin FALCKDK\bq0adm 0x010500000000000515000000EB4AEE19A219BA7F2A4F910006800000

sysadmin FALCKDK\SAPServiceBQ0 0x010500000000000515000000EB4AEE19A219BA7F2A4F91001C800000

sysadmin ALBE0566\SAP_BQ0_LocalAdmin 0x01050000000000051500000071CF7945F91FF261C7082038F3030000

sysadmin FALCKDK\SQLadmins 0x010500000000000515000000EB4AEE19A219BA7F2A4F9100E4650000

sysadmin FALCKDK\Service_SQL 0x010500000000000515000000EB4AEE19A219BA7F2A4F910055820000

serveradmin bq0 0x8D1925DEFA038241994BF83132DA73B6

dbcreator bq0 0x8D1925DEFA038241994BF83132DA73B6

bulkadmin bq0 0x8D1925DEFA038241994BF83132DA73B6

db_owner bd0 0x35820750FAE1D845B9754C002A2F4CEB

db_owner dbo 0x0105000000000005150000000E67264DD4D4AC566FBAD89FED030000

Regards,

Santosh

Hi,

have you run

use BQ0

exec sp_addrolemember 'db_owner','bq0'

as the bq0 is still not member of the db_owner role.

This

use BQ0

exec sp_helprolemember

should return a row like

db_owner bq0 0x3582075.....

Please try to run the following script (open a new query please):

use BQ0

setuser 'bq0'

select top 10 * from SVERS

Did this return any rows ?

Regards

Clas

Hi,

use BQ0

exec sp_helprolemember

gives the result:

db_owner bd0 0x35820750FAE1D845B9754C002A2F4CEB

db_owner bq0 0x8D1925DEFA038241994BF83132DA73B6

db_owner dbo 0x0105000000000005150000000E67264DD4D4AC566FBAD89FED030000

Since,it still shows bd0,could that be a problem?(even though, its showing bq0 as well now after i executed the script you told)

use BQ0

setuser 'bq0'

select top 10 * from SVERS

gave the following:

Msg 208, Level 16, State 1, Line 1

Invalid object name 'SVERS'.

Regards,

Santosh

Hi,

can you please run this:

use BQ0

setuser

exec sp_changedbowner 'sa'

and then again:

use BQ0

setuser

setuser 'bq0'

select top 10 * from SVERS

Any results ?

Clas

Hi,

The first one gave the message command completed successfully.

However, the second one again gave the same result:

Msg 208, Level 16, State 1, Line 1

Invalid object name 'SVERS'.

Regards,

Santosh

Hi,

is this working:

select top 10 * from BQ0.bq0.SVERS

and what is the result of (new query please)

use BQ0

setuser 'bq0'

select user_name()

Regards

Clas

hi Klas,

this one worked and gave the result:

Version

700

One more information i wanted to give u is that the backup-restore was done without shutting down the SAP coz this was done by the database team and they missed it.

Can this be a reason for the system for not coming up now?If yes,then what could be the possible solution?

Regards,

Santosh

And the result of the second script ?

Regards

Clas

Hi,

please run this

use BQ0

setuser

alter user bq0 with default_schema = bq0

and then

use BQ0

setuser

setuser 'bq0'

select * from SVERS

Regards

Clas

Hi,

1.)use BQ0

setuser 'bq0'

select user_name()

gave:

NO COLUMN NAME

bq0

2.) use BQ0

setuser

alter user bq0 with default_schema = bq0

gave:

Command completed successfully

3.) use BQ0

setuser

setuser 'bq0'

select * from SVERS

gives:

Version

700

GOOOD.

Now start the R/3.

Regards

Clas

Hi Klas,

thats really great!!!

The system is up and running now.

Thanks a lot for your guidance.

Can you just give me the steps again needed to perform now?

Since i have to repeat the entire procedure now on my Production system(BP0) on which also the developement system's backup was restored.

so the status is now that restore is complete,now just give me the steps for post-processing so that i can get my production system up and running again.

regards,

Santosh

Hi,

After DB restore you only need to execute user_change.sql script attached to sap note 551915 and ensure that script executed successfully

regards,

kaushal.

Hi,

you should use the STM tools to do the after restore or attach work. See my note 151603 Section 8 for details.

Regards

Clas

Ask a Question

Top Q&A Solution Author

User

Count