SAP system won't start after system copy

[Former Member]

Hi,

I'm performing a system copy using the database restore approach. Once

attached the SAP system will briefly start then fail. R3trans -d does

not work and I've attached the trans.log file. I've ran the script

user_change.sql recommended in another note but this did not resolve

the problem.

Platform is windows 2003, mssql.

Although the trans.log complains that "Conn_i:1 selection:1 singleton:1

flag_fupd:0 use_cursor:0 chksum: 112300

C DbSlRead - Error 103 (dbcode 208) on open

C DbSlRead - <##Y3WLSAPSB0hrs00000055920000000001125810>

C DbSlRead - Error 103 (dbcode 208) on fetch

C DbSlRead - <##Y3WLSAPSB0hrs00000055920000000001125810>

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

1281] [dblink 1281 ]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 004096)

[thxxhead.c 1281]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3,

level 1) [thxxhead.c 9551]

M "

I can select from that table as user hrs (the sid name). I've confirmed

that authentication to MSSQL is mixed and review the db permissions for

hrs, hrsadm, and sapservicehrs.

[Former Member · Accepted solution]

Hi,

Have a look at OSS note 534765.

/Jesper

[Former Member · Accepted solution]

Hi Jesper,

Thanks but we're running MSSQL and that note refers to oracle. It looks very similar though!

Jeff

[Former Member · Accepted solution]

hi jeff,

how did u solve this problem?i am facing similar error when i am doing upgrade. the shadow instance is giving this kind of error.

any sugessions??

Regards

Raghunahth

[Former Member · Accepted solution]

Hi

Check out the note 351586 to solve connection problems with the SQL database.

Mario.