Sbo-common_log.ldf

running 2007 SBO
The above file is now 32GB!!!!!
can we take action to delete file and reset back up conditions?

Hi Chris,
Option 1
You can use DB shrink, which can significantly decrease the log file.
sql help can provide you detail information
Option 2
1. Verify your sbo-common_log.ldf location.
2. make a backup.
3. kill all active sessions
3. detach the sbo-commom db.
4. delete sbo-common_log.ldf.
5. attach sbo-common db, sql will create a new log.ldf file for you.
Thanks and Best Regards
Bruce

Similar Messages

SBO-Common_log grow up to 10 Gig!

Hi friends!
how can i drop/decrease log of SBO-Common DB?
at one of our clients SBO-Common_Data.mdf is of 64Mb, but SBO-Common_Log.ldf is up to 10Gb!
i've read many other forums and i didn't find there any agreement between points of view. Someone tolds that it should be done by LogBackUping and then LogShrinking, others say that it can be done by DB-detaching, deleting ldf-file and then attaching..
could u publish here your methods of decreasing SBO-Common log size?
P.S.: i've done it by 2nd method described before
thanx!

Hi Zsolt & Alexey,
Just to mention (mainly for other readers in this forum):
The SBO-Common database is - as you certainly already know - only used to store binaries like the OBServerDLL.DLL, upgrade package for the SAP Business One client, the Add-On installers and some additional things (info which license server to use, cahced list of DBs in this DB server etc.).
I.e., there's absolutely no need to keep the log information...
Besides using SQL Server Enterprise Manager you can simply run SQL queries to apply suitable settings re size of the logfile:
/* Reduce size of the logfile to xxx MB.... */
/* Please note the particular commands need to be run one-by-one... */
<b>/* Please replace "TMPE-Common_Log" with the "filename" of your logfile (in the DB properties; not the name in the filesystem...)*/</b>
PRINT 'Process <Shrinking Databases> starts'
USE "SBO-Common"
GO
DBCC SHRINKFILE ("TMPE-Common_Log", 1)
GO
/* Limit the max. size of the logfile to e.g. 500 MB
(only works, if current size is less than 500 MB); not sure also about dependencies on number of logged on users etc... */
ALTER DATABASE "SBO-Common"
MODIFY FILE
NAME = "TMPE-Common_Log",
MAXSIZE = 500MB
GO
/* Sets the size of the logfile to 500 MB
(no growth needed, if max. size is 500 MB => no fragmentation)*/
ALTER DATABASE "SBO-Common"
MODIFY FILE
NAME = "TMPE-Common_Log",
SIZE = 500MB
GO
/* Prevent logfile growth */
ALTER DATABASE "SBO-Common"
MODIFY FILE
NAME = "TMPE-Common_Log",
FILEGROWTH = 0MB
GO
PRINT 'Process <Shrinking Databases> has finished'
However, you will need to get rid of the existing 10 gig logfile first, but as I mentioned regardless how you do that, you won't loose real "data"...
HTH,
Frank
Message was edited by: Frank Moebius

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

What makes the SBO-COMMON_log grow...

Does anyone know what makes this file grow?
We have a client with only a handful of users and not much data. Their production database is only 433 MB, but their common log grew to 25 GB (it was set to restrict growth to 26 GB).
On the other hand, we have another client with 16 users and a decent amoung of data being entered. Their production database is 2.5 GB, and even though their common log file was set to restrict growth to 2048 GB (that is not a typo and has been changed), it was only at 1.27 GB.
What would make one grow that much bigger than another?
Thanks for any help.

Dear Vaughn,
Please check the SAP note 1002099 at first and apply the suggestion from
there.
If still you will get the same issue, then run the following query according
SAP note 625546:
DBCC SHRINKFILE ('sbo-common_log', 10)
This should shrink the log file.
To prevent this situation in the future you have to set the recovery
model of the SBO-Common to simple:
Open the MS Enterprise Manager and right-click on the database
SBO-Common > Properties > Options > Recovery Model > Simple
For the SBO-Common it not necessary to use the log file.
For detailed information regarding issue please refer to:
http://channel.sap.com/sbo/documentation -> Support for SAP Business One
-> Archive: Empowerment Sessions -> SYSTEM / SDK - Installation,
Upgrades etc. -> Basics for Optimizing Performance from 07.11.2006.
Regards,
Rakesh Pati
SAP Business One Forum Team

SBO stop functioning and size of SBO-Common is huge

Hi Forum,
I am facing one problem since last two week that SAP HANG on on Server and client.
We are using Windows 2003 R2 server and Windows XP as client. For Remote conneciton we are using GoGlobal.
SAP Business One 2005 B PL 25 we are using. Addon are TDS, XL Reporter, our customised ADDon is using.
And yes size of Database is appx. 6 GB and size of SBO-Common_log.ldf is appx 209 MB after shrinking. Before Shrinking it was 470 MB.
We are daily clean-up temp files and other things at both server and client places.
Please help..
Thanks,
With Best Regards
Chintesh Soni

Hi Chintesh,
Your db size is not that huge. It may only be a little bit more than average. The slow performance could be affected by other factors like hardware, network related or anything could have contributions. You would be better check it in the test environment to narrow down the true cause of the problems.
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

SBOCOMMON_LOG.LDF

Buenas Tardes;
Hoy por la mañana me percate que mi disco duro del servidor esta lleno y windows me avisa que tengo poco espacio en el disco.
Instale el windirstat para ver que estaba pasando y logre identificar que el archivo SBO-COMMON_LOG.LDF mide 58 GB
Como puedo solucionar, no me he atrevido a tocar este archivo, favor su ayuda.

Hola Douglas
Intenta esto cuando, no haya nadie dentro del sistema
Para reducir el tamaño del log de una base de datos Sql Server debe realizar el siguiente procedimiento:
1. Acceder a un administrador de bases de datos remoto como SQL Management Studio.
2. Clic derecho sobre la base de datos en el panel izquierdo explorador de objetos.
3. Seleccionar la opción "Propiedades".
4. Clic en el panel izquierdo en la opción "Opciones".
5. Modificar el "Model Recover" por Simple.
6. Ejecutar el siguiente query
dbcc shrinkdatabase('nombre_basededatos')
7. Cambiar nuevamente el "Model Recover" a Full.

How to change server in SAP B1 8.8

Dear All,
I have a problem in using SAP B1 8.8. I have 2 separated server which is one is contain license server and the other server contain database company. My client doesn't want the company database in one server with license server. In SAP B1 2007 that my client used before, this is not a problem. But now, in SAP B1 8.8, it's become a problem because SAP remove "CHANGE SERVER" button in modul change company. I tried to click in the server list but the server that appear is License Server only. I can't find Database Server.
So, How can i choose the database server ?
Pls help

Hi,
before you can add your <server-name>\SQLEXPRESS you must have your SBO-COMMON database available in SQL Server.
If you have the original SBO-COMMON.mdf and SBO-COMMON_log.LDF files just place them under you SQL Server DATA folder (e.g. C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA) and Attach from MS SQL Server Management Studio.
Also attach any company databases.
After that you can add <server-name>\SQLEXPRESS as follows:
- open SAP B1 Service Manager
- select License Manager service and click Settings
- click Configure Security (bottom left)
- enter password and click OK
- enter your Connection Settings e.g.
    MSSQL_2008
    <server-name>\SQLEXPRESS
    sa
    <sa-user-password>
- click OK
That will take care of the connection settings but not of your Add-ons registration.
So if you have any add-ons (e.g. Screen Painter, Fixed Assets, etc.) you will have to manually edit the AddOnsLocalRegistration.sbo file (under C:\Program Files\SAP\SAP Business One) and change any
Name="<server-name>" entries to Name="<server-name>\SQLEXPRESS"
Save the modified file.
Now start the SAP client, press Change Company and set you Current Server to <server-name>\SQLEXPRESS
Done.

DTW works very slow

Hi there,
i currently want to update about 6000 contact persons in bp master data. Therefor i prepared 2 csv files.
First one :
RecordKey;CardCodeDefaultContact
Second one :
RecordKey;LineNum;Title;Name
The DTW runs about 12 hours and only has updated about 1500 records. Whats wrong ? There is no error, every record is updated very well. But normally it runs very fast.
We use B1 2007 PL45 on a Win 2003 SQL 2005 with actual patches on a 4 CPU / 16 GB RAM machine.
I restarted the server, but it runs slow.
Regards Steffen

Hi Mario,
Do you know about any differences regarding environment between the run back in December and the current run? Am I right, if assuming the PL of SAP Business One did not change?
Nothing has changed without the year. In December we installed PL45 for some reasons, but from their nothing changed.
How is the daily overall performance with SAP Business One?
The performance is very well, there is no problem. Every process runs in a good time.
Did you check the size of SBO-Common.ldf and DBname.ldf?
I maintained the database yesterday. None of the files are to big.
Configure a Native Client connection, eventhough DTW runs on the very same machine.
Can you reproduce the issue in another (test)environment?
I tried to run the update process on different computers. There is only a problem by updating the contact persons or some other information of an existing bp. If i insert new bp or update for example article, the DTW runs very fast. Last week i imported about 2000 articles in less than an hour.
PS: Personally I am interested to gather, if a combination of 2007 A SP00 PL 47 and MSSQL 2008 would speed up that process?
Accordingly to Microsoft MSSQL 2008 Server advertising that Server should deal much faster with queries. In addition MSSQL 2008 has in my opinion a better activity monitor (shows better statistics, locks, less performant queries, ...)
I know there is a better performance with SQL 2008, but SAP do not support this version. Otherwise i could install B1 on a linux system, to get TOP performance. But it is not supported too
Regards Steffen

SBO Server Crashed

Hi,
My SBO Server has crashed. Only thing I could recover is all mdf ldf files. Now I want to re-setup the system.
Plz suggest me the steps that I should follow (Including patch upgrade).
The installation file I've is
SAP Business One 2005 B (7.40.243) SP: 00 PL: 05
Thanx in Adv.

Hi,
I suggest to install the SQL server 2005 first and then SBO application consists of :
1. Installing server application and server tools
2. Installing client
3. Installing optional components
After that, attach the mdf file to the SQL server. you could use this steps:
1. Open SQL server
2. Right click databases --> click/select attach
3. In the attach database window --> click add button (located in the center) to attach the mdf file
4. if there is no log file, you could highlight the log file and then click remvoe button.
Next steps are to open SAP B1 client, then after client is successfully run, upgrade the patch level. The steps are upgrade server tools, common database and help file.
let me know if there are any errors happened in the above processes.
Rgds,

Database restore from SQL 2000 to SQL 2005 for SBO 2005B

Hi Everyone,
I am facing some problems in regards to the restore of SBO Database from SQL 2000 to SQL 2005.
Let me explain you the problem.
See I am using SAP B1 2005B with patch level 38 in my laptop with SQL 2000. I have made an company in this and done work in it as a production company and now I want to restore this company in the server which has SQL 2005. How to do it.
I have taken a backup in my laptop from SAP B1 Server Suite Manager which has SQL 2000 and sucessfully backed up but when I am trying to restore in the server which has SQL 2005 I am getting the following error in SQL 2005 in server :-
Restore failed for Server 'DXBAP001'. (Microsoft.SqlServer.Smo)
System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program Files\Microsoft SQL Server\MSSQL\data\SBO_DCHAR.mdf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Smo)
Please let me know the solution for it.
Thanks in Advance.
Regards,
Kawish Junaid Mazhari

Hi,
In SQL 2005 create a database and name as the 200 one was (though any name would do). when you create the database note the location of the .mdb and .ldf file.
once this had created right click on your new database > tasks > restore database
in the new window select from device and point it to your .bak file created from your 2000 system, ensure you put a tick in the restore box on the new line.
in the options tab tick overwrite database, and, change the file locations in the restore as directory to the file locations of the new database. the file names must be the same too.
you can change the original file names after the restore.
that should do the trick.
thanks,
mike

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

SBO Backup not backing up one of the Company Database

Hi Expert,
My customer environment is :-
Windows Server 2008 R2 SP1
MS-SQL 2005 SP3
SAP B1 2007B PL15 Hotfix
There are 8 company databases ticked in SBO Backup Database tab. 7 of them are backup successfully at the scheduled time, except 1. The MDF file is 3GB and the LDF file is around 800MB. There are still around 45GB free disk spaces remaining in this drive.
May i know why this database not backup?
Thanks,
Taw-Fey
Edited by: Taw Fey Tan on Mar 22, 2011 8:49 AM

Hi Bala,
I have tried to just run SBO Backup for that particular company. Still no backup happen.
But there is an error in Windows Event Viewer Application Log with SBO Backup.
ERROR
The description for Event ID 166 from source SBOBackUp cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The specified resource type cannot be found in the image file
Please advice what else should i do, thanks.
Taw-Fey, Tan

Error using "LDF Database Open.vi" for LDF 2.1 file

Hi there,
I use the USB-LIN for a simulation for LIN bus. We had the LDF file of version 2.0 before but now we get a new LDF file which is in version 2.1.
We used
LDF Starter Kit for LIN 1.0.1
to read the LDF file but it seems that the kit doesn't work any more with the LDF version 2.1.
It there a workaround for the LDF file with version 2.1.
Thx,
Wilbur

Hi,
The NI USB-LIN was created to work with the version 1.3 network standard. However, version 2.0 and 2.1 are backwards compatible, so the NI USB-LIN will work with these networks as well.
there is currently not a plan to update it for LIN 2.1.
Note: The new features introduced in version 2.0 and 2.1 network standards will not be natively supported with the NI USB-LIN.
LIN Version 1.3, 2.0, and 2.1 Comparison
Feature
Supported by NI USB-LIN
LIN 1.3
Yes
LIN 2.0
Yes*
Enhanced checksum
Yes
Off the shelf slave node concept
Yes*
NCF format
Yes*
Diagnostics and slave node configuration
Yes*
Byte arrays
Yes
LIN 2.1
Yes*
New slave node configuration services
Yes*
Slave diagnostics class I-III
Yes*
Functional addressing
Yes*
Resolution table
Yes*

Error while running a stored procedure in SBO

Hi all,
i have a stored procedure that i run in my sbo. When i run the stored procedure i get the following error :
1). [Microsoft][SQL Server Native Client 10.0][SQL Server]Warning: Null value is eliminated by an aggregate or other SET operation.
'Servicecontracten' (OCTR)    05/10/2011 18:03:36 -1
i launch my sp like this :
exec [spu_DS_HistProjektUserVeldenViewBetalingen] (i pass no parameters while testing. i put them fix in my sp)
my stored procedure looks like this :
USE [def1]
GO
/****** Object: StoredProcedure [dbo].[spu_DS_HistProjektUserVeldenViewBetalingen]    Script Date: 10/05/2011 18:03:05 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- Batch submitted through debugger: SQLQuery2.sql|8|0|C:\Users\kvanhauwaert\AppData\Local\Temp\~vs2A98.sql
ALTER PROCEDURE [dbo].[spu_DS_HistProjektUserVeldenViewBetalingen]
          /* @project_number varchar(20),
          @billperiod_type varchar(10) */
AS
BEGIN
     SELECT isnull(lijnnr,0) as lijnnr, isnull(fase,'') as fase, isnull(factuurbedrag,0) as factuurbedrag,
     isnull(billperiod_type,'') as billperiod_type
     INTO #tempDS_HistProjektUserVeldenViewBetalingen
     FROM DS_HistProjektUserVeldenViewBetalingen t1
     WHERE project_number = '08053A'
     SELECT isnull(lijnnr,0) as lijnnr, isnull(fase,'') as fase , isnull(factuurbedrag,0) as factuurbedrag,
          (select sum(isnull(factuurbedrag,0)) from #tempDS_HistProjektUserVeldenViewBetalingen where lijnnr <= t1.lijnnr) as lijntotaal,
          (select sum(isnull(factuurbedrag,0)) from #tempDS_HistProjektUserVeldenViewBetalingen where lijnnr <= t1.lijnNr and billperiod_type = '110-01' ) as lijntotaalKetting
     FROM #tempDS_HistProjektUserVeldenViewBetalingen t1
     WHERE fase,'') is not null
     ORDER BY t1.fase
     DROP TABLE #tempDS_HistProjektUserVeldenViewBetalingen
END
GO
Somebody has a clue what i'm doing wrong ?
thnx

Thanks Gordon for your reply.
i've changed my sp to :
USE [def1]
GO
/****** Object: StoredProcedure [dbo].[spu_DS_HistProjektUserVeldenViewBetalingen]    Script Date: 10/05/2011 18:56:34 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- Batch submitted through debugger: SQLQuery2.sql|8|0|C:\Users\kvanhauwaert\AppData\Local\Temp\~vs2A98.sql
CREATE PROCEDURE [dbo].[spu_DS_HistProjektUserVeldenViewBetalingen]
          /* @project_number varchar(20),
          @billperiod_type varchar(10) */
AS
BEGIN
     SELECT isnull(lijnnr,0) as lijnnr, isnull(fase,'') as fase, isnull(factuurbedrag,0) as factuurbedrag,
     isnull(billperiod_type,'') as billperiod_type
     INTO #tempDS_HistProjektUserVeldenViewBetalingen
     FROM DS_HistProjektUserVeldenViewBetalingen t1
     WHERE isnull(project_number,'') = '08053A'
     SELECT isnull(lijnnr,0) as lijnnr, isnull(fase,'') as fase , isnull(factuurbedrag,0) as factuurbedrag,
          (select sum(isnull(factuurbedrag,0)) from #tempDS_HistProjektUserVeldenViewBetalingen where isnull(lijnnr,0) <= isnull(t1.lijnnr,0)) as lijntotaal,
          (select sum(isnull(factuurbedrag,0)) from #tempDS_HistProjektUserVeldenViewBetalingen where isnull(lijnnr,0) <= isnull(t1.lijnNr,0) and isnull(billperiod_type,'') = '110-01' ) as lijntotaalKetting
     FROM #tempDS_HistProjektUserVeldenViewBetalingen t1
     WHERE isnull(fase,'') <> ''
     ORDER BY t1.fase
     DROP TABLE #tempDS_HistProjektUserVeldenViewBetalingen
END
GO
but that didn't solved my problem. Any other idea's ?
kind regards.
Kurt

Sbo-common_log.ldf

Similar Messages

Maybe you are looking for