Cloning fails at 50% with RC-00118 or RC-50004 after creating control files



-------------------ADX Database Utility Finished---------------
RC-00118: Error occurred during creation of database
Raised by oracle.apps.ad.clone.ApplyDatabase

StackTrace:
java.lang.Exception: Control file creation failed
at oracle.apps.ad.clone.ApplyDatabase.doConf(ApplyDatabase.java:635)
at oracle.apps.ad.clone.ApplyDatabase.doApply(ApplyDatabase.java:473)
at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:366)
at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:110)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:67)
at java.lang.Thread.run(Unknown Source)
====================================================================




Cause:

The listener.ora contains the source listener name

This was originally resolved in CloneContext.java (12.1 - 120.92.12010000.16) but is present again in version: 120.92.12010000.24

This is reported in Bug :12598630 - R12 CLONING FAILS AT 50% DUE TO LISTENER.ORA CONTAINING SOURCE NAME


Workaround:

The Workaround is to make the change on the temporary stage context file prior to the file copy:

1. edit CTXORIG.xml either after adpreclone.pl or before adcfgclone.pl
2. change the s_db_listener value from Source to Target
3. copy files to target
4. run perl adcfgclone.pl dbTier

If the Clone has already failed, the workaround/solution would be:

1. correct the s_db_listener value in the Target context file
2. shutdown the target Database
3. run: perl adcfgclone.pl dbtier /path/to/contextfile.xml

Change Host Name in Red Hat and Oracle Linux

Make sure you are logged in as root and move to /etc/sysconfig and open the network file in vi.

cd /etc/sysconfig
vi network

Look for the HOSTNAME line and replace it with the new hostname you want to use. In this example I want to replace localhost with redhat9.

HOSTNAME=vis.expolanka.com

When you are done, save your changes and exit vi. Next we will edit the /etc/hosts file and set the new hostname.

vi /etc/hosts

In hosts, edit the line that has the old hostname and replace it with your new one.

192.168.1.110     vis.expolanka.com    vis

Save your changes and exit vi. The changes to /etc/hosts and /etc/sysconfig/network are necessary to make your changes persistent (in the event of an unscheduled reboot).

Now we use the hostname program to change the hostname that is currently set.

hostname vis.expolanka.com 

And run it again without any parameters to see if the hostname changed.

hostname

Finally we will restart the network to apply the changes we made to /etc/hosts and /etc/sysconfig/network.

service network restart

You can follow either the first option OR the second one.

Type the following command to enter GUI mode.

[root@localhost ~]# system-config-network

• Go to “DNS Configuration”.
• Modify your preferred hostname and click OK.
• Click ” Save & Quit”.
• Save and reboot your server.

Disable log_archive_dest_3

disable log_archive_dest_3

[root@ebiz Desktop]# su - oraebiz

[oraebiz@ebiz ~]$ 

[oraebiz@ebiz ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Thu Jun 15 11:53:35 2017

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> show parameter log_archive_config;

NAME     TYPE VALUE

------------------------------------ ----------- ------------------------------

log_archive_dest_25     string

log_archive_dest_26     string

log_archive_dest_27     string

log_archive_dest_28     string

log_archive_dest_29     string

log_archive_dest_3     string SERVICE=prodstb2 NOAFFIRM ASYN

C VALID_FOR=(ONLINE_LOGFILES,P

RIMARY_ROLE) DB_UNIQUE_NAME=PR

ODSTB2

SQL> select dest_name,status,error from v$archive_dest_status where dest_id=3;

DEST_NAME

--------------------------------------------------------------------------------

STATUS  ERROR

--------- -----------------------------------------------------------------

LOG_ARCHIVE_DEST_3

BAD PARAM

SQL> alter system set log_archive_dest_3='';

System altered.

You could also disable it by setting the state to DEFER:

SQL> alter system set log_archive_dest_state_3=defer;

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 ManagerThen 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

R12.0.6+ : Oracle Payables Invoice Data Collection Test (Doc ID 732163.1)

APPLIES TO:

Oracle Payables - Version 12.0.6 and later
Information in this document applies to any platform.

MAIN CONTENT

12.0.6 - 12.2 Legacy: :SQLAP:Invoice Data Data Collection

Description

This diagnostic test will display all of the data for all of the tables used to process an invoice in Payables.

This test is applicable for all Payables invoice and payment issues.

No validation will be done on the data collected, therefore no error or warning messages will be provided.

EBS Applicable Releases: 12.0.6 - 12.2
Application Name: Oracle Payables
Test Group: Invoice
Test Name: Invoice Data
Note: Click Here to Get Latest XML File(APListXml.xml 120.x.support.version uploaded on 16-Jun-2014).  Please review the README.txt file included in the zip file for installation instructions. 

RECOMMENDED:  Install and use the standalone version of this diagnostic.  It provides many advantages to the diagnostic framework version referenced in this document.  Please see Doc ID 1677861.1 for more details on the advantages it provides and for instructions on how to install and run.

Usage Instructions

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 "Payables" Scroll down to group "Invoice" Select test name "Invoice Data" Input Parameters (* required) Responsibility Id (LOV) *   Search Criteria (LOV)   Supplier Name (LOV)   Invoice Id (LOV) *   Include GL Tables (Yes or No) (LOV)   Include Related Data (Yes or No) (LOV)   Max Rows Displayed   Output contains Ledger Definition Secondary Ledgers Setup Summary Trial Balance Invoice Payment Tax Accounting 11.5 AX Accounting ( if exists ) 11.5 AP Accounting ( if exists ) General Ledger 11.5 MRC ( if exists ) Supplier Purchasing Encumbrance Prepayment Payment Document and Bank Cash Management Treasury Confirmation Currency Argentina Localizations (if applicable)