Oracle backup and recovery FAQs

ORA-00245

Modify the location of the snapshot control file to the shared disk, execute show snapshot controlfile name; in rman to view it, and execute configure snapshot controlfile name to '+data/****'; in rman to modify it. (Note: If this error is still reported after configuration, execute The database can be solved after restarting srvctl)

ORA-00257

The archive log is about to be full and non-sys users cannot log in to rman. Use sys user login to clear the logs and execute rman.

  • delete archivelog all completed before 'SYSDATE-7';
  • crosscheck archivelog all;
  • delete expired archivelog all;

ORA-00845

Insufficient space in /dev/shm, reset the mount point space mount -o remount,size=4G /dev/shm

ORA-00600:internal error code,arguments:[krbbtgb_wait_no_buffers], [ ],[ ],[ ],[ ],[ ],[ ],[ ],[ ],[ ],[ ],[ ]

During the rac cluster database backup process, asm does not allocate cache and sqlplus executes

  • alter system set "_backup_file_bufcnt"=64 scope=both;
  • alter system set "_backup_dynamic_buffers"=false scope=both;

ORA-01654

The data file capacity has reached the upper limit (default 32G), and you need to manually add a new data file to the table space.

  • select name from v$datafile; (View the size of each data file in turn)
  • ALTER TABLESPACE "USERS" ADD DATAFILE '/data/oracle/oradata/orcl/users02.dbf' SIZE 32G AUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITED;

ORA-19571

The archive log was not cleared in time, resulting in the control file not recording the old recid.

Solution: 1. alter system set control_file_record_keep_time=15 scope=spfile;

                  2、delete archivelog all;   crosscheck archivelog all;   delete expired archivelog all;

ORA-00020:

The number of session connections exceeds the maximum.

Solution:

1. After restarting the database. Check the parameters show parameter processes; modify the parameters alter system set processes=1000 scope=spfile;

2. If the error is still reported after a period of time after the above modifications, it is most likely caused by the increasing number of OMS service connections. Check the connected process name SELECT MACHINE, PROGRAM, COUNT(*) FROM V$SESSION GROUP BY MACHINE, PROGRAM; ----OMS is Oracle web management service, it does not affect the business, just close the service

  • linux method: emctl stop dbconsole 
  • Windows method: net stop OracleDBConsoleorcl (orcl is the instance name)

Guess you like

Origin blog.csdn.net/jiujiederoushan/article/details/128129045