Log buffer overflow

I have been receiving the flex log buffer overflow error for a long time. I don't believe it is causing any problem but I'm not sure.
I have Iplanet Web Server 4.1 on Solaris 2.6.
I have changed the LogFlushInterval from the default 30 seconds to 5 seconds.
I am logging a great deal of information
My questions are...
should I be concerned ?
when I get that error is the buffer being immediately dumped to the log file ?
am I losing any log information ?
can I increase the buffer size ?
should I reduce the LogFlushInterval any more ?
Thanks

The error message indicates that an access log entry exceeded the maximum of 4096 bytes and was truncated. You should check the access log file for suspicious entries.
Adjusting LogFlushInterval won't affect this problem, and unfortunately there's no way to increase flex log buffer size.

Similar Messages

  • Flex Log Buffer Overflow Error

    Hello,
    We are running SunOne Server 6 SP4 on Solaris 2.8.
    We have a site that has numerous URL Forwards that all work. We added another one today and when you try and go to that one we get the following error in the error log:
    flex log buffer overflow- greater than 4096 characters
    Any help on what this means and how to fix it?
    thanks!!

    We found the problem.
    We had a recursive URL call.
    example: what not to do when setting up URL forwards.
    URL Forward /emp directory to /emp/some_file

  • Problem of buffer overflow in Iplanet 6.0sp1

    Hi,
    I am getting these following error messages in the logs
    [30/Mar/2004:12:55:06] warning (19529): flex log buffer overflow- greater than 4096 characters
    Also I am getting a error in logs like filename.ext is temporarly not available
    I am not able to figure out why we are getting this error. If its a patch which needs to be put on the web server, then which patch I would be needing to install.
    Nikhil

    This has been answered before:
    http://swforum.sun.com/jive/thread.jspa?forumID=16&threadID=19626
    PS: 6.0sp1 is very old, perhaps you should consider upgrading to 6.0sp7 or 6.1sp1.
    Thanks
    Manish

  • Device buffer overflow error and Log component missing

    I have some previous information in "Error device buffer overflow" post.
    I am currently running a windows XP machine with a 3.4 GHz
    processor and 3 GB of RAM. I tried using just one 9233 module with the
    cDAQ9172 and it worked. I added the second 9233 module and it started
    giving me the error. I checked the memory usage when acquisition is not
    started it was 868 MB and the CPU usage was 0-2%. When I started
    acquisition the memory usage did not change much it went to about 880
    MB and the CPU to about 100% and the error was displayed. The code shows the error that device buffer is overflowing when I use the program on a new machine even for one module with cDAQ9172 but when I switch it back to the original machine it works for single module but not for multiple.
    As the error suggests. I tried switching the update views in "Update
    signals while running" and "Prepare log data for viewing" off but it
    still did not help. If I switch both these off I wont be able to see
    what kind of impact data I am collecting. Please do correct me if I am
    wrong.
    I  need to colelct the impact data on a printer and I have
    a many locations on it that I need to collect data from.  Please
    suggest a solution for this problem.
          Also, if i try using the same project on some other machine it gives me an error indicating some log component files are missing from signal express and need to be installed. This happens when i transfer the project from one machine to another. 
    Thank you.

    Stu,
    You will still be able to print your data in a later step when setting the two options recommended by the error code.  What is likely happening when you try to move the project is that the project has log files still associated with it from previous attempts.  You should save a copy of the project and in that copy delete the log files, then try to move the project over.  SE projects are directly associated with the log files they create. This should allow you to move the project to a new computer.
    When you go to run your project, you should shut down as many background processes as possible, such as IM clients.  If you can disconnect from your network, I would suggest doing that and turning off any antivirus/anti-spyware software you have to free up resources.
    A couple of further questions:
    Are you connecting to a USB 1.0 or USB 2.0 port?  You should be able to determine this by opening the device manager on your computer and expanding "Universal Serial Bus" section. If any of the drivers have "Enhanced" in their name, you have a USB 2.0 port.
    Does this behavior repeat with any combination of the three modules?  For instance, does it work if you just have module one, module two, or module three install?  Do you still get the error if module two and three are used instead of one and two? (This will help determine if we are encountering a problem with the modules or with SE)
    Finally, if you create a project that contains only one step that only reads the data off of all three modules, do you still get the error? (This will help isolate the problem)
    Seth B.
    Staff Test Engineer | National Instruments
    Certified LabVIEW Developer
    Certified TestStand Developer
    “Engineers like to solve problems. If there are no problems handily available, they will create their own problems.”- Scott Adams

  • XMLTRANSFORM Too large stylesheet - code buffer overflow issue

    Hi All,
    My question is related to MSWordML generation from PLSQL stored procedure.
    1. I have table, containing XSLT stylesheets for different documents
    2. PLSQL stored procedure is generating dynamic content depending on some params and at the end I'm using
    SELECT XMLTRANSFORM(XMLTYPE.createxml(db_data_clob), XMLTYPE.createxml(x.xslt_clob)).GetClobVal()
    INTO   res
    FROM   msword_ml_data x
    WHERE  x.report_id = rep_id_variable;
    where : x.xslt_clob -> column, containing XSLT CLOB
    db_data_clob -> dynamic content CLOB
    res -> CLOB result
    All this was working fine on Oracle11gR1, but I had to reinstall database and I said why not install Oracle11gR2 ...
    Guess what. Stored procedure is raising exception when using XMLTRANSFORM :
    Exception : : ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00004: internal error "Too large stylesheet - code buffer overflow"
    Google says nothing about it. I don't recall setting some special DB property in Oracle11gR1.
    Has anyone encountered this ?
    I haven't changed procedure nor table.
    I'm using exactly the same XSLT's from Java code and they are working just fine, so they are not the reason. My guess is that something in Oracle11gR2 related to XML processing is changed.
    If anyone could help, thanks in advance

    For those who are interested.
    I have logged a service request and it turned out that this is is a bug in Oracle 11gR2.
    "The limitation on the style sheet is not exactly a size limit but a limitation on the number of style sheet instructions and depends on the way the style sheet has been written. This is a C based parser limitation"
    Anyway, the workaround is to create Java stored procedure and do transformation from there.

  • Tiger to Snow Leopard upgrade fails  with buffer overflow

    I'm not sure where to proceed with the following situation:
    I have a 17" MB pro with 1GB memory and 22GB free hard drive space. I booted into the installer from the CD and stepped through the prompts without changing any options to the point where the install starts doing it's magic. Shortly after starting, the install will crash complaining about a buffer overflow during/just after the part where it's finding system files.
    I originally tried to do this with only 10GB free, but after the first failure, I did a repair disk using the Disk Utility and removed a bunch of really old files I no longer needed, which brought the available disk space to 22GB, but this did not help anything. At this point, I'm not sure what to do. I use Carbon Copy Cloner as a backup so I can do a full wipe and install, however I would prefer to avoid that as it is a lot of work to get things back.
    Any assistance is greatly appreciated!
    Error log follows. I cut out a lot of stuff so please let me know if that detail is needed.
    Sep 10 10:35:26 localhost OSInstaller[142]: Total install size including padding: 7325778944 b
    Sep 10 10:35:28 localhost OSInstaller[142]: Starting installation:
    Sep 10 10:35:28 localhost OSInstaller[142]: Calculating expected install size requirements
    Sep 10 10:35:28 localhost Unknown[84]: 2009-09-10 10:35:28.624 Mac OS X Installer[142:c607] Looking for system packages
    Sep 10 10:35:42 localhost Unknown[84]: 2009-09-10 10:35:42.115 Mac OS X Installer[142:c607] Finding system files...
    Sep 10 10:36:01 localhost Unknown[84]: buffer overflow!
    Sep 10 10:37:55 localhost LCA[83]: Child exited with status 6
    Sep 10 10:37:59 localhost Unknown[162]: Launching the Installer Crash Log Viewer
    Sep 10 10:38:32 localhost ReportCrash[159]: Process: Mac OS X Installer [142]
    Sep 10 10:38:32 localhost ReportCrash[159]: Path: /System/Installation/CDIS/Mac OS X Installer.app/Contents/MacOS/Mac OS X Installer
    Sep 10 10:38:32 localhost ReportCrash[159]: Identifier: Mac OS X Installer
    Sep 10 10:38:32 localhost ReportCrash[159]: Version: ??? (???)
    Sep 10 10:38:32 localhost ReportCrash[159]: Code Type: X86 (Native)
    Sep 10 10:38:32 localhost ReportCrash[159]: Parent Process: LCA [83]
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Date/Time: 2009-09-10 10:36:12.446 -0700
    Sep 10 10:38:32 localhost ReportCrash[159]: OS Version: Mac OS X 10.6 (10A432)
    Sep 10 10:38:32 localhost ReportCrash[159]: Report Version: 6
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Exception Type: EXC_CRASH (SIGABRT)
    Sep 10 10:38:32 localhost ReportCrash[159]: Exception Codes: 0x0000000000000000, 0x0000000000000000
    Sep 10 10:38:32 localhost ReportCrash[159]: Crashed Thread: 9
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Application Specific Information:
    Sep 10 10:38:32 localhost ReportCrash[159]: abort() called
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 0: Dispatch queue: com.apple.main-thread
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002b78fa machmsgtrap + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x002b8067 mach_msg + 68
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 com.apple.CoreFoundation 0x005d9dbf __CFRunLoopRun + 2447
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.CoreFoundation 0x005d8d34 CFRunLoopRunSpecific + 452
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.CoreFoundation 0x005d8b61 CFRunLoopRunInMode + 97
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.HIToolbox 0x05143fec RunCurrentEventLoopInMode + 392
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 com.apple.HIToolbox 0x05143da3 ReceiveNextEventCommon + 354
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 com.apple.HIToolbox 0x05143c28 BlockUntilNextEventMatchingListInMode + 81
    Sep 10 10:38:32 localhost ReportCrash[159]: 8 com.apple.AppKit 0x00bdbb99 _DPSNextEvent + 847
    Sep 10 10:38:32 localhost ReportCrash[159]: 9 com.apple.AppKit 0x00bdb40e -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
    Sep 10 10:38:32 localhost ReportCrash[159]: 10 com.apple.AppKit 0x00b9d5fb -[NSApplication run] + 821
    Sep 10 10:38:32 localhost ReportCrash[159]: 11 com.apple.AppKit 0x00b95695 NSApplicationMain + 574
    Sep 10 10:38:32 localhost ReportCrash[159]: 12 com.apple.MacOSXInstaller 0x00006393 0x1000 + 21395
    Sep 10 10:38:32 localhost ReportCrash[159]: 13 com.apple.MacOSXInstaller 0x00002f25 0x1000 + 7973
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 1:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002e582a _semwaitsignal + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x00311681 nanosleep$UNIX2003 + 188
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 libSystem.B.dylib 0x00347872 sleep$UNIX2003 + 63
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.installframework 0x000abe13 dologwatch + 51
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 2: Dispatch queue: com.apple.libdispatch-manager
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002de10a kevent + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x002de824 dispatch_mgrinvoke + 215
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 libSystem.B.dylib 0x002ddce1 dispatch_queueinvoke + 163
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 libSystem.B.dylib 0x002dda86 dispatch_workerthread2 + 234
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 libSystem.B.dylib 0x002dd511 pthreadwqthread + 390
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 libSystem.B.dylib 0x002dd356 start_wqthread + 30
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 3:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002b78fa machmsgtrap + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x002b8067 mach_msg + 68
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 com.apple.CoreFoundation 0x005d9dbf __CFRunLoopRun + 2447
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.CoreFoundation 0x005d8d34 CFRunLoopRunSpecific + 452
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.CoreFoundation 0x005d8b61 CFRunLoopRunInMode + 97
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.Foundation 0x00863498 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 329
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 com.apple.Foundation 0x0082a964 -[NSThread main] + 45
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 com.apple.Foundation 0x0082a914 _NSThread__main_ + 1499
    Sep 10 10:38:32 localhost ReportCrash[159]: 8 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 9 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 4:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002b78fa machmsgtrap + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x002b8067 mach_msg + 68
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 com.apple.CoreFoundation 0x005d9dbf __CFRunLoopRun + 2447
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.CoreFoundation 0x005d8d34 CFRunLoopRunSpecific + 452
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.CoreFoundation 0x005d8b61 CFRunLoopRunInMode + 97
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.Foundation 0x008643e4 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 com.apple.Foundation 0x008b93c8 -[NSRunLoop(NSRunLoop) runUntilDate:] + 79
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 com.apple.osinstallframework 0x0002dbc3 -[OSPreInstallSizingQueueElement _calculateReapedFreeSpace] + 176
    Sep 10 10:38:32 localhost ReportCrash[159]: 8 com.apple.osinstallframework 0x0002e1dd -[OSPreInstallSizingQueueElement run] + 178
    Sep 10 10:38:32 localhost ReportCrash[159]: 9 com.apple.installframework 0x0007be54 -[IFSession(Jobs) _runMetaQueueEngine] + 1594
    Sep 10 10:38:32 localhost ReportCrash[159]: 10 com.apple.Foundation 0x0082a964 -[NSThread main] + 45
    Sep 10 10:38:32 localhost ReportCrash[159]: 11 com.apple.Foundation 0x0082a914 _NSThread__main_ + 1499
    Sep 10 10:38:32 localhost ReportCrash[159]: 12 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 13 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 5:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002b795a semaphoretimedwait_signaltrap + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x002e5469 pthread_condwait + 1066
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 libSystem.B.dylib 0x00314268 pthreadcond_timedwait_relativenp + 47
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.Foundation 0x00866aec -[NSCondition waitUntilDate:] + 453
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.Foundation 0x0081f881 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.Foundation 0x0081f764 -[NSConditionLock lockWhenCondition:] + 69
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 com.apple.installframework 0x0006aef6 +[IFDTargetController(WorkerThread) _handleTargetRequests] + 1169
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 com.apple.Foundation 0x0082a964 -[NSThread main] + 45
    Sep 10 10:38:32 localhost ReportCrash[159]: 8 com.apple.Foundation 0x0082a914 _NSThread__main_ + 1499
    Sep 10 10:38:32 localhost ReportCrash[159]: 9 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 10 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 6:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002e582a _semwaitsignal + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x00311681 nanosleep$UNIX2003 + 188
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 com.apple.Foundation 0x008b4c30 +[NSThread sleepForTimeInterval:] + 123
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.SystemMigration 0x01a04b69 -[SMManager _suppressSpotlightThread:] + 104
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.Foundation 0x0082a964 -[NSThread main] + 45
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.Foundation 0x0082a914 _NSThread__main_ + 1499
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 7:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002d6876 select$DARWIN_EXTSN + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 com.apple.CoreFoundation 0x0061904d __CFSocketManager + 1085
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 8:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x002b78fa machmsgtrap + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x002b8067 mach_msg + 68
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 com.apple.CoreFoundation 0x005d9dbf __CFRunLoopRun + 2447
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 com.apple.CoreFoundation 0x005d8d34 CFRunLoopRunSpecific + 452
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.CoreFoundation 0x005d8b61 CFRunLoopRunInMode + 97
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.Foundation 0x008643e4 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 com.apple.Foundation 0x008b93c8 -[NSRunLoop(NSRunLoop) runUntilDate:] + 79
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 com.apple.installframework 0x0007d48d -[IFDInstallController(Private) _install] + 1561
    Sep 10 10:38:32 localhost ReportCrash[159]: 8 com.apple.osinstallframework 0x00018ccc -[OSInstallController(Private) _install] + 552
    Sep 10 10:38:32 localhost ReportCrash[159]: 9 com.apple.Foundation 0x0082a964 -[NSThread main] + 45
    Sep 10 10:38:32 localhost ReportCrash[159]: 10 com.apple.Foundation 0x0082a914 _NSThread__main_ + 1499
    Sep 10 10:38:32 localhost ReportCrash[159]: 11 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 12 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 9 Crashed:
    Sep 10 10:38:32 localhost ReportCrash[159]: 0 libSystem.B.dylib 0x00324c8e _semwait_signalnocancel + 10
    Sep 10 10:38:32 localhost ReportCrash[159]: 1 libSystem.B.dylib 0x00324b72 nanosleep$NOCANCEL$UNIX2003 + 166
    Sep 10 10:38:32 localhost ReportCrash[159]: 2 libSystem.B.dylib 0x003a05b2 usleep$NOCANCEL$UNIX2003 + 61
    Sep 10 10:38:32 localhost ReportCrash[159]: 3 libSystem.B.dylib 0x003c1c68 abort + 105
    Sep 10 10:38:32 localhost ReportCrash[159]: 4 com.apple.bom 0x0194fb3d _defaultHandler + 64
    Sep 10 10:38:32 localhost ReportCrash[159]: 5 com.apple.bom 0x0194fa8f _BOMExceptionHandlerCall + 89
    Sep 10 10:38:32 localhost ReportCrash[159]: 6 com.apple.bom 0x01971c01 BOMStreamReadUInt32 + 134
    Sep 10 10:38:32 localhost ReportCrash[159]: 7 com.apple.bom 0x01954e40 BOMBomOpen + 226
    Sep 10 10:38:32 localhost ReportCrash[159]: 8 com.apple.PackageKit 0x019a98e7 -[PKBOM initWithBOMPath:] + 148
    Sep 10 10:38:32 localhost ReportCrash[159]: 9 com.apple.PackageKit 0x019b82fe -[PKReceipt(Private) _BOM] + 77
    Sep 10 10:38:32 localhost ReportCrash[159]: 10 com.apple.PackageKit 0x019b7d55 -[PKReceipt(Private) _directoryEnumerator] + 34
    Sep 10 10:38:32 localhost ReportCrash[159]: 11 com.apple.SystemMigration 0x01a4deff -[SMFindSystemFiles _findSystemPaths] + 1785
    Sep 10 10:38:32 localhost ReportCrash[159]: 12 com.apple.SystemMigration 0x01a4e490 -[SMFindSystemFiles systemPaths] + 796
    Sep 10 10:38:32 localhost ReportCrash[159]: 13 com.apple.SystemMigration 0x01a50387 -[SMPathAnalyzer prunedSystemPathsReturningSize:] + 179
    Sep 10 10:38:32 localhost ReportCrash[159]: 14 com.apple.SystemMigration 0x01a508ca -[SMPathAnalyzer prunedReaperPathsReturningSize:] + 53
    Sep 10 10:38:32 localhost ReportCrash[159]: 15 com.apple.osinstallframework 0x00028807 -[IFDiskObject(OSExtensions) calculateReapedFreeSpace] + 404
    Sep 10 10:38:32 localhost ReportCrash[159]: 16 com.apple.osinstallframework 0x0002daf4 -[OSPreInstallSizingQueueElement _calculateReapedFreeSpaceThread] + 71
    Sep 10 10:38:32 localhost ReportCrash[159]: 17 com.apple.Foundation 0x0082a964 -[NSThread main] + 45
    Sep 10 10:38:32 localhost ReportCrash[159]: 18 com.apple.Foundation 0x0082a914 _NSThread__main_ + 1499
    Sep 10 10:38:32 localhost ReportCrash[159]: 19 libSystem.B.dylib 0x002e4fe1 pthreadstart + 345
    Sep 10 10:38:32 localhost ReportCrash[159]: 20 libSystem.B.dylib 0x002e4e66 thread_start + 34
    Sep 10 10:38:32 localhost ReportCrash[159]:
    Sep 10 10:38:32 localhost ReportCrash[159]: Thread 9 crashed with X86 Thread State (32-bit):
    Sep 10 10:38:32 localhost ReportCrash[159]: eax: 0x0000003c ebx: 0x00324ad9 ecx: 0xb04aa82c edx: 0x00324c8e
    Sep 10 10:38:32 localhost ReportCrash[159]: edi: 0x00000000 esi: 0xb04aa888 ebp: 0xb04aa868 esp: 0xb04aa82c
    Sep 10 10:38:32 localhost ReportCrash[159]: ss: 0x0000001f efl: 0x00000247 eip: 0x00324c8e cs: 0x00000007
    Sep 10 10:38:32 localhost ReportCrash[159]: ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
    Sep 10 10:38:32 localhost ReportCrash[159]: cr2: 0xffe2a178
    Sep 10 10:38:32 localhost ReportCrash[159]:

    a brody wrote:
    Regarding the need to buy the packaged bundle, I keep seeing folks here and elsewhere claiming that is not necessary.
    That's because they have not read, or concern themselves with the license agreement. Section 2. "Permitted License Uses and Restrictions", section C says on http://images.apple.com/legal/sla/docs/macosx106.pdf
    It's been read forwards, backwards, and upside down. Nowhere on the packaging is there any identification of the $29 (or $49 family pack) version as only suitable as a "Leopard upgrade" version. There are vague mentions about it on Apple's online sales page and in press releases. I've read the license terms thoroughly and the only conclusion that could reasonably be conferred is that the $29 version carries a "single user" license simply because it doesn't say "family pack". There are plenty of reports that it installs over Tiger just fine.
    Granted I've read numerous reports and I installed my copy over Leopard. However - imagine someone who vaguely heard about it, walked into a store and bought a copy, thoroughly looked over the box and the license terms (within the disc), and installed it in good faith over Tiger. There is ZERO, ZIP, NADA on the package that would lead anyone to believe it is anything but a copy with a "SINGLE USER" license where the terms don't preclude installing over Tiger.
    C. Leopard Upgrade Licenses. If you have purchased an Upgrade for Mac OS X Leopard license, then subject to the terms and conditions of this License, you are granted a limited non-exclusive license to install, use and run one (1) copy of the Apple Software on a single Apple-branded computer as long as that computer has a properly licensed copy of *Mac OS X Leopard already installed on it.*
    The emphasis above is mine.
    While this may not be enforced by a software key, it is there in the license agreement on the PDF included on the CD, when you purchase the under $100 licenses, which are also called "Upgrade" on the store.
    There's an opinion that "Leopard upgrade" only applies to the "Up To Date" versions that require proof of purchase of a recent Mac computer. The reports on those installer discs are that they do in fact check for a valid Leopard installation.
    The following has the most in-depth discussion on the subject of whether or not the license allows for Snow Leopard over Tiger that I've seen so far:
    http://www.mackb.com/Uwe/Forum.aspx/mac/26361/the-29-purchase-price-of-Snow-Leop ard
    This is the best description I've heard on it, from someone who identifies himself as "David Empson":
    http://www.mackb.com/Uwe/Threads/Single.aspx/mac/26361?ArtId=1j5mofd.1pw6lllbtpj dwN%25dempson%40actrix.gen.nz
    If someone walks in and buys Snow Leopard, without written notice from
    Apple that they are buying an Upgrade version which requires Leopard,
    and without discussing that point with the seller, the buyer is under no
    obligation to have researched their purchase in advance and know all of
    Apple's publicity statements from three months ago.
    They are buying it in good faith, and the contract (licence) is valid.

  • Script running in the background and buffer overflow

    Hi,
    I have written a script that is supposed to be a background process, which will check every 5 minutes if given person is logged in on Skype.
    The script does it basic job (alters me when given person is on Skype) but when I try to quit it (see code below, first display dialog inside on idle handler) it does not quit. Instead it displays "buffer overflow" or "stack overflow" error message (I am not certain how to exactly translate the error message - it is not in English as I am not running MacOS X in English). Also on rare occasions it displays another error message about terminated connection.
    Any advise about how get rid of these errors would be greatly appreciated.
    I have saved the script as an application and I have added to Contents/info.plist the following:
    Application is agent (UIElement) = true
    Here is the applet code:
    global interval
    global _path
    on run
    set _path to POSIX path of (alias ((path to me as text) & "Contents:Resources:sound.aif"))
    set interval to 300
    end run
    on idle
    tell application "System Events"
    set _run to (name of processes) contains "Skype"
    end tell
    if _run = true then
    tell application "Skype"
    set _Calls to send command "SEARCH ACTIVECALLS" script name "cal"
    end tell
    if _Calls = "CALLS" then
    tell application "Skype"
    set Lstat to send command "GET USER " & "user_nickname" & " ONLINESTATUS" script name "stats"
    set AppleScript's text item delimiters to " "
    set status to text item 4 of Lstat
    if status is "OFFLINE" then
    --do nothing
    else
    do shell script "afplay " & _path
    tell me
    activate
    display dialog "user_nickname is on Skypie" buttons {"OK", "Change interval", "Quit"} default button 1 giving up after 60 with icon note with title "Skype check"
    if button returned of the result is "Quit" then
    quit
    else if button returned of the result is "Change interval" then
    display dialog "Enter new interval in minutes:" buttons {"OK"} default button 1 default answer "5" with title "Skype check"
    set interval to ((text returned of the result as number) * 60)
    end if
    end tell
    end if
    end tell
    else
    -- do nothing
    end if
    else
    -- do nothing
    end if
    return (interval as number)
    end idle
    on quit
    quit
    end quit

    Delete the following code:
    on quit
    quit
    end quit
    The purpose of the 'on quit' handler is so additional instructions can be executed when the script is told to quit. If desired, 'continue quit' can be part of the handler to call the normal quit command; without the 'continue', the script just repeats the handler over and over with no exit, which causes the overflow.
    (53695)

  • Character set Conversion Buffer Overflow Error

    Hi,
    I have got an issue while loading data from a flat file to a staging table. i.e., Character set Conversion Buffer Overflow. Suppose there are 10,000 records in a flat file, after running control file only 100+ records are loading to the staging table. Remaining are errored out. I think there is no issue with control file because when I load data from different flat file containing same no. of records as the previous flat file, it is loading all the records. what could be the reason and solution for this issue.
    Can anyone please suggest me how to resolve this issue.

    DBNS_OUTPUT is a poor choice for debugging. It has very limited used. And as you've discovered, merely debugging code can now result in new exceptions in the code.
    The proper approach would be to create your own debug procedure (or package). Have your code call this instead of DBMS_OUTPUT.
    In your debug procedure, you can decide what you want to do with that debug data for that specific program in the current environment and circumstances.
    The program that runs could be a DBMS_JOB in which case DBMS_OUTPUT is useless. The program can be called several layers deep from other PL/SQL code.. and you want to know just who is calling your code. Etc.
    Having your own debug procedure allows you to:
    - create an autonomous transaction and log the debug data to a log table
    - write it to a DBMS_PIPE for interactive debugging
    - write it to DBMS_OUTPUT
    - record the PL/SQL call stack to determine who is calling who
    - record the current session's environment (e.g. session_context)
    - record the current session's statistics, opens cursors, current SQL, etc. (courtesy of the V$ views)
    etc. etc.
    In other words, your debug procedure gives you the flexibility to decide on HOW to handle the debugging.
    And when you code goes into production, your debug procedure ships with, containing a simple NULL command.. Which means that at any time the DBA can (when the need arise), add his/her debug methods into it in order to trace a production problem.
    Using DBMS_OUTPUT is a very poor, and often just wrong, choice.
    It is fine for writing a quick test. But when you are developing production code and using DBMS_OUTPUT, you must ask yourself whether you have made the right choice.
    And this is not just about wrapping DBMS_OUTPUT. But also wrapping other system calls like RAISE_APPLICATION_ERROR and so on.

  • SQLLDR exists with conversion buffer overflow

    Hi ,
    i have a flat file with over 3,50,000+ records in csv format. The loader program exits with conversion buffer overflow error in log file after loading 2 60 000 records
    what i need to change in my ctl file to load full set of records.
    i have used following things in ctl file
    OPTIONS (SKIP=1)
    LOAD DATA
    CHARACTERSET WE8ISO8859P1
    INFILE *
    APPEND
    INTO TABLE SYMCDH_QTC_CONTACTS_ALL_TEMP
    FIELDS TERMINATED BY "|"
    OPTIONALLY ENCLOSED BY '"'
    TRAILING NULLCOLS
    (

    Hi,
    the error occurs because some data you are trying to load, exceeds the limit for a varchar2 column in your database. You know which record it is due to the error. So you can extend the size of the column of the table or adjust the given data in the file or take a part of the data to insert into your table.
    Herald ten Dam
    http://htendam.wordpress.com

  • Redo Log Buffer sizing problem

    My pc has 512mb RAM and i was trying to increase the redo log buffer size. Initially the log_buffer size was 2899456 bytes. So i tried to increase it to 3099456 by issuing the command:
    ALTER SYSTEM SET LOG_BUFFER=3099456 SCOPE=SPFILE;
    And i issued SHUTDOWN IMMEDIATE. Upon restarting my database, when i queried SHOW PARAMETERS LOG_BUFFER . The value has been changed to 7029248 bytes not 3099456 which i wanted. How did this happen?

    1.) We are all volunteers.
    2.) It was only 5 hours between posts and you're complaining that there are no answers?
    3.) You didn't bother to mention platform or Oracle version, even after being specifically asked for it? Which part of "What is your Oracle version?" do you not understand? And yes, the platform may be useful too....
    From memory, there could a couple of things going on. First off, starting in 9i, Oracle allocates memory in granules, so, allocating chunks smaller than granule size can result in being rounded up to granule size. Second, on some platforms, Oracle protects the redo buffer with "guard pages", i.e., extra memory that serves simply to try to prevent accidental memory overflows from corrupting the redo buffer.
    If you want a specific answer, or at least a shot at one, post:
    1.) Oracle version (specific version: 8.1.7.4, 9.2.0.8, 10.2.0.3, etc).
    2.) Platform
    3.) O/S and version
    4.) Current SGA size
    Reposting the same question, or threatening to do so, will get you nowhere.
    -Mark

  • /amserver/ui/Login buffer overflow

    Hi,
    When I try to access AM on default port 80, I get the following message:
    Request entity too large
    A request entity is longer than the server can handle.
    In the error logs
    [12/Jul/2007:12:12:49]
    warning(1554): for host 127.0.01 trying to GET /amserver/ui/Login, flex-log reports: HTTP4/98: buffer overflow (log entry greater than 4096 characters)
    Can anyone please help???
    thanks,
    priyanka

    AM is pretty sensitive to cookie domains. What cookie domain did you assign?
    At a minimum, it must have two dots. Something like .example.com (so, your machine name might have been xyz.example.com).
    Assign an IP to the machine, along with a hostname. Have AM's web container listen on the IP, not local loopback (127.0.0.1 / localhost.localdomain)
    I still am not sure that the error you are getting is because of this, but if its on localhost, you'll find it unusable pretty soon anyway.
    Ankush

  • MODPLSQL generates Buffer Overflow errors trying to login

    I am not entirely sure if this the right place but here it goes anyway:
    We are using Oracle Workflow Manager Standalone(2.6.4) as part of our Warehouse Builder setup on a 10.2.0.3.0. Enterprise database on Linux .
    As such the setup has just recently stopped working where as before it worked for a long time.
    The problem is that it is not possible to log in to Oracle Workflow Manager with any user.
    I have traced this problem to the mod_plsql.so library of the Oracle HTTP Server part of the owf setup.
    What happens is that this module tries to login to the database when a user tries to login with hhis browser and sends an ALTER SESSION statement.
    (This is also described in the docs)
    This statement is misformed however, it contains to much characters.
    Instead of :
    ALTER SESSION SET NLS_LANGUAGE='DUTCH' NLS_TERRITORY='THE NETHERLANDS' NLS_CURRENCY='E'
    the last bit , nls_currency, is being filled with random characters .
    Since the total is more than the allowed limit the database returns, or mod_plsql decides, a ora-1017.
    I used the proxy method described here, January 24, 2006: On a breakable Oracle, to find out what the mod_plsql.so package sends to the database.
    Just read DADS /mod_plsql for SQLPlus.
    I have to do this because these requests are handled as a SYS user and as such are not logged.
    The mod_plsql library is supposed to use the DADS.CONF directives over any environment values.
    However in the case of the PlsqlNLSLanguage directive this does not work.
    The environment variable NLS_LANGUAGE , which is set to dutch , is given precedence.
    It uses that to construct the ALTER SESSION statement.
    If i change the environment variable to AMERICAN, the modplsql.so uses this to pick the currency and it gets the $ sign for NLS_CURRENCY.
    Then the ALTER SESSION statement that is being sent is correct and there is no buffer overflow anymore.
    And the database subsequently allows us in. However this changing of NLS_LANGUAGE at an environment variable level is not desirable for us since we get other translate problems.
    Finally The Questions:
    Why does the mod_plsql.so package also send the NLS_CURRENCY ? This is mentioned in none of the (Oracle) documentation but we can clearly see it happening.
    Where does the mod_plsql.so package get this NLS_CURRENCY from? We don't set it anywhere in the environment or the .conf files, yet it is retrieved somewhere. In our case this is retrieveing some garbage data and thus causing the login to fail. Even looking in the .so library i see no mechanism for nls_currency.
    Why does the mod_plsql.so package favor the environment variable over the DADS.CONF PlsqlNLSLanguage directive. All the manuals say otherwise yet in our case it is not being used. And when i load the library in an editor i see remarks that indeed point to my statement.
    The most important question here is where do i need to look to get the NLS_CURRENCY . It is somehow corrupt and i want to correct this ofcourse.
    Another important one is how we can force the mod_plsql.so package to use the PlsqlNLSLanguage directive since we do not want to change the environment variable.
    I hope someone can help us out here.
    rgrds Mike

    Well i must say i am sorry not haveing received any answer whatsoever.
    This absence of Oracle people here is worrying me, and is the second time in a row lately.
    It seems Oracle is abandoning its own products.
    Anyway, just to answer my own thread so that somebody else gets some benefit from it:
    After investigation i find that it works like this when things go right:
    Modplsql creates a connection with the database and sends numerous key value pairs to the server.
    Such as:
    AUTH_TERMINAL
    AUTH_PROGRAM_NM
    AUTH_MACHINE
    AUTH_PID
    AUTH_SID
    AUTH_SESSKEY
    AUTH_PASSWORD
    AUTH_ACL
    AUTH_ALTER_SESSION    :
    NLS_LANGUAGE
    NLS_TERRITORY
    NLS_CURRENCY
    ... and more NLS_ stuff
    It then sends a pl/sql ALTER SESSION statement this time only with
    NLS_LANGUAGE and
    NLS_TERRITORY
    It then sends several pl/sql code bits probably to test if the database can access owa_match packages.
    In this part it also sends pl/sql to get the database NLS_LANGUAGE, NLS_TERRITORY, and NLS_CHARACTERSET.
    It also sends pl/sql to test owa_util.get_version for the proper version.
    The last part is all of the web stuff: all of the CGI variables including the POSTed data if any. Ofcourse when doing authentication tru basic authentication there is no POST data.
    The authentication info is passed on in the first step with AUTH_PASSWORD.
    The environment value NLS_LANGUAGE is used and parsed in the first bit. The corresponding bits pop up in the AUTH_ALTER_SESSION key-value pair. Modplsql finds the other info(i don't know where really) such as NLS_CURRENCY and puts that there.
    The dads.conf PlsqlNLSLanguage setting is used and parsed in the second step. The second step is formed like  alter session set nls_language='DUTCH' nls_territory='THE NETHERLANDS' .
    So my assumption about modplsql not using the Plsql is wrong here, but due to the error i encountered my debug info never got past step 1.
    If the environment value is not set then a default value of AMERICAN_AMERICA is used.
    What went wrong in my case ?
    The environment var was set to DUTCH. Modplsql uses this to lookup nls_currency as explained to output the info in step 1.
    However nls_currency returned garbage instead of just the euro sign. This is the real problem btw and not solved yet in our case. If someone knows where modplsql gets this info i would like to know this. !
    The other steps were never finished and therefore it looked to the database that the AUTH_ALTER_SESSION    key-value pair was too long.
    It could not authenticate this reqeuest causing the effect that nobody could login. Since these requests are handled as SYS users no logging takes place. Only a trace with the error:
    *** SERVICE NAME:(SYS$USERS) 2013-07-10 11:01:29.414
    *** SESSION ID:(458.3138) 2013-07-10 11:01:29.414
    Buffer overflow for attribute AUTH_ALTER_SESSION - max length[850] actual length[1131]
    indicates there is something wrong here.
    Setting the dads.conf file to override this environment parameter doesn'solve this ofcourse since this info is used somewhere else.
    Fixing it, for now at least , means clearing the envrionment variable , then starting the http server.
    And using DUTCH in the dads.conf file.
    After starting the http server we reset the environment variable.
    I am still looking for an answer on where modplsql gets the NLS_CURRENCY info since thats where the corruption is !
    Hope somebody can use this info.

  • Historical Logging Queue Overflow

    Generating an error "Historical Logging Queue Overflow" Error Code -1967390689. At this time my data logger turns off, no longer allowing me to log data. My input and output queues sizes are roughly 20,000 and my buffer size is 30,000. Possible errors? My database is not very big, I have only run this file for a little over 24hrs. I have not had time to accumulate much data.

    What are the deadband settings that you are using on the objects you are logging? It appears that the values may be changing so rapidly, that an overflow is occurring before the data can actually be written to the database. You may want to check out the following KnowledgeBase, as it may have some useful information.
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/862567530005f09e862567c700746a65?OpenDocument
    Hope this helps,
    Patrick R.

  • Spool file error - Buffer Overflow

    I've a sql script that is running from a.sql file. The script fetches almost 9 million data as a result of the query. Main problem is related to spool file generation. It is saying buffer overflow. But, when i write that query from sql prompts it is running within 2 mins and completes the task within 15 mins.
    I've written -
    set serveroutput on size ######
    But, still it is not working. Total application is freeze whenever i want to run it. Tell me any suggestion if u have.
    Satyaki.

    i guess what you are more concerned with is the output produced by your query (the spool file).
    you need not to see what is displayed on the screen all you need is open up the spool file to
    check for those data in there.
    to suppress the output from the screen and still generates spool file. use the SET TERMOUT option.
    e.g.
    -- code for a producing a sample spool file
    spool r:\sample_spool.txt;
    select * from emp;
    spool off;
    at the SQL*Plus command line:
    SQL> @r:\sample_spool.sql;
         EMPNO ENAME      JOB              MGR HIREDATE         SAL       COMM     DEPTNO
          7566 JONES      MANAGER         7839 02-APR-81       2975       1000         20
          7902 FORD       ANALYST         7566 03-DEC-81       3000                    20
          7839 KING       PRESIDENT            17-NOV-81       5000                    10
          7698 BLAKE      MANAGER         7839 01-MAY-81       2850                    30
          7782 CLARK      MANAGER         7839 09-JUN-81       2450                    10
          7369 SMITH      CLERK           7902 17-DEC-80        800                    20
          7499 ALLEN      SALESMAN        7698 20-FEB-81       1600        300         30
          7521 WARD       SALESMAN        7698 22-FEB-81       1250        500         30
          7654 MARTIN     SALESMAN        7698 28-SEP-81       1250       1400         30
          7788 SCOTT      ANALYST         7566 09-DEC-82       3000                    20
          7844 TURNER     SALESMAN        7698 08-SEP-81       1500          0         30
          7876 ADAMS      CLERK           7788 12-JAN-83       1100                    20
          7900 JAMES      CLERK           7698 03-DEC-81        950                    30
          7934 MILLER     CLERK           7782 23-JAN-82       1300                    10
    14 rows selected.
    SQL> -- the above example displays the output on the screen
    SQL> -- now we want to turn it off by using the SET TERMOUT option
    SQL> SQL> set termout off;
    SQL> @r:\sample_spool.sql;
    SQL>
    after executing the script sample_spool.sql it does not display output from the screen which
    we want to avoid the buffer overflow error. and still produce the spool file:
         EMPNO ENAME      JOB              MGR HIREDATE         SAL       COMM     DEPTNO                                  
          7566 JONES      MANAGER         7839 02-APR-81       2975       1000         20                                  
          7902 FORD       ANALYST         7566 03-DEC-81       3000                    20                                  
          7839 KING       PRESIDENT            17-NOV-81       5000                    10                                  
          7698 BLAKE      MANAGER         7839 01-MAY-81       2850                    30                                  
          7782 CLARK      MANAGER         7839 09-JUN-81       2450                    10                                  
          7369 SMITH      CLERK           7902 17-DEC-80        800                    20                                  
          7499 ALLEN      SALESMAN        7698 20-FEB-81       1600        300         30                                  
          7521 WARD       SALESMAN        7698 22-FEB-81       1250        500         30                                  
          7654 MARTIN     SALESMAN        7698 28-SEP-81       1250       1400         30                                  
          7788 SCOTT      ANALYST         7566 09-DEC-82       3000                    20                                  
          7844 TURNER     SALESMAN        7698 08-SEP-81       1500          0         30                                  
          7876 ADAMS      CLERK           7788 12-JAN-83       1100                    20                                  
          7900 JAMES      CLERK           7698 03-DEC-81        950                    30                                  
          7934 MILLER     CLERK           7782 23-JAN-82       1300                    10                                  
    14 rows selected.

  • Short dump in SAP R/3: SQL statement buffer overflow?

    Hello,
    I hope someone can help us with the following problem:
    A short dump in SAP R/3 (DBIF_RSQL_INVALID_RSQL, CX_SY_OPEN_SQL_DB)
    occurred during a delta load, which worked fine for several month.
    The custom code crashes at a FETCH NEXT CURSOR statement.
    I assume, it might be a SQL statement buffer overflow in SAP R/3?
    The problem can be reproduced by RSA3, and is therefore not time-dependent.
    The problem did not occur before or on the quality assurance system.
    Cursor code:
          Read all entries since last transfer (delta mechanism)
            OPEN CURSOR WITH HOLD s_cursor FOR
              SELECT * FROM ekko
                WHERE ebeln IN t_selopt_ekko.
    t_selopt_ekko has up to 60.000 data sets, which worked fine in the past.
    It is very likely that the amount of data during the first crash did not exceed this.
    SQL-Trace of RSA3 call:
    It seems that 25150 data set can be processed via fetch before the short dump occurs
    After that object SNAP is written:
    "...DBIF_RSQL_INVALID_RSQL...dynpen00 + 0xab0 at dymain.c:1645 dw.sapP82_D82
    Thdyn...Report für den Extraktoraufruf...I_T_FIELDS...Table IT_43[16x60]TH058FUNCTION=
    RSA3_GET_DATA_SIMPLEDATA=S_S_IF_SIMPLE-T_FIELDSTH100...shmRefCount  = 1...
    ...> 1st level extension part <...isUsed       = 1...isCtfyAble   = 1...> Shareable Table Header Data
    <...tabi         = Not allo......S_CURSORL...SAPLRSA3...LRSA3U06...SAPLRSA3...
    During dump creation the following occurs:
    "...SAPLSPIAGENTCW...CX_DYNAMIC_CHECK=...CRSFH...BALMSGHNDL...
    DBIF_RSQL_INVALID_RSQL...DBIF_RSQL_INVALID_RSQL...DB_ERR_RSQL_00013...
    INCL_ABAP_ERROR...DBIF_INCL_INTERNAL_ERROR...INCL_INTERNAL_ERROR...
    GENERAL_EXC_WITHOUT_RAISING...INCL_SEND_TO_ABAP...INCL_SEARCH_HINTS...
    INCL_SEND_TO_SAP...GENERAL_EXC_WITHOUT_RAISING...GENERAL_ENVIRONMENT...
    GENERAL_TRANSACTION...GENERAL_INFO...GENERAL_INFO_INTERNAL...
    DBIF_INCL_INTERNAL_CALL_CODE..."
    Basis says, that the Oracle data base works fine. The problem seems to be a SAP R/3 buffer.
    Does anyone had a similar problem or knows where such a buffer might be or how it can be enlarged?
    Best regards
    Thomas
    P.S.
    Found a thread that contains part of the dump message "dynpen00 + 0xab0 at dymain.c:1645":
    Thread: dump giving by std prg contains -> seems not to be helpful
    Found a similar thread:
    Thread: Short dump in RSA3 --Z Data Source -> table space or somting else?
    Edited by: Thomas Köpp on Apr 1, 2009 11:39 AM

    Hi Thomas,
          Its due to different field length.
    Just check it out in code after FETCH NEXT CURSOR what internal table you have mention.
    that internal table shoul deffined by taking refrence of ekko, because your code is
    OPEN CURSOR WITH HOLD s_cursor FOR
    SELECT * FROM ekko
    WHERE ebeln IN t_selopt_ekko.
    hope you got solution.
    Regards,

Maybe you are looking for

  • Icons for both Logic 9.2.0. and 9.1.1.

    When I upgraded to Logic Pro 9.2.0., it created a new icon for 9.2.0., as opposed to updating the previous version of Logic. This left me with two Logic Pro icons. Now that I have upgraded to 9.1.1., my original Logic Pro is updated, and the Logic Pr

  • Problems setting "table reference" for TopLink relationships

    I'm trying to use TopLink to create Java objects over two tables that are linked in a many-to-many relationship. I followed the instructions on the 10g tutorial page (drag all three tables into a database diagram), then created a new field (of type C

  • "Logic has detected a possible conflict "" -- HELP!

    The full error message is, "Logic has detected a possible conflict between one or more third party MIDI or audio drivers. Be sure to install the latest drivers for all audio and MIDI equipment connected to your computer, and remove any older or unuse

  • I set up an autoreply but i cannot work out how to change the subject line to the one I want

    I set up an automatic reply but the subject line come up as re: and what the other person wrote. I want to change the subject line to a set one to all emails. How can I do that?

  • How to see who perform modifications on CUA parameters.-

    Hi All,          I hope this note find you well. Basically, what I need is to see who,when, etc perform several modifications on CUA Parameters. i.e : Tx SCUM --> Defaults Tab --> Logon Languaje --> Changed to "Proposal" If I go through Tx SALE/SCUM/