cancel
Showing results for 
Search instead for 
Did you mean: 

User password problem in RFC after system copy

0 Kudos

HEllo,

we have a problem in ECC6.0 after system copy (refresh QUAL system by PRD data).

BEfore doing this copy, we export RFC data (SM59 tables) of our QUAL system and after the refresh we reimport these RFC in our QUAL system. We don't want RFC comming from productive system.

After this reimport, RFC configuration is ok but we have a problem with RFCuser password. In the password box we have "inconsistent"...

Have you an idea to reimport succesfully these informations ?

Thanks

lionel

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

What if you truncate all the tables what didi you export? Like using command

truncate table RFCDES;

truncate table RFCDOC;

<this way all other tables you have exported>;

and after this use r3trans -i sm59_igw.dat?

0 Kudos

Hello,

I tested it normally (without refresh) export/import of table, but did not succedd to reproduce problem of password inconsistent.

I 'm waiting a downtime to check on another system where I still have to inconsistent passwords. Let see results soon.

I will try anyway to test again on next refresh.

If you think that some tables are missing or someting else to do.. let me know..

Answers (5)

Answers (5)

0 Kudos

HEllo,

could someone help us on this topic ?

thanks

lionel

JPReyes
Active Contributor
0 Kudos

This is just a thought but have you checked that both source and target systems have the same password parameters active?... maybe the passwords setting are different making the passwords inconsistent.

Regards

Juan

0 Kudos

Hello

Password parameters are the same everywhere (source and target)

login/password_change_for_SSO

login/min_password_lng

login/min_password_letters

login/min_password_digits

login/password_max_idle_initial

login/password_max_idle_productive

login/password_expiration_time

login/password_downwards_compatibility

Any other idea?

JPReyes
Active Contributor
0 Kudos

Try the passsword in UPPERCASE

Regards

Juan

Former Member
0 Kudos

you need migration key from SAP. Request migration key and apply in SECSTORE.

0 Kudos

Hello,

This is how we import data :

$ R3trans -w import.log import_rfc.sql

With :

zeaadm 24> cat import_rfc.sql

  1. execute script with

  2. R3trans -w import_sm59.log import_rfc.sql

  3. as <sid>adm in $HOME/SM59

  4. to import RFC data

import

client=001

file='sm59_igw.dat'

Yes, client 001 is used. But anyways, there is no information regarding client (no field MANDT)

Only table SXRFC have one, but table is empty in our system.

select count(*) from sapsr3.sxrfc ;

COUNT(*)

-


0

thanks for your help

Lionel

Former Member
0 Kudos

Did you also import QAS user master? If not change the RFC user credentials as of Production system.

0 Kudos

Hello KVR,

Before refreshing system, we export users (via client copy profile SAP_USERS)

So user credential should be the same.

Former Member
0 Kudos

Hi Hewlett Packard,

I was making sure if he had imported the QAS user master after refresh as its not a mandatory step in everyone's refresh.

Regards

KVR

0 Kudos

Hello,

We performed another refresh yesterday. But unfortunatly it was not working. Password are still inconsistent.

This are exactly way we perform it:

Before restoring DB :

  • export table via R3trans for tables:

RFCDES, RFCDOC, RFCATTRIB, RFCCHECK, RFCDESSECU, RFCSYSACL, RFCTRUST, RFCCMC, RFCGO, SXRFC, IBSSI_RFCDEST, PARAMVALUE, RSECACTB where ident LIKE '___/RFC%'

  • export users via scc8

  • Restore DB, truncate upper rfc tables, import rfc Tables

  • Check SM59 => inconsistent

  • Migrate Secstore => still inconsistent

  • Import Users via transport generated by scc8

  • run scc7 as post actions

  • Tuncatate/re-import rfc tables

  • Check SM59 => inconsistent

  • Migrate Secstore => still inconsistent

What else could be done ?

We have a lot of RFC. so re-enter all password is really a hudge task ..

Thanks a lot for help

Former Member
0 Kudos

Hi,

I used to export and import some four to five RFC tables in 4.7 EE. not sure in newer versions.

Regards

KVR

0 Kudos

Hi,

t hanks for your quick answer but we have already try this.

Please find more information about our actual process:

This are tables extracted and way we extract them :

  1. execute script with

  2. R3trans -w export_sm59.log export_rfc.sql

  3. as <sid>adm in /home/<SID>adm/SM59

  4. this creates a file sm59_<SID>.dat for import of RFC data and a

  5. logfile export_sm59.log

export

client=001

file='sm59_igw.dat'

select * from RFCDES

select * from RFCDOC

select * from RFCATTRIB

select * from RFCCHECK

select * from RFCDESSECU

select * from RFCSYSACL

select * from RFCTRUST

select * from RFCCMC

select * from RFCGO

select * from SXRFC

select * from IBSSI_RFCDEST

select * from PARAMVALUE

select * from TXCOM

select * from RSECACTB where ident LIKE '___/RFC%'

Former Member
0 Kudos

If there is everything ok in client 001 (do you really use this client), I see nothing weird in your command.

What command are you using to import definitions? Do you create controlfile (like rfcimport.ini), where is lines

IMPORT

client = <your client>

file = '<path>/sm59_<SID>.dat'

and finally import it using r3trans -w logfile.txt rfcimport.ini

It have worked for me...

Former Member
0 Kudos

Export the contents of tables rfcattrib, rfcdes and rfcdoc before copy and export them back to system after copy.