- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: EVA problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 04:27 AM
тАО03-08-2010 04:27 AM
EVA problem
I have done this
Create TEST1 database on one host and present to that database 3 storage disks, and also i have created replication group on for second EVA storage on second location and also i have created ORACLE HOME on second server for this kind of standby.
Then i have ended replication and unpresent storage disks on first EVA and present those disks to second EVA and tried to mount those disks to second TEST2 databas, but i have experineced this error after doing
@/db/db_create_controlfile.sql
ORACLE instance started.
Total System Global Area 236000320 bytes
Fixed Size 451648 bytes
Variable Size 201326592 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
Control file created.
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 236000320 bytes
Fixed Size 451648 bytes
Variable Size 201326592 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00344: unable to re-create online log '/a06ef2/db/redo01/redo01.log'
ORA-27041: unable to open file
Linux Error: 30: Read-only file system
Additional information: 4
When i went on that location to see what is problem i have permission as oracle user for that replicated disk BUT i cannot do chmod 755 for oracle user because i receive that this disk is read only, as others also??
Why i receive this errrors?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 04:40 AM
тАО03-08-2010 04:40 AM
Re: EVA problem
When you create a DR Group, the destination vdisk can be presented to hosts, but not with write access.
If you pause the replication, this is still the situation. If you delete the DR Group, keeping the destinationn vdisk, then it becomes a regular vdisk and you can write to it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 11:45 PM
тАО03-09-2010 11:45 PM
Re: EVA problem
To clarify:
On first server i have created database and put those data files on those filesystems, then we use replicated group from other EVA to mount on second server and after doing so owner of those disks were USER1 instead oracle as on original disks, and then guys have put Oracle as owner, but when we try to do chmod 755 we received Read only message for those replicated disks....
How to solve this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 11:57 PM
тАО03-09-2010 11:57 PM
Re: EVA problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2010 12:41 AM
тАО03-10-2010 12:41 AM
Re: EVA problem
As I told you above it's not the same to suspend the replication than to delete the DR group.
As long as the destination vdisk is part of a DR Group, it's read only.
Delete the DR group, leaving it as a regular vdisk, or perform a fail over and then destination vdisk will become source and it will be writable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2010 01:03 AM
тАО03-10-2010 01:03 AM
Re: EVA problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2010 01:08 AM
тАО03-10-2010 01:08 AM
Re: EVA problem
after you have deleted the DR_Group, the destination virtual disk becomes readonly - I've seen it myself.
Why not go into CV-EVA and switch the vdisk to read-write mode?
It is on the [Presentation] tab.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2010 01:15 AM
тАО03-10-2010 01:15 AM
Re: EVA problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2010 02:46 AM
тАО03-10-2010 02:46 AM