BusinessObject DEV CMS DB deleted .How to refresh it from PROD env.

[frndz4rahul]

Hi Team, 

We are using BO 4.2 SP3, Our DEV CMS DB (Oracle) has been deleted accidently and we can not recover this. 

Could you please help me to rebuild our DEV CMS and Audit DB from PROD env.

How we will manage on Cluster things. After Refresh from PROD, I am getting below error :

Unable to log on : Could not connect to Server <>. Please check that the server name is correct and running.

thanks

Rahul

[frndz4rahul]

Can anyone help here ?

[Joe_Peters]

If your CMS database is gone and you have no backup, then you cannot recover.  Your cluster settings and audit data are simply gone.

I would suggest the following:

1. Take a full backup of your server and FRS, just in case you do happen to find a backup of the CMS somewhere and that enables you to recover.
2. Start over from scratch.  Delete the FRS directories.  In CCM, delete the existing SIA, then add a new one.  Create a new CMS database.
3. At this point, you'll have a functional, but empty, BO environment.
4. Import content from production -- users, groups, universes, reports, etc., but only what you want to keep in dev.

Now you should have a functional dev environment. Obviously you will have lost any work that was done in dev after the CMS was deleted.

You might be tempted to do an "expand" installation, or take a copy of the production CMS database.  That won't work.  The CMS database is tied to the production servers, and will create a mess if you try to do that.

[frndz4rahul]

Thank you so much for the reply... I have Uninstalled the previous version(4.2) and Installed fresh 4.3 SP4 300. Installation is Success and I have configured the CMS DB as well. Now I can see below services in CCM :

[frndz4rahul]

1. Apache Tomcat 2. BW publisher service 3. Workflow Assistant. What all services i have to add like SIA

[Joe_Peters]

Yes, you'll need to add a new SIA.

[frndz4rahul]

I am not able to Create SIA. I am getting below Error : 33007 CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027) 35101 The root server reported an error Initialization Failure. (Reason: CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027)CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027) CacheObjectIDs ).

[Joe_Peters]

That looks like a database error. I've seen it happen in Oracle when CMS queries were running too long, but I've never seen it during an installation. The SIA log file might have more useful info, or you might need a DBA to check the database.

[frndz4rahul]

DBA dont see any issue on DB Side. We have increase the number of connections as well. Right now we have old version of client Installed (4.2 SP3) on the machine. is that may be a problem ?

[Joe_Peters]

I don't think the version of the client would cause that problem. For a next step I'd suggest checking the trace files for the SIA and CMS.

[frndz4rahul]

My SIA Agent is working and able to connect from CMS database. Getting cluster name successfully. But i am not able to login on Manage servers, CMC console. Error message is : Account information not recognized: Could not reach CMS 'HKGS00175173:6400'. Specify the correct host and port and check for network issues, please refer to SAP Knowledge Base Article 2151044 on the SAP Support Portal. (FWM 20030). cms.exe is not found in services. Please guide

[Joe_Peters]

That means the CMS is not running. Check the Windows event log, and the CMS logs.

[frndz4rahul]

Could you guide me , how to run CMS is not running. But i see CMS.exe service as running in task manager now. Still i am getting Account information not recognized: Could not reach CMS '<HOST>:6400'. Specify the correct host and port and check for network issues, please refer to SAP Knowledge Base Article 2151044 on the SAP Support Portal. (FWM 20030)

[Joe_Peters]

cms.exe may be running but it's not functional. Check Windows event log and the CMS logs.

[frndz4rahul]

Yes I have checked the windows event logs, It showing Central Management Server stopped, and error is : The root server reported an error Initialization Failure. (Reason: CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027)CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027) CacheObjectIDs ).

[Joe_Peters]

Ok, so that's the same error you got before. It's a generic message and can have many possible causes. Check the CMS logs next. You may need to increase the logging level.