Page tree

Skip to end of metadata
Go to start of metadata

The following issues are related to the database or to the operating system:

Cannot load ianywhere error

SAP SQL Anywhere generates a cannot load ianywhere/ml/jdbcodbc/IIStatement File jdbcodbc\c\nativeobj.c at line #507--aborting execution error when the SAP SQL Anywhere server is already installed. 

This SAP SQL Anywhere related error is displayed when the SAP SQL Anywhere server is already installed. The Infrastructure Management installation is running, and the dbisqlg.exe file exists in the background processes. 

In the error message, click Yes to abort execution of the dbisqlg.exe file. To avoid this error, close the dbisqlg.exe process before you begin the installation.

Connection terminated abnormally

Connection to the database is terminated abnormally. 

Connections to the database are closed, for example, when the jserver process is restarted. This error message is displayed in the storm_ <hostName>db.log file located in the installationDirectory/pw/asatmp directory. 

No response is required. You can ignore this message.

Creation of a table fails

Creation of a table can fail when keywords that are reserved for the database are used for column headings.

You can use the register monitor script to validate whether the table is created after executing the script. When naming column headings, third-party developers might have used keywords that are reserved for the database. Ensure that no one uses the keywords that are reserved for the database. You can obtain a comprehensive list of reserved keywords from the database vendor. The following is a partial list of reserved keywords: 

  • ASA Database 
  • MESSAGE 
  • FIRST 
  • INDEX 
  • Sybase and Oracle\ Databases: 
  • SIZE 
  • LOAD 
  • LOAD_HIGH 
  • LOAD_LOW 
  • LOAD_AVG

Note

This is not a comprehensive list of keywords that are reserved for the databases mentioned previously. Developers must try to find the list of reserved words from database vendors.

Assertion failure

The database crashes after an assertion failure. 

For information about how to recover from an assertion failure, see Recovering from an assertion failure.

Incorrect page count for table

Incorrect page count is displayed after deleting pages from a table in the database.

If an incorrect page count is displayed after you delete pages from a table in the database, perform the following tasks to correct this issue: 

  1. Unload the table content. 
  2. Delete the table. If you are unable to delete the table, rename the original table and create a new table by using the original table name. 
  3. Reload the correct table content back to the table.

Reloading creates the table and adds the contents to the table.

Size of the Oracle data file

If you are using Infrastructure Management on Oracle, the size of the data file cannot exceed 3 MB. 

If you are using Infrastructure Management on Oracle, and the size of the data file exceeds 3 MB, the following error message is written to the proactivenet.log file: 

ORA-01653: unable to extend table PROACT.AUTODISCOVERY_ERRORS by 8 in tablespace NGP_TS 

Contact the Oracle administrator to create a new data file.

Installation fails due to incorrect Oracle character set

The Infrastructure Management installation fails with the following error in the installation log file: failure Error: NLS_CHARACTERSET is set to [WE8MSWIN1252]. It needs to be set to [AL32UTF8]

To resolve this issue, run the installer again and change the Oracle character set to Unicode (AL32UTF8) in the Database Configuration Assistant, Step 9 of 11: Installation Parameters screen.

Pronet_db.log file

The pronet_db.log file captures all the database activities if debug is enabled. Otherwise, it captures the SQL exceptions that occur during run time.