How To Relink and Bounce the Receiving Executables? [ID
552702.1]
Solution
Relink receiving
executables.
cd $PO_TOP/bin
$ adrelink.sh
force=y ranlib=y "PO RCVOLTM"
$ adrelink.sh
force=y ranlib=y "PO RVCTP"
Prior to r11i/r12,
the command is adrelink
Bounce the
Receiving Transaction Manager.
a. $ps -ef | grep
RCVOLTM (to see how many processes are running)
b. Deactivate
Receiving Transaction Manager
(System
Administrator > Concurrent > Manager > Administer)
c. $ps -ef | grep
RCVOLTM (repeat until no processes are running)
d. Restart
Receiving Transaction Manager
Note: If the
package/body is invalid & verifi invalid objects
sqlplus apps/apps
col object_name
for a30
col owner for a10
select
object_name,owner,object_type,status
from DBA_OBJECTS
where status like 'INVALID%'
order by
object_name;
2) Also try to
recompile package PO_DOCUMENT_ACTION_PVT
SQL> alter
package PO_DOCUMENT_ACTION_PVT compile;
SQL> alter
package PO_DOCUMENT_ACTION_PVT compile body;
+++++++++++++++
141118.1,1406164.1
+++++++++++++++
For Trace
1063222.1
++++++++++++++
Solution(154599.1)
The database
administrator should check for space issues like table space and extents.
This can cause the
above symptoms to occur.
Use the following
script from SQL*Plus as the APPS user for possible
extents shortage:
SQL>
Select
substr(s.tablespace_name,1,10)
tablespace,
substr(s.owner,1,8) owner ,
substr(s.segment_type,1,12) type_object,
substr(s.segment_name,1,30) name_objet ,
LPAD(TO_CHAR(s.extents),5,' ') extents,
LPAD(TO_CHAR(s.MAX_EXTENTS),5,' ') MAX_extents
FROM sys.dba_segments s
WHERE s.segment_type IN
('TABLE','INDEX')
and s.extents
>s.MAX_EXTENTS*0.8
ORDER BY extents
desc;
Use the following
script from SQL*Plus as the APPS user for possible
table space
problems:
SQL>
Select
d.tablespace_name,
d.file_name,
d.bytes/1024/1024 gbsize,
sum(f.bytes)/1024/1024 free,
max(f.bytes)/1024/1024 max
from
dba_free_space f,
dba_data_files d
where
f.file_id(+)=d.file_id
group by
d.tablespace_name, d.file_name, d.bytes/1024/1024;
You may also check
the database alert<SID>.log file for possible space problems.
+++++++++++++++
Solution
(351306.1)
Review the shared
pool and increase as needed.
Run the following
test PLSQL call, and if it results in error, this confirms that shared pool
size is the issue:
set serveroutput
on
declare
l_ret_status
VARCHAR2(20);
l_msg_count
NUMBER;
l_msg_data
VARCHAR2(100);
x_group_id NUMBER
:= 1;
x_request_id
NUMBER := 2;
begin
inv_rcv_integration_apis.explode_lpn(1.0,
fnd_api.g_true,
l_ret_status,
l_msg_count,
l_msg_data,
x_group_id,
x_request_id
);
dbms_output.put_line(l_ret_status);
end;
+++++++++++++++++++++++++++
Run SQL scripts below to confirm debug/trace
profile values are set correctly.
+++++++++++++++++++++++++++
SQL> select
user_id from fnd_user where user_name= upper('&UserName');
SQL>select
decode(a.profile_option_name,
'AFLOG_ENABLED','FND:
Debug Log Enabled',
'AFLOG_LEVEL','FND:
Debug Log Level',
'AFLOG_MODULE','FND:
Debug Log Module',
'INV_DEBUG_TRACE','INV:
Debug Trace',
'INV_DEBUG_FILE','INV:
Debug file',
'INV_DEBUG_LEVEL','INV:Debug
Level',
'ONT_DEBUG_LEVEL','OM:
Debug Level',
'OE_DEBUG_LOG_DIRECTORY','OM:
Debug Log Directory',
|'PO_RVCTP_ENABLE_TRACE','PO:Enable
Sql Trace for Receiving Processor',
'RCV_DEBUG_MODE','RCV:
Debug Mode',
'RCV_TP_MODE','RCV:
Processing Mode',
'FND_INIT_SQL','Initialization
SQL Statement - Custom') "Profile",
c.PROFILE_OPTION_VALUE
"Profile Value"
from
apps.fnd_profile_options a, apps.FND_PROFILE_OPTION_VALUES c
where
a.PROFILE_option_NAME in (
'AFLOG_ENABLED',
'AFLOG_LEVEL',
'AFLOG_MODULE',
'INV_DEBUG_TRACE',
'INV_DEBUG_FILE',
'INV_DEBUG_LEVEL',
'ONT_DEBUG_LEVEL',
'OE_DEBUG_LOG_DIRECTORY',
'PO_RVCTP_ENABLE_TRACE',
'RCV_DEBUG_MODE',
'RCV_TP_MODE',
'FND_INIT_SQL')
and
a.profile_option_id = c.profile_option_id (+)
and
a.application_id = c.application_id (+)
and &UserID =
c.level_value (+)
and 10004 =
c.level_id (+)
order by
a.profile_option_name;
+++++++++++++++++++++++++++++
No comments:
Post a Comment