pajama

• You can do onstat -u to get session ids then onstat -g ses <sessionid> to
  get threads. Finally do onstat -g ath to list threads and and look at the ones which have a status of running.
• You can see active threads with 'onstat -g act -r 2'. This will show you active
  threads every 2 seconds. If you will see same thread repeatedly, then you can
  use value of 'rstcb' column of previous output to catch session:
  
  onstat -u | grep value_of_rstcb
  
  Then you can get sql causing high CPU utilization with onstat -g ses session_id"
  

Optim versions for customers can be downloaded from your personally configured Passport Advantage ( PA ) download area. The names of the files, which will be saved on disk are crypt and do not contain any hint about the version in itself.

Sometimes it is necessary to find out which version of Optim is a such file, named like this:CZD0AEN.ZIP

In Optim versions before 8, there is an empty directory in the directory structure, after the downloaded compressed file was extracted. The name of this empty directory, starting with "Bld..." reflects the build number of the specific Optim version.

In a command line operation on Unix or Windows, the directory structure can be created with the command "ls -la" for Unix and Linux, or with the command "dir" for Windows.

• Example from Optim 7.3.1 for Linux:

• With this directory name, Bld3638, the build number can be used to find out the appropriate Optim version; in this example "3638" :

INTRODUCTION

This guide outlines the supported method of adding logical logs in a HDR pair in the IDS environment, where a new log is initially added to the primary and then replicated to the secondary server.

STEPS 

1. This step adds log(s) in a HDR pair environment. Use onparams" command to add the desired number of logs on the primary server, for example: 
   
   $ onparams -a -d logspace 
   
   
2. The onparams operation is automatically replicated on the secondary database server. 
   
   
3. The action of adding logs can be confirmed by checking the online.log messages and a logical log listing (by means of onstat -l" ). 
   The command onstat -l" will display the newly added log(s) with the flag 'A'. 
   The logs are immediately available for use. 
   
   
4. A level-0 archive of the rootdbs and the dbspace containing the newly added log(s) is recommended.

INTRODUCTION

You can change the data replication server type of an IBM® Informix® Dynamic Server (IDS) instance in an HDR pair from Primary to Secondary and Secondary to Primary. 


BEFORE YOU BEGIN

The steps below will only work when data replication has been started with DRAUTO set to 0 (manual), which is the default, in the $ONCONFIG file.

You will need to open two session windows, the first session to connect to the Primary server, and the second session to connect to the Secondary server. After you log in as user informix, set up your environment to administer the database server, you must also check to ensure the Primary server and Secondary server are up and operational.


STEPS

The following steps will show you how to manually change the current Primary server to a new Secondary server, and the current Secondary to a new Primary.

Check server status and message log after each command to ensure the server is in the correct state before the next step. Failing to do so can result in data replication pair out of synchronization and shall require re-establishing the pair from archive.


On the current Primary server

1. Run this command to check the database server status:

onstat -

The output must contain this:

-- on-Line (Prim) -- Up

Note: If it does not show the above then you must correct it before proceeding to the next steps.

2. Shut down the current Primary server, run the following command:

onmode -ky

onmode -d standard

DR: new type = standard
On-Line Mode

onmode -d primary <secondary dbserver name>*

   *<secondary dbserver name> is the former primary database server name.

DR: new type = primary, secondary server name = <secondary dbserver name>
DR: Trying to connect to secondary server = <secondary dbserver name>
DR: Cannot connect to secondary server
DR: Turned off on primary server

onstat -

 -- on-Line (Prim) -- Up

oninit -PHY

Recovery Mode

-- Fast Recovery -- Up

onmode -d secondary <primary dbserver name>*

  *<primary dbserver name>is the former Secondary database server name.

DR: new type = secondary, primary server name = <primary dbserver name>
DR: Trying to connect to primary server = <primary dbserver name>
DR: Cannot connect to primary server
DR: Turned off on secondary server

On-Line Mode
DR: Sending log <log number> (current), size <value> pages, <value> percent used
DR: Sending Logical Logs Completed
DR: Primary server operational

For a while, DBaccess was provided only on the server side, since it is designed as an interactive interface with Informix Dynamic Server. Beginning with CSDK 3.70.xC3, DBaccess became available on the client side. The DBaccess for client-side platforms is available only at the same bit level as the Server side product. For example, when the available Informix Dynamic Server version is 64 bit only, there is no equivalent 32 bit DBaccess client-side product in the CSDK product.

There is no CSDK with DBaccess on the following platforms:

The Smart Large Object file has a name in one of these formats:

For a BLOB value: blob#####.###
For a CLOB value: clob#####.###

예) 파일내용. 오프셋은 16진수로 표현한다

|100,200,/usr/apps/clob9ce7.318|

######.###
The digits of the unique hexadecimal smart-large-object identifier. Automatically assigned to the file when it is created.

start_offset,length,location_path

start_offset
The starting offset (bytes, in hexadecimal) of the smart large object value within the blob/clob file.

length 
The length (bytes, in hexadecimal) of the BLOB or CLOB value.

location_path
The full pathname to the location where the blob/clob file is stored. If a full path is not specified the current directory will be used.

Note: No blank spaces can appear between these values. 

The Optim trace shows:

ERRWERRH ERR_RetryMgr (0240) EXCP 09/27/2011 16:28:36 000062 000006E8 00005A4
Win32 Exception=C0000005 Desc=Access Violation
ERRWERRH ERR_RetryMgr (0000) ENVE 09/27/2011 16:28:36 000063 000006E8 000005A4
Exception:C0000005 (Access Violation) at 02DCC372
Exception occured on 09/27/2011 at 16:28:36
PN0CSS00 csscdep0.c CSSObjDepends(00783-0004C372)
Registers at Failure:
CS=0023 DS=002B ES=002B FS=0053 GS=002B SS=002B
EIP=02DCC372 EAX=40FE7C02 EBX=0412EF48 ECX=40FE7C02
EDX=00000002 EBP=062DD384 EDI=00000830 ESI=00C884A4
ESP=062DD240 FLG=00010202 PID=000006E8 TID=000005A4
Current Stack Len:142784 Attempt to Read at Address 40FE7C0A

**Snip**

CSSCDDL0 CSSGetDDLObject (1333) EXCP 09/27/2011 16:28:36 000064 000006E8 000005A4
ErrMsg: Error Exit)
RetCode: CSSERR_CREDDLERR(07080) Create DDL Object failed
AuxCode: ENVERR_EXCEPTION(01023) Operating System Exception
Token1: UpdDepLinkScan
Token2: Access Violation
Token4: Access Violation

Some of the extended objects that Optim attempts to Archive can produce this issue.

It is important to note that, while the process report returns information about the Server process, this can happen when running locally as well.

For further diagnostics, it may be beneficial to select each of the extended objects one at a time, and re-run the Archive, to pinpoint the failing element.

From the Archive Request:

1) Choose the Objects tab

2) Deselect all of the Extended Objects

3) Successfully re-run the archive

The onconfig parameters TAPESIZE and LTAPESIZE are used in connection with TAPEDEV and LTAPEDEV to determine the size for each tape or file to be used for an ontape backup. At times, the backup size requirement may exceed the size configured for an ontape backup. This is usually not a problem if you are standing by, ready to handle the situation. If you want the backup to fit into a single tape or file, you have to make sure your size estimate is reasonable.

The size needed for an Informix Server Backup using ontape is based on several internal factors. The most important considerations are: 

• when the last backup was done
• the page size used for each dbspace
• how much activity has been transacted since the last backup
• whether it is a level 0, 1, or 2 backup.

To determine backup size requirements, generate an 'onstat -d' listing, and examine the chunk column references for "Size" and "Free". Work with one group of page size at a time to determine a value (K):

1. Review the dbspaces with similar page size (2k, 4k, 8k, etc). Each collection of dbspaces with the same page size is a group (group-P). Add all the totals for (group-P) 'Size' and place it in 'N'.
2. Add all the totals for (group-P) 'Free' and place it in 'F'.
   • Ignore 'size' and 'free' for temp dbspace and sbspace chunks.
3. Subtract F from N (N-F).
   • This will provide the count of pages which are in use (M).
4. Multiply M times the page size (for group-P) to get the number of page units (K ) needed for storage:
   • M * P = K (kb).
5. Repeat steps 1-4 for other page sizes, and add all of the K values. The final result provides a maximum size estimate for the next backup

Console based installation is not supported by Infosphere Federation Server installer.

The installer supports silent install and GUI mode.

GUI mode requires xWINDOWS. 
GUI command execution:
./iisetup

The silent install mode requires a response file. A sample response file is found in following directory and can be modified to reflect customer environment: 
<Installer Media root>/samples 
Silent installer command execution:
./iisetup -options responsefile.rsp -silent