You are currently browsing the category archive for the ‘Oracle Database&EBS General’ category.
If you are using RMI connection than possibly this error should be familiar…
We face with that error after our 10.2.0.5 to 220.127.116.11.6 upgrade. Some of functions just stopped. Those functions are use RMI connection and return some value from one other database.
After reboot database, function started to run again. After made some research I found the root cause.
Here is the steps; Read the rest of this entry »
Finally Oracle 12cR2 version is available on the Oracle Public Cloud and free trial is available. This is a great platform to test new features by using free trail.
Here is the screen shoot
I face with that issue during 10.2.0.5 to 18.104.22.168 database upgrade. My os is : SUN-Sparc x86-64
Here is the steps:
1. Set 11R2 Oracle_home
2. Open 10.2.0.5 database
I faced with that issue on 22.214.171.124 db which is running on Exadata machine.
RMAN backup to disk failed with below error messages:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 2144337920 bytes disk space from 3221225472000 limit
RMAN-03009: failure of backup command on t4 channel at time_here
We had SMON recovery crash with ORA-00607&ORA-00600: internal error code, arguments: [kdBlkCheckError]on 126.96.36.199.0 db on linux system.
Here is the all related error messages and solution:
I faced with that error on 188.8.131.52 db on AIX 6.1 system.
During export an error message EXP-113 is raised:
EXP-00113: Feature New Composite Partitioning Method is unsupported. Table MYTABLE could not be exported
But the export would still complete and also there are some addition error messages are raised:
EXP-00006: internal inconsistency error
EXP-00000: Export terminated unsuccessfully
I face wiht this issue when try to add standby file on standalone 184.108.40.206 database with ASM on AIX operating system:
SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 size 5G;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 size 5G
ERROR at line 1:
ORA-02236: invalid file name
SQL> show parameter DB_CREATE_FILE_DEST
NAME TYPE VALUE
———————————— ———– ——————————
SQL> alter database add standby logfile size 5G;
As a DBA We always need to know backup informations for our databases.So I just prepared quick list for some important list backup commands.
– LIST ARCHIVELOG ALL;
– LIST BACKUP OF ARCHIVELOG ALL;
– LIST BACKUP;
– LIST BACKUP OF DATABASE;
– LIST BACKUP SUMMARY;
– LIST BACKUP BY FILE;
I face this issue on our R12.1.1 wiht 220.127.116.11 RAC database wiht ASM Read the rest of this entry »
I have dataguard configuration such as 2 node rac(18.104.22.168) on aix 6.1 as primary, standalone standby database.
I noticed that Primary can transport archive log to standby but standby can not apply archive log and giving errors at standby alert.log such as:
MRP0: Background Media Recovery terminated with error 1111 and MRP0: Background Media Recovery process shutdown (PROD00DG)