on 10-11-2008 2:06 PM
I'm doing a upgrade to ECC 6.0 SR2. I'm following the instructions of Upgrade Guide SAP ECC 6.0
SR2.
My Operating System is Windows 2003 Server, database is MS-SQL Server and SAP system source is R3
4.7 Ext 200 non-Unicode
I updated SAPup and included the correction fix in the upgrade root directory (\usr\sap\put\).
The environment variables for all users are:
dbms_type=MSS
mssql_dbname=R37
mssql_schema=r37
mssql_server=<myServer>
The Default Database for users <Server>/R37adm and r37 is R37. The default schema for both users is
r37. Both users are owners of the database.
The default profile have the following parameters (the last line is a blank):
SAPSYSTEMNAME = R37
SAPDBHOST = <myServer>
rdisp/mshost = <myServer>
rdisp/accept_remote_trace_level = 0
rdisp/sna_gateway = <myServer>
rdisp/sna_gw_service = sapgw00
rdisp/bufrefmode = sendoff,exeauto
ms/server_port_0 = PROT=HTTP, PORT=8100
dbms/type = mss
dbs/mss/server = <myServer>
dbs/mss/schema = r37
dbs/mss/dbname = R37
I'm running the PREPARE and shows an error when running the script MSSCONCHECK.SQL.
The error in MSSCONCHECK.LOG is:
Msg 208, Level 16, State 1, Server <myServer>, Line 2
Invalid object name 'SVERS'.
The MSSCONCHECK.OUT is:
SAPup> Starting subprocess osql with id 2828 at 20081011141236
EXECUTING osql -S <myServer> -E -d -i e:\usr\sap\put\bin\MSSCONCHECK.SQL -o
e:\usr\sap\put\log\MSSCONCHECK.LOG -h-1 "-w 100" -n
Environment: dbms_type=MSS
Environment: JAVA_HOME=C:\j2sdk1.4.2_12
Environment: Path=C:\Program Files\Windows Resource
Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL
Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft
SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;E:\usr\sap\R37\SYS\exe\run\
Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
The MSSCONCHECK.SQL is:
setuser 'r37'
select VERSION from SVERS
go
Any idea?
Hello
I got answer to your question
Please follow " Note 908718 - Upgrade - Prepare phase error invalid SVERS Object"
I hope this will definitley solve your problem
Best,
Ganesh Gambhir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Did you updated R3trans and tp programs with the lattest ones? if not then start by doin it, I have seem some extrange errors because this two programs are too old and don´t have all the fixes applied.
Good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I have never got this error during upgrade but from the description i can suggest that :
1. SVERS table is database independant table which stores SAP version
2. Check whether in SE16svers u have 620 as it is 4.7 EE
3. Try to run the commands in script on database level singe single or try to run whole script on sql successfully
just check wether the user in set user is correct as per your settings
4. And then try to continue with Prepare if it works
Please follow also
and I think upgrade guide has something to check login to sql manager
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ganesh Gambhir,
In SE16-SVERS I have "620".
If I execute in command-line:
osql -E -S <myserver> -Q "select VERSION from R37.r37.SVERS" -n
It's shown:
VERSION
------------------------------------------------------------------------
620
(1 row affected)
Any other combination shows the same error:
Msg 208, Level 16, State 1, Server <myServer>, Line 2
Invalid object name 'SVERS'.
I cann't continue with the PREPARE, after this error is closed.
Thanks for your reply. Any other idea?
Anybody has any idea?
more information is needed?
Thanks in advanced
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.