Friday, September 23, 2022

Post Clone Steps on EBS Environment

 Post Clone Steps on EBS Environment

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


1) Drop the Private Database link using apps user( ie these db link names are depend on your environment, just for example)


drop database link XXTEST.NIZAMAPPSDBA.COM;

drop database link XXTEST1.NIZAMAPPSDBA.COM;


2) Drop the Private Database link using sys user( ie these db link names are depend on your environment, just for example)


exec dropschema_dblinks('NIZAMAPPSDBA);

exec dropschema_dblinks('APPS');


3) Update the Worflow tables and FND table on Clone Environment(depend on your environment, just for example below)


Update apps.wf_systems (This should show the target Instance and not the source Instance)


select name,display_name from apps.wf_systems;

update apps.wf_systems set name=’<SID>’,display_name=’ <SID>.<hostname.domainname>’;

COMMIT;


eg: update apps.wf_systems set name='TEST.NIZAMAPPSDBA.COM',display_name='TEST.AU123.NIZAMAPPSDBA.COM’;


update apps.wf_systems set name='UATTEST.NIZAMAPPSDBA.COM',display_name='UATEST.DX123.NIZAMAPPSDBA.COM’;



UPDATE wf_notifications SET status ='CLOSED',mail_status ='SENT', end_date ='26-JAN-16' WHERE mail_status in ('MAIL','INVALID','OPEN');


update wf_agents set address = replace (address,'PROD','DEV') ;


eg: update wf_agents set address = replace (address,'HRD','TEST') ;

update wf_agents set address = replace (address,'HRD','UATTEST') ;


select name ,display_name from wf_systems;


update wf_systems set DISPLAY_NAME = replace (DISPLAY_NAME,'PROD.DBALOUNGE.COM','DEV.DBALOUNGE.COM');


eg:update wf_systems set DISPLAY_NAME = replace (DISPLAY_NAME,'PROD.NIZAMAPPSDBA.COM','TEST.NIZAMAPPSDBA.COM'); 

   update wf_systems set DISPLAY_NAME = replace (DISPLAY_NAME,'PROD.NIZAMAPPSDBA.COM','UATTEST.NIZAMAPPSDBA.COM'); 


Commit;


Update the target node in CM fnd_concurrent_queues table using below post_clone.sql script. values will be different and it is based on our environment



WHENEVER SQLERROR EXIT FAILURE

WHENEVER OSERROR EXIT FAILURE


SET echo OFF

SET linesize 150

set verify off

SET show OFF


define Backup_date = "&Backup_Date"


UPDATE fnd_profile_option_values

SET profile_option_value = 'Production Copy '||'&BACKUP_DATE'

WHERE profile_option_id=125;


UPDATE fnd_concurrent_queues

SET node_name='TEST1243'

WHERE node_name in('PROD252','PROD253','PROD214','PROD215','PROD258','PROD259','PROD250','PROD251');


UPDATE fnd_concurrent_queues

SET node_name2='TEST1243'

WHERE node_name2 in('PROD252','PROD253','PROD214','PROD215','PROD258','PROD259','PROD250','PROD251');


UPDATE fnd_concurrent_queues

SET node_name2='TEST1243'

WHERE node_name2 in('PROD252','PROD253','PROD214','PROD215','PROD258','PROD259','PROD250','PROD251');


UPDATE fnd_concurrent_queues

SET target_node='TEST1243'

WHERE target_node in('PROD252','PROD253','PROD214','PROD215','PROD258','PROD259','PROD250','PROD251');


UPDATE fnd_concurrent_queues

SET target_node='TEST1243'

WHERE target_node in('PROD252','PROD253','PROD214','PROD215','PROD258','PROD259','PROD250','PROD251');


commit;


4) Cleaning the Clone Setup and Change the password in Clone Environment


FNDCPASS apps/****** 0 Y system/**** SYSTEM APPLSYS apps


FNDCPASS apps/***** 0 Y system/****** USER sysadmin Welcome123456789



perl $FND_TOP/patch/115/bin/txkManageDBConnectionPool.pl


exec FND_CONC_CLONE.SETUP_CLEAN;



Run cmclean.sql


1. Change the value for context variables s_url_protocol, s_local_url_protocol,s_webentryurlprotocol in context file from https to http. 

3. Change the value of s_help_web_agent, s_login_page, s_external_url context variables to point to http url and the port in the url refers to s_webport.

4. Change the value of s_enable_sslterminator to -  <sslterminator oa_var="s_enable_sslterminator">#</sslterminator>  


AUTOCONFIG

-----------

Run adautocfg.sql in DB and Apps Tier



$FND_TOP/bin/txkrun.pl -script=SetSSOReg -removereferences=yes -appspass=apps


Run adautocfg.pl in DB and Apps Tier


Start the application services.


5) Profile change if SSO to disabled on Clone Environment

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


Application Authenticate Agent to NULL

Applications SSO Type to SSWA

Applications SSO Login Types to Local

Applications Single Sign On Hint Cookie Name to ORASSO_AUTH_HINT

Application SSO LDAP Synchronization to NULL

Applications SSO Auto Link User to NULL

Applications SSO User Creation and Updation Allowed to NULL


 

6) Disable_concurrent_request on Clone Environment

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


update fnd_concurrent_requests

set phase_code = 'C', status_code = 'X'

where status_code in ('Q','I','P','R')

and requested_start_date > SYSDATE

and hold_flag = 'N';



update fnd_concurrent_requests

set phase_code = 'C', status_code = 'X'

where requested_start_date > SYSDATE

and hold_flag = 'N';


update fnd_concurrent_requests

set phase_code = 'C', status_code = 'X';


define Backup_date = "&Backup_Date"


UPDATE fnd_profile_option_values

SET profile_option_value = 'Production Copy '||'&BACKUP_DATE'

WHERE profile_option_id=125;


7) Data Masking on Clone Environment, ie it depend on the evironment and organization requirement

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


login to database using HR schema, run below scripts


create table Per_all_people_f_nomask as select *from Per_all_people_f;

update Per_all_people_f

set full_name=dbms_random.string('U', 20),

first_name=dbms_random.string('U', 20),

last_name=dbms_random.string('U', 20),

middle_names=dbms_random.string('U', 20),

global_name=dbms_random.string('U', 20),

local_name=dbms_random.string('U', 20);


create table per_phones_nomask as select *from per_phones; 

update per_phones

set phone_number=trunc(dbms_random.value(1000000000,9999999999));


create table per_analysis_criteria_no_mask as select *from per_analysis_criteria; 

update per_analysis_criteria

set segment1=trunc(dbms_random.value(1000000000,9999999999)),

segment5=trunc(dbms_random.value(1000000000,9999999999)),

segment6=trunc(dbms_random.value(1000000000,9999999999));






Thursday, September 22, 2022

Demantra related Docs

 Information Center:Demantra Install, Upgrade, Patching,Technical Config (Doc ID 1400207.2)


Install Demantra ~ How to UPGRADE ~ Main Release Patches List And Recommended Patches (Doc ID 1342064.1)



Demantra - Development Sponsored Document Library. CRITICAL Updates, Comprehensive, Effective Technical Briefs, Guides, Notes +! (Doc ID 2245610.1)



To BottomTo Bottom

Tuesday, September 13, 2022

R12 E-Business Suite Concurrent Processing Script Cpadmin.sh Command Line Utility Which Consolidates Existing CP Tools Into A Single Menu-Based Shell Script (Doc ID 2319585.1)

 

APPLIES TO:

Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

GOAL

E-Business Suite R12 Concurrent Processing, Concurrent Manager and Request issues

 

 

 

 

Provide documentation and resources for the new cpadmin.sh command line utility.

The cpadmin.sh script is a command-line tool which consolidates various existing tools for concurrent processing into a single menu-based utility run via a shell script.

 

SOLUTION

The new cpadmin.sh utility initial announcement was provided in the following blog article released by development:

https://blogs.oracle.com/stevenchan/new-cpadmin-utility-for-managing-concurrent-processing-now-available

 

The cpadmin.sh utility is formally documented by development in the following user guide:

https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T575591.htm#8159578

 

This adadmin style utility was designed to integrate the following Concurrent Processing features in one script.

It has the following menu options:

Manager Status

This option is used to view the status of concurrent managers and services.

Use this option to display running managers (with or without process IDs) or display all managers.

The same status information is shown in Administer Concurrent Managers form and OAM Concurrent Managers page.

Clean CP Tables

Use this option to clean up the concurrent processing tables. This utility replaces cmclean.sql. Use this option when the Internal Concurrent Manager (ICM) fails to start due to corrupted/conflicted tables. Note the following actions when choosing this option:

Managers must be stopped first (the utility will verify this).
Clean up inconsistencies in manager tables; remove corruption.
Reset manager states for clean start-up.
Clean and reset Advanced Queue tables for the Output Post-Processor and FNDSM Service Manager.
Reset request conflicts for the Conflict Resolution Manager (CRM).
Identify and clean orphaned requests.

This option is supported by Oracle for use on client systems.

Important: DO NOT USE the cmclean.sql script.

Set Manager Diagnostics

Turn diagnostics on or off for individual managers with this option. You can use this option to turn diagnostics on/off for specific managers without bouncing all services.
This option is available for:

ICM
CRM
Output Post-Processor
Request Processing Managers
Transaction Managers

Each option will display the current diagnostic status (ON or OFF) of the running managers/services and allow you to change the status.

Manager Control

Use this option to send a request such as start, stop, or verify to an individual manager.

Use to send a control request to a manager or service.

This option does the following:

Displays current status of all managers and processes.
Once a manager or service is chosen, offers valid control options for that specific choice.
Valid options for managers: activate, deactivate, verify, restart, abort, shut down.
Valid options for services also include: suspend and resume. Any service can be programmed to respond appropriately to each option; but if one is not, then the service will not respond.

Rebuild Manager Views

Use when Manager Views must be rebuilt.

This option rebuilds the FND_CONCURRENT_WORKER_REQUEST and FND_CONCURRENT_CRM_REQUESTS views with the following steps:

Managers must be stopped first. The utility verifies that these are stopped.
Rebuilds FND_CONCURRENT_WORKER_REQUESTS.
Rebuilds FND_CONCURRENT_CRM_REQUESTS.

Running this option is the same action as running FNDCPBWV.

Move Request Files

Change request log and output file locations with this option.

Use to update the concurrent processing tables for changing the following values for request LOG file, OUT file, or BOTH:

Individual requests: fully qualified file name or node name
Range of requests: directory name or node name
Range of requests can be selected by minimum/maximum date or minimum/maximum request_id

Important: The cpadmin utility changes only the concurrent processing database table values to support movement. The files must be manually moved by an administrator.

Analyze Request

Use this option to analyze a concurrent request.

Use when analyzing a request for any reason. This is non-destructive.

Managers need not be shut down for this option.

This option does the following:

Checks the manager's status.
Analyzes the request's status.
Provides a detailed report on concurrent program.
Gives a detailed report on request's current status.

Running the cpadmin utility:

Complete the steps below to run the command-line utility and its maintenance tasks.

1. Set the environment. in order to apply the environment variables defined for the system. See Setting the Environment, Oracle E-Business Suite Maintenance Guide for more information.
2. From any directory, start cpadmin with the below command:
   $ cpadmin.sh
   The utility starts and prompts you for the APPS password (required).
3. Respond to prompts. Supply the information requested by cpadmin prompts. Prompts unique to an option are described with the option. When you complete the prompts, the Main Menu appears.
4.Choose one of the tasks listed above.
5. Exit the cpadmin utility.

 

Note:

CPADMIN utility is designed only for interactive mode, and there is no documentation for it to be used otherwise.

Wednesday, September 7, 2022

Title Migrate EBS to OCI EBS Cloud Manager

https://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/compute-iaas/creating_backup_of_ebs_instance_on_oci/101_backup_oci.html

 https://apexapps.oracle.com/pls/apex/f?p=133:180:106932995936354::::wid:753

https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=672&clear=RR,180&session=104626518666679


Deploying Oracle E-Business Suite Cloud Manager Version 20.1.1.X on Oracle Cloud Infrastructure (Doc ID 2434500.1)


  • Create the Source Oracle E-Business Suite Environment
  • Prepare the Source Oracle E-Business Suite Environment
  • Install the Oracle E-Business Suite Cloud Backup Module
  • Create a Backup with the Oracle E-Business Suite Cloud Backup Module
  • Deploy an EBS Environment on Cloud Manager from a Backup
Lift and Shift On-Premises EBS to OCI
  • Prepare your tenancy for Oracle E-Business Suite
  • Oracle E-Business Suite Cloud Manager Deployment and Configuration
  • Provision Oracle E-Business Suite Environment
  • Clone Oracle E-Business Suite Environment







Monday, September 5, 2022

Apps password not working

 Someone changed apps password using 'alter user' which is not a good practice.


Now during a clone, password change is not working using FNDCPASS.


1) SEC_CASE_SENSITIVE_LOGON parameter is already set to FALSE

2) select fnd_web_sec.validate_login('GUEST','ORACLE') from dual;

FND_WEB_SEC.VALIDATE_LOGIN('GUEST','ORACLE')
--------------------------------------------------------------------------------
Y
3) There is no error on FNDCPASS but password change is not successful.



So, this is what we did as a fix,


Changed apps password to default apps/apps -- using 'alter user'.

Updated password in FND_ORACLE_USERID to apps using encrypted value.

and then re-tried FNDCPASS, this time it was successful.


EBSPROD> create table FND_ORACLE_USERID_BAK as (select * from FND_ORACLE_USERID);

Table created.

EBSPROD> create table FND_USER_BAK as (select * from FND_USER);

Table created.


SQL> ALTER USER apps IDENTIFIED BY apps;

User altered.

SQL> ALTER USER applsys IDENTIFIED BY apps;

User altered.

Below is the value for encrypted apps password --


SQL> update apps.FND_ORACLE_USERID set ENCRYPTED_ORACLE_PASSWORD = 'ZGA34EA20B5C4C9726CC95AA9D49EA4DBA8EDB705CB7673E645EED570D5447161491D78D444554655B87486EF537ED9843C8' where ORACLE_USERNAME in ('APPS', 'APPLSYS');

2 rows updated.

SQL> commit;

Commit complete.


#######################
col user_name for a30
select USER_NAME from APPS.fnd_user order by 1;



CREATE FUNCTION apps.decrypt_pin_func(in_chr_key IN VARCHAR2,in_chr_encrypted_pin IN VARCHAR2)
RETURN VARCHAR2

     AS
LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String';
/


######################
SYSADMIN
=========
SELECT APPS.decrypt_pin_func('GUEST/ORACLE',(SELECT ENCRYPTED_FOUNDATION_PASSWORD from APPS.fnd_user where USER_NAME='GUEST')) from dual;
SELECT ENCRYPTED_USER_PASSWORD FROM APPS.FND_USER where USER_NAME='SYSADMIN';
SELECT APPS.decrypt_pin_func('&appspwd','&sysadminkey') from dual;

Oracle E-Business Suite Release 12.2 System Schema Migration

In This Document Section 1: Overview of the EBS System Schema Section 2: Requirements for Using the EBS System Schema Section 3: Migrating t...