on 07-02-2013 3:57 PM
I use SUM to upgrade from EHP5 to EHP6 and NW EHP2 to EHP3.
In the phase PREP_GENCHECKS/CONFCHK! i got an error that the connection to the database can not be done.
The system is green and everyone can login. No errors to connect to database, but the SUM prints this error:
here is the log file from TOOLOUT.LOG
SAPup> Starting subprocess in phase 'CONFCHK' at 20130627112419
ENV: JAVA_HOME=C:\j2sdk1.4.2_22-x64
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: SAPSYSTEMNAME=IS9
ENV: dbs_mss_schema=IS9
ENV: PATH=C:\usr\sap\IS9\DVEBMGS00\exe
EXECUTING C:\usr\sap\IS9\DVEBMGS00\exe\tp.EXE pf=C:\usr\SUM\abap\var\DEFAULT.TPP getdbinfo IS9
TRACE-INFO: 1: [ dev trc,00000] Thu Jun 27 11:24:19 2013 1514 0.001514
TRACE-INFO: 2: [ dev trc,00000] DlLoadLib success: LoadLibrary("dbmssslib.dll"), hdl 0, addr 000007FEEC140000
TRACE-INFO: 3: 12 0.001526
TRACE-INFO: 4: [ dev trc,00000] using "C:\usr\sap\IS9\DVEBMGS00\exe\dbmssslib.dll" 7 0.001533
TRACE-INFO: 5: [ dev trc,00000] Thread ID:5124 1151 0.002684
TRACE-INFO: 6: [ dev trc,00000] Thank You for using the SLODBC-interface 10 0.002694
TRACE-INFO: 7: [ dev trc,00000] Using dynamic link library 'C:\usr\sap\IS9\DVEBMGS00\exe\dbmssslib.dll' 15 0.002709
TRACE-INFO: 8: [ dev trc,00000] dbmssslib.dll patch info 35 0.002744
TRACE-INFO: 9: [ dev trc,00000] SAP patchlevel 0 8 0.002752
TRACE-INFO: 10: [ dev trc,00000] SAP patchno 401 8 0.002760
TRACE-INFO: 11: [ dev trc,00000] Last MSSQL DBSL patchlevel 0 8 0.002768
TRACE-INFO: 12: [ dev trc,00000] Last MSSQL DBSL patchno 324 8 0.002776
TRACE-INFO: 13: [ dev trc,00000] Last MSSQL DBSL patchcomment Local connection to a named instance does not use LPC (1782171)
TRACE-INFO: 14: 14 0.002790
TRACE-INFO: 15: [ dev trc,00000] ODBC Driver chosen: SQL Server Native Client 10.0 native 372 0.003162
TRACE-INFO: 16: [ dev trc,00000] lpc:(local) connection used on isu2005uc 130 0.003292
TRACE-INFO: 17: [ dev trc,00000] lpc:(local) connection used on isu2005uc 13902 0.017194
TRACE-INFO: 18: [ dev trc,00000] lpc:(local) connection used on isu2005uc 3431 0.020625
TRACE-INFO: 19: [ dev trc,00000] Driver: sqlncli10.dll Driver release: 10.50.2769 3479 0.024104
TRACE-INFO: 20: [ dev trc,00000] GetDbRelease: 10.50.2769.00 328 0.024432
TRACE-INFO: 21: [ dev trc,00000] GetDbRelease: Got DB release numbers (10,50,2769,0) 12 0.024444
TRACE-INFO: 22: [ dev trc,00000] ERROR: -1 in function ExecuteAndFlush (SQLExecDirect) [line 6814] 3944 0.028388
TRACE-INFO: 23: [ dev trc,00000] (102) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'execute.'.
TRACE-INFO: 24: 19 0.028407
TRACE-INFO: 25: [ dev trc,00000] <if user_name() != 'IS9' execute as login = suser_sname(suser_sid('IS9')) with no revert> failed -- connect terminated
TRACE-INFO: 26: 27 0.028434
TRACE-INFO: 27: [ dblink ,00000] ***LOG BY2=>sql error 102 performing CON 52 0.028486
TRACE-INFO: 28: [ dblink ,00000] ***LOG BY0=>Incorrect syntax near 'execute.'. 10 0.028496
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: Connect to IS9 failed (20130627112419, probably wrong environment).
SAPup> Process with PID 4868 terminated with status 232 at 20130627112419!
Have anyone an idea how to solve this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
nothing has changed after done the notes.
the fixscript output shows
-----------------------------------------
Jul 4 2013 9:05:25 Starting ..
Jul 4 2013 9:05:25 UserID and SchemaID are the same.
Jul 4 2013 9:05:25 Nothing to do. Exiting.
------------------------------------------
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Found the following for Snotes/KBAs:
Ranking | Application Area | Number | Short text | Released On | ||
---|---|---|---|---|---|---|
1. | 0.220 | BC-EHP-INS | 1758017 | SYB: Add. Info - Software Update Manager 1.0 SP07 | 05/29/2013 | |
2. | 0.220 | BC-EHP-INS | 1741993 | SYB: Add. Info - Software Update Manager 1.0 SP06 | 01/08/2013 | |
3. | 0.220 | BC-EHP-INS | 1711269 | SYB: Add. Info - Software Update Manager 1.0 SP05 | 10/11/2012 | |
4. | 0.220 | BC-EHP-INS | 1664769 | SYB: Additional Info - Software Update Manager 1.0 SP04 | 08/29/2012 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have checked all my releases:
the kernel is 7.21 EXT UC with release 100.
the mssql libs are the newest 117 (dbmssslib.dll,...)
the environment variables are all set how it is discribed in note 1684408
I have also chekced the note 1775206
the execute of
( use IS9
select schema_id('is9'), user_id('is9') )
results (5 | 5 )
any other ideas?
Hi
Kindly check the below mention SAP Notes
Note 1086375 - User ID/Schema ID inconsistency in SQL database
Note 1656672 - tp getdbobjsize returns size 0 for all objects
Thanks
Sriram
Hi Sven,
Please check the following, maybe this is somehow "different":
Compare the Windows login name to the login name stored in SQL Server, use for example
SELECT SUSER_SNAME(SUSER_SID('COMPUTERNAME\User', 0)) ;
Because when you said The system is green and everyone can login. No errors to connect to database, I assume you did check R3trans -d, and I was curious regarding these error message (
execute as login = suser_sname(suser_sid('IS9')) with no revert> failed -- connect terminated
ERROR: Connect to IS9 failed (20130627112419, probably wrong environment).
), which mentioned about "probably wrong environment" between the users.
I hope this will help you.
Hi
Kindly go thru the 1. sap Note 1665882 - DBCON-connect: Incorrect syntax near 'max'
2. In the SAPSID user all the environment variable are set in the right way
3. check the Kernel & DBSL patch level for MS Sql DB
Thanks
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.