The Scheduler is a set of tasks that execute SQL statements at predefined times or as determined internally by the server. The SQL statements can either collect information or monitor and adjust the server.
Appropriate Content: Informix Documentation Team
Con etiquetas: server X
IngeHalilovic 060000MPB8 Etiquetas:  tasks administration scheduler database server informix automatic oat 1.067 Visitas
One of the great things about IBM® Informix® is how many tasks are done automatically. Many of the automatic tasks are done by the Scheduler.
Here's the documented definition of the Scheduler:
The Scheduler has been around in Informix for quite a while, but Informix development adds new tasks fairly frequently. And, of course, you can add your own tasks. Check out the blog posting from the IDS Experts on how to create your own Scheduler tasks.
To view all the Scheduler tasks, either query the ph_tasks table or look at them in the OpenAdmin Tool for Informix (OAT), on the Task Scheduler > Scheduler page.
Don't forget that you can customize existing tasks, even built-in ones. For example, you can change the threshold or when the task runs. See the The Scheduler topics in the information center for all your options.
IngeHalilovic 060000MPB8 Etiquetas:  connection manager oat transactions spl database server features xid timeseries high-availability genero fixpack cluster administration warehouse inout informix 1.509 Visitas
Here's a summary of the IBM® Informix® 11.70.xC6 new features:
· · Enhancements to the OpenAdmin Tool (OAT) for Informix
· · Support for the same XID for transactions on different databases
· · Coordinating transactions within a high-availability cluster
· · Easier failover configuration for Connection Managers in a high-availability cluster
· Application development
· · Enhanced support for OUT and INOUT parameters in SPL routines
· · Additional functions for spatial data
· · Return the default values of columns
· · SPL routines for application compatibility
· Time Series data
· · Load time series data faster through a virtual table
· Data warehousing
· · Refresh dimension-table data without reloading the whole data mart
The What's new in Informix topic has short descriptions of each of these features and links to more information.
Also, we've added some interesting links to the portal topics in the information center (those are the top-level nodes in the left-side navigation pane). We've split up SQL, client API, and Informix Genero® information into separate nodes to make it easier for you to find what you need.
IngeHalilovic 060000MPB8 Etiquetas:  assertion_failure database error server informix corruption 1.556 Visitas
Did you know that assertion failures are the number one reason for calls to Informix® support? When we in Informix documentation found that out, we decided to shed some light on assertion failures.
What is an assertion failure?
An assertion failure occurs when the database server cannot continue normal processing and must shut down.
What do I do when I get an assertion failure?
If your production server is currently down, contact IBM® Software Support immediately.
To correct an assertion failure:
Tune in next week for part 2 -- how do you prevent assertion failures from happening.
If you missed the Chat with the Labs last week, listen to the replay here: https://www.ibm.com/developerworks/wikis/display/ifmxchatwithlab/Home. Two IBM® Informix® support engineers, Ron Privitt and Sanjit Chakraborty, discuss the top 10 issues that generate support calls. You'll hear about the issues, how to solve and prevent them, and tips on what information to gather so that support can solve your problems quicker.
If you upgrade to either version 11.70xC3 or 11.50xC9 of IBM Informix, you can:
IngeHalilovic 060000MPB8 Etiquetas:  replication features server database oat memory gskit embeddability event_alarms informix 1.553 Visitas
IBM® Informix® 11.50.xC9 is the ninth release of 11.50, and yet, it has new features! Here's a summary:
The 59 new oninit return codes introduced in Informix® 11.70 describe exactly why the server didn't start. We also document what your next move should be.
For example, oninit return code 175 says: The database server failed to initialize the root dbspace. What you should do if you get this return code is to check the root dbspace related parameters in server configuration file (onconfig) to make sure that the path for the root dbspace is valid.
The oninit return codes are documented in the Administrator's Reference.