Experience: is what you get soon after you need it.
GIAC Cloud Penetration Tester (GCPN)
GIAC Cloud Security Automation (GCSA)
GIAC Security Essentials (GSEC)
Certified Kubernetes Administrator (CKA)
Cloud Certified Security Professional (ISC2)
CyberSecurity Certified Professional (ISC2)
AWS Certified Solutions Architect Associate
Azure Certified Architect Expert
Azure Certified Architect
Azure Certified Administrator
Oracle Cloud Infrastructure 2018 Certified Architect Associate.
Oracle Cloud Infrastructure Classic 2018 Certified Architect Associate.
Oracle Database Cloud Administrator Certified Professional.
Oracle Database Cloud Service Operations Certified Associate.
Search This Blog
Wednesday, October 5, 2011
ORA-00959: tablespace '_$deleted$$0' does not exist
Issues was; These objects were taking 0 blocks and hence were not picked up my re-org script from the dba_segments for re-org
so these were just sitting there without occupying any blocks but still pointing to the old tablespace which we deleted after the
re-org
select table_name,blocks from dba_tables where tablespace_name='DATA_001' and blocks='0'
this will give us the list of the objects that has 0 blocks but indeed belong to the above tablespace which we dropped.
select * from USER.USER_EMPLOYEE_ERROR move
*
ERROR at line 1:
ORA-00959: tablespace '_$deleted$25$0' does not exist
so tried move this table to new tablespace
SQL> alter table USER.USER_EMPLOYEE_ERROR move tablespace DATA_001;
alter table USER.USER_EMPLOYEE_ERROR move tablespace DATA_001
*
ERROR at line 1:
ORA-00959: tablespace '_$deleted$25$0' does not exist
how about atleast move..
SQL> alter table USER.USER_EMPLOYEE_ERROR move;
alter table USER.USER_EMPLOYEE_ERROR move
*
ERROR at line 1:
ORA-00959: tablespace '_$deleted$25$0' does not exist
SQL> select tablespace_name from dba_tablespaces where tablespace_name like '%deleted%';
no rows selected
where as I can still see the objects in the database. So decided to create the ddl scripts via TOAD
and then dropped these objects and recreated them.
drop table USER.USER_EMPLOYEE_ERROR purge; <-- without purge we cannot drop the table
create table USER.USER_EMPLOYEE_ERROR (col a,b,c..);
1 comment:
Great tip! Solved my problem!
Tommy Yuen
Post a Comment