Password problem with user DDIC

[Former Member]

Hi again,

I'm still trying to install Solution Manager 3.2.

The installation procedure said it's higly recommended to change the passwords for user DDIC and user SAP*.

For me, it's absolut normal to choose a password not only containing alphatical chars, but also special chars.

So the password of user DDIC starts with an exclamation point (!).

Now the installation procedure stops at the SAP IGS > RFC Connection.

Entering the password for user DDIC doesn't take any effect. The screen does not change and the log says:

WARNING[E] 2006-04-13 16:41:44 [iaxxrfcimp.cpp:450]

CAbRfcImpl::openRfcConn

Unable to open RFC connection.

I opened my saplogon and created a new connection entry for my sap solution manager server.

I get the standard login screen for sap and tried to login with user DDIC.

If I enter password containing only normal chars, I get the expected error message: wrong username or password.

But if I enter the correct password with the '!' as the first letter, the error message says, I must make an entry in every required field.

I entertain suspicion, that using special chars, especially the exclamation point, is not allowed.

How can I change the password without interrupting the installation process?

I only have three buttons: OK (which isn't working at that moment), Cancel and Logoff.

I don't know what happens, if I click on Cancel or on Logoff.

Maybe I can finish the installation and setup the RFC connection later?

Or the system accepts my inputs and goes on.

Any idea?

[Former Member · Accepted solution]

If the user is locked you will need to update UFLAG field in table USR02.

Example:

Update USR02 ser UFLAG=0 where BNAME='DDIC' and MANDT=000

Hope this helps!

Best Regards,

Federico G. Babelis

NetWeaver Certified Consultant

GAZUM Technologies S.A.

Consulting Services and Software Solutions

http://www.gazum.com

...download FREE Marketplace Manager at: http://www.gazum.com/products

[RiccardoEscher]

Hello Knud,

funny, I nearly forgot it's existance, but a '!' at the first position in a dynpro field is the so called "Rücknahmebengel" from old R/2 days.. (no, don't ask me for an english translation).

If I remember well, you could reset the content of the dynpro field to it's default with the '!' at the first position, for example if some dnypro check forbiddes a value and you don't want to cancel the transaction. You can test it with a date selection field of some report: insert some wrong value like 'ddddddd', you will get an error message blocking all the transaction; now change the first 'd' with '!' and press enter...

It seems that '!' is not a good choice for the first character of any dynpro field.

Bye

[Former Member]

The question is where can you trace who unlock it and ran the command at database level.

Any specific file that I should be looking at ? Any place I can find the command history ?

[Former Member]

Forgot to add,

once you have reset the user name sap, you can then logon to client 000, using user=sap and password=pass.

further you can reset the password for ddic and sap*.

Hope this helps.

cheers,

chetan

[RiccardoEscher]

Hello Chetan Hinduja,

one can also delete the record for sap* in usr02, in this case sap* will have it's default and built in password 'PASS' (same situation as when you log into a newly created client).

The sid is not always part of the name of the database schema, for example if you plan system copies by copying the database files you will never use the sid for the schema name.

Bye

[Former Member]

Hi Riccardo,

You are right, i know many customers who keep common database schema example SAPR3, so that is it simplifies the system copy procedure.

Cheers,

Cheran

[Former Member]

Hi,

the table is no longer sapr3.usr02.

With WAS, you need to postfix your system sid to sap, so the table would be sap<SID>.usr02.

if SID = SOL

unlocking user ddic:

sqlplus "/as sysdba"

sql> update sapsol.usr02 set uflag=0 where bname='ddic' and mandt=000;

sql> commit;

resetting password for sap*

sqlplus "/as sysdba"

sql> update sapsol.usr02 set bname='SAP1' where bname='SAP' and MANDT=000;

sql> commit;

Cheers,

Chetan

[Former Member]

The problem gets more difficult...

During my tries, the DDIC user is now locked and I don't know how to unlock him without logging into the system.

I could use sqlplus to connnect to oracle

like:

<b>sqlplus /nolog

connect sys as sysdba</b>

But I don't know which db or table I should update.

I googled and found the table sapr3.usr02 but it seems this table does not exist?