Shrink SBO COMMON Database

I found that the log file of my customer's SBO COMMON Database is too large.
Is it important? Can I just shrink it without disturbing my customer's process?
Will the SAP performance be better after I shrink the log file of SBO COMMON?
Edited by: jupitercd on Sep 14, 2011 2:18 PM

Hi,
How many companies do you maintain in a single application server? instead of shrinking the Sbo-common,why dont you restore it to its original size? As far as i know, Common will just gather info of all DB's installed in the app server and it will keep it(add-on info, patch level and etc.) on my own opinion,its better to restore than to shrink.(how to restore?get a new common from a newly installed system with same patch level and restore it into your live DB. )
Regards,
Darius Gragasin

Similar Messages

Truncate or Shrink the SBO-COMMON Database in B1.

Hello everybody!!
I need to know if it's safe to either truncate or shrink the SBO-COMMON database. I kow all recovery trail will be lost, but that doesn't matter much, since I'm planning to switch from "full recovery" to "simple" recovery model. The database is backed up on a daily basis, so only the last back up of the databse is relevant.
In notes 625546, 783183 and 548772 SAP clearly states that truncating or shrinking a production database is a safe procedure, but what about the SBO-COMMON? I guess one can follow the same rationale as in the production databases, but I'm not sure.
Thanks for any valuable help.
Emilio Méndez.

Ross:
Thanks a lot for the advice. I'm still triyng to get official word from SAP through a message in the Market Place. Anyhow, I'm going to take your adivce as a "best practice" for a reasonable maintenace plan to the databases used by B1.
I'm only waiting for some other comments before I mark the thread as "answered".
Thanks a lot for the help,
Emilio Mendez.

License allocation table in SBO-COMMON database

Hi all,
Does anyone know which table in SBO-COMMON database stores the information regarding the license allocation?
This would help me a lot 'cause I need to update that table in order to rescue a license that was blocked when I deleted a company database.
Please advise.
Victor

Hi Victor.
This info is not saved in any tables. They are in B1upf.xml which under licensing server. You can backup and recreate the file by reassign all licenses.
Thanks,
Gordon

-111: Unable to access SBO-Common database

Dear all,
I am getting following error in addon.
Error Code:-111
Error Message: Unable to access SBO-Common database
My SAP version is : SAP 9.0 PL 11
Please give me some solution

Hi Pravin,
mostl likely your sa password is wrong.
On what line do you get this error?
Regards
Ad

DTW error in SAP hana "Unable to access SBO-Common database"

Hi.. Experts
I am working on SAP Hana Pl 04 64 bit, On which I got the error "Unable to access SBO-Common database " While using DTW.
also company databases are also not presents,For more details for more details find out attachment.
I have also check out all services & Restart them.
Please give me proper solution.

Discussion moved from SAP Business One (中文) to SAP Business One Application
Find Topic Spaces on SCN (Forums)

DTW error "Unable to access SBO-Common database " for sap hana

Hi.. Experts
I am working on SAP Hana Pl 04 64 bit, On which I got the error "Unable to access SBO-Common database " While using DTW.
also company databases are also not presents,For more details for more details find out attachment.
I have also check out all services & Restart them.
Please give me proper solution.

Hi,
Please check:
1.Ensure you have the correct DB Type selected under the Login options.
2.Verify that all connection information is correct (for example, the correct user name and password or the user has enough right to connect to the database server in case Windows Authentication is used).
3. Check whether the database is running properly, make sure that the COMMON and company databases are not suspended or stopped.
4. Ensure there is no DI API version mismatch.
Thanks & Regards,
Nagarajan

Can SBO-COMMON database be re-attached after Reinstalling MSSQL 2005

Hi All,
I encountered collation issue. The MSSQL Server Collation is incorrectly indicated when upgrade from 2005B to 8.8 was performed. (the correct one should be SQL_Latin1_General_CP1_CI_AS instead of Latin1_General_CI_AS. But my various company databases are correctly stated as SQL_Latin1_General_CP850_CI_AS (as required by SAP B1).
Now, I am considering creating a new SQL Instance with the correct collation, then use the SBO Upgrade Server to create the SBO-COMMON and re-direct the License Server to the new instance. But all my AddOns requires for re-installation.
My next alternative is to uninstall MSSQL 2005 and re-install with the correct collation. But I am wondering if the backup SBO-COMMON can be used. Also, will the installed AddOns prompts for re-installation?
I have checked against SAP Note 987436. is this the only lifeline?
These solutions will required certain amount of downtime from the customer. Is there a cleaner way out of this?
Please help.
Regards
Jessie Ng

Hi,
Some of our B1 customers have encountered the wrong collation settings. Here are the problems they've got :
1. When trying to use any functionality of Drag & Relate, the following error message will be displayed: 'No matching record found'.
2. When runing "Sales\Purchase analysis report" for Business Partner, the report might not retrieve any results eventhough it should.
Here is the solution from SAP note:
Collation Settings of MSSQL Server 2005 or 2008
Symptom
When defining the wrong collation during manual installation of MSSQL Server 2005 or MSSQL 2008, in certain situations it might cause functional problems. Examples:
1. When trying to use any functionality of Drag & Relate, the following error message will be displayed: 'No matching record found'.
2. When runing "Sales\Purchase analysis report" for Business Partner, the report might not retrieve any results eventhough it should.
Other terms
MSSQL 2005, MSSQL 2008, SQL server, documentation, collation, Drag & relate, drag and relate, collation settings, collation setting, SQL 2005, SQL 2008
Reason and Prerequisites
Consulting Note
Solution
The latest version of any documentation can be found at http://service.sap.com/smb/sbo/documentation.
Please make sure to choose collation setting of: SQL_Latin1_General_CP1_CI_AS
when installing MSSQL 2005 / 2008 Server.
In order to check what the collation is set to in your server, please run the following query:
Collation of your Server:
select SERVERPROPERTY ('collation')
(This query gets the collation settings of MSSQL Server's System Database "Master")
Expected answer : SQL_Latin1_General_CP1_CI_AS
In case you have already installed the MSSQL 2005 or 2008 Server with any collation other than SQL_Latin1_General_CP1_CI_AS, please follow the steps below:
Change your server collation to SQL_Latin1_General_CP1_CI_AS.
You can find Microsoft's instructions for changing an SQL server collation here:
http://msdn2.microsoft.com/en-us/library/ms179254.aspx
Please note that collation settings of Database "Master" needs to be changed only. All SAP Business One Databases must not be changed! These must remain on SQL_Latin1_General_CP850_CI_AS.
If you need any clarifications with this process please refer to an Expert Empowerment Session "SQL 2005 Server Collation settings" at https://websmp203.sap-ag.de/~sapidb/011000358700000050892007E/ or http://service.sap.com/smb/sbo/support -> Archive: Empowerment Sessions.
If you have any Servicepack for MSSQL Server installed, but the Servicepack is not included into your DVD MSSQL Server, do as follows:
1. Deinstall Servcicepack
2. Change Collation Settings as per Expert Empowerment Session
3. Install Servicepack again
JimM

How reduce Sbo-common log is over 40GB??

Hi all
I have a big problem that what I think my SBO-COMMON_log.LDF is very big and the server tell me everyday that I don't have enough free space on HD.
I'd tried to clean and shrink the SBO-COMMON_log.LDF but I can't.
Please HELP!!!
Thanks all.
Paco
Hola a todos
Tengo un grave problema o eso creo, porque el SBO-COMMON_log.LDF es enorme pasa los 40GB, y continuamente esto recibiendo mensajes del servidor avisandome que no queda espacio libre en el disco.
He intentado limpiar y reducir el archivo pero no hay manera.
Por favor AYUDADME.
Gracias
Paco

Hi Paco,
It's not really worth keeping a log file for the SBO-COMMON database as the data movement is so small. Therefore I normally set the recovery level of this database to simple. This will then set the log file to a few kilobytes and the log file will not grow. If you'd rather keep the recovery model at full then I recommend you truncate the log file and then set up transaction log backups for the database so the log file doesn't keep growing.
When you say that you've tried to shrink the log file, what procedure have you tried? In some cases I've found that the shrink database options in SQL don't work but setting the recovery model to simple and running the DBCC shrinkfile command in Query Analyzer with shrink the file to virtually nothing. For more details see here:
http://support.microsoft.com/kb/907511
Of course, before you start playing around with your database, make sure you have a good backup
Hope this helps,
Owen

Importance of Common Database in SAP B1

hi guys,
Up to this point, its not very clear to me if it is necessary to back the Common Database of SAP business one.
As per documentation, it states that Common database includes tables for basic initialization of any new company database (for example, built-in reports and system queries). This means that every new database created, this is the time when Common Database is update or something?
My main concern here is, is it necessary for me to back/restore both the common and reg company database? I need to know this as early as possible because I am not backing up this common database .
Thanks,
Beth

hello Lili,
The common database stores required tables that used when run company databases. it is System Databases. In addition to the SAP Business One company database with the application data, you should backup the database SBO-Common once after installation, and after each upgrade.
when creating new company database, there maybe updating process of common database beside upgradingPL.
Based on securityguide file, it states:
Creating the SBO_SP_Role in Each New Database
This role enables execution permissions only to SAP Business One stored procedures in the specific database.
The following procedure should be carried out on the SBO-COMMON database and the company database.
1. On the Microsoft SQL Server Management Studio navigation pane, choose Databases → SBO-COMMON (or company database) → Security → Roles → Database Roles.
Right Click and choose New Database Role Database Role New window appears.
2. Enter SBO_SP_Role in the Name field and choose OK.
The list of Roles appears in the right pane.
3. Double-click the new role and choose from the left pane Securables.
4. From the right pane, press the Add button. The Add Objects window appears.
5. On the Add Objects window choose All Objects of the Types and press OK. The Select Objects Types window appears. Choose Stored Procedures. Press OK to confirm and close the window.
6. For SAP Business One stored procedures, select the EXEC option in the bottom pane.
Stored procedures might change in future releases of SAP Business One, therefore, this role should be updated accordingly. Instructions to change the role due to changed stored procedures will be included in the documentation of future versions.
See Appendix A Stored Procedures in SBO-Common and Appendix B - Stored Procedures for Regular Company
Rgds,

Client has deleted SBO-COMMON by mistake

My client has deleted the SBO-COMMON database while deleting other databases, assuming that it is like a DEMO database....
Please guide me the solution for this.SAP B1 is not functioning.Do i need to re-install SAP B1 Server.

You will have to re-install SAP Business One server. If you sill have the demo databases (SBO UK etc) you can un-check the option to install the demo database.
Also, I would recommend that you suggest to detach the database within MS SQL first, wait for a period of time for the end user to really confirm that the database is a demo / un-used database and then only remove the mdf and log file.
Alternatively, get them to check with you / a B1 partner before doing any work in the MS SQL relating to SAP B1.

SBO-Common

Hi, I had to re-install MS SQL 2005 and SAPB1 2005 A and server tools from the beginning. I have now just attached my company database and at first glance it seems to work ok. I am wondering, do I need to restore the old SBO-Common database, overwriting the new one created in the re-install? Is that important/necessary? Thanks, Tom

Hi Tom..........
If you re installed SAP and newly generated SBO Common tehn you no need to replace old SBO common.
But if you have been working with any of the addons then i guess you shoud replace it with Old SBO Common DB else you have to configure your addon in newly generated SBO Common DB.........
Regards,
Rahul

SBO-Common with the DI server

Do I need to have the DI server installed on the same machine as the SBO-Common database in order for the DI server to work? Or can I use a DI server on a remote environment? Thanks in advance

I installed the DI server on the same machine which is a staging machine. Now I have two environments dev and staging with the SBO-Common database installed and two identical SAP databases. My code can connect to one but not the other. I get a "General Error" error message. Have you ever seen this? Thanks

SBO COmmon Upgrad Error

hello all,
im doing an upgrade from SBO 2007a SP01 PL09 to SBO2007a SP01 PL12, but when i upgrade the sbo common database it gives me this error. [see Image|http://s264.photobucket.com/albums/ii184/abing430/SAP/?action=view&current=CommonError.jpg]. base on this error i have found this sap note 1379089, but when i get to the service manager - Event Sender my computer hangs up...
please help..
best regards,
Fidel

Hello Fidel,
Have you checked the forum?
You may start from the follows:
Unable to install 8.8 client
Upgradation Failed - SAP b1 8.8 PL 12
Thanks,
Gordon

SBO-Common saved on another disk

Can I save SBO-Common on another Disk, like data file on D: and log file on E: or this is system DB that should be saved on default SQL path
Thanks,
Olga

Hi,
It is better if you change only the company database to another drive and leave the SBO-Common database as it is.
Refer this note:[641647|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=641647] on Change Hard drive for SQL Server and SBO
To know more about SBO-COMMON databse,refer this thread
Re: Purpose of SBO-COMMON
Also refer note:[594954|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=594954] might be helpful !

2007 B Upgrade - Cannot connect to SBO-COMMON db

Hi,
Trying to upgrade SBO 2005B PL43 to SBO 2007B PL07.
The SBO -Common database exist
The SQL Express <TCP and Pipes> enable
In the SBO Common Upgrade, when I enter the correct server name, user, password and press OK, i get the follow error:
"The Connection to the specified server has failed"
"Check your password and the that server exist on the network"
Any idea?
Tanks

Hi Marcio
In 2007 you must specify the server type as SQL or SQL_2005 (Type 1 or Type 4). There are also limitations in 2007 with respect to SQL Express. The best is to check the supported databases on the portal or check with your local SAP office.
Kind regards
Peter Juby

Shrink SBO COMMON Database

Similar Messages

Maybe you are looking for