How to fix: error "The Function Is Not Available Under The Responsibility"

Sometimes after logging into application, we get error "The Function Is Not Available Under The Responsibility ". This is applicable to 11.5.10 only.

Please perform following steps to fix the issue -

1) Manually run the 'Compile Security' concurrent program, set the parameter to YES.

2) Shut down Middle Tier (Apache)

3) Delete the contents of $OA_HTML/_pages directory (11.5.10 only).

4) Restart Middle tier

Metalink Reference: The Function Is Not Available Under The Responsibility [ID 454285.1]

FSG Transfer Program - To transfer FSG definitions from source to target database

• Database links must be available

• Copy is initiated from target database, not source

• Any budgets, currencies referenced must exist in target database

Navigate to Submit concurrent request window and select ‘Program - FSG Transfer’

Parameters:

- Component Type – Pick one or ALL

- Component Name – Leave blank to copy all of a type or ALL

- Source DB Chart of Accounts – must be typed and must match exactly as no way to validate this field

- Target DB Chart of Accounts – choose from LOV

- Source Database – choose from LOV

• If object with same name already exists, no copy will be done and warning message will be printed

• If currency/budgets/encumbrances do not exist, copy will be performed, but references will be removed from the copied report

• If program is interrupted, can be re-started with same parameters, objects already copied will just give warning message

HOW to find a list of Oracle Forms, Reports and Shell Scripts that include the keyword “SEARCH KEYWORD”

1. Log in to the application server using APPLMGR

2. Change directory to $AU_TOP/forms/US and execute following -

find . -exec grep "SEARCH KEYWORD" '{}' \; -print

3. Change directory to $CUSTOM_TOP and execute following -

find . -exec grep "SEARCH KEYWORD" '{}' \; -print

Re-Build Indexes in your database package using dbms_index_utl.build_table_indexes

Scenario

You have a Table that you use in your Package/Procedure and do a lot of DML (Insert/Update/Delete) operations on it.

You notice the performance of the SQL Statements is not as good as it used to be when you created the Indexes.

This happens because the DML operations, especially Update and Delete create "holes" or "gaps" in the Index.

Solution

You may consider using dbms_index_utl.build_table_indexes in your package

PROCEDURE dummy_schema.dummy_procedure
IS
BEGIN
DELETE FROM dummy_table
WHERE dummy_conditions = 'TRUE';

COMMIT;
-- REBUILD INDEX
dbms_index_utl.build_table_indexes
(LIST => 'DUMMY_SCHEMA.DUMMY_TABLE',
just_unusable => FALSE,
locality => 'ALL',
concurrent => TRUE,
cont_after_err => TRUE,
max_slaves => 8
);
END dummy_procedure;

Note: The procedure's schema should have INDEX privilege on the custom table.