Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Month: September 2017

September 1, 2017 ORACLE APPLICATIONS R12 ARCHITECTURE
APPS DBAInstallations/Configurations-ApplicationsOracle APPS DBA

ORACLE APPLICATIONS R12 ARCHITECTURE

 

  • Oracle E-Business Suite Release-12 have a Multi-tiered Architecture, that supports Oracle Applications products.
  • They are comprised of a Database Tier which manages the Oracle Database and stores all data.
  • An Application Tier hosts various servers, manages communication between the desktop and database tier and contains the application file system.
  • Client Desktop through which user access Oracle Applications.

 

Architecture-R11i vs R12

                                              Architecture-R11i vs R12

1. Desktop Tier

  • The client interface is provided through HTML for HTML-based applications, and via a Java applet in a Web browser for the traditional Forms-based applications.
  • In Oracle Applications Release 12, each user logs in to Oracle Applications through the E-Business Suite Home Page on a desktop client web browser.
  • The E-Business Suite Home Page provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications.
  • Oracle JInitiator will no longer be required to run Oracle Forms in E-Business Suite Release 12.
  • Oracle Forms in Release 12 will run directly in the native Sun Java2 Standard Edition plug-in.
  • The Forms client applet is a general-purpose presentation applet that supports all Oracle Applications Forms-based products, including those with customization and extensions.
  • The Forms client applet is packaged as a collection of Java Archive (JAR) files.
  • The JAR files contain all Java classes required to run the presentation layer of Oracle Applications forms.

2. Application Tier

  • The application tier has a dual role, hosting the various servers and service groups that process the business logic, and managing communication between the desktop tier and the database tier.
  • This tier is sometimes referred to as the middle tier.
  • Four servers or service groups comprise the basic application tier for Oracle Applications:
  1. Web services
  2. Forms services
  3. Concurrent Processing server
  4. Admin server

3. Database Tier

  • The database tier contains the Oracle database server, which stores all the data maintained by Oracle Applications.
  • The database also stores the Oracle Applications online help information. More specifically, the database tier contains the Oracle data server files and Oracle Applications database executable that physically store the tables, indexes, and other database objects for your system.
  • The database server does not communicate directly with the desktop clients, but rather with the servers on the application tier, which mediate the communications between the database server and the clients.

 

 

September 1, 2017 Oracle RMAN Commands List
Installation/Configurations10gInstallation/Configurations11gInstallation/Configurations12cOracle Database Material

Oracle RMAN Commands List

Here is the list of key most RMAN commands that are used for Backup and related activities:

 

LIST Commands

LIST Commands are generic RMAN commands that will show/list various types of information when executed within RMAN utility.

RMAN> list backup;

It lists all the backups taken using RMAN utility.

RMAN> list backup of database;

The above command lists out all the (individual) files that are in the backup.

RMAN> list backup of tablespace system;

The above command lists out all the files that are in the backup that belong to the tablespace ‘system’.

RMAN> list backup of control file;

The above command lists out all backups of the control file.

 

CONFIGURE Commands

CONFIGURE commands in RMAN are used to configure/setup various initial settings:

RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY2;

The above commands indicates how many days the backup copies need to be retained. Default is 1 day.

RMAN> CONFIGURE RETENTION POLICY CLEAR;

The above command resets the Retention policy to the default value of 1 day.

CONFIGURE BACKUP OPTIMIZATION ON;

The above command verifies to make sure that identical files are NOT backed up to the device specified.

CONFIGURE BACKUP OPTIMIZATION CLEAR;

The above command resets the Optimization option to the default value.

 

SHOW Commands

Show commands are used to show/display the configuration setting values.

RMAN> show all;

The above command shows all the current configuration settings on the screen.

RMAN> show retention policy;

The above command shows the current retention policy.

RMAN> show default device type;

The above command shows the default device type configured for backups.

RMAN> show datafile backup copies;

The above command shows the number of backup copies available in the target database.

 

BACKUP Commands

Backup commands are the real commands which do the actual backup work.

RMAN> backup database;

The above command backs up the database (target).

RMAN> backup database include current controlfile plus archive log;

The above command backs up the target database and the current control file and archive log files.

 

REPORT Commands

Report commands list/report specific information. The difference between report and list command is report command output is in a better format.

RMAN> report obsolete;

The above command reports which backups can be deleted.

 

DELETE Commands

Delete commands delete/remove specific items from the server, repository catalog.

RMAN> delete obsolete;

The above command deletes all the backups that are older based on the retention policy setup.

 

 

September 1, 2017 PL/SQL Code For Dropping All Objects in Schema
Database ScriptsScripts

PL/SQL Code For Dropping All Objects in Schema

 

DECLARE
v_itemcount INTEGER;
BEGIN
SELECT Count(*)
INTO   v_itemcount
FROM   all_objects AO
WHERE  AO.owner = USER
AND AO.object_type NOT IN ( ‘INDEX’ )
AND AO.object_name NOT LIKE ‘BIN$%’;

WHILE ( v_itemcount > 0 ) LOOP
FOR v_cmd IN (SELECT ‘drop ‘
|| AO.object_type
|| ‘ ‘
|| AO.object_name
|| Decode(AO.object_type, ‘TABLE’,
‘ CASCADE CONSTRAINTS’,
) AS DROPCMD
FROM   all_objects AO
WHERE  AO.owner = USER
AND AO.object_type NOT IN ( ‘INDEX’ )
AND AO.object_name NOT LIKE ‘BIN$%’) LOOP
BEGIN
EXECUTE IMMEDIATE v_cmd.dropcmd;
EXCEPTION
WHEN OTHERS THEN
NULL; — ignore errors
END;
END LOOP;

SELECT Count(*)
INTO   v_itemcount
FROM   all_objects AO
WHERE  AO.owner = USER
AND AO.object_type NOT IN ( ‘INDEX’ )
AND AO.object_name NOT LIKE ‘BIN$%’;
END LOOP;

EXECUTE IMMEDIATE ‘purge recyclebin’;
END;

[edsanimate_start entry_animation_type= “fadeIn” entry_delay= “0” entry_duration= “2” entry_timing= “linear” exit_animation_type= “” exit_delay= “” exit_duration= “” exit_timing= “” animation_repeat= “infinite” keep= “yes” animate_on= “load” scroll_offset= “” custom_css_class= “”]

NOTE: Be Careful Before Running it On Production Environment [edsanimate_end]