cancel
Showing results for 
Search instead for 
Did you mean: 

System Copy of IDM 7.2 Copying Identity Center Database

Former Member
0 Kudos

I need to do system copy of IDM 7.2.

Source and Target Systems: SAP NW IDM 7.2 SPS08 on Sql server 2008/ Windows 2008 R2.

I have the document https://scn.sap.com/docs/DOC-40514

In that document step 3.2 says running the system copy jobs which I  think have to run on on the Source.

Do these jobs create SQL scripts which I will copy to the new Target system and run on Target. to import the data?

After reading the document it's not clear how the Target Database is populated with Source Data?

Any help is highly appreciated.

Regards,

Rao D

Accepted Solutions (0)

Answers (1)

Answers (1)

keith_zhang
Active Participant
0 Kudos

Hello Rao,

I found on page 5 of the document, it explains the different jobs functions during the copy process. The 06 and 07 job, will copy the relevant table content from source to target. These 2 jobs should be originally empty, they are created by 04 and 05 job.

When performing the system copy, all these jobs should be run in the given order, and they will complete the system copy. After that, also check the post-system copy steps to finish.

I have not tested to run a system copy, but I guess these parts from the doc should give you some hints?

BR, Keith

Former Member
0 Kudos

Hi Keith,

Appreciate your response.

My Source and Target are in two different Data Centers.

So when I run the System Copy jobs in Source System, the Target is not connected.

Like the regular system copy where you take the export dump from Source system and then copy it to Target system for import, do we have that facility here?

Can I use SQL Server Attach & Detach method to copy Identity Center Database or the regular backup & restore for SQL Server database?

Regards,

Rao D

keith_zhang
Active Participant
0 Kudos

Hi Rao,

There is also 'transport' function:

http://scn.sap.com/docs/DOC-17104

and 'configuration copy tool':

http://scn.sap.com/docs/DOC-4365

These will generate export file. But both of these are for moving configurations, instead of the data. So before the current system copy jobs are released, I know some customers may try to use some DB tool, but sorry that I have no experience with doing it in that way

BR, Keith

Former Member
0 Kudos

Just a short comment:

It is a prerequisite that both the source and the target can be accessed at the same time (be on the same network), which I guess should be clarified better in the document. There is no possibility for creating an export dump with system copy.

If both the source and the target are SQL Servers, then Attach and Detach should work ok.

former_member2987
Active Contributor
0 Kudos

Mia,

My thoughts exactly!

Former Member
0 Kudos

MIa/Matt,

Appreciate your response.

Like you have mentioned the document should say that the Source and Target should be on the same Network.

I was also thinking about Detach/Attach method is a better option, but what are the post copy steps that I need to add on the Target Server ? Are they different from the document https://scn.sap.com/docs/DOC-40514

Regards,

Rao D

Former Member
0 Kudos

Keith,

Thank you very much for your response.

The Copy and Transport documents are useful.

Regards,

Rao D

Former Member
0 Kudos

Hi Rao,

I had to double-check this one When using Detach/Attach, on the SQL Servers, there is no need to check the SQL queries (section 4.1). You would need to create the dispatcher scripts (section 4.2).

Best regards,

Mia

Former Member
0 Kudos

Hi Mia,

Appreciate your response.

The procedures are totally different I think.

The SQL Export scripts procedure is totally different from Detach/Attach or DB level Backup/Restore.

In the second procedure , the post restore steps not same as the 1st procedure.

Regards,

Rao Devaguptapu