SAP HANA License:

SAP HANA License:

HANA License need to be purchased depends on RAM, Let’s take  example 128/256 RAM if we are using  need to purchased license for that.

And every year need to be renewal license.

Best Advantage is every year hardware part’s are getting cheaper, so that would be advantage when you are renewal of license. 

License keys are required to use SAP HANA Database. We can install and delete the license keys using subsequent methods

 - SAP HANA Studio

 - SAP HANA HDBSQL command line tool 

   HANA SQL Query Editor.

HANA License Key Types:

     The SAP HANA database supports two kinds of license key.

                    I. Temporary License Key

                    II. Permanent License Key

Temporary License Key:

            The temporary license keys are automatically installed with a new SAP HANA database installation. It is valid for 90 days from installation date. During this period we should request in service market place and apply permanent license key.

Permanent License Key:

The permanent license keys are valid until the predefined expiration date. It has to be requested on the SAP Service Marketplace under Keys & Requests and applied to the individual SAP HANA database. Furthermore they specify the amount of memory licensed to the target SAP HANA installation.

Note: Before a permanent license key expires, we should request and apply a new permanent license key. If it is expires, a temporary license key valid for 28 days is automatically installed. During this time, we can request and install a new permanent license key again.

There are two types of permanent license key available for SAP HANA

                    I.  Unenforced (SWPRODUCTNAME=SAP-HANA)

                    II. Enforced (SWPRODUCTNAME=SAP-HANA-ENF)

Unenforced License:

If an unenforced license key is installed, the operation of SAP HANA is not affected if its memory consumption exceeds the licensed amount of memory.

Enforced License:

If enforced license key is installed the system will be locked if memory consumption of HANA exceeds the license amount of memory plus some tolerance. If this happens HANA has to be restarted or a new license key should be requested, or a new license key that covers the amount of memory in use needs to be installed.

Authorization for Licensing Management

            The user required authorization of LICENSE ADMIN system privilege.

Important Points

There are a few different license models for SAP HANA depending on the business scenario (SAP HANA Stand-alone, SAP HANA Cloud, SAP Business Suite, SAP NetWeaver Business Warehouse or another Application on top of SAP HANA, etc.) and not all of them are based on memory.

If anyone have license related any questions, Please Contact with your SAP Account Executive who will gladly provide details.

Applying SAP HANA License

 For example of SAP HANA License Install and delete using the SAP HANA Studio, SAP HANA HDBSQL command line tool and HANA SQL Query Editor.

I. Installing SAP HANA License Using SAP HANA Studio

Windows: Start – All Programs – SAP HANA – SAP HANA Studio

                   

Right Click in left hand side  to Add system

Fill the required details Host Name, Instance Number, Description and Select the Locale.

Press next to Enter the User Name and Password with LICENSE ADMIN privilege User.

Press Finish Button. The screen shows HDB, SYSTEM and License(optional) are SID, User and Description

Right click on DB1 and go to Properties

Temporary License status:

License Expired status:

 Now we can generate the HANA License in Service Market Place(http://service.sap.com/license key) SMP login required.

Get the information required to request a permanent license key.

     To request the first permanent license key for a newly installed SAP HANA database, you need to provide the hardware key and the system ID. To request a subsequent permanent license key, you need the installation number and system number of your SAP HANA database. You can get the required information in the SAP HANA studio as follows:

    I.  In the Systems view, right-click the system and choose Properties – License.

    II. Get Hardware Key and you can use SQL to access the required information from the M_LICENSE system view.



The below Screen shows SAP Internal License Register:

Select your system type from below list

Select your License type:

Quantity of Memory

Download the text file

Unenforced SWPRODUCTNAME=SAP-HANA – This License file is Unenforced

Enforced SWPRODUCTNAME=SAP-HANA-ENF


Install License key in Hana Studio

Press Install License Key and Select the text file

Select License.txt file from directory where you downloaded file saved directory

Apply License Using SAP HANA HDBSQL command line tool
Login into sidadm in SAP Hana Database OS level

Copy License key from License.txt file and execute the command line SET SYSTEM LICENSE ‘<Entire License.txt file>’;

Note: Before update License in command line, we should enable multiline mode on this server using this command: \mu ON. (updated this – from Kimberley Chen’s feedback.)



Check the License status

Apply License using SAP HANA SQL Query Editor

In SQL Editor to execute the command SET SYSTEM LICENSE <License File Location>

Delete an Existing Permanent License Key

     We can delete all existing license keys in an SAP HANA database, for example, if permanent license keys with an incorrect installation number or incorrect system number were installed on the database.



Prerequisites

You have the system privilege LICENSE ADMIN.

Uninstall the license key using one of the following options:

SAP Hana Studio

     In the Systems view, right-click the system and choose Properties – License.

Choose Delete License Key.

System Lockdown

The system goes into lockdown mode in the following situations:

     1.     The temporary license key has expired.

     2.     You were using a temporary license key and the hardware key has changed.

     3.     The permanent license key has expired and you did not renew it within 28 days.

     4.     The installed license key is an enforced license key and the current memory consumption exceeds the licensed amount plus the tolerance.

     5.     You deleted all license keys installed in your database.

In lockdown mode, no queries are possible. Only a user with the system privilege LICENSE ADMIN can connect to the database and execute license-related queries, such as, obtain previous license data, install a new license key, and delete installed license keys. In addition, the database cannot be backed up in lock down mode.


Troubleshooting:

SAP Note 1738512 – HANA license expiration error still appears after successful installation of new license file while working with HANA rev25 or earlier

SAP Note 1739427 – How to request and install SAP HANA license key from SAP for more details.

HANA Administration areas:

SAP HANA LANDSCAPE:

-          SAP Components, Editions.

-          Use Cases, Scenarios and guides

  

SAP HANA Architecture:

-          SAP HANA Memory Management and Data Persistence

-          Different types of Sizing SAP HANA

-          Scale out SAP HANA

 SAP HANA Tool Overview:

-          SAP HANA studio for Administrator

-          DBA Cockpit

-          HDBSQL command line tool

HANA Installation including Pre and Post Installation steps:

-          Preparing SAP HANA installation

-          Different types of installation Scenarios

-          Post Installation steps

Operate SAP HANA:

-          Starting and stopping SAP HANA

-          Configuration of SAP HANA

-          Periodic manual tasks

-          Encryption

Backup and Recovery:

-          Concepts of Backup & Recovery

-          Data Area backup

-          Log Area backup

-          Backup of Configuration files and Backup Catalog

-          Recovery

-          Data base copy

-          High Availability

Maintaining Users and Authorizations:

-          User Management

-          Types of Privileges

-          Roles

-          Administrative  tasks

-          Authentication methods

-          Auditing

Monitoring and  Troubleshooting:

               -          Monitoring with SAP HANA Studio

-          Monitoring with DBACOCKPIT

-          Monitoring with SOLMANAGER

-          Lock concept in SAP HANA

-          Remote Support

-          SAP Early watch alert

Software lifecycle Management:

               -          Transport Changes

-          Updating SAP HANA & HANA Studio

HANA Life Cycle Manager:

               -          Updating SAP HANA

-          Updating SAP HANA Studio, SLD, Rename SID, Memory

-          Manager

Data Provisioning:

-          Configuration data replication with SAP Landscape Transformation (SLT)

SAP BW HANA Migration

SAP Certification 

HANA- In-memory Technology

SAP HANA is an in-memory, column-oriented, relational database management system developed and marketed by SAP

Its primary function as database server is to store and retrieve data as requested by the applications. In addition,
it performs advanced analytics (predictive analytics, spatial data processing, text analytics, text search, streaming analytics,
graph data processing) and includes ETL capabilities as well as an application server.

HANA Backup Strategy:

During normal database operation, data is automatically saved from memory to disk at regular save points.

Additionally, all data changes are recorded in the redo log. The redo log is saved from memory to disk with each committed database transaction. If there is a power failure, the database can be restarted like any disk-based database, and it returns to its last consistent state by replaying
the redo log since the last save-point.

While save-points and log writing protect your data against power failures, save-points do not help if the storage itself is damaged. To protect against data loss due to disk failures, backups are required. Backups save the payload (the actual data) of the data area and log area to different locations. Backups are performed while the database is running.


The backup is taken using the built-in database backup feature of SAP HANA DB.
Backup is taken like below

Complete Data (Database Full Backup)
Log Backup

• Data in SAP HANA is constantly written into disk from memory at save-points. Data-backup can be performed with database being online

To perform a data-backup in SAP HANA, below are prerequisites:

DATABASE USER: Backup in SAP HANA can only be performed with a database user, so it is necessary to create or use a existing user with the necessary privileges and authorizations

BACKUP_ADMIN: This is the system privilege that the Database user used for performing the backup should have .

CATALOG READ: System privilege that the Database user need to have for collecting the information required by the backup wizard

Data backup can be taken manually or can be scheduled. 

SAP HANA database backups up its services (nameserver,nameservertopology,indexserver,xsengine and statisticserver)

Which will be stored in a specific destination mentioned in configuration file  global.ini with the parameters

basepath_databackup and basepath_logbackup

Parameters pointing as below to the default values: 

basepath_databackup=$(DIR_INSTANCE)/backup/data used for databackup,

basepath_logbackup==$(DIR_INSTANCE)/backup/log respectively for logbackup

Backup can be performed with the below sql query

BACKUP DATA USING FILE  ('<path><prefix>')

The backup files generated by performing the databackup of SAP HANA database will be as below

COMPLETE_DATA_BACKUP_databackup_0_1

COMPLETE_DATA_BACKUP_databackup_1_1

COMPLETE_DATA_BACKUP_databackup_2_1

COMPLETE_DATA_BACKUP_databackup_3_1

COMPLETE_DATA_BACKUP_databackup_4_1

Where COMPLETE_DATA_BACKUP is the prefix(default) ,which can be changed to the required prefix while performing a data backup.

There are 3 types of Backup methods:

Full Backup: A full data backup is a complete data backup or a data snapshot of the SAP HANA data area

Incremental backup: Will be take the backup of incremental data.

Complete backup: A delta data backup covers incremental and differential data backups. In addition to this log backups are supported too.

• SQL users require the system privilege BACKUP ADMIN or BACKUP OPERATOR to perform a data backup. If you execute data backups using SAP HANA studio, the privilege CATALOG READ is also needed. It is not recommended to use the  SYSTEM user for normal database operation. Instead, we recommend that you create dedicated administration users with only the privileges necessary for backup and recovery.
• The recovery process can only be started by the operating system user <sid>adm.
• Data and log areas can only be backed up when the SAP HANA database is online. During data and log backup,  the system is available as usual.

• All the configured services must be running such as indexserver, statisticsserver, etc.
•  Backup can be executed using an arbitrary SQL interface like hdbsql. In addition SAP HANA  database provides with the SAP HANA studio and the web-based SAP HANA cockpit two powerful UIs to fulfil that task. In addition DBA cockpit (ABAP stack only) can be used too.
• Backup and recovery always applies to the whole database. It is not possible to back up or recover individual database objects.

Data backup:

By default, data backups are written to the following destination: $DIR_INSTANCE/backup/data. You can specify a different destination when you perform the backup. Alternatively, you can change the default backup destination in the Backup section in SAP HANA studio.

To change the default destination for data backups:

1. In SAP HANA studio, go to Backup.

2. Go to the Configuration tab and choose Data Backup Settings.

3. Specify the new default destination in the Destination field.

4. Save.

Different data backups can be written to different destinations, but all the parts of one particular data backup are written to the same destination.

Log backup:

By default, log backups are written to the following destination: $DIR_INSTANCE/backup/log. You can change the backup destination in the Backup editor in SAP HANA studio.

To change the default destination for log backups:

1. In SAP HANA studio, go to Backup.

2. Go to the Configuration tab and choose Log Backup Settings.

3. Specify the new default destination in the Destination field.

4. Save.

In general changes to the data or log backup destinations take effect immediately.


Each backup name comprises the following elements: <path><prefix>

If no complete path is specified, the default backup destination is prepended to the backup name. For file-based backups, the backups are written to a destination in the file system. For backups made using third-party backup tools, a pipe is created in the file system. The pipe is always created in the directory /usr/sap/<SID>/SYS/global/hdb/backint. The backup tool decides where the backups are actually written.

You can use the prefix proposed by the system or you can specify a different prefix for the backup name. During backup, each service backs up its data to the specified backup destination.

Below is an example of a set of backup files from one data backup created with SAP HANA studio. The backups can have different names.

/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1 (name server topology)
/backup/data/COMPLETE_DATA_BACKUP_databackup_1_1 (name server)
/backup/data/COMPLETE_DATA_BACKUP_databackup_2_1 (for example, index server)...
In the above example, the <path> is /backup/data/, the <prefix> is COMPLETE_DATA_BACKUP. databackup_0_1 is the suffix, which is automatically added by the system.

• To estimate the size of a data backup, table M_CONVERTER_STATISTICS. This system table contains the number of currently used blocks. To estimate the size of the next complete data backup, you can use either of the following SQL commands:

           select sum(allocated_page_size) from M_CONVERTER_STATISTICS

• The backup catalog provides information about the execution of backups, recoveries and their history.  It enables the system to determine whether a recovery is possible and to choose which data and log backup to use to recover the database.
• The monitoring views M_BACKUP_CATALOG and M_BACKUP_CATALOG_FILES can be used to display information about the backup catalog. 
• The system privilege CATALOG READ is needed for this.

•      After the initial load has finished successfully, a data backup is strongly recommended.
•      It is recommended to perform a backup (including configuration files) before the database      software is upgraded to a new version. 
•    If the software upgrade fails, the database can then be recovered with no data loss.
• After adding or removing a host or a service, a data backup is recommended.

To ensure that you can recover your database to the most recent point in time without needing to replay a large number of log backups, you should perform data backups at regular intervals.

Archiving of log backups should be part of your overall backup strategy.

The configuration files are not backed up as part of the database backup.

Configuration files that contain customer-specific changes can be backed up manually in order to more easily identify and restore customer-specific changes in a recovery situation.

Configuration files that contain customer-specific changes are located by default in the following directories:

   For global configuration settings:

  $DIR_INSTANCE/.. /SYS/global/hdb/custom/config
  For host-specific configuration settings:

$SAP_RETRIEVAL_PATH

Configuration files are only created in these directories if customer-specific changes are made to them after installation.

If no customer-specific changes have been made, these directories may be empty.

Automatic log backup can be enabled or disabled using parameter enable_auto_log_backup. By default, automatic log backup is enabled.

 During normal system operation (log mode normal), it is recommended that automatic log backup be kept activated.
 
If automatic log backup is disabled, the log area grows until the file system is full. If the file system is full, the database will freeze until the situation is resolved.


Log Modes:


After changing the log mode parameter, it is strongly recommended to create a full data backup of the database. If you use a HANA revision older than revision 90 you have to restart the database to activate the changes.

This parameter can have the following values:

log_mode = normal (default)
Log segments are automatically backed up if automatic log backup is enabled.
log_mode = normal is recommended to provide support for point-in-time recovery.

log_mode = overwrite
Log segments are freed by savepoints and no log backup is performed. This can be useful for test installations that do not need to be backed up or recovered.
log_mode = overwrite is not recommended for production systems. No point-in-time recovery is possible. For recovery, only data backups are used; the logs must be disregarded.

Log Backup Timeout

You can specify a timeout for log backups. The timeout determines the intervals at which the logs are backed up. If the log segments become full before the timeout, the logs will be backed up anyway. If the timeout exceeds but the log segment contains no commit entry, the log segment will not be backed up at this point in time. The log backup timeout is controlled by the parameter log_backup_timeout_s.

Specifying an appropriate time interval for log backups enables you to recover a SAP HANA database with minimum data loss. For example, if you need to recover the database in a situation where the log area is unusable, and only the data and log backups are available.

Recommended: Specify a time interval. For example 900s.

If you specify a timeout 0, the log backups are only made when a log segment is full and when services are restarted.

Note: The backup timeout only takes effect if automatic log backups are enabled.

Do not delete log segments on operating system level, as the log area will become unusable and the database may stop working immediately.



SAP HANA RECOVERY:


When either data or log area becomes unusable because of hardware failure or some other issues.For  recovering SAP HANA database one has to recover using the last available data backup and by replaying the log backup
When some logical error occurs ,which requires the database to be recovered to point in time of failure,which requires the databack up to be recovered and log entries from the log ckup has to be replayed

Pre-prerequisites for recovery:

-> <sid>adm:user password is required to shutdown the target system where the backups have to be recovered upon
-> Similar configuration:between source and target system ,if backups are to be recovered on different target system

-> Atleast one databackup and logbackups taken before the system failure or the time to which the system needs to be recovered
Recovery Types
Available Recovery types option with SAP HANA

Recovering the database to the most recent state:used for recovering the database to the time as close as possible to the current time . Databackup ,logbackup available since last databbackup and log area are required to perform the above type recovery
Recovering the database to the point in time :used for recovering the database to the specific point in time. . Databackup ,logbackup available since last databbackup and log area are required to perform the above type recovery
Recovering the database to specific database:Used for recovering the database to a specified data backup.specificdatabackup is required for the above type of recovery option.
Backup and recover using HANA studio


To Backup using SAP HANA Studio
From the context menu choose Backup  option, choose the backup destination path and backup prefix then choose finish.
To recover using SAP HANA Studio
From the context menu choose Recovery option ,provide<SID>adm username and password and then choose the required recovery type.Then specify the location of the required backup files(databackup and logbackup).Install the license and finish the process.

Note 1:Constraints that applies with recovery of SAP HANA database are

Recovery of the backup from higher system release to lower system release is not possible.
Recovery can’t be interrupted or stopped in between ,once it is triggered
-> SAP HANA studio provides point-in-time recovery with full GUI support.

In a recovery situation, you can use SAP HANA studio to restore customer-specific changes (configuration settings) either before or at the end of the recovery. To recover your database from SAP HANA studio -> navigator view -> open context menu of the database -> choose "Recover...". Confirm that the database can be shut down - recovery is only done when the database is offline. In the recovery wizard choose one of the recovery types:

Recover the database to its most recent state.
Recover the database to a certain point in time.
Recover the database to a specific data backup. (Just a specific data backup is used for recovery; Log entries are not replayed neither from the log backups nor from the log area.)
Caution: The SAP HANA database will be initialized with the specified data backup. This backup becomes the first backup of a new database life cycle. Older backups are not compatible with the log written after the recovery.

Recover the database to a certain log position. (Advanced option to be used in exceptional cases if a previous recovery failed.)
The SAP HANA database uses the backup catalog to identify the destination of the backups. You do not need to specify whether File or Backint was used for the backup.

• Online Revcovery is not possible; Database recovery is always a full recovery of the whole database and therefore always requires a downtime.   
• SAP HANA studio shows the progress of the recovery and reports when it is finished.
•  Also we can cancel a recovery while it is running. However, canceling a recovery makes the database inconsistent. To be able to work with the database, a further recovery would then be necessary

Backup or recovery problems, Below is the log/trace files location:

content of directory $SAP_RETRIEVAL_PATH/trace as minimum backup.log, backint.log (if you are using a third-party backup tool) and all *.trc files
list of the content (recursive) of your backup directories, typically $DIR_INSTANCE/backup

HANA -SQL Error Codes

The following table lists error codes displayed by SAP HANA database and their descriptions.

Error Code	Description
1	General warning
2	General error
3	Fatal error
4	Cannot allocate enough memory
5	Initialization error
6	Invalid data
7	Feature not supported
8	Invalid argument
9	Index out of bounds
10	Invalid username or password
11	Invalid state
12	Cannot open file
13	Cannot create/write file
14	Cannot allocate enough disk space
15	Cannot find file
16	Statement retry
17	Metadata schema version incompatible between database and executable file
18	Service shutting down
19	Invalid license
128	Transaction error
129	Transaction rolled back by an internal error
130	Transaction rolled back by integrity constraint violation
131	Transaction rolled back by lock wait timeout
132	Transaction rolled back due to unavailable resource
133	Transaction rolled back by detected deadlock
134	Failure in accessing checkpoint file
135	Failure in accessing anchor file
136	Failure in accessing log file
137	Failure in accessing archive file
138	Transaction serialization failure
139	Current operation cancelled by request and transaction rolled back
140	Invalid write-transaction identifier
141	Failure in accessing invisible log file
142	Exceed max num of concurrent transactions
143	Transaction serialization failure until timeout expires
144	Transaction rollback, unique constraint violated
145	Transaction distribution work failure
146	Resource busy and acquire with NOWAIT specified
147	Inconsistency between data and log
148	Transaction start is blocked until Master_Restart finishes
149	Distributed transaction commit failure
150	Statement cancelled due to old snapshot
256	SQL processing error
257	SQL syntax error
258	Insufficient privilege
259	Invalid table name
260	Invalid column name
261	Invalid index name
262	Invalid query name
263	Invalid alias name
264	Invalid datatype
265	Expression missing
266	Inconsistent datatype
267	Specified length too long for its datatype
268	Column ambiguously defined
269	Too many values
270	Not enough values
271	Duplicate alias
272	Duplicate column name
273	Not a single character string
274	Inserted value too large for column
275	Aggregate function not allowed
276	Missing aggregation or grouping
277	Not a GROUP BY expression
278	Nested group function without GROUP BY
279	Group function is nested
280	ORDER BY item must be the number of a SELECT-list
281	Outer join not allowed in operand of OR or IN
282	Two tables cannot be outer-joined to each other
283	A table may be outer joined to at most one other table
284	Join field does not match
285	Invalid join condition
286	Identifier is too long
287	Cannot insert NULL or update to NULL
288	Cannot use duplicate table name
289	Cannot use duplicate index name
290	Cannot use duplicate query name
291	Argument identifier must be positive
292	wrong number of arguments
293	Argument type mismatch
294	Cannot have more than one primary key
295	Too long multi key length
296	Replicated table must have a primary key
297	Cannot update primary key field in replicated table
298	Cannot store DDL
299	Cannot drop index used for enforcement of unique/primary key
300	Argument index is out of range
301	Unique constraint violated
302	Invalid CHAR or VARCHAR value
303	Invalid DATE, TIME or TIMESTAMP value
304	Division by zero undefined
305	Single-row query returns more than one row
306	Invalid cursor
307	Numeric value out of range
308	Column name already exists
309	Correlated subquery cannot have TOP or ORDER BY
310	SQL error in procedure
311	Cannot drop all columns in a table
312	Sequence is exhausted
313	Invalid sequence
314	Numeric overflow
315	Invalid synonym
316	wrong number of arguments in function invocation
317	P_QUERYPLANS not exists nor valid format
318	Decimal precision specifier is out of range
319	Decimal scale specifier is out of range
320	Cannot create index on expression with datatype LOB
321	Invalid view name
322	Cannot use duplicate view name
323	Duplicate replication ID
324	Cannot use duplicate sequence name
325	Invalid escape sequence
326	CURRVAL of given sequence is not yet defined in this session
327	Cannot explain plan of given statement
328	Invalid name of function or procedure
329	Cannot use duplicate name of function or procedure
330	Cannot use duplicate synonym name
331	User name already exists
332	Invalid user name
333	Column not allowed
334	Invalid user privilege
335	Field alias name already exists
336	Invalid default value
337	INTO clause not allowed for this SELECT statement
338	Zero-length collumns are not allowed
339	Invalid number
340	Not all variables bound
341	Numeric underflow
342	Collation conflict
343	Invalid collate name
344	Parse error in data loader
345	Not a replication table
346	Invalid replication ID
347	Invalid option in monitor
348	Invalid datetime format
349	Cannot CREATE UNIQUE INDEX
350	Cannot drop columns in the primary-key column list
351	Column is referenced in a multi-column constraint
352	Cannot create unique index on CDX table
353	Update log group name already exists
354	Invalid update log group name
355	The base table of the update log table must have a primary key
356	Exceed maximum number of update log group
357	The base table already has a update log table
358	Update log table can not have a update log table
359	Concatenated string is too long
360	View WITH CHECK OPTION where-clause violation
361	Data manipulation operation not legal on this view
362	Invalid schema name
363	Number of index columns exceeds its maximum
364	Invalid partial key size
365	No matching unique or primary key for this column list
366	Referenced table does not have a primary key
367	Number of referencing columns must match referenced columns
368	Unique constraint not allowed on temporary table
369	Exceed maximum view depth limit
370	Cannot perform DIRECT INSERT operation on table with unique indexes
371	Invalid XML document
372	Invalid XPATH
373	Invalid XML duration value
374	Invalid XML function usage
375	Invalid XML index operation
376	Python stored procedure error
377	JIT operation error
378	Invalid column view
379	Table schema mismatch
380	Fail to change run level
381	Fail to restart
382	Fail to collect all version garbage
383	Invalid identifier
384	Constant string is too long
385	Could not restore session
386	Cannot use duplicate schema name
387	Table ambiguously defined
388	Role already exists
389	Invalid role name
390	Invalid user type
391	Invalidated view
392	Can't assign cyclic role
393	Roles must not receive a privilege with grant option
394	Error revoking role
395	Invalid user-defined type name
396	Cannot use duplicate user-defined type name
397	Invalid object name
398	Cannot have more than one order by
399	Role tree too deep
400	Primary key not allowed on insert-only table
401	Unique constraint not allowed on insert-only table
402	The user was already dropped before query execution
403	Internal error
404	Invalid (non-existent) structured privilege name
405	Cannot use duplicate structured privilege name
406	INSERT, UPDATE and UPSERT are disallowed on the generated field
407	Invalid date format
408	Password or parameter required for user
409	Multiple values for a parameter not supported
410	Invalid privilege namespace
411	Invalid table type
412	Invalid password layout
413	Last n passwords can not be reused
414	User is forced to change password
415	User is deactivated
416	User is locked
417	Can't drop without CASCADE specification
418	Invalid view query for creation
419	Can't drop with RESTRICT specification.
420	Password change currently not allowed
421	Cannot create fulltext index
422	Privileges must be either all SQL or all from one namespace
423	LiveCache error
424	Invalid name of package
425	Duplicate package name
426	Number of columns mismatch
427	Cannot reserve index ID any more
428	Invalid query plan ID
429	Integrity check failed
430	Invalidated procedure
431	User's password will expire within few days
432	This syntax has been deprecated and will be removed in next release
433	Null value found
434	Invalid object ID
435	Invalid expression
436	Could not set system license
437	Only commands for license handling are allowed in current state
438	Invalid user parameter value
439	Composite error
440	Table type conversion error
441	This feature has been deprecated and will be removed in next release
442	Number of columns exceeds its maximum
443	Invalid calculation scenario name
444	Package manager error
512	Replication error
513	Cannot execute DDL statement on replication table while replicating
514	Failure in accessing anchor file
515	Failure in accessing log file
516	Replication table has not conflict report table
517	Conflict report table already enabled
518	Conflict report table already disabled
576	API error
577	Cursor type of forward is not allowed
578	Invalid statement
579	Exceed maximum batch size
580	Server rejected the connection(protocol version mismatch)
581	This function can be called only in the case of single statement
582	This query does not have result set
583	Connection does not exist
584	No more lob data
585	Operation is not permitted
586	Invalid parameter is received from server
587	Result set is currently invalid
588	Next() is not called for this result set
589	Too many parameters are set
590	Some paramters are missing
591	Internal error
592	Not supported type conversion
593	Remote-only function
594	No more result row in result set
595	Specified parameter is not output parameter
596	LOB streaming is not permitted in auto-commit mode
597	Session context error
598	Failed to execute the external statement
599	Session layer is not initialized yet
600	Failed routed execution
601	Too many session variables are set
602	Cannot set readonly session variable
603	Invalid LOB
604	Remote temp table access failure
605	Invalid XA join request
606	Exceed maximum LOB size
607	Failed to cleanup resources
608	Exceed maximum number of prepared statements
1024	Session error
1025	Communication error
1026	Cannot bind a communication port
1027	Communication initialization error
1028	I/O control error
1029	Connection failure
1030	Send error
1031	Receive error
1032	Cannot create a thread
1033	Error while parsing protocol
1034	Exceed maximum number of sessions
1035	Not supported version
1036	Invalid session ID
1037	Unknown hostname
1280	SqlScript error
1281	Wrong number or types of parameters in call
1282	Output parameter not avariable
1283	OUT and IN OUT parameters may not have default expressions
1284	Duplicate parameters are not permitted
1285	At most one declaration is permitted in the declaration section
1286	Cursor must be declared by SELECT statement
1287	Identifier must be declared
1288	Expression cannot be used as an assignment target
1289	Expression cannot be used as an INTO-target of SELECT/FETCH statement
1290	Expression is inappropriate as the left hand side of an assignment statement
1291	Expression is of wrong type
1292	Illegal EXIT statement, it must appear inside a loop
1293	Identifier name must be an exception name
1294	An INTO clause is expected in SELECT statement
1295	EXPLAIN PLAN and CALL statement are not allowed
1296	Identifier is not a cursor
1297	Wrong number of values in the INTO list of a FETCH statement
1298	Unhandled user-defined exception
1299	No data found
1300	Fetch returns more than requested number of rows
1301	Numeric or value error
1302	Parallelizable function cannot have OUT or IN OUT parameter
1303	User-defined exception
1304	Cursor is already opened
1305	Return type is invalid
1306	Return type mismatch
1307	Unsupported datatype is used
1308	Illegal single assignment
1309	Invalid use of table variable
1310	Scalar type is not allowed
1311	Out parameter is not specified
1312	At most one output parameter is allowed
1313	Output parameter should be a table or a table variable
1314	Inappropriate variable name: do not allow "" for the name of variable or parameter
1315	Return result set from select stmt exist when result view is defined
1316	Some out table var is not assigned
1317	Function name exceedes max. limit
1318	Built-in function not defined
1319	Parameter must be a table name
1320	Parameter must be an attribute name without a table name upfront
1321	Parameter must be an attribute name without an alias
1322	CE_CALC not allowed
1323	Parameter must be a vector of columns or aggregations
1324	Join attribute must be available in projection list
1325	Parameter must be a vector of SQL identifiers
1326	Duplicate attribute name
1327	Parameter has a non supported type
1328	Attribute not found in column table
1329	Duplicate column name
1330	Syntax Error for calculated Attribute
1331	Syntax Error in filter expression
1332	Parameter must be a valid column table name
1333	Join attributes not found in variable
1334	Input parameters do not have the same table type
1335	Cyclic dependency found in a runtime procedure
1336	Unexpected internal exception caught in a runtime procedure
1337	Variable depends on an unassigned variable
1338	CE_CONVERSION: customizing table missing
1339	Too many parameters
1340	The depth of the nested call is too deep
1536	Swapx error
1537	This table has no swap space
1538	Swap already activated
1539	Swap not yet activated
1540	Swap space is not created
1541	Failure in unpinning a swap page
1542	Failure in swap file
1543	Failure in accessing swap data file
1544	Failure in accessing swap log file
1545	Swap buffer overflow
1546	Swap buffer reservation failure
1792	Shared memory error
1793	Invalid key or invalid size
1794	The segment already exists
1795	Exceed the system-wide limit on shared memory
1796	No segment exists for the given key, and IPC_CREAT was not specified
1797	The user does not have permission to access the shared memory segment
1798	No memory could be allocated for segment overhead
1799	Invalid shmid
1800	Allow read access for shmid
1801	Shmid points to a removed identifier
1802	The effective user ID of the calling process is not the creator
1803	The GID or UID value is too large to be stored in the structure
1804	The user does not have permission to access the shared memory segment
1805	Invalid shmid
1806	No memory could be allocated for the descriptor or for the page tables
1807	Unknown shared memory error
2048	Column store error
2049	Primary key is not specified for column table
2050	Not supported ddl type for column table
2051	Not supported data type for column table
2052	Not supported dml type for column table
2053	Invalid returned value from attribute engine
2304	Python DBAPI error
2305	Interface failure
2306	Programming mistake
2307	Invalid query parameter
2308	Not supported encoding for string
2560	Distributed metadata error
2561	DDL redirect error
2562	DDL notification error
2563	DDL invalid container ID
2564	DDL invalid index ID
2565	Distributed environment error
2566	Network error
2567	Metadata update not supported in slave
2568	Metadata update of master indexserver is failed
2816	SqlScript Error
2817	SqlScript Builtin Function
2818 - 2889	SqlScript
3584	Distributed SQL error
3585	Expression shipping failure
3586	Operator shipping failure
3587	Invalid protocol or indexserver (statisticsserver) shutdown during distributed query execution
3588	Sequence shipping failure
3589	Remote query exectuion failure
3840	general auditing error
3841	Invalid privilege
3842	Audit trail writer is blocked
3843	Audit policy with current name already exists
3844	Invalid combination of audit actions
3845	Invalid action status for auditing
3846	Invalid auditing level
3847	Invalid policy name
4096	General error in the process of stored plan
4097	Invalid operation in generating plans
4098	Invalid operation in execution the chosen plan
4099	Invalid operation in storing the pinned plan
4100	Invalid operation in loading the stored plan
4101	Invalid operation in deleting the chosen plan
4103	Failed to prepare for runtime reorganization
4104	Transaction blocked since runtime reorganization is in progress
4105	ERR_REORG_TRANS_EXISTS_GENERAL. Cannot start reorganization due to the transactions in execution