Usman Shahid Oracle Apps DBA / APPS DBA / EBS DBA / Oracle E-Business Suite Applications

  Oracle Application Express (APEX) is a low-code development platform that enables you to build scalable, secure enterprise apps, with world-class features, that can be deployed anywhere. Here are the step by step instructions to install Oracle Apex 20.1 on Windows and Unix/Linux systems.  Oracle Apex Installation Requirements Oracle Application Express release 20.1 requires  an Oracle Database release 18c or later, OS Windows 10 / Linux  There are the steps to install Oracle Application Express release 20.1. Step 1 Download Apex To download Oracle Application Express release 20.1, go to following link: https://www.oracle.com/tools/downloads/apex-201-downloads.html Step 2. Unzip in desired location  After downloading, you will get a zip file named something like - apex_20.1. Copy the file from the default download folder and paste it to the folder in which you want to install Oracle Apex 20.1, for example, I moved this file to F:\oracle\apex20, and after extracting the file, I got the

  In this section, we will see how we can change the login prompts/text attributes. For example, we want to change the default prompt from “User Name” to “Account Name”. This can be done very easily by customizing the seeded messages. To change the text attribute, perform the steps below: Login to Oracle E-Business Suite with any user having “Application Developer” Responsibility. Open “Messages” using the navigation given below: Navigation: Application Developer > Application > Messages Change the “Current Message Text” from “User Name” to “Account Name” and Save. Bounce OACore using the commands below. Enter weblogic password when prompted. [oracle@apps html]$ admanagedsrvctl.sh stop oacore_server1 [oracle@apps html]$ admanagedsrvctl.sh start oacore_server1 Clear Browser Cache and the changes would be visible. The following text prompts are available to be changed. Sl. No Message Default Value 1 FND_SSO_USER_NAME User Name 2 FND_SSO_PASSWORD Password 3 FND_SSO_FORGOT_PASSWORD L

  Here, we will see a few basic examples to customize the Login page. 1. Changing Login Page Background Login to putty using ‘oracle’ user and initialize to the ‘Run’ file system. [oracle@apps ~]$ . /u01/install/APPS/EBSapps.env run Note down the path for OA_MEDIA. [oracle@apps ~]$ echo $OA_MEDIA /u01/install/APPS/fs1/EBSapps/comn/java/classes/oracle/apps/media Transfer the image in this path, in my case which is login.png. [oracle@apps ~]$ cd $OA_MEDIA [oracle@apps media]$ ls -lrt login.png -rw-r--r-- 1 oracle oinstall 533676 Mar 4 15:34 login.png Next, note down the path for OA_HTML directory. [oracle@apps ~]$ echo $OA_HTML /u01/install/APPS/fs1/FMW_Home/Oracle_EBS-app1/applications/oacore/html Create a css file called ‘custom-login.css’ and add the following. Note that you should not amend the login.css or login.js file in the OA_HTML directory. body { height: 100%; background-repeat: no-repeat; background-attachment: fixed; background-position: cen

  EBS 12.2.10: step by step multitenant cloning with 19c Database  This post is not about how we normally do an EBS 12.2 cloning. You can search many blogs, articles over web. Well, in this post i am going to illustrate on how we can clone an EBS 12.2.10 environment where the Database is 19c multitenant with one CDB and one PDB. The main challenge comes when we want to do a restore the database and rename it based upon our target convention. Did, any of the below questions come to your mind, when you are about to do these sort of clone 1. When we do a restore/recover the database which is multitenant in nature, then in the target, then how the database will be opened 2. Which script to use to achieve the multitenant clone for EBS 3. How to rename the PDB after clone High level Steps:- Run adpreclone on the source database and application nodes. Back up the full Container Database (CDB) database with archives by using RMAN Hot backup and copy it to the target node. Clean up the target d

  We have seen this error couple of times in the Concurrent manager Administer screen in our R12.1.3 QA instances. OPP Concurrent Manager status : System Hold, Fix Manager before resetting counters Solution: 1. Shutdown the Apps Tier cleanly make sure there are no sessions:  [applmgr@oracle ~]$ cd $ADMIN_SCRIPTS_HOME [applmgr@oracle scripts]$ ./adstpall.sh apps/***** [applmgr@oracle ~]$ ps -ef | grep FNDLIBR [applmgr@oracle ~]$ ps -ef | grep FNDSM [applmgr@oracle ~]$ ps -ef | grep FNDCRM [applmgr@oracle ~]$ ps -ef | grep FNDFS [applmgr@oracle ~]$ ps -ef | grep applmgr 2. Stop the database. [ora@oracle  ~]$ sqlplus / as sysdba SQL*Plus: Release 11.1.0.7.0 - Production on Tue Dec 14 14:28:07 2021 Copyright (c) 1982, 2008, Oracle.  All rights reserved. Connected to an idle instance. SQL> shut immediate 3. Start the database. [ora@oracle ~]$ sqlplus / as sysdba SQL*Plus: Release 11.1.0.7.0 - Production on Tue Dec 14 14:28:07 2021 Copyright (c) 1982, 2008, Oracle.  All rights reserved. C

  REP-0069: Internal error REP-57054: In-process job terminated:Terminated with error: REP-1804: Unable to open printer definition file '/apps/apps_st/appl/CUST_TOP/12.0.0/reports/HPL.prt'. Solution :-   Verify HPL.prt file location and copy HPL.prt file to ( '/apps/apps_st/appl/CUST_TOP/12.0.0/reports/HPL.prt' ) path. [applmgr@oracle ]$ locate HPL.prt /apps/apps_st/appl/fnd/12.0.0/reports/HPL.prt [applmgr@oracle ]$ cp /apps/apps_st/appl/fnd/12.0.0/reports/HPL.prt  /apps/apps_st/appl/CUST_TOP/12.0.0/reports/ Now retest issue.

  Encountered while restoring the server on test database. Restore log file :- Finished restore at 03-MAR-22 released channel: c1 released channel: c2 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of switch command at 03/03/2022 22:58:55 ORA-19563:  header validation failed for file RMAN> CAUSE :- Check alerts log in target and get the file number/name for which throwing this error . SQL > SELECT FILE#, NAME FROM V$DATAFILE where  NAME like '%system%'; FILE#           NAME -----------      -------------  92            /u01/test/db/apps_st/data/system17.dbf  139          /u01/test/db/apps_st/data/system17.dbf Solution :- Rename the file like (system17.dbf to system18.dbf) SQL > SELECT FILE#, NAME FROM V$DATAFILE where  NAME like '%system%'; FILE#           NAME -----------   

  ERROR :  SQL> startup ORACLE instance started. Total System Global Area 2.1475E+10 bytes Fixed Size                 12170960 bytes Variable Size            3019901232 bytes Database Buffers         1.8388E+10 bytes Redo Buffers               54935552 bytes Database mounted. ORA-01172: recovery of thread 1 stuck at block 3024 of file 19 ORA-01151: use media recovery to recover block, restore backup if needed Cause:  This error usually means that blocks of file 19 are corrupted, In this case we need to recover file 19. Crash recovery or instance recovery could not apply a change to a block because it was not the next change.  This can happen if the block was corrupted and then repaired during recovery. SOLUTION :-  We need to recover all of corrupted block by using data file recovery or Database recovery.  In my case I have recover datafile 19. SQL>  recover datafile 19; Media recovery complete. SQL> alter database open; Database altered. SQL> select name,OPEN_MODE from v$d