Release Bulletin

AMD Opteron 2.2 GHz or greater

Red Hat Linux 5.2 (AMD) for 64-bit systems

Sun Solaris 10 x64/x86 SunOS 5.10

UltraSPARC 1.2 GHz or greater

Sun Solaris 10 (SPARC) for 64-bit systems

SunOS 5.10

IBM AIX p6 4.7 GHz or greater

IBM AIX 6.1

If you manually truncate the RAP_JOB_HISTORY table and the spt_table Transfer table in ASE is not cleared at the same time, ASE can, as a result, end up with multiple entries in the spt_table Transfer table associated with the same ID. This results in RAP_JOB_HISTORY table entries with finish times that occur prior to their start times.

Workaround: To avoid such errors, do not manually truncate the RAP_JOB_HISTORY table. Instead, use the delete from command.

Locking is set as an option in the command while creating the table. To avoid deadlocking when running multiple interlink truncation rules, choose either datapages or datarows when locking the table. For example:

create table STOCK_TRADE (
INSTRUMENT_ID        SYB_ID                         not null
TRADE_DATE           SYB_DATE                       not null
TRADE_SEQ_NBR        SYB_COUNT                      not null
TRADING_SYMBOL       SYB_CODE_VAR                   null
TRADE_TIME           SYB_TIMESTAMP                  null
TRADE_PRICE          SYB_MONEY                      null
TRADE_SIZE           SYB_COUNT                      null
(constraint PK_STOCK_TRADE primary key nonclustered (INSTRUMENT_ID,TRADE_SEQ_NBR, TRADE_DATE)) lock datapages

When locking the table, choose either lock datapages or lock datarows.

Workaround: Sybase recommends that you do not change the operator administration status of the default administrative user rapadmin.

Workaround: By default, the value of the RAPCache server number of user connections parameter is set to 250. Increase this value if more connections are needed based on system activity.

Workaround: “Sample Queries� in the RAP - The Trading Edition Data Model and Queries contains an optional procedure that describes how to load additional sample data into the RAPStore STOCK_HISTORY table, as well as into the RAPStore STOCK_QUOTE and STOCK_TRADE tables.

You may see:

Initializing Wizard........
		Verifying JVM.4916 Killed
		Verifying JVM..5117 KilledInitializing: Command not found

No Java Runtime Environment (JRE) was found on this system.

Workaround: If you encounter this error, re-run the installer from the command line by appending -is:jvmtimer 30 to the installation command. For example, use:

setupSolaris.bin -is:jvmtimer 30

RAP users accessing the data transfer and data truncation functions may notice a memory leak while performing scheduled job processes. To avoid memory leaks, shut down the job scheduler process periodically. To restart the job scheduler process:

Workaround:

use sybmgmtdb
go
sp_sjobcontrol @name=NULL, @option="stop_js"
go
sp_sjobcontrol @name=NULL, @option="start_js"
go

A timeslice error may occur during heavy I/O contention while the data transfer utility is active.

Workaround:

Execute:

sp_configure 'cpu grace time', 1000
go

On Linux RHEL Update 3.0 and greater, Adaptive Server version 15.5 running on multiple engines requires the security feature Exec-Shield to be disabled. To disable Exec-Shield:

Workaround:

Add the following lines in /etc/sysctl.conf:

kernel.exec-shield = 0
kernel.exec-shield-randomize=0

To make the action take effect without rebooting, as SU, enter: /sbin/sysctl -p for the action to take effect.

If you have sufficient memory to hold the entire RAPCache database, use an in-memory database for your RAPCache. If you do not have enough memory, use a relaxed-durability database instead.

If there is not enough physical memory on the machine, you can improve overall load performance of large data sets by using raw devices, rather than file system devices. Writes are faster while using raw devices, as there is no double buffering as with file system devices. The initial load performance with a raw device may not be as good as with a file system device, but there is no performance drop over time, and the total load time is less than the load time with a file system device.

Workaround:

To use raw devices rather than file system devices, change the physname specification in the disk init commands to the names of raw devices. The disk init dsync parameter has no effect when initializing a raw device.

Sybase IQ running in Sybase RAP does not apply the default precision and scale when defining a message type.

Workaround:

create table QA_EUREX ( 
PRODUCT_ID    VARCHAR(4), 
YEAR          NUMERIC(4,0), 
MONTH         NUMERIC(2,0), 
DAY           NUMERIC(2,0), 
) 

create table QA_EUREX ( 
PRODUCT_ID    VARCHAR(4), 
YEAR          NUMERIC, 
MONTH         NUMERIC, 
DAY           NUMERIC, 
) 

Workaround:

To successfully run the migration script, first change the following paths:

• For lines 17,19, and 21 the filepath shows

  <RAP_DIR>/OpsConsole/RAPCache/SYBASE.sh

  Change this to:

  <RAP_DIR>/RAPCache/SYBASE.sh

• An error in the bcp command on line 22 shows

  bcp master.dbo.OPERATOR out <RAP_DIR>/OpsConsole/OpsConsole/OpsDB/rap_operator.csv -S$4 -U$2 -P$3 -c -t, -e<RAP_DIR>/OpsConsole/OpsConsole/OpsDB/rap_operator.err -J

  Change this to:

  bcp master.dbo.OPERATOR out <RAP_DIR>/OpsConsole/OpsDB/rap_operator.csv -S$4 -U$2 -P$3 -c -t, -e<RAP_DIR>/OpsConsole/OpsDB/rap_operator.err -J

• For lines 26,28, and 30 the filepath shows,

  <RAP_DIR>/OpsConsole/OpsConsole/OpsDBEngine/bin64/sa_config.sh

  Change this to:

  <RAP_DIR>/OpsConsole/OpsDBEngine/bin64/sa_config.sh

• An error on the dbisqlc command on line 33 shows

  <RAP_DIR>/OpsConsole/OpsConsole/OpsDB/rap_operator.csv

  Change this to:

  <RAP_DIR>/OpsConsole/OpsDB/rap_operator.csv

The Performance and Tuning Guide is a new guide that has been created to help fine tune RAP components.

The Users Guide has been renamed and is now called Data Model and Queries.

The New Features Summary gives a summary of the new updates, features, and configurations in RAP.

Sybase IQ 15.1 ESD #1

Adaptive Server Enterprise 15.5

PowerDesigner 15.1