SBO-COMMON demasiado grande

Buenas tardes, Recien he llegado a realizar la actualizacion de SAP 2007A a 8.8 y me encuentro con un SBO COMMON de 533 MB con un archivo log de 70 GB! , he realizado los procedimientos de reduccion de SQL2008 pero simplemente el corre la solicitud dice ok y todo queda igual.. Agradezco quien me informe de algun procedimiento adicional a realizar, Gracias

Tengo entendido que sap recomienda ese modo de recuperacion en SIMPLE
No olvides calificar el aporte si te fue de ayuda
Saludos!

Similar Messages

Creating user defined table in SBO-COMMON

Hello experts,
I'd like to create a user defined table in SBO-COMMON. I'll tell you why:
I have successfully created a SAP B1 addon which adds freight costs to an order if the total amount is under a certain threshold. We have 2 administrations running, a live one and a test administration. We have put the connectionstring to determine the expense code of the freight costs in the exe.config-file of the addon.
We want to be able to point the addon from one administration to the other by modifying only one value, a centralized value, independent of SAP administration. The most proper way to do that in my opinion is to put it in SBO-COMMON and the only logical way to do that is a user defined table in SBO-COMMON.
Is there such a way?
My alternative is to abuse another database on the server and just add the info there, but I'd prefer to store it in SBO-COMMON.
Thanks for your time!
Vincent

UDT cannot be created in sbo-common. You may create new db and work with table in this db (but it will be not UDT, but standard sql table), or create new company db only for this purposes and create UDT there.

Add-On connection for Journal Entry - Failed to Connect to SBO Common

We have a customer (SAPBO 2005A SP01 PL29) with some specific requirements that required an add-on running in the background to monitor the addition of Goods Receipt PO's to the system. When the GRPO is successfully added, the Add-On will (behind the scenes) create an appropriate Journal Entry through the SAP DI. One of the issues that we encountered during the development of this functionality was that when it was tested by users, they weren't authorized to access the Financials module or the Journal Entry screen. What we ended up doing was creating a secondary connection (vCompany) in the DL pulling the information from the encrypted user information from SAP the Add-On used to connect, but utilizing a management level user ID and password. Once that connection has been made, the Journal Entry is added through the DI and that secondary connection is disconnected.
The problem that we're encountering is this. When the users are logged into SAP Client with an regular user, and the GRPO adds, the secondary connection fails and returns a message of "Failed to Connect to SBO-Common". However, if the user is logged into SAP as an adminitrative level user and the GRPO is added, the secondary connection is successful and the Journal Entry is created. The secondary connection is strictly used for the JE. Here's the code (VS.Net 2005) for the secondary connection:
vCompany = New SAPbobsCOM.Company
vCompany.UseTrusted = True
vCompany.language = SAPbobsCOM.BoSuppLangs.ln_English
vCompany.CompanyDB = oCompany.CompanyDB
vCompany.UserName = "XXXXX"
vCompany.Password = "YYYYY"
vCompany.Server = oCompany.Server
vCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
lRetConnect = vCompany.Connect()
Where "XXXXX" would be the appropriate management level SAP User Name and "YYYYY" would be that users password.
Has anyone else had this kind of issue where you needed a secondary connection with management level access behind the scenes to accomplish something in SAP and had problems getting it to connect? Any thoughts or ideas would be greatly appreciated.

Hi Dennis,
what you can try is to make a untrusted connection
oCompany.UseTrusted = False
and set the DBUser and Pwd
oCompany.DbUserName = "sa"
oCompany.DbPassword = "insertpwd"
lg David

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

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

How to Change sbo-common ldf & mdf path

Dear experts,
Our C drive space is very low, that why I want to change my sbo-common .ldf and .mdf data path( Its hold 15gb).
I had changed other .ldf and .mdf path using restore process. But when I change the sbo-common path then error is occurred (database are use).
I run the SP_WHO and find out the spid and kill the IDs but one or two id was create again that's why
I not change the path.
Please give me the solution.
Tanks ,
Arabinda Pal

Hi,
Close SAP on server and client machines.
follow below steps:
Always take a full backup before a detach.
Detach the database, delete/rename the log file, attach the database - this will create a minimum size log file.
Note that the log file must be deleted/renamed otherwise it will be re-used even though it is not mentioned in the attach.
Enterprise manager
Right click on the database, All tasks, Detach database, OK.
Delete/rename the disk log file.
Right click on databases, All tasks, Attach database, Select the .mdf file, OK, Yes (to the create new log message).
t-sql
sp_detach_db [dbname]
Delete/rename the disk log file.
sp_attach_single_file_db [dbname], [filename]
where [filename] is the name of the physical data file (.mdf).
Thanks,
Neetu

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

Changing location DB SBO-Common

Hi all,
Detailed problem description:
I am using SQL Server 2005.
To free space on the C drive we want to move mdf (data) and ldf (log) files for example 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data'
to the D-drive, 'D:\Data'.
I know SBO-Common is necessairy for SBO, the others not sure.
How can I move those files, without creating any problems?
Thanks, Chief

Hi Chief
Accutally I think it's a SQL Server job and you do not even need to change anything
in SBO.Just relocate the DB to the new location by following the below MS kb,
then click the refresh botton the choose company windows at SBO.That should work.
http://support.microsoft.com/kb/224071
Regards,
Syn Qin
SAP Business One Forums Team

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 error when Using oRecordSet = oCompany.GetCompanyList

Good Day
Experts:
I am having a bit of trouble running the code in the COM DI\05.OrderAndInvoice sample.
On the line --> oRecordSet = oCompany.GetCompanyList
An error appears "Connection to SBO-Common has failed".
I would like to do the same thing in one of my screens but I cannot even get the sample to work. I am not sure
what connecting to SBO-Common does but appearently I need that since the sample or my application does not work.
Can anyone help?
Thanks,
EJD

oCompany = New SAPbobsCOM.Company
' Init Connection Properties
oCompany.Server = "servername" ' change to your company server
oCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
oCompany.DbUserName = ""
oCompany.DbPassword = ""
oCompany.UseTrusted = True
lRetCode = oCompany.Connect()
If lRetCode <> 0 Then ' if the connection failed
oCompany.GetLastError(lErrCode, sErrMsg)
MsgBox("Connection Failed - " & sErrMsg, MsgBoxStyle.Exclamation, "Default Connection Failed")
End If
'Create a list of companies...
oRecordSet = oCompany.GetCompanyList ' get the company list

SBO-Common LOGFILE = 40.000 MB/40GB - Wechsel von FULL auf SIMPLE Mode ?

Guten Morgen,
unsere B1 läuft seit Oktober 2009. Aktuell ist das Logfile der SBO-Common-DB bei 40.000 MB Größe angelangt.
Als Lösung wurde mir vorgeschlagen:
- DB -> Eigenschaften -> Optionen - Mode von derzeit FULL auf SIMPLE zu stellen
- DB -> Task -> Shrink -> Database
Ist das eine gute Lösung ?
Darf ich fragen, wie bei Euch die Einstellungen am SQL lauten ?
(Unser System: PL10HF2-SP1 - SQL-2005 SP2)
Vielen Dank für Eure Wissenwerte.
Gruß
Markus

Hallo nochmal,
wünsche frohes neues Jahr...
habe es so gemacht, wie mir vorgeschlagen wurde vom SAP-Partner:
- DB -> Eigenschaften -> Optionen - Mode von derzeit FULL auf SIMPLE zu stellen
- DB -> Task -> Shrink -> Database
Gesamtdauer: ca. 1 Minute
Ergebnis: wie gewünscht
Danke und viele Grüße
Markus

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

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

SBO-COMMON demasiado grande

Similar Messages

Maybe you are looking for