Suresh Patnaik
Monday, June 13, 2016
Monday, March 31, 2014
ORA-01552: cant use system rollback segment for non-system tablespace "Users" in Oracle 10g
ORA-01552: cant use system rollback segment for non-system tablespace "Users"
sys@oradb> select name,status from v$datafile;
NAME STATUS
-------------------------------------------------------------------------------- -------
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\SYSTEM01.DBF SYSTEM
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\UNDOTBS01.DBF OFFLINE
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\SYSAUX01.DBF ONLINE
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\USERS01.DBF ONLINE
sys@oradb> select segment_name, status from dba_rollback_segs;
SEGMENT_NAME STATUS
------------------------------ ----------------
SYSTEM ONLINE
_SYSSMU1$ NEEDS RECOVERY
_SYSSMU2$ NEEDS RECOVERY
_SYSSMU3$ NEEDS RECOVERY
_SYSSMU4$ NEEDS RECOVERY
_SYSSMU5$ NEEDS RECOVERY
_SYSSMU6$ NEEDS RECOVERY
_SYSSMU7$ NEEDS RECOVERY
_SYSSMU8$ NEEDS RECOVERY
_SYSSMU9$ NEEDS RECOVERY
_SYSSMU10$ NEEDS RECOVERY
11 rows selected.
sys@oradb> select file#,name from v$datafile;
FILE# NAME
---------- --------------------------------------------------------------------------------
1 C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\SYSTEM01.DBF
2 C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\UNDOTBS01.DBF
3 C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\SYSAUX01.DBF
4 C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\USERS01.DBF
sys@oradb> select tablespace_name from dba_tablespaces;
TABLESPACE_NAME
------------------------------
SYSTEM
UNDOTBS1
SYSAUX
TEMP
USERS
sys@oradb> alter tablespace UNDOTBS1 online;
Tablespace altered.
sys@oradb> select name,status from v$datafile;
NAME STATUS
-------------------------------------------------------------------------------- ------
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\SYSTEM01.DBF SYSTEM
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\UNDOTBS01.DBF ONLINE
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\SYSAUX01.DBF ONLINE
C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORADB\USERS01.DBF ONLINE
sys@oradb> show parameter undo_management
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_management string MANUAL
sys@oradb> alter system set undo_management=auto scope=spfile;
sys@oradb> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
sys@oradb> startup;
ORACLE instance started.
Total System Global Area 603979776 bytes
Fixed Size 1250380 bytes
Variable Size 230689716 bytes
Database Buffers 364904448 bytes
Redo Buffers 7135232 bytes
Database mounted.
Database opened.
sys@oradb> show parameter undo_management
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_management string AUTO
Thursday, November 8, 2012
How to Clean Up After a Failed CRS Install
10g RAC: How to Clean Up After a Failed CRS Install
Doc ID: Note:239998.1 Type: BULLETIN
Last Revision Date: 25-OCT-2005 Status: PUBLISHED
PURPOSE
-------
The purpose of this document is to help DBA's and support analysts understand how
to clean up a failed CRS (Cluster Ready Services) install for 10g RAC.
SCOPE & APPLICATION
-------------------
DBA's and Support Analysts
10g RAC: How to Clean Up After a Failed CRS Install
---------------------------------------------------
Not cleaning up a failed CRS install can cause problems like node reboots.
Follow these steps to clean up a failed CRS install:
1. Run the rootdelete.sh script then the rootdeinstall.sh script from the
$ORA_CRS_HOME/install directory. Running these scripts should be sufficent
to clean up your CRS install. If you have any problems with these scripts
please open a service request.
If for some reason you have to manually remove the install due to problems
with the scripts, continue to step 2:
2. Stop the Nodeapps on all nodes:
srvctl stop nodeapps -n
3. Prevent CRS from starting when the node boots. To do this issue the following
as root:
Sun:
rm /etc/init.d/init.cssd
rm /etc/init.d/init.crs
rm /etc/init.d/init.crsd
rm /etc/init.d/init.evmd
rm /etc/rc3.d/K96init.crs
rm /etc/rc3.d/S96init.crs
rm -Rf /var/opt/oracle/scls_scr
rm -Rf /var/opt/oracle/oprocd
rm /etc/inittab.crs
cp /etc/inittab.orig /etc/inittab
Linux:
rm -f /etc/init.d/init.cssd
rm -f /etc/init.d/init.crs
rm -f /etc/init.d/init.crsd
rm -f /etc/init.d/init.evmd
rm -f /etc/rc2.d/K96init.crs
rm -f /etc/rc2.d/S96init.crs
rm -f /etc/rc3.d/K96init.crs
rm -f /etc/rc3.d/S96init.crs
rm -f /etc/rc5.d/K96init.crs
rm -f /etc/rc5.d/S96init.crs
rm -Rf /etc/oracle/scls_scr
rm -f /etc/inittab.crs
cp /etc/inittab.orig /etc/inittab
HP-UX:
rm /sbin/init.d/init.cssd
rm /sbin/init.d/init.crs
rm /sbin/init.d/init.crsd
rm /sbin/init.d/init.evmd
rm /sbin/rc3.d/K960init.crs
rm /sbin/rc3.d/S960init.crs
rm -Rf /var/opt/oracle/scls_scr
rm -Rf /var/opt/oracle/oprocd
rm /etc/inittab.crs
cp /etc/inittab.orig /etc/inittab
HP Tru64:
rm /sbin/init.d/init.cssd
rm /sbin/init.d/init.crs
rm /sbin/init.d/init.crsd
rm /sbin/init.d/init.evmd
rm /sbin/rc3.d/K96init.crs
rm /sbin/rc3.d/S96init.crs
rm -Rf /var/opt/oracle/scls_scr
rm -Rf /var/opt/oracle/oprocd
rm /etc/inittab.crs
cp /etc/inittab.orig /etc/inittab
IBM AIX:
rm /etc/init.cssd
rm /etc/init.crs
rm /etc/init.crsd
rm /etc/init.evmd
rm /etc/rc.d/rc2.d/K96init.crs
rm /etc/rc.d/rc2.d/S96init.crs
rm -Rf /etc/oracle/scls_scr
rm -Rf /etc/oracle/oprocd
rm /etc/inittab.crs
cp /etc/inittab.orig /etc/inittab
4. If they are not already down, kill off EVM, CRS, and CSS processes or reboot
the node:
ps -ef | grep crs
kill
ps -ef | grep evm
kill
ps -ef | grep css
kill
Do not kill any OS processes, for example icssvr_daemon process !
5. If there is no other Oracle software running (like listeners, DB's, etc...),
you can remove the files in /var/tmp/.oracle or /tmp/.oracle. Example:
rm -rf /var/tmp/.oracle
or
rm -rf /tmp/.oracle
6. Remove the ocr.loc
Usually the ocr.loc can be found at /etc/oracle
7. Remove the CRS install location:
rm -Rf
8. De-install the CRS home in the Oracle Universal Installer
9. Clean out the OCR and Voting Files with dd commands.
* if /dev/rdsk does not exist, you can skip this
Example:
dd if=/dev/zero of=/dev/rdsk/V1064_vote_01_20m.dbf bs=8192 count=2560
dd if=/dev/zero of=/dev/rdsk/ocrV1064_100m.ora bs=8192 count=12800
If you placed the OCR and voting disk on a shared filesystem, remove them.
If you are removing the RDBMS installation, also clean out any ASM disks if
they have already been used.
10.If you would like to re-install CRS, follow the steps in the RAC Installation manual.
.
Saturday, March 19, 2011
Oracle 8i Recover Database
Steps to recover a oracle 8i database, when you have the database
(provided you are having the complete directory structure)
- in no archive log mode
- no backups
Recovery process
- Backup the files (initdb.ora, pwddb.ora, oradata, admin folders and any other directory structure where tablespaces exists) from the existing structure .
- Copy initdb.ora & pwddb.ora files into the Oracle_Home/database directory structure, where you have installed your oracle binaries.
- Execute the command "ORADIM -NEW -SID sid -INTPWD password -STARTMODE m -PFILE ORACLE_HOME\DATABASE\initdb.ora"
- sqlplus /nolog
- connect internal/oracle as sysdba
- startup pfile= ORACLE_HOME\DATABASE\initdb.ora nomount
- open init.ora file and check the directory structure of the control files & copy your existing control files by creating the same directory structure.
- Execute the command alter database mount
- select * from v$controlfiles;
- select name from v$database;
- create & copy the directory structures of the data files
- Execute the command alter database open;
Once the database is completely mounted and opened, make sure you crosscheck
your recovered data.
Subscribe to:
Posts (Atom)