on 2024 Jul 31 12:27 PM
Hello,
in the Moment, i am trying to install a Netweaver AS Java System on a MaxDB in Windows 11. I already reinstalled the Server, but there is the same Mistake every Time. As you can see in the Image, the Problem is the Creation of the SAPMDADB user (SAP SID is MDA), with the Password "*". Interestingly, when i try to do it with the DBADMIN in the MaxDB Studio, than it do not work either. If i change the Password to [for example] Abcd0123 it has no Problem. Do i have to change the Password Policy or what can i change?
It is a Test System and our only one running Windows because we only need to test Scripts, i can change everything possible. Thanks in advance!
unfortunately i can not get your point. i think you should use another password then "*" , this is no sufficient passwords. why you do not use your ABC123d password? there should no problem with your os password restrictions sap<sid>db Schema User is in the database.
you mentioned, that you deinstalled/reinstalled it on the same host, sometimes there are some old obsolet reginfos in windows leftover, check out
SAPNOTE 572836
but i think you just need a maxdb confirm password
br
robert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
furthermore superdba and control are also affected from the mentioned password restrictions in maxdb.
swpm should ask you at first for superdba and control password. does this work on your side? after that the swpm asks you for schema user password. at this point there is no user created at all. creation takes place when swpm will begin to execute the installation. at first it creates the db instance with user CONTROL after that SUPERDBA User activates it. so you should be able to login with superdba or control, even when swpm is not able to create schema user. can you login with database studio to your db instance using superdba or control?
i can not understand. swpm creates users in maxdb with the passwords, which you have given in swpm dialoge. furthermore you can do the following and create db instance on your own by hand (this are exact the steps, which swpm will trigger in installation)
create new DB instance:
-----------------------------
dbmcli db_create <SID> control,******
connect to new instance:
------------------------------
dbmcli -u control,******-d <SID>
set parameter:
------------------
param_startsession
param_init
param_put SESSION_TIMEOUT 0
param_put _UNICODE YES
param_put _SERVERDB_FOR_SAP YES
param_put MAXDATAVOLUMES 64
param_put MAXUSERTASKS 150
param_checkall
param_commitsession
1211150
720896
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0001 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 LOG L:\sapdb\<SID>\saplog\DISKL0001 F 1048576 // 8GB a 8kb Blöcke
activate
-----------
db_admin
db_activate SUPERDBA,*******
load_systab
further data files if needed
-----------------------------------------------------------------------------------------------------
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0002 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0003 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0004 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0005 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0006 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0007 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0008 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0009 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0010 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 DATA F:\sapdb\<SID>\sapdata\DISKD0011 F 2883584 // 25GB a 8kb Blöcke
param_addvolume 1 LOG L:\sapdb\<SID>\saplog\DISKL0002 F 2197152 // 8GB a 8kb Blöcke
param_addvolume 1 LOG M:\sapdb\<SID>\saplog\LOG_M_002 F 2197152 // 8GB a 8kb Blöcke
dbmcli -d <SID> -u control,control db_addvolume DATA F:\sapdb\<SID>\sapdata\DISKD0002 F 2883584
dbmcli -d <SID> -u control,control db_addvolume DATA F:\sapdb\<SID>\sapdata\DISKD0003 F 2883584
dbmcli -d <SID> -u control,xxxxxx db_addvolume LOG L:\sapdb\<SID>\saplog\ DISKL0001 F2228224
User | Count |
---|---|
63 | |
10 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.