Hi all,

I have a customer who asked us the imapct on changing mode of /etc/hosts to 600(rw-------) to an IQ server.

They have to change the mode as above due to a guideline from Government.

Is it ok with an IQ server if we change hostname in all scripts, such as .odbc.ini, to ip address for the machine where the IQ server is running ?

1. Would you please let me know what kind of impacts would be expected if the customer change the mode of the /etc/hosts file ?

2. Are there any points we should consider ?

Any replies would be highly appreciated.

Regards.

Jerry

After exec statement in Interactive SQL:

RESTORE DATABASE 'E:\Data\test_DWH_IQ.db'

FROM '\\server\IQ_DWH_BackUp\IQ_DWH_INC20140804'

rename  ...

I Get message:

ERROR [08001] [Sybase][ODBC Driver][Sybase IQ]Unable to start specified database: unable to start database "E:\Data\test_DWH_IQ.db"

Note: I not start IQ Server. Only exec statement in Interactive SQL.

BackUP from 15.3 version server.

Restore on 15.4 server.

This is warning or db is corrupt?

Why restore statement trying start Sybase IQ after execution?

SAP IQ 16 sp08 and above now supports PAM User Authentication(PAMUA). Pluggable Authentication Module(PAM) is an centralized authentication system available on most Unix and Linux platforms and it provides a generic common interface to multiple low-level authentication schemes.  To configure PAM on your system,  you will need see your operating system documentation. The libpam.so[a] dynamic library must be installed on your system. SAP IQ sp08 documentation does provide sample pam authentication program(pamclient) for setting up and and testing PAM authentication on your system without SAP IQ Server.

Sample PAM Authorization Program - Administration: User Management and Security - SAP Library

pamclient program can be compiled and then tested on your system.

Two executables pamtest.so(PAM Server Authentication Module) and pamclient(sample test program, which can be used to test pamtest.so,  to confirm that is installed correctly).

Linux;
pamtest.so must be copied to /lib64/security/pamtest.so

and as root create pamtest file in /etc/pam.d

[pam.d]$ cat pamtest

auth    required        pamtest.so

account required        pamtest.so

Test:

[root@myhost pam.d]# echo + bob bobspwd > /tmp/pamtest.ctl

[root@myhost pam.d]#  pamclient bob bobspwd pamtest

#0 Authenticated user "bob" using service pamtest.

[root@myhost pam.d]# cat  /tmp/pamtest.ctl

+ bob bobspwd

[root@myhost pam.d]# rm /tmp/pamtest.ctl

For passwd service, make sure passwd service has correct entries:

[@hostname pam.d]$ cat passwd

#%PAM-1.0

auth       include      system-auth

account    include      system-auth

password   substack     system-auth

#-password   optional    pam_gnome_keyring.so

Configure PAM authentication in SAP IQ Server:

[@myhost  pam.d]$ dbisql -c 'uid=DBA;pwd=sql;eng=demo0801' -nogui

(DBA)> create login policy usepam pam_service_name = sshd pam_failover_to_std=on;
Execution time: 0.105 seconds

(DBA)> create user myuser login policy usepam
Execution time: 0.026 seconds

(DBA)> exit
[@myhostpam.d]$ dbisql -c 'uid=myuser;pwd=xxxxxxx;eng=demo0801' -nogui

(myuser)> quit

Note: login_mode option should be set as temporary option , every time you (re)start the database the login_mode will be reset back to its public setting…. So if you are setting login_mode to include PAMUA using a temporary setting then you will need to (re)set the temporary login_mode setting each time you start the database.  (This is precisely the point of using a temporary option when using PAMUA, Kerberos, integrated login, etc – it gives added security so that someone that gets a copy of your database cannot force a login into the database since they will not have DBA permissions to set the login_mode).

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:

                 http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01839.1602/doc/html/jan1292624444594.html

                 http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01839.1602/doc/html/jan1328621506262.html

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:

• If the connection is being made to a server which is not member of thespecified logical server
• If there are more waiters at the gate than the specified threshold of waiters in the -iqgovern queue.
• If the specified node type does have role different than that requested.

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01839.1602/doc/html/jan1328621506262.html

Hi,

I have a customer who has a problem to log in to cockpit console.

When ct installed IQ16 SP08 on window 2008 R2 (Korean package version), ct failed to log in to cockpit console.

Because there are no system information on it.

Cockpit console failed to bring the system information, It's a blank.

Ct found out that the issue is related to OS System.

If ct installed IQ16 SP08 on window 2008 R2 (English version) or added a package of english language.

And then ct changed express language from korean to english.

Ct succeeded to log in to cockpit console.

So Ct is wandering what is the differences between korean package version and English version.

Is it a language problem?

Thanks

Gi-Sung Jang

I want to share test results on FP NBit index with you and give some suggestions in using FP NBit index in IQ 16.0.

This document was written to guide our customers to be able to maintain the NEW FP NBit indexes more efficiently.

[ FP NBit ]

Continuous NBit dictionary compression replaces 1, 2, and 3 byte dictionary compression as the default column storage mechanism in 16.0.

All datatypes except LOB (character and binary) and BIT datatypes can be NBit columns.

[ Test Scenario ]

Checked the FP index type on the l_orderkey & l_partkey column depending on specifying IQ Unique Constraint.

Investigated the FP index type after changing values of the NBIT FP options and executing DML operations.

The test table was dropped and recreated whenever each test were completed.

[ Table Information ]

[ Error ]

An error was occurred when :
Setting FP_NBIT_ENFORCE_LIMITS Option to 'ON' and value of IQ UNIQUE constraint of a column was bigger than FP_NBIT_AUTOSIZE_LIMIT option.
Above values are commonly less than the cardinality of the column as well.

I. 08/11 02:24:51. 0000007077 [20897]:  9000000 Rows, 1 Seconds
I. 08/11 02:24:51. 0000007077 Exception Thrown from slib/s_dpNBit.cxx:3054, Err# 303, tid 181 origtid 181
I. 08/11 02:24:51. 0000007077    O/S Err#: 0, ErrID: 4098 (db_sqlexception); SQLCode: -1013124, SQLState: 'QDD32', Severity: 14
I. 08/11 02:24:51. 0000007077 [22154]: NBIT Column l_partkey exceeded token limit of 1980000
-- (slib/s_dpNBit.cxx 3054)

Even if a column has a FP NBit index, the above error can be occurred when the cardinality of the column become greater than the value of IQ Unique constraint.

[ Suggestions ]

1. In order to create FP NBit Indexes, you should satisfy one of following condistions.
          ● Without regarding to FP_NBIT_ENFORCE_LIMITS Option, the value of IQ UNIQUE constraint or FP_NBIT_AUTOSIZE_LIMIT Option is greater than the real cardinality of a column.
          ● FP_NBIT_ENFORCE_LIMITS is set to ‘OFF' and the value of IQ UNIQUE constraint is greater than FP_NBIT_AUTOSIZE_LIMIT
          ● A table is created without specifying IQ UNIQUE constraints and FP_NBIT_AUTOSIZE_LIMIT Option is greater than the real cardinality of a column,  and Dictionary Size of the column is less than FP_NBIT_LOOKUP_MB Option.

     You can see the dictionary size on a column by running sp_iqindexmetadata procedure as below.

2. Please keep an imporatant thing in manual below in mind when you specify an IQ UNIQUE constraint.

"Using IQ UNIQUE with an n value less than the FP_NBIT_AUTOSIZE_LIMIT is not necessary.
Auto-size functionality automatically sizes all low or medium cardinality columns as NBit.
Use IQ UNIQUE in cases where you want to load the column as Flat FP or when you want to load a column as NBit when the number of distinct values exceeds the FP_NBIT_AUTOSIZE_LIMIT."

3. I think it is desirable to set FP_NBIT_ENFORCE_LIMITS Option to 'OFF' so that you could avoild the error "s_dpNBit.cxx:3054".
For columns having integer family data types which do not have special meaning for indexing, such as (unsigned)bigint, numeric and float, it's good to use IQ UNIQUE(0) in order to create a flat FP index from the beginning.

4. You should also consider the value of "-iqlm" switch in a configuration file.
In case there are so many FP NBit indexes running in memory, you may encounter an error below.

I. 8/15 02:47:49. 0000000013 Exception Thrown from slib/s_dpNBit.cxx:252, Err# 13, tid 2 origtid 2
I. 8/15 02:47:49. 0000000013 O/S Err#: 0, ErrID: 517 (hos_memexception); SQLCode: -1013130, SQLState: 'QBC75', Severity: 14
I. 8/15 02:47:49. 0000000013 [22160]: All IQ large memory has been used, allocation canceled [size: 11430208]

If there are many concurrent DML transaction running, it will be better to lower the value of FP_NBIT_LOOKUP_MB option so that the large memory could not be exhausted.

[ See also ]

Please refer to the manual pages for details about database options below related to FP NBit maintenance.

● FP_NBIT_AUTOSIZE_LIMIT limits the number of distinct values that load as NBit
http://help.sap.com/saphelp_iq1608_iqrefso/helpdata/en/a8/73755184f21015a76ff1329f851c5d/content.htm

● FP_NBIT_LOOKUP_MB sets a threshold for the total NBit dictionary size
http://help.sap.com/saphelp_iq1608_iqrefso/helpdata/en/a8/73a52f84f2101588a9c5a2df1d1389/content.htm

● FP_NBIT_ROLLOVER_MAX_MB sets the dictionary size for implicit NBit rollovers from NBit to Flat FP
http://help.sap.com/saphelp_iq1608_iqrefso/helpdata/en/a8/73d4b984f2101592ac80c2eed3effc/content.htm

● FP_NBIT_ENFORCE_LIMITS enforces NBit dictionary sizing limits. This option is OFF by default
http://help.sap.com/saphelp_iq1608_iqrefso/helpdata/en/a8/74045684f21015abbbd6b7d63613e5/content.htm

If you find an incorrect information or you have different opinions on this item,  please let me know.

Thanks

Jerry

SAP IQ 15.4 supports a rolling upgrade.

in SAP IQ 15.4 SP04 cover letter:

Note: Do not run ALTER DATABASE UPGRADE. Running this command

  will prevent rolling the binary back to 15.4 GA if  required.

I have one question.

For example, if customer create a database uses the SP03, customer can use the rolling upgrade?

When customer upgrade to SP04 from SP03 database, they must run the ALTER DATABASE UPGRADE?

Thanks in advance,

Yasuo Kogawa| Senior Support Engineer
SAP Active Global Support

Is Sybase IQ Client certified with Windows 8 .

if so which version .

Is there any plan to add support for SAP IQ 16 on solaris 11?

Hi

We had a problem with IQ_SYSTEM_MAIN getting full and crashing the the coordinator/writer.

The dbspace is sized at 80GB for a 3Tb multiplex and normally runs at 21% utilization.

Is there any way I monitor the content of this space to determine why it would suddenly fill up

BTW to user data gets writtten to this space

Johan

Hi,

We some times need to get the full command of grant not one by one.

Here is a procedure to get the full command of grant.

Steps to get the full sentences from procedures.

1) Create procedure "grant_all_tables"

2) Execute a procedure with parameters.

    Get the full commands of "grant select on the DBA's tables to user gjang":

    Ex) call grant_all_tables('select','DBA','%','gjang');

3) copy the grant command and execute a grant command.

* grant type : 'select, insert, update, delete, all'

* table pattern : % -> all tables

I uploaded a procedure "grant_all_tables".

I have tested in IQ12.7/15.x/16.x.

Thanks

Gi-Sung Jang

Hi all,

Does IQ15.4 support RedHat 6.4?

I found a information regarding this like below.

** Supported Server Platforms

Sybase IQ is compatible with these platforms and operating systems.

- Red Hat Enterprise Linux 6.2 (Linux on POWER; 64-bit)

- Red Hat Enterprise Linux 6.2 x86-64, Advanced Server and Workstation Editions

- Red Hat Enterprise Linux 6.0 (Linux onPOWER;64-bit) - minimum patch level Update-2

- Red Hat Enterprise Linux 6.0 x86-64, Advanced Server and Workstation Editions -minimum patch level Update-2

Thanks

Gi-Sung Jang

Dear All,

I have a customer who wants to know the plan or workaround for AIX-32bit such as "Linux 32bit".

• IQ15.4 ESD4/4.2 Client.
• OS : AIX-32bit.

[from customer]

Please let me know whether Sybase IQ Network Client 15.4 ESD 4/ESD4.2 is available for AIX 32 bit OS.

If not, what is the workaround?

I could see the same software available for Linux 32 bit OS in SAP marketplace but not for AIX 32 bit.

thanks

Gi-Sung Jang

Dear all,

[Env]

- SAP IQ/16.0.0.807/140507/P/sp08/Enterprise Linux64 - x86_64 - 2.6.18-194.el5/64bit/2014-05-07 18:02:42

I have a customer who has a problem about IQ_VLDBMGMT.

According to customer, they purchased a IQ_VLDB license like below.

Ct asked me how to check the VLDB license through sp_iqlmconfig.

Because IQ_VLDBMGMT not showin in sp_iqlmconig.

Ct kept failing to enable VLDB as follows.

1) sp_iqlmconfig 'allow', 'IQ_VLDBMGMT', '10'

2) call sp_iqlmconfig ('allow', 'IQ_VLDBMGMT', '10')

3) sp_iqlmconfig 'allow', 'IQ_VLDBMGMT', 10

[Error]

Could not execute statement.

Wrong number of parameters to function 'sp_iqlmconfig'

SQLCODE=-154, ODBC 3 State="42000"

Line 1, column 1

Are there any possibilities about this?

Any comments will be greatly appreciated.

Thanks,

Gi-Sung Jang

Hi,

I'm looking for some kind of a howto to setup multiplex without migrating an existing one. Unfortunately I wasn't able to find some. Or is it the default way creating a database and maybe migrating it later from simplex to multiplex?

Thanks,

Frank

1. Problem

A IQ_VLDBMGMT license is not shown in sp_iqlmconfig in spite of purchased proper VLDB licenses.

[sp_iqlmconfig]

...

Optional license in use: IQ_VLDBMGMT

    > No

IQ_VLDBMGMT License Count in use

    > 0

So customer tried to enable the IQ_VLDBMBMT license using sp_iqlmconfig, but customer is getting the error.

   > sp_iqlmconfig 'allow', 'IQ_VLDBMGMT', 10

[Error]

   Could not execute statement.

   Wrong number of parameters to function 'sp_iqlmconfig'

   SQLCODE=-154, ODBC 3 State="42000"

   Line 1, column 1

2. Cause

A "sp_iqlmconfig" you executed is not upgraded yet  to support the IQ16 SP08 new syntax.

Because customer forgot to execute a "alter database upgrade" command.

The ALTER DATABASE statement upgrades databases created with earlier versions of the software. This applies to maintenance releases as well as major releases.

When you upgrade a database, SAP Sybase IQ makes these changes:

1) Upgrades the system tables to the current version.

2) Adds any new database options.

3) Enables new features in the current version

3. Resolution

Need to execute an "alter database upgrade" when upgrading an IQ.

We can see the upgrade history through syshistory like below.

[syshistory]

operation,object_id,sub_operation,version,platform,first_time,last_time,details

'UPGRADE',0,'','16.0.0.807','Linux 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:3','2014-09-03 09:31:59.000','2014-09-03 09:32:34.000',CA=1FE38EF000D001FEDFF7FDD;

Dear all,

• IQ15.2
• OS : HP

I have a customer who has a plan to apply a patch of LVM due to H/W issue.

Ct asked me that there are any effects on IQ when changing a version of LVM from 0903 to 1209.

[H/W Issue]

-------------------------------------------

Table 1 LVM Fixes in HP-UX 11i v3 September 2012 Release

In a cluster with 3 or more nodes, when VG recovery is in progress for at

least 5 VGs on each node following a previous server node crash, one or

more nodes may get TOC'ed by SG.

On the TOC'ed node, most of the lvmkd daemons will have the following

stack trace:

------------------------------------------------------------

Current Version of LVM

• BaseLVM B.11.31.0903 Logical Volume Manager

Does anyone has a similar experiences?

Any comments will be greatly appreciated.

Thanks in advance.

Thanks and Best regards,

Gi-Sung, Jang

Hi Team,

This document may be necessaryfor those whohave problemswithinstallation IQ16.0 SP08 64bitonWIndows.

Attach files: Step to Install IQ16.0 SP0864bit

This ispart of the installbecause youcan choose to continue and installSAPControl Centeror Cockpit Server

After you can directlyapplythe update e.g:PL03

Regards,

Claude

Context:

Sometimes after new IQ server upgrade, we experience unusual errors or uncommon behavior when trying to execute a system procedure or setting an option.

For example, you may get unexpected syntax errors,  system procedure doesn't
exist, or option doesn't exist.

If you are in that case, then you first need to check whether the database is actually migrated to IQ server level where the commands in question are
supported and expected to work.

Follow steps below:

1- Connect to database as DBA

2- Get the current server full version : select @@version

2- Execute query

select substring(operation,1, 12) as operation, substring(version,1, 12)
as version,  first_time, last_time, substring(platform,1, 20) as platform
from SYSHISTORY
order by  last_time ;

3- See "version" values. If 'UPGRADE "version" and 'LAST_START' "version" are
not the same, then the database is not upgraded to current server version.

If  no 'UPGRADE' in the result, then compare INIT with LAST_START.

INIT : Information about when the database was created.

START :  Information about when the database was started using a specific
version of the database server on a particular operating system.

UPGRADE : Information about when the database was upgraded.

LAST_START : Information about the most recent time the database server was
started. A LAST_START operation is converted to a START operation when the
database is started with a different version of the database server and/or on a
different operating system than those values currently stored in the LAST_START
row.

4- If the database is NOT migrated, then it belongs to DBA to decide to
migrate or not. The reason of keeping the database could be the need to
start/use it with previous server version in other environments or ability of
rolling upgrade.

5- To migrate the database go though Migrating database steps from SAP IQ
manuals or in SP/EBF readme .

Example from iqdemo 16 on Linux:

select @@version

SAP IQ/16.0.0.807/140507/P/sp08/Enterprise Linux64 - x86_64
- 2.6.18-194.el5/64bit/2014-05-07 18:02:42

select substring(operation,1, 12) as operation, substring(version,1, 12)
as version,  first_time, last_time, substring(platform,1, 20) as platform

from SYSHISTORY
order by  last_time

operation,version,first_time,last_time,platform
'INIT','16.0.0.653','2014-02-13
13:54:16.000','2014-02-13 13:54:16.000','Linux
2.6.32-131.0.1'
'START','16.0.0.653','2014-02-13 05:54:18.000','2014-08-08
09:12:21.000','Linux 2.6.32-131.0.1'
'START','16.0.0.807','2014-08-08
09:12:21.000','2014-08-08 09:12:21.000','Linux
2.6.32-131.0.1'
'LAST_START','16.0.0.807','2014-08-08
09:12:21.000','2014-08-08 09:12:21.000','Linux
2.6.32-131.0.1'
'UPGRADE','16.0.0.807','2014-08-08
09:13:50.000','2014-08-08 09:13:50.000','Linux 2.6.32-131.0.1'

In this example, the database is created with IQ version
16.0.0.353 at '2014-02-13 13:54:16'.

It was last started on '16.0.0.807'   IQ
server at '2014-08-08 09:12:21'

then migrated to same version '16.0.0.807'  at '2014-08-08
09:13:50'