Known issues in Content Manager
The following list describes issues that are known to exist in Content Manager.
- Search does not find unicode characters in a Format Area
- When you search in a Format Area, search does not find unicode characters.
- Search issues
-
- No operator precedence
- Search queries that combine the AND and OR operators may lead to unexpected results, because the search engine does not use operator precedence. Users using search should use unary operators such as + instead.
- CONTAINS search finds the reversed string
-
When searching with the CONTAINS operator, for example, when searching for
Title CONTAINS abc, the search engine also returns the reversed string, that is, a string containingcba. - Spaces in Format Areas cannot be found
-
When searching for a string containing a space, for example, "pizza margherita", in a Format Area, the string will not be found because the Format Area space is actually the HTML
character. Users need to search for "pizza margherita" instead.
- Oracle issues
-
- Oracle does not install 32-bit policy files on a double client installation
-
This issue only occurs if your Oracle version is 11.2.0.1.2 or higher, but lower than 11.2.0.2. If both the 32-bit and 64-bit Oracle clients are installed, no policy files for the x86 version of the client software is installed. This is a known Oracle bug which was fixed in 11.2.0.2. If your version is lower than 11.2.0.2, you must register assembles for policy DLLs manually. For more information, refer to the Oracle bug in question:
Oracle Bug 9953792: 64-BIT POLICY DLLS REMOVED FROM GAC_64 AFTER INSTALL 32-BIT CLIENT. - String length in Oracle in bytes rather than characters
- In Oracle, column length constraints can be specified in bytes rather than in characters. If this is the case, the actual maximum number of characters depends on the kinds of characters you use.