Non-generation of some profiles during transport

[prasnad]

Hi,
We have transported a transport request containing 700+ roles from DEV to QA system. All the roles have generated profiles in DEV system. But, in QA, prifiles for some roles were not generated. What could be the reason? Is it a Basis issue? The systems are ECC6 EhP4 SP3 with DB2 9.5 FP4 on SuSe Linux 10 SP3. Thanks in advance.

[thx4allthefish]

moved from Basis.

[Harters]

I did see this once but the reason was that when the transport was created initially with the first say 50 roles, the check box "also transport the profiles" (or whatever it is called) was deselected. Then when subsequent roles were added to the transport the check box remained checked so out of say 300 roles, only 250 had profiles moved.

Another way I can think of is if the roles were created in a different systems other than dev and had therefore different profile names so this might cause issues as the role doesn't know which profile to use - new or old.

Have you checked the transport to see if the profiles are contained in the table objects (USR12 e.t.c?)

[henrik]

Are they by any chance derived roles? I've seen issues where certain derived roles would show up as not generated if not all derived roles from that master was transported.

[os]

If your SID names do not differ in the first and third characters of the names and someone was already regenerating (as others have mentioned and might be the cuplits or creating other roles in QAS which blocked the name of the profile, then this will happen.

You should check your transport log and reset the number range of the profile generation to make them unique. This is a good idea anyway.