Sanitizing the CE5xx transaction logs

We are currently producing the squid (extended) transaction logs on the content engines with the sanitize feature disabled. I do not want to change the configuration on the CE, as the information in the logs is being used for reporting purposes.
Is there any after market software that will strip the IP information and userid's from the logs?

Did you ever find anything? If you do, post it here. I would love to look at such a product as well.

Similar Messages

How does one read the Unity transaction logs on Exchange?

I'm trying to find out who placed a call to whom on a particular day and time. A subscriber receives a blank email periodically with no "from" statement, just a timestamp. They don't have unified messaging. I want to see if the transaction logs (located on Exchange) contain that information but they are all cryptic symbols. Is there an application or utility to read tham? These are the files located in the \Exchsrvr\MDBDATA folder. This is Unity 5.x and Excahnge 2003. Thanks.

Hi,
I think you may be wanting to look at Message Tracking?
http://www.msexchange.org/tutorials/Exchange-2003-Message-Tracking-Logging.html
But here's also an explanation of the transaction logging and how to read them from the same site:
http://www.msexchange.org/articles/Transaction-Logs-Lifeblood-Exchange.html
Hope that helps,
Brad

What is the current schedule for 6.1.2 and will it fix the Exchange transaction log issue in 6.1?

Just spent the entire night with virtually no sleep with our firm's group of IT engineers trying to keep our Exchange system online due to massive transaction log growth. Confirmed the issue related to 6.1 calendar bug with Activesync. The workarounds are not practical for large groups of users who depend on their mobile devices for work. Our users have no way of knowing that they are causing an issue so the Apple guidance isnt terribly useful to communicate to 1000 users. When can we expect a resolution? The problem is only going to get worse as more and more users hit the bug. Does anyone know if the issue will resolve as soon as someone installs the 6.1.2 update, assuming that has the fix. Im not trying to bash anyone but this is a very serious problem in enterprise deployments.

The update was released some time today. 6.1.2 appears to specifically fix the Exchange issue causing excess comms and logging issues. However, although the update is available i do not see the notification badge on the Settings icon. Is this controlled by Apple or is there a user setting i am missing somewhere? I would prefer that all users see the badge to expedite user action.

Oracle DB equivalent of SQL Server's Simple Transaction Logging mode?

G'Day Experts !
Was wondering if Oracle DB has the functional equivalent of the 'simple' transaction logging available in SQL Server?
Would this be availabe at the schema level, or would it have to be the entire instance?
I'm asking because the WebCenter Interaction portal and related services has no practical use for point-in-time rollbacks. The portal uses discreet event boundaries which unfortunately do not map into the relational world.
Thanks!
Rob in Vermont

Plumtree wrote:
G'Day Experts !
Was wondering if Oracle DB has the functional equivalent of the 'simple' transaction logging available in SQL Server?
Would this be availabe at the schema level, or would it have to be the entire instance?
I'm asking because the WebCenter Interaction portal and related services has no practical use for point-in-time rollbacks. The portal uses discreet event boundaries which unfortunately do not map into the relational world.
Thanks!
Rob in VermontHi Rob
I assume you are referring to the simple recovery model, i.e lose everything since last backup. Oracle's equivalent of that is to run a database in NOARCHIVELOG mode. It applies to the database rather than the instance, though you probably intended database when you said instance.
Niall Litchfield
http://www.orawin.info/

WAE 512 and transaction logs problem

Hi guys,
I have a WAE 512 with ACNS 5.5.1b7 and I'm not able to export archived logs correctly. I tried to configure the WAE as below:
transaction-logs enable
transaction-logs archive interval every-day at 23:00
transaction-logs export enable
transaction-logs export interval every-day at 23:30
transaction-logs export ftp-server 10.253.8.125 cache **** .
and the WAE exported only one file of about 9 MB even if the files was stored on the WAE as you can see from the output:
Transaction log configuration:
Logging is enabled.
End user identity is visible.
File markers are disabled.
Archive interval: every-day at 23:00 local time
Maximum size of archive file: 2000000 KB
Log File format is squid.
Windows domain is not logged with the authenticated username
Exporting files to ftp servers is enabled.
File compression is disabled.
Export interval: every-day at 23:30 local time
server type username directory
10.253.8.125 ftp cache .
HTTP Caching Proxy logging to remote syslog host is disabled.
Remote syslog host is not configured.
Facility is the default "*" which is "user".
Log HTTP request authentication failures with auth server to remote syslog host.
HTTP Caching Proxy Transaction Log File Info
Working Log file - size : 96677381
age: 44278
Archive Log file - celog_213.175.3.19_20070420_210000.txt size: 125899771
Archive Log file - celog_213.175.3.19_20070422_210000.txt size: 298115568
Archive Log file - celog_213.175.3.19_20070421_210000.txt size: 111721404
I made a test and I configured the archiveng every hour from 12:00 to 15:00 and the export at 15:10, the file trasnferred by the WAE was only three one of 12:00 the other of 13:00 and 14:00 the 15:00 has been missed.
What can I do?
Thx
davide

Hi Davide,
You seem to be missing the path on the FTP server; which goes on the export command.
Disable transaction logs, then remove the export command and then add it again like this: transaction-logs export ftp-server 10.253.8.125 cache **** / ; after that enable transaction logs again and test it.
Let me know how it goes. Thanks!
Jose Quesada.

Question. usage of transaction log

Hello,
our BI-Database (db2 v.9.5) is 3 TB big. log_dir 20GB
1) What would be your suggestions regarding size of log:dir to prevent the error transaction log is full.
2) How can I monitor the usage of the transaction log? We would like to set up a monitoring to send out an alarm, when the usage reaches 90%. A database select or can I find the information in db2diag.log?
Regards,
Alexander

Hi Alexander,
in addition to the script Joachim provided, the following gives a SQL based solution to find about Log Space usage
db2 "SELECT TOTAL_LOG_AVAILABLE AS LOG_AVAILABLE,TOTAL_LOG_USED as LOG_USED, APPL_ID_OLDEST_XACT as OLDEST_APPL_ID from SYSIBMADM.SNAPDB"
Yo can find more interesting values on the snapdb admin view here:
DB2 9.5 Information Center
Gruss,
Hans-Jürgen
Edited by: Hans-Juergen Moldowan on Jan 19, 2009 5:07 PM

Transaction Logs in SQL Server

Hi, the BW system has the following properties:
BW 3.1C Patch 14
BASIS/ABA 6.20 Patch 38
BI_CONT 310 Patch 2
PI_BASIS Patch 2004_1_620
Windows 2000 Service Pack 4
SQL Server 2000 SP3 version 8.00.760
Database used space: 52 GB
Database free space: 8.9 GB
Transaction log space: 8 GB
I am having the following problem. The SQL transaction logs on the SQL Server fill up very rapidly while aggregates are rolling up. Sometimes taking up to 16-20 GB of transaction log space in the SQL Server. We only have 8 GB of space available for the transaction logs. When the aggregates are not rolling up, the logs do not fill up at all. I have tried changing the logs to Simple logging, but all that does is delay the fill, and at that point you cannot backup simple logs to free up DB space.
What is it about aggregates that fills up the transaction log? Anybody know a solution to this without adding disk space to the transaction log disk?
Thanks,

Hello,
the log backup on simple mode is not necessary. The full database after switching back to full is a must.
Please keep in mind, that even running on simple mode the log can be filled up, as all transactions are still written to the log. Commited transaction then can truncated from the log. But when you run a hugh transaction like a client copy, the log might grow as well. The log will be freed once the transaction commits or rolls back. And no, you can't split a client copy in several transactions.
Best regards
Clas

Very high transaction log file growth

Hello
Running Exchange 2010 sp2 in a two node DAG configuration. Just recently i have noticed a very high transaction log file growth for one database. The transaction logs are growing so quickly that i have had to turn on circular logging in order to prevent
the log lun from filling up and causing the database to dismount. I have tried several things to try find out what is causing this issue. At first i thought this could be happening because of virus, an Active Sync user, a users outlook client, or our salesforce
integration, howerver when i used exmon, i could not see any unusual high user activity, also when i looked at the itemcount for all mailboxes in the particular database that is experiencing the high transaction log file growth, i could not see any mailboxes
with unusual high item count, below is the command i ran to determine this, i ran this command sever times. I also looked at the message tracking log files, and again could see no indication of a message loop or unusual high message traffic for a
particlar day. I also followed this guide hopping that it would allow me to see inside the transaction log files, but it didnt produce anything that would help me understand the cause of this issue. When i ran the below tool againts the transaction log files,
i saw DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD, or OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO, or HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH.
I am starting to run out of ideas on how to figure out what is causing the log file build up. Any help is greatly appreciated.
http://blogs.msdn.com/b/scottos/archive/2007/07/12/rough-and-tough-guide-to-identifying-patterns-in-ese-transaction-log-files.aspx
Get-Mailbox -database databasethatkeepsgrowing | Get-MailboxStatistics | Sort-Object ItemCount -descending |Select-Object DisplayName,ItemCount,@{name="MailboxSize";exp={$_.totalitemsize}} -first 10 | Convertto-Html | out-File c:\temp\report.htm
Bulls on Parade

If you have users with iPhones or Smart Phones using ActiveSync then one of the quickest ways to see if this is the issue is to have users shot those phones off to see if the problem is resolved. If it is one or more iPhones then perhaps look at
what IOS they are on and get them to update to the latest version or adjust the ActiveSync connection timeout. NOTE: There was an issue where iPhones caused runaway transactions logs and I believe it was resolved with IOS 4.0.1
There was also a problem with the MS CRM client awhile back so if you are using that check out this link.
http://social.microsoft.com/Forums/en/crm/thread/6fba6c7f-c514-4e4e-8a2d-7e754b647014
I would also deploy some tracking methods to see if you can hone in on the culprits, i.e. If you want to see if the problem is coming from an internal Device/Machine you can use one of the following
MS USER MONITOR:
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=9A49C22E-E0C7-4B7C-ACEF-729D48AF7BC9&displaylang=en and here is a link on how to use it
http://www.msexchange.org/tutorials/Microsoft-Exchange-Server-User-Monitor.html
And this is a great article as well
http://blogs.msdn.com/b/scottos/archive/2007/07/12/rough-and-tough-guide-to-identifying-patterns-in-ese-transaction-log-files.aspx
Also check out ExMon since you can use it to confirm which mailbox is unusually active , and then take the appropriate action.
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=9A49C22E-E0C7-4B7C-ACEF-729D48AF7BC9&displaylang=en
Troy Werelius
www.Lucid8.com
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

Log Reader Agent is not able to read Transaction Log of Publisher database.

Hi,
There is no restore or change in recovery model or detach-attach action performed on my production database but still I am seeing below error message from Log Reader Agent-
Error messages:
The process could not execute 'sp_repldone/sp_replcounters' on 'ProdInstance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help:
An error occurred while processing the log for database 'MyDatabase'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. (Source: MSSQLServer, Error number: 9004)
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: The process could not execute 'sp_repldone/sp_replcounters' on 'ProdInstance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Note- CheckDB on production and distribution database executed successfully. Also, I need subscriber to be a true copy of publisher so I think sp_replrestart is not an option for me.
My question is how to resolve this issue? I am thinking that reinitialization should resolve the problem but what if this is not going to resolve? Do I need to reconfigure the transaction replication? Please sugegst.

Hi,
Please check out this link on how to resolve “The process could not execute 'sp_repldone/sp_replcounters'” error.
http://blogs.msdn.com/b/repltalk/archive/2010/02/19/the-process-could-not-execute-sp-repldone-sp-replcounters.aspx
The possible cause could be:
1.The last LSN in Transaction Log is less than what the LSN Log Reader is trying to find. An old backup may have been restored on top of Published Database. After the restore, the new Transaction Log doesn't contain the data now distributor & subscriber(s)
have.
2.Database corruption.
Since you have not restored the published database, I suggest you run
DBCC CHECKDB to confirm the consistency of the database. Refer to the How to fix in the above link.
Thanks.
Tracy Cai
TechNet Community Support

Client Deletion, Transaction log getting full.

Hi Gurus,
We are trying to delete a client by running:
clientremove
client = 200 (*200 being the client we want to remove)
select *
The transaction log disk space allocated is 50GB, it is getting full (in simple mode) and client deletion never completes. The size of the table it is accessing is 86 GB, and i think 200 client will be occupying around 40-45GB. Client 200 has 15.5 million rows in the table.
I am i giving proper command ?is there any explicit commit i can include or any workaround for deleting the client and not hammer the log file.
Thanks guys
Edited by: SAP_SQLDBA on Jan 22, 2010 6:51 PM

Hi,
Backup the active transaction log file and Shrink the file directly.
Please refer the following SAP Notes to get more information.
[ Note 625546 - Size of transaction log file is too big|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=625546]
[ Note 421644 - SQL error 9002: The transaction log is full|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=421644]
Which version of SQL Server u are using ? SP Level ?
Frequently perform Transaction Log backup (BACKUP TRANS) to remove inactive space within the Transaction Log Files.
Please refer [Note 307911 - Transaction Log Filling Up in SQL Server 7.0|https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=307911] to get more information about the reasons for such kind of situation.
Regards,
Bhavik G. Shroff

About transaction logs

Can you tell me about transaction log space? how does it gets full? How is it related to performance?

Hi,
Monitoring the SAP Log Disk
Use
The size of the transaction log must be checked regularly to work out how much free space is available on the log disk. There should always be enough free space to allow the next file extension. When the SAP system has been installed the autogrow increment is set. At least the size of this increment should be available on the log disk to permit the next file extension. If less space is available and the transaction log file fills up, the SAP system will come to a standstill.
Ideally, the transaction log should never be filled to more than 60-70%. If the transaction log regularly exceeds this level between 2 transaction log backups, the transaction log must be saved at more frequent time intervals.
The size of the log can be assessed on the basis of information given for completed backups in the SAP transaction for Backup and Restore Information.
Procedure:
       1.      To access the transaction for Backup Restore Information choose CCMS ® DB Administration ® Backup logs.
Alternatively, enter the transaction code DB12.
The initial screen of the monitor CCMS Monitoring Tool u2013 DB12 (Backup Restore Information) appears.
       2.      Choose Backup history and then Logs Backup.
       3.      A result list appears. Find the largest transaction log backup of the past week. Select a row and then History info to find out the number of pages that were processed during the backup. To work out the amount of space used in the transaction log, multiply the number of dumped pages by 8 KB. You can then work out how much free space is left on the transaction log disk.
If you use a RAID1 disk system exclusively for the SAP transaction log and create hourly log backups, you will rarely encounter space problems. The SAP log file is initially created with a size of 1 GB. The smallest disk normally has 9 GB space and the log file can therefore grow to 9 GB.
Hope it Helps
Srini

Oracle dump transaction log like Sybase

Hello
In Sybase we use the dump transaction log command for the needed databases that dumps whatever is in the transaction log of that db to file system, after that dump file is copied over to another database server and loads the other database, this is like a replication
Does oracle have something similar to this?
Many thanks

the closest you'll get to what you are looking for is a dataguard setup. Dataguard will manage the shipment of the logs on it's own and keep things in sync.
There is another option of Oracle Advanced Replication but you will need to review if that really meets your needs. The following is simply an overview of it:
http://www.orafaq.com/wiki/Advanced_Replication_FAQ
Or GoldenGate:
http://www.oracle.com/technetwork/middleware/goldengate/overview/index.html
Edited by: rui_catcuddler on Oct 20, 2010 7:54 AM

Replay transaction logs to a new empty mailbox database

My Exchange 2010 mailbox database got corrupted and do not really have a good backup to recover from and it is not a DAG too.
Using eseutil log files are good but if I do soft recovery, it complains of a missing log file. Going through the log files it is just one file that is missing and even checking the creation date for this file at that time the server was offline because
we were relocating.
Soft recovery has not been successful.
I want to try hard recovery but do not know how much data will be lost. Or better still is there a way to replay log files of the corrupted database into the new database and continue from there?

Without having a good backup, you can not ensure about the security of data that would be recovered.
If you have an old backup of the database and all transaction log files since that backup then you can restore everything up to the last transaction log file.
If you want to do it in the RSG then you can copy all transaction log files from the production storage group to the log file directory of the RSG, then restore you last backup and let the backup program mount the database. Exchange will automatically replay
the log files in the RSG directory and the files on the tape. Please follow this Library : http://technet.microsoft.com/en-us/library/aa998370(EXCHG.65).aspx
If you still unable to recover the data manually, you may consider on this automated software (http://www.exchangeserverrecovery.com/) that might be helpful to recover the data without any losses and resolve
your purpose.

Update deactivated when DB2 transaction logs fill.

Hi All,
We are running SAP on DB2 Version9 on AIX platform.
We notirced that when transaction logs get full, the Update workprocess gets deactivated. This happens in any usage type that we have.. SRM, ECC , BI.
In the workprocess log we find this
C &+     ABAP location info 'SAPLSNR3', 2480
C &+     SAP user 'P1245690', transaction code 'WRF_WSOA2'
C &+
C *** ERROR in DB6Execute[dbdb6.c, 4556] (END)
B ***LOG BYL=> DBQ action required because of database error            [dbsh#2 @ 1100] [dbsh    1100 ]
B SQL code: -964, SQL text: SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1
M ThIVBChangeState: update deactivated
M ***LOG R0R=> ThIVBChangeState, update deactivated () [thxxvb.c     11442]
M
M Sun Aug 8 08:30:44 2010
M *** ERROR => ThVBCheckCommit: reject bad ROLLBACK [thxxvb.c     13471]
A
A Sun Aug 8 08:57:56 2010
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
I have never heard of Update being deactivated for transaction log full at DB level. Update can be held up butwill it get deactivated.
Is it possible that update gets deactivated if it not able to post the tranaction data in DB?
Please let me know your ideas on this and how we can prevent this update from deactivating.
Thanks and REgards,
Raghavan

Hi,
If you search for "SQL0964C The transaction log for the database is full" then some of solutions ask for to execute the below mentioned steps :-
Use the following procedure to increase the size of the DB2 transaction log (logfilsiz):
1. Determine the current log file size setting by issuing the command:
su - <db2instance>
db2 list db directory # to list the database name
db2 connect to <databaseName>
db2 get db config for <databaseName> and check LOGFILSIZ parameter.
A sample output given from my test system :-
Log file size (4KB)                         (LOGFILSIZ) = 16380
Number of primary log files                (LOGPRIMARY) = 20
Number of secondary log files               (LOGSECOND) = 40
Changed path to log files                  (NEWLOGPATH) =
Path to log files                                       = /db2/<dataname>/log_dir/NODE0000/
Overflow log path                     (OVERFLOWLOGPATH) =
Mirror log path                         (MIRRORLOGPATH) =
First active log file                                   =
Block log on disk full                (BLK_LOG_DSK_FUL) = YES
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
2. Increase the size of the log file size setting by issuing the command:
db2 UPDATE db cfg for <databaseName> using LOGFILSIZ <new_value>
Example:
db2 UPDATE db cfg for <databaseName> using LOGFILSIZ 5000
3. Stop the ibmslapd process.
4. Issue the commands:
db2 force applications all
db2stop force
5. Restart ibmslapd process.
Once the db issue is resolved then your update work process must be running fine.

Cleaning up transaction logs on a CE507/560

Hi,
We are exporting the CE transaction logs to an FTP server.
Is there any function on the CE that will delete any transaction log that has been FTP'ed off of the box?
Thx.

HI,
I could not copy the archived transaction logs to the ftp server, here is the message i received every time:
Jun 08, 2004 12:45:29 Session 25, Peer xx.xx.xx.xx 550 temp : No such file or directory.
i cannot specify the directory to which the transaction logs are copied.
Can you give me a detailed example explaining how to define the ftp directory. i'm using 3cdaemon ftp server.
Regards

Sanitizing the CE5xx transaction logs

Similar Messages

Maybe you are looking for