You are currently browsing the category archive for the ‘Oracle Database&EBS General’ category.

While I was trying to make rpm installation by yum, it gave below error

[root@veridata ~]# yum install pdksh*
Loaded plugins: langpacks, ulninfo
Existing lock /var/run/yum.pid: another copy is running as pid 8432.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 85 M RSS (513 MB VSZ)
Started: Thu Mar 14 21:19:39 2019 - 01:41 ago
State : Sleeping, pid: 8432
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 85 M RSS (513 MB VSZ)
Started: Thu Mar 14 21:19:39 2019 - 01:43 ago
State : Sleeping, pid: 8432
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 85 M RSS (513 MB VSZ)
Started: Thu Mar 14 21:19:39 2019 - 01:45 ago
State : Sleeping, pid: 8432

So how We can handle this error? Here is the step:

Read the rest of this entry »

Advertisements

I face with that issue while I was making Oracle 11.2.0.1 version on OEL 7.6. At prerequest check screen

Here is the screen shot:

Screenshot_1.jpg

Read the rest of this entry »

While I am installing Oracle 11.2.0.4 on RHEL 7.6 I hit this message on prereq screen.

After I made some search I found a solution as below.

Login as installation user. In my case my user is oracle

Read the rest of this entry »

After Installing OEL7.6 boot loader comes with 3 options.  You need to choose the options to can login your system every boot.

linux.jpg

If you want to fix default boot you need to follow below steps:

Read the rest of this entry »

You may hit with that error code during the export process. I faced with those error on Oracle 12c database.

Complete error messages are:

ORA-31693: Table data object "SCHEMA"."TABLE_NAME_HERE" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 21 with name "_SYSSMU21_2773200038$" too small

Read the rest of this entry »

You may need to try to clean Alerts in your OEM. This method can be helpful when there are alerts that the agent won’t clear clearstate or reset dynamic properties won’t work

Here are the steps

First, log in as SYSMAN or your repository owner.

Read the rest of this entry »

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 11.2.0.4 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 12.1.0.2.0 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 11.2.0.4 and my os is linux 6

Read the rest of this entry »

Advertisements
Advertisements