You are currently browsing the category archive for the ‘Oracle Database&EBS General’ category.
We have x6-2 Exadata machine. When trying to create a single-instance database on one of the database nodes on Exadata system by using DBCA it throws :
ORA-02249 – missing or invalid value for MAXLOGMEMBERS.
For testing, I can create RAC database without any issue.
My steps are:
Advertisements
We faced with that issue while we are trying to install Oracle12cR2 database on Solaris 11
While we tried to install grid software on solaris root.sh ended by below syntax:
DATE CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.
DATE CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.
DATE CLSRSC-594: Executing installation step 2 of 19: 'ValidateEnv'.
DATE CLSRSC-175: Failed to write the checkpoint 'ROOTCRS_STACK' with status 'START' (error code 1)
DATE CLSRSC-177: Failed to add (property/value):('VERSION'/'12.2.0.1.0') for checkpoint 'ROOTCRS_STACK' (error code 1)
DATE CLSRSC-363: User ignored prerequisites during installation
DATE CLSRSC-594: Executing installation step 3 of 19: 'CheckFirstNode'.
DATE CLSRSC-594: Executing installation step 4 of 19: 'GenSiteGUIDs'.
DATE CLSRSC-594: Executing installation step 5 of 19: 'SaveParamFile'.
DATE CLSRSC-175: Failed to write the checkpoint 'ROOTCRS_PARAM' with status 'START' (error code 1)
DATE CLSRSC-594: Executing installation step 6 of 19: 'SetupOSD'.
DATE CLSRSC-594: Executing installation step 7 of 19: 'CheckCRSConfig'.
DATE CLSRSC-594: Executing installation step 8 of 19: 'SetupLocalGPNP'.
DATE CLSRSC-175: Failed to write the checkpoint 'ROOTCRS_GPNPSETUP' with status 'START' (error code 1)
DATE CLSRSC-175: Failed to write the checkpoint 'ROOTCRS_GPNPSETUP' with status 'SUCCESS' (error code 1)
DATE CLSRSC-175: Failed to write the checkpoint 'ROOTCRS_GPNPSETUP' with status 'SUCCESS' (error code 1)
DATE CLSRSC-175: Failed to write the checkpoint 'ROOTCRS_STACK' with status 'FAIL' (error code 1)
Died at /u01/app/12.2.0/grid/crs/install/crsutils.pm line 4120.
The command '/u01/app/12.2.0/grid/perl/bin/perl -I/u01/app/12.2.0/grid/perl/lib -I/u01/app/12.2.0/grid/crs/install /u01/app/12.2.0/grid/crs/install/rootcrs.pl ' execution failed
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 11.2.0.4.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 »
Hot News!!!!
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 11.2.0.3 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 11.2.0.4 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 11.2.0.3.0 db on linux system.
Here is the all related error messages and solution:
I faced with that error on 11.2.0.2 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 11.2.0.1 database with ASM on AIX operating system:
Symptoms:
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
———————————— ———– ——————————
db_create_file_dest string
Solution:
SQL> alter database add standby logfile size 5G;
Database altered.
