You may hit performance issue on your dataguard setup. You may not hit the transfer gap but You may have an apply gap on your standby site. It can because some critical issue if your primary side goes down.

There are some trick which You can increase your performance on the Standby database on your dataguard setup

I assume that your standby has apply gap more than 2 hours.

Read the rest of this entry »


I faced with that issue on version on Linux 6. There were no messages or warnings in the alert log file.

Export status showed as executing and there weren’t any errors.

I used below sql to identify wait:

select v.status, v.sid,v.serial#,io.block_changes,event
from v$sess_io io, v$session v
where io.sid = v.sid
and v.saddr in (
    select saddr
    from dba_datapump_sessions
) order by sid;

Read the rest of this entry »

I faced with that error message on EE version on RHEL6

Here are the error messages

SQL> startup nomount;
ORA-27126: unable to lock shared memory segment in core
Linux-x86_64 Error: 12: Cannot allocate memory
Additional information: 3894
Additional information: 2129923
Additional information: 6090752

Read the rest of this entry »

If your export size volume is huge than you may need to split export files instead of single FS. In this case, We need to use the multiple directories feature of EXPDP utility.

By using this feature, We can create multiple dump files in multiple directories and distribute our logical export to different directories on the operating system.

In my case my db version in and my os is linux 6

Read the rest of this entry »

You may with that error message during the export-import process.


Import to a database using IMPDP is erroring out

Db Versions:

Source DB 12.1.x
Target DB 11.2.x


ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-39142: incompatible version number 4.1 in dump file “DUMP_PATH/xxx.dmp”

Read the rest of this entry »

I faced with that issue trying to install Oracle 11g database on Linux 6.  Here is the screenshot:


Read the rest of this entry »

I face with that error message while I was making 12c installation on Solaris machine. The Screen shoot is:


Read the rest of this entry »

The X$ tables are owned by the SYS database user and are read-only, which is why they are referred to as fixed tables and the V$ views are referred to as fixed views. This statement might be a juicy invitation for you to try to verify this read-only property. Any attempt to alter these tables with a DDL or DML statement is met with an ORA-02030 error.

Only SYS can query the X$ tables, they cannot be granted.  However, you can create view on them and grant the view.
Read the rest of this entry »

One of our Prod database backup ended by  below errors:

RMAN-06207: WARNING: 1 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Datafile Copy +DATA/DB_NAME/DATAFILE/XXX_TS.319.962390011

Read the rest of this entry »

Merhaba Arkadaşlar,

Bildiğiniz gibi blog’um içerisinde türkçe paylaşım yok denecek kadar az. Bugün sizlerle Yusuf Şimşek’in geliştirdiği  Ön Muhasebe Programı hakkında paylaşım yapmak istiyorum.

Yusuf Bey, Şirketiniz için rahatlıkla kullanabileceğiniz kolay,  kullanıcı dostu arayüze sahip,  güzel hazırlanmış ve tasarlanmış program raporları vasıtasıyla, Şirketinizi ön muhasebenizi kolaylıkla tutmanızı sağlayan güzel bir ürün geliştirmiş. Kendisini tebrik ediyorum.

Programın demosunu indirebilir, gerekli desteği ve demo ayrıtınlarına  bu linke  tıklayarak erişebilirsiniz.

Programın işlevselliğinden ve Yusuf Bey’in yaklaşımından son derece memnun kaldığım için bu postu sizlere paylaşmak istedim.