Error Messsage
While compiling the flexfields, the procedure wf_event.raise failed with following
parameters:
event_name = oracle.apps.fnd.flex.dff.compiled
event_key = FND.$SRS$.FNDSCURS
The error raised is:
ORA-00604: error occurred at recursive SQL level 1
ORA-01502: index 'APPLSYS.SYS_C00169351' or partition of such index is in unusable state
Check the Unstale index
select index_name, status from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
WF_JAVA_DEFERRED_N1 UNUSABLE
SYS_C00169351 UNUSABLE
WF_DEFERRED_N1 UNUSABLE
SYS_C00105999 UNUSABLE
Solution:
Rebuild Unstale index.
select 'alter index 'owner'.'index_name' rebuild;' from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
SQL*Plus Command Reference
SQL*PLUS - SET Statement
http://www.ss64.com/orasyntax/plus_set.html
SQL*Plus FAQ
http://www.orafaq.com/wiki/SQL*Plus_FAQ
SQL*Plus Command Reference
http://download-west.oracle.com/docs/cd/B10500_01/server.920/a90842/ch13.htm
http://www.ss64.com/orasyntax/plus_set.html
SQL*Plus FAQ
http://www.orafaq.com/wiki/SQL*Plus_FAQ
SQL*Plus Command Reference
http://download-west.oracle.com/docs/cd/B10500_01/server.920/a90842/ch13.htm
How to Restart The Concurrent Manager in Unix.
goal: How to restart the concurrent manager in Unix
goal: How to bounce the concurrent manager in Unix
fact: Oracle Application Object Library
fix:
1. At the command line issue the following shutdown command:
CONCSUB apps/apps sysadmin 'System Administrator' SYSADMIN CONCURRENT FND SHUTDOWN
Note: There are 3 options which can be used for controlling the Internal
Manager from the OS as follows:
SHUTDOWN = Standard, non-invasive shutdown.
DEACTIVATE = Will not allow further Requests to Process once Issued.
ABORT = Terminate Requests and Deactivate the Internal Manager.
2. At the command line, issue the following Start Up command:
startmgr sysmgr="[fnd_usernamd/fnd_password]" mgrname="[mgrname]" printer="[printername]"
mailto="[userid userid2...]" restart="[Nminutes]" logfile="[log_file_name]" sleep="
[new_check]" pmon="[manager_check]" quesiz="[number_check]" diag="[YN]"
ExAMPLE:
startmgr sysmgr="applsys/apps" mgrname="std" printer="localprint"
mailto="Ramesh Mani" restart="N" logfile="mgrlog" sleep="90"
pmon="5" quesiz="10" diag="N"
Note: a space is required between arguments and the "diag" parameter
may be omitted if desired.
Reference: 147449.1
goal: How to bounce the concurrent manager in Unix
fact: Oracle Application Object Library
fix:
1. At the command line issue the following shutdown command:
CONCSUB apps/apps sysadmin 'System Administrator' SYSADMIN CONCURRENT FND SHUTDOWN
Note: There are 3 options which can be used for controlling the Internal
Manager from the OS as follows:
SHUTDOWN = Standard, non-invasive shutdown.
DEACTIVATE = Will not allow further Requests to Process once Issued.
ABORT = Terminate Requests and Deactivate the Internal Manager.
2. At the command line, issue the following Start Up command:
startmgr sysmgr="[fnd_usernamd/fnd_password]" mgrname="[mgrname]" printer="[printername]"
mailto="[userid userid2...]" restart="[Nminutes]" logfile="[log_file_name]" sleep="
[new_check]" pmon="[manager_check]" quesiz="[number_check]" diag="[YN]"
ExAMPLE:
startmgr sysmgr="applsys/apps" mgrname="std" printer="localprint"
mailto="Ramesh Mani" restart="N" logfile="mgrlog" sleep="90"
pmon="5" quesiz="10" diag="N"
Note: a space is required between arguments and the "diag" parameter
may be omitted if desired.
Reference: 147449.1
The field PARAMETER.CONFIG could not be located or read
Symptoms
You are encountering the following error while trying to start/stop the apache
using adapcctl.sh
"The field PARAMETER.CONFIG could not be located or read."
The adapcctl.log carries the following errors:
Cannot read value from field PARAMETER.CONFIG
Cause: The field PARAMETER.CONFIG could not be located or read.
Changes
You upgraded to RDBMS 9.2.0.4 from RDBMS 8.0.6, but the instance was fine for a couple of days after the upgrade. This problem suddenly cropped up.
Cause
Your guest user is end-dated
That is the sole reason you are getting this error.
Fix
Back up your FND_USER TABLE
Run the following command update fnd_user set end_date=null where user_name='GUEST';
Retest with adapcctl.sh
Reference: 298143.1
You are encountering the following error while trying to start/stop the apache
using adapcctl.sh
"The field PARAMETER.CONFIG could not be located or read."
The adapcctl.log carries the following errors:
Cannot read value from field PARAMETER.CONFIG
Cause: The field PARAMETER.CONFIG could not be located or read.
Changes
You upgraded to RDBMS 9.2.0.4 from RDBMS 8.0.6, but the instance was fine for a couple of days after the upgrade. This problem suddenly cropped up.
Cause
Your guest user is end-dated
That is the sole reason you are getting this error.
Fix
Back up your FND_USER TABLE
Run the following command update fnd_user set end_date=null where user_name='GUEST';
Retest with adapcctl.sh
Reference: 298143.1
Diagnostic Script for Concurrent Manager
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - - - - -
spool ccm.lst
prompt Step 1 Checking how many rows in FND_CONCURRENT_REQUEST.
select count(*) from fnd_concurrent_requests;
prompt
-----------------------------------------
prompt Step 2 Checking how many rows in FND_CONCURRENT_PROCESSES table.
select count(*) from fnd_concurrent_processes;
prompt
-----------------------------------------------
prompt Step 3 Checking sys.dual table which should have one and only one row.
select count(*) from sys.dual;
prompt If you have more than one row in sys.dual, please delete it
prompt sql> delete rownum from SYS.DUAL;
Prompt rownum= the row number to delete
prompt
prompt
prompt
---------------------------------------------
prompt Step 4 Checking fnd_dual. There must be at lest one row:
select count(*) from fnd_dual;
prompt If there are no record selected,
prompt Update fnd_dual table to have at lest one record
prompt
----------------------------------------------
prompt Step 5 Checking the Internal Manager queue name "FNDICM" which should be=1
select concurrent_queue_id from fnd_concurrent_queues
where concurrent_queue_name='FNDICM';
prompt
----------------------------------------------
prompt Step 6 Checking for Active processes under the Internal Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDICM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
-----------------------------------------
prompt Step 7 Checking for Active processes under the Standard Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='STANDARD'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
------------------------------------------
prompt Step 8 Checking for Active processes under the Conflict Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDCRM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
---------------------------------------------------
prompt Step 9 Checking Actual and Target Processes for Internal Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDICM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
--------------------------------------------------------
prompt Step 10 Checking Actual and Target Processes for the Standard Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='STANDARD';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
prompt Step 11 Checking Actual and Target Processes for Conflict Resolution Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDCRM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
Prompt Step 12 Checking if the control_code set to 'N':
select control_code from fnd_concurrent_queues
where control_code='N';
prompt
prompt If any rows selected, please update the table fnd_concurrent_queues:
prompt Update fnd_concurrent_queues set control_code = null
prompt where control_code ='N';
PROMPT Update fnd_concurrent_queues set target_node = null;
PROMPT commit;
prompt
prompt
--------------------------------
PROMPT Step 13 Checking terminated processes:
PROMPT
select count (*) from fnd_concurrent_requests
where status_code='T';
prompt
prompt If you have terminated processes run the following sql statement:
prompt
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'T';
prompt
------------------------------------------
prompt Step 14 Checking pending requests:
select count(*) from fnd_concurrent_requests
where status_code='P';
prompt If any rows selected please run the following sql statement:
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'P';
prompt
------------------------------------------------------
prompt Step 15 Checking Running processes:
prompt
select count (*) from fnd_concurrent_requests
where status_code='R';
prompt
prompt If you have Running processes run the following sql statement
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'R';
prompt
------------------------------------------
prompt Step 16 Checking the PMON method, which should be set to LOCK:
prompt
select profile_option_id , profile_option_value
from FND_PROFILE_OPTION_VALUES
where profile_option_id= (select profile_option_id
from FND_PROFILE_OPTIONS
where profile_option_name='CONC_PMON_METHOD');
prompt
prompt If the PROFILE_OPTION_VALUE was't LOCK please
prompt Reset PMON to LOCK by running afimpmon.sql script(The manager should be down)
prompt 1-At UNIX command prompt:
prompt 2-cd $FND_TOP/sql
prompt 3-Log into SQLPLUS as apps/
prompt SQL> @afimpmon.sql
prompt prompt1:dual
prompt prompt2:LOCK (LOCK MUST BE ALL UPPERCASE)
prompt For Oracle Applications Release 11.5, when you check the PMON
prompt Method you may get no rows selected which is normal,
prompt because in apps 11.5 the Pmon Method is hard coded to Lock at
prompt the Operating System level.
prompt
prompt
-------------------------------------------------------
prompt Step-17 Checking how many FNDLIBR processes are running:
prompt -For Unix :From unix command prompt $ ps -ef grep -i fndlibr
prompt If you have any FNDLIBR processes running,please kill them before
prompt starting or shuting down the internal manager
prompt
prompt
prompt -For NT, through Task Manager, check the entries under the Processes tab
for FNDLIBR.exe processes.
prompt If there are any, Highlight and click [End Process] button to kill processes
prompt
----------------------------------------------------------
prompt Step-18 Checking how many "FND_%"invalid objects:
select substr(owner,1, 12) owner, substr(object_type,1,12) type,
substr(status,1,8) status, substr(object_name, 1, 25) name
from dba_objects
where object_name like 'FND_%'
and status='INVALID';
prompt If you have any invalied objects please see note#113947.1 via Metalink
prompt
--------------------------------------------------------------
prompt Step-19-How to find the PID in the O/S for request_id:
prompt If you do not like to check this enter any number then click Enter to Exit
select r.request_id, p.os_process_id
from FND_CONCURRENT_REQUESTS r,FND_CONCURRENT_PROCESSES p
where r.controlling_manager = p.concurrent_process_id
and request_id=&request_id;
prompt
prompt Please upload the "ccm.lst" output to Support, Thanks.
prompt
spool off
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - - - - - -
spool ccm.lst
prompt Step 1 Checking how many rows in FND_CONCURRENT_REQUEST.
select count(*) from fnd_concurrent_requests;
prompt
-----------------------------------------
prompt Step 2 Checking how many rows in FND_CONCURRENT_PROCESSES table.
select count(*) from fnd_concurrent_processes;
prompt
-----------------------------------------------
prompt Step 3 Checking sys.dual table which should have one and only one row.
select count(*) from sys.dual;
prompt If you have more than one row in sys.dual, please delete it
prompt sql> delete rownum from SYS.DUAL;
Prompt rownum= the row number to delete
prompt
prompt
prompt
---------------------------------------------
prompt Step 4 Checking fnd_dual. There must be at lest one row:
select count(*) from fnd_dual;
prompt If there are no record selected,
prompt Update fnd_dual table to have at lest one record
prompt
----------------------------------------------
prompt Step 5 Checking the Internal Manager queue name "FNDICM" which should be=1
select concurrent_queue_id from fnd_concurrent_queues
where concurrent_queue_name='FNDICM';
prompt
----------------------------------------------
prompt Step 6 Checking for Active processes under the Internal Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDICM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
-----------------------------------------
prompt Step 7 Checking for Active processes under the Standard Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='STANDARD'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
------------------------------------------
prompt Step 8 Checking for Active processes under the Conflict Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDCRM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
---------------------------------------------------
prompt Step 9 Checking Actual and Target Processes for Internal Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDICM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
--------------------------------------------------------
prompt Step 10 Checking Actual and Target Processes for the Standard Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='STANDARD';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
prompt Step 11 Checking Actual and Target Processes for Conflict Resolution Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDCRM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
Prompt Step 12 Checking if the control_code set to 'N':
select control_code from fnd_concurrent_queues
where control_code='N';
prompt
prompt If any rows selected, please update the table fnd_concurrent_queues:
prompt Update fnd_concurrent_queues set control_code = null
prompt where control_code ='N';
PROMPT Update fnd_concurrent_queues set target_node = null;
PROMPT commit;
prompt
prompt
--------------------------------
PROMPT Step 13 Checking terminated processes:
PROMPT
select count (*) from fnd_concurrent_requests
where status_code='T';
prompt
prompt If you have terminated processes run the following sql statement:
prompt
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'T';
prompt
------------------------------------------
prompt Step 14 Checking pending requests:
select count(*) from fnd_concurrent_requests
where status_code='P';
prompt If any rows selected please run the following sql statement:
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'P';
prompt
------------------------------------------------------
prompt Step 15 Checking Running processes:
prompt
select count (*) from fnd_concurrent_requests
where status_code='R';
prompt
prompt If you have Running processes run the following sql statement
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'R';
prompt
------------------------------------------
prompt Step 16 Checking the PMON method, which should be set to LOCK:
prompt
select profile_option_id , profile_option_value
from FND_PROFILE_OPTION_VALUES
where profile_option_id= (select profile_option_id
from FND_PROFILE_OPTIONS
where profile_option_name='CONC_PMON_METHOD');
prompt
prompt If the PROFILE_OPTION_VALUE was't LOCK please
prompt Reset PMON to LOCK by running afimpmon.sql script(The manager should be down)
prompt 1-At UNIX command prompt:
prompt 2-cd $FND_TOP/sql
prompt 3-Log into SQLPLUS as apps/
prompt SQL> @afimpmon.sql
prompt prompt1:dual
prompt prompt2:LOCK (LOCK MUST BE ALL UPPERCASE)
prompt For Oracle Applications Release 11.5, when you check the PMON
prompt Method you may get no rows selected which is normal,
prompt because in apps 11.5 the Pmon Method is hard coded to Lock at
prompt the Operating System level.
prompt
prompt
-------------------------------------------------------
prompt Step-17 Checking how many FNDLIBR processes are running:
prompt -For Unix :From unix command prompt $ ps -ef grep -i fndlibr
prompt If you have any FNDLIBR processes running,please kill them before
prompt starting or shuting down the internal manager
prompt
prompt
prompt -For NT, through Task Manager, check the entries under the Processes tab
for FNDLIBR.exe processes.
prompt If there are any, Highlight and click [End Process] button to kill processes
prompt
----------------------------------------------------------
prompt Step-18 Checking how many "FND_%"invalid objects:
select substr(owner,1, 12) owner, substr(object_type,1,12) type,
substr(status,1,8) status, substr(object_name, 1, 25) name
from dba_objects
where object_name like 'FND_%'
and status='INVALID';
prompt If you have any invalied objects please see note#113947.1 via Metalink
prompt
--------------------------------------------------------------
prompt Step-19-How to find the PID in the O/S for request_id:
prompt If you do not like to check this enter any number then click Enter to Exit
select r.request_id, p.os_process_id
from FND_CONCURRENT_REQUESTS r,FND_CONCURRENT_PROCESSES p
where r.controlling_manager = p.concurrent_process_id
and request_id=&request_id;
prompt
prompt Please upload the "ccm.lst" output to Support, Thanks.
prompt
spool off
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - - - - - -
How To Trace a Concurrent Request And Generate TKPROF File
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:9891571609150575875::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,453527.1,1,1,1,helvetica
Reference:
Metalink Note ID: 453527.1
Organization Setup Frequently Asked Questions - FAQ
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6356763575233978369::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,109665.1,1,1,1,helvetica
Doc ID:
109665.1
Reference:
Metalink Note ID: 453527.1
Organization Setup Frequently Asked Questions - FAQ
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6356763575233978369::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,109665.1,1,1,1,helvetica
Doc ID:
109665.1
FNDFS Fails to Relink on Red Hat 4.0 - Undefined Reference to dl_iterate_phdr@GLIBC_2.2.4
Starting link of fnd executable 'FNDFS' on Mon Feb 16 23:26:17 EST 2009
gcc -s -L/U01/oracle/U01ora/8.0.6/lib -L/U01/oracle/U01ora/8.0.6/lib/stubs -ldl -o /U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS
/U01/oracle/U01appl/fnd/11.5.0/lib/afpfss.o \
/U01/oracle/U01appl/fnd/11.5.0/lib/libfnd.a -lsql /U01/oracle/U01ora/8.0.6/lib/nautab.o /U01/oracle/U01ora/8.0.6/lib/naeet.o
/U01/oracle/U01ora/8.0.6/lib/naect.o /U01/oracle/U01ora/8.0.6/lib/naedhs.o `cat /U01/oracle/U01ora/8.0.6/lib/naldflgs` -lnetv2 -lnttcp
-lnetwork -lncr -lclient -lvsn -lcommon -lgeneric -lmm -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lnetv2 -lnttcp -lnetwork -lncr
-lclient -lvsn -lcommon -lgeneric -lepc -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lclient -lvsn -lcommon -lgeneric -lnlsrtl3 -lcore4
-lnlsrtl3 -lcore4 -lnlsrtl3 `cat /U01/oracle/U01ora/8.0.6/lib/sysliblist` -ldl -lpthread -lm /U01/oracle/U01ora/8.0.6/rdbms/lib/defopt.o
/U01/oracle/U01ora/8.0.6/rdbms/lib/ssbbded.o
/usr/lib/gcc/i386-redhat-linux/3.4.6/libgcc_s.so: undefined reference to `dl_iterate_phdr@GLIBC_2.2.4'
collect2: ld returned 1 exit status
make: *** [/U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS] Error 1
Done with link of fnd executable 'FNDFS' on Mon Feb 16 23:26:19 EST 2009
Relink of module "FNDFS" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /U01/oracle/U01appl/fnd/11.5.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.
Done with link of product 'fnd' on Mon Feb 16 23:26:19 EST 2009
adrelink is exiting with status 1
End of adrelink session
Solutions:
For Red Hat 4.0, re-apply Patch 4198954 by doing the following:
1. Verify the package has already been installed by running the following command:
#rpm -qs compat-oracle-rhel4
package compat-oracle-rhel4 is not installed
#rpm -qs compat-libcwait-2
package compat-libcwait-2 is not installed
2. Use the following command to apply the patch 4198954:
# rpm -Uvh compat-oracle-rhel4-1.0-5.i386.rpm
Preparing... ########################################### [100%]1:compat-oracle-rhel4 ########################################### [100%]
# rpm -Uvh compat-libcwait-2.1-1.i386.rpm
Preparing... ########################################### [100%]
1:compat-libcwait ########################################### [100%]
3. Verify the file sizes are now correct by running the following command again:
ls -l /usr/bin/gcc*
The correct file sizes are as follows:
[root@vision]# ls -l /usr/bin/gcc*
-rwxr-xr-x 1 root root 914 Feb 23 2005 /usr/bin/gcc
-rwxr-xr-x 2 root root 84780 Dec 1 2004 /usr/bin/gcc32
-rwxr-xr-x 1 root root 93120 Sep 26 10:28 /usr/bin/gcc.orig
4. Re-link the FNDFS executable using adadmin
Refered ID:
Doc ID: 464519.1
gcc -s -L/U01/oracle/U01ora/8.0.6/lib -L/U01/oracle/U01ora/8.0.6/lib/stubs -ldl -o /U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS
/U01/oracle/U01appl/fnd/11.5.0/lib/afpfss.o \
/U01/oracle/U01appl/fnd/11.5.0/lib/libfnd.a -lsql /U01/oracle/U01ora/8.0.6/lib/nautab.o /U01/oracle/U01ora/8.0.6/lib/naeet.o
/U01/oracle/U01ora/8.0.6/lib/naect.o /U01/oracle/U01ora/8.0.6/lib/naedhs.o `cat /U01/oracle/U01ora/8.0.6/lib/naldflgs` -lnetv2 -lnttcp
-lnetwork -lncr -lclient -lvsn -lcommon -lgeneric -lmm -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lnetv2 -lnttcp -lnetwork -lncr
-lclient -lvsn -lcommon -lgeneric -lepc -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lclient -lvsn -lcommon -lgeneric -lnlsrtl3 -lcore4
-lnlsrtl3 -lcore4 -lnlsrtl3 `cat /U01/oracle/U01ora/8.0.6/lib/sysliblist` -ldl -lpthread -lm /U01/oracle/U01ora/8.0.6/rdbms/lib/defopt.o
/U01/oracle/U01ora/8.0.6/rdbms/lib/ssbbded.o
/usr/lib/gcc/i386-redhat-linux/3.4.6/libgcc_s.so: undefined reference to `dl_iterate_phdr@GLIBC_2.2.4'
collect2: ld returned 1 exit status
make: *** [/U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS] Error 1
Done with link of fnd executable 'FNDFS' on Mon Feb 16 23:26:19 EST 2009
Relink of module "FNDFS" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /U01/oracle/U01appl/fnd/11.5.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.
Done with link of product 'fnd' on Mon Feb 16 23:26:19 EST 2009
adrelink is exiting with status 1
End of adrelink session
Solutions:
For Red Hat 4.0, re-apply Patch 4198954 by doing the following:
1. Verify the package has already been installed by running the following command:
#rpm -qs compat-oracle-rhel4
package compat-oracle-rhel4 is not installed
#rpm -qs compat-libcwait-2
package compat-libcwait-2 is not installed
2. Use the following command to apply the patch 4198954:
# rpm -Uvh compat-oracle-rhel4-1.0-5.i386.rpm
Preparing... ########################################### [100%]1:compat-oracle-rhel4 ########################################### [100%]
# rpm -Uvh compat-libcwait-2.1-1.i386.rpm
Preparing... ########################################### [100%]
1:compat-libcwait ########################################### [100%]
3. Verify the file sizes are now correct by running the following command again:
ls -l /usr/bin/gcc*
The correct file sizes are as follows:
[root@vision]# ls -l /usr/bin/gcc*
-rwxr-xr-x 1 root root 914 Feb 23 2005 /usr/bin/gcc
-rwxr-xr-x 2 root root 84780 Dec 1 2004 /usr/bin/gcc32
-rwxr-xr-x 1 root root 93120 Sep 26 10:28 /usr/bin/gcc.orig
4. Re-link the FNDFS executable using adadmin
Refered ID:
Doc ID: 464519.1
How To Configure RMAN Backups To Tape via Oracle Enterprise Manager
Solution
+ Log in to Oracle Enterprise Manager Database Control
+ Navigate to: Maintenance -> Backup Settings -> Device
If grid control is used, we need to first select the appropriate database from Targets.
+ Now, under Tape Settings, specify the number of Tape Drives that will be available for this backup schedule/policy. RMAN will allocate that many simultaneous channels as many Tape Drives are specified.
+ On the same screen, specify the MML specific parameters under "Media Management Vendor Library Parameters" which as per our example above are:
ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)
Refer to the example script above and the screen shot below:
+ Log in to Oracle Enterprise Manager Database Control
+ Navigate to: Maintenance -> Backup Settings -> Device
If grid control is used, we need to first select the appropriate database from Targets.
+ Now, under Tape Settings, specify the number of Tape Drives that will be available for this backup schedule/policy. RMAN will allocate that many simultaneous channels as many Tape Drives are specified.
+ On the same screen, specify the MML specific parameters under "Media Management Vendor Library Parameters" which as per our example above are:
ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)
Refer to the example script above and the screen shot below:
+ Specify preferred credentials on the same page if they are not configured already. Additionally, also configure advanced settings such as CONTROLFILE AUTOBACKUP or the backup Retention Policy under the Policy sub-tab of the Backup Settings page. Click OK to save your settings.
+ Now, navigate to: Maintenance -> Schedule Backup.
+ Select Whole Database under Customized Backup and click Schedule Customized Backup. In the screen that follows, accept the defaults though you may like to tinker with some of the settings i.e. to delete obsolete backups etc under Advanced as per your requirement. click Next.
+ In this screen, select Tape to make backups to TAPE. Notice that the MML parameters that we saved earlier are shown here:
+ Click Next.On the new page you can specify Job Name, Job Description and the job schedule. Make appropriate changes and click Next.
+ Click Next
+ This last page now summarizes the configuration we have specified for our backup job and the EM generated script. You might want to edit the EM generated backup script for customized tags or format (backup-piece handle). After you have ensured all settings are appropriate, click Submit Job to complete the setup.
Refference: 735953.1
Create Document in R12 Web ADI Menu Generates HTTP 404 File Not Found Error
Symptoms
When trying to use the function Create Document the following error is displayed:
HTTP 404 File Not Found Error
Steps To Reproduce:
===================
Navigation -
1. Log onto a Release 12 instance with WEB ADI Installed
2. Seleft Responsibility Oracle Web ADI
3. Select Create Document
Solution
1. Go into the responsibility System Administrator.
2. Navigate to System Administrator > Security > Responsibility > Define > Oracle web ADI Responsibility
3. Set the menu to Desktop Integration Menu and save
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
When trying to use the function Create Document the following error is displayed:
HTTP 404 File Not Found Error
Steps To Reproduce:
===================
Navigation -
1. Log onto a Release 12 instance with WEB ADI Installed
2. Seleft Responsibility Oracle Web ADI
3. Select Create Document
Solution
1. Go into the responsibility System Administrator.
2. Navigate to System Administrator > Security > Responsibility > Define > Oracle web ADI Responsibility
3. Set the menu to Desktop Integration Menu and save
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
Subscribe to:
Posts (Atom)
