[INS-41208] None of the available network subnets is marked for use by Oracle Automatic Storage Management (ASM)
Cause – At least one of the available network subnets should be configured for use by Oracle Automatic Storage Management (ASM). Action – Configure one of the available network subnets for Oracle Automatic Storage Management (ASM) use if you intend to configure Near Oracle ASM or Client Oracle ASM This error occurs when we install flex clusters in RACContinue reading “[INS-41208] None of the available network subnets is marked for use by Oracle Automatic Storage Management (ASM)”
[INS-41107] The interface (eth1) chosen as Public or Private is not on a shared subnet. Nodes not defining are: [rac2]
Network interface subnet are not same for both the RAC nodes Cause – The Public or Private interface on the nodes indicated are on a different subnet than the ones used on other nodes.Action – Ensure that the specified Public or Private interface share the same subnet across the nodes. NODE 1: NODE 2: Solution: Contact your network adminContinue reading “[INS-41107] The interface (eth1) chosen as Public or Private is not on a shared subnet. Nodes not defining are: [rac2]”
[INS-40401] The Installer has detected a configured Oracle Clusterware home on the system.
RAC installation fail due to some misconfiguration When we reinstall RAC,we see the below error It is better to deconfigure and cleanup the debris which are partially configured in grid home Deconfigure the oracle high availability using perl script on the grid home Run the deinstall script to cleanup the failed inventory Run the crsContinue reading “[INS-40401] The Installer has detected a configured Oracle Clusterware home on the system.”
Wipe out and reuse ASM disk header !
Grid installation fails due to issues to execute root.sh scripts on both nodes It is always a challenge,if the installation get failed at half of progress and there is no other option that we have to reinstall grid because of ignorance of failed prerequisites Read the disk header to check the validity of the diskContinue reading “Wipe out and reuse ASM disk header !”
ORA-01722: invalid number[sqlldr]
When loading data using sqlloader from a csv file to a table,due to improper format of integers in specific columns, we get ora-1722 error Solution: Add filler option on the column where you have format mismatch of numbers The error is bypassed!
Recovery catalog for your database
Create a catalog user grant permissions to user Create tablespace for catalog and map it to rcat user Connect to recovery catalog with the user create a catalog and register to the database Crosscheck backup of the database to verify the catalog in action Verify the databases registered with recovery catalog
ORA-06598: insufficient INHERIT PRIVILEGES privilege
I get the below error while generating sqltxtract and sqltxplain analysis with sqltxadmin user and my session got disconnected and kicked me out ! Solution: Ensure that you have connected to sqltxplain user and the sqlt users have following privileges to access the sqltx packages.
Configure logical partitions for oracle asm
Use fdisk to list the physical disks available to create logical sectors on the device.Here we have external disks added with persistent storage. We add primary partitions for all the devices /dev/sda , /dev/sdb, /dev/sdc, /dev/sdd … Download oracleasmlib and oracleasmsupport rpms using yum or download from support website to use oracleasm utility ! FirstContinue reading “Configure logical partitions for oracle asm”
Why to choose an optimizer goal?
Optimizer is a software or an algorithmic code which has the intelligence to decide the path to access the data in an efficient way in oracle database. We have options to choose optimizer mode to prioritize the utilization of resources to serve their own purpose. There are two options in cost based optimizer mode ALL_ROWSContinue reading “Why to choose an optimizer goal?”
ORA-39095: Dump file space has been exhausted: Unable to allocate 8192 bytesJob “SYS”.”SYS_EXPORT_FULL_02″ stopped due to fatal error
While exporting full database with multiple files per set and degree of parallelism,we encounter the ORA-39095 error Solution: 1)FILESIZESpecify the size of each dump file in units of bytes. The parameter value should be increased as per the total size of the object or database eg: If database size is 1GB,then filesize per set =Continue reading “ORA-39095: Dump file space has been exhausted: Unable to allocate 8192 bytesJob “SYS”.”SYS_EXPORT_FULL_02″ stopped due to fatal error”
Loading…
Something went wrong. Please refresh the page and/or try again.
Follow My Blog
Get new content delivered directly to your inbox.
