2. Highlight table accesstab right click -.Export ->ODBC Database -> Machine Data Source ->Sybase IQ Datasource -> OK
3. create table accesstab (col1 long integer, col2 text (255) in Microsoft Access and insert row
4. Highlight table accesstab right click -.Export ->ODBC Database -> Machine Data Source ->Sybase IQ Datasource -> OK
5. Verify export by login into SAP IQ database.
Purpose
The purpose of this document is to provide you with the steps to configure RLV on IQ 16 simplex server along with a simple example to see how the RLV feature works
Step 1: Configure RLV Memory
-iqrlvmem <max MB>
sa_server_option ‘rlv_memory_mb’,<max MB>
Step 2: Create RLV Dbspace
create dbspace rlvdbsp using file rlvfile1 ‘rlvfile1.iq’ size 1000 IQ RLV STORE
Step 3: Create/enable RLV table
create table <table-name> (<column definition>) {ENABLE|DISABLE} RLV STORE
e.g
create table rlvtab(col1 int, col2 char(10) ENABLE RLV STORE
To enable/disable RLV storage for a table
alter table <table-name> {ENABLE|DISABLE| RLV STORE}
e.g
alter table rlvtab ENABLE RLV STORE
alter table rlvtab DISABLE RLV STORE
Note: option BASE_TABLES_IN_RLV_STORE registers newly created tables in RLV store after this option is set to ON.
Step 4: Control Versioning
Snapshot_Versioning: Controlling Row-level or Table-level versioning on a connection by connection basis
Syntax:
Set [Temporary] Option Snapshot_Versioning =‘Table-level’|’Row-level’
- default is ‘Table-Level’
- DBA can restrict Snapshot_Versioning values
Set Option Allow_Snapshot_Versioning = ‘Any’ | ‘Table-Level’ | ‘Row-level’
Example of setting up an RLV table and seeing how it works:
This script creates the iqdemo database in the current directory: C:\dbs\16rlv
Continue <Y/N>? y
Setting up temporary files ...
Starting Server ...
Connecting to server via TCPIP ...
Using: uid=DBA;pwd=sql;eng=bld_demo_9577;dbn=utility_db;links=tcpip(host=vm-test;port=9577)
Creation completed.
Shutting down server ...
SQL Anywhere Stop
Server Utility Version 16.0.0.481
Volume in drive C has no label.
Volume Serial Number is B085-C0E8
Directory of C:\dbs\16rlv
09/24/2013 01:37 PM 662 iqdemo.cfg
09/24/2013 01:37 PM 3,874,816 iqdemo.db
09/24/2013 01:37 PM 104,857,600 iqdemo.iq
09/24/2013 01:37 PM 40,674 iqdemo.iqmsg
09/24/2013 01:37 PM 26,214,400 iqdemo.iqtmp
09/24/2013 01:36 PM 1,157 iqdemo.lmp
09/24/2013 01:37 PM 327,680 iqdemo.log
09/24/2013 01:37 PM 104,857,600 iqdemo_main.iq
8 File(s) 240,174,589 bytes
Demo database created successfully
2. Edit cfg file and add -iqrlvmem 2048
3. Start server
4. You can create rlv dbspace and table using SCC (SAP Control Center), but here is how to do it using dbisql. Run dbisql and execute
CREATE DBSPACE "rlvdbspace" USING FILE "rlvdbfile1" 'c:\dbs\16rlv\rlvdbfile1.iq' SIZE 1024 MB RESERVE 1 MB IQ RLV STORE;
5. Set some options that impact RLV Merge
SET OPTION PUBLIC.RV_AUTO_MERGE_EVAL_INTERVAL='1';
SET OPTION PUBLIC.RV_MERGE_TABLE_NUMROWS=10000;
SET OPTION PUBLIC.BASE_TABLES_IN_RLV_STORE='ON'
SET OPTION PUBLIC.Snapshot_Versioning = 'Row-level';
Note: RV_AUTO_MERGE_EVAL_INTERVAL & RV_MERGE_TABLE_NUMROWS are set at a low value to be able to see RLV feature working in a small test environment.
6. Create example table and stored procedure to load the table
create table rlvtest
(
col1 varchar(125) not null,
col2 int not null,
col3 varchar(1024),
create_time datetime default getdate(),
create_by varchar(20) default CURRENT USER,
mod_time datetime default getdate(),
modified_by varchar(20) default CURRENT USER,
primary key(col2)
)
ENABLE RLV STORE;
create procedure
p_load_rlvtest()
as
begin
declare @li_line_num int
select @li_line_num = 1
while (@li_line_num < 60000)
begin
insert into rlvtest (col1, col2, col3) values('Test data ' + convert(char(10), @li_line_num), @li_line_num,
'The information contained in this email is confidential and intended only for the addressee.
If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden' )
select @li_line_num= @li_line_num + 1
if ((@li_line_num % 10000) = 0)
begin
commit
end
end
select @li_line_num
end;
7. Run dbisql session and execute the following
call p_load_rlvtest()
8. Command to check the rlv merge history
select * from sysiqrlvmergehistory
9. What to look for in iqmsg
‘Current active row count’ will display how many rows have been inserted.
‘Mrg B’ – indicates the begin of the merge process
‘Mrg E’ – indicates the end of the merge process
You will see such entries in the iqmsg, but since I set merge_rows to 10000, the merge happens and row count is back to 0
I. 09/30 11:15:48. 0000000021 0000005656 Current active row count for table rlvtest is 10000
I. 09/30 11:15:48. 0000000021 0000005656 Current active row count for table rlvtest is 0
I. 09/30 11:15:48. 0000000021 Cmt 8120
I. 09/30 11:15:48. 0000000021 PostCmt 0
I. 09/30 11:15:48. 0000000021 Txn 8121 0 8121
I. 09/30 11:15:48. 0000000021 Cmt 8122
I. 09/30 11:15:48. 0000000021 PostCmt 0
I. 09/30 11:15:49. 0000000194 Txn 8123 0 8123
I. 09/30 11:15:49. 0000000194 Cmt 8124
I. 09/30 11:15:49. 0000000194 PostCmt 0
I. 09/30 11:15:49. 0000000195 Txn 8125 0 8125
I. 09/30 11:15:49. 0000000195 Cmt 8126
I. 09/30 11:15:49. 0000000195 PostCmt 0
I. 09/30 11:15:49. 0000000195 Txn 8127 0 8127
I. 09/30 11:15:49. 0000000195 Mrg B 788 NO
I. 09/30 11:15:49. 0000000195 Mrg D
I. 09/30 11:15:49. 0000000195 [20917]: Delete of 0 rows started for table:
I. 09/30 11:15:49. 0000000195 [20919]: Delete of 0 rows completed for table: rlvtest, 0 seconds.
I. 09/30 11:15:49. 0000000195 Mrg U
I. 09/30 11:15:49. 0000000195 Mrg I
I. 09/30 11:15:49. 0000000195 [20896]: Insert for 'rlvtest' completed in 0 seconds. 20000 rows inserted.
I. 09/30 11:15:50. 0000000195 Mrg E
I. 09/30 11:15:51. 0000000195 Cmt 8128
I. 09/30 11:15:51. 0000000195 PostCmt 0
Related Content
Recover RLV from failed recovery - http://scn.sap.com/docs/DOC-44821
RLV Memory Management and Monitoring - http://scn.sap.com/docs/DOC-50252
Resolving RLV Store Out of Memory Error - http://scn.sap.com/docs/DOC-45064
After migrating a simplex SAP IQ 15.2 ESD#2 database to SAP IQ 16.0 SP3 running on Sun Solaris 10 over a Sparc 64 machine, I encounter that some queries where returning zero rows or returning erroneous data; Also, some of the queries where making the database crash. To solve those problems I rebuild the indexes in the table.
After installing and configuring SAP IQ 16.0 SP3 I upgrade the database using follow statement:
ALTER DATABASE UPGRADE SYSTEM PROCEDURE AS DEFINER OFF
And, set the following options:
SET OPTION PUBLIC.FP_NBIT_IQ15_Compatibility = OFF
SET OPTION PUBLIC.CREATE_HG_WITH_EXACT_DISTINCTS = OFF
SET OPTION PUBLIC.REVERT_TO_V15_OPTIMIZER=OFF
Then, I performed consistency and allocation test
sp_iqcheckdb 'verify database'
sp_iqcheckdb 'allocation database'
Both DBCC retuned “No Errors Detected”.
And, I rebuild all the indexes of all the columns over 250 char long.
Then, while testing I encounter the errors described in the first paragraph.
So, to generate the statements to rebuild all the indexes on the table bellowing to the user DBA I wrote the following 2 scripts:
select 'sp_iqrebuildindex ''DBA.' + T.[table_name] + ''', ''index ' + I1.index_name + ' retier ''' + char(13) + 'go'
from sysidx I1, sysiqidx I2, systab T
where T.table_id = I1.table_id
and (I2.table_id=I1.table_id and I2.index_id = I1.index_id)
and T.creator = 1
and I2.index_type = 'HG'
select 'sp_iqrebuildindex ''DBA.' + T.[table_name] + ''', ''index ' + I1.index_name + '''' + char(13) + 'go'
from sysidx I1, sysiqidx I2, systab T
where T.table_id = I1.table_id
and (I2.table_id=I1.table_id and I2.index_id = I1.index_id)
and T.creator = 1
and I2.index_type <> 'HG'
And then, I just executed the generated scripts to rebuild all the indexes.
You can also modify these scripts to generate the statements to rebuild the indexes of any given table:
select 'sp_iqrebuildindex ''DBA.' + T.[table_name] + ''', ''index ' + I1.index_name + ' retier ''' + char(13) + 'go'
from sysidx I1, sysiqidx I2, systab T
where T.table_id = I1.table_id
and (I2.table_id=I1.table_id and I2.index_id = I1.index_id)
and T.[table_name] = 'myTable'
and T.creator = 1
and I2.index_type = 'HG'
Union
select 'sp_iqrebuildindex ''DBA.' + T.[table_name] + ''', ''index ' + I1.index_name + '''' + char(13) + 'go'
from sysidx I1, sysiqidx I2, systab T
where T.table_id = I1.table_id
and (I2.table_id=I1.table_id and I2.index_id = I1.index_id)
and T.[table_name] = 'myTable'
and T.creator = 1
and I2.index_type <> 'HG'
Or, you can use these scripts to build dynamic SQL that will rebuild all the indexes in the database.
This post has first been published on my personal blog at http://wp.me/p1Gouv-6N
1. Create the remote server entry in the interfaces file; sql.ini (Windows) or interfaces (UNIX).
[myIQServer]
master=TCP,myIQHost,4091
query=TCP,myIQHost,4091
2. Add the remote server
sp_addserver 'myIQServer', ASIQ, myIQHost:4091'
3. Add the external login (SAP IQ) to be used by the local user (ASE) when connecting the SAP IQ database
sp_addexternlogin myIQServer, myLocalUser, myIQUser, myIQPassword
4. Verify connectivity using passthrough
connect to myIQServer
select @@version
@@version
------------------------------------------------------------------------------
Sybase IQ/16.0.0.653/131122/P/sp03/Sun_Sparc/OS 5.10/64bit/2013-11-22 01:16:26
1 record(s) selected [Fetch MetaData: 0ms] [Fetch Data: 0ms]
[Executed: 12/03/2014 2:00:20 PM] [Execution: 2ms]
disconnect from myIQServer
This document has previously been published in my personal blog at ASE 15.7: Create a Remote Server to SAP IQ 16.0 | ARBIME
In environments where lot of researches query the database, it is necessary to allow the users to run queries that are resource and time intensive. Even if there are database options that automatically avoid runaway queries, we cannot be too restrictive in this kind of environments. This flexibility allows users to execute runway queries (queries that never end or that has execution time considerably longer than expected and, consume system resources). This document explains how to identify and kill a runway query.
This document were fist posted on my personal blog at SAP IQ: How to Kill Runaway Queries | ARBIME
Steps listed below can be used to export data from SAP HANA into SAP IQ.
1. Set environment variables
Edit $SYBASE/IQ-16_0/IQ-16_0.csh and set HANA_HOME, ODBCHOME and ODBCINI environment variables.
setenv HANA_HOME /hana/sap/hdbclient/libodbcHDB.so
setenv ODBCHOME /hana/rel16_iq_sp03/
setenv ODBCINI /hana/rel16_iq_sp03/odbc.ini
2. Add HANA and IQ entries in odbc.ini
[iq1603]
DRIVER=/hana/rel16_iq_sp03/IQ-16_0/lib64/libdbodbc16.so
EngineName=iq1603
CommLinks=tcpip(host=myhost;port=9286)
Userid=DBA
Password=sql
AutoStop=no
DatabaseName=iqdb
[SB1]
Driver=/hana/sap/hdbclient//libodbcHDB.so
ServerNode=myhost:30315
3. Source $SYBASE/IQ-16_0/IQ-16_0.csh and restart IQ server. IQ server has to be started with HANA_HOME and OBCINI environment
variables.
4. Create HANA remote server named SB1 on the machine "myhost" with listening on port 30315:
dbisql -c 'dsn=iq1603' -nogui
(DBA)> create server SB1 class 'hanaodbc' using 'dsn=SB1'
Execution time: 0.067 seconds
5. Create externlogin to map the local user named DBA to the user SYSTEM with the password 'Saphanasql1'
DBA)> create externlogin DBA to SB1 remote login SYSTEM identified by 'Saphanasql1'
Execution time: 2.111 seconds
6. Confirm connection to HANA instance SB1
(DBA)>sp_remote_tables SB1
(NULL)
_SYS_STATISTICS
HOST_ONE_DAY_FILE_COUNT
(NULL)
_SYS_STATISTICS
HOST_RECORD_LOCKS
(NULL)
_SYS_STATISTICS
STATISTICS_LAST_CHECKS
(1090 rows)
7. Create schema ,table on HANA instance SB1
(DBA)> forward to SB1
0 row(s) affected
Execution time: 0 seconds
(DBA)> create schema hanaiq
0 row(s) affected
Execution time: 0.23 seconds
(DBA)> create table hanaiq.t1(col1 int)
0 row(s) affected
Execution time: 1.321 seconds
8. insert row in to HANA table hanaiq.t1
(DBA)> insert into hanaiq.t1 values(1)
0 row(s) inserted
Execution time: 0.07 seconds
(DBA)> commit
Execution time: 0.031 seconds
(DBA)> select * from hanaiq.t1
COL1
-----------
1
(1 rows)
Execution time: 0.037 seconds
(DBA)> forward to
Execution time: 0.001 seconds
9. create a proxy table named TAB1 for the remote table hanaiq.t1 at the remote server SB1
(DBA)> create existing table DBA.TAB1 (COL1 int) at 'SB1.HANAIQ..T1'
Execution time: 0.441 seconds
(DBA)> select count(*) from DBA.TAB1
count()
-----------
1
(1 rows)
Execution time: 0.063 seconds
(DBA)>
Login Redirection feature in SAP IQ 16 allows load balancing by redirecting login connecting to overloaded node to less node in the same logical server. Login Redirection can be controlled by using login server policy options:
- LOGIN_REDIRECTION
- REDIRECTION_WAITERS_THRESHOLD
For information related to these options see:
Steps to setup Login Redirection:
In my setup, I have iq1602c, iq1602q1, iq1602q2, and iq1602q1 and iq1602q2 are members of logical server ls1
[sybase@myhost]$ dbisql -c 'dsn= iq1602c' -nogui
(DBA)> CREATE LOGICAL SERVER ls1 MEMBERSHIP (iq1602q1,iq1602q2);
Execution time: 0.062 seconds
(DBA)> alter ls policy root TEMP_DATA_IN_SHARED_TEMP=ON login_redirection = On dqp_enabled = 1 redirection_waiters_threshold = 5
Execution time: 0.106 seconds
[sybase@myhost]$ dbisql -c 'dsn= iq1602c' -nogui
(DBA)> alter login policy root add logical server ls1
Execution time: 0.059 seconds
we have iq1602q1 and iq1602q2 in logical server ls1. Now if we connect to Coordinator iq1602c, login will be redirected to either iq1602q1
or iq1602q2.
dbisql -c 'uid=DBA;pwd=sql;eng= iq1602c;LS=ls1;NODETYPE=WRITER' -nogui
(DBA)> select @@servername
@@servername
--------------------------------------------------------------------------------
iq1602q1
(1 rows)
Execution time: 0.043 seconds
Now for testing shutdown iq1602q1, connection will be redirected to iq1602q2
dbisql -c 'uid=DBA;pwd=sql;eng= iq1602c;LS=ls1;NODETYPE=WRITER' -nogui
(DBA)> select @@servername
@@servername
--------------------------------------------------------------------------------
iq1602q2
if connection redirection is enabled and login/connection will redirect connections when:
In Memory row-level feature is available in SAP IQ 16. This feature allows more than one user to update same table concurrenlty as long as they are adding or modifying different rows. You will need to configure IQ server with additional memory for RLV store ie. in addition to main cache, temp cache adn size of large memory pool, you will need need additional memory for RLV store.
RLV memory can be configured wtih startup switch -iqrlvmem (default 2G).
# iqdemo.cfg
# ------------------------------------------------------------
# Default startup parameters for the ASIQ demo database
# ------------------------------------------------------------
-n iq1602
-x tcpip{port=9447}
# The following parameters are also found in the configuration file
# /usr/sybase/rel16_iq_sp02/IQ-16_0/scripts/default.cfg. Any parameters not specified below
# and not in the start up parameter list, will be added by start_iq
# using default.cfg as a guide.
-c 512m
-gc 20
-gd all
-gl all
-gm 10
-gp 4096
-iqmc 2000
-iqtc 2000
-zr sql
-iqrlvmem 4096
sa_server_option SA system procedure can be used to increase RLV memory dynamically:
sa_server_option 'RLV_memory_mb', 8192
This will configure RLV store size to 8192MB
RLV memory usage depends on several factors:
Every single RLV enabled table will require an in-memory table to hold its data. The memory requirement of this RLV store will change during the life of the table while it is RLV enabled. The initial size of RLV store needed during first DML can be calculated approximately using following formula:
#COLS = #columns + 1 (pseudo column)
Base RLVstore (BRS) = ( Initial setup of the RLV store )
BRS ~= (#COLS) x 16MB
Fixed datatypes of a subfragment uses default 16MB to store data in the RLV store. Variable datatypes uses default 512KB and bit datatypes uses 128KB default size.
Example:
Number of Cores=4
Number of Columns=303
RLV memory can be approximately calculated using:
16mb*4*303=~19GN
for Singleton insert using only 1 core, RLV memory used:
16mb *1*303= ~4.8GB
Data is store in table fragment. Each table fragments is further subdivided into subfragments. Multiple table versions of the table fragments may be required to handle multiple transactions. Each table version will have the RLV memory size requirement of at least equal to this BRS(Base RLV Store). Multiple transactions will create multiple table store versions that need to be stored in memory simultaneously. Multiple table versions can quickly increase the memory requirement of the RLV enabled table. Old transactions can hold onto old references to the in-memory store whch will also consume memory.
RLV Out Of Memory Errors:
Exception Thrown from rvlib/rv_TabStoren.cxx:178, Err#5, tid 3227 origtid 3227
O/S Err#: 0,ErrID: 15008 (rv_PersistenceException); SQLCode: -1013129, SQLState: 'QRLV1',Severity: 14
[22159]: RLVStore has run out of memory Exception Thrown from rvlib/rv_TabStoren.cxx:178, Err# 5, tid 3 origtid 3227
O/S Err#: 0, ErrID: 15008 (rv_PersistenceException); SQLCode: -1013129, SQLState: 'QRLV1', Severity: 14
Explanation A:
- To much data is being modified/ added by RLV transactions at once
Fix:
- Reduce the size of update/inserts and increase frequency of commits to keep amount of data modified/transaction.
Explanation B:
- Automated merge is not able to keep up with RLV workload
Fix:
- Review RLV merger history table(SYSIQRLVMERGEHISTORY)
- Adjust the automated merger period(RV_AUTO_MERGE_EVAL_INTERVAL)
- Adjust automated thresholds, RV_MERGE_TABLE_NUMROWS, RV_MERGE_TABLE_MEMPERCENT, and RV_MERGE_NODE_MEMSIZE RLV Options.
Explanation:
- Maximum RLV memory configure too low.
-increase maximum RLV memory using server startup switch –iqrlvmem
or
-increase maximum RLV memory using sa_server_option
sa_server_option ‘rlv_memory_mb’, <max MB>
- issue manual merge to free of RLV memory using
sp_iqmergerlvstore (merge_type, table_name, [table_owner])
Note: if low or out of memory , then issue blocking merge, as non-blocking merge needs to setup additional in-memory table fragments, which won’t be
possible,if already low/out of memory
Monitor:
(DBA)> sp_iqrlvmemory
table_id fragments total data dictionary bitmap
-----------------------------------------------------------------
1089 1 6 0 3 2
822 1 64 64 1 1
(2 rows)
(DBA)> select * from sp_iqstatus() where name like '%RLV%'
Name
Value
----------------------------------------------------------------
RLV memory limit:
4096Mb
RLV memory used:
76Mb
(2 rows)
This doc talk about how to set up RPC to other server, when RPC is embedded with in begin … end block. When Remote procedure is
created, engine has no knowledge of what Remote Procedure does and therefore It cannot implicitly define result set for Remote Procedure.
If Remote Procedure is executed using "call foo(...)" in DBISQL or dbisqlc, the application will open a cursor on the call statement
and the proper "cursor describe stuff" will automatically happen. BUT, if you attempt to execute a "call foo(...)" within a procedure
or batch, the engine does not automatically open a cursor on the call. Instead, it is up to the user to explicitly force a cursor to be opened either by
declaring a cursor within the stored procedure or batch or using the RPC in the from clause of a select statement. Furthermore, if the RPC is going
to be used in the from clause, then the RPC *MUST* be created with a RESULT clause in order to allow the engine to predefine the schema
of the expected result set.
STEPS:
Add source and target SAP Sybase IQ server entries in the interfaces. Add $ODBCINI and $ODBCHOME environment variables in $SYBASE/IQ-15_4/IQ-15_4.csh and then source to setup environment variables
CREATE SERVER "iqdemo1543" CLASS 'SAODBC' USING 'dsn=iqdemo1543';
2. Create Externlogin
CREATE EXTERNLOGIN "DBA" TO "iqdemo1543" REMOTE LOGIN "DBA" IDENTIFIED BY 'sql';
3. Create Remote Procedure:
create "DBA"."remwho"()
result(
ConnHandle unsigned bigint,
IQconnID unsigned bigint,
Userid varchar(255),
ReqType varchar(255),
IQCmdType char(32),
BlockedOn unsigned bigint,
BlockUserid varchar(255),
IQCursors unsigned integer,
IQThreads unsigned integer,
IQIdle integer,
SAIdle integer,
TempTableSpaceKB unsigned bigint,
TempWorkSpaceKB unsigned bigint )
at 'iqdemo1543...sp_iqwho'
4. Execute Remote Procedure
begin select * from remwho() end
ConnHandle IQconnID Userid
ReqType
IQCmdType BlockedOn BlockUserid
IQCursors
IQThreads IQIdle SAIdle TempTableSpaceKB TempWorkSpaceKB
--------------------------------------------------------------------------------
-----------------------------------------------------------------------
23 5625 DBA
OPEN
IQUTILITYOPENCURSOR 0 (NULL)
0
1
0 0 0 0
(1 rows)
Execution time: 0.025 seconds
Steps listed below can be used to setup remote connection from SAP Sybase IQ and SAP Sybase Adaptive Server Enterprise. First you will need to install OCS 157 64 bit on IQHOST in diferent location for using ASE odbc driver
1. setup Environment variables.
cd to $SYBASE/IQ-15_4 and edit IQ-15_4.csh and add:
setenv LIBPATH "${LIBPATH}:/usr/sybase/rel157/DataAccess64/ODBC/lib"
setenv PATH "${PATH}:/usr/sybase/rel157/DataAccess64/ODBC/lib"
setenv ODBCINI /usr/sybase/rel154_iq_esd3/odbc.ini
setenv ODBCHOME /usr/sybase/rel154_iq_esd3/
2. source IQ-15_4.csh
3. Add SAP Adaptive Server Enterprise and SAP Sybase IQ Server entries in interfaces
% cat $SYBASE/interfaces
aixase157
master tcp ether ASEHOST 8412
query tcp ether ASEHOST 8412
iq154
master tcp ether IQHOST 9522
query tcp ether IQHOST 9522
4. % cat $SYBASE/odbc.ini
[aixase157]
Description = Sybase ODBC Data Source
UserID = sa
Password =
Driver = /usr/sybase/rel157/DataAccess64/ODBC/lib/libsybdrvodb.so
Server = ASEHOST
Port = 8412
Database = pubs2
UseCursor = 1
[iq154]
DRIVER=/usr/sybase/rel154_iq_esd3/IQ-15_4/lib64/libdbodbc12.so
EngineName=iq154
CommLinks=tcpip(host=IQHOST;port=9522)
Userid=DBA
Password=sql
AutoStop=no
DatabaseName=iqdemo
5. stop and restart IQ server
6. Create Server and externlogin
% dbisql -c 'dsn=iq154' -nogui
(DBA)> select @@version
@@version
--------------------------------------------------------------------------------
Sybase IQ/15.4.0.3027/130814/P/ESD 3.6/Enterprise Linux64 - x86_64 - 2.6.18-194.el5/64bit/2013-08-14 03:34:24
(1 rows)
Execution time: 0.014 seconds
(DBA)> create server aixase157 class 'ASEODBC' usin
'Description=Sybase ODBC Data Source;Driver=/indigo61/sbagai/rel157/DataAccess64/ODBC/lib/libsybdrvodb.so;
UserID=sa,Password=;Server=indigo6;Port=8412;Database=pubs2;UseCursor=1'
;
Execution time: 0.036 seconds
(DBA)> create externlogin DBA to aixase157
remote login 'sa' ;
Execution time: 0.032 seconds
(DBA)> forward to aixase157
0 row(s) affected
Execution time: 0.01 seconds
(DBA)> select @@version
expr_1
--------------------------------------------------------------------------------
---------------
Adaptive Server Enterprise/15.7.0/EBF 19803SMP ESD#01 /P/RS6000/AIX 6.1/aseasap
/2918/64-bit/FBO/Wed Feb 8 06:09:12 2012
(1 rows)
Execution time: 0.85 seconds
(DBA)>
if you are unable to start SAP IQ Coordinator Server or Database in multiplex system, check .iqmsg and .srvlog for diagnostics information, depending
on the error you might be able to recover Coordinator using forced recovery steps. Most of the time assertion failed error messages are SA errors. Forced
recovery will not work for SA assertion failed error messages, you will need to restore from backups. It is advisable to contact SAP Sybase
technical support for assistance. For IQ issues (s_buf, freelist), you can follow steps listed below for performing forced recovery. For any
questions or concerns contact SAP Sybase Technical support.
Before using forced recovery, it is very important to restrict access to the database, you can either use -gm 1(allows single connection plus
one DBA connection so that DBA can connect and drop others in case of emergency, or issue sa_server_option('disable_connections', 'on')
after starting server in forced recovery mode, after forced recovery procedures, issue sa_server_option('disable_connections', 'off') on the same
connection.
Steps:
1. Shut down all secondary nodes using stop_iq or stop_server.sh
2. Start Coordinator with -iqfrec , -iqmpx_sn 1 , -gn 1 and -gd 1
start_iq -n <coordinator_server> @params.cfg -gd dba -gm 1 -iqfrec <coord db name without .db extn> -iqmpx_sn 1 <coord db name with .db extn>
start_iq -n < coordinator_server> @params.cfg -gd dba -gm 1 -iqfrec coord -iqmpx_sn 1 coord.db
3. Forced recovery marks all allocation within database as in use, run sp_iqcheckdb in dropleaks mode to reset allocation map to correct
state.
set temporary option dbcc_log_progress='on' ;
sp_iqcheckdb 'dropleaks database';
If there are no errors and sp_checkdb displays message 'Freelist Updated' you have recovered leaked blocks. Continue to Step 4
if incosistency is found, follow the instructions for dropping inconsistent indexs/tables or columns to drop inconsistent objects in Administration:
Backup, Restore and Data Recovery (Chapter: System Recovery and Database Repair)
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01759.1601/doc/pdf/iqbackup.pdf
4. Issue Checkpoint
5. Shutdown Coordinator using stop_iq or stop_server.sh script
6. Restart Coordinator normally without -iqfrec, -iqmpx_sn 1 , -gd 1 and -gm 1 switches
./start_server.sh
Note: start_server.sh and stop_server.sh scripts are generated by Sybase Control Center in Server .db directory.
7. If corruption was in IQ_SYSTEM_MAIN then run_sp_iqcheckdb on IQ_SYSTEM_MAIN else run dbcc on entire database.
set temporary option dbcc_log_progress='on' ;
sp_iqcheckdb 'verify dbspace IQ_SYSTEM_MAIN';
sp_iqcheckdb 'verify database'
8. Synchronize Secondary Nodes.
Query html plans are generated for load execution plans. Load execution html plans are generated for these statements:
To Generate html plans for load execution, you will need to set appropriate Query options:
For detailed information on these options:
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc00801.1600/doc/pdf/iqrefso.pdf
These option can be set as temporary option as well, Html plans should be only used to evaluate the performance of a particular query or load. Query_plan database option shouldn't be set to ON as it can significantly impact performance, especially as the volume of insert..value statement increases.
Query Plan Nodes:
New Query Plan Nodes:
Global Transaction Resiliency is HA functiionality available in IQ 16. This functionality allows Global Transactions to survive temporary communcation and temporary Coordinator failures.
Global Transaction is started by DML( delete/insert/load/update) on Multiplex Secondary(Writer) Node. Global Transactions are linked to INC( Internal Internode Communication) connection between Secondary(Writer) node and Coordinator. RW operation executed on Secondary(Writer) node behave as they were executed the Coordinator and does acquire table locks. Global Transaction failure can occur due to Coordinator failure(crash due to Hardware/Software issues, Coordinator Shutdown), Failover and INC(internal internode communication) . In such scenarios active Global DML transactions on Secondary(Writer) node will fail, secondary node will not be able to commit/rollback these transactions, even after Coordianator is available after some time. These transactions will need to be applied again.
With Global Transaction Resiliency functionality, Global Transactions are suspended and resumed, when INC connection is restored in following conditions:
In case of temporary failure of INC/Coordianator Global DML transactions on Secondary(Writer) node are kept in suspended state, and failures are resolved within timeout set with MPX_LIVENESS_TIMEOUT database option, then global transaction resumes, as if there were no failures. If the failures persists longer than the timeout set, then global transaction cann't be resumed, Secondary(Writer) rolls back suspended global transaction.
System Stored Procedure sp_iqconnection can be used to check connection status on Secondary(Writer) Node.
For complete details on sp_iqconnection:
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38151.1600/doc/pdf/iqrefbb.pdf
System Stored Procedures sp_iqmpsuspendedconninfo() can be used to for details about currently suspended connections and transactions on the Coordinator Node.
and
sp_iqmpxincstatistics() can be used for snapshot of the aggregate statistics of the INC(internal Internode communication) status since server startup as if the moment of execution
For complete details:
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01839.1600/doc/pdf/iqmpx.pdf
Database options to control Globaal Transaction Resilency behavior:
mpx_heartbeat_frequency: Default: 60 seconds
Minimum: 2 seconds
Maximum: 3600 seconds
mpx_heartbeat_frequency option sets the interval at which Secondary node internally polls Coordiator availability.
mpx_liveness_timeout: Default: 3600 seconds
Minimum: 0 seconds
Maximum: 3600 seconds
mpx_liveness_timeout option sets the timeout in seconds before a Secondary(Writer) Node rolls back suspended global transactions, if Coordiator is not available for a timeout greater than this option values. Cooridnator rollback suspended global transactions if Secondary(Writer) Node fails to resume the transactions for a period greater than twice of this option values.
For complete details:
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01839.1600/doc/pdf/iqmpx.pdf
Global Transaction Resiliency functionality does not affect trasactions initiated on the Coordinator Node. DDL commands from Secondary Nodes(Writer/Reader) will fail if Coordiator Node is not available.
SAP IQ has done it again! With the help of our partners BMMsoft, HP, Intel, NetApp, Red Hat, and MD&Profy set the Guinness World's record for the largest data warehouse at 12.1 petabytes (PB). It is an exciting milestone in SAP's Big Data strategy and proof o four leading technologies. View the press release and read the blog by Mike Hagman for details.
SAP IQ and the In-Memory Data Fabric
SAP In-Memory Data Fabric delivers real-time, in-context business decisions for everyone while simplifying the IT landscape. Allowing for complex analyses, plans and simulations to be done with real-time data and made available immediately. SAP IQ provides petabyte scale expansion - never put data in cold storage again. SAP IQ provides:
Subscribe for the quarterly newsletter to hear the latest news on SAP IQ and SAP ASE!
*New procedures for SAP IQ 15.x backup and restore databases*
<<< backup db INCREMENTAL SINCE FULL >>>
(DBA)> backup database INCREMENTAL SINCE FULL to '/data/sybase/iq1540/IQ-15_4/demo/iqdemo_isf.dmp';
Execution time: 0.563 seconds
<<< list all dbfiles in your database , you need to know these information for write restore script !!! >>>
(DBA)> sp_iqfile;
DBSpaceName DBFileName Path SegmentType RWMode Online Usage DBFileSize Reserve StripeSize BlkTypes FirstBlk LastBlk OkToDrop
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
IQ_SYSTEM_MAIN IQ_SYSTEM_MAIN iqdemo.iq MAIN RW T 11 200M 100M 1K 1H,2528F,32D,96A,128M 1 25600 N
iq_main iq_main iqdemo_main.iq MAIN RW T 12 100M 200M 1K 1H,1502A 1045440 1058239 N
iq_main iq_main2 /data/sybase/iq1540/IQ-15_4/demo/iqdemo_main2.iq MAIN RW T 49 100M 30M 1K 1H,6170A 2090880 2103679 N
test_dbspace filehist1 /data/sybase/iq1540/IQ-15_4/demo/test_dbspace.iq MAIN RW T 1 100M 0B 1K 1H,93A 3136320 3149119 N
user_dbspace user_dbspace /data/sybase/iq1540/IQ-15_4/demo/user_dbspace.iq MAIN RW T 1 100M 0B 1K 1H,48A 4181760 4194559 N
IQ_SYSTEM_TEMP IQ_SYSTEM_TEMP iqdemo.iqtmp TEMPORARY RW T 3 25M 200M 1K 1H,64F,16A 1 3200 N
(6 rows)
Execution time: 0.016 seconds
<<< backup database history summary >>>
(DBA)> sp_iqbackupsummary;
backup_id backup_time backup_type selective_type virtual_type depends_on_id creator backup_size user_comment backup_command
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10551603 2013-04-10 12:26:17.0 Full All inclusive Non virtual 0 DBA 68108 (NULL) backup database to '/data/sybase/iq1540/bk_full.dmp'
10552169 2013-04-10 12:35:27.0 Incremental since full All inclusive Non virtual 10551603 DBA 5580 (NULL) backup database incremental since full to 'bk_isf.dmp'
23483573 2013-11-26 08:41:43.0 Full All inclusive Non virtual 0 DBA 83212 (NULL) backup database full to '/data/sybase/iq1540/backup.dmp'
27838396 2014-01-15 08:06:49.0 Full All inclusive Non virtual 0 DBA 83212 (NULL) backup database to '/data/sybase/iqdemo.dmp' to '/data/sybase/iq1540/iqdemo.dmp'
27838519 2014-01-15 08:08:41.0 Full All inclusive Non virtual 0 DBA 83068 (NULL) backup database to '/data/sybase/iqdemo2.dmp'
27840379 2014-01-15 08:39:16.0 Full All inclusive Non virtual 0 DBA 83068 (NULL) backup database to '/data/sybase/iqdemo3.dmp'
27840404 2014-01-15 08:39:30.0 Full All inclusive Non virtual 0 DBA 83068 (NULL) backup database to '/data/sybase/iqdemo3.dmp'
27841397 2014-01-15 08:55:38.0 Full All inclusive Non virtual 0 DBA 83068 (NULL) backup database crc off attended off to '/data/sybase/iqdemo.bk1' to '/data/sybase/iqdemo.bk2'
27841576 2014-01-15 08:58:28.0 Full All inclusive Non virtual 0 DBA 83068 (NULL) backup database crc off attended off to '/data/sybase/iqdemo.bk1' to '/data/sybase/iqdemo.bk2'
27845482 2014-01-15 10:02:47.0 Full All inclusive Non virtual 0 DBA 83068 (NULL) backup database crc off attended off to '/data/sybase/iqdemo.bk1' to '/data/sybase/iqdemo.bk2' to '/data/sybase/iqdemo.bk3'
28014247 2014-01-17 08:32:16.0 Full All inclusive Non virtual 0 DBA 83212 (NULL) backup database full to '/data/sybase/iq1540/IQ-15_4/demotest/iqdemo.dmp'
29459031 2014-02-07 06:17:22.0 Full All inclusive Non virtual 0 DBA 83212 (NULL) backup database to '/data/sybase/iq1540/IQ-15_4/demo/iqdemo_full.dmp'
32773687 2014-04-21 04:08:28.0 Full All inclusive Non virtual 0 DBA 88920 (NULL) backup database to '/data/sybase/iq1540/bk_full.dmp'
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive Non virtual 32773687 DBA 6816 (NULL) backup database incremental since full to '/data/sybase/iq1540/IQ-15_4/demo/iqdemo_isf.dmp'
(14 rows)
Execution time: 0.02 seconds
<<< you can specify timestamp and return recently backup need for restore >>>
(DBA)> sp_iqrestoreaction getdate();
sequence_number backup_id backup_archive_list backup_time virtual_type restore_dbspace restore_dbfile backup_comment
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 32773687 /data/sybase/iq1540/bk_full.dmp 2014-04-21 04:08:28.0 Non virtual (NULL) (NULL) (NULL)
2 32774107 /data/sybase/iq1540/IQ-15_4/demo/iqdemo_isf.dmp 2014-04-21 04:15:14.0 Non virtual (NULL) (NULL) (NULL)
(2 rows)
Execution time: 0.035 seconds
<<< you can know backup id's details - Full backup >>>
(DBA)> sp_iqbackupdetails 32773687;
backup_id backup_time backup_type selective_type depends_on_id dbspace_id dbspace_name dbspace_rwstatus dbspace_createid dbspace_alterid dbspace_online dbspace_size dbspace_backup_size dbfile_id dbfile_name dbfile_rwstatus dbfile_createid dbfile_alterid dbfile_size dbfile_backup_size dbfile_path
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
32773687 2014-04-21 04:08:28.0 Full All inclusive 0 0 system ReadWrite 0 0 Online 3960 3960 0 system ReadWrite 0 0 3960 3960 /data/sybase/iq1540/IQ-15_4/demo/iqdemo.db
32773687 2014-04-21 04:08:28.0 Full All inclusive 0 16384 IQ_SYSTEM_MAIN ReadWrite 0 0 Online 204800 22424 16384 IQ_SYSTEM_MAIN ReadWrite 0 0 204800 22424 iqdemo.iq
32773687 2014-04-21 04:08:28.0 Full All inclusive 0 16387 iq_main ReadWrite 7 0 Online 204800 61392 16387 iq_main ReadWrite 7 8793633 102400 12024 iqdemo_main.iq
32773687 2014-04-21 04:08:28.0 Full All inclusive 0 16387 iq_main ReadWrite 7 0 Online 204800 61392 16388 iq_main2 ReadWrite 8694403 0 102400 49368 /data/sybase/iq1540/IQ-15_4/demo/iqdemo_main2.iq
32773687 2014-04-21 04:08:28.0 Full All inclusive 0 16388 test_dbspace ReadWrite 15499438 0 Online 102400 752 16389 filehist1 ReadWrite 15499438 0 102400 752 /data/sybase/iq1540/IQ-15_4/demo/test_dbspace.iq
32773687 2014-04-21 04:08:28.0 Full All inclusive 0 16389 user_dbspace ReadWrite 15707281 0 Online 102400 392 16390 user_dbspace ReadWrite 15707281 0 102400 392 /data/sybase/iq1540/IQ-15_4/demo/user_dbspace.iq
(6 rows)
Execution time: 0.019 seconds
<<< you can know backup id's details - Incremental since full backup >>>
(DBA)> sp_iqbackupdetails 32774107;
backup_id backup_time backup_type selective_type depends_on_id dbspace_id dbspace_name dbspace_rwstatus dbspace_createid dbspace_alterid dbspace_online dbspace_size dbspace_backup_size dbfile_id dbfile_name dbfile_rwstatus dbfile_createid dbfile_alterid dbfile_size dbfile_backup_size dbfile_path
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive 32773687 0 system ReadWrite 0 0 Online 3960 3960 0 system ReadWrite 0 0 3960 3960 /data/sybase/iq1540/IQ-15_4/demo/iqdemo.db
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive 32773687 16384 IQ_SYSTEM_MAIN ReadWrite 0 0 Online 204800 2824 16384 IQ_SYSTEM_MAIN ReadWrite 0 0 204800 2824 iqdemo.iq
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive 32773687 16387 iq_main ReadWrite 7 0 Online 204800 16 16387 iq_main ReadWrite 7 8793633 102400 8 iqdemo_main.iq
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive 32773687 16387 iq_main ReadWrite 7 0 Online 204800 16 16388 iq_main2 ReadWrite 8694403 0 102400 8 /data/sybase/iq1540/IQ-15_4/demo/iqdemo_main2.iq
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive 32773687 16388 test_dbspace ReadWrite 15499438 0 Online 102400 8 16389 filehist1 ReadWrite 15499438 0 102400 8 /data/sybase/iq1540/IQ-15_4/demo/test_dbspace.iq
32774107 2014-04-21 04:15:14.0 Incremental since full All inclusive 32773687 16389 user_dbspace ReadWrite 15707281 0 Online 102400 8 16390 user_dbspace ReadWrite 15707281 0 102400 8 /data/sybase/iq1540/IQ-15_4/demo/user_dbspace.iq
(6 rows)
Execution time: 0.017 seconds
(DBA)>
<<< you can check backup output files name and details >>>
sgsinvm0257:~> pwd
/data/sybase/iq1540
sgsinvm0257:~> ls -al bk*
-rw-r--r-- 1 sybase users 92369508 Apr 21 04:08 bk_full.dmp.1
<<< you can check backup history on logfile - 'backup.syb' under $IQDIR15/logfiles directory, that is alternative way if you don't use 'sp_iqbackupsummary' >>>
sgsinvm0257:~> cd $IQDIR15/logfiles
sgsinvm0257:~/IQ-15_4/logfiles> ls -al back*
-rw-r----- 1 sybase users 1884 Apr 21 04:15 backup.syb
<<< backup.syb is text file and every dump will log one line when dump job finished >>>
sgsinvm0257:~/IQ-15_4/logfiles> tail backup.syb
BACKUP, 1841178609.0, iqdemo.db, ASIQ, '2014-01-15 08:39:00.000', DBA, Full, Arch, /data/sybase/iqdemo3.dmp, ''
BACKUP, 1841178609.0, iqdemo.db, ASIQ, '2014-01-15 08:39:00.000', DBA, Full, Arch, /data/sybase/iqdemo3.dmp, ''
BACKUP, 1844332529.0, iqdemo.db, ASIQ, '2014-01-15 08:55:00.000', DBA, Full, Arch, /data/sybase/iqdemo.bk1, ''
BACKUP, 1844332529.0, iqdemo.db, ASIQ, '2014-01-15 08:58:00.000', DBA, Full, Arch, /data/sybase/iqdemo.bk1, ''
BACKUP, 1841178609.0, iqdemo.db, ASIQ, '2014-01-15 10:02:00.000', DBA, Full, Arch, /data/sybase/iqdemo.bk1, ''
BACKUP, 1841178609.0, iqdemo.db, ASIQ, '2014-01-17 08:32:00.000', DBA, Full, Arch, /data/sybase/iq1540/IQ-15_4/demotest/iqdemo.dmp, ''
RESTORE, -1606913199.0, , ASIQ, '2014-01-17 08:32:00.000', DBA, Full, Arch, /data/sybase/iq1540/IQ-15_4/demotest/iqdemo.dmp, ''
BACKUP, -2060036111.0, iqdemo.db, ASIQ, '2014-02-07 06:17:00.000', DBA, Full, Arch, /data/sybase/iq1540/IQ-15_4/demo/iqdemo_full.dmp, ''
BACKUP, 1195710449.0, iqdemo.db, ASIQ, '2014-04-21 04:08:00.000', DBA, Full, Arch, /data/sybase/iq1540/bk_full.dmp, ''
BACKUP, 1179940849.0, iqdemo.db, ASIQ, '2014-04-21 04:15:00.000', DBA, InSF, Arch, /data/sybase/iq1540/IQ-15_4/demo/iqdemo_isf.dmp, ''
During the migration of SAP IQ 15.2 ESD#3 to IQ 16.0 SP3 I experienced a considerable increase in the time required to load dataset from SAS 9.3 on PCs to SAP IQ 16.0 SP3 on a Solaris server using the insert command. The load of 72K rows when from 1hr to 4hrs and the SAP IQ 16 server was responding slowly to other users. When trying to use RLV to load the table from SAS, the server stop responding after all the rows where loaded in SAP IQ memory, the commit and the RLV store merge never happened and it was necessary to hot recycle SAP IQ (kill the Unix process and recover the database). I also notice that when number of rows to be loaded where under 10K, the insert performed well.
To solve this problem I worked with Laura Rodriques from The Ottawa Hospital, who provide expertise with SAS and Saroj Bagai, Support Architect at SAP Active Global Support.
1. If not already done, set the option ALLOW_READ_CLIENT_FILE to ‘ON’
set option public.ALLOW_READ_CLIENT_FILE = 'ON'
2. Grant the READCLIENTFILE system permission to the user
grant READCLIENTFILE to myUser
3. Grant the load permission to user on the table to load.
grant load on mySchema.MyTable to myUser
Note: RLV is disable on the table in SAP IQ.
1. Establish a new SAS/ACCESS connection to SAP IQ
libname dwtest sybaseiq user=&dwuser password=&dwpassword dsn=MySAPIqDb schema=mySchema;
2. Use “proc append” to load the data from a local work library in SAS.
procappendbase=dwtest.myTable
(BULKLOAD=YES
BL_USE_PIPE=NO
BL_DELETE_DATAFILE=NO)
data=work.mySASDataset;
run;
Where:
base= the table in the SAP IQ database that we are loading the data into.
BULKLOAD=YES calls a DBMS-specific bulk-load facility to insert or append rows to a DBMS table
BL_USE_PIP=NO specifies that a flat file is used to transfer data
BL_DELETE_DATAFILE=NOdoes not delete these files [saves a .dat file in the SAS User’s home directory; e.g. BL_mySASDataset_1715082846.dat]
data= the library and dataset of the data to be loaded to the SAP IQ Table
Using this process the load of the 72K rows from SAS to IQ was reduced to around 4 seconds.
References:
This post was first published in my personal blog at SAP IQ: Bulk Loading Data from SAS | ARBIME
If RLV failed to recover due to any kind of corruption such as OS exceptions/checksum errors on reading page from disk or mismatched sequence number on head/tail of page.
Recovery Steps:
delete * from table where rowid() > 2^48
5. Stop and restart SAP Sybase IQ server normally i.e without -gm 1 -gd DBA and -iqrvrec_bypass 1 switches.
sp_iqsysmon system stored procedure monitors multiple components of SAP IQ, including the management of Buffer allocations, Buffer manager, Buffer pool, Catalog statistics, CPU utilization , Free list management, Memory management, Prefetch management, IQ RLV-Memory Store statistics , Large Memory Allocator(LMA) statistics, Server context statistics, Thread management and Transaction management.
Large Memory Allocator has been added in SAP IQ 16 and is responsible for enforcing large memory allocation. Large memory is used by load and query engine.
Example: Starts sp_iqmonitor in the file mode and write statistics for Large Memory Allocator(LMA) to the log file
sp_iqsysmon start_monitor,'filemode' , '-section lma'
sp_iqsysmon stop_monitor
Large Memory Allocator (Statistics)
Large Memory Space 8421m
Large Memory Max Flexible 2105mb
Large Memory Num Flex Allocations 0
Large Memory Flexible % 50%
Large Memory Flexible used 0 mb
Large Memory Inflexible % 90%
Large Memory Inflexible used 0 MB
Large Memory Anti-Starvation % 50%
Large Memory Num Connections 0
Large Memory Space” – Maximum Large Memory configured size (-iqlm value from params.cfg)
“Large Memory Max Flexible” - Maximum memory granted for flexible operators. (e.g Load Engine(hash sort merge for hash/has-range partitioned table and hash sort merge cursor)).
“Large Memory Num Flex Allocations” – This is the count of memory chucks allocated as flex memory.
“Large Memory Flexible %” – percentage of large memory used for flexible operators.
“Large Memory Flexible used” – This is the total amount of memory allocated to flex users.
“Large Memory Inflexible %” – Percentage of large memory used for inflexible operators(N-bit metadata structures, data buffer of column vector in load ).
“Large Memory Inflexible used” – Large memory used by inflexible operators
“Large Memory Anti-Starvation %” – This only applies to flexible operators.
“Large Memory Num Connections” – This only applies to flexible operators and is the number of clients using lma. Internal concept only – has nothing to do with DB connections or users. There could be unregistered users too so this is not an accurate count of users.
When a new SAP IQ database is created we can use the MESSAGE PATH clause to specify the path where the message trace file will be stored; if you omit the MESSAGE PATH clause, the message trace file is created in the same directory of the .db file.
Sometimes it is necessary to later relocate the message trace file to a different location.
Here is a simple procedure to reallocate the message trace file.
1. Identify the actual location
select file_name from sysfile
where dbspace_name = 'IQ_SYSTEM_MSG'
file_name
----------------------------
devDwIqDb.iqmsg
2. Alter the IQ_SYSTEM_MSG dbspace
ALTER DBSPACE IQ_SYSTEM_MSG RENAME '/log_vol/dev/devDwIqDb.iqmsg'
3. Verify the new location
select file_name from sysfile
where dbspace_name = 'IQ_SYSTEM_MSG'
file_name
----------------------------
/log_vol/dev/devDwIqDb.iqmsg
4. Restart SAP IQ
Done!
This post was first published on my personal blog at SAP IQ: Relocate the Message Trace File to a Different Location | ARBIME
The transaction log file of a SAP IQ database can grow to undesirable size. It is recommended to truncate it frequently.
Here is a simple method to truncate the transaction log file when no backup is need. No downtime is necessary. Please note that there are other methods to backup and control grow of the transaction log file.
This procedure has been tested on SAP IQ 15 and IQ 16 on Solaris10.
which dbbackup
/IQ/Server/IQ-16SP8/IQ-16_0/bin64/dbbackup
dbbackup -c 'eng=SAPIQSrvr;dbn=SAPIQDb;uid=myUser;pwd=myPassword' -xo
SQL Anywhere Backup Utility Version 16.0.0.807
Transaction log truncation completed
Done!
This post was first published on my personal blog at SAP IQ: Truncate the Transaction Log | ARBIME