Skip to main content

Database Administration

This page contains advice and answers to frequently asked questions regarding the patching and administration of a Hazid Integrity database connection. A Hazid Integrity database can be deployed using the Oracle or MSSQL database engine, it is therefore important to follow the relevant advice for your deployment.

When using the Configuration Tool logs will be produced for patching errors that can be interrogated in your application data

"%APPDATA%\Hazid Technologies\Logs\ConfigToolError.log"

Oracle Upgrade Instructions​

When upgrading or installing an Integrity database deployment using the Oracle database engine the 'max_string_size' parameter must be set to 'EXTENDED' to enable the application of project patch PRJ_118.

Preliminary Steps​

Ensure all users are logged out of the database Access the database machine as the user set up to manage the database. For instance, on Linux, this user is often named “oracle” by default.

Check Existing Parameter Setting​

Run SQLPlus as a System User (sqlplus / as sysdba)

Check the Current Setting of ‘max_string_size’ 

SELECT NAME, VALUE FROM V$PARAMETER WHERE NAME='max_string_size'

alternatively, you may use

SHOW PARAMETER max_string_size;

Evaluate the Result – If the value of ‘max_string_size’ is ‘STANDARD’, proceed to the next steps to update the parameter.

Alter System for Container Based Instances (Oracle v18+)​

Run the following commands to update the Parameter for Container Based Instances (Oracle v18+) 

 1. SHUTDOWN IMMEDIATE;   
 2. STARTUP UPGRADE; 
 3. ALTER SYSTEM SET MAX_STRING_SIZE=’EXTENDED’;
 4. SHUTDOWN IMMEDIATE;
 5. STARTUP MOUNT; 
 6. ALTER DATABASE OPEN MIGRATE;  
 7. @?/rdbms/admin/utl32k.sql  
 8. SHUTDOWN IMMEDIATE; 
 9. STARTUP;

MSSQL Upgrade Instructions​

When upgrading an existing MSSQL Integrity database deployment existing database users must be granted the REFERENCES permission to schemas they have access. In a typical Hazid Integrity database install the <SCHEMA_NAME> will be identical to the <USER_NAME>

GRANT REFERENCES ON SCHEMA::[<SCHEMA_NAME>] TO [<USER_NAME>] AS [dbo]

FAQ​

ORA-43922: Collation of the column cannot be modified​

This issue only applys to Oracle databases.

When applying patch PRJ_118 to a project connection you may run into this error if you have not followed the steps detailed in the Upgrade Instructions to set 'max_string_size' to 'EXTENDED'.

The REFERENCES permission was denied on the object 'ACTION_NUMBER_SEQ', database '<DATABASE_NAME>, schema '<SCHEMA_NAME>'.​

This issue only applies to MSSQL databases.

When applying patch RES_031 to a results connection you may run into this error if you have not followed the steps detailed in the Upgrade Instructions where your users must be granted the REFERENCES permission for their schema.