Asif's Oracle Repository

Background:  When we run, the following SQL Query/Script will provide the profile option values set at different levels. That is Site, Application, Responsibility, User.  So, this script lists ALL Users/Responsibilities/Applications set against a particular Profile option SQL Script:   Enter 'Profile Option Name' as need to check  Eg. FND: Debug Log Enabled [You can get the exact name from table fnd_profile_options_tl]    SELECT fpo.profile_option_name SHORT_NAME,          fpot.user_profile_option_name NAME,          DECODE (fpov.level_id,                  10001, 'Site',                  10002, 'Application',                  10...

SELECT s.inst_id, NVL (s.username, 'Internal') "Database User", m.SID, s.serial#, p.spid "DB OS Process", m.TYPE, DECODE (m.lmode, 0, 'None', 1, 'Null', 2, 'Row Share', 3, 'Row Excl.', 4, 'Share', 5, 'S/Row Excl.', 6, 'Exclusive', lmode, LTRIM (TO_CHAR (lmode, '990')) ) "Lock Type", DECODE (m.request, 0, 'None', 1, 'Null', 2, 'Row Share', 3, 'Row Excl.', 4, 'Share', 5, 'S/Row Excl.', 6, 'Exclusive', request, LTRIM (TO_CHAR (m.request, '990')) ) "Lock Request", DECODE (command, 0, 'None', DECODE (m.id2, 0, dusr.username || '.' || SUBSTR (dobj.NAME, 1, 30), 'Rollback Segment' ) ) "Object", s.machine "Application Server", s.process "Apps OS process", m.ctime, NVL (NVL (usr.description, s.action), 'Database Session' ) "Online User,Concurrent", N...

  The Internal Workflow of an E-Business Suite Concurrent Manager Process                       Concurrent processing is one of the key elements of any E-Business Suite system. It provides scheduling and queuing functionality for background jobs, and it’s used by most of the application modules. As many things depend on concurrent processing, it’s important to make sure that the configuration is tuned for your requirements and hardware specification. This is the first article in a series about the performance of concurrent processing. We’ll take a closer look at the internals of concurrent managers, the settings that affect their performance, and the ways of diagnosing performance and configuration issues. Today we’ll start with an overview of the internal workflow of a concurrent manager process. Enjoy the reading! There are few things...

Perform the following to clone an Oracle home: Verify that the installation of Oracle Database to clone is successful. You can do this by reviewing the installActions date_time .log file for the installation session, which is typically located in the / orainventory_location /logs directory. If you install patches, then check their status using the following: $ cd $ORACLE_HOME/OPatch Include $ORACLE_HOME/OPatch in $PATH $ opatch lsinventory Stop all processes related to the Oracle home. See "Stopping Existing Oracle Processes" for more information about stopping the processes for an Oracle home. Create a ZIP file with the Oracle home (but not the Oracle base) directory. For example, if the source Oracle installation is in the /u01/app/oracle/product/11.2.0/dbhome_1 , then you zip the dbhome_1 directory by using the following command: # zip -r dbhome_1.zip /u01/app/oracle/product/11.2.0/dbhome_1 Do not include the admin , fast_recovery_area , and oradata dir...

      Oracle Database 18c is Oracle 12c Release 2 (12.2.0.2) In the old terms, Oracle Database 18c is a patchset for Oracle 12.2.(18c = 12.2.0.2)   Release Version Numbering Changes Beginning in 2018, a new numbering schema for the database software is implemented. Instead of a legacy nomenclature such as 12.2.0.2, a three (3) field format consisting of: Year. Update. Revision is used, such as 18.1.0. This allows clear indication of: •the feature release designation of the database software (the first field) •the quarterly Update (the second field) •the quarterly Revision (the third field)   18c released as : •1-Mar-2018 - 18c released in OCI and OCI-C Database services (note: we earlier indicated in error these were released 16-Feb) •16-Feb-2018 - 18c is released for Exadata and LiveSQL.oracle.com   Release 12.2: New releases will be annual and the version will be the last two digits of the release year. The release originally planned as...

 Startup sequence of Grid Infrastructure daemons and its resources in 11gR2 RAC. OHASD Phase OHASD Agent Phase CRSD Agent Phase CRSD Agent Phase crsd.bin starts two more agents (crsd orarootagent(Oracle root agent) and crsd oraagent(Oracle Agent)) 1. When a node of an Oracle Clusterware cluster start/restarts, OHASD is started by platform-specific means. OHASD is the root for bringing up Oracle Clusterware. OHASD has access to the OLR (Oracle Local Registry) stored on the local file system. OLR provides needed data to complete OHASD initialization. 2. OHASD brings up GPNPD and CSSD. CSSD has access to the GPNP Profile stored on the local file system. This profile contains the following vital bootstrap data; a. ASM Diskgroup Discovery String b. ASM SPFILE location (Diskgroup name) c. Name of the ASM Diskgroup containing the Voting Files 3. The Voting Files locations on ASM Disks are accessed by CSSD with well-known pointers in the ASM Disk headers and CSSD...

   While running adcfgclone.pl as oracle user, the session just hangs without giving any error in the log file. The issue was that it wasn’t able to connect to the database as : sqlplus "/as sysdbaa This can be  occur due to improper shutdown of the database. While in the course of a database shutdown, if any of the oracle process is not completed killed and it holds a large shared memory segment, such issues can occur which would prevent from normal database operation. So next time when an instance tries to start it is not able to grab a large chunk of memory to get started. This can be checked as follows: After the database has been shut down , there shouldn’t be any processes running as oracle on the server level: ipcs -m | grep <oracle user> eg: ipcs -m | grep oracle key              shmid          owner   perms ...