How to separate a cloned BO server

[former_member368770]

Hi,

We have a BO PRD server which has got SP2 + Patch 15 installed on it. The PRD server is not in sync with the DEV server which has got BO SP5 + Patch 7 installed on it. During testing on DEV we encountered some issues which we have raised with SAP for fixes. As a result we have decided to put the PRD server upgrade on hold until those issues are fully fixed.

Before we do a full upgrade on PRD we decided to test the upgrade on an identical environment. Since we did not have a TST environment we decided clone our PRD server and name that as TST and do all installation on this virtual machine. TST server has a different name and IP address in comparison with PRD.

To separate TST from PRD I created a new SIA node under CCM and then deleted the old one. The CMS and Audit Databases are copies of PRD, but on different server with different names.

After separation the TST server was fine with all the servers running fine in CMC. There was no impact on PRD. After that I installed SP4 (inc. FP03) on the TST server along with its patch 15.

I did a reboot after the install and checked whether I could get into CMC. Had no problems. However when I tried to logon to BI Launchpad it gave HTTP 500 error.

Apparently after that all our reports in PRD started throwing "(Error: RWI 00200) (Error: INF)" errors while opening the document. When I rolled back the changes in TST server with the snapshot of the server all the reports in PRD started working fine.

The different config files in TST still have names of the PRD server. I wonder what sort of linkage is there between TST and PRD which caused this problem. ALL the servers are on Windows 2008R2.

Does anyone have any idea on how to fix this issue? I am new to BO , hence any feedback will be appreciated. Thanks

Regards,

Lad

[Former Member · Accepted solution]

If the CMS Db (TST) was simply a copy of the PRD Db (backed up DB), it should not give any problems. The processing servers should not be linked in any manner as the cloned SIA in TST was removed and later a new SIA was created.

The error thrown in PRD seems an issue at the WIPS when reports were being viewed. Were you able to check the server status in PRD when the issue occured. It seems that the webi processing server was recycling and might have got hold at some point.

Also I suspect that there is a probability that the new system (TST) might have got clustered at some point accidentally. In such scenario the issue would occur as one Box (server entries) were on previous versions, which gave the error.

How about creating a new Db connection for CMS in TST to the backed up database. That might help the cause

This might help.

[former_member368770 · Accepted solution]

Hi Arvind,

How can I remove the second node (ABOJISTAP01) which was created in PRD by mistake prior to cloning. Although it can no longer be found in CCM it is still visible in CMC. Since our TST is an identical copy of PRD the additional node (ABOJISTAP01) is also visible there.

I could not find it in the registry on the two environments. Can anyone please assist me with this. Thanks

H

[Former Member · Accepted solution]

Please check the SAP KDB

1339944 - How to delete an unused Node that is listed in the Central Management Console

• Delete all the servers referring to ABOJISTAP01 node.

• All the services are deleted, now we need to delete the ABOJISTAP01 NODE.
• Right Click on the node and capture the CUID.

• Note down the CUID’s of ABOJISTAP01 nodes and login to the respective CMS DB.

• Execute the below SQL statement

'DELETE FROM CMS_INFOOBJECTS7 where SI_CUID = 'CUID of ABOJISTAP01' and commit the changes.

[former_member368770 · Accepted solution]

Hi JRK,

Thanks. We executed the SQL statement and it worked. The unused node is no longer visible in CMC.

I am looking forward to install SP4 on this TST server and hope there will be no connection with PRD whatsoever.

By the way do I need to execute this statement as well: Delete from CMS_INFOOBJECTS7 where ObjectID= 4  to delete cluster entries if any?

When I do run a select statement I find ObjectID = 4 in the SQL. Please advise. Thanks

Regards,

Hitesh

[Former Member · Accepted solution]

if we perform the steps in the below order then no need to perform the above query.

1) Delete Servicese mentieond

2) Delete the Node

if you wont delete the services, then you have to execute mentioned query to delete the service entries from the CMS DB.

[former_member368770 · Accepted solution]

Hi JRK,

Thanks for the reply.

The reason I asked about running this query [CMS_INFOOBJECTS7 where ObjectID= 4  to delete cluster entries if any] is because when I tried to install SP4 on the TST server the default CMS Name displayed was ABOJRSAP01 (for PRD) instead of ABOJRSAT01 (for TST), hence it seems like there is still some reference to PRD CMS i.e cluster entries.

What do you reckon I should do? If I change the CMS name from ABOJRSAP01 to ABOJRSAT01 manually the installation will go ahead, but I want to be absolutely sure that there is no cluster between the two environments.

Previously prior to deleting the node (even though the services were deleted) I went through this installation process and that's when we figured out that the changes in TST somehow had an impact on PRD. By rolling back changes on TST resolved the issue in PRD.

Looking forward to hear from you. Thanks

[Former Member · Accepted solution]

The CMS name which was displayed during the Installation will be cached from local system. it will not go to CMS DB and fetch the existing CMS Name.

I had a similar issue and Changed the CMS name and performed the instlation.

[Former Member · Accepted solution]

Dear Hitesh

Did you find a solution for this issue? We have recently cloned our production environment to create a TST environment. We are experiencing the same issues you described in here.

[former_member368770 · Accepted solution]

Hi Thembela,

I cannot confirm this just yet. I have so far installed SP4 + Patch 15 over SP2 in TST. Once I have fully installed SP5 + Patch I need to test it out. Only then I will be able to confirm this. However so far things are looking positive.

I made same changes in the registry, but very little. I am not sure what I did was correct or not, but searched for the PRD server name and replaced some of them with TST server name particularly for Original Machine Name, Group Prefix.

On the TST server go to \Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data and look for the CMS node name and open that up. There might be two of them; one for TST and one for PRD. If there any reference to your PRD CMS WebIntelligenceServicers then yes, you need to delete them. Likewise within TST if there is any reference to PRD WIS.

Similarly delete the corresponding entries in the registry as shown below. The name should correspond to the data. In my case I deteted the one boxed in red below. I did a gpupdate after that.

Hope this makes sense.

Regards,

H

[Former Member]

Seems like TST machine is still connecting to the PROD. Please remove the prod machine name in TST machine registry entries and test the issue.

Regards,

Santosh Returi

[former_member368770]

Hi Santosh,

Thanks for your reply. Could you please elaborate further on this changes to the registry entries. Do you mean I need to delete or replace the prd machine name with tst machine name? I can alot of entries with prd server name.

Is there anything I need to take into account before making changes to registry? Please advise. Thanks

Regards,

Hitesh

[former_member368770]

Hi Santosh,

I have had a look at the registry and found the prd WIPS'S(...AP01...) under the tst (...AT01...). Do i need to delete the prd ones?

Please advise. Thanks

Regards,

Hitesh

[Former Member]

Could you pleas check the below things:

• Login to any TST server

• From the CCM, stop the SIA

• go to SIA > Properties > Configuration

• Modify the Cluster Name of the restored environment to be different from the source environment

• Confirm that the cluster key is different between source and destination environments. (If it is same then change the cluster key.)

• Login in CMC TST with ADMIN ID. Go to servers and Nodes.

• Delete all the servers referring to PROD environment. (Do not delete the running Central Management server Of TST.)

• All the services are deleted, now we need to delete the PROD NODES.

• Note down the CUID’s of all the PROD nodes and login to DR CMS DB.

• Execute the below SQL statement

'DELETE FROM CMS_INFOOBJECTS6 where SI_CUID = 'CUID of the PROD NODE' and commit the changes.

• Now all the PROD nodes are deleted from TST System.

• Update the Host file of the TST servers with the Wrong IP Address of all the PROD servers to avoid the communication between PROD and TST.

• Update the Host file of the PROD servers with the Wrong IP Address of all the TST servers to avoid the communication between PROD and TST.

• Contact your network team to stop the mirroring/SNAPSHOT from PROD to TST BO servers and same for the CMS/AUDIT DB also.

[Former Member]

Issue might be possibly be due to cluster configuration setup. It might help.

[former_member182521]

Hi Hitesh,

Cloning is not the recommended way of building a new server, but it should work logically.

I suspect in your TST environment BO servers (services) are still referencing the your old PRD environment.  Have you removed the old server references in your TST environment and created a fresh SIA with associated servers in TST.

Refer the blog below for removing old server entries.

BusinessObjects Content recovery and Disaster recovery - BO XI 3.x

Regards,

Mani