This is one of the silly mistakes that I have commited quite often.
Trying to assign sysdba previlage to user and getting struck up, only to find the password file is not as per specification.Oracle requires password file to be in the format 'orapwd$SID'.It checks for the presence of the file at $ORACLE_HOME/dbs location.The file should be provided permission 4640.
Run the follwing after loading Oracle Database profile:
orapwd file=$ORACLE_HOME/dbs/orapwd$ORACLE_SID password=oracle entries=5
Change the permission of th created file to 4640.
Parameter REMOTE_LOGIN_PASSWORDFILE should have value remote/shared.
Once the above requirements are satisfied, users could be granted sysdba previlages.
Friday, August 27, 2010
Saturday, June 12, 2010
Places to Go Before I Die
- Leh,India - From Manali by Road
- Alaska
- New Zealand
- Switzerland
- Gurudongmar Lake , Sikkim,India
- Santorini, Greece
- Greenland
- Pamukkale,Cappadocia - Turkey
- The Storr, Scotland
- Anzio, Italy
The list is growing every day.... :-)
Helpful travel URL's
Sikkim Home Stay
Wednesday, June 09, 2010
Oracle Database Cloning using Cold Backup
Steps to clone an Oracle Database (File System Based) using cold backup.
1.Shutdown the source database
2.Backup the datafiles.
3.Copy the datafiles to destination location.
4.Execute the command 'alter database backup controlfile to trace' from the source database.
5.Rename this file to create_db.sql
6.Modify the file for the following:
6.1 Remove the contecnt under NoResetlog Section.
6.2 Rename the work reuse to set
6.3 Update the Database Name
6.4 Comment the commands - RECOVER DATABASE USING ....
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE
6.5 Modify the datafile locations in this file so as to reflect the new location in destination database.
7.Copy the initSID.ora file from the source and to destination location and modify it contents for new database.
8.At the destination location, set the oracle home and oracle sid parameters
9.Connect as Sysdba and execute the create_db.sql script.
10.Once the control file is created ,execute the command 'alter database open resetlogs;'
11.Bounce the database once and it is ready for use.
1.Shutdown the source database
2.Backup the datafiles.
3.Copy the datafiles to destination location.
4.Execute the command 'alter database backup controlfile to trace' from the source database.
5.Rename this file to create_db.sql
6.Modify the file for the following:
6.1 Remove the contecnt under NoResetlog Section.
6.2 Rename the work reuse to set
6.3 Update the Database Name
6.4 Comment the commands - RECOVER DATABASE USING ....
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE
6.5 Modify the datafile locations in this file so as to reflect the new location in destination database.
7.Copy the initSID.ora file from the source and to destination location and modify it contents for new database.
8.At the destination location, set the oracle home and oracle sid parameters
9.Connect as Sysdba and execute the create_db.sql script.
10.Once the control file is created ,execute the command 'alter database open resetlogs;'
11.Bounce the database once and it is ready for use.
Subscribe to:
Posts (Atom)