cancel
Showing results for 
Search instead for 
Did you mean: 

Personas 2.0 and System Copy

former_member188433
Participant
0 Kudos

Hi Folks - We will soon do a system copy in our ERP landscape (copying production to QA).  We use a database restore method for this.

We have a couple of Personas 2.0 SP02 scenarios active in production.

I am concerned about Personas production tables overlaying the QA tables.  Has anyone done this type of system copy before with Personas?  If so can you recommend a procedure to handle this scenario?

There are currently 46 tables in the /PERSOS/ namespace - should they all be copied from QA and restored after the system copy?

Thanks - Jeff

Accepted Solutions (1)

Accepted Solutions (1)

steverumsby
Active Contributor
0 Kudos

When you do a system copy, everything in the target system is deleted and replaced with the contents of the source system. Personas is no different. After your system copy, you QA system will have all of the Personas flavours from production. Anything that was in QA only will be gone. If you have stuff in QA and not yet in production, you will have to put it back after the copy.

If the flavours were developed in DEV first, then just replay the transports that copied them to QA. If not, or if they've been changed in QA, then export them before the system copy and import them afterwards.

Steve.

former_member188433
Participant
0 Kudos

Thanks Steve.  Most of the tables in the /PERSOS/ namespace are unfamiliar to me.  Does it make sense to copy all 46 of the /PERSOS tables in QA before the system copy (to ensure we capture everything?

Regards - Jeff   

steverumsby
Active Contributor
0 Kudos

Nothing in a QA system should be unique. It should have all got there by being transported from DEV, right? The official answer to your question, therefore, is to re-transport anything from DEV after the system copy. You'll need to re-do the Personas system config, but apart from that, transports from DEV should give you back everything.

That said, if you want to be sure, I guess copying all the tables would work but to be honest I've never done it. It certainly isn't a recommended practice. I can't immediately think of anything that would go wrong, but I would be reluctant to give any guarantees.

Steve.

tamas_hoznek
Product and Topic Expert
Product and Topic Expert
0 Kudos

I wouldn't advise to do straight table copies, since I'd be worried about tables referencing GUIDs belonging to a different system and similar cases.

The best way is to do things as Steve suggested: via the transport system.

Answers (0)