Tag Archives: OAM

Help target US/FND/@OAM_WF_GSC_MLR_DETAILS could not be found

Problem:

On the page:
Applications System:DEV1  >   Workflow  >   Service Components  > Component Details: Workflow Notification Mailer: DEV1

after clicking the Help link, the following error appears:

404 NOT FOUND 

An error occurred while retrieving Oracle Applications Help information. 

Help target US/FND/@OAM_WF_GSC_MLR_DETAILS could not be found.

Solution:

Bug in EBS help files. Instead, manually navigate to help file:

Help Contents > Applied Technology > Oracle Workflow > Administrator’s Guide > Oracle Workflow Manager

 

Reference:

Help Files in OAM Error Help Target US/FND/@OAM_WF_GSC_MLR_DETAILS Could Not Be Found [ID 1074282.1]

Framework Pages Have Different Look and Feel in IE7

Problem:

Oracle Applications Framework pages have different fonts and sizes in Internet Explorer 7 (IE7).

Oracle Applications Manager and Self Service screens have different fonts.

Firefox renders pages ok.

Solution:

To implement the solution, please execute the following steps:

1. Stop Apache

2. Delete files from the following directories:
$OA_HTML/cabo/images/cache/
$OA_HTML/cabo/styles/cache/

3. Start Apache

4. Clear the browser cache

Reference:

Framework Pages Have Different Look and Feel in IE7 [ID 741054.1]

ORA-01400: cannot insert NULL into (“HR”.”PAY_ELE_TMPLT_CLASS_USAGES”.”CLASSIFICATION_ID”)

Problem: When running International HRMS Setup from the UK HRMS Super User responsibility, the following error occurs:

Inserting Balance Attribute Definition : ONLINE_SOE_BALANCE_ATTRIBUTE
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
ORA-01400: cannot insert NULL into ("HR"."PAY_ELE_TMPLT_CLASS_USAGES"."CLASSIFICATION_ID")

Solution: Ensure that the Human Resources product (PER) is licensed.

Read more »

AutoConfig taking long on database tier

Problem:

Running AutoConfig on the database tier of the ebusinesstest machine takes long (over 20 minutes).

Solution:

Log file (/u0/oracle/testdb/9.2.0/appsutil/log/TEST_ebusinesstest/03161419/adconfig.log) showed:

Starting synchronization of file system Context file and its templates with those in the database
Database connection     : Failed
OAM Context editing support feature: Unverified
OAM Customization support feature  : Unverified
File system template    : /u0/oracle/testdb/9.2.0/appsutil/template/adxdbctx.tmp
Checking for customizations to Context template
Warning: Unable to connect to Database.
If the system is OAM enabled, this may result in loss of customizations.
Looking for custom template at : /u0/oracle/testdb/9.2.0/appsutil/template/custom/adxdbctx.tmp
Custom template         : Not available
Customizations found    : None
----------------------------------------------------------------
File system Context file :/u0/oracle/testdb/9.2.0/appsutil/TEST_ebusinesstest.xml
Checking the Context file for possible updates from the Database
Warning: Unable to connect to Database.
If the system is OAM enabled, this may result in loss of customizations and the Context files in DataBase and in the file system may be unsynchronized

Edited context file (/u0/oracle/testdb/9.2.0/appsutil/TEST_ebusinesstest.xml) and changed domain name of machine from (s_domainname) ‘support.com’ to ‘illuminatnm.com’.

Reran AutoConfig on the database tier and it completed under one minute. ‘illuminatnm.com’ domain remains in context file.

Validation Error occurred

Problem:

When trying to set up Workflow Notifications in Oracle Application Manager, the following error occurred:

Validation error occurred. Please check indicated fields below.

Solution:

Log on as user SYSADMIN and set up the workflow.

Run the $FND_TOP/sql/wfver.sql script.

Resolving Non-Starting Servers

Problem: In Oracle Applications Manager, in Applications Dashboard, on the database is appearing up. The remaining servers are shown as down.

Solution:

  1. Tried stopping and restarting the entire system (stopPROD.sh and startPROD.sh).

Executing service control script:

/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adrepctl.sh stop

script returned:

****************************************************
You are running adrepctl.sh version 115.29
Reports Server for PROD is already stopped.
adrepctl.sh: exiting with status 2
.end std out.
.end err out.
****************************************************
Executing service control script:
/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adfmcctl.sh stop
script returned:
****************************************************
You are running adfmcctl.sh version 115.16
forms load balancing client for PROD already stopped.
adfmcctl.sh: exiting with status 2
.end std out.
.end err out.
****************************************************
Executing service control script:
/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adfmsctl.sh stop
script returned:
****************************************************

Subject:  Summary of Possible Reasons and Solutions for the Problem Where All Concurrent Requests Stuck in Pending Phase Doc ID:  Note:182154.1

2.  When shutting down the concurrent manager are there any FNDLIBR processes still running at the OS level?   If so, do a kill -9 on them.  Then restart the concurrent manager.

Tried this, but CM stopped successfully with no need to kill FNDLIBR.

3.  Rebuild the concurrent manager views.  As applmgr run the following from the OS:

This is non-destructive.

Concurrent Manager views can be rebuild by running the following command at the command line:

Ensure that concurrent manager is shutdown.

FNDLIBR FND FNDCPBWV apps/apps SYSADMIN 'System Administrator' SYSADMIN

Restart the concurrent manager.

Executed the above, but no change.

Executed the code:

update fnd_concurrent_queues
set control_code = 'A'
where concurrent_queue_name = 'FNDCRM';
commit;
SQL> update fnd_concurrent_queues
2  set control_code = 'A'
3  where control_code = 'N'
4  /
SQL> select control_code, target_node, concurrent_queue_name
2  from fnd_concurrent_queues
3  where control_code = 'N'
4  /
C TARGET_NODE                    CONCURRENT_QUEUE_NAME
- ------------------------------ ------------------------------
N                                FNDCRM
N                                FNDSCH
N                                STANDARD
N                                PODAMGR
N                                RCVOLTM
N                                PASMGR
N                                INVMGR
N                                INVTMRPM
N                                IEU_SH_CS
N                                IEU_WL_CS
N                                OAMCOLMGR
C TARGET_NODE                    CONCURRENT_QUEUE_NAME
- ------------------------------ ------------------------------
N                                OAMGCS_LINUX-BLADE

updated /etc/hosts file:

[applmgr@linux-blade etc]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain   localhost
128.x.x.x      linux-blade.domainname  linux-blade
SQL> create table fnd_concurrent_queues_vseeram
2        as select * from fnd_concurrent_queues;

Setting up TNSNAMES.ORA for ADI

In Oracle Applications 11.5.10, there is a security feature which prevents users from logging on to the database using SQL tools such as SQL*Plus or TOAD. Refer to Note: 291897.1 (11.5.10 New Features: Managed SQL*Net Access from Hosts) for information on resolving this problem.

To get information pertaining to the host, log on to Oracle Applications Manager, click on Site Map, Administration, and then Hosts. Click the Show link to see the host name, domain and IP address. To determine the port numbers associated with the instance, click View Configuration.

All information is available to place entries into the TNSNAMES.ORA.

NEWTEST = (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=ORACLESERVER.company.local)(PORT=1521))
                (CONNECT_DATA=(SID=PROD))
            )
FNDFS_ORACLESERVER=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=ORACLESERVER.company.local)(PORT=1626))
            (CONNECT_DATA=
                (SID=FNDFS)
            )
        )