Truncating log files

Are there any server settings that will truncate logs on startup?
Thanks in advance,
Josh Cimino
Software Developer
Mxi Technologies Ltd.
1430 Blair Place, Suite 800
Ottawa, ON, Canada
K1J 9N2
E: [email protected]
T: 613.747.4698 ext 479
F: 613.747.1909
www.mxi.com
"From the flight line to the bottom line"
[att1.html]

Exchange 2013 SP1. I have about 30 databases in a 4 server DAG, with half the DBs on servers 1 and 2 and the other half on 3 and 4. All copies show healthy. When I run Get-MailboxDatabase
–Status | ft name,last* -auto it shows the last full and incremental backups as about a month ago, despite many successful backups since then, according to Arcserve anyway. And, log files are not truncating. Any ideas?
Did you apply the Nov 2014 Updates? If so, that may explain the issue as a VSS bug was introduced. Make sure you have installed the latest updates:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c78faf9a-e126-4f51-b8fe-69d547a9d365/november-2014-update-rollup-kb3000853-vss-backups-broken?forum=winserver8gen
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Truncating Log file - SQL

Hi All,
We need some help in reducing the size of our log files.
Our database has grown to 17gig and our log file is just over 12gig. Our database recovery model is "full".
We are running complete backups once a night, and also doing an hourly transaction log backup. I have tried right clicking the database in EM->all tasks->shrink database and specifically selected the log file and clicked ok, as well as just clicking ok, but there seems to be no effect.
Can anyone outline how to do this? From what I can tell, we are only using around 50Mb of the logfile and the rest is just empty space!
Thanks
Rajiv

Ok, lets split this up into 2 issues to keep things simple:
1. In our present situation (using the FULL recovery model), we are performing a full backup every night. We are also backing up the transaction log every hour during working hours. In this scenario, from what I understand the transaction log file should be truncated to the point of backup. This is not happening on my server, so I am asking for guidance as to the best way to investigate why this is happening, and then of course the best way of truncating the file manually (T-SQL?).
2. In terms of the recovery model, in our business people phone in with orders, payments etc which are all input directly into B1. We physically wouldn't be able to recover back to the previous day/last full backup, as alot of the input data isn't on paper/email. I have done a test restore with backup + logs etc previously - it's not difficult per se, just lo-ong =).
The change in hardware works 2 ways... yes, you're right in that hardware may be more reliable, but the basic business need for recovery in the event of failure remains unchanged (in our specific case). In contrast however, as the hardware gets faster and faster, our 17gig DB + logfile (note, this should be nowhere near 12gig) will not be as incumbent as perhaps one might expect on our file server. Now if we can do full backups semi-transparently using the simple model every hour on newer hardware... that's one less thing to worry about! =)

Crystal Report Server Database Log File Growth Out Of Control?

We are hosting Crystal Report Server 11.5 on Microsoft SQL Server 2005 Enterprise. Our Crystal Report Server SQL 2005 database file size = 6,272 KB, and the log file that goes with the database has a size = 23,839,552.
I have been reviewing the Application Logs and this log file size is auto-increasing about 3-times a week.
We backup the database each night, and run maintenance routines to Check Database Integrity, re-organize index, rebuild index, update statistics, and backup the database.
Is it "Normal" to have such a large LOG file compared to the DATABASE file?
Can you tell me if there is a recommended way to SHRINK the log file?
Some Technical Documents suggest frist truncating the log, and the using the DBCC SHRINKFILE command:
USE CRS
GO
--Truncate the log by changing the database recovery model to SIMPLE
ALTER DATABASE CRS
SET RECOVERY SIMPLE;
--Shrink the truncated log file to 1 gigabyte
DBCC SHRINKFILE (CRS_log, 1000);
GO
--Reset the database recovery model.
ALTER DATABASE CRS
SET RECOVERY FULL;
GO
Do you think this approach would help?
Do you think this approach would cause any problems?

my bad you didn't put the K on the 2nd number.
Looking at my SQL server that's crazy big my logs are in the k's like 4-8.
I think someone enabled some type of debugging on your SQL server, it's more of a Microsoft issue, as our product doesn't require it from looking at my SQL DB's
Regards,
Tim

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

CPO SQL Log Files

Hey guys
We have started to see an exponential growth in our SQL log files that is in direct correlation with running more processes more consistently.
Has anyone had any issues with running a log truncating script to both the TEO_processlog and TEO_reportinglog files?
something along the lines of
ALTER DATABASE ExampleDB SET RECOVERY SIMPLE
DBCC SHRINKFILE('ExampleDB_log', 0, TRUNCATEONLY)
Thanks
Matt

Matt,
Yes, many people (if they do not need the t-logs) will reduce them. In 3.0 (during install) you can actually set it to SIMPLE mode instead of the more full recovery mode. I do that on most all of my boxes. Prior to CPO 3.0 you would have to do it like you show above.
On most of my pre 3.0 boxes I would do something like
USE <TEOProcess_DB_Name>;GO
-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE <TEOProces_DB_Name> SET RECOVERY SIMPLE;GO
-- Shrink the truncated log file to 1000MB.
DBCC SHRINKFILE ("<TEOProcess_log_file_name>", 1000); GO
Of course this is on SQL only. You can find more information on DBCC Shrinkfile at Microsoft's help site.
If you need to reset the database to full mode it's:
-- Reset the database recovery model.
ALTER DATABASE <TEOProcess_DB_Name> SET RECOVERY FULL;GO
--Shaun

Why is the transaction log file not truncated though its simple recovery model?

My database is simple recovery model and when I view the free space in log file it shows 99%. Why doesn't my log file truncate the committed
data automatically to free space in ldf file? When I shrink it does shrink. Please advice.
mayooran99

My database is simple recovery model and when I view the free space in log file it shows 99%. Why doesn't my log file truncate the committed
data automatically to free space in ldf file? When I shrink it does shrink. Please advice.
mayooran99
If log records were never deleted(truncated) from the transaction log it wont show as 99% free.Simple recoveyr model
Log truncation automatically frees space in the logical log for reuse by the transaction log and thats what you are seeing. Truncation wont change file size. It more like
log clearing, marking
parts of the log free for reuse.
As you said "When I shrink it does shrink" I dont see any issues here. Log truncation and shrink file is 2 different things.
Please read below link for understanding "Transaction log Truncate vs Shrink"
http://blog.sqlxdetails.com/transaction-log-truncate-why-it-didnt-shrink-my-log/

Truncate SQL 2008 R2 log files

How do I truncate a log file. Running out of space.
Help is appreciated.
Thanks
Dave Kozlowski

If your db is in Full Recovery:
ALTER DATABASE
[DatabaseName] SET
RECOVERY SIMPLE WITH
NO_WAIT
DBCC SHRINKFILE
([LogFileName, 1)
ALTER DATABASE [DatabaseName]
SET RECOVERY
FULL WITH NO_WAIT
GO
Ayad

How to Properly Protect a Virtualized Exchange Server - Log File Discontinuity When Performing Child Partition Snapshot

I'm having problems backing up a Hyper-V virtualized Exchange 2007 server with DPM 2012. The guest has one VHD for the OS, and two pass-through volumes, one for logs and one for the databases. I have three protection groups:
System State - protects only the system state of the mail server, runs at 4AM every morning
Exchange Databases - protects the Exchange stores, 15 minute syncs with an express full at 6:30PM every day
VM - Protecting the server hosting the Exchange VM. Does an child partition snapshot backup of the Exchange server guest with an express full at 9:30PM every day
The problem I'm experiencing is that every time the VM express full completes I start receiving errors on the Exchange Database synchronizations stating that a log file discontinuity was detected. I did some poking around in the logs on the Exchange server
and sure enough, it looks like the child partition snapshot backup is causing Exchange to truncate the log files even though the logs and databases are on pass-through disks and aren't covered by the child partition snapshot.
What is the correct way to back up an entire virtualized Exchange server, system state, databases, OS drive and all?

I just created a new protection group. I added "Backup Using Child Partition Snapshot\MailServer", short-term protection using disk, and automatically create the replica over the network immediately. This new protection group contains only the child partition
snapshot backup. No Exchange backups of any kind.
The replica creation begins. Soon after, the following events show up in the Application log:
=================================
Log Name:      Application
Source:        MSExchangeIS
Date:          10/23/2012 10:41:53 AM
Event ID:      9818
Task Category: Exchange VSS Writer
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      PLYMAIL.mcquay.com
Description:
Exchange VSS Writer (instance 7d26282d-5dec-4a73-bf1c-f55d5c1d1ac7) has been called for "CVssIExchWriter::OnPrepareSnapshot".
=================================
Log Name:      Application
Source:        ESE
Date:          10/23/2012 10:41:53 AM
Event ID:      2005
Task Category: ShadowCopy
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      PLYMAIL.mcquay.com
Description:
Information Store (3572) Shadow copy instance 2051 starting. This will be a Full shadow copy.
=================================
The events continue on, basically snapshotting all of Exchange. From the DPM side, the total amount of data transferred tells me that even though Exhange is trunctating its logs, nothing is actually being sent to the DPM server. So this snapshot operation
seems to be superfluous. ~30 minutes later, when my regularly scheduled Exchange job runs, it fails because of a log file discontinuity.
So, in this case at least, a Hyper-V snapshot backup is definitely causing Exchange to truncate the log files. What can I look at to figure out why this is happening?

SQLException Error in Log file

Does anyone know of the following error, and how to fix this? I keep getting it in my engine log file like every 30 mn.
Thank you,
-Lilach
--------------------------------------------- Error -----------------------------------------------------------------
Exception [java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.].
Caused by: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
Caused by: [BEA][SQLServer JDBC Driver][SQLServer]The statement has been terminated.
fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.].
     at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
     at fuego.directory.provider.jdbc.mssqlserver.MSSQLServerPersistenceManager.mapSQLException(MSSQLServerPersistenceManager.java:116)
     at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
     at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:221)
     at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:180)
     at fuego.directory.hybrid.jdbc.DelegatorFuegoParticipantAccessor.updateOrPersistHumanParticipant(DelegatorFuegoParticipantAccessor.java:224)
     at fuego.directory.hybrid.HybridParticipantAccessor.updateHumanParticipant(HybridParticipantAccessor.java:377)
     at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
     at $Proxy6.updateHumanParticipant(Unknown Source)
     at fuego.directory.hybrid.HybridParticipantAccessor.fetchHumanParticipant(HybridParticipantAccessor.java:189)
     at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
     at $Proxy6.fetchHumanParticipant(Unknown Source)
     at fuego.directory.provider.notifiers.DirObjectType$3.fetchDirObjectFor(DirObjectType.java:74)
     at fuego.directory.provider.notifiers.DirectoryObjectProxy.getObject(DirectoryObjectProxy.java:160)
     at fuego.directory.provider.notifiers.DirectoryObjectProxy.createAddEvent(DirectoryObjectProxy.java:91)
     at fuego.directory.provider.notifiers.BasePollingEventGenerator.buildEvents(BasePollingEventGenerator.java:148)
     at fuego.directory.hybrid.ldap.LDAPPollingEventGenerator.buildEvents(LDAPPollingEventGenerator.java:109)
     at fuego.directory.provider.notifiers.BasePollingEventGenerator.generateEvents(BasePollingEventGenerator.java:51)
     at fuego.directory.hybrid.HybridMultipleEventGenerator.generateEvents(HybridMultipleEventGenerator.java:43)
     at fuego.directory.provider.notifiers.DirectoryNotifier.notifyChanges(DirectoryNotifier.java:403)
     at fuego.server.service.DirectoryListener.updateEngineFromDirectoryImpl(DirectoryListener.java:328)
     at fuego.server.service.DirectoryListener$DirectoryPollingItem.execute(DirectoryListener.java:381)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.fengine.service.FEngineExecution.executeImmediate(FEngineExecution.java:65)
     at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
     at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
     at fuego.server.execution.PollingDirectory.execute(PollingDirectory.java:46)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251)
     at fuego.server.execution.ToDoItem.run(ToDoItem.java:536)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:775)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
     at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
     at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
     at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
     at albpm.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
     at albpm.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
     at albpm.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
     at albpm.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
     at albpm.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
     at albpm.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source)
     at albpm.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
     at albpm.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source)
     at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
     at albpm.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
     at albpm.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
     at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
     at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createParticipantInfo(JDBCParticipantsAccessor.java:1280)
     at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipantInternal(JDBCParticipantsAccessor.java:1195)
     at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:217)
     ... 49 more

Hi All ,
I having this error . Are there any fixes for this bug ?
my configuration file is like the following ;
+<?xml version="1.0" encodxxx="UTF-8"?>+
+<?fuego version="6.1 ALPHA" application="albpmenterprise"?>+
+
+<config>+
+     <object id="person">+
+          <object-filter>+
+               <![CDATA[+
+                    (objectclass=person)+
+               ]]>+
+          </object-filter>+
+          <relative-dn>ou=xxxBANK,cn=Users</relative-dn>+
+          <attribute id="id" value="uid"/>+
+          <attribute id="lastName" value="sn"/>+
+          <attribute id="firstName" value="givenname"/>+
+          <attribute id="displayName" value="displayname"/>+
+          <attribute id="mail" value="mail"/>+
+          <attribute id="telephoneNumber" value="telephonenumber"/>+
+          <attribute id="employeeId" value="employeeNumber"/>+
+          <attribute id="thumbnailPhoto" value="thumbnailPhoto"/>+
+          <attribute id="manager" value="manager"/>+
+          <attribute id="modifyTimeStamp" value="modifyTimestamp"/>+
+     </object>+
+     <object id="group">+
+          <object-filter>+
+               <![CDATA[+
+                    (objectclass=xxxGroupObject)+
+               ]]>+
+          </object-filter>+
+          <relative-dn>+
+               </relative-dn>+
+          <attribute id="id" value="cn"/>+
+          <attribute id="modifyTimeStamp" value="modifyTimestamp"/>+
+          <attribute id="displayName" value="cn"/>+
+          <attribute id="name" value="cn"/>+
+          <attribute id="description" value="description"/>+
+          <attribute id="assignedParticipants" value="uniquemember"/>+
+          <attribute id="assignedGroups" value="uniquemember"/>+
+          <attribute id="ou" value="distxxxuishedName"/>+
+     </object>+
+     <object id="ou">+
+          <object-filter>+
+               <![CDATA[+
+                    (objectclass=xxxOUObject)+
+               ]]>+
+          </object-filter>+
+          <relative-dn>+
+               +
+          </relative-dn>+
+          <attribute id="name" value="ou"/>+
+          <attribute id="description" value="description"/>+
+     </object>+
+</config>+

WebLogic 10.3.2.0 hanging at startup after "The server log file is opened."

Hi,
A WebLogic 10.3.2.0 server is hanging at startup. There are no error messages. The last command in the startup window is:
"The server log file <log file dest> is opened. All server side log events will be written to this file."
I think the next line should be:
"Security initializing using security realm realm."
Any ideas on what could be the issue? For instance what resources should be accessed at that point of time? There is sufficient space left on the (virtual machine) disk. The VM configured with 8GB memory. Could it be performance related still?
Following is written to the log file:
####<12.aug.2010 kl 09.47 CEST> <Info> <WebLogicServer> <oim> <> <Main Thread> <> <> <> <1281599254656> <BEA-000214> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.> ####<12.aug.2010 kl 09.47 CEST> <Notice> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255312> <BEA-170019> <The server log file ....logs\AdminServer.log is opened. All server side log events will be written to this file.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255390> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Diagnostics> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599255671> <BEA-320001> <The ServerDebug service initialized successfully.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Store> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599256515> <BEA-280050> <Persistent store "WLS_DIAGNOSTICS" opened: directory="....s\domains\oim\servers\AdminServer\data\store\diagnostics" writePolicy="Disabled" blockSize=512 directIO=false driver="wlfileio2"> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3s" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "http" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "https" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "iiop" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "iiops" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldap" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldaps" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "cluster" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "clusters" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "snmp" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "admin" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002624> <The administration protocol is "t3s" and is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <RJVM> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257468> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address          :7001
Public Address          N/A
Http Enabled          true
Tunneling Enabled     false
Outbound Enabled     false
Admin Traffic Enabled     true>
####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257687> <BEA-002609> <Channel Service initialized.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258000> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000436> <Allocating 3 reader threads.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000446> <Native IO Enabled.> ####<12.aug.2010 kl 09.47 CEST> <Info> <IIOP> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599259500> <BEA-002014> <IIOP subsystem enabled.>
Thanks!!

tried both of these, still having same error as below:
<Sep 8, 2010 1:32:37 PM IST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Sep 8, 2010 1:32:37 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic2 javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic2 denied
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:250)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 8, 2010 1:32:37 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Pls help me out ASAP...

MR11 log file

Hi,
While run MR11 for GR/IR clearing account a log file is generated and document number is 5400000010. Where this log file is stored by default and how it should display ? Beside F.13 automatic clearing clears those GR/IR records whose balance shows as 0. And difference amount is cleared through F-03 by choosing document number from GR and IR under same purchase order. In F.13(automatic clearing) does not clear those same GR value and IR value inspite of same PO number. These values are easily tracebale from normal balance viewing mode through FBL3N. Why these values are not cleared through F.13 ?
Regards,
Samrat

Immediate AI:
0. Check the log file auto growth setup too and check is this a practically a good one and disk has still space or not.
1. If disk is full where you are keeping log file, then add a log file in database property page on another disk where you have planned to keep log files, in case you can't afford to get db down. Once you are done then you can plan to truncate data out of
log file and remove that if it has come just first time issues. If this happens now and then check for capacity part.
2. You can consider shrinking the log files after no any other backup are going on or any maintenance job like rebuild\reorg indexes \update stats jobs are executing as this will be blocking it.
If db size is small and copy files from prod to dr is not that latency prone, and shrink is not happening, then you can try changing recovery model and then do shrinking and reconfigure log-shipping after reverting recovery model.
3. Even you can check if anyone mistakenly places some old files and forgot to remove them which is causing disk full issues. Also
4. For permanent solution, do monitor the environment for capacity and allocate good space for log file disks. Also consider tweaking frequencies of the log backup from default that suits your environment.
Santosh Singh

Server shutdown with the following log file -?

JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=128m
WLS Start Mode=Production
CLASSPATH=:/home3/bea9/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home3/bea9/jdk150_07/lib/tools.jar:/home3/bea9/weblogic92/server/lib/weblogic_sp.jar:/home3/bea9/weblogic92/server/lib/weblogic.jar:/home3/bea9/weblogic92/server/lib/webservices.jar::/home3/bea9/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/home3/bea9/weblogic92/server/lib/xqrl.jar::
PATH=/home3/bea9/weblogic92/server/bin:/home3/bea9/jdk150_07/jre/bin:/home3/bea9/jdk150_07/bin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/opt/nettladm/bin:/opt/fc/bin:/opt/fcms/bin:/opt/upgrade/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/hparray/bin:/opt/langtools/bin:/opt/imake/bin:/opt/perf/bin:/opt/ignite/bin:/opt/OV/bin/OpC:/opt/hpnp//bin:/opt/resmon/bin:/usr/sbin/diag/contrib:/opt/pred/bin:/opt/sec_mgmt/spc/bin:/opt/graphics/common/bin:/opt/OV/bin:/opt/ssh/bin:/opt/sec_mgmt/bastille/bin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.5.0.07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.07-_20_mar_2007_05_31)
Java HotSpot(TM) Server VM (build 1.5.0.07 jinteg:03.20.07-04:39 PA2.0 (aCC_AP), mixed mode)
Starting WLS with line:
/home3/bea9/jdk150_07/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -da -Dplatform.home=/home3/bea9/weblogic92 -Dwls.home=/home3/bea9/weblogic92/server -Dwli.home=/home3/bea9/weblogic92/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home3/bea9/patch_weblogic922/profiles/default/sysext_manifest_classpath -Dweblogic.Name=Admin -Djava.security.policy=/home3/bea9/weblogic92/server/lib/weblogic.policy weblogic.Server
<May 13, 2009 10:36:22 AM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/home3/bea9/weblogic92/platform/lib/p13n/p13n-schemas.jar:/home3/bea9/weblogic92/platform/lib/p13n/p13n_common.jar:/home3/bea9/weblogic92/platform/lib/p13n/p13n_system.jar:/home3/bea9/weblogic92/platform/lib/wlp/netuix_common.jar:/home3/bea9/weblogic92/platform/lib/wlp/netuix_schemas.jar:/home3/bea9/weblogic92/platform/lib/wlp/netuix_system.jar:/home3/bea9/weblogic92/platform/lib/wlp/wsrp-common.jar>
<May 13, 2009 10:36:24 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0.07 jinteg:03.20.07-04:39 PA2.0 (aCC_AP) from Hewlett-Packard Company>
<May 13, 2009 10:36:29 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP2 Mon Jun 25 01:32:01 EDT 2007 952826 >
<May 13, 2009 10:37:03 AM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /home3/bea9/license.bea>
<May 13, 2009 10:37:03 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<May 13, 2009 10:37:03 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<May 13, 2009 10:37:04 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /home3/bea9/user_projects/domains/Production/servers/Admin/logs/Admin.log is opened. All server side log events will be written to this file.>
<May 13, 2009 10:37:08 AM EDT> <Alert> <Socket> <BEA-000414> <Could not initialize POSIX Performance Pack.>
<May 13, 2009 10:37:08 AM EDT> <Warning> <Socket> <BEA-000444> <Could not load the performance pack that can take advantage of /dev/(e)poll device due to:
     weblogic.utils.NestedError: Could not initialize /dev/poll Performance Pack. Ensure that /dev/poll device exists and is initialized..
Will attempt to use the performance pack that does not depend on /dev/(e)poll device.>
<May 13, 2009 10:37:18 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<May 13, 2009 10:37:35 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<May 13, 2009 10:37:35 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<May 13, 2009 10:37:52 AM EDT> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
<May 13, 2009 10:37:53 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<May 13, 2009 10:37:53 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<May 13, 2009 10:37:54 AM EDT> <Warning> <Server> <BEA-002611> <Hostname "ncsci015", maps to multiple IP addresses: 10.45.8.61, 127.0.0.1>
<May 13, 2009 10:37:54 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:9001 for protocols iiop, t3, ldap, http.>
<May 13, 2009 10:37:54 AM EDT> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 10.45.8.61, 127.0.0.1>
<May 13, 2009 10:37:54 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.45.8.61:9001 for protocols iiop, t3, ldap, http.>
<May 13, 2009 10:37:54 AM EDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "Admin" for domain "Production" running in Production Mode>
<May 13, 2009 10:37:54 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<May 13, 2009 10:37:54 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<May 13, 2009 10:39:55 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 13, 2009 10:43:47 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
<May 13, 2009 10:44:08 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Dtcr%2CType%3DAppDeployment%22%29.>
<May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 13, 2009 12:34:44 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 13, 2009 12:43:36 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 13, 2009 1:12:29 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 14, 2009 12:27:16 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 14, 2009 12:27:29 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
<May 14, 2009 12:29:21 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 14, 2009 12:29:30 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
<May 14, 2009 12:29:44 PM EDT> <Error> <netuix> <BEA-423405> <An exception [Broken pipe (errno:32)] was thrown while rendering the content at [jsp/contentheader/ContentMenu.jsp].
java.net.SocketException: Broken pipe (errno:32)
     at java.net.SocketOutputStream.socketWrite0(Native Method)
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:97)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:141)
     at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:525)
     at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:504)
     Truncated. see log file for complete stacktrace
>
<May 14, 2009 1:47:36 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 14, 2009 1:47:48 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
<May 14, 2009 1:57:17 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 14, 2009 1:57:27 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
<May 15, 2009 9:15:48 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 15, 2009 12:07:05 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 15, 2009 12:07:14 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Dtcr%2CType%3DAppDeployment%22%29.>
<May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
<May 19, 2009 2:29:26 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
<May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<May 31, 2009 10:27:32 PM EDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<May 31, 2009 10:27:32 PM EDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 10.45.8.61:9001 was shutdown.>
<May 31, 2009 10:27:32 PM EDT> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on 127.0.0.1:9001 was shutdown.>
The server shutdown with the above output in the log file, can you please let me know why this happened and any solution for it?
Thanks.

Have you see that in your posted log:
<May 13, 2009 10:37:08 AM EDT> <Alert> <Socket> <BEA-000414> <Could not initialize POSIX Performance Pack.>
<May 13, 2009 10:37:08 AM EDT> <Warning> <Socket> <BEA-000444> <Could not load the performance pack that can take advantage of /dev/(e)poll device due to:
weblogic.utils.NestedError: Could not initialize /dev/poll Performance Pack. Ensure that /dev/poll device exists and is initialized
Will attempt to use the performance pack that does not depend on /dev/(e)poll device.>
it seems to be a trouble with server performance pack. Try to DISABLE performance pack on your server and restart (unckeck "Native IO Enabled" on your domain"). You can also found some suggestions on http://edocs.bea.com/wls/docs92/messages/Socket.html (check for "BEA-000414" message).
Regards
Nat.

Log Reader Agent: transaction log file scan and failure to construct a replicated command

I encountered the following error message related to Log Reader job generated as part of transactional replication setup on publisher. As a result of this error, none of the transactions propagated from publisher to any of its subscribers.
Error Message
2008-02-12 13:06:57.765 Status: 4, code: 22043, text: 'The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately 24500000 log records have been scanned in pass # 1, 68847 of which were marked for replication, elapsed time 66018 (ms).'.
2008-02-12 13:06:57.843 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on ServerName.'.
2008-02-12 13:06:57.843 Status: 0, code: 18805, text: 'The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {00065e22:0002e3d0:0006}. Back up the publication database and contact Customer Support Services.'.
2008-02-12 13:06:57.843 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'ServerName'.'.
Replication agent job kept trying after specified intervals and kept failing with that message.
Investigation
I could clearly see there were transactions waiting to be delilvered to subscribers from the followings:
SELECT * FROM dbo.MSrepl_transactions -- 1162
SELECT * FROM dbo.MSrepl_commands -- 821922
The following steps were taken to further investigate the problem. They further confirmed how transactions were in queue waiting to be delivered to distribution database
-- Returns the commands for transactions marked for replication
EXEC sp_replcmds
-- Returns a result set of all the transactions in the publication database transaction log that are marked for replication but have not been marked as distributed.
EXEC sp_repltrans
-- Returns the commands for transactions marked for replication in readable format
EXEC sp_replshowcmds
Resolution
Taking a backup as suggested in message wouldn't resolve the issue. None of the commands retrieved from sp_browserreplcmds with mentioned LSN in message had no syntactic problems either.
exec sp_browsereplcmds @xact_seqno_start = '0x00065e220002e3d00006'
In a desperate attempt to resolve the problem, I decided to drop all subscriptions. To my surprise Log Reader kept failing with same error again. I thought having no subscription for publications log reader agent would have no reason to scan publisher's transaction log. But obviously I was wrong. Even adding new log reader using sp_addLogreader_agent after deleting the old one would not be any help. Restart of server couldn't do much good either.
EXEC sp_addlogreader_agent
@job_login = 'LoginName',
@job_password = 'Password',
@publisher_security_mode = 1;
When nothing else worked for me, I decided to give it a try to the following procedures reserved for troubleshooting replication
--Updates the record that identifies the last distributed transaction of the server
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
-- Flushes the article cache
EXEC sp_replflush
Bingo !
Log reader agent managed to start successfully this time. I wish if I could have used both commands before I decided to drop subscriptions. It would have saved me considerable effort and time spent re-doing subscriptions.
Question
Even though I managed to resolve the error and have replication funtioning again but I think there might have been some better solution and I would appreciate if you could provide me some feedback and propose your approach to resolve the problem.

Hi Hilary,
Will the below truncate the log file marked for replication, is there any data loss, when we execute this command, can you please help me understand, the internal working of this command.
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1

Warning Capture in Log file using SSIS 2008

While doing insert from datasource1 (flat file/ xml source) to datasource2(Oledb) , some data is getting truncated . The User want to capture the log in some log file.
The field which got truncated along with the row details
and number of truncation which has occured.
I observe in flat file source we Redirect Row for Error and Truncation, but how to capture which row got truncated
and what value got truncated.
and it need to written in notepad/txt file

The User wan't to insert length of specific character and discard the rest. I think redirect rows transfer the failed row so we won't have records inserted into the target db.
could you please suggest how to achieve the requirement.

Growing nsure audit log file in sys\etc\logcache

I have a Netware 6.5 OES2 server that suddenly had a quickly growing file in the \sys\etc\logcache folder. The file has just recently stabilized, but I would like to shrink the file. I am aware that this is part of NSure auditing and would like to leave that running. Can the files in this directory be deleted, or how to I go about shrinking or truncating them?
Thanks.

That would be OES, as OES2 only exists on Linux.
TID 10089097 seems to cover this in a general sense:
configuring the PA on NetWare, is to configure the eDirectory, Filesystem, and Netware OS instrumentation. This is done at the NCP server object in iManager. From the eDirectory Administration task list, select Modify Object. Browse for server object. This is the NCP server object, in the tree, not the Secure Logging Server object in the Logging Services container. Click on the Nsure Audit tab. Below the tab, there will links to the individual components, eDirectory, NetWare, and Filesystem.
Without having it installed myself, I would expect that you could reset log files and suchlike in there.

Truncating log files

Similar Messages

Maybe you are looking for