DBACLASS https://dbaclass.com/ database administration Sun, 02 Dec 2018 12:30:54 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.5 TESTING https://dbaclass.com/testing/ https://dbaclass.com/testing/#respond Sun, 02 Dec 2018 12:30:54 +0000 http://dbaclass.com/?p=3988 [HDquiz quiz = “229”]

The post TESTING appeared first on DBACLASS.

]]>
[HDquiz quiz = “229”]

The post TESTING appeared first on DBACLASS.

]]>
https://dbaclass.com/testing/feed/ 0
ORA-01157: cannot identify ORA-01110: data file with dba_temp_file https://dbaclass.com/ora-01157-cannot-identify-ora-01110-data-file-with-dba_temp_file/ https://dbaclass.com/ora-01157-cannot-identify-ora-01110-data-file-with-dba_temp_file/#respond Sun, 30 Oct 2016 14:07:31 +0000 http://dbaclass.com/?p=1230                                  Recently one of our database was migrated. After migration DB is up and running, But we found below errors in the alert log.   Errors in file /oracle/app/oracle/admin/test/diag/rdbms/b2btrn/TEST/trace/test_ora_20464.trc: ORA-01157: cannot identify/lock data file 205 – see DBWR trace file […]

The post ORA-01157: cannot identify ORA-01110: data file with dba_temp_file appeared first on DBACLASS.

]]>
                                 Recently one of our database was migrated. After migration DB is up and running, But we found below errors in the alert log.

 

Errors in file /oracle/app/oracle/admin/test/diag/rdbms/b2btrn/TEST/trace/test_ora_20464.trc:
ORA-01157: cannot identify/lock data file 205 – see DBWR trace file
ORA-01110: data file 205: ‘/test/oradata/b2btrn/tempfile/temp1.304.921456819’

Now I queried dba_temp_files, and got the same error.

 

SQL> select file_name from dba_temp_fileS;
ERROR:
ORA-01157: cannot identify/lock data file 205 – see DBWR trace file
ORA-01110: data file 205: ‘/test/oradata/b2btrn/tempfile/temp1.304.921456819’

And the file is not present physically also:
ls -ltr /test/oradata/b2btrn/tempfile/temp1.304.921456819
/test/oradata/test/tempfile/temp1.304.921456819: No such file or directory

 



 
To fix it , I have dropped the temp file:

 

SQL>select file#,name from v$tempfile
FILE# NAME
———- ——————————————————————-
1 /test/oradata/temp03.dbf
3 /test/oradata/b2bsit1_iastemp.dbf
4 /test/oradata/sit1b2b_iastemp.dbf
2 /test/oradata/b2btrn/tempfile/temp1.304.
SQL> alter database tempfile ‘/test/oradata/b2btrn/tempfile/temp1.304.921456819’ drop;

Database altered.

SQL>select file_name from dba_temp_fileS

FILE_NAME
————————————————————–
/test/oradata/b2bsit1_iastemp.dbf
/test/oradata/sit1b2b_iastemp.dbf
/test/oradata/temp03.dbf

 

The post ORA-01157: cannot identify ORA-01110: data file with dba_temp_file appeared first on DBACLASS.

]]>
https://dbaclass.com/ora-01157-cannot-identify-ora-01110-data-file-with-dba_temp_file/feed/ 0
ORA-38301: can not perform DDL/DML over objects in Recycle Bin https://dbaclass.com/ora-38301-can-not-perform-ddldml-over-objects-in-recycle-bin/ https://dbaclass.com/ora-38301-can-not-perform-ddldml-over-objects-in-recycle-bin/#comments Sun, 30 Oct 2016 12:44:43 +0000 http://dbaclass.com/?p=1225            While dropping a tablespace, getting error ORA-38301: can not perform DDL/DML over objects in Recycle Bin . SQL> drop tablespace DATA including contents and datafiles; drop tablespace DATA including contents and datafiles * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 1 ORA-38301: can not perform DDL/DML over […]

The post ORA-38301: can not perform DDL/DML over objects in Recycle Bin appeared first on DBACLASS.

]]>
           While dropping a tablespace, getting error ORA-38301: can not perform DDL/DML over objects in Recycle Bin .

SQL> drop tablespace DATA including contents and datafiles;
drop tablespace DATA including contents and datafiles
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-38301: can not perform DDL/DML over objects in Recycle Bin

 

Solution:

Before dropping the tablespace, disable recyclbin . 

1. Disable recyclebin:

SQL> ALTER SYSTEM SET recyclebin = OFF DEFERRED;

System altered.

2. Drop tablespace:

SQL> drop tablespace DATA including contents and datafiles;
Tablespace dropped.

3.  Enable recyclebin 

SQL > ALTER SYSTEM SET recyclebin = ON DEFERRED;

System altered.

 

The post ORA-38301: can not perform DDL/DML over objects in Recycle Bin appeared first on DBACLASS.

]]>
https://dbaclass.com/ora-38301-can-not-perform-ddldml-over-objects-in-recycle-bin/feed/ 1
RMAN-20005: target database name is ambiguous https://dbaclass.com/rman-20005-target-database-name-is-ambiguous/ https://dbaclass.com/rman-20005-target-database-name-is-ambiguous/#respond Fri, 14 Oct 2016 08:00:40 +0000 http://dbaclass.com/?p=1140                           While running rman commands from the catalog database, you might get the error RMAN-20005: target database name is ambiguous. , if the database was restored from another database. ERROR: rman target sys/oracle#51234@RMANBKP catalog rman_b2ccrmpd/rman@catdb Recovery Manager: Release 12.1.0.2.0 – Production on Fri Oct […]

The post RMAN-20005: target database name is ambiguous appeared first on DBACLASS.

]]>
                          While running rman commands from the catalog database, you might get the error RMAN-20005: target database name is ambiguous. , if the database was restored from another database.

ERROR:

rman target sys/oracle#51234@RMANBKP catalog rman_b2ccrmpd/rman@catdb

Recovery Manager: Release 12.1.0.2.0 – Production on Fri Oct 14 10:34:05 2016

Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.

connected to target database: B2CCRMPD (DBID=1927730802, not open)
connected to recovery catalog database
RMAN> list backup;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 10/11/2016 06:13:34
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20005: target database name is ambiguous

SOLUTION:

1. connect to the catalog database , check the dbid.
oracle@sec86-5:~/RMAN$ sqlplus rman_b2ccrmpd/rman@catdb

SQL*Plus: Release 12.1.0.2.0 Production on Tue Oct 11 06:14:17 2016
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select db_key,dbid,name from rc_database;

DB_KEY DBID NAME
———- ———- ——–
96243 1927730802 B2CCRMPD
    1 1924697918 B2CCRMPD

 

We can see there are two dbid entries in the catalog. Now set the correct db id of the target db and run rman commands.
rman target sys/oracle#51234@RMANBKP catalog rman_b2ccrmpd/rman@catdb

Recovery Manager: Release 12.1.0.2.0 – Production on Fri Oct 14 10:34:05 2016

Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.

connected to target database: B2CCRMPD (DBID=1927730802, not open)
connected to recovery catalog database
RMAN> set DBID=1927730802;

RMAN> list backup;

it will work

The post RMAN-20005: target database name is ambiguous appeared first on DBACLASS.

]]>
https://dbaclass.com/rman-20005-target-database-name-is-ambiguous/feed/ 0