Oracle Error:
SQL> startup nomount pfile=”C:\db\init.ora”;
ORA-00380: cannot specify db_##k_cache_size since 16K is the standard block size
Solution: Cannot define a non-standard block size the same size as the db_block_size
IF db_block_size=2048 then you cannot set db_2k_cache_size
IF db_block_size=4096 then you cannot set db_4k_cache_size
If db_block_size=16384 then you cannot set db_16k_cache_size
IF db_block_size=32768 then you cannot set db_32k_cache_size
This article covers the conversion of a pre-existing Oracle 11g single instance database into a two node RAC. The following assumptions are made for this procedure to execute correctly:
1. Oracle 11g GRID has been installed on both RAC nodes.
2. Oracle 11g RDBMS has been installed on both RAC nodes.
3. Oracle 11g single instance database has been copied to RAC node 1 and operates correctly as a single instance database.
1. Logon to node 1 of your Oracle RAC server as the RDBMS owner.
2. Copy the file $ORACLE_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC_AdminManaged.xml
[oracle@mylinux1 dbhome_1]$ cp $ORACLE_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC_AdminManaged.xml orcl.xml
[oracle@mylinux1 dbhome_1]$
2. The sample XML file gives detailed instruction on how to edit the file for your specific use. In this example edit the following lines:
SourceDBHome = Single instance Oracle Home directory
TargetDBHome = RAC instance Oracle Home, this could be the same as the single instance Oracle Home directory
SourceDBInfo SID= SID of the Source database.
Password = SYS password
Node name= node1 name, normally this is the machine name.
Node name= node2 name, normally this is the machine name.
InstancePrefix = prefix of your RAC database, normally this is equal to the SID of your source database.
SharedStorage type=”ASM” or “OCFS”
3. Ensure that the single instance database is up and running.
[oracle@mylinux1 dbhome_1]$ ps -ef|grep smon
oracle 18508 1 0 02:12 ? 00:00:00 ora_smon_orcl
oracle 26774 7777 0 02:46 pts/1 00:00:00 grep smon
[oracle@mylinux1 dbhome_1]$
4. Execute the rconfig command and pass your edited xml file to it.
[oracle@mylinux1 bin]$ ./rconfig ./orcl.xml
Converting Database “orcl” to Cluster Database. Target Oracle Home: /u01/app/oracle/product/11.2.0/dbhome_1. Database Role: PRIMARY.
Setting Data Files and Control Files
Adding Database Instances
Adding Redo Logs
Enabling threads for all Database Instances
Setting TEMP tablespace
Adding UNDO tablespaces
Adding Trace files
Setting Flash Recovery Area
Updating Oratab
Creating Password file(s)
Configuring Listeners
Configuring related CRS resources
Starting Cluster Database
< ?xml version=”1.0″ ?>
Operation Succeeded
/u01/app/oracle/product/11.2.0/dbhome_1
[oracle@mylinux1 bin]$>
5. Now the database can be confirmed in rac mode on both nodes.
[oracle@mylinux1 bin]$ ps -ef|grep smon
oracle 16544 1 0 03:04 ? 00:00:00 ora_smon_orcl1
oracle 21072 7777 0 03:07 pts/1 00:00:00 grep smon
[oracle@mylinux1 bin]$
[root@mylinux2 ~]# ps -ef|grep smon
oracle 27298 1 0 03:03 ? 00:00:00 ora_smon_orcl2
root 29474 23387 0 03:07 pts/4 00:00:00 grep smon
[root@mylinux2 ~]#
This completes configuration of single instance to Oracle 11g RAC.
Larry J. Catt, OCP
oracle@allcompute.com
www.allcompute.com
Error: During use of RMAN utility the following is generated.
RMAN-00554: initialization of internal recovery manager package failed
RMAN-03000: recovery manager compiler component initialization failed
RMAN-06001: error parsing job step library
RMAN-01006: error signalled during parse
RMAN-00600: internal error, arguments [8083] [] [] [] []
LFI-00005: Free some memory failed in lfibrdt().
LFI-00004: Call to lfibgl() failed.
[oracle@mylinux1 bin]$
Check: Look at the storage configuration of both the RMAN binaries and location of backups. In this example the storage was OCFS, which can be used for both the backup pieces and the binaries, but not with the tag – datavolume.
/dev/mapper/oracle_home /rac1 ocfs2 _netdev,datavolume,nointr 0 0
1. Logon to the Oracle server as the root user.
2. Dismount the storage in question.
umount /rac1
3. Mount the storage without the datavolume tag.
mount /dev/mapper/oracle_home /rac1 ocfs2 _netdev,nointr 0 0
4. Update your /etc/fstab file with new entries.
This completes resolution of RMAN error due to use of OCFS storage.
Larry Catt, OCP
oracle@allcompute.com
www.allcompute.com
The following procedure shows how to remove an Oracle database with dbca utility from the command line.
1. Logon as the oracle software owner.
[root@mylinux2 root]# su – oracle
[oracle@mylinux2 ~]$
2. Change directories to $ORACLE_HOME/bin
[oracle@mylinux2 ~]$ cd $ORACLE_HOME/bin
[oracle@mylinux2 bin]$
3. Obtain the ORACLE_SID of the database you wish to delete.
[oracle@mylinux2 bin]$ ps -ef|grep smon
oracle 4746 1 0 Feb09 ? 00:00:00 ora_smon_orcl
oracle 7839 7796 0 00:39 pts/1 00:00:00 grep smon
[oracle@mylinux2 bin]$
4. Obtain the userid and password of a user with sysdba privileges, normally this would be sys.
5. Logon to the database if open with the immediate option and exit.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@mylinux2 bin]$
6. Ensure that no oracle database processes are running for the ORACLE_SID you wish to delete
[oracle@mylinux2 bin]$ ps -ef|grep orcl
oracle 11485 7796 0 01:46 pts/1 00:00:00 grep orcl
[oracle@mylinux2 bin]$
7. Execute the command dbca -deleteDatabase -sourceDB Larry J. Catt, OCP
[oracle@mylinux2 bin]$ ./dbca -silent -deleteDatabase -sourceDB orcl – sysDBAUserName larry -sysDBAPassword larry
Connecting to database
4% complete
9% complete
14% complete
19% complete
23% complete
28% complete
47% complete
Updating network configuration files
48% complete
52% complete
Deleting instance and datafiles
76% complete
100% complete
Look at the log file “/u01/app/oracle/cfgtoollogs/dbca/orcl.log” for
further details.
[oracle@mylinux2 bin]$
This completes deleting an oracle database from command line with dbca.
oracle@allcompute.com
www.allcompute.com
The following Perl command will change a string in every file of the present directory.
NOTE: Remove the <> symbols.
[old_string] = String you want replaced.
[new_string] = New string.
perl -p -i -e “s/[old_string]/[new_string]/g” *
Larry Catt, OCP
oracle@allcompute.com
www.allcompute.com
Error:
[oracle@mylinux1 bin]$ ./dbca -silent -deleteDatabase -sourceDB orcl -sysDBAUserName larry -sysDBAPassword larry
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORA-00845: MEMORY_TARGET not supported on this system
Solution:
1. Logon to the database as sysdba
2. Execute the command.
SQL> show parameter memory_target;
NAME TYPE VALUE
———————————— ———– ——————————
memory_target big integer 3104M
SQL>
3. Issue the command.
SQL> alter system reset memory_target;
System altered.
SQL>
4. Shutdown the database
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
5. Startup the database.
SQL> startup open
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 217157632 bytes
Fixed Size 2211928 bytes
Variable Size 159387560 bytes
Database Buffers 50331648 bytes
Redo Buffers 5226496 bytes
Database mounted.
Database opened.
SQL>
6. Execute command:
SQL> show parameter memory_target
NAME TYPE VALUE
———————————— ———– ——————————
memory_target big integer 0
SQL>
7. re-execute
[oracle@mylinux1 bin]$ ./dbca -silent -deleteDatabase -sourceDB orcl -sysDBAUserName larry -sysDBAPassword larry
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
[oracle@mylinux1 bin]$
This completes resolution of Oracle Error ORA-32004 – ORA-00845.
Larry Catt, OCP
oracle@allcompute.com
www.allcompute.com
Moving Oracle RAC databases into and out of archive log mode requires a few more steps due to the existence of multiple instances. This procedure covers the steps required to move a non-archive log mode database into archive log mode.
1. Logon to Oracle node1 server as the oracle software owner.
2. Validate the current archive log mode of the database, by logging onto the database and issuing the [archive log list] command.
[oracle@mylinux1 ~]$ export ORACLE_SID=orcl1
[oracle@mylinux1 ~]$ sqlplus ‘/ as sysdba’
SQL*Plus: Release 11.2.0.1.0 Production on Thu Jan 20 22:57:07 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u05/oradata/orcl/archive
Oldest online log sequence 66
Current log sequence 68
3. Move the node out of cluster mode by changing the parameter cluster_database equal to false and exit.
SQL> alter system set cluster_database=false scope=spfile;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
[oracle@mylinux1 ~]$
4. Stop the clustered database with srvctl utility.
[oracle@mylinux1 ~]$ srvctl stop database -d orcl
5. Logon to sqlplus on node1 and startup the instance in single instance mode with mount option.
[oracle@mylinux1 ~]$ sqlplus ‘/ as sysdba’
SQL*Plus: Release 11.2.0.1.0 Production on Thu Jan 20 22:59:08 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 367476736 bytes
Fixed Size 2213376 bytes
Variable Size 293603840 bytes
Database Buffers 67108864 bytes
Redo Buffers 4550656 bytes
Database mounted.
SQL>
6. Alter the database to archive log mode.
SQL> alter database archivelog;
Database altered.
SQL>
7. Change the parameter cluster_database back to true, shutdown the instance, and exit.
SQL> alter system set cluster_database=true scope=spfile;
System altered.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
8. Use the srvctl utility to startup the clustered database.
[oracle@mylinux1 ~]$ srvctl start database -d orcl
9. Logon to sqlplus on node1 and check the archive log mode with the command [archive log list].
[oracle@mylinux1 ~]$ sqlplus ‘/ as sysdba’
SQL*Plus: Release 11.2.0.1.0 Production on Thu Jan 20 23:01:22 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u05/oradata/orcl/archive
Oldest online log sequence 66
Next log sequence to archive 68
Current log sequence 68
SQL>
This completes moving an Oracle RAC database into archive log mode.
Larry J. Catt, OCP
oracle@allcompute.com
www.allcompute.com
During the normally life cycle of a database, multiple upgrades will occur, resulting in parameters becoming obsolete. This article shows how to determine the parameter which is obsolete and removing it.
Typical error generated by an obsolete parameter:
[oracle@mylinux2 bin]$ ./dbca -silent -deleteDatabase -sourceDB orcl
-sysDBAUserName larry -sysDBAPassword larry
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
[oracle@mylinux2 bin]$
1. Logon to the database as the sys user.
[oracle@mylinux2 bin]$ sqlplus ‘/ as sysdba’
SQL*Plus: Release 11.2.0.1.0 Production on Thu Feb 10 01:32:07 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
2. Execute the following SQL to find the problem
select name, value from v$parameter where ISDEPRECATED=’TRUE’ and ISDEFAULT=’FALSE’;
SQL> select name, value from v$parameter where ISDEPRECATED=’TRUE’ and ISDEFAULT=’FALSE’;
NAME
——————————————————————————–
VALUE
——————————————————————————–
remote_os_authent
FALSE
SQL>
3. Reset this parameter
SQL> alter system reset remote_os_authent;
System altered.
SQL>
4. Stop database.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
5. Start database.
SQL> startup
ORACLE instance started.
Total System Global Area 217157632 bytes
Fixed Size 2211928 bytes
Variable Size 159387560 bytes
Database Buffers 50331648 bytes
Redo Buffers 5226496 bytes
Database mounted.
Database opened.
SQL>
This completes removing of obsolete or deprecated Oracle parameters.
Larry Catt, OCP
oracle@allcompute.com
www.allcompute.com
If you have executed root.sh on the installation of an Oracle 11g clusterware or RDBMS install and it failed. Remove the changes made by root.sh before re-execution with the following procedure.
1. Logon as the root user.
2. Navigate to the Oracle GRID_HOME
3. Execute the following command.
/opt/app/11.2.0/grid/crs/install/rootcrs.pl -deconfig –force -verbose
This completes the undoing the execution of root.sh from an Oracle Grid Installation.
Larry J. Catt, OCP 9i, 10g
oracle@allcompute.com
www.allcompute.com
The following procedure shows how to debug the Oracle opatch utility when you receive an error.
1. Execution of opatch utility results in the following error.
[oracle@mylinux1 OPatch]$ opatch lsinventory
Invoking OPatch 11.1.0.6.6
Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/11.2.0/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /etc/oraInst.loc
OPatch version : 11.1.0.6.6
OUI version : 11.2.0.1.0
OUI location : /u01/app/oracle/product/11.2.0/dbhome_1/oui
Log file location : /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2011-04-02_19-17-51PM.log
Patch history file: /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch_history.txt
Inventory load failed… OPatch cannot load inventory for the given Oracle Home.
LsInventorySession failed: Unable to create patchObject
OPatch failed with error code 73
[oracle@mylinux1 OPatch]$
2. Set the environmental variable OPATCH_DEBUG equal to true.
[oracle@mylinux1 OPatch]$ export OPATCH_DEBUG=true
[oracle@mylinux1 OPatch]$
3. Re-execute your opatch utility and every action performed by opatch will be displayed in your buffer. Use the messages to determine the error.
This completes use of debug with the opatch utility.
Larry J. Catt, OCP
oracle@allcompute.com
www.allcompute.com