Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to handle refresh of CMS database 1

Status
Not open for further replies.

Rivdog

MIS
Sep 24, 2004
13
US
Hi,

I'm the admin for a new test BOE XI rel 2 server. The server is used for both testing and development. (We run on MS Server 2003 with the CMS using a RDMS (and Auditing is also on, with its own schema)). My question is how to handle when the database is refreshed. The DBA will refresh the test database every so often. Will there be a problem between the CMS and the Input File Repository server? (I don't care about the Output File Repository server.)

I understand that when the database is refreshed, that the objects (reports, etc) will be as of the date of the database refresh. The developers can republish their reports and update their groups. However, the reports (Crystal Reports) are in the IFR server. How tight is the relationship between the CMS and the IFR server? There could be a conflict. Will it mess up the serveer? Should I use a BIAR of the test server (created just before the refresh) and reimport all objects after the refresh?

Thanks, mrivney
 
I wouldn't "refresh" the CMS database if at all possible - it just doesn't make sense and can really screw things up.

Where are they refreshing it from? The problem is that the database is just a set of links to the actual files. So, if you're refreshing the database from another environment, the links to the files in the file stores will be bad. You'll also probably have problems with the CMS pointing to the wrong "cluster name", which can cause some major problems (I know that one from experience!! :-()

We have this issue in our production staging environment because after every software release the files for databases from Production are copied to prod staging (it's Oracle, the dba's do this, I'm not sure of all the details...) Prior to doing this, our dba's now save a copy of all of the data in the prod staging cms database out. After the copy, they truncate all of the tables and import the saved data back in.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top