Ingres are broadcasting live webinars for Ingres VectorWise, starting this week. The first is entitled ‘Welcome to Ingres VectorWise”

Join our Ingres System Engineers as they share a high-level overview of the Ingres VectorWise technology including a demonstration of the product. Find out more about this new feature and to understand how to increase the performance of your analytic workloads using Ingres VectorWise with your existing hardware.

Duration will be approximately 40 mins.

Presenter: Joel Brunger
Date: Friday, July 8, 2010
Time: 10am ET / 2pm GMT / 3pm BST / 4pm CET
Register – http://info.ingres.com/g/?BGGYOVT4OJ

Presenter: Mary Schulte
Date: Friday, July 8, 2010
Time: 4pm PT / 11pm GMT / 9 am EST (July 9)
Register – http://info.ingres.com/g/?PCGJ51KY29

Presenter: Stephane Padique (Presentation will be in French/En français)
Date: Vendredi, July 23, 2010
Time: 1pm GMT / 2pm BST / 3pm CET
Register – http://info.ingres.com/g/?UX1J8X7Y71

Related Posts

• IUA VectorWise Demo Video
• PECL ingres-2.2.2 released
• Simplifying an OpenAPI trace log

Related Posts

• Ingres VectorWise Webinars
• PECL ingres-2.2.2 released
• Simplifying an OpenAPI trace log

For some time the Ingres terminal monitor has had the, slightly cryptic (to me at least), flag “-history_recall”. This flag allows you to use the cursor keys within a terminal monitor session to scroll through previous queries and edit them in-line. Users of Ingres on Windows have been able to do this by default, without any special flags, by virtue of Microsoft Windows Console API. As of change 2911 this feature is now active by default on UNIX/Linux and should be part of Ingres 10.0 when it gets released.

Related Posts

• Ingres 10.0 – Escaping from the Ingres terminal monitor
• What BLOB tables do I have?
• Logging Ingres JDBC connections under tomcat

$ sql iidbdb
INGRES TERMINAL MONITOR Copyright 2010 Ingres Corporation
Ingres Linux Version II 10.0.0 (int.lnx/2863)NPTL login
Thu Apr 29 08:46:38 2010

continue
*

to:

$ sql iidbdb
INGRES TERMINAL MONITOR Copyright 2010 Ingres Corporation
Ingres Linux Version II 10.0.0 (int.lnx/2903)NPTL login
Thu Apr 29 09:16:40 2010
Enter \g to execute commands, "help help\g" for help, \q to quit

continue
*

No more ninja skills needed for executing a query or to escape from the terminal monitor.

Related Posts

• Ingres 10.0 – “sql -history_recall” now enabled by default
• What BLOB tables do I have?
• Logging Ingres JDBC connections under tomcat

grep -v "IIapi_wait\|Dispatch" api.log

Turning this into:

!IIapi_initAPI: initializing API.
!IIapi_initialize: INGRES API initialized, envHndl = 090F9308
!IIapi_initialize: startup API
!IIapi_initialize: version = 6
!IIapi_initialize: INGRES API initialized, envHndl = 09078018
!IIapi_connect: connect to DBMS Server
!IIapi_connect: envHndl = 09078018, connHndl = 00000000, tranHndl= 00000000
!IIapi_connect: target = @server,tcp_ip,ii[user:secret]::dbname
!IIapi_thread(-1226205472): allocated local storage 091A5E78
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_setEnvParam: set environment parameter
!IIapi_setEnvParam: envHndl = 09078018
!IIapi_setEnvParam: paramID = 24.
!IIapi_autocommit: set autocommit state
!IIapi_autocommit: connHndl = 091A5960, tranHndl = 00000000
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_query: starting a query
!IIapi_query: connHndl = 091A5960, tranHndl = 091A69B8, queryType = 0
!IIapi_query: queryText = set session with description='hello'
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_close: closing a query
!IIapi_close: stmtHndl = 091A8070
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_query: starting a query
!IIapi_query: connHndl = 091A5960, tranHndl = 091A69B8, queryType = 0
!IIapi_query: queryText = set lockmode session where readlock=nolock
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_close: closing a query
!IIapi_close: stmtHndl = 091A6580
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_cancel: cancelling a query
!IIapi_cancel: invalid handle
!IIapi_appCallback: request completed, status = INVALID_HANDLE
!IIapi_close: closing a query
!IIapi_close: invalid statement handle
!IIapi_appCallback: request completed, status = INVALID_HANDLE
!IIapi_autocommit: set autocommit state
!IIapi_autocommit: connHndl = 091A5960, tranHndl = 091A69B8
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_disconnect: disconnecting a connection
!IIapi_disconnect: connHndl = 091A5960
!IIapi_appCallback: request completed, status = SUCCESS
!IIapi_releaseEnv: Release Environment
!IIapi_releaseEnv: envHndl = 09078018
!IIapi_terminate: shutdown API
!IIapi_releaseEnv: Release Environment
!IIapi_releaseEnv: envHndl = 090F9308
!IIapi_terminate: shutdown API
!IIapi_termAPI: shutting down API completely.
!IIapi_termAPI: API shutdown.

A lot simpler to read – Now I can see that a bad statement handle has been passed to IIapi_cancel() and IIapi_close(). Now I know what the problem is it’s time to find where the statement handle is coming from.

[1] It should be noted that you cannot always discount IIapi_wait() calls. A number of years ago I hit a weird timing issue due to a missing IIapi_wait() call.

Related Posts

• Ingres VectorWise Webinars
• IUA VectorWise Demo Video
• PECL ingres-2.2.2 released

Getting web applications to connect to Ingres via Apache on UNIX/Linux can be quite fiddly. Here is a simple guide on the setup steps needed to allow the Ingres PHP, Python and Ruby drivers to work with Apache on RedHat Enterprise Linux, CentOS and Fedora Linux. I’ve also published articles on doing the same for Debian/Ubunutu and Novell SLES/OpenSUSE in the Ingres Community Wiki.

Pre-requisites

It is assumed that you have the following installed:

• Ingres 2006 or newer ( Ingres >= 9.0.4 )
• RedHat Enterprise Linux 5.4, CentOS 5.4 and Fedora Linux 11
  • These steps might apply to earlier releases as well
• Apache 2.2.8
  • The steps here apply to other releases of Apache from 1.3 onwards
  • mod_env – An Apache module which modifies the environment which is passed to CGI scripts and SSI pages

Disabling SELinux

As of writing this Ingres and SELinux do not interact very well. To use Ingres on an SELinux enabled system, SELinux needs to be placed in permissive or disabled modes. To determine the current state of SELinux run the following:

sestatus

sample output:

$ sudo /usr/sbin/sestatus
SELinux status:                 disabled

If the status is enforcing then SELinux must be disabled using the command:

setenforce 0
# or to disable SELinux but log exceptions to policy to /var/log/secure
setenforce Permissive

This will only disable SELinux until the next reboot of the server. To make the change permanent edit /etc/sysconfig/selinux, changing SELINUX to disabled or permissive.

Enabling Ingres for Apache

Any user that connects to Ingres must be a known (defined) user. Specifically a user account must be created within Ingres using CREATE USER .... In the case of web applications served by Apache, Tomcat or whatever, the server process owner is the user that Ingres will initially see. To determine the process owner for Apache execute the following:

ps -fe | grep httpd | grep -v grep

On my system I get the following:

[grant@uksl-grant-rhel64 ~]$ ps -fe | grep httpd | grep -v grep
root      3331     1  0 Apr08 ?        00:00:02 /usr/sbin/httpd
apache   23356  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23357  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23358  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23359  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23360  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23361  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23362  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd
apache   23363  3331  0 Apr11 ?        00:00:00 /usr/sbin/httpd

Which shows two user accounts for Apache. The root account can be ignored since it is a monitor/control process that starts up and shuts down servers as required. The processes run under the apache account will be used to connect to Ingres.

To add apache to Ingres run the following, as the ingres administrator:

sql iidbdb <<EOSQL
create user apache\g
commit\g
\q
EOSQL

You should see something similar to:

ingres@esva-suse:~> sql iidbdb <<EOSQL
> create user apache\g
> commit\g
> \q
> EOSQL
INGRES TERMINAL MONITOR Copyright 2008 Ingres Corporation
Ingres Linux Version II 9.2.0 (a64.lnx/143)NPTL login
Tue Apr 13 23:33:18 2010

continue
* Executing . . .

continue
* Executing . . .

continue
* Ingres Version II 9.2.0 (a64.lnx/143)NPTL logout
Tue Apr 13 23:33:18 2010

Now the Ingres DBMS is setup for the Apache web server.

Enabling Apache for Ingres

1. Edit, (as root), /etc/sysconfig/httpd to include the following:

    II_SYSTEM=/opt/Ingres/IngresII
    LD_LIBRARY_PATH=/opt/Ingres/IngresII/ingres/lib:/opt/Ingres/IngresII/ingres/lib/lp32
    ODBCSYSINI=/opt/Ingres/IngresII/ingres/files
    export II_SYSTEM LD_LIBRARY_PATH ODBCSYSINI

   Note – ODBCSYSINI is only needed for the Python driver or applications based on ODBC

2. Create a new config file (as root), /etc/httpd/conf.d/ingres.conf, adding the following:

PassEnv II_SYSTEM LD_LIBRARY_PATH ODBCSYSINI

3. Restart apache (as root):

   service httpd restart

Verifying the setup

To see that the environment variables are visible the following code snippets can be executed through Apache through PHP and mod_python.

PHP

• Code:

  < ?php
    echo "II_SYSTEM is :" .$_SERVER["II_SYSTEM"] . "<br/>\n";
    echo "LD_LIBRARY_PATH is :" .$_SERVER["LD_LIBRARY_PATH"] . "<br />\n";
  ?>

• Sample Output:

  II_SYSTEM is :/opt/Ingres/IngresII
  LD_LIBRARY_PATH is :/opt/Ingres/IngresII/ingres/lib:/opt/Ingres/IngresII/ingres/lib/lp32
  

Python

• Code, save as python_env.py:

from mod_python import apache

def environment(req):
    req.content_type = "text/html"
    req.add_common_vars()
    env_vars = req.subprocess_env.copy()

    req.write('< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">')
    req.write('<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">')
    req.write('<head><title>mod_python.publisher</title></head>')
    req.write('<body>')
    req.write('<h2>Environment Variables</h2>')
    req.write('<table border="1">')
    req.write('<tr><td>%s</td><td>%s</td></tr>' % ("II_SYSTEM", env_vars['II_SYSTEM']))
    req.write('<tr><td>%s</td><td>%s</td></tr>' % ("LD_LIBRARY_PATH", env_vars['LD_LIBRARY_PATH']))
    req.write('</table>')
    req.write('</body>')
    req.write('</html>')

• Ouput from http://localhost/env.py/environment:

   Environment Variables
   II_SYSTEM	/opt/Ingres/II
   LD_LIBRARY_PATH	/lib:/usr/lib:/usr/local/lib:/opt/Ingres/II/ingres/lib:/opt/Ingres/II/ingres/lib/lp32
  

If you have any comments feel free to post them below.

Updated Apr 14, 2010 9:50 to include SELinux information

Related Posts

• Ingres VectorWise Webinars
• IUA VectorWise Demo Video
• PECL ingres-2.2.2 released

Related Posts

• Ingres VectorWise Webinars
• IUA VectorWise Demo Video
• PECL ingres-2.2.2 released

select r1.relid as base_table,
       c.attname as column_name,
       r2.relid as extend_table
from iirelation r1,iirelation r2,iiattribute c,iiextended_relation e
where r1.reltid=e.etab_base and r2.reltid=e.etab_extension
  and r1.reltid=c.attrelid
  and c.attid=e.etab_attid
  and r1.reltidx=0
  and c.attrelidx=0
order by base_table,column_name

Running this against my demodb database I get the following:

┌────────────────────────────────┬────────────────────────────────┬────────────────────────────────┐
│base_table                      │column_name                     │extend_table                    │
├────────────────────────────────┼────────────────────────────────┼────────────────────────────────┤
│nclob                           │ntext                           │iietab_367_368                  │
│nclob2                          │ntext                           │iietab_369_36a                  │
│nclob2                          │ntext2                          │iietab_369_36b                  │
│nclob3                          │ntext                           │iietab_3c0_3c1                  │
│user_profile                    │up_image                        │iietab_f5_f6                    │
└────────────────────────────────┴────────────────────────────────┴────────────────────────────────┘
(5 rows)

Extending the above query we can also determine the size of each iietab_xx_yy table:

select r1.relid as base_table,
       c.attname as column_name,
       r2.relid as extend_table,
	   t.allocated_pages * float4(t.table_pagesize) / 1024 / 1024
       as megabytes
from iirelation r1, iirelation r2,
     iiattribute c, iiextended_relation e,
     iitables t
where r1.reltid=e.etab_base
  and r2.reltid=e.etab_extension
  and r1.reltid=c.attrelid
  and c.attid=e.etab_attid
  and r1.reltidx=0
  and c.attrelidx=0
  and t.table_reltid = e.etab_extension
  order by megabytes desc;

For example:

┌────────────────────────────────┬────────────────────────────────┬────────────────────────────────┬───────────┐
│base_table                      │column_name                     │extend_table                    │megabytes  │
├────────────────────────────────┼────────────────────────────────┼────────────────────────────────┼───────────┤
│nclob2                          │ntext2                          │iietab_369_36b                  │      1.258│
│nclob2                          │ntext                           │iietab_369_36a                  │      0.258│
│nclob                           │ntext                           │iietab_367_368                  │      0.258│
│nclob3                          │ntext                           │iietab_3c0_3c1                  │      0.258│
│user_profile                    │up_image                        │iietab_f5_f6                    │      0.258│
└────────────────────────────────┴────────────────────────────────┴────────────────────────────────┴───────────┘

Useful if you want to know how much space your BLOB/CLOB data is taking up. Thanks to Kristoff, Paul and Gerhard for working out the SQL.

Updated to recognize Kristoff Picards’ contribution

Related Posts

• Logging Ingres JDBC connections under tomcat
• Ingres VectorWise Webinars
• IUA VectorWise Demo Video

UK Ingres User Association Conference 2010
10th June 2010, London
www.iua.org.uk

Outlines or abstracts for presentations on Ingres, OpenROAD, open source, or any other Ingres-related topics are welcome. The theme for this year’s event is “Open Source Innovation” so any papers relating to Ingres and Open Source tools and products would be particularly welcome.

The UK IUA Committee invites anyone working with Ingres or OpenROAD, or related technologies to submit ideas for papers to be presented at this year’s annual conference. The conference will take place on 10th June 2010 in Central London (venue to be confirmed).

A sell-out crowd attended the high quality presentations at last year’s event, and with your assistance and contribution, we aim to make this year’s IUA Conference an even bigger success.

Outlines and abstracts can be submitted in any reasonable format (e.g. Word, plain text, Powerpoint, PDF, etc.). Please submit your ideas for papers via email to Ray Collins (ray.collins@iua.org.uk) by Monday, 12 April 2010 for evaluation by the conference paper selection committee. Note that you need only send an outline or proposal at this stage. You do not need to provide a complete presentation to be considered.

Notification of whether your paper has been selected or rejected will be sent by Friday 14 April 2010.

Topics we are particularly interested in hearing about this year:

• VectorWise
• Hardware and software consolidation, and virtualization
• Applications developed with Open Source
• Migrations to Open Source
• Ingres Community Projects
• Open Source economics
• Management issues in Open Source
• Productivity Tools
• Security
• Improving Performance

If you have any questions regarding this year’s 2010 Conference, the committee members are happy to assist. Please send all questions and queries to info@iua.org.uk.

Thank you to all who have supported the IUA by presenting at our previous Meetings, Special Events and the Annual Conference in the past, and for your continued interest and support of the UK IUA.

Some random posts

Posted via email from Idle thoughts

Some random posts