Hello BV,
You have the option to create the SAP message & get the SAP support.
"instead of renaming SAPLIP to SAPLIQ, can I configure LCA, LDA and LEA connections to use SAPLIP for "standard livecache user instead" ?? That's what my colleagues are saying they have done in the past. Does that sound a possible workaround ?"
-> Yes, you can use the same liveCache user on the production & a copy SCM system.
Just to be sure that the LCA/LDA/LEA connections on a copy system changed to a copy liveCache server/liveCache name. Saved. Application server restarted & liveCache restarted in LC10, check lcinit.log.
Then run solution from note 1015489 (connection problems after system copy).
And skip the rename of liveCache user in the liveCache copy after the restore of the production backups.
And you still have to run further post SCM copy steps.
"If I rename SAPLIP to SAPLIQ, wouldn't I loose the data in livecache ?"
-> May be, if you run already APO applications as SAPLIQ user.
Has to be checked if you have any data ownered by SAPLIQ user before to drop it.
"can anyone share their experience on this please ? what do you do after QA refresh from production of SCM/livecache ? Do you rename the SAP<sourcesid> user to SAP<targetsid> user at database level in Livecache or Do you configure LCA, LEA and LDA connections to use the SAP<sourceid> user ?"
-> Both options are used by customers.
Regards, Natalia Khlopina