After modifying Workflow Package getting below error ORA-00054: resource busy and acquire with NOWAIT

After modifying Workflow Package getting below error ORA-00054: resource busy and acquire with NOWAIT

After modifying any workflow package, while approving or acting on the notification getting below error.

ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired 

ORA-06512: at "APPS.WF_NOTIFICATION", line 5137 ORA-06512: at line 1

It is due to the old state of the existing code creating this error.

Resolution:

1. Clear the old session locking up the old objects.

a. Search the session


select s.* 

from gv$access a, gv$session s 

where object IN  ('AP_WORKFLOW_PKG')

and a.inst_id=s.inst_id 

and a.sid=s.sid 


order by logon_time;



b. Kill the session ( Restart workflow and OPMN, will clear most of them )



2. Bounce the database

SMTP Error. Getting below error while trying to send email in XXXXXXX instance

Getting below error in EBS R12.1.3 in Oracle Database 

SMTP Error. Getting below error while trying to send email in XXXXXXX instance

Oracle Error in Send Mail prog--ORA-29277: invalid SMTP operation

ORA-06512: at "SYS.UTL_SMTP", line 82

ORA-06512: at "SYS.UTL_SMTP", line 540

ORA-06512: at "SYS.UTL_SMTP", line 525

ORA-29278: SMTP transient error: 421 Service not available 

It can be below different issues.

1. You don't have enough privileges.

2. SMTP server not given properly.

3. Check WF config to validate SMTP server.

4. Firewall ports are opened for the SMTP mail. Use command prompt to send email.

ORA-12012: error on auto execute of job "ORACLE_OCM"."MGMT_CONFIG_JOB_2_3"

Error message

*** 2014-10-05 09:00:07.681
*** SESSION ID:(5646.61909) 2014-10-05 09:00:07.681
*** CLIENT ID:() 2014-10-05 09:00:07.681
*** SERVICE NAME:(SYS$USERS) 2014-10-05 09:00:07.681
*** MODULE NAME:(DBMS_SCHEDULER) 2014-10-05 09:00:07.681
*** ACTION NAME:(MGMT_CONFIG_JOB_2_3) 2014-10-05 09:00:07.681

ORA-12012: error on auto execute of job "ORACLE_OCM"."MGMT_CONFIG_JOB_2_3"
ORA-29280: invalid directory path
ORA-06512: at "ORACLE_OCM.MGMT_DB_LL_METRICS", line 2436
ORA-06512: at line 1



To supress this error message, we have to disable it as per the (https://blogs.oracle.com/UPGRADE/entry/upgrade_to_11_2_0)

SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');
SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');

It has been tried in stage First.

SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');

PL/SQL procedure successfully completed.

SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');

PL/SQL procedure successfully completed.



Another way is to reconfigure this OCM if you want to use this feature.

Cause:

SQL>select * from dba_directories where DIRECTORY_NAME like '%OCM_CONFIG%';

MGMT_DB_LL_METRICS wants to write to ORACLE_OCM_CONFIG_DIR2, which is not created by the built-in instrumentation scripts.

Sotutions:

1. You have to run the below command to check whether OCM is configured.

$ORACLE_HOME/ccr/bin/deployPackages -l

( some time there is a permission issue on $ORACLE_HOME/ccr/bin/deployPackages )
-- Then you can check it and give execute permission to $ORACLE_HOME/ccr/bin/deployPackages
-- Then try again

Installation Steps:

If OCM is not installed, please install it using steps given in the below document. It will create the directory during the installation. NO need to follow step 2.

Oracle Configuration Manager Installation and Administration Guide


2.
Connect as sysdba

SQL> @ORACLE_HOME/ccr/admin/scripts/ocmjb10.sql

SQL> @ORACLE_HOME/ccr/admin/scripts/execute execocm.sql

3.

Output should be like, if everything is fine :

SQL> select * from dba_directories where DIRECTORY_NAME like '%OCM_CONFIG%';

OWNER    DIRECTORY_NAME         DIRECTORY_PATH
-------- ---------------------- ------------------------------------------------------------------
SYS      ORACLE_OCM_CONFIG_DIR2 /u01/app/oracle/product/11.2.0.3/dbhome_1/ccr/state
SYS      ORACLE_OCM_CONFIG_DIR  /u01/app/oracle/product/11.2.0.3/dbhome_1/ccr/hosts/dc2oda-1/state

**Directory ORACLE_OCM_CONFIG_DIR2 should be returned in output.

Journal posting error in R12

Journal posting error in R12

<< glpsqp() 23-APR-2013 16:26:08

glpsqs() 23-APR-2013 16:26:08

PERF0005: Oracle error detected in glpsqs() - ORA-20001: An active sequence assignment is required.
ORA-06512: at "A


Please find the below document for the issue.

1. R12: Posting Throws ORA-06512: at "APPS.GL_GLPPOS_ACCTSEQ_PKG" [ID 1058014.1]
2. Posting a Journal Fails in GLPHOK due to ORA-20001 error [ID 242002.1]
3. GL Posting Program Terminated With Errors in GLPUBR [ID 292683.1]

ORA-20000: ORU-10027: buffer overflow, limit of 2000 bytes

ERROR at line 1:
ORA-20000: ORU-10027: buffer overflow, limit of 2000 bytes
ORA-06512: at "SYS.DBMS_OUTPUT", line 91
ORA-06512: at "SYS.DBMS_OUTPUT", line 58
ORA-06512: at line 6




Sol : set serveroutput on size 1000000 ( give some extra size)

Unable to create anonymous session.

Unable to create anonymous session. Your session is no longer valid. Oracle error 20001: java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: Oracle error -1653: ORA-01653: unable to extend table APPLSYS.FND_LOGINS by 16 in tablespace APPS_TS_ARCHIVE has been detected in FND_SIGNON.AUDIT_USER. has been detected in FND_SIGNON.NEW_PROXY_ICX_SESSION. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_SIGNON", line 18 ORA-06512: at "APPS.FND_SIGNON", line 530 ORA-06512: at "APPS.FND_SESSION_MANAGEMENT", line 390 ORA-06512: at "APPS.FND_SESSION_MANAGEMENT", line 538 ORA-06512: at "APPS.FND_AOLJ_UTIL", line 217 ORA-06512: at line 1 has been detected in createSession(int, String)(userid=6','716498702FC0487EE044001A4B0621D724654810232605405413161982081592').

Solution:
Check the available space in the server.

ORA-06512: at line

Error:
ORA-06512: at line
Cause:

This error message indicates the line number in the PLSQL code that the error resulted.
Action:

For example, if you had the following PLSQL code:
declare
v_number number(2);
begin
v_number := 100;
end;


You would receive the error message:
The first line of the error message (ie: ORA-06502) indicates the error that occurred, while the second line of the error message (ie: ORA-06512) indicates that the error occurred at line 4 of the PLSQL code.