Hello,
please notice. Do not use the user SYSDBA (SUPERDBA) as user for the Contentserver.
The usage of the SUPERDBA will lead into into upgrade and migration problems afterwards.
The default username for the ContentServer user is SAPR3. If this not exist create one and use this user.
The user must be a DBA user with DEFAULTCODE ASCII. The SYSDBA did not has these CODE attributes.
'CREATE USER SAPR3 PASSWORD SAP DBA DEFAULTCODE ASCII'
Kind regards,
Burkhard
used create user but ginving error
dbmcli>sql_execute CREATE USER SAPR3 PASSWORD <pass> SAP DBA DEFAULTCODE ASCII
err-24948,ERR_NODBNAME:Datase name required
Hi,
it seems you are not connected with dbmcli. See dbmcli -d for options.
However for executing SQL command sqlcli should be the preferred tool from the command line
sqlcli -d <db_name> -u SUPERDBA,<password>
>CREATE USER SAPR3 PASSWORD <pass> SAP DBA DEFAULTCODE ASCII
DB Studio is showing the error
User management exception: Cannot connect to host 192.168.10.100:7210 [Connection timed out: connect], -813.
I already checked
> x_server stop
2016-01-21 18:03:48 8544 INF 12905 sdbgloballistener on port 7210 stopped
> x_server start
2016-01-21 18:03:52 6976 INF 12916 Found running XServer on port 7200
2016-01-21 18:03:52 6976 INF 13011 version 'U64/LIX86 7.8.02 Build 041-121-251-982'
2016-01-21 18:03:52 6976 INF 13010 installation sid - path:/sapdb/sid/db
2016-01-21 18:03:52 7584 INF 12798 NISERVER NI support started.
2016-01-21 18:03:52 96992 WNG 12453 NISSLSRV NISSL Init: SSL: Could not locate ticket file
2016-01-21 18:03:52 54048 INF 12903 sdbgloballistener on port 7210 started
> x_server
2016-01-21 18:07:34 91744 INF 12916 Found running XServer on port 7200
2016-01-21 18:07:34 91744 INF 13011 version 'U64/LIX86 7.8.02 Build 041-121-251-982'
2016-01-21 18:07:34 91744 INF 13010 installation sid - path: /sapdb/sid/db
2016-01-21 18:07:34 42528 INF 12916 Found running sdbgloballistener on port 7210
2016-01-21 18:07:34 42528 INF 13011 version 'U64/LIX86 7.8.02 Build 031-121-246-245'
> sdbregview -l
Installation: Global /sapdb/programs
Global Listener 7.8.02.31 valid 64 bit
Installation Compatibility 7.8.02.31 valid 64 bit
Installer 7.8.02.31 valid
SAP Utilities Compatibility 7.8.02.31 valid 64 bit
Installation: SID /sapdb/SID/db
Base 7.8.02.41 valid 64 bit
DB Analyzer 7.8.02.41 valid 64 bit
Database Kernel 7.8.02.41 valid 64 bit
Fastload API 7.8.02.41 valid 64 bit
JDBC 7.6.09.00 valid
Loader 7.8.02.41 valid 64 bit
Messages MSG 0.10269 valid
ODBC 7.8.02.41 valid 64 bit
Redist Python 7.8.02.41 valid 64 bit
SAP Utilities 7.8.02.41 valid 64 bit
SQLDBC 7.8.02.41 valid 64 bit
SQLDBC 76 7.6.06.27 valid 64 bit
SQLDBC 77 7.8.02.41 valid 64 bit
Server Utilities 7.8.02.41 valid 64 bit
Installation: CL_SID /sapdb/clients/SID
Base 7.8.02.41 valid 64 bit
Fastload API 7.8.02.41 valid 64 bit
JDBC 7.6.09.00 valid
Loader 7.8.02.41 valid 64 bit
Messages MSG 0.10269 valid
ODBC 7.8.02.41 valid 64 bit
Redist Python 7.8.02.41 valid 64 bit
SAP Utilities 7.8.02.41 valid 64 bit
SQLDBC 7.8.02.41 valid 64 bit
SQLDBC 76 7.6.06.27 valid 64 bit
SQLDBC 77 7.8.02.41 valid 64 bit
> xinstinfo SID
GlobalDataPath : /sapdb/data
GlobalProgramsPath : /sapdb/programs
PrivateDataPath : /sapdb/SID/data
Rundirectory : /sapdb/SID/data/wrk/SID
InstallationPath : /sapdb/SID/db
Kernelversion : KERNEL 7.8.02 BUILD 041-121-251-982
:~ # /sapdb/programs/bin/sdbverify
Checking installation "Global" (/sapdb/programs, 7.8.02.31)
Checking package Installer
Checking package SAP Utilities Compatibility
Checking package Global Listener
Checking package Installation Compatibility
Checking installation "Legacy" (/sapdb/programs, )
Checking installation "sid" (/sapdb/sid/db, 7.8.02.41)
Checking package Base
Checking package SQLDBC
Checking package SQLDBC 77
Checking package Fastload API
Checking package SQLDBC 76
Checking package SAP Utilities
Checking package Server Utilities
Checking package Database Kernel
Checking package Redist Python
Checking package Loader
Checking package ODBC
Checking package Messages
Checking package JDBC
Checking package DB Analyzer
Checking installation "CL_sid" (/sapdb/clients/sid, 7.8.02.41)
Checking package Base
Checking package SQLDBC
Checking package SQLDBC 77
Checking package Fastload API
Checking package SQLDBC 76
Checking package SAP Utilities
Checking package Redist Python
Checking package Loader
Checking package ODBC
Checking package Messages
Checking package JDBC
Successfully done
> xuser list
-----------------------------------------------------------------
XUSER Entry 1
--------------
Key :DEFAULT
Username :SAPSID
UsernameUCS2 :S.A.P.S.I.D. . . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
Long Password :?????????
Dbname :SID
Nodename :bigmama
Sqlmode :SAPR3
Cachelimit :-1
Timeout 0
Isolation 0
Charset :<unspecified>
-----------------------------------------------------------------
XUSER Entry 2
--------------
Key :w
Username :SUPERDBA
UsernameUCS2 :S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
Long Password :?????????
Dbname :SID
Nodename :bigmama
Sqlmode :SAPR3
Cachelimit :-1
Timeout 0
Isolation 0
Charset :<unspecified>
-----------------------------------------------------------------
XUSER Entry 3
--------------
Key :c
Username :CONTROL
UsernameUCS2 :C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
Long Password :?????????
Dbname :SID
Nodename :bigmama
Sqlmode :SAPR3
Cachelimit :-1
Timeout 0
Isolation 0
Charset :<unspecified>
-----------------------------------------------------------------
XUSER Entry 4
--------------
Key :c_J2EE
Username :CONTROL
UsernameUCS2 :C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
Long Password :?????????
Dbname :SID
Nodename :bigmama
Sqlmode :SAPR3
Cachelimit :-1
Timeout 0
Isolation 0
Charset :<unspecified>
Prashanth Bidare wrote:
In case of connect problems of an SAP system (e.g. R3trans, the work processes, ...) you should always check the XUSER data.
To maintain the XUSER data you can use Database Manager CLI (DBMCLI) or XUSER. How the XUSER entries should look like for an SAP system is described in note 39439.
Hi Prashanth,
I already check the user list using command "xuser list", and it shows all users required to be put in xuser list: SAP<SID> (SAPBAP), CONTROL, SUPERDBA.
bapadm> xuser list
-----------------------------------------------------------------
XUSER Entry 1
--------------
Key :DEFAULT
Username :SAPBAP
UsernameUCS2 :.S.A.P.B.A.P. . . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
PasswordUTF8 :?????????
Dbname :BAP
Nodename :devbap
Sqlmode :SAPR3
Cachelimit :-1
Timeout 
Isolation
Charset :<unspecified>
-----------------------------------------------------------------
XUSER Entry 2
--------------
Key :c
Username :CONTROL
UsernameUCS2 :.C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
PasswordUTF8 :?????????
Dbname :BAP
Nodename :devbap
Sqlmode :SAPR3
Cachelimit :-1
Timeout
Isolation
Charset :<unspecified>
-----------------------------------------------------------------
XUSER Entry 3
--------------
Key :c_J2EE
Username :CONTROL
UsernameUCS2 :.C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
PasswordUTF8 :?????????
Dbname :BAP
Nodename :devbap
Sqlmode :SAPR3
Cachelimit :-1
Timeout
Isolation
Charset :<unspecified>
-----------------------------------------------------------------
XUSER Entry 4
--------------
Key :w
Username :SUPERDBA
UsernameUCS2 :.S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . .
Password :?????????
PasswordUCS2 :?????????
PasswordUTF8 :?????????
Dbname :BAP
Nodename :devbap
Sqlmode :SAPR3
Cachelimit :-1
Timeout
Isolation
Charset :<unspecified>
Thanks,
Kris
Anand Naroji wrote:
can you please check following link for reference
Hi Anand,
I check on your link, all user list has correct DB name as we can see from the "xuser list" result I mentioned above
Thanks,
Kris
Hi Kris,
first check if you have the right passwords and user names.
To check you should a native MaxDB tool like sqlcli instead of R3trans.
>sqlcli -d BAP -n devbap-u SAPBAP,<pwd> select user from dual
and next test the XUSER entry with the option -U <xuserkey>.
>sqlcli -U DEFAULT select user from default
Burkhard
Burkhard Diesing wrote:
Hi Kris,
first check if you have the right passwords and user names.
To check you should a native MaxDB tool like sqlcli instead of R3trans.
>sqlcli -d BAP -n devbap-u SAPBAP,<pwd> select user from dual
and next test the XUSER entry with the option -U <xuserkey>.
>sqlcli -U DEFAULT select user from default
Burkhard
Hi Burkhard,
Here is the result when I execute your sql command mentioned above:
Using user SAPBAP:
sqlcli -d BAP -n devbap -u SAPBAP,<pwd> select user from dual
* -4008: POS(1) Unknown user name/password combination SQLSTATE: 28000
* -4008: POS(1) Unknown user name/password combination SQLSTATE: 28000
Using user SUPERDBA:
sqlcli -d BAP -n devbap -u SUPERDBA,<pwd> select user from dual
| EXPRESSION1 |
| -------------------------------- |
| SUPERDBA |
1 row selected (619 usec)
Since the database restored from BAD, I try to execute using user SAPBAD
sqlcli -d BAP -n devbap -u SAPBAD,<pwd> select user from dual
| EXPRESSION1 |
| -------------------------------- |
| SAPBAD |
1 row selected (1388 usec)
sqlcli -U DEFAULT select user from default
* -4008: POS(1) Unknown user name/password combination SQLSTATE: 28000
I think the user SAPBAP does not exist in the database. How to convert or changes the user from SAPBAD into SAPBAP?
Thanks,
Kris
Hello Kris,
first check which users are exists on the database
>sqlcli -d BAP -n devbap -u SUPERDBA,<pwd> select username from users
If the user exists try to set the password new to ensure that you have the correct one.
>sqlcli -d BAP -n devbap -u SUPERDBA,<pwd> alter password SAPBAP <pwd>
Then try to connect again with sqlcli an user SAPBAP
Burkhard
Burkhard Diesing wrote:
Hello Kris,
first check which users are exists on the database
>sqlcli -d BAP -n devbap -u SUPERDBA,<pwd> select username from users
If the user exists try to set the password new to ensure that you have the correct one.
>sqlcli -d BAP -n devbap -u SUPERDBA,<pwd> alter password SAPBAP <pwd>
Then try to connect again with sqlcli an user SAPBAP
Burkhard
Hi Burkhard,
The SAPBAP user does not exist. Below is the result:
devbap:> sqlcli -d BAP -n devbap -u SUPERDBA,<pwd> select username from users
| USERNAME |
| -------------------------------- |
| CONTROL |
| SUPERDBA |
| SAPBAD |
3 rows selected (8320 usec)
Thanks,
Kris
You have a user SAPBAD.
Was the system copy from your development system BAD?
Burkhard Diesing wrote:
You have a user SAPBAD.
Was the system copy from your development system BAD?
HI Burkhard,
Yes, it was system copy from BAD.
Thanks,
Kris
Kris Adrianto wrote:
HI Burkhard,
Yes, it was system copy from BAD.
Thanks,
Kris
The user SAPBAD owns all tables and data of your SAP System.
So the user SAP User exists but did not has the right name.
I am not an upgrade expert. I guess you have not made a simple system copy. This was a system copy and system rename.
You should check the system copy guides and note. If a manual rename user is required. I guess it should happen when you execute the rename tasks.
Burkhard
Hi,
please check whether you can reach the database.
From the server where Database Studio is installed execute
c:\sapdb\clients\DatabaseStudio\bin\x_ping -d <database> -n <servername>.
Or on you server, where MaxDB is installed execute:
/sapdb/<id>/db/bin/x_ping localhost.
Please tell us the result.
Regards,
Barbara
x_ping -d SID -n bigmama
Pinging SID on bigmama with 512 bytes of data over a maximum of 10 hops.
Hop Server
0 XServer
1 SID
SID: reply time=904us
SID: reply time=653us
SID: reply time=552us
SID: reply time=502us
SID: reply time=533us
SID: 'UNKNOWN'
Approximate round trip times:
Minimum = 502us, Maximum = 904us, Average = 628us
x_ping localhost
Checking connection to 'localhost' ... ok.
Version of Server is
----------------------------------------------------------
UNKNOWN
----------------------------------------------------------
Burkhard Diesing wrote:
Kris Adrianto wrote:
HI Burkhard,
Yes, it was system copy from BAD.
Thanks,
Kris
The user SAPBAD owns all tables and data of your SAP System.
So the user SAP User exists but did not has the right name.
I am not an upgrade expert. I guess you have not made a simple system copy. This was a system copy and system rename.
You should check the system copy guides and note. If a manual rename user is required. I guess it should happen when you execute the rename tasks.
Burkhard
Hi,
I was checking on Note http://service.sap.com/sap/support/notes/129352 and there is one command I have to execute to rename the SAP<SID> user:
dbmcli -d <new_database_name> -u <dbm_operator>,<password> -uSQL <database_system_administrator>,<password> sql_execute rename user SAP<SAPSID> to SAP<NEWSID>
or using this command in database studio:
sql_execute rename user SAP<SAPSID> to SAP<NEWSID>
Thanks,
Kris
This looks good.
Does DB Studio still show an error?
If you still see the error in DB Studio, try the following check on java level.
1. On the windows server, where Database Studio is installed, search for sapdbc.jar. It could be under c:\sapdb\clients\SID\runtime\jar
2. cd \sapdb\clients\DatabaseStudio
3. java -jar C:\sapdb\clients\SID\runtime\jar\sapdbc.jar -d SID -n 192.168.10.100:7210 -u <superdba>,<pwd> -a db_state
Assuming that 192.168.10.100 is still the bigmama server.
4. On the AIX server execute:
x_cons SID show act
What are the results of 3. andl 4.?
Regards,
Barbara
Hello Daniel,
what is the result of
dbmcli -d SDB -u superdba,admin user_get superdba
Can you try to load the the system tables with
dbmcli -d DBM,control load_systab -u superdba,admin
Kind regards,
Burkhard
Hi Burkhard
output from 1st command:
I:\sapdb\programs\pgm>dbmcli -d SDB -u superdba,admin user_get superdba
OK
SERVERRIGHTS=UserMgm,InstallMgm,SystemCmd,DBFileRead,AccessUtility,Recovery,Back
up,ParamFull,ParamCheckWrite,ParamRead,AccessSQL,ExecLoad,LoadSysTab,DBStop,DBSt
art,DBInfoRead,SharedMemoryMgm,SchedulerMgm,Scheduling,EvtDispMgm,EvtDisp
GUIRIGHTS=
SECONDPASSWORD=NO
DISABLED=NO
COMMENT=
USERTYPE=DBA
EXTERNAL_IDS=
MASTER_PW_ALTER_TIME=2016-01-28 15:04:48
second did not worked due to wrong syntax, but probably you mean:
I:\sapdb\programs\pgm>dbmcli -d SDB -u DBM,control load_systab -u superdba,admin
ERR
-24907,ERR_DBAWRONG: wrong SYSDBA
I:\sapdb\programs\pgm>
Still not working
BR
Daniel
Hallo Daniel,
could you please check if your sysdba is the superdba.
Try it with sqlcli
sqlcli -d SDB -u superdba,admin select sysdba from dual
use table SYSDD.VERSION instead of dual. Table dual is loaded by load_systab
Message was edited by: Burkhard Diesing