pajama

-244 Could not do a physical-order read to fetch next row.
-107 ISAM error: record is locked.

-245 Could not position within a file via an index.
-144 ISAM error: key value locked.

Row, page, or table is locked.

onstat -k will show you the locks

• The owner column of onstat -k has the same value as the onstat -u column address. The onstat -u output should help you identify the owner of the locks in onstat -k. The owner's username will be listed in the user column of onstat -u The onstat - u output also has a sessid column. You can use the sessid value to find out more about the session that holds the lock. Run onstat -g ses <sessid value>.
  
• The tblsnum column of onstat -k is the hexadecimal tablespace number ( part number, partnum ). You will use this value to identify the table or index that is locked. How to find a table name based on partnum

• Additional information regarding onstat -k found in the Information Center here, Monitoring Locks

• Set Lock Mode to wait;
  SET LOCK MODE statement syntax 
  
• Set Lock Mode to wait n;
  
  n = number of seconds to wait
  SET LOCK MODE statement syntax 
  
• Set row level locking and use BEGIN WORK statement.
  LOCK MODE Clause (How to set row level locking for a table) 
  
• Consider using 'Committed Read' isolation level and the use of USELASTCOMMITTED parameter in onCONFIG file. When using this isolation mode and USELASTCOMMITTED is set to 'committed read' in onCONFIG, the last committed version of the data will be returned avoiding lock contention. USELASTCOMMITTED only works with table that has row level locking. 
  USELASTCOMMITTED Configuration Parameter 
  
  Note: USELASTCOMMITTED is a new feature in IDS 11, and is not available in IDS 10 or lower. 
  
  

When installing a 32-bit IBM Informix Client SDK product on a 64-bit Windows machine, you may see a message stating that you cannot install becuase you are using a 64 bit machine.

The problem is due to the Windows redirection path not being included in your systems PATH environment variable setting.

Windows 64-bit machine

1. Open a Windows command window ('cmd')
2. run: "set PATH=C:\WINDOWS\SysWOW64\;%PATH%"
3. Run the setup.exe for IBM Informix Client SDK

"C:\windows\syswow64\odbcad32.exe" and look under the Drivers tab.

Using JDBC, we may get errors like -79784 (" Locale not supported.") or -908 ("Attempt to connect to database server NAME failed.") when trying to connect to a database using the following locale: ko_kr.cp_949

For example, the following connection:
jdbc:informix-sqli://myhost:ids_port/mydatabase:informixserver=myidsserver;user=mylogin;password=mypasswd;DB_LOCALE=ko_kr.cp_949;CLIENT_LOCALE=ko_kr.cp_949

might return error -79784 or -908 if used with JDK earlier than 1.6 and/or JDBC earlier than 3.50.JC8

When using JDBC, in order to be able to connect properly to a database using locale ko_kr.cp_949 you have to use JDK1.6 or later and JDBC 3.50.JC8 or later.

OAT is first bundled with CSDK in 3.70.xC4 fixpaks. This does not include the 64-bit CSDK 3.70.FC4 on Windows.

You can install the 32-bit OAT on a Windows 64-bit machine.

PROBLEM

Shadow passwords are not supported in either IBM® IDS versions 7.31 or 9.40. This operating system enhancement is not available until the release of HP-UX® 11i (11.11), and for purposes of backward compatibility IDS 7.31 and 9.40 are ported to earlier releases of HP-UX 11. 


SCOPE

The following products and operating systems are affected:

• Use Trusting Computing Based (TCB) as an alternative password shadowing scheme.
• Upgrade to IBM® Informix® Dynamic Server™ version 10

Q. How can I resolve various "unknown terminal" errors I receive when running dbaccess?

A. Set the environment variables TERM and TERMCAP to point to $INFORMIXDIR/etc/termcap.

Example:

For csh:
setenv TERM vt100
setenv TERMCAP $INFORMIXDIR/etc/termcap

For ksh :
export TERM=vt100
export TERMCAP=$INFORMIXDIR/etc/termcap

IDS can only allocate a maximum of 16,775,215 disk pages per table partition or fragment. It should also be noted that this is independent of the dbspace configured page size.

Also, IDS can only track approximately 200 extents (logical grouping of disk pages) per table partition or fragment. The most likely root cause will be that one or both these values have been realized.

As user informix, run oncheck -pt <database>:<table name >".

In the resulting output, examine the value for "Number of pages used" or "Number of pages allocated". If either one is equated to 16,775,215 then this is the most likely root cause of the problem. 

However, should these values not be close to 16,775,215 then it's likely that the table has already allocated a high number of smaller extents (logical grouping of data or index pages).
If so , then the value for "Number of extents" will be close to or greater than 200, (there is no 'hard' limit due to various architectural reasons).

Example output to oncheck -pt :

TBLspace Report for dbase:informix.customer

Physical Address 1:36878
Creation date 801 Page Locking
TBLspace use 4 bit bit-maps
Maximum row size 134
Number of special columns 0
Number of keys 0
Number of extents 186
Current serial value 10139
Current SERIAL8 value 1
Current BIGSERIAL value 1
Current REFID value 2
First extent size 8
Next extent size 16
Number of pages allocated 16775215
Number of pages used 16775215
Number of data pages 16775215
Number of rows 1118341
Partition partnum 1049005
Partition lockid 1049005

If the value for Number of pages used or allocated is at 16775215, then try one of the following recommendations:

Non Fragmented Tables:

1. If the indexes defined for the table are attached , drop and recreate the table's indexes as "detached" (in their own separate partitions).

Note: A CREATE INDEX statement that does not specify IN TABLE as its storage clause creates indexes that store their pages in separate partitions from the data pages by default.

2. Fragment the table using a Round Robin or an ｅxpression Based strategy. This will result in additional partitions being created in order to track the table internally.

If the value for Number of extents is close or exceeds 200, then :

Reorganize the table using a larger initial extent size to defeat a high number of smaller extents being allocated.