This chapter describes issues associated with Oracle Adaptive Access Manager. It includes the following topics:
This section describes general issue and workarounds. It includes the following topic:
"Last Used On" Column Does Not Sort in Fingerprint Details Page
ADF Exceptions When Incorrect Password Entered for OAAM Admin
Due to a bug, you cannot sort on the "Last Used On" column for the tabs in the Fingerprint Detail.
When a user tries to log in to the OAAM Admin Console with incorrect passwords, ADF exceptions appear in the log. They do not impact the functionality.
The alert messages in the standard policies packaged with Oracle Adaptive Access Manager support a number of languages. However, the alert messages are not globalized.
The Oracle BI Publisher report RecentLogins is impacted by this issue. The alert messages from the out-of-the-box policies that appear in the RecentLogins report will not follow the report's locale settings.
This section describes scheduler issues and their workarounds. It includes the following topics:
Altering the Schedule Parameters Does Not Affect Next Recurrence
Pause and Cancel Job Status Does Not Appear in Job Instance Tab
Altering the schedule parameters of a Scheduled Task does not have any effect for the next recurrence if the start date/time is not changed.
The Pause and Cancel Job statuses are not shown in the Job Instance tab when a job is canceled or paused.
This section describes audit and reporting issues and their workarounds. It includes the following topics:
The Commit Snapshot Diff event detail does not fit entirely into the data field because event logs are part of the audit information. Since snapshot data can be large, it is not practical to log all data to the audit log. Hence for audit purpose, data that is larger than the available audit event data space may appear truncated in the audit event.
The following are issues in the BI Publisher Search Transactions Report:
When all transaction types are selected, the common Transaction and Entity fields should be available in the drop down lists. In BI Publisher, the drop down lists are empty when a specific transaction type is not selected.
The Transaction field, Transaction Value field, Entity field, and Entity Value field may not be intuitive to the user. For example, when the user selects an attribute from the Transaction field, he must enter the value in the Transaction Value field when there is another Transaction Value 2 field. Incorrect results are displayed if the values are interchanged.
Transaction 2 field does not have a drop down lists. The user is unable to manually enter the attribute if he wants to search by the second Transaction field.
The results page does not display the searched attributes. For example, the user searches by Entity Field: Creditcard Number with Value:1111. The credit card information is not available in the results page. The Session ID and Transaction ID are shown as hyperlinks and when clicked, the user is redirected to an error page.
This section describes configuration issues and their workarounds. It includes the following topics:
The transaction definition is not updated when linking an entity to one that has been added to a transaction. The workaround is to configure the transaction definition in this order:
Configure entities.
Link entities.
Add entity instances to transactions.
While loading the OAAM partition RCU schemas, the following error messages are generated in the oaam_partn.log :
SP2-0606: Cannot create SPOOL file "db_setup.lis"
SP2-0606: Cannot create SPOOL file "cr_vcrypt_obj.lis"
SP2-0606: Cannot create SPOOL file "vr_policy_init.lis"
SP2-0606: Cannot create SPOOL file "v_user_init.lis"
SP2-0606: Cannot create SPOOL file "v_scorepolicy.lis"
SP2-0606: Cannot create SPOOL file "cr_v_Q_global.lis"
SP2-0606: Cannot create SPOOL file "cr_vcrypt_config.lis"
SP2-0606: Cannot create SPOOL file "cr_v_ans_hint.lis"
SP2-0606: Cannot create SPOOL file "cr_v_b_locale.lis"
SP2-0606: Cannot create SPOOL file "oaam_db_patch_oracle_10_1_4_5_01.log"
SP2-0606: Cannot create SPOOL file "oaam_db_patch_oracle_10_1_4_5_02.log"
SP2-0606: Cannot create SPOOL file "create_monitor_rollup.lst"
SP2-0606: Cannot create SPOOL file "oaam_db_patch_oracle_10_1_4_5_07.log"
The error message occurs because the spooling of the OAAM partition to the file does not occur. Functionality is not impacted and the message can be safely ignored.
When running the create_purge_proc.sql script, you will be asked to:
Enter value for oaam_data_tbs
Enter value for oaam_indx_tbs
The two values to enter are as follows:
Enter value for oaam_data_tbs: <SchemaPrefix>_BRSADATA
Enter value for oaam_indx_tbs: <SchemaPrefix>_BRSAINDX
You can find these values by executing the following query as an OAAM schema user:
select tablespace_name from user_tablespaces;
This section describes configuration issues and their workarounds. It includes the following topics:
Due to a bug, under certain circumstances, the OAAM command line scripts may fail.
If the OAAM command line script fails to launch, execute the script as follows:
bash script_name
Due to a bug, as part of setting up the CLI environment, users must execute the following command on the command line from the CLI working directory:
chmod 750 findjar.sh
The Config Security Store fails to create the policy store object when using variables such as ORACLE_HOME and MW_HOME while running wlst.sh using configureSecurityStore.py with -m join. Always use absolute paths for ORACLE_HOME and MW_HOME while running the command for -m join.