on 12-29-2010 3:24 AM
Dear All..
Please Help, I installed BPC with multi server, server A for BPC Application and server B for Database. And i installed server C with database BPC. I want switch database to server C. I switch the database to server C in Server Manager --> Options --> Server Options for field SQL Server name, OLAP Server name and Insight OLAP Server name. But this not work, the application still use database in server B. Please help for this problem.....
Best Regards,
Setiadi
SAP BPC doesn't install any component into database. It is just create and configure tables and databaseintoSQL server.
So for sure you don't have to install anything into database. Everything is done when you are doing the installation of application server.
Regards
Sorin Radulescu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear All
I try change the database, its can move. But some error when open BPC Administration, the error message :
A dimension information file be created. There may be a network or security issue.
Error Message: There is no member cache file on the System. You have to run member processing first.
Please help for this error...
Hi Dharma
Not sure why you are getting this error, but have you tried to do the following in order to resolve your error:
In the Admin Console -> Refresh Client-Side dimension files
Then Export Dimension - once that has completed
Process the dimensions using the "Process members from member sheet"
Hope this Helps
Kind Regards
Daniel
This may occur when the field "Value", which is located in the row "FileServer (DataPath)" of the tblServerInfo table, does not have the correct information defined.
To fix this issue:
Open the SQL Server Management Studio
Connect to BPC Database Server
Expand Databases
Expand AppServer Database
Open tblServerInfo
Add the correct path of BPC Data Folder
This is an example of the row in question that needs to be modified:
ServerType ServerName Field Value
FileServer FileServer1 DataPath Here is the place that needs to modified
I suggest the reinstall of SAP BPCapplication server with new configuration. It is safe, faster and you are sure that everything is fine.
Performing changes into different files and tables it will be more complicate and you will never be sure that everything is fine.
When we are speaking about change of database server the it is even more complicate,
Appserver database it is the one where BPC is keeping the information where are the BPC servers.
So changing the databse server can cause a lot of troubles because into new server this database is not created or doen't have the right fields. Because of that many other issue will appear.
So my suggestion is to do reinstall because it is easy and faster way to solve yourproblem.
Regards
Sorin Radulescu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you change the database server name in Server Manager, some inportant files and registry entries get chagned, however Server Manager only partially completes the job in Appserver.
You will see a new alias created in tblServerInfo which is named "SQLSERVER2", "OLAPServer2", etc,which refers to the new server.
But, if you look at tblAppSetInfo, you will see that the aliases pointed to for all your application sets are all the "1" version. So you can do one of the following:
Update all entries in tblAppSetInfo to refer to the correct aliases (not recommeneded, in my opinion)
Update tblServerInfo so that the new, correct information is in the "1" aliases so that all your appsets automatically point to the "new" sql server, then remove the "2" entries. This is the preferred method, especially if you are not going to use the previous server anymore.
Hi Setiadi,
The prefered method here would be to backup your appset, uninstall, and reinstall BPC. Point to the new database server during the installation.
If you choose not to reinstall, here are a few things you should look at:
1. Update the \BPC\Websrvr\bin\outlooksoft.config file to point to the correct server (not sure about this step).
2. Ensure that the tblServerInfo, tblAppSetInfo and tblAppSetAccess tables in the AppServer database have the correct settings.
3. Connect to the SSAS instance through SQL Server Management Studio. Expand 'Database\Your_AppSet\Data Sources\AppDef' and display the properties. In the Connection String line select the button with 3 periods, confirm the Server Name and click the 'Refresh' button, then click 'Test Connection' to verify the connection.
Thanks,
Scott
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.