Oracle ORA Errors
Download as TXT, PDF1 like569 views
The document provides a comprehensive list of Oracle (ORA) errors and their solutions as experienced by the author, Manish. Key errors include permission issues, database recovery commands, and account lock status, with detailed troubleshooting steps for each case. It also covers configurations and best practices for managing Oracle databases, including RMAN commands and performance tuning tips.
Oracle ORA Errors
- 1.  Greetings to Everyone !! I Myself Manish, have decided to share some foremost Oracle(ORA)Errors which i faced recently. So i listed it down the ORA Errors with proper Solutions to it. I hope it Might help You. 1) ORA-01139: Reset logs option valid after incomplete database recovery. 0RA-00264 :recovery session cancelled due to errors 0RA-00283 : no recovery needed. Above solution: recover database until cancel; alter database open resetlogs; ------------------------------------------------------------------------------- 2) ORA-12546: TNS:permission denied TNS -12537: TNS connection closed TNS -12560: TNS Adapter Error TNS-00507: connection closed Linux Error :29(Illegal Seek) 0RA- 27369 - Operation not Permitted Solution: Assumptions: 1) It might happen the permission is not sufficient enough for the listener to listen from the port. Most Common Solutions Tried : 1) I checked my Host Entry which i made was correct enough to make a connection to the database. 2) I checked the port that is by default Oracle XE runs on 1521, in my case it was not listening up. So i kept this point apart. 3) I checked my Listener.ora and tnsnames.ora files, from where the database listens the port and manages the connection, it was well and good. 4) I have tried my changing the Parameter HOST = LOCALHOST to HOST =127.0.0.1 OR HOST= LOCALHOST.LOCALDOMAIN. 5) I tried once to stop and start my listener in LSNRCTL. 6) I have restarted my Database by firing the command shutdown immediate/abort ,Startup in SQLPLUS/ as sysdba; 7) I tried to see whether ulimit was properly set or not that is you can find over in the ./bash profile, or you can look over /etc/security/limits.conf file 8) I tried to set the group-name as chown -R oracle:dba /u01 9) I tried to put the group-name as chown -R root:root /SExtProc 10) I tried to install(ORACLE-XE) with root permission. Solution: 1) Host- Entry: I added a new line in the host entry as 127.0.0.1 localhost.localdomain localhost 2) I changed the sql.net configuration file(/u01/app/oracle/product/11.2.0/xe/network/admin/samples) from tcp.validnode_checking=no to tcp.validnode_checking=yes. 3) i changed the permission root:root to /u01( This is the directory where my oracle xe gets installed ,but it varies if you change accordingly) and given the
- 2. permission 777 . 4) I changed the permission of /var/tmp/oracle to 777 and assigned as root:root and moved to the directory /home/oracle ( oracle is the user which created) .Make sure the oracle which you are giving permission as 777 is actually a binary file so don t try to open it as it occupies a large amount of data. 5) I changed the HOST= localhost to HOST = 127.0.0.1. 6) Service network restart 7) Restarted the database and listener . If Suppose the above solution doesnt work, Just make these 2 changes. It might Happen it may work though. 1) listener .ora file : localhost.localdomain 2) Service Network Restart. --------------------------------------------------------------------- 3)ORA-01012: not logged on Solution : sql>shutdown abort sql>startup --------------------------------------------------------------------- 4) ORA-01031: insufficient privileges - Solution: 1) Move to $ORACLE_HOME /bin, and Assign the below Priveleges. chmown oracle:oinstall oracle chmod 6571 oracle 2) After that move to /home/oracle chmod 700 oracle chown -R oracle:dba oracle 3) Lastly if the Oracle 11G xe gets installed on /u01 Partition, so move to /u01 and grant the below Priviliges. chown -R oracle:dba oracle ------------------------------------------------------------------------- 5) RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/30/2016 00:20:47 ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
- 3. solution: just change the no archive log to archive log mode. ( alter database archivelog ;) rman target system/manager nocatalog; backup full database tag 'mybackup'; alter database open; -------------------------------------------------------------------------- 6) ORA-01126: database must be mounted in this instance and not open in any instance solution: SQL> shutdown immediate SQL> startup mount) -------------------------------------------------------------------- 7) ORA-00265: instance recovery required, cannot set ARCHIVELOG mode solution: SQL>shutdown immediate SQL>startup mount SQL>alter database archivelog; SQL>archive log list; (Shows the mode whether it is archive or no archive) ) -------------------------------------------------------------------------------- ------------- 8) RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/30/2016 01:56:16 ORA-19502: write error on file "/u01/app/oracle/flash_recovery_area/MANISH/backupset/2016_09_30/o1_mf_nnndf_FUL LBACKUP_cyty6jkg_.bkp", block number 73728 (block size=8192) ORA-27072: File I/O error Additional information: 4 Additional information: 73728 Additional information: 729088 Solution: File permission ie check the recovery_file_Dest permission ..it should be
- 4. oracle:dba. if dba group is not found then add the group dba using the root permission. if you do with oracle user again the permission error will come. so login with the root make the group dba by typing groupadd -f dba. Then move to flash recovery_Dest_size and change the permission as oracle:dba It might happen the disk is full so that it doesnt able to write the necessary files on the disk. so make sure the size is enough to store the backup. If the db_Recovery_file_dest is not configured then try to configure so that you can look in the respective path. alter system db_recovery_File_dest size = 1g scope=both sid='*'; alter system db_Recovery_File_Dest ='/u01/app/oracle/flash_Recovery_Area' scope=both sid='*'; after firing these 2 commands try to see in the show parameter db_RECOVERY now try to run the RMAN commands..To check the details : select * from v$recovery_File_Dest or select * from v$flash_recovery_area_usage; -------------------------------------------------------------------------------- ------------------------ Special Notes : Backup control files: RMAN : show all you will find the device type over there or show device type Auto backup control files: RMAN: configure control file autobackup on ; manually : RMAN : backup device type spfile; backup tablespace users; Backup archive logs: RMAN: backup archivelogs all;
- 5. Listener : - Listener and database run differently. - Separate process runs on DS - “PMON” is the background process that is handed by Listener - single listener can be for multiple DB - LSNRCTL( listener control utility) Ps -ef | grep tns Oracle Instance Recovery : ROLL FORWARD : it rolls those transaction which are committed and not present in the data file will return to the disk ROLL BACKWARD : it roll backs from backward those transaction which are not committed and present in the disk, should be removed from the disk Database open. ( first up all roll forward will happen where all the committed data are made permanent to the database. Again a stage where a database with committed and uncommitted data( a data which was made permanent but not committed) will be present.. So what it does is that it takes older values of uncommitted data from undo segment and update the values in the database.) This is how the Oracle Instance recovery happens. TYPES OF RMAN BACKUPS & COMPONENTS : full backup : taking enitre db backup incremental backup: level 0 + level 1 level 0 = db backup level 1 = incremental ( it takes the difference between any level( l0/l1) to respective level)..just takes the changes that were found on the last level. its doesnt matter whether it is l0 /l1. Again there are two types : Differential( Default) : L0 +L1 ( As explained above, just the changes between the levels it takes) Cummulative ( In cummulative, it takes the backup from the last L0). For example , if you have taken l0 at sunday , and on tuesday it takes the backup from sunday to tuesday( ie it includes L0 of sunday + l1 of monday) same for wed ( lo( sun)+ l1(mon) +l2(tues)).. Recovery section:
- 6. - shutdown the database - sqlplus / as sysdba; - startup mount - set autorecovery on; - alter database recover; - alter database open; oracle: oak ridge automatic computer and logical engine Performance Tuning : 1) use count(1) instead of count(*) select count(1) from emp where id =1; 2) Never compare null with null. select statement where null = null 3) compare number with number and string with string select statement where id = '567' ======= wrong instead select statement where id = 767 4) if you use more than one table use aliases name. select statement where m.id = d.id; ( where tablename master m, distance d) (2 tables :master , distance) (2 aliases respectively (m,d)). 5) try to use union all instead of union. table_1 select statement union all table_2 select statement 6) use IN instead of OR Select statement where id = 10 or id =11 or id =12; instead select statement where id IN( 10,11,12);
- 7. -------------------------------------------------------------------------------- ----- 9) ORA -28000: Account locked solution : logon sqlplus / as sysdba; select username, account_Status from dba_users; you will find the list of username with the account status. if locked then try to unlock by firing below command : alter user username identified by password account unlock; -------------------------------------------------------------------------------- 10) ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated ORA-01262: Stat failed on a file destination directory Linux-x86_64 Error: 2: No such file or directory solution : Under this ORA , its seen that not a single command works. that is alter,startup, shutdown abort. so what you can do is that you can try by using paramterfile. search for the parameter file location on which instance you wanna run. once you find the location of pfile , fire the below command on sqlplus / as sysdba; startup pfile='location' mount; From this you can start over this instance.. But the actual Startup doesnt work, if you shutdown the instance for a moment ,and again if you try to start the oracle instance , it doesnt work.it again shows the same error. so the solution what i found is backup the files(tablespaces, full backup) so for a moment startup with the pfile ,now switch to the rman command for backup. rman target system/manager nocatalog; backup full database tag 'mybackup' backup tablespace users; make sure the controlfile configure is turned off in RMAN. Again you have to take care that error what it says..It says the
- 8. db_Reocvery_file_Dest is not translated.. might be chnages that it doesnt exist in the location.. so once you make a backup ,you would be getting the new init.ora file modified at backup date(today date) in the backup dest try to open it.. In that find the db_Recovery_dest.. Now try to corelate the path with that location. if not found then try to make and give the permission 777 and oracle:dba now try to shutdown the instance. and fire any command ie startup, you will see that its working. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ------- END -Manish Mudhliyar.