Skip to Content
Technical Articles
Author's profile photo Roland Kramer

demystifying NLS/ILM error messages …

last changed: 27th of September 2022

while a lot of People think that nearline storage (NLS) for SAP BW/4 and information lifecycle management (ILM) for S/4 is not used by SAP customer, you punish him with the lie. Of course the usage is also possible with SAP BW and ERP as well, and the SAP IQ Roadmap is save for the next decade.

To bring more light into the NLS/DTO/ILM configuration, this Blog explains some of the most repetitive error messages and most importantly their root causes.

Three Things to know:

Unfortunally, when the child has fallen into the well, then good advice is expensive. For this topic the Document – SAP First Guidance – SAP NLS Solution with SAP IQ 16.x is the first line of defense, as it contains the complete e2e case described in detail and continuously updated since 2013. However, it still looks like that you can nail the Document to the gate of the Cologne Dom, and there would be still hardliners saying: “but my case is different”. Hell, it is not as all errors can be reduced to the proper configuration.

despite%20it%20is%20Teched%20or%20not%20-%20the%20Cat%20is%20also%20curious

despite it is Teched or not – the Cat is also curious

 


common Error Messages

here some of the most current and repetitive Error Message which occur, when you start the Process the first time in the SAP ABAP Backend (despite which release/OS/DB/etc.)

Three Kind of Error Message could rise:

ADBC error 'Internal error 16 has occurred' (refers to old/missing ODBC libraries, Notes 2516116, 2844842
Allocation failed. Dbspace IQ_SYSTEM_TEMP is OUT OF SPACE (refers to SAP Note 2982226, IQ Temp Space)
unexpected return code 8192 calling DBDS (refers to missing IQ Network Client, Note 3119008)
[IQ Error SQL-308:HY000][Sybase IQ]Connection was terminated (refers to IQ TEMP and BACKUP issues)
[IQ Error SQL-308:HY000][SAP][ODBC Driver][SAP IQ]Connection was terminated (refers to message above)
SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: 
(refers to incorrect IQ remote source, Notes 1989436 and 3196447)
[IQ Error SQL-100:08001][SAP][ODBC Driver][SAP IQ]Database server not found 
(IQ ServerName/SYBASE_IQ_ENGINE missing, refer to SAP Note 3136413)
[IQ Error SQL-771:HY000][Sybase IQ]Event 'BACKUP_REQUEST' not found
[IQ Error SQL-1090:08004][Sybase IQ]Function 'substr' has invalid parameter '3' ('-1')
[IQ Error SQL-143:42S22][Sybase IQ]Column 'RECORDMODE' not found (refers to SAP Note 2996682)
[IQ Error SQL-143:42S22][Sybase IQ]Column 'ARCHREQUID_SID' not found (refers to SAP Note 2562256)
[IQ Error SQL-1068:42S02][SAP][ODBC Driver][SAP IQ]Default dbspace '<USER DB SPACE>' not found (missing DB space after IQ copy, refer to Notes 2634028 and 2634024)
[IQ Error SQL-1000121:HY000][Sybase IQ]binary data not supported on data longer than 32767 Bind host variable 
(ILM - refers to SAP Note 2806115)
[IQ Error SQL-853:24000][Sybase IQ]Cursor not in a valid state (refers to SAP Note 2982226)
[IQ Error SQL99987]ERROR: could not start iq load. 
(refers to Note 2933420, missing space/SYBASE_IQ_LOAD_DIR in DBCO string)
[IQ Error SQL99988]ERROR: Driver SAP IQ is unsupported for connections to Sybase IQ
[IQ Error SQL99999]decimal overflow has occured (New, refers to Note 3217479)
[IQ Error SQL-1084:HY000][SAP][ODBC Driver][SAP IQ]Use of feature 'DBSPACE' is not allowed 
(refers to wrong SSL/TLS IQ Setup)
[IQ Error SQL-121:42000][SAP][ODBC Driver][SAP IQ]Permission denied: you do not have required privilege to create table "udatest" 
(refers to Note 2372218, create table/index with user DBA)
[IQ Error SQL-131:42000][SAP][ODBC Driver][SAP IQ]Syntax error near '999' on line 1
[IQ Error SQL-131:42000][Sybase IQ]Syntax error near '(end of line)' on line 
(refers to wrong/missing DB user space - Notes 1959690 and 2297484) 
[SAP][ODBC Driver][SAP IQ]User ID 'SAPNLS' does not exist 
(missing/wrong IQ User - refers to Note 2344235)
[SAP][ODBC Driver][SAP IQ]Not enough server threads available for this query 
(refers to Note 3017355) SAP DBTech JDBC: [258]: insufficient privilege 
(refers to Note 3119008, permission of SAP<SID> user)
SQLCode = -121: Permission denied: you don't have the permission to create objects in dbspace IQ_SYSTEM_MAIN 
(refers to DB Option Enable_LOB_Variables)
invalid remote object name: Cannot retrieve why the ODBC API has failed: line 0 col 0 (at pos 0)
(refers to HANA ODBC/SDA Driver mismatch and old HANA Studio, Notes 2184030, 2352696)
ERROR => Codepage mismatch between executable (UNICODE) and DBSL shared library dbsybslib.so 
(ASCII refers to Note 1820534, only UC supported for ASE/IQ LibDBSL)

 

# error messages in conjunction with SSL/TLS

Encryption error: The FIPS library (libdbcrypto.so) cannot be found in the LD_LIBRARY_PATH
[SAP][ODBC Driver Manager] Unable to load driver libdbodbc17_r.so
[SAP][ODBC Driver][SQL Anywhere]Unable to connect: The server did not accept the requested encryption type
[SAP][ODBC Driver][SAP IQ]Connection error: Connection was dropped (may not be an SAP IQ server)
SQLCODE=-832 SQLSTATE=08001
[IQ Error SQL-1145:08001][SAP][ODBC Driver][SAP IQ]Unable to connect: The server did not accept the requested encryption type
[IQ Error SQL-895:08001][SAP][ODBC Driver][SAP IQ]Encryption error: Unable to open certificate file '/usr/sap/B4H/SYS/global/hostname_SQ1_11.crt'
[IQ Error SQL-895:08001][SQL Anywhere]Encryption error: Unrecognized encryption option 'skip_certificate_name_check'

DBSL Dev: the option 'skip_certificate_name_check=yes' is automatically added in the DBCO connection string when DBSL finds libdbodbc17.so

 

CL_RSDA_ADSO_ARCHIVING_REQUESTCM01U (refers to IQ performance settings, Note 2371160)
CL_RSDA_ADSO_ARCHIVING_REQUESTCM01Q (refers to IQ backup problems, Note 2741824 and RSDANLCON settings)
CL_RSDA_ADSO_CURSOR===========CM003 (refers to Note 3075223, NLS Archiving limit)
CL_RSDA_ADSO_DTO_PROCESS_INV==CM004 (refers to Note 3076162, enable load striping for DTO)
CL_RSDA_ADSO_RESTORE_REQUEST==CM00V (refers to SAP Note 2996682, BW System Inconcisteny)
CL_RSDA_DAP_A=================CM02A (refers to RSDAP activation/prod. usage)
CL_RSDA_DAP_A=================CM029 (refers to SAP Note 2562256, Column 'ARCHREQUID_SID' not found)
CL_RSDA_NEARLINE_CONNECTION===CP    (refers to missing NLS connection)
CL_RSDA_NEARLINE_OBJECT=======CM00Q (refers to IQ lock mode problems after copy)
CL_RSDA_NEARLINE_OBJECT=======CM01B (refers to IQ configuration problems, Note 3017355)
CL_RSDA_NEARLINE_OBJECT=======CM00T (refers to SDA setup problems, Note 3119008)
CL_RSDA_NEARLINE_REQUEST======CM004 (refers to missing IQ Backup event, Note 2741824)
CL_RSDA_NEARLINE_REQUEST======CM006 (refers to IQ copy problems, Notes 2344235 and 3085053)
CL_RSDA_NEARLINE_SEGMENT======CCIMP (refers to SAP Note 2982226, IQ Temp Space)
CL_RSDA_NEARLINE_WRITER=======CM002 (refers to NLS configuration RSDANLCON)
CL_RSDA_NEARLINE_WRITER=======CM004 (refers to NLS DAP and request size, Note 3075223)
CL_RSDA_ADV_NEARLINE_WRITER===CM006 (refers to SAP Note 2996682, Column 'RECORDMODE' missing)
CL_RSDA_INFOPROV_WRITER_CUBE==CM003 (refers to MasterData inconcistencies, Note 2866852, IQ TEMP space)
CL_RSDA_INFOPROV_WRITER_CUBE==CM003 (refers to Note 3214341)
CL_RSDA_INFOPROV_WRITER_CUBE==CP    (refers to IQ timeout due to inconcistencies, Note 2289880)
CL_RSDA_INFOPROV_WRITER_ODSO==CM003 (duplicate entries - Note 2400729)
CL_RSDA_SYB_CONNECTION_IMPL===CP    (refers to missing IQ ODBC drivers and IQ backup, Note 3119008)
CL_RSDA_SYB_CONNECTION_IMPL===CM02U (refers to IQ BACKUP, Notes 2658428 and 2741824)
CL_RSDA_SYB_CONNECTION_IMPL===CM006 (refers to wrong setup of RSDANLCON, "is Default Con" not ticked)
CL_RSDA_SYB_CONNECTION_IMPL===CM00C (refers to Note 2482264, space problem)
CL_RSDA_SYB_CONNECTION_IMPL===CM00E (refers to IQ configuration/concisteny problems, Note 3017355)
CL_RSDA_SYB_CONNECTION_IMPL===CM00K (refers to SAP Note 3119008, wrong SDA/ODBC con.)
CL_RSDA_SYB_CONNECTION_IMPL===CM00L (refers to SAP Note 3119008, wrong IQ Client SW)
CL_RSDA_SYB_CONNECTION_IMPL===CM00X (refers to Note 2191066, missing backup)
CL_RSDA_SYB_CONNECTION_IMPL===CM01J (refers to IQ License LOB/VLDBMGMT)
CL_RSDA_SYB_CONNECTION_IMPL===CM02B (refers to HANA perm. and ODBC driver, Notes 2352696 and 3106440)
CL_RSDA_SYB_CONNECTION_IMPL===CM02U (refers to missing IQ Backup event, Notes 2741824/3017355)
CL_RSDA_SYB_CONNECTION_IMPL===CM03T (refers Report RSDA_CLEANUP_DTO_COLDSTORE)
CL_RSDA_SYB_CURSOR============CM002 (refers to SAP Note 2996682, BW System Incconcisteny)
CL_RSDA_SYB_CURSOR============CM004 (refers to SAP Note 3217479, BW System Incconcisteny)
CL_RSDA_SYB_WRITER_STRIPED====CM002 (refers to Notes 2307267, 2902060 NLS load stripping mismatch)
CL_RSDA_SYB_WRITER_TSN_STRIPEDCM002 (refers to Notes 2307267, 2902060 NLS load stripping mismatch)
CL_RSDA_SYB_WRITER_TSN========CM002
CL_RSDA_SYB_WRITER_TSN========CP
CL_RS2HANA_VIEW_OBJ===========CM004 (refers to CL_RSDA_SYB_CONNECTION_IMPL===CM02B)
CL_RSSDA_FEDERATION_SERVICES==CM004 (refers to HANA priv. and no spc on device, Notes 1989436/2902060)
CL_RSSDA_FEDERATION_SERVICES==CM00H (refers to HANA virtual Index creation, Note 2790789)
CL_RSSDA_FEDERATION_SERVICES==CM011 (new, refers to BW/4 2021 during RSDANLCON setup)
CL_RSSDA_REMOTE_SOURCE========CM009 (new, refers to BW/4 2021 missing HANA remote source temporary)
CL_RSDRS_SQL_QUERY============CM01C (refers to InfoCube/aDSO Model Complexity, Note 2720236)
CL_SQL_STATEMENT==============CM002 (refers to IQ configuration problems, Note 3017355)
CL_SQL_STATEMENT==============CM008 (refers to Note 2482264, space problem)

 


the Solution for all of this …

to make a log story short, with the following SAP Notes 99% Percent of all “individual Problems” are solved.

Note 2741824 – How to setup backup automation for SAP IQ Cold Store/Near-line Storage
Note 2780668 – SAP First Guidance – BW NLS Implementation with SAP IQ
Note 3218186 – Error: Create new (IQ) database from utility database fails
Note 3017355 – SAP IQ 16.1 SP04 PLx – correct SAPIQDB.cfg settings
Note 3094594 – Enable SAP IQ for DBACOCKPIT
Note 3085053 – Landscape Considerations for NLS and ILM
Note 3119008 – Configure SAP IQ and HANA for SDA/ODBC
Note 3196447 – troubleshooting an existing SAP IQ 16.x Implementation for NLS/DTO and ILM

to easy for you? I’m afraid to say, it is quite straight forward.

of course you should check your Software Level as well to ensure that you are up-to date with the SAP Corrections – Access Expert Search

Version SP-Level Current SP (12/2021) Support
SAP BW 7.40 26 SAPKW74026 until End of 2020
SAP BW 7.50 24 SAPK-75022INSAPBW until End of 2027
SAP BW/4 1.0 20 SAPK-10020INDW4CORE until End of 2021
SAP BW/4 2.0 11 SAPK-20010INDW4CORE until End of 2024
SAP BW/4 2021 2 SAPK-30001INDW4CORE commitment until 2040
Components Category
BW-WHM-DST-ARC BW/4 only BW4-DM-DTO Program Error
BW-SYS-DB-IQ optional BW-WHM-DST-DTP Search Term
BC-SYB-IQ optional BW-WHM-DBA-ADSO archive, near-line, IQ

Note 2191066 – You must do a full backup before doing an incremental backup – SAP IQ
Note 2344235 – Consulting: Handling Data Archiving Processes during system copies
Note 2482264 – Error write iq data file failed: only X out of Y bytes written occur during BW archiving process – SAP BW with SAP IQ Near-line Storage
Note 2634028 – How to & Where to BackUp IQ database -SAP IQ
Note 2800016 – BW HCPR – Collective Note for Problems with Queries on HANA CP
Note 2902060 – Why the temp files created by DBSL to handle data loads from DTO into IQ are excessively large
Note 3075223 – NLS Archiving limit by number of records
Note 3076162 – Load DTO data package wise into IQ ( hot -> cold with load striping )
Note 3081905 – Overlap between deletion criteria and archiving criteria
Note 3092501 – RSDA_SYB_PARTITION_MONITOR short dump
Note 3097868 – DAP transport fails in IQ
Note 3102238 – RSDA_SYB_SE16 – wrong HDB restriction
Note 3107783 – Load DTO data package wise back from Sybase IQ ( cold -> hot )
Note 3153446 – Archiving of IMOCube with more than 255 characteristics results in mes RSDA 228
Note 3169877 – RSDA_CLEANUP_ARCHIVE enhancements
Note 3214341 – SAP NLS: improved error logging upon archiving reload
Note 3217479 – NLS on sybase IQ: reload with LOB fields
Note 3238815 – Pruning of IQ access is not working (Pilot Note, please contact SAP)

 


Three things to know when using NLS/DTO/ILM

 

I still remember this phrase from a Swiss SAP Sales Person from my early days. 
I told him, that I did some Consulting activities which helped
one of many Customers to move forward with their SAP BW Solution.
His Answer to that Information was fairly simple for him:
"Roland, what is your Point? I can only remember three things at the time."

 


First: correct Setup of the SAP IQ Database

Check that you are using the current Versions for SAP IQ Database and Network Client (SDA/ODBC)

Note 2551457 – SAP IQ 16.1 SP 03 Supported Operating Systems and Versions
Note 2669590 – SAP IQ 16.1 SP 04 Supported Operating Systems and Versions
Note 3060790 – SAP IQ 16.1 SP 05 Supported Operating Systems and Versions
Note 2833463 – RedHat 8 Certification – SAP ASE / SRS / IQ / SDK

Note 2201721 – How to download SAP IQ support packages and patches

Note 3210982 – SAP IQ 16.1 SP04 PL13 (Build 17090) Release Notes Information
Note 3210938 – SAP IQNC 16.1 SP04 PL13 (Build 17090) Release Notes Information

Note 3213605 – SAP IQ 16.1 SP05 PL03 (Build 11595) Release Notes Information
Note 3214513 – SAP IQNC 16.1 SP05 PL03 (Build 11595) Release Notes Information

this is already a big fountain of possible error and problem sources, especially

Note 2072203 – How to generate an SAP SQL Anywhere or SAP IQ Request Log to record executed SQL commands from database clients
Note 2270379 – How to dynamically enable SQL Server Request Logging – SAP IQ

Q – the easy Installer for SAP IQ – would be an answer, but unfortunally not “official” as the result is “supported”, but the way of the SAP IQ Database Installation is not (what an irony).


Second: correct SDA/ODBC Setup to the primary Database

  • is really all necessary software accessible?
  • is the grant possible between the IQ remote source and the primary DB?
  • are the correct variables in the correct profiles activated
  • are all server restarted after the configuration?
  • are the current updates for the ODBC/SDA/LibDBSL drivers installed?

The SDA/ODBC Setup is still a complex manual task, which could be potentially automated, or SAP IQ and HANA could be use SAP proprietary connection Methods which is not considered.

Note 3119008 – Configure SAP IQ and HANA for SDA/ODBC

Current (08.2022) SAP HANA Client/ODBC/SDA drivers:

Note 2184030 – SAP HANA Smart Data Access: How to Increase the Number of Objects Displayed
Note 1989436 – Open ODS View with Smart Data Access – Invalid Table Name during Query Execution
Note 2100962 – FAQ: BW Near-Line Storage / Cold Store with HANA Smart Data Access: Query Performance
Note 2165650 – FAQ: BW Near-Line Storage / Cold Store with HANA Smart Data Access
Note 2352696 – SAP HANA Smart Data Access 2.0 Master Release Note
Note 2695442 – External Hana View: Activation of BW Object fails with error ‘Replication failed RS2HANA_AUTH234’
Note 2902060 – Why the temp files created by DBSL to handle data loads from DTO into IQ are excessively large
Note 3122299 – “user is not authorized” error during HCPR data read
Note 3149596 – Checklist to resolve insufficient authorization errors related to External SAP HANA views
Note 3211177 – How to find invalid Views and re-validate them – SAP IQ

SAP Help – (NetWeaver) SAP HANA Smart Data Access (SDA) for Near-Line Storage in SAP IQ
SAP Help – (HANA) SAP Authorization Objects

Also the following Issues have to be considered here, when the SDA/ODB connection worked in the past and suddenly not anymore:

  • If the correct LibDBSL for ASE/IQ was not included in a SAP Kernel Update, the connection doesn’t work anymore.
  • If in the meantime a SAP ABAP Upgrade took place, the SAP ABAP Environment is overwritten and the SDA/ODBC Setting are missing.
  • The SAP BW System was overwritten by a System Copy and the RSDANLCON Settings are not fitting anymore. (Note 2344235).
  • The existing SAP IQ Database was replace by an old Backup from a System Copy and the Settings are not fitting as well anymore (DBCO and RSDANLCON).
  • Eventually the SAP IQ Network client Directory was deleted or replaced and the SDA/ODBC Environment is not fitting anymore.
  • Since the correct SDA/ODBC Setup is working, additional Setting to other Databases were added to the Environment which causes the original Setup to stop.
  • The IQ Backup Events are not working properly, as they are mandantory for the correct writing process of the nearline storage data.
  • The DBCO Entry for the IQ Database was changed and the setting for min/optimal/permanent changed without notice.
  • Due to authorization issues someone changed the user in the DBCO Connection from SAP<SID>USR to DBA, this will not work.
  • the SAP_SYSTEM_MAIN DB and/or SAP_SYSTEM_TEMP DB Space are full due to missing IQ Database Monitoring and follow up errors take place.

 


Third: correct ABAP Customizing (HANA/DBCO/RSDANLCON)

Please Note, the DBCO connection which is further used, MUST use a designated user to proceed further. the Admin User DBA is not aligned for this.
SAP First Guidance – SAP NLS Solution with SAP IQ 16.x => Chapter 3.1.1.

Also this could be automated with the extension of Q – the easy Installer for SAP IQ as the SAP Host Agent is capable to do remote calls and execution to the SAP Backends, and the SAP IQ Database Installer already defined all necessary SAP Environment Variables and Informations.

Before executing the first DAP you have to execute a full/incremental backup since full event.
This can now be done with the new DBACOCKPIT for IQ.
Note 3123892 – New features for DBACOCKPIT on SAP IQ (TCI for SAP_BASIS release 750 SP11-22 and 753 SP00-SP07)
Note 3212812 – DBSPACE usage screen correction for TB and PB in DBACOCKPIT for SIQ dashboard

Blog – enable SAP IQ for DBACOCKPIT
Blog – How to Capture Historical Database and DBSpace Sizes in SAP HANA Cloud, data lake and SAP IQ

Blog – SAP IQ Audit Process (SAP ILM, SAP BW NLS/DTO, and Standalone SAP IQ)

If you see this, then the NLS setup is done correctly and the IQ Backup Events are in place and triggered, the IQ Database Options are set and the permissions for the affected users in SAP IQ and the primary Database are maintained correctly.

 


Is there a final conclusion?

The new and improved ABAP Transaction DBACOCKPIT for SAP IQ (second Wave is underway) will allow the customer to have much more analysis capabilities solving the problems by themselves also with the help of the mentioned SAP Notes above (choose the three important ones for you … ;-))

And imagine: there would be absolutely nothing to complain and everyone would be a specialist … 😉


Roland Kramer, SAP Platform Architect for Intelligent Data & Analytics
@RolandKramer

 

“I have no special talent, I am only passionately curious.”

 

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Thorsten Staerk
      Thorsten Staerk

      Always nice to read from you. BTW, I can only remember ONE thing at a time and that is how I love your comment on curiosity 👍

      Author's profile photo Kiran Kodre
      Kiran Kodre

      Roland: First let me thank you 'Cos looks like as far as Sybase IQ NLS information is considered your content is lot of help for many projects to resolve many issues.

      But we are having issues re-loading data from NLS to BW. There is literature on handling issues while moving data from BW to NLS IQ but there is very less information on issues while loading data back into BW. SAP must be not expecting that.

      We are getting this error "Exception occurred in line 66 of include CL_RSDA_INFOPROV_WRITER_CUBE==CM003 (program CL_RSDA_INFOPROV_WRITER_CUBE==CP)"  when we are reloading historical data from IQ to a BW Cube that is empty. We are not able to resolve this and any help is highly appreciated. (This doesn't look like duplicate records error issue).

      Here are the details of the DAP for the BW data target :-

      Selection Profile:- Time Slice Archiving

      Selection Profile: Details:-
      Characteristic for Time Slice: (0FISCPER)  Time characteristic is in key and is used as primary partitioning characteristic
      Primary Partitioning Characteristic: (0FISCPER)

      No Semantic Group

      We don't know why we are getting this error if the Cube is empty in BW and we are just trying to load the NLS data.

       

      Any help is highly appreciated Roland.

       

      -Kiran

       

      Author's profile photo Roland Kramer
      Roland Kramer
      Blog Post Author

      Hello Kiran Kodre

      "Exception  occurred in line 66 of include CL_RSDA_INFOPROV_WRITER_CUBE==CM003 (program CL_RSDA_INFOPROV_WRITER_CUBE==CP"

      => Check the IQ TEMP space

      Note 3017355 – SAP IQ 16.1 SP04 PLx – correct SAPIQDB.cfg settings

      => Check the MasterData Consistency

      Wiki - Variable Handling: SIDs Generated for New Values

      And always keep the LibDBSL up to date as mentioned in the Blog above, and IQ Server/Network Client in sync.

      Best Regards Roland