1752290 Members
5275 Online
108786 Solutions
New Discussion юеВ

Re: ORA-00604

 
Senthil Prabu.S_1
Trusted Contributor

Re: ORA-00604

Hello,
This should solve your problem;
http://www.cryer.co.uk/brian/oracle/ORA01555.htm


HTH,
Prabu.S
One man's "magic" is another man's engineering. "Supernatural" is a null word.
Gerardo Mora
Advisor

Re: ORA-00604

Hi Enrico,

Try to delete the tablespace with out other users in the system for ex. starting the database in restric mode or increase the roll back segments size.
share to learn
Sandman!
Honored Contributor

Re: ORA-00604

You can alter the tablespace to nologging mode but that will only affect objects created after the alter statement is run. As suggested truncate all objects in the tablespace after changing its logging mode and then simply drop it. That should do the trick for you. This way undo information won't be saved and you won't have to resize your rollback segments.

~hope it helps
Frank de Vries
Respected Contributor

Re: ORA-00604

Enrico

If you have sql*navigator or Toad it would make it easier to copy paste the output, if you just use sql*plus then you need to spool to file and run the file as a script:

Thus login into your schema as the owner

SQL>spool yourfile.sql
SQL>set pages 0
SQL>set feedback off
SQL>set echo off
SQL>select 'truncate table '||table_name||' resuse ;' from user_tables ;
SQL> spool off

You want to quickly edit yourfile.sql and
take the command that is repeated out and then save.

SQL> get yourfiles.sql
SQL> r
Look before you leap