Skip to main content


Showing posts from January, 2018

Oracle E-Business Suite Maintenance

Select File System for maintenance: As pre-12.2 Oracle E-Business Suite releases has one file system, there was no choice about where maintenance activities had to be carried out from. Use of a dual file system in Release 12.2 has required the introduction of a Configuration Change Detector, which automatically detects when changes are made to one file system and replicates them to the other. Patching cycle is in progress: During this time maintenance tasks should be performed on the patch file system . If for some reason you need to perform such tasks on the run file system, you must either complete or abort the patching cycle first. No patching cycle is in progress: Maintenance tasks should be performed on run file system , then clone the run file system to the patch file system using the adop fs_clone command OR adop will run this command automatically in the prepare phase of the next patching cycle, which could increase time for patching cycle. Generating Files: File Types

Oracle E-Business Suite Password Management using AFPASSWD

AFPASSWD Utility: It is an enhanced version of FNDCPASS and includes the following features: It  prompts for passwords required for the current operation. It avoids the security risk incurred by entering passwords on the command line for FNDCPASS. User enter the new password twice to confirm. Can be used to migrate Oracle EBS user passwords to a non-reversible hash password scheme. Note: Always run AutoConfig after changing any system (type 2) password. Refer : How To Change Applications Passwords Using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) ( Doc ID 437260.1 )   To migrate Oracle E-Business Suite user passwords to a password hashing scheme: AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -m <HASH_MODE> {FULL|BACKGROUND|PARTIAL} Known issues of AFPASSWD: Adadmin Fails After Schema Password Is Changed Using AFPASSWD (Doc ID 1492939.1) ISSUE DURING AFPASSWD UTILITY RUN (Doc ID 2157967.1) AFPASSWD Relink Fails While Applying R

Oracle E-Business Suite Password Management using FNDCPASS

Oracle E-Business Suite Password Management: Before changing the APPS password using the FNDCPASS utility: Take backup of table FND_USER and FND_ORACLE_USERID . " alter user " command is not supported and should not be used for changing the apps password in any case. Always use FNDCPASS to change the APPS password. Check FNDCPASS log for any kind of error. If there is any error in the FNDCPASS log, then DO NOT run autoconfig or try to change configuration file manually. Until and unless FNDCPASS log has no error,  do not run autoconfig as you will get problem while logging in oracle application. If there is and error in the FNDCPASS log, then either restore table  FND_USER and FND_ORACLE_USERID to log into Applications or open SR to support with the FNDCPASS log. If you are on Oracle E-Business Suite Release 12.1 or 12.2 , ensure that your sqlnet_ifile.ora has the line SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8 (if the initialization parameter SEC_CASE_SEN

Oracle E-Business Suite Schema Type

Oracle E-Business Suite Schema: Type 1 . Schemas that exist in every Oracle database - SYS, SYSTEM. Type 2 . A small set of critical core schemas used by shared components of Oracle E-Business Suite - APPLSYSPUB, APPLSYS, APPS, APPS_NE. APPYSYSPUB schema: It is public account , and has only Read-Only privileges on a few tables and views for signing on to Applications . The password for this account can be seen from the OS in the environment variable or logical GWYUID. It was pointless to change it before the security patch that allowed the APPLSYSPUB password to be encrypted. Warning: The APPLSYSPUB password is unique in that it must be maintained as an uppercase password . This means that if you opt to change the APPLSYSPUB password in Oracle Database 11g, you must enter the new password in all uppercase to preserve system functionality. Oracle recommend that the APPLSYSPUB password should be changed on all Release 12.x systems , using either AFPASSWD or FNDCPASS. Au

Oracle E-Business Suite Scripts

Oracle E-Business Suite scripts: AutoConfig Scope and Components: 1. In Release 12.2 application tier is AutoConfig-enabled. 2. Applications context file location - INST_TOP as <INST_TOP>/appl/admin/<CONTEXT_NAME>.xml 3. The Release 12.2 database tier created via Rapid Install is also AutoConfig-enabled. 4. Database context file location - RDBMS ORACLE_HOME as <RDBMS_ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml AutoConfig components: Applications context - An XML repository located in the INST_TOP that contains information specific to the APPL_TOP.  Database context - An XML repository located in the RDBMS ORACLE_HOME that contains information specific to that database tier.  AutoConfig template files - Files containing named tags that are replaced with instance-specific information from the appropriate context, in the process of instantiation.  AutoConfig driver files - Every Oracle E-Business Suite product maintains a driver file used by Au

Data Modeling for Big Data | Data Modeling for Analytical Data

Data Modeling for BigData:

MySQL Sharding using ProxySQL | MariaDB Maxscale | MySQL ScaleArc | MySQL Router | MySQL Fabric

Sharding: Sharding means scale out. Each node runs MySQL instance. Data is partitioned across all nodes. Sharding key is used to distribute data across nodes.   Example of sharding: Each customer store data in their own schema MySQL instance per customer OS instance / container per customer Environment per customer includes database server Application server and required components Ref: MySQL Proxy SQL - MariaDB MaxScale - ScaleArc - MySQL Router - MySQL Fabric - Explore Sharding and commonly used solution for MySQL sharding:

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief down