Tag: Osama

Stage Oracle EBS R12

Posted on by Osama Mustafa in Application
in this article i will clarfiy how to download Oracle EBS R12 and learn how to stage this product.

Let’s start with how to download Oracle EBS R12 :

Step 1 : Go to https://edelivery.oracle.com
Step 2 : Enter Your UserName and Password to get acces to this site, and you also register for free.
Step 3 : in this step you have to select which product you need in our case “E-Business Suite” and platform compatiable with EBS , Windows, Linux , AiX and Solaris.
Step 4 : we need to download all the zip files belonging to the following parts:

  1. Rapid Install Start Here
  2. Rapid Install RDBMS
  3. Rapid Install Databases
  4. Rapid Install Tools
  5. Rapid Install APPL_TOP

Staging Oracle EBS is Easy & Simple

  1. By Creating Stage Directory , and make sure you have enough space on that direcoty , copy download file to stage folder, and exetation for downloadable files “zip”.
  2. Unzip the files and in this case you will have Stage area for EBS.

Documet Dowload Here.
Thank you
Osama mustafa
 
 

ORA-01151: use media recovery to recover block, restore backup if needed

Posted on by Osama Mustafa in Database

SQL> startup
ORACLE instance started.

Total System Global Area 599785472 bytes
Fixed Size 1288820 bytes
Variable Size 192939404 bytes
Database Buffers 402653184 bytes
Redo Buffers 2904064 bytes
Database mounted.
ORA-01172: recovery of thread 1 stuck at block 4545 of file 1
ORA-01151: use media recovery to recover block, restore backup if needed
SQL>

Cause :
  There is block corruption in tablespace.

Solution :

 SQL> shutdown immediate;
 SQL> startup mount;
 SQL> recover database;
 SQL> alter database open;

 

Find Resote Point Rman

Posted on by Osama Mustafa in Database
Some Times you need to Restore your Database To Earlier time , and before doing that you have to check weather database have valid to do that or not

Simple Query :

SQL>  select resetlogs_change#,to_char(resetlogs_time,
 'DD-MON-YYYY HH24:MI:SS') Last_resetlog_time from v$database_incarnation;
 
RESETLOGS_CHANGE# LAST_RESETLOG_TIME
----------------- --------------------
                1 11-SEP-2008 22:57:51
           88033 23-MAY-2011 10:12:42
 
Or Sometimes you could Use v$restore_point , Such as
 
SELECT scn, time, database_incarnation#, guarantee_flashback_database from
v$restore_point; 
 
 
Thank you 
Osama Mustafa

ORA-20222: Workload was not captured in the current database

Posted on by Osama Mustafa in Database


Happy New Year For All , And Wish you All Best 

ORA-20222 “Given capture_id \”%s\” is invalid or the corresponding capture failed”

ORA-20222: Workload was not captured in the current database. Cannot export!
ORA-06512: at “SYS.DBMS_WORKLOAD_CAPTURE”, line 1588
ORA-06512: at line 2

 Regarding to Https://support.oracle.com Note :

DATABASE CAPTURE AND REPLAY COMMON ERRORS AND REASONS [ID 463263.1]
This Error 

is a generic error message that can occur due other underlying error during Capture.
Check the error accompanying with ORA-20222.

Ensure correct directory name is used including check the case-sensitivity of the directory name.
The directory name is case sensitive. Ensure READ and WRITE privilege on the DIRECTORY object to the which is the capture is written.

Thank you 
Osama mustafa

Happy New Year Again . 

ORA-01210: data file header is media corrupt

Posted on by Osama Mustafa in Database

ORA-00283: recovery session canceled due to errors
ORA-01110: data file 24: ‘/ora/data/gamesds/system02.DBF’
ORA-01122: database file 24 failed verification check
ORA-01110: data file 24: ‘/ora/data/gamesds/system02.DBF’
ORA-01210: data file header is media corrupt

Error Cause:
The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistancy of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database. 
 
 
Solution :
Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery.

 Or The Below Solution , You Must Be Sure that you have Valid Backup to restore it .

SQL> shutdown immediate
SQL > Startup mount 
SQL> ALTER DATABASE DATAFILE '/ora/data/gamesds/system02.DBF' OFFLINE ;
SQL > ALTER database Open ;

Thank you
Osama Mustafa

DBMS_METADATA Is Missing During expdp

Posted on by Osama Mustafa in Database
The Error Appear During The expdp Database , And Looks

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD []
ORA-04067: not executed, package body “SYS.DBMS_METADATA” does not exist
ORA-06508: PL/SQL: could not find program unit being called: “SYS.DBMS_METADATA”
ORA-06512: at “SYS.DBMS_SYS_ERROR”, line 62
ORA-06512: at “SYS.KUPW$WORKER”, line 6226

Cause:

 SYS.DBMS_METADATA Is Missing .

Solution :

Check if the above object exists

SELECT owner, object_name, object_type, status FROM dba_objects WHERE  object_name=’DBMS_METADATA’;

Not Found :

$ORACLE_HOME/rdbms/admin/prvtmeta.plb
$ORACLE_HOME/rdbms/admin/utlrp.sql

Startup/Shutdown Logical Standby Database

Posted on by Osama Mustafa in Database
Simple Steps to do that


Shutdown Steps :

On Primary do the following :

SQL > alter system switch logfile ;
SQL > alter system archive log current ; 

Go to Standby :

SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
SQL> shutdown immediate;

Primary Database :

SQL> shutdown immediate;

Startup Steps :

Primary Database

SQL>startup;

 Standby Database:

SQL > startup
SQL > alter database start logical standby apply immediate ;

Thank you
Osama Mustafa

Bulid Logical Database

Posted on by Osama Mustafa in Database
I Post Earlier What is the Different Between Logical Database and Standby Database , Both Are Type For Data Guard .

Today i will take about how to configure Logical Database , to do this you must first create Physical Standby Which i mention it before , And you can Follow the link .

These steps for 10g,  Now After create physical Standby Database , And Make sure its working Without any problem , You Have to follow the below steps to Create Oracle Logical Standby.


Steps to convert Standby Database to Logical Standby Database :

Step #1 : 

in this step logminer Dictionary Must be Built into redo data. ( Build LogMiner Tables for Dictionary)

On Primary

SQL> begin
  2  dbms_logstdby.build;
  3  end ;
  4  /

OR

 SQL> execute dbms_logstdby.build;

Step #2:

Now we have stop Managed recovery between primary and standby :

On Standby :

SQL> alter database recover managed standby database cancel ;

Database altered.

Step #3 :

Convert Physical Standby to Logical Standby .

On Standby :

SQL> alter database recover to logical standby stdby ;

Database altered.

Notices : If this command hang and take to much Time then Back to step #1 and did it again .

Step #4:

On Standby ( New Logical)  we open it in Resetlog mode .

On New Logical ( Standby) :

SQL> shutdown immediate ;
ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup mount ;
ORACLE instance started.

Total System Global Area  839282688 bytes
Fixed Size                  2217992 bytes
Variable Size             532678648 bytes
Database Buffers          301989888 bytes
Redo Buffers                2396160 bytes
Database mounted.

SQL>
SQL>
SQL> alter database open resetlogs ;

Database altered.

Step #5:

Start Apply Service On logical

SQL> alter database start logical standby apply ;

Database altered.

OR

SQL> alter database start logical standby apply immediate ;
Database altered.

Just As Check if everything Goes Fine :

SQL> select database_role , Name from v$database ;

DATABASE_ROLE    NAME
—————- ———
LOGICAL STANDBY  STDBY

Thank you
Osama Mustafa

ora-00845 memory_target not supported on this system

Posted on by Osama Mustafa in Database
The Error Will be Appear like the following : 

SQL> startup nomount;
ORA-00845: MEMORY_TARGET not supported on this system

 Cause :

This error comes up because you tried to use the Automatic Memory Management (AMM) feature of Oracle 11g R2. Well done, but it seems that your shared memory filesystem (shmfs) is not big enough. So let’s look at the steps necessary to enlarge your shared memory filesystem to avoid the error above.

Solution 

mount -t tmpfs shmfs -o size= /dev/shm

Thank you
Osama Mustafa

Logical Standby Vs Physical Standby

Posted on by Osama Mustafa in Database
What is the difference between these two Data Guard configuration , When To Use them :

Physical Standby:

1- Physical Standby Database Its exactly same As Primary Database.
2-  In Physical Data Guard The archivelog Applied directly after transfer from primary database (FTP)

Properties of Physical Standby

1- Maintain Is Easy.
2- Creation is Easy .
3- Copy Of your Primary Database ( Disaster Recovery Solution ).

Usage :

High availability solutions Or disaster recovery Solution.

Logical Standby

1 – Opposite Of standby Database , Which is not Match primary Database .
2 – This Kind Of Configuration can be Opened in Read Only Mode .
3 – can have additional materialized views and indexes added for faster performance
4 – LogMiner Techniques to transfer Archivelog.

Properties Of Logical Database :

1 – Open In Read only Mode .
2 – Sometimes its used as RollBack Solution In Upgrade ,

Usage:

1 – reporting Database to avoid overhead in primary database.
2 – Query Database .

How they Works :

Regarding to Oracle documentation  :

LNS (log-write network-server) and ARCH (archiver) processes running on the primary database select archived redo logs and send them to the standby database, where the RFS (remote file server) background process within the Oracle instance performs the task of receiving archived redo-logs originating from the primary database.

Alternatively, a supplementary mechanism may transfer the archived redo logs. On the standby database a Fetch Archive Log (FAL) client monitors for gaps in the sequence of received logs. If it finds a gap, it may invoke one or more Fetch Archive Log (FAL) servers to run on the primary database to forward the missing item(s).

Once the archived redo logs have arrived, other processes (such as an ARCH (Archiver process), an MRP (Managed Recovery Process), and/or an LSP (Logical Standby Process)) may set about applying the log contents to the standby database.

 Conclusion :

The difference between physical and logical standby is in the way the changes from the primary are applied. Both created as an exact image of the primary database. Both receive redo logs from the primary database.

 Refernce :
 Oracle DataGuard architecture 

Thank you
Osama mustafa