Installation Guides › Policy Server Installation Guide › Configuring SOA Security Manager Data Stores in a Relational Database › Important Considerations
Important Considerations
Consider the following before configuring a policy store:
- Avoid possible policy store corruption—Be sure that the database server that is to host the policy store is configured to store objects in UTF-8 form:
- (Oracle) Be sure that the database is configured to store objects in UTF-8 form. Oracle supports unicode within many of their character sets. For more information about configuring your database to store objects in UTF-8 form, see your vendor-specific documentation.
- (SQL Server) Be sure that the database is configured using the default collation (SQL_Latin1_General_CP1_CI_AS). Using a collation that is case sensitive can result in unexpected behaviors. For more information about configuring your database to store objects using the default collation, see your vendor-specific documentation.
- Do not use brackets around the IP address when using IPv6 ODBC data sources or the connection fails.
Example: Use fec0::9255:20c:29ff:fe47:8089 instead of [fec0::9255:20c:29ff:fe47:8089]
Note: For more information about IPv6-supported databases, see the SOA Security Manager r12.1 SP3 Platform Support Matrix on the Technical Support site.
More information:
Locate the SOA Security Manager Platform Support Matrix