cancel
Showing results for 
Search instead for 
Did you mean: 

max db 7.5.00.38 backup recovery not working for homogen system copy

Former Member
0 Kudos

Hello,

windows x32 2003 SE

Max DB 7.5.00.18

sap ERP 2004 SR1 ECC 5.0

Abap System

Unicode Central İnstallation local

Unicode Database İnstallation local

System Copy /MaxDb System Recovery Option

All steps done according to SAP Note Number 129352

Homogeneous system copy with MaxDB (SAP DB) till (Xserver running

DB instance Online)

Recovery with Initialization

Error message:

"-2 wrong user name password combination"

After this error message situation DB connect impossible sUPERDBA, CONTROL, DBM

Where is the problem, who can suggest overcome this error message

Thanks.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello

Oksana Alekseio,

Melanie Handreck

I solved problem so many thanks for your suggestions.

I installed the fresh new system with the same SID then restore from backup old data.

Finally it is working correctly.

.

Former Member
0 Kudos

Hello,

I just wanted to mention that we ran into this same issue

and solved it the same way you did (re-installing using the

same SID as the backup).

Has anyone been able to do this without re-installing the

system using the same SID from the backup? We have

tried this 4 or 5 times and always run into an issue

with the DBM/DBA accounts.

Thank you,

Joe Haynes

System: SAP R/3 4.70 ext 110 on MAX DB 7.5.0.29 over RH2.1

Melanie
Advisor
Advisor
0 Kudos

Hello Joe,

it is not necessary to install a database with the same name as in the backup which you use for the restore. It is possible to choose a different database name.

As you are an SAP customer, please open a customer message, when you run into this problem again. I would like to check the log files to figure out what went wrong. Or maybe you still have the log files from your last system copy - then I can analyze these.

Best regards,

Melanie Handreck

Melanie
Advisor
Advisor
0 Kudos

Hello,

did you check that the parameter _UNICODE is set to YES in the target database?

The parameter needs to be set to the same value as in the source instance. If this is not yet the case, you need to change the parameter and to perform the recovery again.

If this is not the cause of the problem, please explain in more detail where you get the error message (DBMGUI, dbmcli - at which command, SAP-System, ...).

Kind regards,

Melanie

P.S.: As you are an SAP customer, such issues should be analyzed in a customer message.

Former Member
0 Kudos

Hello Mehmet,

can you check the database state with the dbmcli? Could you log on with the user and passwords data for example?

dbmcli -d <DBSID> -u control,<passw> db_state

If this command failed because of the wrong user/password combination, please use the note 39439 for correcting the XUSER entries.

If this command succeeds but the connect to the database failed for example

dbmcli -d <DBSID> -u control,<passwd> -uSQL control,<passwd> sql_execute select * from dual

it means the password of the user control in your database is other as you think and you need to know it for correcting the XUSER entries and connecting to the database.

Regards,

Oksana Alekseious