Tablespace read only fails

Hi,
10gR2 on Solaris10
There is a data  tablespace  that resists turning it into read only tablespace.
How to find what session is holding locks on objects within that tablespace?
Thx,

There are some attempt here:
select bl.INST_ID, bl.sid, bl.TYPE, bl.LMODE,bl.REQUEST,s.USERNAME
from GV$GLOBAL_BLOCKED_LOCKS bl, gv$session s
where bl.INST_ID=s.INST_ID and bl.SID=s.sid;
INST_ID   SID TY      LMODE    REQUEST USERNAME
         3   186 PS          4          6 USERWEB1
         3   376 PS          4          0 USERWEB1
select o.name object_name, u.name owner, lid.*
  from (select
  2    3                 s.inst_id, s.sid, s.serial#, p.spid,nvl (s.sql_id, 0), s.sql_hash_value,
  4                 decode (l.type,
  5                         'tm', l.id1,
  6                         'tx', decode (l.request,
  7                                       0, nvl (lo.object_id, -1),
  8                                       s.row_wait_obj#
                       -1
  9   10   11                        ) as object_id,
12                   l.type lock_type,
13                 DECODE (l.lmode,
14                         0, 'NONE',
15                         1, 'NULL',
16                         2, 'ROW SHARE',
                       3, 'ROW EXCLUSIVE',
17   18                         4, 'SHARE',
19                         5, 'SHARE ROW EXCLUSIVE',
20                         6, 'EXCLUSIVE',
21   22                        ) mode_held,
               DECODE (l.request,
23   24                         0, 'NONE',
25                         1, 'NULL',
26                         2, 'ROW SHARE',
27                         3, 'ROW EXCLUSIVE',
28                         4, 'SHARE',
29                         5, 'SHARE ROW EXCLUSIVE',
30                         6, 'EXCLUSIVE',
31                         '?'
32                        ) mode_requested,
33                 l.id1, l.id2, l.ctime time_in_mode,s.row_wait_obj#, s.row_wait_block#,
34                 s.row_wait_row#, s.row_wait_file#
35            from gv$lock l,
36                 gv$session s,
37                 gv$process p,
38                 (select object_id, session_id, xidsqn
39                    from gv$locked_object
40                   where xidsqn > 0) lo
41           where l.inst_id = s.inst_id
           and s.inst_id = p.inst_id
42   43             and s.sid = l.sid
44             and p.addr = s.paddr
45             and l.sid = lo.session_id(+)
46             and l.id2 = lo.xidsqn(+)) lid,
47         SYS.obj$ o,
       SYS.user$ u
48   49   WHERE o.obj#(+) = lid.object_id
50   AND o.owner# = u.user#(+)
51   AND object_id <> -1;
no rows selected
SELECT username U_NAME, owner OBJ_OWNER,
  2  object_name, object_type, s.osuser,
  3  DECODE(l.block,
  4    0, 'Not Blocking',
  1, 'Blocking',
  5    6    2, 'Global') STATUS,
  7    DECODE(v.locked_mode,
  8      0, 'None',
  9      1, 'Null',
10      2, 'Row-S (SS)',
11      3, 'Row-X (SX)',
12      4, 'Share',
13      5, 'S/Row-X (SSX)',
14      6, 'Exclusive', TO_CHAR(lmode)
15    ) MODE_HELD
16  FROM gv$locked_object v, dba_objects d,
gv$lock l, gv$session s
17   18  WHERE v.object_id = d.object_id
19  AND (v.object_id = l.id1)
20  AND v.session_id = s.sid
21  ORDER BY username, session_id;
no related users or tables
SELECT SUBSTR(TO_CHAR(w.session_id),1,5) WSID, p1.spid WPID,
SUBSTR(s1.username,1,12) "WAITING User",
  2    3  SUBSTR(s1.osuser,1,8) "OS User",
  4  SUBSTR(s1.program,1,20) "WAITING Program",
  5  s1.client_info "WAITING Client",
  6  SUBSTR(TO_CHAR(h.session_id),1,5) HSID, p2.spid HPID,
  7  SUBSTR(s2.username,1,12) "HOLDING User",
  8  SUBSTR(s2.osuser,1,8) "OS User",
  9  SUBSTR(s2.program,1,20) "HOLDING Program",
10  s2.client_info "HOLDING Client",
11  o.object_name "HOLDING Object"
12  FROM gv$process p1, gv$process p2, gv$session s1,
13  gv$session s2, dba_locks w, dba_locks h, dba_objects o
14  WHERE w.last_convert > 60
15  AND h.mode_held != 'None'
16  AND h.mode_held != 'Null'
17  AND w.mode_requested != 'None'
18  AND s1.row_wait_obj# = o.object_id
19  AND w.lock_type(+) = h.lock_type
20  AND w.lock_id1(+) = h.lock_id1
21  AND w.lock_id2 = h.lock_id2
22  AND w.session_id = s1.sid
23  AND h.session_id = s2.sid
24  AND s1.paddr = p1.addr
25  AND s2.paddr = p2.addr
26  ORDER BY w.last_convert DESC;
no related objects

Similar Messages

  • Unable to Make tablespace Read Only in 10g

    Hi All,
    I am using Oracle database 10g R2 (10.2.0.3) on AIX 5.3 platform. Our database is using ASM based storage.
    I am trying to make a tablespace read only but its not returning the command once I execute that.
    I have checked the sessions status and confirmed that no user is writing/reading the tablespace. The tablespace is having 150GB size and having only one table in it.
    I had given following command using sys user.
    alter tablespace SMS_DATA read only;
    However this command was kept running for three hours before I kill that. I have tried to take another tablespace off-line and have face same situation.
    Can any one tell me why this simple task is unable to complete.
    PS: My database is working fine and user are running queries and getting results in desired time.
    Regards
    Farooq

    Hi,
    I have diagnosed the problem by running v$transaction commands and found that one transaction is running since morning.
    FKHALID>SELECT SES_ADDR, START_SCNB,START_TIME FROM V$TRANSACTION ORDER BY START_SCNB;
    SES_ADDR START_SCNB START_TIME
    07000004C63E69E0 515936552 09/01/09 08:41:16
    07000004C937FB20 590533316 09/01/09 20:16:02
    07000004C639E360 590777564 09/01/09 20:20:42
    07000004C5346740 590860241 09/01/09 20:22:41
    07000004D23B86E8 590863096 09/01/09 20:22:46
    FKHALID@PAKEDWP>SELECT SQL_TEXT, SADDR FROM V$SQLAREA,V$SESSION WHERE V$SQLAREA.ADDRESS = V$SESSION.SQL_ADDRESS AND SQL_TEXT LIKE 'alter tablespace%';
    SQL_TEXT SADDR
    alter tablespace SMS_DATA read only 07000004C937FB20
    this shows that sess_addr (07000004C63E69E0) is creating the problem as my command is waiting for completion of this command.
    Now I have joined the view with v$session and have found the sid.
    SELECT a.sid,a.serial#, a.username, b.xidusn, b.used_urec, b.used_ublk ,b.ses_addr FROM v$session a, v$transaction b WHERE a.saddr = b.ses_addr;
    After killing that process, I was able to change the status of tablespace successfully.
    Thanks for your prompt response.
    Regards
    Farooq
    Edited by: Fkhalid on Sep 1, 2009 7:34 PM
    Edited by: Fkhalid on Sep 1, 2009 7:44 PM

  • To make tablespace read only

    if i want to make a tablespace read only. should there be no active transaction on that tablespace or datebase.
    null

    Hi,
    I have diagnosed the problem by running v$transaction commands and found that one transaction is running since morning.
    FKHALID>SELECT SES_ADDR, START_SCNB,START_TIME FROM V$TRANSACTION ORDER BY START_SCNB;
    SES_ADDR START_SCNB START_TIME
    07000004C63E69E0 515936552 09/01/09 08:41:16
    07000004C937FB20 590533316 09/01/09 20:16:02
    07000004C639E360 590777564 09/01/09 20:20:42
    07000004C5346740 590860241 09/01/09 20:22:41
    07000004D23B86E8 590863096 09/01/09 20:22:46
    FKHALID@PAKEDWP>SELECT SQL_TEXT, SADDR FROM V$SQLAREA,V$SESSION WHERE V$SQLAREA.ADDRESS = V$SESSION.SQL_ADDRESS AND SQL_TEXT LIKE 'alter tablespace%';
    SQL_TEXT SADDR
    alter tablespace SMS_DATA read only 07000004C937FB20
    this shows that sess_addr (07000004C63E69E0) is creating the problem as my command is waiting for completion of this command.
    Now I have joined the view with v$session and have found the sid.
    SELECT a.sid,a.serial#, a.username, b.xidusn, b.used_urec, b.used_ublk ,b.ses_addr FROM v$session a, v$transaction b WHERE a.saddr = b.ses_addr;
    After killing that process, I was able to change the status of tablespace successfully.
    Thanks for your prompt response.
    Regards
    Farooq
    Edited by: Fkhalid on Sep 1, 2009 7:34 PM
    Edited by: Fkhalid on Sep 1, 2009 7:44 PM

  • Can I make a LOB segment tablespace 'READ ONLY' so no backup?

    Greetings
    Environment: Oracle 11.2.0.3 on Solaris 10.5
    LOB newbie here.
    I am currently supporting a database, but not the application, that is loading fairly large XML files into CLOB columns. Today I have 121 LOBSEGMENTs taking up about 1GB of space and in the same tablespace as the owner table.
    I understand that the CLOB data will not be changing that often.
    My issue is now my RMAN backup is much larger and is filling the mount point where the backup files are stored.
    I'd like to move the LOBSEGMENT objects to a different tablespace, back it up once and mark the tablespace as READ ONLY so it doesn't get backed up every time.
    I am currently doing a full database backup every day and archivelog backups every 4 hours.
    Can I use something like: ALTER TABLE 'X' MOVE LOB 'Y' STORE AS TABLESPACE 'Z' ?
    Is it then possible to alter the 'Z' tablespace to READ ONLY and not affect the user's ability to update the other parts of the table?
    Other alternatives are most welcome!!
    Thanks very much!!
    -gary

    Thanks for the quick response.
    I don't want you to give up, I'd just like some advice from your experience.
    Even though I am working in a test environment I was hesitant to execute the above commands so as not to cause the application to fail as the user is loading the XML data.
    I want the tablespace storing the LOBSEGMENTs to be READ ONLY but I wasn't sure if I could specify just the LOBSEGMENT part of a row to be READ ONLY without causing update problems for the other columns in the table.
    I realize the new LOBSEGMENT tablespace will be READ ONLY and the original tablespace with the rest of the data will remain READ WRITE.
    Also, I'm assuming if the CLOB data ever needs to change I should be able to alter the tablespace back to READ WRITE, have the user make the changes, be sure the new data is backed up and alter the tablespace back to READ ONLY.
    Is this how you would handle the situation?
    Thanks very much!
    -gary

  • Is there any performance value to making a tablespace READ ONLY?

    In 9i, if I were to set a tablespace which only contains data to be reported over - is there any value in making it READ ONLY other than "safety" of the data? I am particularly interested to know if it can increase performance.
    Thanks

    When you say safety, you are partly correct, because data cannot be deleted, but it can be dropped, check the below SQL statements.
    With regard to performance, yes you will gain some. For better performance while accessing data in a read-only tablespace, you can issue a query that accesses all of the blocks of the tables in the tablespace just before making it read-only. A simple query, such as SELECT COUNT (*), executed against each table ensures that the data blocks in the tablespace can be subsequently accessed most efficiently. This eliminates the need for Oracle to check the status of the transactions that most recently modified the blocks.
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96521/tspaces.htm#922
    SYS@BABU> create tablespace test_ts datafile 'D:\ORACLE\ORADATA\TEST_TS1.DAT' SIZE 15M
      2  EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
    Tablespace created.
    SYS@BABU> CREATE TABLE TAB1 (A NUMBER) tablespace test_ts ;
    Table created.
    SYS@BABU> BEGIN
      2  FOR A IN 1..10 LOOP
      3  INSERT INTO TAB1 VALUES (A);
      4  END LOOP;
      5  COMMIT;
      6  END;
      7  /
    PL/SQL procedure successfully completed.
    SYS@BABU> ALTER TABLESPACE test_ts READ ONLY;
    Tablespace altered.
    SYS@BABU> DELETE FROM TAB1;
    DELETE FROM TAB1
    ERROR at line 1:
    ORA-00372: file 6 cannot be modified at this time
    ORA-01110: data file 6: 'D:\ORACLE\ORADATA\TEST_TS1.DAT'
    SYS@BABU> truncate table TAB1;
    truncate table TAB1
    ERROR at line 1:
    ORA-00372: file 6 cannot be modified at this time
    ORA-01110: data file 6: 'D:\ORACLE\ORADATA\TEST_TS1.DAT'
    SYS@BABU> DROP TABLE TAB1 ;
    Table dropped.

  • How long should it take to make a Tablespace READ-ONLY

    Hi,
    We have a Tablespace which occupies 300MBs
    It is taking in excess of 30mins to make it Read Only.
    What would cause this delay?
    We are on 9.2.0.4
    Thanks

    Ask yourself the following questions
    Is any user assigned the target tablespace for their default or temporary tablespace?
    How many transactions are currently running against objects in the target tablespace?
    How many dirty buffers exist for objects that are assigned to the target tablespace?
    The answer to each of the above questions should be none in which case the tablespace alteration should take only a few seconds.
    HTH -- Mark D Powell --

  • ORA-00060: deadlock detected while waiting for resource with Tbs Read-only

    Hi all,
    We're using Oracle 10.2.0.1 and 9.2.0.4.
    I'm testing the performing of a procedure that inserts, like this:
    CREATE OR REPLACE PROCEDURE P$TAD_TEST
    IS
    TYPE T_T1_C1          IS TABLE OF T1.C1%TYPE INDEX BY PLS_INTEGER;
    TYPE T_T1_DT           IS TABLE OF T1.DT%TYPE INDEX BY PLS_INTEGER;
    P_C1 T_T1_C1;
    P_DT T_T1_DT;
    P_RESULT NUMBER;
    BEGIN
    FOR j IN 1..4032 LOOP
    P_C1(j) := j;
    P_DT(j) := SYSDATE + (j/24/60);
    END LOOP;
    FORALL i IN P_C1.FIRST..P_C1.LAST SAVE EXCEPTIONS
    INSERT INTO T1 VALUES (P_C1(i), P_DT(i));
    EXCEPTION
    WHEN OTHERS THEN
    P_RESULT := SQLCODE;
    END;
    The table T1 is partitioned across 10 tablespaces. The test consist to take
    these tablespace read-only and perform the procedure, and analyze the results,
    like erros.
    but when I perform the procedure, The alert.log indicates the error
    ORA-00060: deadlock detected while waiting for resource.
    Why this occurs only the tablespaces are read-only?
    thank you!!!!

    Hi,
    yesterday we got this error again(in fact twice) and we were able to get the trace file. It says this is NOT oracle error. i was wrong in suspecting Oracle. This is the trace file details. i dont know how to debug this. Any help appreciated.
    *** 2010-06-15 16:24:29.243
    *** ACTION NAME:() 2010-06-15 16:24:29.231
    *** MODULE NAME:(JDBC Thin Client) 2010-06-15 16:24:29.231
    *** SERVICE NAME: 2010-06-15 16:24:29.231
    *** SESSION ID:(482.4266) 2010-06-15 16:24:29.231
    DEADLOCK DETECTED ( ORA-00060 )
    [Transaction Deadlock]
    The following deadlock is not an ORACLE error. It is a
    deadlock due to user error in the design of an application
    or from issuing incorrect ad-hoc SQL. The following
    information may aid in determining the deadlock:
    Deadlock graph:
    ---------Blocker(s)-------- ---------Waiter(s)---------
    Resource Name process session holds waits process session holds waits
    TX-00300021-0000b52d 209 482 X 247 474 S
    TX-002a0009-00011b24 247 474 X 209 482 S
    session 482: DID 0001-00D1-0000000A session 474: DID 0001-00F7-00000008
    session 474: DID 0001-00F7-00000008 session 482: DID 0001-00D1-0000000A
    Rows waited on:
    Session 474: obj - rowid = 0000CED4 - AAAM7UAAxAAAVgSAAA
    (dictionary objn - 52948, file - 49, block - 88082, slot - 0)
    Session 482: obj - rowid = 0000D8BF - AAANi/AAuAAB+z/AAA
    (dictionary objn - 55487, file - 46, block - 519423, slot - 0)
    Information on the OTHER waiting sessions:
    Session 474:
    pid=247 serial=31796 audsid=25502259 user: 62/USER
    O/S info: ....
    program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
    Current SQL Statement:
    INSERT QUERY1
    End of information on OTHER waiting sessions.
    Current SQL statement for this session:
    INSERT QUERY2
    Thanks,
    AK

  • Are 'read only' items causing my automatic row processing to fail?

    I have a form that uses automatic row processing to update my table.
    I recently had to add a check to lock down the fields using the read only condition where a record has been 'approved'. So, I turned off all of the fields and hid the update button.
    Now they want me to check to see if the user is a manager, and if so, allow them to see the update button, and make a single field on the form modifiable.
    I have the user identified as a manager, and can make the field accept the change (a yes/no combo box). Yet when they click the update button, the form just sits there. A branch is supposed to fire on hitting that button, taking them back to the previous report, but it doesn't happen. The source of the combo box in question uses a column on the table, and works fine when the form has all of the fields showing for modification.
    I had some validations that I finally set to never fire, thinking that they were failing and just not giving the error messages. I know a bad sql or pl/sql atatement in a validation will cause the form to just keep sitting there doing nothing, and thought it might help.
    Several of the various fields are combo boxes, several are text boxes.
    I'm stumped.
    Shall I keep the regular update button hidden whether it is a manager or not (because it has been 'approved'), and enable a new button that fires off a process to update the one field that the manager may want to change? Does making a field 'read only' always have a detrimental effect on the auto processes I've been counting on? Is that if fact what is happening now?
    Thanks in advance for any advice or comments on this.
    Clayton

    Hi, Scott.
    My version is 3.0.0.00.20
    I have received info to set up the application, though I have not activated it as yet. I'm reluctant to try to load up the various tables to make it work. It could be done.
    My workaround is to that the user (a manager) fires off to another form to show an individual record, and ask if he/she really wants to make this change. On submit, they will be taken back to the original locked down form, and I will update the single field in that process of returning them. This will actually be a plus, in that I expect to show them all of the 'duplicate' entries for that item, and show them that by 'activating' this particular item, they will 'deactivate' the one duplicate that is currently active. Or, if they are deactivating the sole item that is active, that there will in fact be no active items in the system. Convoluted as heck, but they swear this is how they've been doing business with their briefcases and file cabinets of Excel files. I'm surprise they even float at this point (these are ships we're talking about).
    This all may be due to the form originally having a next/previous/count process once arrived at my clicking on the edit button of the report of items. All of that has been hidden away, and though the fields exist of the form, they are not used. They only see the current item that they clicked on from the report.
    I read up a little on session state, as well as posts with the debug error I was getting. I'm still not on board with the whole issue of 'state'. Items stay as they are until they're changed, no? I suppose that sounds simplistic.
    One of the things that caught my eye was several combo box lists that on read only mode, showed [] square brackets. Which, in some cases is okay.
    What I'll try to do is set up a public application - for future use if nothing else. I'm going to be working on this for awhile. I have more than a bit of work to do to cleanse the data as well as get rid of the single sign on requirement (I'll assume that I should have to do this) in order to share the app.
    I know you're expecting me to have this up and running for you to look at, but I'm under the gun. And they actually like my workaround.
    I'll keep everybody informed, one way or another.
    Clayton

  • Read Only access to tablespace

    Hi,
    Oracle 10.2.0.4
    How can I grant read only access to a tablespace for a user.
    Thanks

    It is no ussual.... a tablespace is a box where one or more user store his data... sure you do not want to say user and not tablespace?
    Grant select to the objects of this tablespace...DBA_TABLES or ALL_TABLES...
    Select 'GRANT SELECT ON ' || OWNER || '.' || TABLE_NAME || ' TO <USERNAME> ' FROM DBA_TABLES WHERE TABLESPACE_NAME = <TABLESPACE>

  • Pacstrap failed. Now I have a read-only filesystem that is unusable

    Hello,
    I have been using Linux for the past few years (primarily Ubuntu and Fedora), and have used the command line a lot.
    I was just following the instructions on the Beginners guide. I set up wifi, and partitioned the disk using gdisk (all my computers since late 2009 have not used MBR). I then set up my mirrorlist (left the first one, and added my university as second).
    When I ran pacstrap (without -i), it started downloading everything. I think it finished most of it. The kernel had been downloaded, and the filesystem supposedly set up. Then, I got an error. (I am not sure where it was, and I wasn't logging the output. There were many many lines of:
    [timestamp] EXT4-fs (sda1): ext4_da_writepages: jpd2_start:8192 pages, ino xxxxxxx; err -30
    Then:
    [timestamp] EXT4-fs error (device sda1): ext4_journal_start_sb:370: [timestamp] EXT4-fs error (device sda1): ext4_journal_start_sb:370: [timestamp] EXT4-fs error (device sda1): Remounting filesystem read-only
    error: command failed to execute correctly
    error: could not create directory /mnt/var/lib/pacman/local/groff-1.21-2/: Read-only file system
    error: could not commit transaction
    error: failed to commit transaction (transaction aborted)
    Errors occured, no packages were upgraded.
    warning: could not remove lock file /mnt/var/lib/pacman/db.lck
    ==> ERROR: Failed to install packages to new root
    pacstrap /mnt base base-devel 35.27s user 6.19s system 3% cpu 17:34.81 total
    Trying to rerun pacstrap gets me an error that the lockfile still exists. I cannot remove it because it is a "read-only filesystem". Its permissions are 000, and the folder it is in (pacman) has 755.
    I also cannot make an fstab or continue with the installation.
    I tried to run the setup again, and it kept failing. (MBR failed too, with the same error.)
    What do you think caused it, and what could I do to resolve it. I couldn't find anything like that in the forums, or on google.
    Last edited by masasin (2012-10-27 03:18:37)

    Are the ext4 errors not a dead giveaway that the FS (or physical disk) are misbehaving? It's remounted itself read-only to prevent further damage.

  • Time Machine backup fails w/error: Backup Volume is Read Only

    This is another Leopard Bug! My Time Machine has always "just worked," but tonight, backup failed. Looking at the error message, it says, "Backup Volume is Read Only." My Time Machine was set up correctly, and has been working fine for quite some time. Now what?

    Update: The next scheduled backup succeeded. I didn't change anything. Doesn't exactly give you that feeling of confidence in your equipment. The whole point of Time Machine is it is supposed to work in the background. If I have to think about it, and check up on it, it is useless, and I may as well return to my old manual backup methods.

  • Read Only Tablespace Backup Issue

    Hii!!
    I had been trying to to take Read Only Table space Backup. So, firstly changed the tablespace using
    SQL> alter tablespace users read only;
    Tablespace altered.
    2. Then took backup of all the data files using OS Copy command.
    Now , the issue i am facing is that can i change the table space to read_write mode???? If yes , then how?? , plz help...

    I had been trying to to take Read Only Table space Backup. So, firstly changed the tablespace using
    SQL> alter tablespace users read only;
    Tablespace altered.
    2. Then took backup of all the data files using OS Copy command.
    Now , the issue i am facing is that can i change the table space to read_write mode???? If yes , then how?? , plz help...Yes you can do,
    SQL> alter tablespace users read write;After successful restore,
    sys@11GDEMO> select tablespace_name,status from dba_tablespaces where tablespace_name='CKPT';
    TABLESPACE_NAME                STATUS
    CKPT                           ONLINE
    sys@11GDEMO> alter tablespace ckpt read only;
    Tablespace altered.
    sys@11GDEMO> select tablespace_name,status from dba_tablespaces where tablespace_name='CKPT';
    TABLESPACE_NAME                STATUS
    CKPT                           READ ONLY+
    sys@11GDEMO> alter tablespace ckpt read write;+
    Tablespace altered.
    sys@11GDEMO> select tablespace_name,status from dba_tablespaces where tablespace_name='CKPT';
    TABLESPACE_NAME                STATUS
    CKPT                           ONLINE+
    sys@11GDEMO>
    Edited by: CKPT on Jul 6, 2011 11:22 AM

  • Installing Yosemite failed, and it turned my disc into "read only"

    Tried to upgrade my MacBook Pro (Early 2011) to 10.10 from 10.9.5 AppStore. It failed after reboot. Then the disaster began...
    (Yes, unfortunately I didn't backup...)
    My disc became "Read only":
    I couldn't install 10.10, neither reinstall 10.9.5.
    Tried to repair the disc and permissions with 10.10 Disk Utility, both failed.
    Tried Disk Utility in 10.9.5 recovery, it says "unable to mount the disc".
    Tried to use Disk Utility "Restore", to copy the entire volume to another disc, it gave me "Could not restore - Input/output error",
    Tried to create a new image from that disc, still Input/output error.
    Then I used a new disc, clean installed Yosemite on it. However, I couldn't migrate my data from the old disc. In Migration Assistant, it couldn't find any source. (Tried to connect to another disc with clean installed Yosemite, Migration Assistant could find it)
    When I tried to simply copy "all files" (including all hidden files) to another empty disc, I always ended up with "The operation can’t be completed because you don’t have permission to access “some file”." ("some file" changes every time).
    Thai disc had been working for over one year without any problem, until I hit "Upgrade to Yosemite"...
    It's been a week now, and I have no idea what else I can try to repair my disc / make it writable again / migrate system information from that disc... Please help!

    First, look at this article and see if your model can do an Internet Recovery: Computers that can be upgraded to use OS X Internet Recovery. If yours needs the firmware update, then do that  before moving on.
    Install Mavericks, Lion/Mountain Lion Using Internet Recovery
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Internet Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
    Partition and Format the hard drive:
    Select Disk Utility from the main menu and click on the Continue button.
    After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion. Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Install button. Be sure to select the correct drive to use if you have more than one.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    This should restore the version of OS X originally pre-installed on the computer.
    If for some reason your hard drive cannot be repartitioned or is not even visible in Disk Utility, then the drive has failed and needs to be replaced.

  • Backing up database with read-only tablespaces

    I am trying to develop a script that will dynamically build RMAN scripts for backing up
    a database with read-only tablespaces. The application running on this database creates
    new tablespaces in read-write mode on weekly basis, populates them, and then puts them in read-only mode. So I need to backup all read-write tablespaces plus take backup of all read-only tablespaces once. The problem is that the application also includes a process that puts a tablespace back into read-write mode, updates it, and puts it back into read-write mode. So I need to be able to access "a history" of the tablespace - when was it put into read-only mode - to compare it with a history of backups. While history of backups is available in RMAN views, I couldn't find any way to extract tablspaces
    history.
    There should be RMAN command to the effect
    "backup all read-write tablespaces and read-only tablespaces if they have not been backed up at least once since becoming read-only".
    Regards,
    Sev
    null

    just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
    1) make new dataset with compression
    2) enable shadow migration between the new and old
    3) change the database to use the new location
    4) watch as data is automatically copied and compressed :-)
    the the down side, you need extra space to pull the off.

  • Which table shows the tablespace in read-only mode or read-write mode.

    HI All,
    Can someonoe help me out to find which table shows whether the a tablespace is in Read-only mode or Read-write.
    Thanks,
    naveen

    Try this:
    select tbl.table_name, tb.tablespace_name, TB.STATUS from dba_tablespaces tb, dba_tables tbl
    where TB.TABLESPACE_NAME = tbl.TABLESPACE_NAME and TB.TABLESPACE_NAME = 'YOUR_TABLESPACE_NAME' and tbl.table_name = 'TABLE_NAME'

Maybe you are looking for