How Long a Session Has been Idle or Inactive In Oracle Database ?

SYMPTOMS

There are up to one thousand sessions connected to Oracle Database from a Weblogic connection pool. User wanted to know how long those sessions have been idle ( INACTIVE), so the Weblogic connection pool can be reviewed and reconfigured properly.

SOLUTION

The below query can be run to meet this requirement:

SQL>select USERNAME,
           MACHINE,
           STATUS,
           LOGON_TIME,
           LAST_CALL_ET INACTIVE_SECONDS 
    from  gv$session 
    order by LAST_CALL_ET desc; 

USERNAME   MACHINE    STATUS    LOGON_TIME         INACTIVE_SECONDS
---------- ---------- -------   -----------------  ----------------
USERAPP    machine1  INACTIVE   20170917-17:04:17             3523
USERAPP    machine2  INACTIVE   20170918-02:57:03             2068
USERAPP    machine3  INACTIVE   20170917-17:52:09             1141
...
..
.
USERAPP    machine1 INACTIVE   20170917-17:17:01               176
USERAPP    machine1 I NACTIVE   20170917-17:17:01              176

REFERENCES

According to Oracle doc :

LAST_CALL_ET NUMBER If the session STATUS is currently ACTIVE, then the value represents the elapsed time in seconds since the session has become active.If the session STATUS is currently INACTIVE, then the value represents the elapsed time in seconds since the session has become inactive.
Advertisements
Posted in SQL Scripts For DBA | Tagged , | Leave a comment

Data Guard Not Applying Logs After RAC Standby Database Restarted

11.2.0.4 RAC standby database is not applying archivelogs after instances are all restarted.  It is configured in Data Guard management.

After investigation, there is nothing special, but only “PreferredApplyInstance” is configured for RAC node1 ‘STBTEST1’.

Original :

PreferredApplyInstance ='STBTEST1'

Modify “PreferredApplyInstance” to empty:

PreferredApplyInstance=''

Restarted RAC standby database instances , all archivelogs are applied to database from the node which is chosen randomly by Data Guard.

Posted in DataGuard, GI and RAC | Tagged , | Leave a comment

ORA-03135: connection lost contact in12.1.0.2 Standby Database

Newly built 12.1.0.2 DataGuard got below errors:

Primary Database alert.log:

Mon Sep 11 11:35:59 2017
TT01: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
TT01: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Mon Sep 11 11:35:59 2017
Errors in file /u01/app/oracle/diag/rdbms/ractest/RACTEST1/trace/RACTEST1_tt01_30967.trc:
ORA-03135: connection lost contact
Error 3135 for archive log file 42 to 'STBTEST'
Mon Sep 11 11:35:59 2017
Errors in file /u01/app/oracle/diag/rdbms/ractest/RACTEST1/trace/RACTEST1_tt01_30967.trc:
ORA-03135: connection lost contact
LNS: Failed to archive log 42 thread 1 sequence 852 (3135)

Standby Database Alert.log

Fatal NI connect error 12170.

VERSION INFORMATION:
 TNS for Linux: Version 12.1.0.2.0 - Production
 Oracle Bequeath NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production
 TCP/IP NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production
 Time: 06-SEP-2017 16:50:33
 Tracing not turned on.
 Tns error struct:
 ns main err code: 12535

TNS-12535: TNS:operation timed out
 ns secondary err code: 12608
 nt main err code: 0
 nt secondary err code: 0
 nt OS err code: 0
 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xx.xx.xx.xx)(PORT=63637))
Wed Sep 06 16:50:34 2017
RFS[37]: Possible network disconnect with primary database

SOLUTION

Remove SQLNET.SEND_TIMEOUT in sqlnet.ora of standby database.

CAUSE

This issue is identified as  Bug 22061775  when SQLNET.SEND_TIMEOUT exists in sqlnet.ora file.

This issue occurs only on LGWR/ASYNC log transportation.

REFERENCES

ORA-03135 on TTnn process in Standby Database With Sqlnet.send_timeout (Doc ID 2285110.1)

Posted in 12c new features, DataGuard, ORA- ERRORS | Tagged , , , , | Leave a comment

ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added

The below error occurred when creating a new Data Guard Broker configuration on 12.1.0.2 RAC database.

DGMGRL>CREATE CONFIGURATION 'RACTEST_DG' as PRIMARY DATABASE IS 'RACTEST' CONNECT IDENTIFIER IS RACTEST;
Error: ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added

SOLUTION

1)Remove /reset parameter ‘log_archive_dest_2’ on both primary and standby database side.

SQL> alter system set log_archive_dest_2='' scope=both;

System altered.

DGMGRL>CREATE CONFIGURATION 'RACTEST_DG' as PRIMARY DATABASE IS 'RACTEST' CONNECT IDENTIFIER IS RACTEST;
Configuration "RACTEST" created with primary database "RACTEST"

DGMGRL> ENABLE CONFIGURATION;
Enabled.

DGMGRL> show configuration;

Configuration - RACTEST_DG

Protection Mode: MaxPerformance
 Members:
 RACTEST - Primary database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 1 second ago)

2) Add standby database into Data Guard broker.

DGMGRL> ADD DATABASE 'STBTEST' AS CONNECT IDENTIFIER IS 'STBTEST';
Database "STBTEST" added


DGMGRL> show configuration;

Configuration - RACTEST_DG

Protection Mode: MaxPerformance
 Members:
 RACTEST - Primary database
 STBTEST - Physical standby database (disabled)

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 59 seconds ago)


DGMGRL>enable database STBTEST;
Enabled.

3) Check Data Guard status.

DGMGRL> connect /
Connected as SYSDG.
DGMGRL> show configuration;

Configuration - RACTEST_DG

Protection Mode: MaxPerformance
 Members:
 RACTEST - Primary database
 STBTEST - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 50 seconds ago)

Database Status:
 SUCCESS

So there is no ‘log_archive_dest_2’ configured for both primary and standby database before configuring Data Guard Broker in 12.1.0.2 database, as per below extracted from Oracle doc:

As of Oracle Database 12c Release 1 (12.1), for all databases to be added to a broker configuration, any LOG_ARCHIVE_DEST_n parameters that have the SERVICE attribute set, but not the NOREGISTER attribute, must be cleared.

Also Make sure do the same before you configure Data Guard Broker by using Oracle OEM. Otherwise it will fail without any errors provided, for which it might take you some time to investigate.

Posted in DataGuard, ORA- ERRORS | Tagged , , , , , , , | Leave a comment

ORA-15001: diskgroup does not exist or is not mounted. ORA-15040: diskgroup is incomplete

SYMPTOM

              GI: 12.2.0.1.170814 (26609817)
        RAC HOME: 12.1.0.2.160419 (22291127)

Just started to build a standby database. Tried to put standby database controlfile into ASM diskgroup by using RMAN , got below errors:

RMAN> restore controlfile to '+DATA' from '/tmp/standby.ctl';

Starting restore at 2017-09-05 09:44:30
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1694 instance=STYTEST1 device type=DISK

channel ORA_DISK_1: restoring control file
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 09/05/2017 09:44:32
ORA-19870: error while restoring backup piece /tmp/standby.ctl
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15040: diskgroup is incomplete

CAUSE

This is a bug “21626377 – 12.2_150812: DBCA FAILS TO CREATE 12102 DB OVER 12.2 GI/ASM”

SOLUTION

1) Apply latest PSU patch against RAC home( 12.1.0.2). For now , the latest RU for 12.1.0.2 is 12.1.0.2.170814 (26609783).

2) Retry again from RMAN successfully.

RMAN> restore controlfile to '+DATA' from '/tmp/standby.ctl';

Starting restore at 2017-09-05 10:30:39
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=989 instance=STYTEST1 device type=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 2017-09-05 10:30:40

3) Review alert.log. The diskgroup “+DATA” was mounted successfully.

Tue Sep 05 10:30:40 2017
NOTE: ASMB mounting group 2 (DATA)
...
..
.
SUCCESS: mounted group 2 (DATA)
...
..
.
Posted in 12c new features, ASM, GI and RAC | Tagged , , , | Leave a comment

How to Clone Oracle RAC Home in 12c

Here is an example of how to clone 12.1.0.2 RAC home from one cluster to another cluster.

Source RAC home : /u01/app/oracle/product/12.1.0/dbhome_1

Target RAC home: /u01/app/oracle/product/12.1.0/dbhome_3

 

1) As root user, create a copy of the source RAC home on source cluster:

# cd /u01/app/oracle/product/12.1.0/dbhome_1

# tar -cvf ../dbhome_1.tar  ./

2) Manually copy dbhome_1.tar file onto target cluster. Then as root user, extract the file into target RAC home accordingly:

# mkdir -p /u01/app/oracle/product/12.1.0/dbhome_3
# cd /u01/app/oracle/product/12.1.0/dbhome_3
# tar –xvf dbhome_1.tar

3) As root user, change the ownership of the target RAC home:

# chown -R oracle:oinstall /u01/app/oracle/product/12.1.0/dbhome_3

Repeat step 2) and 3 on each node of the target cluster.

4) Clone RAC home as ORACLE_HOME owner ( oracle user here ) on each node by specifying right LOCAL_NODE for each node:

$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_3
$ perl $ORACLE_HOME/clone/bin/clone.pl ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=OraDB12Home3 ORACLE_BASE=/u01/app/oracle "CLUSTER_NODES={racnode1,racnode2}" "LOCAL_NODE=racnode1"
./runInstaller -clone -waitForCompletion "ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_3" "ORACLE_HOME_NAME=OraDB12Home3" "ORACLE_BASE=/u01/app/oracle" "CLUSTER_NODES={racnod1, racnode2}" "LOCAL_NODE=racnode1" -silent -paramFile /u01/app/oracle/product/12.1.0/dbhome_3/clone/clone_oraparam.ini
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 500 MB. Actual 50550 MB Passed
Checking swap space: must be greater than 500 MB. Actual 20479 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2017-09-04_04-40-39PM. Please wait ...You can find the log of this install session at:
 /u01/app/oraInventory/logs/cloneActions2017-09-04_04-40-39PM.log
.................................................. 5% Done.
.................................................. 10% Done.
.................................................. 15% Done.
.................................................. 20% Done.
.................................................. 25% Done.
.................................................. 30% Done.
.................................................. 35% Done.
.................................................. 40% Done.
.................................................. 45% Done.
.................................................. 50% Done.
.................................................. 55% Done.
.................................................. 60% Done.
.................................................. 65% Done.
.................................................. 70% Done.
.................................................. 75% Done.
.................................................. 80% Done.
.................................................. 85% Done.
..........
Copy files in progress.

Copy files successful.

Link binaries in progress.

Link binaries successful.

Setup files in progress.

Setup files successful.

Setup Inventory in progress.

Setup Inventory successful.

Finish Setup successful.
The cloning of OraDB12Home3 was successful.
Please check '/u01/app/oraInventory/logs/cloneActions2017-09-04_04-40-39PM.log' for more details.

Setup Oracle Base in progress.

Setup Oracle Base successful.
.................................................. 95% Done.

As a root user, execute the following script(s):
 1. /u01/app/oracle/product/12.1.0/dbhome_3/root.sh

Execute /u01/app/oracle/product/12.1.0/dbhome_3/root.sh on the following nodes:
[racnode1]
.................................................. 100% Done.


# /u01/app/oracle/product/12.1.0/dbhome_3/root.sh
Check /u01/app/oracle/product/12.1.0/dbhome_3/install/root_racnode1_2017-09-04_16-42-21.log for the output of root script

5) Check new RAC home has been register in target cluster oraInventory:

$cd /u01/app/oraInventory/ContentsXML

$ cat inventory.xml
...
..
.
<HOME NAME="OraDB12Home3" LOC="/u01/app/oracle/product/12.1.0/dbhome_3" TYPE="O" IDX="10">
 <NODE_LIST>
 <NODE NAME="racnode1"/>
 <NODE NAME="racnode2"/>
 </NODE_LIST>
</HOME>
...
..
.

6) Check patches of target RAC home  binary which is same as source RAC home binary:

$opatch lsinventory

7) Review the log files from cloning:

  • Central_Inventory/logs/cloneActionstimestamp.log
    
    Contains a detailed log of the actions that occur during the Oracle Universal Installer part of the cloning.
  • Central_Inventory/logs/oraInstalltimestamp.err
    
    Contains information about errors that occur when Oracle Universal Installer is running.
  • Central_Inventory/logs/oraInstalltimestamp.out
    
    Contains other miscellaneous messages generated by Oracle Universal Installer.
Posted in GI and RAC | Tagged , , , , | Leave a comment

How to Find Mapping Between ASM Disks and Physical Disks

Here are the simple steps for mapping between ASM disks and physical disks in Linux 7.3 and GI 12cR2.

1) List all ASM disks:

$oracleasm listdisks
...
..
.
OCR_VOTE
..
.

2) To get the major and minor number for the ASM disk:

a) List from /dev/oracleasm/disks/

$ ls -ltr /dev/oracleasm/disks/OCR_VOTE
brw-rw----. 1 grid dba 253, 6 Aug 29 10:18 /dev/oracleasm/disks/OCR_VOTE
$

or

b) Run “oracleasm querydisk -d ” :

$ oracleasm querydisk -p -d OCR_VOTE
Disk "OCR_VOTE" is a valid ASM disk on device [253,6]
/dev/mapper/ocr_votep1: LABEL="OCR_VOTE" TYPE="oracleasm"

c) Map to physical disk by using major and minor value:

$ ls -ltr /dev/|grep "253, 6"
brw-rw----. 1 root disk 253, 6 Aug 29 10:18 dm-6

OR

$ls -ltr /dev/mapper/|grep dm-6
lrwxrwxrwx. 1 root root 7 Aug 29 10:18 ocr_votep1 -> ../dm-6
# multipath -l|grep -i ocr_vote
ocr_vote (3600a09803830344a6b2b473639763735) dm-5 NETAPP ,LUN C-Mode
$ls -ltr /dev/mapper/|grep ocr_vote
lrwxrwxrwx. 1 root root 7 Aug 29 09:54 ocr_vote -> ../dm-5
lrwxrwxrwx. 1 root root 7 Aug 29 10:18 ocr_votep1 -> ../dm-6
Posted in ASM, GI and RAC | Tagged , , , , | Leave a comment

PRVG-10091 : failed to retrieve the ASM password file location for an ASM instance

Problem

Verifying system upgrade readiness for Grid Infrastructure 12.1.0.2 to 12.2.0.1 with below command, then get “PRVG-10091” warning:

$ /u01/app/12.2.0.1/grid/runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /u01/app/12.1.0.2/grid -dest_crshome /u01/app/12.2.0.1/grid -dest_version 12.2.0.1.0 -fixupnoexec -verbose

...
..
.
Verifying Verify that the ASM instance was configured using an existing ASM
parameter file. ...FAILED
PRVG-10091 : failed to retrieve the ASM password file location for an ASM
instance.
...
..
.

Investigation

The ASM password file parameter is not configured, it’s required for 12.2.0.1 upgrade.

$ srvctl config asm -a
ASM home: <CRS home>
Password file:       <------ MISSING
ASM listener: LISTENER
ASM is enabled.
ASM is individually enabled on nodes:
ASM is individually disabled on nodes:

Solution

1)Found the password file under GI_HOME/dbs/,  then modify ASM configuration by using srvctl, rerun the CVU checks, still failed with different “ASMCMD-8001” warning message:

$ /u01/app/12.1.0.2/grid/dbs$ ls -ltr /u01/app/12.1.0.2/grid/dbs/orap*
-rw-r-----. 1 grid oinstall 8704 Aug 25 11:46 orapw+ASM


$ srvctl modify asm -pwfile /u01/app/12.1.0.2/grid/dbs/orapw+ASM
$ srvctl config asm -a
ASM home: <CRS home>
Password file: /u01/app/12.1.0.2/grid/dbs/orapw+ASM
ASM listener: LISTENER
ASM is enabled.
ASM is individually enabled on nodes:
ASM is individually disabled on nodes:

-- new warning mesasage
--
Verifying Verify that the ASM instance was configured using an existing ASM
parameter file. ...FAILED
PRCT-1011 : Failed to run "asmcmd". Detailed error:
ASMCMD-8001: diskgroup 'u01' does not exist or is not mounted

So the password file has to be stored in ASM diskgroup instead of local disk.

2) Move  current passwordfile into  ASM diskgroup:

a) Get current ASM password information:

ASMCMD> pwget --asm
/u01/app/12.1.0.2/grid/dbs/orapw+ASM

ASMCMD> lspwusr
Username sysdba sysoper sysasm
 SYS     TRUE   TRUE    TRUE
 ASMSNMP TRUE   FALSE   FALSE

b) Copy current password file into ASM diskgroup:

-- password name "orapw+ASM" is not accepted in diskgroup
--
ASMCMD> pwcopy /u01/app/12.1.0.2/grid/dbs/orapw+ASM OCR_VOTE/orapw+ASM
ASMCMD-8001: diskgroup 'orapw+ASM' does not exist or is not mounted

-- requires compatible.asm of 12.1.0.0.0 or higher
--
ASMCMD> pwcopy /u01/app/12.1.0.2/grid/dbs/orapw+ASM +OCR_VOTE/orapwASM
copying /u01/app/12.1.0.2/grid/dbs/orapw+ASM -> +OCR_VOTE/orapwASM
ASMCMD-8016: copy source '/u01/app/12.1.0.2/grid/dbs/orapw+ASM' and target '+OCR_VOTE/orapwASM' failed
ORA-19505: failed to identify file "+OCR_VOTE/orapwasm"
ORA-17502: ksfdcre:4 Failed to create file +OCR_VOTE/orapwASM
ORA-15056: additional error message
ORA-15221: ASM operation requires compatible.asm of 12.1.0.0.0 or higher
ORA-06512: at line 4
ORA-06512: at "SYS.X$DBMS_DISKGROUP", line 486
ORA-06512: at line 3 (DBD ERROR: OCIStmtExecute)
ASMCMD>

-- set compatible.asm of 12.1.0.0.0 or higher
--

SQL> select NAME,COMPATIBILITY,VOTING_FILES from v$asm_diskgroup where NAME='OCR_VOTE';

NAME COMPATIBILITY                VOTING_FILES
------------------------------ ------------------------------ -
OCR_VOTE 11.2.0.0.0              Y


SQL> alter diskgroup OCR_VOTE  set attribute 'compatible.asm'='12.1.0.0.0';
Diskgroup altered.

SQL> select NAME,COMPATIBILITY,VOTING_FILES from v$asm_diskgroup where NAME='OCR_VOTE';

NAME COMPATIBILITY             VOTING_FILES
------------------------------ ------------------------------ -
OCR_VOTE 12.1.0.0.0           Y

-- Copy passwordfile into diskgroup OCR_VOTE again
--
ASMCMD> pwcopy /u01/app/12.1.0.2/grid/dbs/orapw+ASM +OCR_VOTE/orapwASM
copying /u01/app/12.1.0.2/grid/dbs/orapw+ASM -> +OCR_VOTE/orapwASM

c) Reconfigure ASM  instance to use passwordfile in diskgroup

$ srvctl modify asm -pwfile +OCR_VOTE/orapwASM
$ srvctl config asm -a
ASM home: <CRS home>
Password file: +OCR_VOTE/orapwASM
ASM listener: LISTENER
ASM is enabled.
ASM is individually enabled on nodes:
ASM is individually disabled on nodes:
$

d) Rerun the CVU checks successfully.

...
..
.
Verifying Daemon "proxyt" not configured and running ...PASSED
Verifying loopback network interface address ...PASSED
Verifying Grid Infrastructure home path: /u01/app/12.2.0.1/grid ...
 Verifying '/u01/app/12.2.0.1/grid' ...PASSED
Verifying Grid Infrastructure home path: /u01/app/12.2.0.1/grid ...PASSED
Verifying Privileged group consistency for upgrade ...PASSED
Verifying CRS user Consistency for upgrade ...PASSED
Verifying Clusterware Version Consistency ...PASSED
Verifying Check incorrectly sized ASM Disks ...PASSED
Verifying Network configuration consistency checks ...PASSED
Verifying File system mount options for path GI_HOME ...PASSED
Verifying /boot mount ...PASSED
Verifying OLR Integrity ...PASSED
Verifying Verify that the ASM instance was configured using an existing ASM parameter file. ...PASSED
Verifying User Equivalence ...
Verifying Checking user equivalence for user "grid" on all cluster nodes ...PASSED
...
..
.
Posted in 12c new features, ASM, GI and RAC, Upgrading and Patching | Tagged , , , , , , , , , | Leave a comment

How to Disable SELinux or Set SELinux to Permissive Mode

It is suggested to disable SELinux or set SELinux to permissive mode for Oracle GI/RAC. Otherwise you might get similar below errors:

Disk "ASM_DISK1" does not exist or is not instantiated
Writing disk header: done
Instantiating disk: oracleasm-instantiate-disk: Unable to open manager: No such file or directory 
failed
Clearing disk header: done

Solution

For REHL7.3  :

1) Permanently disable SELinux:

a) Modify /etc/selinux/config, and change the SELINUX value:

SELINUX=disabled

b) Reboot the server.

2) Permanently set SELinux to Permissive mode:

a) Modify /etc/selinux/config, and change the SELINUX value:

SELINUX=permissive

b) Reboot the server.

3) Change SELinux running mode without rebooting

a) Change to Permissive mode:

# setenforce
usage: setenforce [ Enforcing | Permissive | 1 | 0 ]

# setenforce 0

b) Change to  Enforcing mode:

# setenforce
usage: setenforce [ Enforcing | Permissive | 1 | 0 ]

# setenforce 0

4) Check the status of SELinux:

a) Use “getenforce” command:

# which getenforce
/usr/sbin/getenforce

# /usr/sbin/getenforce
Permissive

b) Use “sestatus” command:

# which sestatus
/usr/sbin/sestatus

# /usr/sbin/sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 28
#
Posted in ASM, Configuration, Linux, Security | Tagged , , , , , , , , , , , | Leave a comment

ORA-15260: permission denied on ASM disk group

Problem

Try to set ASM diskgroup attribute, then get below errors:

$ sqlplus / as sysdba
...
..
.
SQL> alter diskgroup OCR_VOTE SET ATTRIBUTE 'compatible.asm' ='11.2.0.2';
alter diskgroup OCR_VOTE SET ATTRIBUTE 'compatible.asm' ='11.2.0.2'
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15260: permission denied on ASM disk group

Solution

Logon ASM instance with right privilege

$ sqlplus / as sysasm

...
..
.
SQL> alter diskgroup OCR_VOTE SET ATTRIBUTE 'compatible.asm' ='11.2.0.2';

Diskgroup altered.
Posted in ASM, GI and RAC, ORA- ERRORS, User Privileges and Roles | Tagged , , | Leave a comment