demystifying NLS/ILM error messages …
last changed: 21st of December, 2021
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.
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.
Example 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:
- native SAP IQ Error Messages, SAP IQ Severity Codes
- SQL error messages
- detailed ABAP Exceptions throwing by ABAP Classes (this list)
[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 , BW System Incconcisteny) [IQ Error SQL-853:24000][Sybase IQ]Cursor not in a valid state (refers to SAP Note 2982226, IQ Temp Space) Allocation failed. Dbspace IQ_SYSTEM_TEMP is OUT OF SPACE (refers to SAP Note 2982226, IQ Temp Space) 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) CL_RSDA_ADSO_ARCHIVING_REQUESTCM01Q (refers to IQ backup problems, Note 2741824) CL_RSDA_ADSO_CURSOR===========CM003 (refers to Note 3075223 - NLS Archiving limit) 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_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) CL_RSDA_NEARLINE_REQUEST======CM004 (refers to missing IQ Backup event) 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_SYB_CONNECTION_IMPL===CM006 (refers to wrong setup of RSDANLCON) CL_RSDA_SYB_CONNECTION_IMPL===CM00C (refers to Note 2482264, space problem) 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===CM02U (refers to missing IQ Backup event) 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_WRITER_STRIPED====CM002 (refers to Notes 2307267, 3116052 NLS load stripping) CL_RSSDA_FEDERATION_SERVICES==CM004 (refers to Note 1989436, insufficient priv.) CL_RSDRS_SQL_QUERY============CM01C (refers to InfoCube/aDSO Model Complexity, Note 2720236) 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 2780668 – SAP First Guidance – BW NLS Implementation with SAP IQ
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
to easy for you? I’m afraid to say, it is quite straight forward.
|Version||SP-Level||Current SP (12/2021)||Support|
|SAP BW 7.40||26||SAPKW74026||until End of 2020|
|SAP BW 7.50||22||SAPK-75022INSAPBW||until End of 2027|
|SAP BW/4 1.0||20||SAPK-10020INDW4CORE||until End of 2021|
|SAP BW/4 2.0||10||SAPK-20010INDW4CORE||until End of 2024|
|SAP BW/4 2021||0||SAPK-30001INDW4CORE||commitment until 2040|
|BW-WHM-DST-ARC||BW/4 only||BW4-DM-DTO||Program Error|
|BC-SYB-IQ||optional||BW-WHM-DBA-ADSO||archive, near-line, IQ|
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 3116052 – NLS: cursor lost during archiving in the copy phase
Blog – enable SAP IQ for DBACOCKPIT
Check that you are using the current Versions for SAP IQ Database and Network Client (SDA)
- for SAP IQ 16.1 SP04
Note 3124580 – SAP IQ 16.1 SP04 PL11 (Build 16220) Release Notes Information
Note 3124547 – SAP IQNC 16.1 SP04 PL11 (Build 16220) Release Notes Information
- for SAP IQ 16.1 SP05
Note 3077531 – SAP IQ 16.1 SP05 (Build 10160) Release Notes Information
Note 3077550 – SAP IQNC 16.1 SP05 (Build 10160) Release Notes Information
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
this is already a big fountain of possible error and problem sources, especially
- SAP IQ Database Options are missing or wrong
- SAP IQ Database User to the SAP ABAP Backend lacks of permissions
- SAP IQ Database Backup with Events
Q – the easy Installer for SAP IQ – would be an answer, but unfortunally of “official” as the result is “supported, but the way of the SAP IQ Database Installation is not.
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?
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.
SAP Help – (NetWeaver) SAP HANA Smart Data Access (SDA) for Near-Line Storage in SAP IQ
SAP Help – (HANA) SAP Authorization Objects
Third: correct ABAP Customizing for the use case
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.
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?
for now, there is no light a the end of the tunnel in sight. Never the less, the upcoming new and improved ABAP Transaction DBACOCKPIT for SAP IQ 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
“I have no special talent, I am only passionately curious.”