Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Monday, October 21, 2019

OMF (Oracle Manage Files)

OMF (Oracle Manage Files) is a database feature, that simplifies tablespace creation. Using OMF, Oracle will automatically assign datafile names to tablespaces and automatically create and delete the required datafiles the operating-system level. It is introduced in Oracle 9i.

These are the parameter for this feature:

db_create_file_dest and db_create_online_log_dest_n.

The db_create_file_dest specifies, where the datafiles will be placed.
The db_create_online_log_dest_n specifies, where the online logs will be placed. Use 1,2,3 instead of n, when you want to have 3 members in each group.

Example:
db_create_file_dest='/oracle/oradata'
db_create_online_log_dest_1='/oracle/oradata'
db_create_online_log_dest_2='/oracle/oradata

How to convert NON-OMF to OMF files ( Oracle Managed File conversion - NON-ASM ) (Doc ID 2182089.1)

Wednesday, October 16, 2019

demilitarized zones (DMZ)

A DMZ is simply a place that is under your control but outside of your internal network and it a place to put servers that you want outsiders to reach but you don't want them to get to your internal network. By limiting access, you can also fine tune monitoring.

However, you would want to expose a portion of these internal applications outside your enterprise for your non-employee users like customers and vendors. For example, Oracle E-Business Suite (flagship Oracle ERP application) has some of the modules like iRecruitment, iSupplier, iStore etc.


In Oracle Application how the nodes (FND_NODES) is to exposed:

>To expose to public use the profile “Node Trust Level”

>Set node to Public/Private (Normal -> private, External -> public)

>Set "Responsibility Trust Level" profile to decide whether to expose Application Responsibility to inside or outside firewall.

Internal Applications Tier
The internal applications tier is the server configured for internal users to access Oracle E-Business Suite. It runs the following major application services:

Web and Forms Services
WebLogic Administration service, Node Manager, Oracle HTTP Server, OPMN, WebLogic Managed Servers
Concurrent Manager Services
Reports and Discoverer Services
External Applications Tier
The external applications tier is the server configured for external users for accessing Oracle E-Business Suite. It runs the following application service:

Oracle HTTP Server
WebLogic components like node manager, managed servers etc.

OPMN
Oracle Process Manager and Notification Server (OPMN) is installed and configured on every tier designated to run the web application.  OPMN provides an integrated way to manage all Oracle Application Server components.  OPMN consists of two main pieces:  the Process Manager and the Notification Server. The Process manager (PM) is the centralized process management mechanism in Oracle Application Server and is used to manage the Oracle HTTP Server. The PM starts, restarts, stops, and monitors every process it manages. It also performs death-detection and automatic restart of the processes. Oracle Notification Server (ONS) is the transport mechanism for failure, recovery, startup, and other related notifications between components in Oracle Application Server.

OHS
Oracle HTTP Server (OHS) is installed and configured on every tier that is designated to run the web application . It provides the key infrastructure required for serving the static and dynamic content generated by Oracle E Business Suite products.

Webgate is an out-of-box client which enforces OAM policies on HTTP resources. Typically, it is installed on the webserver like apache and traps all incoming http traffic before it hits core apache. In this fashion, webgate can enforce OAM policies on the http resources residing on the http server.

Oracle id related reference:
Oracle E-Business Suite 11i Configuration in a DMZ (Metalink Note 287176.1)
Oracle E-Business Suite Release 12 Configuration in a DMZ (Metalink Note 380490.1)
Oracle E-Business Suite Release 12.2 Configuration in a DMZ (Doc ID 1375670.1)


Sunday, October 6, 2019

Recover a table:

In previous releases point in time recovery of a table or table partition was only possible by manually creating a point in time clone of the database.

For TSPITR, we need to specify the auxiliary destination where RMAN would create a temporary database by restoring the controlfile, SYSTEM
tablespace, UNDO tablespace, SYSAUX tablespace and finally the tablespace that needs to be recovered.

Once the temporary database is restored and recovered, RMAN automatically exports the contents of tablespace to be recovered from the
temproary tablespace to a dump file and imports this dump into the Target(Main) database where the table was dropped.


rman target /
RMAN> run
2> {
3> recover tablespace MYTS until time "to_date('2013-05-04:11:38:00','YYYY-MM:DD:HH24:MI:SS')" auxiliary destination '+FRA';
4> }


Once the import is done successfully, RMAN automatically deletes the temporary database that it had created earlier.

Now, lets connect to the main database and check if we are able to access the dropped table. But, before that, you need to bring the tablespace online.

recovering a dropped table with flashback:The recyclebin feature introduced in Oracle 10g allows you to recover dropped tables using the flashback table...to before drop command. With recyclebin, Oracle does not automatically delete dropped tables. Instead, Oracle renames dropped and their associated objects, giving them system-generated recyclebin names that begin with BIN$.

SQL> select object_name, original_name, type from recyclebin;
 OBJECT_NAME                       ORIGINAL_NAME              TYPE   
  ------------------------------    -----------------------    -------
BIN$ABCSD5   TESTING                    TABLE
select * from "BIN$ABCSD5" ;
SQL> flashback table testing to before drop;
SQL> select index_name from user_indexes where table_name = 'testing';
 alter index "recyclebin_name" rename to original_name;


New in Oracle 12c is the Multitenant Architecture, as well as the ability to restore one table from an RMAN backup.


RECOVER TABLE TEST.T1 UNTIL SCN 1853267 AUXILIARY DESTINATION '/u01/aux' REMAP TABLE 'TEST'.'T1':'T1_PREV';
recover table hari.emp until time "to_date('2018-08-14 21:53:42','yyyy-mm-dd:hh24:mi:ss')" auxiliary destination '/u01/fra';
recover table hari.emp until time "to_date('2018-08-14 21:53:42','yyyy-mm-dd:hh24:mi:ss')" auxiliary destination '/u01/fra';

run {

recover table example.test_restore of pluggable database PDB2

until time "to_date('12-01-2016 17:16:00','mm/dd/yyyy hh24:mi:ss')"

auxiliary destination '/oradata/CDB2/aux'

;

}

RMAN> run {

recover table example.test_restore of pluggable database PDB2

until time "to_date('12-01-2016 17:16:00','mm/dd/yyyy hh24:mi:ss')"

auxiliary destination '/oradata/CDB2/aux'

;

}

=================

1.Flashback features:

SHOW RECYCLEBIN;
flashback table <table> to before drop;
FLASHBACK TABLE HR.REG_HIST TO BEFORE DROP;

2.Database Point-in-Time Recovery:

3. Tablespace point-in-time recovery (TSPITR) :

4. Oracle 12c Table Point-in-time Recovery:

rman target /

RMAN> recover table emp.emp until time "to_date('2010-05-16 02:21:27','yyyy-mm-dd:hh24:mi:ss')" auxiliary destination '/u02/RC_BKP';

RMAN> recover table mm.test until time "to_date('00/17/2013 21:01:15','mm/dd/yyyy hh24:mi:ss')" auxiliary destination '/u03/app/oracle/ux' remap table mm.test:test_temp;