DB2 schema user after Production DB copy

[Former Member]

I have often faced issues with the DB2 schema user after a PROD copy to the QA system using the redirected restore approach . many times the R3trans -D will not working and cause headache for Basis Administrators.

This did not happen in earlier versions as the sap schema owner was by default : SAPR3 ( same in QA and PROD )

Assuming that my PROD system is PRD , the schema owner for the objects in production will be SAPPRD.

And assuming my Quality system is QAT , the schema owner for the objects in quality will be SAPQAT.

The issues happen after a standard redirect restore because the schema owner of the objects change to SAPPRD  in the QA system post refresh .

1.  As DB2 uses authorization from the OS level users , hence the user SAPPRD will need to be created in the QA Host .

2.  Using the password for the SAPPRD user recently created , you should be able to connect to QAT DB2 system.

db2 connect to QAT user SAPPRD using <Passwd>

3. Once this done , we can go ahead with the next step . It involves creation of the password entry for the user recently created in the Database. Before this - as per the standard refresh procedure , we need to give DBADM authorization to QATADM user on the database .

As QATADM user , perform these steps :

dscdb6up -create sapprd <Passwd>

db2 connect to QAT  user sapprd using <Passwd>

dscdb6up sapprd  <Passwd>

Please see the below screenshot for the actual output and execution of this critical step . 

Comments and suggestions are most welcome !

Thanks

Rishi