Insights, updates, and deep dives into cybersecurity, cloud technology, and AI innovation.
When entering new services, I was having this error, and I couldnât figure out why: Checking Table âserviceâ  ERROR: 10813âŠservice(number=XXXXXXX): Nextusagedate is â0000-00-00â (FIX MANUALLY) BillMax support promptly acknowledged that it is a bug that cause this behavior under rare circumstances. The solution is to run on the billmax database the following SQL: update service [âŠ]
Both our secure and unsecure email systems are able to handle text, rich text and html messages. It is up to you to set your email program (i.e. Mozilla Thunderbird or Outlook Express) to use HTML or RTF for formatting email. However, we recommend that you stick with text-only emails, as the graphics and other [âŠ]
If you need to make sure that data incoming from a data source is integer, you can use: if ( =~ m/^[d]*$/ ) { print âintegernâ; } More info is on SitePoint.
When developing queries and stored procedures, it is possible to lock up access to the database. This can happen most frequently when autocommit is off, and a transaction is left hanging in a window. If all else fails, the application that is causing the lockup can be identified and forced with: LIST APPLICATIONS; FORCE APPLICATION (<application [âŠ]
I found this info in the PostgreSQL archives. Here are 2 methods: Best method from Dan Lyke: Apache::DBI will pool across Perl programs, and you donât have to change anything in your scripts. Next best method from Gilles DAROLD: in your perl script use the following code use vars qw(); ||= DBI::connect(, , ); [âŠ]
Often programmers that havenât worked with patches before find it intimidating. Patches are actually very simple to deal with. Here is how. Creating Patches diff -u oldfile newfile > filename.patch or diff -urN /olddir /newdir > filename.patch or diff -urN -X excludes /olddir /newdir > filename.patch diff options: -u Output (default 2) lines of unified [âŠ]
When trying to LOAD table data where one of the rows are generated, DB2 9.1 and 9.5 on Linux and AIX will crash if the generated field uses a user defined function (fenced or unfenced). IBM is aware of the issue, and the following APARs exist to track the problem: V9.1 APAR is IZ48197 V9.5 [âŠ]
We have large amounts of data, and in development we have to often to bulk insert and updates by the millions. DB2 allows us to dramatically speed up these operations by allowing to not log them. The trick is to use: ALTER TABLE <table_name> NOT LOGGED INITIALLY However, one needs to be careful using this [âŠ]
To retrieve to list of tables in DB2, you need to use the system tables, and then a little bit of sed. Here is how it goes: db2 âSELECT tabschema || â.â || tabname FROM syscat.tablesâ | sed -e â/ //gâ You can redirect this into a file, and you may need to cut off [âŠ]