PLS-00905: object APPS.APPS is Invalid

-
Today development team has reported an issue that when they are trying to compile any package which have apps.<> schema reference thrown an error:

 Troubleshoot :

1. Package code I have compiled successfully in other instances like dev2, however got the error in dev1 instance. If we remove schema reference (apps) then it’s compiling from dev1 also but as per coding standard it has good practice to use apps.<>. This show that there are some issue on dev1 DB.

Error on Dev1:
ORA-06550: line 7, column 3:
PLS-00905: object APPS.APPS is invalid
ORA-06550: line 7, column 3:
PL/SQL: Statement ignore.
 
2. Now we should make sure that we have created the package in the right place.

set linesize 90
column owner       format a20
column object_name format a30
column object_type format a20

show user
select owner, object_name, object_type
  from dba_objects
 where object_name='LPW_PO_APPROVAL'
 order by 1,2,3;

 It looks good:

owner            object_name                     object_type
APPS            LPW_PO_APPROVAL    PACKAGE
APPS            LPW_PO_APPROVAL    PACKAGE BODY
ARCHIVE    LPW_PO_APPROVAL    SYNONYM
MERGE        LPW_PO_APPROVAL    SYNONYM

if it is in different schema then connect to sys user and provide 
grant select on <schema>.<packagename> to apps;
and then try. But this is not my case.

3. I have checked the compiler log again and found APPS.APPS that means some developer mistakenly crated the apps name package on apps schema. That may be our case.
Now check :
select owner, object_name, object_type
  from dba_objects
 where OBJECT_NAME='APPS'
 order by 1,2,3;
ohh Great i found one object created with name apps.
now we should drop this :
drop package apps;
4. Try compiling the package in dev1 instance again. This time we had resolved the issue.
Package has been compiled successfully. Hurry  We have resolved the issue.



Comments

Post a Comment

Popular posts from this blog

Workflow Agent Listener Service WF_DEFERRED + Business Event not processing

-
Workflow Agent Listener Service WF_DEFERRED Will Not Start, Mailer May Be Down To implement the solution, please execute the following steps: 1.  Use this query to identify any remaining items in wf_deferred queue: SQL> select corrid, decode(state, 0, '0 = Ready', 1, '1 = Delayed', 2, '2 = Retained', 3, '3 = Exception', to_char(state)) State, count(*) COUNT from wf_deferred group by corrid, state; 2. Items with the APPS corrid will not dequeue from agent listener via service container.  This runs the deferred listener from the command lin e . Make sure that the listener and workflow service components - including the mailer - are down before you run this . This is not intended to be a substitute for the normal operation of this service container from the OAM console. Use this only during this cleanup operation. One will have to run this script manually: begin wf_log_pkg.wf_debug_flag := TRUE; wf_event...
Read more

Output Post Processor - EBS 12.2.4 Troubleshoot

-
Output Post Processor TroubleShooting Issue 1 Output Post Processor is Down with Actual Process is 0 And Target Process is 1 1. Shutdown Concurrent Managers 2. To ensure concurrent manager down; check there is no FNDLIBR process running. ps -ef | grep FNDLIBR 3. Run adadmin to relink FNDSVC executable. a. Invoke adadmin from command prompt b. Choose option 2 (2. Maintain Applications Files menu) c. Choose option 1 (1. Relink Applications programs ) d. Then type FND When prompted; ( Enter list of products to link (all for all products) [all] : FND ) e. Ensure adrelink is exiting with status 0 4. Start Concurrent Managers 5. Check the Output Post Processor Issue 2 Concurrent Processing  R12 Output Post Processor Service Not Coming Up Reason : If Service Manager for the node is not running.  Possible cause might be service manager definition is missing under Concurrent ->Manager ->Define form. If the Service Manager is not pr...
Read more

How to Diagnose Workflow Notification Mailer Issue

-
Outbound Notification Emails : 1. Check if the notification is present in the recipient/user's Worklist/Notifications page.If it does not exist     then it means that notification itself is not created and need to check the corresponding workflow     status.You may also query the notification from the wf_notifications table SQL> select recipient_role,notification_id,status,mail_status from wf_notifications where recipient_role like '&user_name';    The e-mail notification is sent only if all of following are true.                --Notification status is OPEN or CANCELED                --Notification mail_status is MAIL or INVALID 2. Check Recipient role has a valid e-mail address and notification preference MAIL% SELECT email_address, nvl(WF_PREF.get_pref(name, 'MAILT...
Read more