Installation and Upgrade Guides › Policy Server Installation Guide › Prerequisites for Running Reports Using Crystal Reports › How to Configure the Policy Server for Crystal Reports › Create the Oracle Database Schema For Logging

Create the Oracle Database Schema For Logging

You may have already created an Oracle logging database when you created the Oracle database with the SiteMinder schema. If you already created a logging database, do not run sm_oracle_logs.sql again, as it will overwrite the current database with a new one.

If you are using Oracle to store reports information, run the sm_oracle_logs.sql script to create a schema for logging. If there is no schema in the database to log data, reports will not work. This script is included in the <siteminder_installation>\db\SQL directory.

siteminder_installation

Specifies the installed location of SiteMinder.

To create the Oracle database schema for logging

1. Make sure the Oracle database instance that will contain the SiteMinder logs data is accessible from the Policy Server machine. Test the communication using tnsping or sqlplus.
2. Create the SiteMinder schema in the Oracle database:
   1. Log in to Oracle with sqlplus (or some other Oracle utility) as the user who administers the Policy Server database information.
   2. Import the script to create a schema for logging:

      $NETE_PS_ROOT/db/sql/sm_oracle_logs.sql

      Note: If you are using sqlplus, run the schema using an @ sign.

      Example: @$NETE_PS_ROOT/db/sql/sm_oracle_logs.sql

   Note: Environment variables may not function in Oracle's SQL utility. If you encounter problems when using the utility, specify an explicit path for $NETE_PS_ROOT rather than one with an environment variable.

3. Create the Oracle database schema for stored procedures.

Note: The 6.x Policy Server and OneView Monitor services still start even if they are unable to connect to the audit logs database.

More Information:

Create the Oracle Database Schema For Stored Procedures