Karan Rajpoot Oracle DBA Blog's

                                             Oracle 12c Grid binary installation High-Level Steps for Oracle 12c grid binary installation 1) Download the below grid software linuxamd64_12102_grid_1of2 linuxamd64_12102_grid_2of2. 2) Add the necessary groups. eg) asmdba, asmadmin, asmoper. 3) Create or modify a user. eg) Grid or Oracle user. 4) Unzip the grid software from that user. eg) unzip <file name> Note:- Unzip the files in sequential way, first linuxamd64_12102_grid_1of2 then linuxamd64_12102_grid_2of2   Now let's see the above steps with the help of practical  Step 1) First thing that needs to be done after download, Copy the zip files in some other folder to change the ownership from root to respective user (Oracle/Grid). [root@dr sf_Oracle_DBA_Softwares]# cp linuxamd64_12102_grid_1of2.zip linuxamd64_12102_grid_2of2.zip /opt Step 2) Create the necessary groups and user. Group Creation [root@dr sf_Oracle_DBA_Softwares]

                                    Recovery Catalog Database Using RMAN  By default, RMAN connects to the target database in NOCATALOG mode, meaning that it uses the control files in the target database as the sole repository of RMAN metadata. Perhaps the most important decision you make when using RMAN is whether to create a recovery catalog as the RMAN repository for normal production operations. A recovery catalog is a schema created in a separate database that contains metadata obtained from the target control file. With the use of the recovery catalog database, you can put all the backup or pieces information of the multiple databases in a single location. ==> Benefits of Using the Recovery Catalog as the RMAN Repository When you use a recovery catalog, RMAN can perform a wider variety of automated backup and recovery functions than when you use the control file in the target database as the sole repository of metadata. ==>The following features are av

                                               Configure Flash Recovery Area To Configure Flash Recovery Area first there is a need to set below parameters. Parameter 1) db_recovery_file_dest_size Parameter 2) db_recovery_file_dest Now let's start  We can check the current location of Flash Recovery Area through the below query. Query: - select NAME,SPACE_LIMIT,SPACE_USED,NUMBER_OF_FILES from V$RECOVERY_FILE_DEST; Step 1) Now set the db_recovery_file_dest_size parameter  Step 2) Now set the db_recovery_file_dest parameter Step 3) Now we will bounce the database to reflect the changes in the spfile and then will check the status of the parameters through below command Command: - show parameter recover; We can see from the above output both the parameter's has been set as per the requirement. Step 4) Check the database mode, it should be in archive log mode. If it is not set to archive log then need to change t

                                              ORA-12899: value too large for column Error: -  ORA-12899: value too large for column. Cause: - This error occurs when you have given the data type value which is greater than its maximum value. Solution: - Try to give the data type value under its maximum assign value or try to increase the size of the maximum value. let's understand the things with the help of the below example: - Example: - Step 1) SQL> create table employee (emp_id number, emp_name varchar(10), emp_desig varchar(10)); Table created. Step 2) SQL> insert into employee values (1001, 'Paul', 'Project_Engineer'); insert into employee values (1001, 'Paul', 'Project_Engineer')                                            * ERROR at line 1: ORA-12899: value too large for column "SYS"."EMPLOYEE"."EMP_DESIG" (actual: 16, maximum: 10) Note: - At the time of tabl

                                                  ORA-00984: column not allowed here Error: -  ORA-00984: column not allowed here. Cause: - When you try to insert the value in a table and forget to enclose the string value in a single quote, then you will get this error. Solution: - Put the string value under single quotes and re-execute the command again. Example: -  SQL> insert into employee values (1001, Paul, Engineer); insert into employee values (1001, Paul, Engineer)                                          * ERROR at line 1: ORA-00984: column not allowed here Note: - In the above output string value has not enclosed with single quotes, To resolve this, Put the string value under single quotes and re-run the command again like below. SQL> insert into employee values (1001, 'Paul', 'Engineer'); 1 row created. Hope that will resolve your issue.

                                                          Types of SQL Statements The SQL statement can be categorized into the following four ways: - 1)  DDL ( Data Definition Language) 2) DML ( Data Manipulation language) 3) DCL ( Data Control Language) 4) TCL ( Transaction Control Language)  Now we will understand each of the above statements with examples: - 1) DDL ( Data Definition Language): -  The DDL statement provides commands for defining relation schemas, that is for creating tables, indexes, sequences and so on and also commands for dropping, altering renaming objects. a) CREATE: - It is used to create objects in the database. Example: - Object Creation b) ALTER: - It is used to alter the structure of the database. Example: - Alter the structure of the database c) RENAME: - To rename an object. Example: - Rename of a tablespace d) DROP: - This command is used to delete the objects from the database. Example: - Drop ob

                                      ORA-01119: error in creating database file Error: -  ORA-01119: error in creating a database file Cause: - Datafile size has not mentioned in the datafile creation command. Solution: - Mention the datafile size at the end of the command and re-execute it.  Example: - SQL> alter tablespace users add datafile '/u01/app/oracle/oradata/prod/users02.dbf'; alter tablespace users add datafile '/u01/app/oracle/oradata/prod/users02.dbf' * ERROR at line 1: ORA-01119: error in creating database file '/u01/app/oracle/oradata/prod/users02.dbf' ORA-17610: file '/u01/app/oracle/oradata/prod/users02.dbf' does not exist and no size specified ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Note: - In the above command datafile size has not mentioned at the end of the command, Put the datafile size and re-execute co