SQL LOG FILE SIZE INCREASING

Hi DBA's
SQL Log file size occupies more disk space on the server, the overall database size is 8GB
How to decrease the SQL LDF file size on the server, please explain the suitable steps to perform
Thanks
DBA

use master
go
dump transaction <YourDBName>
with no_log
go
use <YourDBName>
go
DBCC SHRINKFILE (<YourDBNameLogFileName>,
100) -- where 100 is the size you may want to shrink it to in MB, change it to your needs
go
-- then you can call to check that all went fine
dbcc checkdb(<YourDBName>)
Andy ,
what point in asking user to use No_log and you did not even motioned about what this eveil command will do. Actually its
seriously not required reason being initial size of log file set to 8 G.
Plus what is point in running checkdb ?
I don't agree to any part you pointed
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

SQL log file size is extending rapidly

Hello All,
We are using ECC 6.0, our database is SQL 2005 & operating system is Windows NT 4x AMD64 L.
Our database log file size is increasing rapidly, now its size is more than the all 4 data files (near about 300gb).
Last week I tried to shrink log file but it didn't worked.
Now less space is remained on disk, please help me.
Now the system is started giving dump at the time of log in, & the dump is like "START_CALL_SICK ".
I am attaching dump error text file.
Please help why is this happening.
Thanks in advance
Mahendra

Hi,
I have backed up log file & shrink the file but it didn't worked for me
What is the result? It shrinks the log and release all the space (for all committed transactions).
How can i add another log file?
Can i delete old log file after adding new log file.
You can add another log file by following below steps. but in your case, this is not the right solution because you have good amount of log file configuration for your database (now its size is more than the all 4 data files (near about 300gb)).
Open SQL server management studio > Expand database > Right click on database > Select Files > Click on Add > Give the input parameters (Logical file name, path, initial size etc.) click on OK
If system is not allowing you to shrink the log file, it means you have active transactions in system which are continuously using your log file.
Regards,
Nick Loy

Log file size increasing

Hi,
the log file in our Oc4j-soa container is getting increased once in 2 min with the following messages:
<soa-home>/opmn/logs/default~oc4jsoa~log
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor weblogic.jms.ConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by:
       Missing class: weblogic.jndi.WLInitialContextFactory
     Dependent class: com.sun.naming.internal.VersionHelper12
              Loader: jre.bootstrap:1.5.0_19
         Code-Source: unknown
       Configuration: jre bootstrap
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.]
Please examine the log file to determine the problem.
     at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:207)
     at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:98)
     at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:192)
     at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:133)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:428)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:419)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:382)
     at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:106)
     at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
     at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:113)
     at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:283)
     at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:232)
     at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:199)
     at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:151)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is oracle.classloader.util.AnnotatedClassNotFoundException:
       Missing class: weblogic.jndi.WLInitialContextFactory
     Dependent class: com.sun.naming.internal.VersionHelper12
              Loader: jre.bootstrap:1.5.0_19
         Code-Source: unknown
       Configuration: jre bootstrap
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:179)
     at oracle.tip.adapter.jms.JMS.JMSFactory.jndiLookup(JMSFactory.java:227)
     at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:138)
     ... 16 more
Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
     Missing class: weblogic.jndi.WLInitialContextFactory
     Dependent class: com.sun.naming.internal.VersionHelper12
     Loader: jre.bootstrap:1.5.0_19
     Code-Source: unknown
     Configuration: jre bootstrap
This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
The missing class is not available from any code-source or loader in the system.
     at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2078)
     at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1679)
     at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1635)
     at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1620)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
<2010-02-24 03:42:32,224> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #2291
<2010-02-24 03:43:03,701> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connect...
it goes on like this. Please suggest a solution to stop this since the size of the log is becoming large also it is very difficult to find other error messages in it.

Hi,
Weblogic.jar is not present in <SOA_HOME>/j2ee/"OC4J_SOA"/connectors/JMSAdapter/JMSAdapter directory. But I am able to post message to the queue. No error is coming while initiating the BPEL process also I could see the message in the queue.
But only in the log file, those error messages are coming.

Log Configurator - Increase log file size from 10 mb to 20 mb

Hi All,
We have implemented custom logging in our implementation using custom Log Destinations and Locations.
The log destination (inside log configurator service) we were using earlier had size of 10 mb for each file and the file count was 5.
Now, as the log files are getting archived very soon we changed the log file size to 20 mb and file count as 5.
After restarting server, the log viewer in NWA and within Visual Admin does not show updated logs. We have monitored this for sometime now so that new logs are written to the log files still the situation is same.
Strangely, logs are getting updated at OS level in the log files but the entries are nto shown on Log Viewer in NWA or Visual Admin.
Are there any restrictions on the log file size or any other parameter needs to be changed to make this work ?
Looking forward for your inputs and suggestions.
Regards,
Prasanna

Hi All,
We have implemented custom logging in our implementation using custom Log Destinations and Locations.
The log destination (inside log configurator service) we were using earlier had size of 10 mb for each file and the file count was 5.
Now, as the log files are getting archived very soon we changed the log file size to 20 mb and file count as 5.
After restarting server, the log viewer in NWA and within Visual Admin does not show updated logs. We have monitored this for sometime now so that new logs are written to the log files still the situation is same.
Strangely, logs are getting updated at OS level in the log files but the entries are nto shown on Log Viewer in NWA or Visual Admin.
Are there any restrictions on the log file size or any other parameter needs to be changed to make this work ?
Looking forward for your inputs and suggestions.
Regards,
Prasanna

Reduce the Production Log file size(.LDF)

Hi Everybody,
We are using R/3 ECC 6.0 VERSION with SQL 2005 Database. For the past two days our Production Server Performance is very slow due to the size of Production Log file(.LDF) it crossed 17 GB. i want to reduce this Log file size. i dont know how. plz some one help me to do this job.otherwise this will become Serious Issue.
Points will be rewarded
Thanks
Siva

How did you trace the slowness back to the log file? A 17 GB log file is on the small side for a Production system. I don't think a hotfix is going to fix your log growth.
Is the log on the same physical disk as your data files? Is it on a very slow hard drive or is the drive having an I/O problem? That is the only way it would impact performance to a noticable degree. A large or small log file will have no real effect on performance since it is just appended to and not read during writes, and in most production environments it is on a seperate disk or part of a SAN.
You can decrease its growth by increasing your log backup time. Do you back it up now? You can probably set your backup software to shrink the file when it finished backing up. You should consult your DBA team and ask for their advice, they can quickly point you in the right direction.

BackPRD.log File Suddenly Increases to 78GB in SAPBACKUP folder in Linux server

Dear Experts,
There is a problem in our SAP Production server. As earlier when i check the space it is good and after 25 Minutes while i am checking of the Directory spaces, the Backup folder size increases suddenly to 100 more than earlier it is. The backPRD.log file size earlier it is 13 MB and it is Now showing as 78 GB. Is there any thing to resolve the issue and i have checked some forms also there is no thread for the same issue. With this the Restoration is also not possible Using the Source system Backup on Target system.
Thanks, Regards,
Harsha.

Hi Sanjay,
Could you confirm for
1.Any recent changes into DB as well as at the end of backup device (Could be a third party software or hardware) ?
2.Any recent SP,kernel,DB upgrade as well as OS upgrade activity performed at your end ?
3.Any modifications under backup schedule if using it from DB13 or any changes under third party scripts ?
4.Have you activated trace for the system ?
Addition to all if you're able to login to system than please share system logs from SM21,recent dump details from ST22 if any.
With this the Restoration is also not possible Using the Source system Backup on Target system.
With the above logs would like to check alert_<SID>.log file as well.
Regards,
Gaurav

Get Total DB size , Total DB free space , Total Data & Log File Sizes and Total Data & Log File free Sizes from a list of server

how to get SQL server Total DB size , Total DB free space , Total Data & Log File Sizes and Total Data & Log File free Sizes from a list of server

Hi Shivanq,
To get a list of databases, their sizes and the space available in each on the local SQL instance.
dir SQLSERVER:\SQL\localhost\default\databases | Select Name, Size, SpaceAvailable | ft -auto
This article is also helpful for you to get DB and Log File size information:
Checking Database Space With PowerShell
I hope this helps.

Log file size in Sun Directory Server

Does anyone have an idea about the how the Sun Directory Server's log file size will increase in size with respective to the actions performed?
Can someone give a data regarding this? If someone has a better scenario and the supportive data w.r.t log file size it will be helpful.
Thanks,

AFAIK No its based on time "At a certain time, or after a specified interval, the server rotates your access logs. "
More info in Archiving Log Files in [http://docs.sun.com/app/docs/doc/820-7985/gczxv?l=en&a=vie]
It should be easy to write such a script to be run as a daemon in logs directory. Here is the pseudo code :
while [1]
do
get size of the access/error log file
If size of file > max_size
<ws-install-dir>/https-<instance>/bin/rotate
sleep for sometime
done

Log file size in Sun Access Manager

Does anyone have an idea about the how the Sun Access Manager's log file size will increase in size with respective to the actions performed?
Can someone give a data regarding this? If someone has a better scenario and the supportive data w.r.t log file size it will be helpful.
Thanks,

I would like to take the log files backup daily (for future reference).
I need to know the following:
1) What log files need to be backup? Do I need to take all am*.* files (It will be around 3.5 GB in size)?
2) Ideally, I believe that only few MB of data goes into these am*.* files but, I cannot store every day 3.5 + GB of logs
3) I observed that these files (am*.* have every days activity added to them), So I would like to enable the Log rotation
Please let me know how can I proceed.
Thanks

MessageBox log file size

Hi,
In our prod environment, the MessageBox data file is withing the recommended limits - 2GB, but the log file is 32GB. Is this a reason to worry, or it is normal? I couldn't find any recommendations on this.
Thank you very much!

This is not normal.
IMO your BizTalk database Jobs are not running , Make sure your BizTalk SQL servers jobs have been enabled and SQL server agent is running.
Please have a look of
How to Configure the Backup BizTalk Server Job article to enable the jobs.
The BizTalk backup job is responsible for keeping the log file size in the limit.
you can try shrinking the log file using following SQL command
USE BiztalkMsgBoxDb;
GO
-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE BiztalkMsgBoxDb
SET RECOVERY SIMPLE;
GO
-- Shrink the truncated log file to 1 MB.
DBCC SHRINKFILE (BiztalkMsgBoxDb_Log, 2);
GO
I would recommend you to have a read of following articles
BizTalk Environment Maintenance from a DBA perspective
BizTalk Databases: Survival Guide
hope this helps.
Greetings,HTH
Naushad Alam
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or
Mark As Answer
alamnaushad.wordpress.com

How to set up PopProxy* log file size ?

Dear All,
Does anybody know how to set up MMP PopProxy* log file size and rollovertime ?
./imsimta version
Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)
libimta.so 7.0-3.01 64bit (built 09:24:13, Dec 9 2008)
Steve

SteveHibox wrote:
Does anybody know how to set up MMP PopProxy* log file size and rollovertime ?Details on these settings are available here:
http://wikis.sun.com/display/CommSuite6U1/Communications+Suite+6+Update+1+What%27s+New#CommunicationsSuite6Update1What%27sNew-MMPLogging
Regards,
Shane.

VMX20 - Limit virtual machine log file size and number

Hi all,
Here is parameter file
log.rotateSize=1000000
log.keepOld=10
that I have apply on virtual machine VMX. After I run the compliance checker again and it still showing fail.
I also have try restart the virtual machine machine few time but the log file keep increase.
For my understanding if we apply this parameter setting once the virtual machine log file over 1,000kb or 10 log file the new log file will replace the old one, correct me if Ii wrong.
Here is my question
1. Did the parameter file have restrict on any version of VMware?
2. If the log file less than 1,000kb and it already have 10 log file, so the new log file will still replace the old log file?
Thk.
Best regards.
Wong Pak Lian

Hi a_nut_in,
The problem have been solved in VMware vsphere version 5 with compliance checker for vsphere 5.0.
But under VMware vsphere version 4 I have found out the parameter is ok and workable but the results is still showing fail, will this is software bug?
Thk.
Best regards.
Wong Pak Lian

File sizes increase in StarOffice 8

I've got a letter I send out about once a month, just changing dates in the contents for each edition. It has a linked .jpg file as background.
In StarOffice 7 the .sxw file size is 8 Kb.
In StarOffice 8 the size has leapt to 44 Kb, whether I save it in .sxw or .odt format.
Why?

I find that file sizes increase both with text documents and with spreadsheets, sometimes by a great deal. One of the reasons I switched from 5.2 to 7 was the much smaller file sizes, since I keep my weekly back-ups on floppies (and am a stingy sort of fellow generally). But I had to run 7 and 5.2 together, since 7 does not handle Sanskrit/Hindi founts (the SO "help" team just asked a whole lot of questions and then disappeared). So now I have (on Windows) 5.2, 7 and 8. I have still not checked if 8 handles these founts. If it does, I can remove 5.2. For the rest, 8 does not seem to offer any advantage over 7 -- not counting the data base, which I have still to look into. File size, in my view, goes against it.

Log file size

We have a DNS Server running on solaris 9, it's generating huge logs hence /var/adm/messages file size is vey big. Is there any way to create seperate log file for everyday or can I restrict the log file size for a single file.
Thank you

Hmmm,
For what type environment is this DNS server used for? How many domains/delegated domains are configured on the host?
I think by default BIND allows 1000 recursive lookup connections. (That is already plenty and if you have that amount of legitimate traffic you will have to add more DNS servers and configure the nodes accordingly)
Is the server listed as a Name Server for your domain and used externally for name resolution for your domain host entries, maybe the SOA?
nslookup (enter)
set type=ns (enter)
you_domain_mane (i.e. your_domain.com) (enter)Or
dig �q NS your_domain.com
If the affected server returns in the list it is NEVER EVER a good idea to allow recursive lookups.
My guess is that you are subject to denial of service, unless you host a fairly large environment with 1000s of hosts.
Change the recursive-cient connection back (you system cannot handle 5000 recursive lookups and your system utilization shows this.)
Then configure
�category queries { your_query_file; };� In your namd.conf
restart BIND
Use �rndc� to change the trace level to 1
Let it run for 2 -5 min and stop BIND entirely
Then run something like:
�cat your_query_file | cut -d'/' -f2 | sort | uniq �c | more� (depends on the log file format, better yet use nwak)
take a quick look to see if there is one IP that is hammering your system.

Archive Log file size

I am using Oracle database 9.2.0.1.0, My OS is Linux AS4 Update version.
My database is in archive log mode, the archive file size generated on disk is 100 MB. I want to monitor the reason that why the size of redo generated is too big.
Kindly suggest.
Regards

Archived log file size will always be the same size as redo log or less than the redo log size (but never bigger than redo log size)
ARCHIVE_LAG_TARGET is the reason (apart from manual archiving ALTER SYSTEM ARCHIVE LOG CURRENT/ALL) why you see archived logs with lesser size than redo log
why archive log file size constanly change?

SQL LOG FILE SIZE INCREASING

Similar Messages

Maybe you are looking for