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
Similar Messages
-
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. -
class test
public static void main(String[]args)
System.out.println(1.20+4.90-4.90); System.out.println(1.20+4.90-4.90-1.20);
please run the following program
i have a similar problem with this buffer overflow.
i am doing a cshier program that perform the calculation i wrote in the test program,
note that my values are double.. what can i do to prevet this??E.D.-inc wrote:
class test
public static void main(String[]args)
System.out.println(1.20+4.90-4.90); System.out.println(1.20+4.90-4.90-1.20);
please run the following program
i have a similar problem with this buffer overflow.
i am doing a cshier program that perform the calculation i wrote in the test program,
note that my values are double.. what can i do to prevet this??As jverd mentioned, this isn't a buffer overflow. You need to format your answers.
public class Fubar1
public static void main(String[] args)
double d1 = 1.20 + 4.90 - 4.90;
double d2 = 1.20 + 4.90 - 4.90 - 1.20;
System.out.printf("%3.2f\n", d1);
System.out.printf("%3.2f\n", d2);
} -
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. -
Iam doing Data acquisition using NI-PXI 4472 and buffered period Measurement using NI-PXI 6602 simultaneously,my program gives an buffer overflow error
murali_vml,
There are two common buffer overflow and overwrite errors.
Overflow error -10845 occurs when the NI-DAQ driver cannot read data from the DAQ device's FIFO buffer fast enough to keep up with the acquired data as it flows to the buffer (i.e., the FIFO buffer overflows before all the original data can be read from it). This is usually due to limitations of your computer system, most commonly the result of slow processor speeds (< 200 MHz) in conjunction with PCMCIA DAQ boards, which have small FIFO buffers (e.g., the DAQCard-500). Sometimes using a DAQCard with a larger FIFO can solve the problem, but a better solution is to lower the acquisition rate or move to a faster system. Another cause of the -10845 error could be due to an interrupt-driven
acquisition. For example, PCMCIA bus does not support Direct Memory Access (DMA). If the system is tied up processing another interrupt (like performing a screen refresh or responding to a mouse movement) when it is time to move data from the board, then that data may get overwritten.
Overwrite error -10846 occurs when the data in the software buffer that you created for an analog input operation gets overwritten by new data before you can retrieve the existing data from the buffer. This problem can be solved by adjusting the parameters of your data acquisition, such as the lowering the scan rate, increasing the buffer size, and/or increasing the number of scans to read from the buffer on each buffer read. Additionally, performing less processing in the loop can help avoid the -10846 error.
See the NI-DAQ Function Reference Manual for a listing of all NI-DAQ error codes.
Have a great day. -
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 AMHi 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, -
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 quitDelete 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) -
Hi There,
I have a code to read the text file in jsp, the problem i am facing is of buffer overflow as the text file contains more than 2000 records and when i upload data to database it throws exception of buffer overflow, any help will be appriciated.
Thanks.P.S. A JSP should, obviously, do nothing but produce HTML, which is what it is meant for after all. Any other actions should, of course, be handled be external classes and uploads and other "like" actions should be done by servlets, again, of course. You do know this, right? You do know that scriptlets in a JSP are 1) just plain wrong, and 2) a maintainance nightmare, right? (among other things that are just plain wrong with this "plan".
-
2 Microphones. Buffer overflow.
I'm getting a buffer overflow error while acquiring data from 2 microphones.
I'm sampling at 22050 S/s with 5000 S/ch.
Within a second I get the error,
"Error 4823 occurred at Sound Input Read (DBL).vi->New.vi
Possible reason(s):
LabVIEW: (Hex 0x12D7) You cannot perform this operation without an active task. Ensure that a task is active and try again. An input task might stop running if the input buffer overflows. Overflow occurs when the data is not read fast enough."
Is there something I can do to fix this? I tried playing with the S/ch and S/s values but couldn't fix the problem. I would think this will become a bigger problem when I try more than 2 microphones. I searched online for a solution to this problem but couldn't find anything that worked for me.
Thanks very much. Examples or any suggestions are greatly appreciated.
Message Edited by ap8888 on 03-16-2010 12:02 AM
Solved!
Go to Solution.
Attachments:
New.vi 118 KBSee this
-
ADL buffer overflow crash when loading external module
Hi,
ADL version: 1.5.3
Flex SDK version: 3.5
Flash Builder version: 4.5
OS: Vista 64bit
I have a project that uses various external Flex modules at runtime.
With Flash Builder 4, the Debug Launcher runs fine when compiling on a Windows XP box. The app behaves correctly, no crash.
When debugging the same project on a Vista 64bit using Flash Builder 4.5, all seems fine until I load an external module. At that point, the adl.exe process crashes with the following report:
Problem signature:
Problem Event Name: BEX
Application Name: adl.exe
Application Version: 1.5.3.9120
Application Timestamp: 4b06f734
Fault Module Name: Adobe AIR.dll
Fault Module Version: 2.6.0.19120
Fault Module Timestamp: 4d7a8030
Exception Offset: 005ef27a
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 4105
Additional Information 1: 6495
Additional Information 2: 5d54e5c02589ce8bdd8a34774c75928b
Additional Information 3: 819d
Additional Information 4: edcc4aab88b7f32eab72edc2ecc4f717
BEX is a buffer overflow.
Does anyone have any clue why the ADL would crash with such a configuration.
Thank you,
MartinHi
I have the same problem.
Flex version 4.6
AIR: 3.1
Fb: 4.5
code to reproduce:
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
width="1200" height="800" minWidth="1200" minHeight="800"
applicationComplete="applicationConpleteHandler(event)"
resizing="windowedapplication1_resizingHandler(event)">
<fx:Declarations>
<!-- Place non-visual elements (e.g., services, value objects) here -->
</fx:Declarations>
<fx:Script>
<![CDATA[
import mx.controls.Alert;
import mx.events.FlexEvent;
var loader:Loader;
protected function applicationConpleteHandler(event:FlexEvent):void
loader = new Loader;
loader.width = this.stage.width;
loader.height = this.stage.height;
stage.addChild(loader);
var f:File = new File("C:/Users/Мурзик/AppData/Roaming/com.oreilly.WhiteSpace/Local Store/sandler/sandler_0.2.37.swf");
var urlReq:URLRequest = new URLRequest("C:/Users/username/AppData/Roaming/flash_file.swf");
loader.load(urlReq);
protected function windowedapplication1_resizingHandler(event:NativeWindowBoundsEvent):void
//loader.width = this.stage.width;
//loader.height = this.stage.height;
]]>
</fx:Script>
</s:WindowedApplication>
Is there any solution? -
Hi.
I have a HIL system where I have a Simulink model (dll) running a 1kHz on an RT system with VeriStand. Some outputs from the model is mapped directly to CAN signals. Theese CAN messages are sent periodically typically at 10, 50 and 100Hz.
Looking from the outside, i.e. listening on the CAN interface the messages seems to be sent correctly. However I get a lot of errors shown in the console viewer, see below. The errorcode is -1074388984 which is CAN buffer overflow.
When I disable the the messages which contains parameters mapped from the model the error code reporting stops.
It seems that a CAN message is stored in the transmit buffer after every iteration of the model i.e. every 1ms, then causing buffer overflow.
Is there a setting somewhere to avoid theese error messages or is it a bug? I have no problem with this the I was using the beta.
Regards
RogerHi.
1. Yes, I have used NI Dynamic Test and then later the VeriStand beta. However, my client PC has been reinstalled (Windows XP) meaning that I have a "clean" installation of the released Veristand software. On the RT target I have uninstalled all NI-software and then installed the new softare according to the VeriStand installation instructions.
2. The version of NI-CAN is 2.6.3 (f2)
3. It is NI-CAN 8461 board that are used.
4. My configuration is PXI chassie 1042Q, 8106 controller, FPGA board 7813R ans CAN 8461. I have a custom device configured that uses the FPGA board
5. I have created a blank configuration, added my model and mapped only one signal to the model and this results in the same problem. If I stop the model the error reporting stops. If I remove the mapping the error reporting stops.
/Roger -
Hello,
I modified the very simple example "Cont-Ext-Buff-Cnt" to use 20MHz source clock and connected the signal of my encoder to gate. I can read fine with slow RPM, 1000 or lower. But I do get Overflow problem (-200141) for RPM > 1000. I am using 16 MIO E series card. I changed the BufferSize, Rate, # of samples, but still had the same problem over 1000 RPM. I am using Visual C++ 2005/NIDAQmx8.5/Vista. My processor speed is very good. Here is a snippet of the code I am using. Could anyone help me with this issue, or had a similar situation?
DAQmxErrChk (DAQmxCreateTask("",&taskHandle));
DAQmxErrChk (DAQmxCreateCICountEdgesChan(taskHandle,"Dev1/Ctr0","",DAQmx_Val_Rising,0,DAQmx_Val_CountUp));
DAQmxErrChk (DAQmxSetCICountEdgesTerm(taskHandle,"Dev1/Ctr0","/Dev1/20MHzTimebase"));
DAQmxErrChk (DAQmxCfgSampClkTiming(taskHandle,"/Dev1/PFI7",200000,DAQmx_Val_Falling,DAQmx_Val_ContSamps,3600));
DAQmxErrChk (DAQmxStartTask(taskHandle));
while(i < 100) { // # of iterations
i++;
DAQmxErrChk (DAQmxReadCounterU32(taskHandle,1800,TimeOut,Buffer,3600,&ReadOnTimeCntr,NULL));
printf("\rTime=%d at loop=%d",ReadOnTimeCntr,i);
fflush(stdout);Hello Neal,
Thank for the reply, and No, the name is not a comment about NI.
I tried your suggestions and still couldn't get it to work. I think the error is Buffer overflow and here what it says: " DAQmx Error: Measurements: Data was overwritten before it could be read by the system.
If Data Transfer Mechanism is Interrupts, try using DMA. Otherwise, divide the input signal before taking the measurement.Task Name: _unnamedTask<0> Status Code: -200141". I think the "E" card uses DMA automatically, and I don't like to divide the signal of the encoder, as I know it worked before using traditional drivers. Here is the code I am using, this code fails when the RPM of the encoder exceeds about 1300 RPM or so (360 Samps/ Revolution). I don't know what I am missing as I would think this example would be very trivial.
int main(void)
int error=0;
int i=0;
TaskHandle taskHandle=0;
int32 read;
uInt32 data[8000];
char errBuff[2048]={'\0'};
float64 Rate = 80000;
// DAQmx Configure Code
DAQmxErrChk (DAQmxCreateTask("",&taskHandle));
DAQmxErrChk (DAQmxCreateCICountEdgesChan(taskHandle,"Dev1/ctr0","",DAQmx_Val_Rising,0,DAQmx_Val_CountUp));
DAQmxErrChk (DAQmxSetCICountEdgesTerm(taskHandle, "Dev1/Ctr0", "/Dev1/20MHzTimebase") );
DAQmxErrChk (DAQmxCfgSampClkTiming(taskHandle,"/Dev1/PFI7",Rate,DAQmx_Val_Rising,DAQmx_Val_ContSamps,50000));
// DAQmx Start Code
DAQmxErrChk (DAQmxStartTask(taskHandle));
printf("Continuously reading. Press Ctrl+C to interrupt\n");
while( 1 ) {
// DAQmx Read Code
DAQmxErrChk (DAQmxReadCounterU32(taskHandle,8000,10.0,data,8000,&read,NULL));
printf("\rAcquired %d samples",read);
fflush(stdout); -
I have created executable file, tested it for several days on my laptop and send it to the customer together with hardware.
As soon as he received it he faced buffer overflow problem.
Is it possible to eliminate this poblem?
When this error appeares the part of the program that does acceleration analysis still workes but signal generation stopped.
Unfortunately I do not have this hardware so I have to modify the program wihou testing it.
What are the ways to avoid buffer overflow(one of them is probably just to use DAQmx configure input buffer but I do not know where to insert it and how configure it).
Attachments:
Generator-Accelerometer New.vi 636 KBHere is what I see is happening.
You are using DAQ assistant in the 2nd loop to acquire 1000 samples at 1000 Hz It is set for continuous samples. So that will take a second. Then the data is passed of to the other functions. I don't know how long they would take to run, but they are pretty substantial. (By the way, your write measurment file as no data going into it.) If it takes longer than a second, then the DAQ functions which have been continuing, will have the buffer overwritten and you will get the error.
You could ignore the error, but that also means you've lost data which may or may not be important.
It is better to pass the data off into a queue. Let another parallel loop do the number crunching and saving to file. Search the labview help and the discussion forums for producer/consumer design architecture for examples. With only the DAQ assistant in the loop, you will get all of the data. The only risk would be if the queue would grow without bounds in the event that each chunk of data still takes longer than a second to process.
Putting a wait statement in the top loop as well will help. Without a wait statement, a loop will run as fast as it possibly can. Since you are mainly reading a local variable and some controls such as the stop button, you probably don't need to run instantaneously. Even a small wait of a few milliseconds can help yield processor time to other loops.
In your top loop, you are recalculating the waveform and writing it to the analog output on every iteration. It would be better to put that code in a case statement that only executes in the event the values change. I believe with continuous samples, and if you allow that channel to regenerate its data, the analog output will run continuously without needing to update it every iteration.
Also, please move your front panel down and size it to fit closer to the front panel controls. For some reason your VI appears with the title bar off the top of the screen.
Message Edited by Ravens Fan on 04-08-2008 01:33 PM -
Data socket buffer overflow detection
Hello,
I plan to use data socket to access SharedVariables. I started with the example Buffering.vi from the Shared_Variable_Buffering.lvproj shipped with LabVIEW 2009 SP1 (DSC-Module).
This example leads to a read buffer overflow caused by the high speed write loop and low speed read loops. The interesting part is, that reading the SharedVariable values using a SharedVariable-Node delivers a warning for that buffer overflow situation. But, the DataSocket-Read doesn't deliver any warning or error and I didn't find a way to detect the overflow. Does someone know how to get this done?
Thanks for your help.
ThomasHello Maria,
thank you for your reply.
It took a while, but today I checked out the Variable Client - Server.lvproj example shipped with the newest LabVIEW. And I was surprised to find even another possibility to interact with Shared-Variables: the new VI's contained in the DataComunication/SharedVariables palette (used by the Variable Refnum API Client.vi in the example).
And with the DSC-Module, another possibility is available: the also new VI's contained in the DSC Module/Tags palette (try the DSC Tag API.lvproj example, but don't forget to manually deploy the libs before starting the VI's).
So, plenty of possibilities available. It will take some time to realize the advantages (or disadvantages) of each one, especially for the new VI's.
Let's see what possibilities we gain with LabVIEW 2010...
Regards,
Thomas
Maybe you are looking for
-
A simple question about wrong sorting with multiple sort columns in Excel 2010
Hi, everyone! I have encountered a problem that I don't know how to explain. So I post it here because I don't know if there is another more relevant forum... I have a data sheet with the students' scores for the course. All the data were generated
-
Logic Express and Garritan Personal Orchestra
Hi. Please can somebody explain (simply!) how to access Garritan sounds in Logic Express 8. Many Thanks Nick
-
Windows XP, SP3: 'Skype has encountered a problem ...
I have seen quite a few people have this issue on here, but despite countless forum searches and multiple uninstalls/re-installs, I have not been able to fix my problem. I have not had any issues will Skype on my other computer. But I have recently g
-
Can not download purchased music.
I purchased two songs with an itunes gift card. When I went to download them it did not work. As I can see from other posts I am not the only person with this problem, that makes me wonder. I do not like itunes taking money from me then not letting m
-
CK74 Batch Input performance issue
Hi SDNers I've created a Batch input (call transaction) in order to load additive costs for several materials/months. However, I realized that the performance is really poor. So I've been analyzing this issue and I found 314528 SAP note where it says