Online DBA

<<Back to Oracle ASM Main Page ORA-15106: missing or invalid operating system disk locator string +ASM2>  alter diskgroup DATA add failgroup DATA_1 disk  '/dev/mapper/oradata_s2_45',  '/dev/mapper/oradata_s2_47', failgroup DATA_2 disk  '/dev/mapper/oradata_s2_46',  '/dev/mapper/oradata_s2_48' rebalance power 3; ERROR at line 3: ORA-15106: missing or invalid operating system disk locator string Cause: The command did not specify a valid operating system path for the device as a string. Troubleshooting TIPPS 1> Check if all the disks got correct permissions at OS level eg, ls -lrt  /dev/mapper/oradata_s2_45 2> Verify the  asm_diskstring parameter is set to discover the newly added disks SQL> show parameter string NAME                     TYPE  VALUE asm_diskstring           string  /dev/mapper/*s2* 3> Check if ASM can see these disks +ASM2> select MOUNT_STATUS,HEADER_STATUS,NAME,PATH,FAILGROUP from v$asm_disk wh

<<Back to DB Administration Main Page How to Resolve Vendor Code 17002 Unable to Connect to Oracle DB Check out following 1) host name resolves correctly 2) network access to the host is ok 3) there is a listener running on the host 4) there is exactly one listener running with same name <ps -ef|grep tns> 5) the listener is configured to run on port P. and you are using port P to connect

<<Back to Oracle RAC Main Page How to disable crs auto start/restart in oracle RAC Disable CRS auto start #crsctl disable crs CRS-4621: Oracle High Availability Services autostart is disabled . Use the crsctl disable crs command to prevent the automatic startup of Oracle High Availability Services when the server boots. This command only affects the local server If you disable Oracle High Availability Services automatic startup, you must use the crsctl start crs command to start Oracle High Availability Services. You can check the current CRS configuration using below command Check the current CRS configuration #  crsctl config crs CRS-4622: Oracle High Availability Services autostart is enabled .

<<Back to Exadata Main Page Listing Exadata storage cells and their configuration info login to your Exadata Cell Server and execute below command # imageinfo Kernel version: 2.6.39-400.284.1.el6uek.x86_64 #1 SMP Mon Sep 12 19:26:25 PDT 20                                                                                                             16 x86_64 Cell version: OSS_12.1.2.3.3_LINUX.X64_161013 Cell rpm version: cell-12.1.2.3.3_LINUX.X64_161013-1.x86_64 Active image version: 12.1.2.3.3.161013 Active image kernel version: 2.6.39-400.284.1.el6uek Active image activated: 2016-10-25 14:54:29 +0200 Active image status: success Active system partition on device: /dev/md5 Active software partition on device: /dev/md7 Cell boot usb partition: /dev/sdm1 Cell boot usb version: 12.1.2.3.3.161013 Inactive image version: 12.1.2.3.2.160721 Inactive image activated: 2016-09-13 16:03:45 +0200 Inactive image status: success Inactive system partition on device: /dev/md6 Inactive softwar

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the

<<Back to DB Administration Main Page What is TEMP Tablespace? A temporary tablespace contains transient data that persists only for the duration of a session. No permanent schema objects can reside in a temporary tablespace. A temp file stores temporary tablespace data. Types of Temp Tablespace Starting from 12.2 Temporary tablespaces can be shared or local. How to Find if a Tablespace is shared or local SQL>select TABLESPACE_NAME,SHARED from DBA_TEMP_FILES where upper (TABLESPACE_NAME)=upper('&TABLESPACE_NAME'); What is Default Temporary Tablespaces Every database user account is assigned a default shared temporary tablespace. If the database contains local temporary tablespaces, then every user account is also assigned default local temporary tablespace. A user query can access either shared or local temporary tablespace. After the database accesses a temporary tablespace for a query, it does not switch to a different one. How to find the default