Database Issues

Release Notes › Known Issues › Previous versions issues › Database Issues

Database Issues

36171

Incorrect settings of the NLS_LANG parameter may result in a failed installation (schema creation error), ORA-01843 errors and/or other errors when installing the database.

To resolve:

Determine the character set to use for your database instance.
CA Business Service Insight [assign the version number for your book] supports both the AL32UTF8 and the WE8MSWIN1252 character sets.
- CA strongly recommends using the AL32UTF8 character set for new deployments.
Use of the WE8MSWIN1252 character set in your database instance prevents use of strings containing non-western European characters.

Note: For the database to store strings containing non-western European characters you must use the AL32UTF8 character set.
Set the NLS_LANG parameter.
You must use the identical parameter for the database instance and all CA Business Service Insight servers (Web, Application, Database).

The NLS_LANG parameter is made up of three parts: language, territory, character set. The format is: <language>_<territory>.<characterset>.

Example_1: AMERICAN_AMERICA.WE8MSWIN1252

Example_2: AMERICAN_AMERICA.AL32UTF8

Notes:
The NLS_LANG parameter must be set in the registry prior to installation of the database instance. The exact location in the registry depends on the specific Oracle version installed and the OS. Refer to your Oracle documentation for the exact location.
- For specific information on how to set the NLS_LANG parameter refer to your official Oracle documentation.

N/A	There is a known issue where when migrating an Oracle 11g database from versions lower than 8.0, the migration process might fail due to incorrect value in the o7_dictionary_accessibility parameter.

To resolve:

Before running the migration, run the following query while connected to the database as "sysdba":
```
select value from v$parameter where name = upper('o7_dictionary_accessibility’);
```
If the result is “FALSE”, run the following commands to change it to “TRUE” (restart of the database is needed) in sql*plus while connected to the database as sysdba.
```
alter system set o7_dictionary_accessibility=TRUE scope=spfile;
shutdown immediate
startup
```

Make sure the parameter was changed by running the following command:

select value from v$parameter where name = upper('o7_dictionary_accessibility’);

After running the migration successfully, run the following commands to change the parameter back to “FALSE” (restart of the database is needed) in sql*plus while connected to the database as sysdba.
```
alter system set o7_dictionary_accessibility=FALSE scope=spfile;
shutdown immediate
startup
```

Make sure the parameter was changed by running the following command:

select value from v$parameter where name = upper('o7_dictionary_accessibility’);

N/A	When running CA Oblicore Guarantee SQL scripts not via the supplied batch or shell files, the value of the nls_length_semantics parameter may be overridden for the duration of the current session by the configuration of the tool used to access the database. This may cause the character fields of newly created or modified tables to have the wrong length.
N/A	The path to the folder under which the database files are created cannot contain spaces.

General Issues

N/A	Errors issued by the Content Transfer Tool, OMV, SMI and the ACE2 Manager component to the log are not available for alerts.

Enhanced Reporting

The Enhanced Reporting add-in for Word fails on Office 2007 and on Windows XP.

An error is generated when uploading a *.docx file containing an invalid, hyperlinked, URL (colored blue) to generate a new document repository. For example, the URL \\bhb@hbh\vgvgvgv <file:///\\bhb@hbh\vgvgvgv> would generate the error.

The issue is known and has been reported in the literature; it results when opening the document using the SDK object: WordprocessingDocument.Open(EntityProvider.GeneratedFilePath, true)