Cube compression filling up the system logs

Hi,
I reloaded the inventory cube with 2LIS_03_BF (init with data transfer) with 46million records (in a single request). When I try to compress the request without the marker update BX has already been compressed with the marker update) , the system logs are getting filled up and the production system is freezing up.
Is there any solution that makes the compression job take lesser time and generate less logs? At this time, we are not looking in to dropping the data and reloading in smaller chunks, cos that will take another 2days to reload the 46mil records.
Thanks for any suggestions,
Ajax.

Hi Ajax,
We had a similar issue early last yr. Compression uses a lot of temp spaces and fills up the logs . You can ask your basis team to help you by increasing the MAX_LOGS parameter temporarily to complete your compression. As a last resort you can also ask them to involve secondary logs or setting the logs to "unlimited" value and rerun the compression job .However pls note that this is limited by the filesystem size.
Hope it helps .
Thnks
Ram

Similar Messages

Application messages are in the system log instead of the application log

Hi SAP GURUS.
The standard output is created from the outbound delivery .
All the messages are hitting the system log instead of the application log .
This is after the upgrade from 4.6c to ECC 6.0 .
Please provide the details how to move the log to the application log since the output is the standard output (SAP provided output type ).

verzunof wrote:
Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.
verzunof wrote:
I'm not certain if those messages indicate a power issue but you can try *resetting the System Management Controller* and see if that helps. Here's how: http://support.apple.com/kb/HT1806
"The System Management Controller (SMC) is a chip on the logic board that controls all power functions for your computer. If your computer is experiencing any power issue, resetting the SMC may resolve it. The SMC controls several functions, including:
Telling the computer when to turn on, turn off, sleep, wake, idle, and so forth.
Handling system resets from various commands.
Controlling the fans."
Carolyn

Mdworker saturating the system.log file

Hi,
i have a problem on my late 2010 MBA, running 10.6.8. Frequently, the fan goes frantic, and it appears it is linked to mdworker running over and over again. It seems to be doing that when the vpn from the company is running (Juniper through Secure App Manager).
I checked the system.log file and it is 2.63Go for the past 5 days! Mostly filled with
Jan 3 08:45:39 Puss mdworker[59604]: socket(PF_ROUTE) failed: Operation not permitted
Jan 3 08:45:39 Puss sandboxd[59747]: mdworker(59604) deny system-socket
Jan 3 08:45:39 Puss sandboxd[59747]: mdworker(59604) deny network-outbound /private/var/run/mDNSResponder
(repeated 500 times and over, and eventually:
Jan 3 08:45:39: --- last message repeated 1 time ---
Jan 3 08:45:39 Puss mdworker[59604]: socket(PF_ROUTE) failed: Operation not permitted
Jan 3 08:45:39 Puss sandboxd[59747]: mdworker(59604) deny system-socket
Jan 3 08:45:39 Puss com.apple.launchd[1] (0x100101ea0.mach_init.mdworker[59604]): Exited with exit code: 1
Can the vpn really have an influence on Spotlight? What is spotlight trying to index and why is it denied?
Eventually, i may be dreaming, but it seems that something is chewing up my SSD space. Without adding much files, it feels like free space is going down.
Thanks for any help.

I solved the problem by adding the hidden '/private' directory on the harddisk to the places that spotlight is forbidden to index (in the systems preference pane -> Spotlight ->Privacy)
You have drag the '/private' folder into the locations box.
You may have to install something like 'secrets' to show hidden folders in the finder.
(see here: https://code.google.com/p/blacktree-secrets/wiki/Help )
ignore everything above - same error messages came back

How to configure the system log on Mac OS X???

Now the system log is removed one week after the creation but I need to store it permanently.
How to do it??

Eugene Mirgorodskiy wrote:
Now the system log is removed one week after the creation but I need to store it permanently.
It's not really "removed". The system log is "rotated" out, at least partly to avoid having it grow too large. The older log information is in a series of files named like "system.log.0.bz2, system.log.1.bz2, etc. A file of type ".bz2" is a particular type of compressed file. Eventually the oldest of those files will be deleted. If you want to keep those forever, I'd copy off the oldest of those files on a regular basis to some other location.

Understanding the system log (boot time 2 minutes)

Dear Apple Discussion,
I am trying to read the system.log correctly - mainly because my boot time is 2 minutes.
I have read that the beginning of the boot up is indicated by the line:
localhost kernel[0]: standard timeslicing quantum is 10000 us
is this correct?
Next, does the line:
loginwindow[165]: Login Window Started Security Agent
indicate that the login window has come up?
If both of these are correct then my boot time should be 18s (according to the time stamps in the log) - it defefinitely is not that.
Does the boot process start instead at this line:
shutdown: reboot by root:
If this were the case, the boot time would be closer to 2 minutes according to the log (which is what it actually is).
This then brings up the next problem: the two minutes basically come from the following line:
Nov 29 17:30:24 Purrfekt shutdown: reboot by root:
Nov 29 17:30:24 Purrfekt SystemStarter[177]: authentication service (194) did not complete successfully
Nov 29 17:30:24 Purrfekt kernel[0]: CiscoVPN : unloading cisco ipsec kernel module.
Nov 29 17:30:24 Purrfekt kernel[0]: CiscoVPN : detaching from interface: en1.
Nov 29 17:30:24 Purrfekt kernel[0]: CiscoVPN : interface en1, filter has been safely detached.
Nov 29 17:30:24 Purrfekt kernel[0]: CiscoVPN : detaching from interface: en0.
Nov 29 17:30:24 Purrfekt kernel[0]: CiscoVPN : interface en0, filter has been safely detached.
Nov 29 17:32:12 localhost kernel[0]: standard timeslicing quantum is 10000 us
ending line of the boot process occurs at (if my above assumption is correct):
Nov 29 17:32:31 Purrfekt loginwindow[165]: Login Window Started Security Agent
So why does it hang for so long at this one process? Am I reading the log incorrectly? I have searched around here and also on google ("slow boot time", "cisco vpn tiger", etc..) but haven't found anything relating to my problem.
Thanks for any help.
MonkeyApple
v.1 PowerBook G4 15'' Mac OS X (10.4.3)

I am trying to read the system.log correctly - mainly because my boot time is 2 minutes.
It appears to be that a restart or shutdown process delays nearly 2 minutes rather than a startup process, presumably due to one of WindowServer children or a bug stays in Mac OS X 10.4.3 Update-- Mine delays approximately 30 - 40 minutes on PowerMac G5 2.7 Ghz on every shutdown or restart process. Your computer is PowerMac G4 so that make sense. I found a suspect application which is a security related. Although I am still investigating further because the issue does not occur on the lower drive bay where I install another Mac OS X 10.4.3 Update (but no third-party software) as a test facility.
localhost kernel[0]: standard timeslicing quantum is 10000 us
This is correct and the first line to display sequential events in a boot process.
loginwindow[165]: Login Window Started Security Agent
This is also a normal behavior.
SystemStarter[xxx]: authentication service (xxx) did not complete successfully
This can be displayed depending on a computer configuration.
A sequential event from CiscoVPN: unloading cisco ipsec kernel module to CiscoVPN: interface en0, filter has been safely detached seems to be all right if you PROPERLY configure VPN policy and IPsec (Internet Protocol Security) authenticate, etc for your Cisco device. IPsec is a framework for a set of protocols for security at the network or packet processing layer of network communication.
I suggest to check all related settings with Netwrok/Sharing panes and the router configurations for VPN (IPsec), IPv6, security, etc. Also check routing table and all socket connections after you launch Network Utility or via Terminal commands.
FYI: interface en0 is a wired connection and interface en1 is a wireless connection such as AirPort. IPsec kernel module is a unit of kernel program or componet for IPsec.
Hope this helps.
G5 Dual 2.7GHz, Dell XPS 3.2GHz, G3B&W, Sony LTop Mac OS X (10.4.3) Tiger10.4.2, MacOS 9.2.2, WinXP Pro, Win ME, Linux

Job also cancelled due to process termination. See the system log

Hi Friends,
I am working Interface Programs in HCM Module.
My problem is when i am Executing my program in BACKGROUND .After some time my job is canceling. In log i am getting message
"Job also cancelled due to process termination. See the system log"
when i see that system log also i am unable to find any thing.
but in fore ground is working fine .
Please help me .
Thanks in Advance..
Regards,
Kumar...

Hi,
You need to check that program in debugging for the Backgournd process.
For doing the debugging of the background process do the following steps.
1)go sm37 and select your job.
2)in the command line just type JDBG (not the /nJDBG OR /oJDBG) and hit enter. it goes to the debuggin mode.
Thanks

How do we do Archiving the system logs in SAP-BW

Hi All
How do we do Archiving the system logs in SAP-BW.
Can anyone will let me know reagrding this
If you have any docs also pls forward to my id [email protected]
Thanks & Regards
Balji

Balaji,
What is the landscape you have ?
Windows / Unix / Solaris etc ?
Also there are a lot of logs that are generated:
Archive log ,
System Log,
Transaction log etc...
The usual procedure is to copy them into another location and then delete the original file , the system will usually recreate the log and start logging new entries..
Arun
Hope it helps...

Managing the system.log

Hi!
Just can't find any information regarding the system.log file (.../cluster/server/log/system.log); size limit or other information. I have looked in the config tool and the admin tool, but all I find has to do with the other log files. I have also looked in the Administrator guide. Could anyone guide me to some information?
regards,
Hilde

Hi Hilde
u can find log under C:\usr\sap\SID\JC<instance-number>\j2ee\cluster\server0\log
using support platform u also get detail about log.
http://j2ee_host:j2ee-port/sp
login with administrator user.
expand the node under server node and check logging property.
regards,
kaushal

Understand the System Log?

I want to understand the System Log. What happened at this or that time, but in particular I want to see how much my son is playing World of Warcraft.
I know the info is there somewhere, but I don't know how to retrieve it...?

Hi, Andreas.
Understanding system logging is a rather complex issue: not one that lends itself to a quick description here. Its primary use, unless your a SysAdmin, is for gleaning additional information for troubleshooting, as discussed in my Checking Console for clues FAQ.
Tracking your child's game play is not something you are likely to find in the Console logs. Instead, consider MacMinder.
Since you have children using computers, you may also want to review my "Internet Safety for Children" FAQ.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Push notification service fills the system log with errors

When I have the push notification service enabled, my system logs become filled with messages such as this:
Sep 8 22:54:54 xserve jabberd/c2s[2175]: [7] [::ffff:192.168.1.100, port=50064] connect
Sep 8 22:54:54 xserve jabberd/c2s[2175]: [7] [::ffff:192.168.1.100, port=50064] disconnect jid=unbound, packets: 0
They occur at a rate of about two every second. What does that message mean and how do I stop it?

When I took a look at push notification, I noticed that it was listening to a different port than what dovecot had been configured to use.(jabberd was set to listen to 5347, while Dovecot (email) was using the standard 5222 port for that open protocol. Not sure what the ichat server is set to use.
Eventually, I did manage to get it working by updating the push notification config to listen to 5222. But it made no real difference because thunderbird and mail.app prefer imap updatings instead of push notification. So I turned it off.
Not sure if this is of any help to you.
Message was edited by: JFMezei

AppleFWOHCI_Async messages in the system.log

Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.

verzunof wrote:
Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.
verzunof wrote:
I'm not certain if those messages indicate a power issue but you can try *resetting the System Management Controller* and see if that helps. Here's how: http://support.apple.com/kb/HT1806
"The System Management Controller (SMC) is a chip on the logic board that controls all power functions for your computer. If your computer is experiencing any power issue, resetting the SMC may resolve it. The SMC controls several functions, including:
Telling the computer when to turn on, turn off, sleep, wake, idle, and so forth.
Handling system resets from various commands.
Controlling the fans."
Carolyn

With Mac OS X can the system.log files be safely deleted?

I just did a search of my HD using OmniDiskSweeper, and there's a file called system.log that's 8GB The path is /private/var/log/system.log Can this file be deleted without any bad effects? Wouldn't the system just create a new one when needed? I opened the file in Console, looked at some of it, and as far as I can tell I would think it's okay to delete, but I'd like to be sure before I do it. Thanks!

I also just found a new file was created-- /private/var/tmp/tmp.1.UhmvZp after I looked in the console and had to force quit. That one is 3.3GB. Any of these files can be deleted? I know not to delete the sleepimage file, which just created another 1GB swapfile and is up to 4GB.
In September I brought my Macbook to an Apple genius because I was loosing so much HD space without downloading or installing anything. He told me to reinstall the OS and it did help recover some space. Now I know where that HD space is going!

2008R2 Domain - Recently started receiving the old EventID 8003 Bowser in the System Log - Any ideas?

Hi All,
I've "googled" this to death and noted the registry keys that are associated with the "Computer Browser Service."
On the PDC:
IsDomainMaster = TRUE
MaintainServerList = Auto
On one of the Workstations noted in the EventID Logs:
MaintainServerList = Auto
There is no "IsDomainMaster" key on the Workstation.
In addition, I've looked for the "browstat.exe" utility, but after my google searches, it turns out that tool has been deprecated for 2008R2 and Win7. Our entire company is on Win7...
From what I've read, the logged 8003 messages are no big deal, but it seems odd that all of a sudden, late May, I started receiving these messages and I'm trying to retrace my steps. The DCs had not been patched at that time.
Thank you for your time,
Mr Mister

We can close this question.
From an elevated prompt, I ran 'fsutil resource setautoreset true' and attempted to remove the files with .blf and regtrans-ms file extensions from C:\Windows\System32\config\TxR. but these files were locked by system processes. (They are also
tagged with the hidden file attrib so you may not see them at first)
So, I booted the system with a Windows 2008 R2 Install Disk, selected repair OS and selected the command prompt. I then performed a chkdsk /f c: and selected "Y" to unmount the drive. It made some repairs.
With the system booted from the install disk, and chkdsk executed, the locks were freed and I was able to delete the files from C:\Windows\System32\config\TxR.
Once the system rebooted, the services came back fine and everything was back to normal.

Can't delete the system log

It's taking up 28 GB of my hard drive , delete bin is greeted out. How can I delete it please. I will copy it to external drive before I delete in case I need it. Thanks for help.

You can't delete an account if it is logged in, or if it is the only admin account on the system. So make sure that there is at least one other admin account, and that the account you want to delete os logged out.

When upgrading from 10.7 to 10.8.2, are the system.log files backed up anywhere?

One of my clients needs to confirm whether a USB device was plugged into their computer between two dates in September 2012 because they're worried some sensitive data may have been stolen. However, their computers were upgraded from 10.7 to 10.8.2 on the 29th of November 2012, and since the kernel.log and system.log files have now been combined in this update, it has obviously created a new file in the new format. Sadly, this has only come to light now, and there appear to be no backups of the whole drive from before this date.
Does anyone know if the 10.7 logfiles would have been preserved anywhere during the upgrade, or are they lost for good?

No, the merging operation deletes the old files during upgrading the OS X. Have you tried searching even hidden files starting at the root level so see if anything has been hidden away somewhere? I haven't seen the upgrade do that but if this is really important it may be worth the effort.

Cube compression filling up the system logs

Similar Messages

Maybe you are looking for