In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
Oracle Study-Oracle 11gR2 access ASM disk group error
System environment: RedHat EL6
Oracle: Oracle 11gR2
In Oracle 11gR2, in a project that migrates file systems to ASM disk groups, Oracle users cannot access ASM disk groups. In Oracle 11gR2, grid users manage ASM instance, and the following error is found after inspection:
SQL > select name,state from v$asm_diskgroup
NAME STATE
DATA MOUNTED
FRA MOUNTED
SQL > show parameter control
NAME TYPE VALUE
-
Control_file_record_keep_time integer 7
Control_files string + FRA
Control_management_pack_access string DIAGNOSTIC+TUNING
SQL >
Control file migration and Oracle users cannot access FRA disk groups:
RMAN > restore controlfile from'/ u01max App amp oracle control 01.ctl'
Starting restore at 15-MAR-16
Using target database control file instead of recovery catalog
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID=21 device type=DISK
RMAN-00571: =
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =
RMAN-00571: =
RMAN-03002: failure of restore command at 03/15/2016 17:48:57
ORA-19504: failed to create file "+ FRA"
ORA-17502: ksfdcre:4 Failed to create file + FRA
ORA-15001: diskgroup "FRA" does not exist or is not mounted
ORA-15055: unable to connect to ASM instance
ORA-12547: TNS:lost contact
ORA-19600: input file is control file (/ u01/app/oracle/oradata/prod/control01.ctl)
ORA-19601: output file is control file (+ FRA)
RMAN > restore controlfile from'/ u01max App amp oracle control 01.ctl'
Starting restore at 15-MAR-16
Using channel ORA_DISK_1
Channel ORA_DISK_1: copied control file copy
Output file name=+FRA/prod/controlfile/current.256.906573439
Finished restore at 15-MAR-16
Solution:
1. View $ORACLE_HOME/bin/oracle
[oracle@node1 ~] $ls-l / u01/app/oracle/product/11.2.0/db_1/bin/oracle
-rwxr-x--x 1 oracle asmadmin 173515991 Mar 15 14:14 / u01/app/oracle/product/11.2.0/db_1/bin/oracle
-for the executable file of $ORACLE_HOME/bin/oracle, the grid user should have permission to access and modify:
[root@node1 ~] # chmod 6751 / u01/app/oracle/product/11.2.0/db_1/bin/oracle
[oracle@node1 ~] $ls-l / u01/app/oracle/product/11.2.0/db_1/bin/oracle
-rwsr-s--x 1 oracle asmadmin 173515991 Mar 15 14:14 / u01/app/oracle/product/11.2.0/db_1/bin/oracle
2. View $GRID_HOME/bin/oracle
[root@node1 ~] # ls-l / u01/11.2.0/grid/bin/oracle
-rwxrwxr-x 1 grid oinstall 152462814 Mar 15 14:00 / u01/11.2.0/grid/bin/oracle
Modify permissions:
[root@node1 ~] # chmod + s / u01/11.2.0/grid/bin/oracle
[root@node1 ~] # ls-l / u01/11.2.0/grid/bin/oracle
-rwsrwsr-x 1 grid oinstall 152462814 Mar 15 14:00 / u01/11.2.0/grid/bin/oracle
[root@node1 ~] #
-at this point, the problem is solved, and Oracle users can access ASM diskgroup normally!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.