telnet: connect to address 10.1.150.139: Connection refused

[root@ve ~]#  netstat -tulpn | grep 1521
[root@ve ~]#  ps aux | grep oracle

sqlplus / as sysdba

startup

lsnrctl start listener

[root@ve2 ~]# netstat -tuplen

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address               Foreign Address             State       User       Inode      PID/Program name

tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN      0          10168      1641/rpcbind

tcp        0      0 0.0.0.0:37779               0.0.0.0:*                   LISTEN      29         1931       1685/rpc.statd

tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      0          10766      1859/sshd

tcp        0      0 127.0.0.1:631               0.0.0.0:*                   LISTEN      0          11715      1740/cupsd

tcp        0      0 127.0.0.1:25                0.0.0.0:*                   LISTEN      0          10825      1939/master

tcp        0      0 :::37382                    :::*                        LISTEN      1500       22646      6882/ora_d000_dbtes

tcp        0      0 :::111                      :::*                        LISTEN      0          10173      1641/rpcbind

tcp        0      0 :::1521                     :::*                        LISTEN      1500       21481      6952/tnslsnr

tcp        0      0 :::23602                    :::*                        LISTEN      29         1939       1685/rpc.statd

tcp        0      0 :::22                       :::*                        LISTEN      0          10768      1859/sshd

tcp        0      0 ::1:631                     :::*                        LISTEN      0          11714      1740/cupsd

tcp        0      0 ::1:25                      :::*                        LISTEN      0          10827      1939/master

udp        0      0 0.0.0.0:111                 0.0.0.0:*                               0          10165      1641/rpcbind

udp        0      0 0.0.0.0:24700               0.0.0.0:*                               29         1927       1685/rpc.statd

udp        0      0 0.0.0.0:631                 0.0.0.0:*                               0          11717      1740/cupsd

udp        0      0 0.0.0.0:968                 0.0.0.0:*                               0          10167      1641/rpcbind

udp        0      0 0.0.0.0:1013                0.0.0.0:*                               0          1921       1685/rpc.statd

udp        0      0 :::9648                     :::*                                    29         1935       1685/rpc.statd

udp        0      0 ::1:61374                   :::*                                    1500       22641      6882/ora_d000_dbtes

udp        0      0 ::1:14353                   :::*                                    1500       22586      6850/ora_pmon_dbtes

udp        0      0 :::111                      :::*                                    0          10170      1641/rpcbind

udp        0      0 :::47502                    :::*                                    1500       21758      6878/ora_mmon_dbtes

udp        0      0 ::1:23356                   :::*                                    1500       21664      6884/ora_s000_dbtes

udp        0      0 :::968                      :::*                                    0          10172      1641/rpcbind

Increase JAVA heap size in Oracle Application (EBS) 12.2.5

select developer_parameters from  fnd_cp_services

WHERE service_id = (SELECT manager_type

FROM fnd_concurrent_queues

WHERE concurrent_queue_name = 'FNDCPOPP');

You simply increase the value.

   UPDATE fnd_cp_services SET developer_parameters =

'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx4096m'

WHERE service_id = (SELECT manager_type

FROM fnd_concurrent_queues

WHERE concurrent_queue_name = 'FNDCPOPP');

Commit;

Oracle Receivables Receipt Data Setup Test (Doc ID 732201.1)

To Bottom

---

R12.0.6+ :  ORACLE RECEIVABLES (AR): RECEIPT DATA SETUP DIAGNOSTIC TEST To execute the test, do the following: Start Oracle E-Business Suite Connect to responsibility Application Diagnostics Select the Diagnose menu option Click button Select Application and select Application "Oracle Receivables" Scroll down to group "Receipts" Select test name "Receipt Data" Input Parameters (* required) Responsibility ID   Cash Receipt Id   Include GL Tables

AC-00005: No write permissions for creating the Context file – /tmp/temp.xml

Problem :

While making Oracle Application Clone :

Target System Root Service [enabled] :

Target System Web Entry Point Services [enabled] :

Target System Web Application Services [enabled] :

Target System Batch Processing Services [enabled] :

Target System Other Services [disabled] :

Do you want to preserve the Display [hooraps1:0.0] (y/n) ? : n

Target System Display [erp2:0.0] :
RC-50004: Error occurred in CloneContext:
AC-00005: No write permissions for creating the Context file – /tmp/temp.xml
Raised by oracle.apps.ad.context.AppsContext
Check Clone Context logfile /u07/appprod/apps/apps_st/comn/clone/bin/CloneContext_0908103640.log for details.

ERROR: Context creation not completed successfully.
For additional details review the file /tmp/adcfgclone_17325.err if present.

When you check log file you will get this :

StackTrace:
java.lang.Exception: AC-00005: No write permissions for creating the Context file – /tmp/temp.xml
Raised by oracle.apps.ad.context.AppsContext
at oracle.apps.ad.context.AppsContext.getOaEnabledValues(AppsContext.java:733)
at oracle.apps.ad.context.CloneContext.setConfigHome(CloneContext.java:2306)
at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:606)
at oracle.apps.ad.context.CloneContext.main(CloneContext.java:5023)

RC-50004: Error occurred in CloneContext:
AC-00005: No write permissions for creating the Context file – /tmp/temp.xml
Raised by oracle.apps.ad.context.AppsContext
Context file creation not succesful


Solution :

Simply go to this path by root user /tmp/temp.xml . Give 777 rights to temp.xl .
And now login with application user and run perl adcfgclone.pl appsTier !!

RC-50013 Fatal: Instantiate driver

Error:
Seen the issue during the execution of adcfgclone.
perl adcfgclone.pl dbTechStack
====================
WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
[APPLY PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: /EBS/oracle/product/12c/perl/bin/perl -I /EBS/oracle/product/12c/perl/lib/5.14.1 -I /EBS/oracle/product/12c/perl/lib/site_perl/5.14.1 -I /EBS/oracle/product/12c/appsutil/perl /EBS/oracle/product/12c/appsutil/clone
ouicli.pl INSTE8_APPLY 1
AutoConfig is exiting with status 1
WARNING: RC-50013: Fatal: Instantiate driver did not complete successfully.
/EBS/oracle/product/12c/appsutil/driver/regclone.drv
====================
CAUSE:
The script was trying to register the oracle home in inventory but its failing to update it.
SOLUTION:
Please delete existing files under oraInventory folder and retry the adcfgclone.

[oracle@ebsdb01 bin]$ cat /etc/oraInst.loc
inst_group=dba
inventory_loc=/EBS/oracle/product/oraInventory
cd /EBS/oracle/product
rm -rf oraInventory
mkdir oraInventory

Retry :   perl adcfgclone.pl dbTechStack

ORA-02062: distributed recovery received DBID

select * from DBA_2PC_PENDING;
select * from DBA_2PC_NEIGHBORS;
select * from sys.pending_trans$;
select * from SYS.PENDING_SESSIONS$;
select * from SYS.PENDING_SUB_SESSIONS$;

SELECT KTUXEUSN, KTUXESLT, KTUXESQN, /* Transaction ID */
KTUXESTA Status,
KTUXECFL Flags
FROM x$ktuxe
WHERE ktuxesta!='INACTIVE'


1. Force committing the transactions in collecting state:
COMMIT FORCE 'transaction_id',commit#;

2. execute DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY('transaction_id');

Transaction ID:
160.15.14218
17.25.695140
22.22.673214


Commit;

Scheduling Workflow Mailer Stop and Start events as good practice

The Workflow Notification Mailer runs on the generic service called Workflow Mailer Service, which in turn uses the Standard workshift, active 24 hours every day. This means the notification mailer runs non-stop.

 Not allowing the mailer to restart periodically may present some issues:

• The corresponding log file corresponding to the Workflow Mailer Service will grow several gigabytes large and eventually the OS will error due to I/O file handling.
• Some SMTP servers and IMAP servers used for outbound and inbound processing respectively, have time limits to the sessions connected to them. If the mailer reaches those time limits it will encounter a connection error and will be abnormally brought down.
• Similarly the same might happen to the session the mailer establishes to retrieve HTML and framework content from the application server. This is less likely though but it has been seen.
• The size of the INBOX folder in the IMAP server won't get expunged as long as the mailer does not refreshes the session. For a purged INBOX folder it takes the mailer to restart - and for parameter Expunge Inbox on Close to be set to Yes.

In order for the issues above to be minimized, a good practice is to schedule the Mailer to automatically go down and start up periodically, daily preferably. This can be done by using the event schedule feature provided in the Workflow Mailer configuration. This can be done as follows:

First, connect to EBS using the responsibility Workflow Administrator Web Applications and go to Workflow Manager

Then edit the Notification Mailer configuration. Continue going through the train stages until you reach the Schedule Events stage:

In the screen shot above the stopping event is set to happen at 11:50 PM and the starting event at 11:55 PM, and these are set to repeat every using 1440 minutes as the interval. If no interval value is specified the stop/start events are raised just once.