MS Access database opens read only

An Access application with linked databases opens read only, but sometimes is editable. The system was developed in Access 10 on a Win 7 machine and migrated to a standalone laptop running Win 8 and Office 365.
The Access 10 has no problem in operating the application. The Win 8 laptop randomly opens the application read only. I have reviewed Trust settings and there is no difference between the different laptops and systems. 
Is this a common problem? Is it associated with Win 8? Is it associated with Access form Office 365? The application is crucial to the business and we are getting way behind because we don't have a reliable or useful system. Last year the same application
ran satisfactorily on Win 7 and Access 10.
I would welcome some thoughts leading too a solution.

Hi,
Did you get the error message like "You are trying to open a read-only database". If yes, this issue may be due to the permission of the Access database. If we migrate the Access database from Access 2010 to Access 2013, the user/account's permission
may be changed with different Windows operation system. We need the full control permission of the Access database. To workaround this issue, follow these steps:     
On the desktop, double-click My Computer.
Locate the Microsoft Access database that you moved.
Right-click the database name, and then click Properties.
In the Properties dialog box, clear the Read-only check box under
Attributes.
Click OK to apply the change.
Open your database in Access.
Please note: Make sure the user has full control of the root folder.
If no, please tell us the whole error message, we'd like to do further troubleshooting.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Similar Messages

  • Standby database errors - Alter database open read only

    alter database open read only
    AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
    Signalling error 1152 for datafile 1!
    Beginning standby crash recovery.
    Serial Media Recovery started
    Managed Standby Recovery starting Real Time Apply
    Media Recovery Waiting for thread 1 sequence 216
    Mon Dec 20 11:58:18 2010
    Standby crash recovery need archive log for thread 1 sequence 216 to continue.
    Please verify that primary database is transporting redo logs to the standby database.
    Wait timeout: thread 1 sequence 216
    Standby crash recovery aborted due to error 16016.
    Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
    ORA-16016: archived log for thread 1 sequence# 216 unavailable
    Recovery interrupted!
    Completed standby crash recovery.
    Signalling error 1152 for datafile 1!
    Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
    ORA-10458 signalled during: alter database open read only...
    Mon Dec 20 12:13:46 2010
    ALTER DATABASE RECOVER managed standby database using current logfile disconnect
    Attempt to start background Managed Standby Recovery process (MDM2)
    Mon Dec 20 12:13:46 2010
    MRP0 started with pid=23, OS id=18974
    MRP0: Background Managed Standby Recovery process started (MDM2)
    started logmerger process
    Mon Dec 20 12:13:51 2010
    Managed Standby Recovery starting Real Time Apply
    Parallel Media Recovery started with 2 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 216
    Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
    The above lines are from alert log of standby database.
    Standby standbase
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
    Parameters set on primary are
    log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
    log_archive_dest_state_1 ENABLE
    log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
    log_archive_dest_state_2 ENABLE
    dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
    dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
    fal_server MDM2
    standby_file_management AUTO
    log_archive_config dg_config=(MDM1,MDM2)
    db_file_name_convert MDM2, MDM1
    ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
    Standby pfile
    *.archive_lag_target=900
    *.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='+MDMDG1'
    *.db_domain=''
    *.db_file_name_convert='MDM1','MDM2'
    *.db_name='MDM'
    *.db_recovery_file_dest='+MDMDG2'
    *.db_recovery_file_dest_size=10485760000
    *.db_unique_name='MDM2'
    *.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
    *.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
    *.fal_server='MDM11','MDM12'
    *.instance_name='MDM2'
    *.log_archive_config='dg_config=(MDM1,MDM2)'
    *.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
    *.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='MDM_%t_%s_%r.arc'
    *.log_file_name_convert='MDM1','MDM2'
    *.memory_target=838860800
    *.nls_language='ENGLISH'
    *.nls_territory='UNITED KINGDOM'
    *.open_cursors=300
    *.processes=500
    *.remote_login_passwordfile='exclusive'
    *.sessions=555
    *.standby_file_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    On standby ASM
    ASMCMD [+] > find * *
    +MDMDG1/ASM/
    +MDMDG1/ASM/ASMPARAMETERFILE/
    +MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
    +MDMDG1/MDM/
    +MDMDG1/MDM2/
    +MDMDG1/MDM2/CONTROLFILE/
    +MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
    +MDMDG1/MDM2/CONTROLFILE/current.265.738243333
    +MDMDG1/MDM2/DATAFILE/
    +MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
    +MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
    +MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
    +MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
    +MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
    +MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
    +MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
    +MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
    +MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
    +MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
    +MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
    +MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
    +MDMDG1/MDM2/DATAFILE/USERS.278.738243347
    +MDMDG1/MDM2/ONLINELOG/
    +MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
    +MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
    +MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
    +MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
    +MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
    +MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
    +MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
    +MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
    +MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
    +MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
    +MDMDG2/MDM/
    +MDMDG2/MDM/DG_CONFIG/
    +MDMDG2/MDM2/
    +MDMDG2/MDM2/AUTOBACKUP/
    +MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
    +MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
    +MDMDG2/MDM2/CONTROLFILE/
    +MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
    +MDMDG2/MDM2/CONTROLFILE/current.271.738243335
    +MDMDG2/MDM2/ONLINELOG/
    +MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
    +MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
    +MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
    +MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
    +MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
    +MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
    +MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
    +MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
    +MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
    +MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
    +MDMDG3/MDM/
    +MDMDG3/MDM/ARCH/
    +MDMDG3/MDM2/
    +MDMDG3/MDM2/ARCH/
    -- Please can I know how to open read only standby database.

    user5846399 wrote:
    ORA-16016: archived log for thread 1 sequence# 216 unavailable
    Recovery interrupted!archived log for thread 1 sequence# 216
    This file is needed for recovery, Find it and move it to the standby database side.

  • Startup command starts database but alter database open read only gives error

    Hi,
    I'm having some strange behavior. I've 10.2.0.3 database on windows 2003.
    The startup command starts database without any issues.
    But if I try following it gives error.
    startup mount (successful no errors)
    alter database open read only; gives error that file Mnnnnnn is missing.
    Why this is happening and how to fix it?
    Thanks.

    You really need to show us exactly what Oracle is telling you, using copy and paste, so we can have some clue.  You can hide details like instance and host names if they show up.
    I'm wondering if you had some messed up offline datafile in a tablespace, where Oracle handles it with startup, but gets upset when you try to open read-only.  It's some bizarro sequence of events like: add a datafile to a tablespace, decide that was a mistake, alter it offline, then remove it from the OS without telling Oracle any more about it.  I've come back from vacation to find scenarios like this, it winds up being a time-bomb trying to recreate a standby later.  Or something like that, I could be unremembering some details.

  • Database open read only

    Does the alert<sid>.log always show a warning message as such when a standby database is put into read only mode?
    ***Warning - Executing transaction without active Undo Tablespace

    Hi,
    It's a bug happen to 9i
    Bug 3270493:EXCESSIVE QMNX TRACE FILES WHEN PLACING STANDBY IN READ ONLY MODE
    This does not reproduce in 10g. It looks like there were some modifications made to kwqitnfy to check whether the database is in read-write mode before starting the QMNC process.
    The workaround is to set aq_tm_processes=0 when using the database in read-only mode for the long-term. This can be done with a simple alter system command:
    ALTER SYSTEM SET aq_tm_processes=0;
    By running the above command, the errors would stop and therefore so would the trace files.
    Note: Use spfile is applied in order to ensure aq_tm_processes will be zero after restart.
    Mike

  • Error during open standby database in read only mode

    hi,
    alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u02/app/oracle/oradata/standby/system01.dbf'
    Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
    what is the reason of this.
    Thanks in advance.

    thanks for your reply.
    [oracle@standby admin]$ cat listener.ora
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
    LISTENER_STANDBY =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME =/opt/app/oracle/product/11.2.0/db_1)
    (PROGRAM = extproc)
    tnsfile
    [oracle@standby admin]$ cat tnsnames.ora
    standby =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.124)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = standby)
    ora11g =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.120)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ora11g)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.120)(PORT = 1521))
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    pfile
    [oracle@standby standby]$ cat initstandby.ora
    ora11g.__db_cache_size=130023424
    ora11g.__java_pool_size=4194304
    ora11g.__large_pool_size=4194304
    ora11g.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    ora11g.__pga_aggregate_target=146800640
    ora11g.__sga_target=276824064
    ora11g.__shared_io_pool_size=0
    ora11g.__shared_pool_size=121634816
    ora11g.__streams_pool_size=8388608
    *.audit_file_dest='/u01/app/oracle/admin/ora11g/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.1.0'
    #*.control_files='/u02/app/ora11g/oradata/ora11g/control01.ctl','/u01/app/oracle/flash_recovery_area/ora11g/control02.ctl'
    *.db_block_size=8192
    *.db_domain=''
    *.db_name='ora11g'
    *.db_recovery_file_dest='/opt/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=4039114752
    *.diagnostic_dest='/opt/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=ora11g)'
    *.memory_target=2016M
    *.open_cursors=300
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.undo_tablespace='UNDOTBS1'
    *.audit_file_dest='/opt/app/oracle/admin/standby/adump'
    *.audit_trail=none
    #*.background_dump_dest='/opt/app/oracle/admin/standby/bdump'
    #*.compatible='10.2.0.2.0'
    #*.control_files='/opt/app/oracle/oradata/standby/control01.ctl'
    #,'/opt/app/oracle/oradata/standby/control02.ctl','/opt/app/oracle/or
    *.control_files='/u02/app/oracle/oradata/standby/control_sb01.ctl'
    #,'/u02/app/oracle/oradata/standby/control_02.ctl','/u02/app/oracle/oradata/standby/control_03.ctl'
    *.core_dump_dest='/u01/app/oracle/diag/rdbms/standby/standby/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    #*.db_name='standby'
    #*.dispatchers='(PROTOCOL=TCP) (SERVICE=standby)'
    *.job_queue_processes=10
    *.log_archive_dest_1='location=/opt/app/oracle/arch'
    *.log_archive_config='dg_config=(standby,ora11g)'
    *.log_archive_dest_1='LOCATION=/opt/app/oracle/oradata/standby/archivelog'
    *.log_archive_dest_2='service=orcl valid_for=(online_logfiles,primary_role) db_unique_name=ora11g'
    *.log_archive_format='%t_%s_%r.dbf'
    *.standby_file_management=auto
    *.db_unique_name =standby
    *.fal_server='ora11g'
    *.fal_client='standby'
    *.service_names='standby'
    *.open_cursors=300
    *.pga_aggregate_target=525336576
    *.processes=1500
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=1576009728
    *.undo_management='AUTO'
    *.undo_tablespace='undotbs02'
    #*.user_dump_dest='/opt/app/oracle/diag/rdbms/standby/standby/trace'
    *.standby_file_management ='manual'
    *.instance_name =standby
    #*.standby_archive_dest=/opt/app/oracle/oradata/standby/archivelog
    *.db_file_name_convert=(/u02/app/ora11g/oradata/ora11g,/u02/app/oracle/oradata/standby)
    *.log_file_name_convert='/u02/app/ora11g/oradata/ora11g','/u02/app/oracle/oradata/standby'
    #*.remote_listener=LISTENER_ora11g

  • Unable to open database in READ ONLY mode

    When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
    1) Startup mount
    2) SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-16005: database requires recovery
    But database opens succesfully when opened in READ WRITE mode.

    user12038051 wrote:
    When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
    1) Startup mount
    2) SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-16005: database requires recovery
    But database opens succesfully when opened in READ WRITE mode.
    sqlplus '/as sysdba'
    shutdown imediate;
    startup;
    shutdown imediate;
    startup mount;
    recover database;
    alter database open read only;

  • Cannot open standby database in read only....

    i do the following procedure on my standby database
    ORACLE 9.2.0.7
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 538412112 bytes
    Fixed Size 742480 bytes
    Variable Size 402653184 bytes
    Database Buffers 134217728 bytes
    Redo Buffers 798720 bytes
    SQL> lter database mount standby database;
    SP2-0734: unknown command beginning "lter datab..." - rest of line ignored.
    SQL> alter database mount standby database;
    Database altered.
    SQL> SQL> recover standby database until cancel;
    ORA-00279: change 4274363673 generated at 09/18/2006 11:25:08 needed for thread
    1
    ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9135.arc
    ORA-00280: change 4274363673 for thread 1 is in sequence #9135
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 4275275613 generated at 09/18/2006 14:03:09 needed for thread
    1
    ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9136.arc
    ORA-00280: change 4275275613 for thread 1 is in sequence #9136
    ORA-00278: log file '/u12/oradata/dbadmon/arch/dbadmon9135.arc' no longer
    needed for this recovery
    ORA-00308: cannot open archived log '/u12/oradata/dbadmon/arch/dbadmon9136.arc'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    THEN i check in the alert...
    Errors in file /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc:
    ORA-00704: bootstrap process failure
    ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
    Mon Sep 18 13:59:16 2006
    Error 704 happened during db open, shutting down database
    USER: terminating instance due to error 704
    Instance terminated by USER, pid = 24028
    ORA-1092 signalled during: alter database open read only...
    followed by the trace file...
    /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    ORACLE_HOME = /u00/oracle/product/9.2.0.1
    System name: AIX
    Node name: eserver1
    Release: 1
    Version: 5
    Machine: 000651FA4C00
    Instance name: dbadmon
    Redo thread mounted by this instance: 1
    Oracle process number: 14
    Unix process pid: 24028, image: oracle@eserver1 (TNS V1-V3)
    *** SESSION ID:(11.1) 2006-09-18 13:58:57.859
    Start recovery at thread 1 ckpt scn 4274363673 logseq 9135 block 2
    *** 2006-09-18 13:59:00.215
    Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9135.arc
    *** 2006-09-18 13:59:11.868
    Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9136.arc
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 27062Kb in 13.99s => 1.86 Mb/sec
    Longest record: 8Kb, moves: 22/97639 (0%)
    Change moves: 43706/193539 (22%), moved: 4Mb
    *** 2006-09-18 13:59:14.688
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
    Current SQL statement for this session:
    select /*+ rule */ name,file#,block#,status$,user#,undosqn,xactsqn,scnbas,scnwrp,DECODE(inst#,0,NULL,inst#),ts#,spare1 from undo$
    where us#=:1
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    ksedmp+0148 bl ksedst 1029170CC ?
    ksfdmp+0018 bl 01FD771C
    kgeriv+0118 bl _ptrgl
    kgesiv+0080 bl kgeriv FFFFFFFFFFEBEF0 ? 080000000 ?
    101A6C640 ? 000000000 ?
    FFFFFFFFFFEBE70 ?
    ksesic5+005c bl kgesiv 70000000E517A78 ?
    70000000E517748 ?
    Can anyone gie me a hand please???
    Thanks in advance.

    Doc ID: Note:1038418.6
    Please check permissions on dump desitnation directory.
    Also check if dual table is present.

  • Starting database in Read only mode

    hi,
    i am using oracle 8i, we want to copy the Production database to other machine, but on starting that m/c database should be opened in read only mode without DBA interaction what to do for that. pl tell
    thanx in advance

    SQL> STARTUP MOUNT
    ORACLE instance started.
    Total System Global Area 177281688 bytes
    Fixed Size 453272 bytes
    Variable Size 150994944 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    SQL> ALTER DATABASE OPEN READ ONLY;
    Database altered.
    SQL> DELETE FROM SCOTT.EMP;
    DELETE FROM SCOTT.EMP
    ERROR at line 1:
    ORA-16000: database open for read-only access
    kuljeet pal singh

  • Oracle 9.2.0.2 fails open read only with java exception

    Hi folks!
    I hope you can help me to narrow down this issue.
    I've a database running on windows 2003 64 bits. Oracle version is 9.2.0.2.
    I'm experiencing the following issue:
    When I try to open my database in read only mode, it crashes with ORA-604 and ORA-16000.
    The trace is pointing me to some kind of connection to an SQL Server...., but, to tell truth, I'm not understandig the problem, can anyone help me?
    The error itself is:
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]No ResultSet set was produced.
    Thanks!

    I know this is not an tail -f 50 ...., but the last 100 lines are equals to the following:
    "starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=12
    ARC0: Archival started
    ARC1 started with pid=13
    ARC1: Archival started
    Sun Aug 22 21:36:12 2010
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Sun Aug 22 21:36:12 2010
    ARC0: Thread not mounted
    Sun Aug 22 21:36:12 2010
    ARC1: Thread not mounted
    Sun Aug 22 21:36:13 2010
    ALTER DATABASE MOUNT
    Sun Aug 22 21:36:17 2010
    Successful mount of redo thread 1, with mount id 1255534413.
    Sun Aug 22 21:36:17 2010
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE MOUNT
    Sun Aug 22 21:36:32 2010
    alter database open read only
    Sun Aug 22 21:36:34 2010
    SMON: enabling cache recovery
    Sun Aug 22 21:36:34 2010
    Database Characterset is WE8ISO8859P1
    Sun Aug 22 21:36:37 2010
    Errors in file c:\oracle\admin\orcl\udump\orcl_ora_32704.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-16000: database open for read-only access"
    Obviously, with the details of the startup.
    One additional detail:
    After that errors, I started the database on restrict mode, and it opens (I fact, this is not surprising, I was expecting that result)
    I'll keep working on this....

  • Access Database Opens in Read Only for Users

    I just moved an Access Database to a new server (from Server 2003 to Server 2012). From the server, using Office 2010, I can open the database without issue but, if a user try's to open the same database from either a shortcut or mapped with Office 2010,
    they get the message that the database is Read Only. Did I miss a step in moving the database to the new server? Thanks

    Hi,
    Did your user get the error message "You are trying to open a read-only database..."? If it was, please try the following method:
    On the desktop, double-click My Computer.
    Locate the Microsoft Access database that you moved.
    Right-click the database name, and then click Properties.
    In the Properties dialog box, clear the Read-only check box under
    Attributes.
    Click OK to apply the change.
    Open your database in Access.
    Resource:
    http://support.microsoft.com/kb/324666/en-us (It also applies to Access 2010)
    Hope it's helpful.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Using  Data Pump when database is read-only

    Hello
    I used flashback and returned my database to the past time then I opened the database read only
    then I wanted use data pump(expdp) for exporting a schema but I encounter this error
    ORA-31626: job does not exist
    ORA-31633: unable to create master table "SYS.SYS_EXPORT_SCHEMA_05"
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPV$FT", line 863
    ORA-16000: database open for read-only access
    but I could by exp, export that schema
    My question is that , don't I can use Data Pump while database is read only ? or do you know any resolution for the issue ?
    thanks

    You need to use NETWORK_LINK, so the required tables are created in a read/write database and the data is read from the read only database using a database link:
    SYSTEM@db_rw> create database link db_r_only
      2   connect to system identified by oracle using 'db_r_only';
    $ expdp system/oracle@db_rw network_link=db_r_only directory=data_pump_dir schemas=scott dumpfile=scott.dmpbut I tried it with 10.2.0.4 and found and error:
    Export: Release 10.2.0.4.0 - Production on Thursday, 27 November, 2008 9:26:31
    Copyright (c) 2003, 2007, Oracle.  All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORA-39006: internal error
    ORA-39065: unexpected master process exception in DISPATCH
    ORA-02054: transaction 1.36.340 in-doubt
    ORA-16000: database open for read-only access
    ORA-02063: preceding line from DB_R_ONLY
    ORA-39097: Data Pump job encountered unexpected error -2054
    I found in Metalink the bug 7331929 which is solved in 11.2! I haven't tested this procedure with prior versions or with 11g so I don't know if this bug only affects to 10.2.0.4 or 10* and 11.1*
    HTH
    Enrique
    PS. If your problem was solved, consider marking the question as answered.

  • 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.

  • 11gR2 Real Time Apply / open read only

    Hi,
    I have a single instance primary database with a physical standby. The release is 11.2.0.1.0.
    Max Availability mode
    LGWR SYNC transport
    Data Guard Broker configuration enabled
    Both the primary and standby database are registered with the Grid Infrastructure (Standalone installation on each server, no cluster)
    When I stop and start the standby database it seems to default to open read only using Managed Real Time Recovery.
    SQL> SELECT DEST_ID, RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS
    2> WHERE DEST_ID=2;
    DEST_ID RECOVERY_MODE
    2 MANAGED REAL TIME APPLY
    I do not want to Active Data Guard on this particular database. So I removed and added the database again using srvctl this time supplying the -s mount flag. Now when I stop/start the standby it opens in mount mode and MANAGED recovery which is OK.
    My question is why did the standby automatically get opened in read only. Is the a change in behaviour introduced along with Active Data Guard? Is the default behaviour for a database registered with Grid Infrastructure to simply start the database in open mode and becuase this is 11.2 standby this means open read only?
    Thanks

    Dear user234564,
    This has been introduced in Oracle Database 11g Data Guard New Features and it is called the Active Data Guard. With the new release you can open the physical standby database in read only mode and the real time apply will continue as it is on the mount stage. This ability has not been granted on 10g. So i think it could be the normal behaviour.
    11g physical standby database will be opened and the MRP process will still apply the archivelogs to the standby database. You can simply have it tested.
    Please refer;
    http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/manage_ps.htm#CHDGJEFF
    Let me give you a quick hint but it is off topic;
    The number of standby databases that a primary database can support is increased from 9 to 30 in this release.
    The capability to create 30 standby databases, combined with the functionality of the Oracle Active Data Guard option, allows the creation of reader farms that can be used to offload large scale read-only workloads from a production database.Hope That Helps.
    Ogan

  • Infosec returing error on Lync Edge Server "3.2.5. Database Open Access (database-open-access)"

    I am working on a deployment and in order to get the ports opened to the outside world the InfoSec team runs a scan against the Edge servers. They have come back with the following issue. Has anyone run across this and how do you work around it?
    .2.5. Database Open Access (database-open-access)
    Description:
    The database allows any remote system the ability to connect to it. It is recommended to limit direct access to trusted systems because
    databases may contain sensitive data, and new vulnerabilities and exploits are discovered routinely for them. For this reason, it is a
    violation of PCI DSS section 1.3.7 to have databases listening on ports accessible from the Internet, even when protected with secure
    authentication mechanisms.
    Affected Nodes:
    Affected Nodes: Additional Information:
    69.197.x.x:1434 Running Microsoft SQL Monitor service
    Page 17
    Audit Report
    Affected Nodes: Additional Information:
    69.197.x.x:52591 Running TDS service
    69.197.x.x:1434 Running Microsoft SQL Monitor service
    69.197.x.x:51773 Running TDS service
    References:
    Source Reference
    URL
    https://www.pcisecuritystandards.org/security_standards/download.html?id=pci_dss_v1-2.pdf
    Vulnerability Solution:
    Configure the database server to only allow access to trusted systems. For example, the PCI DSS standard requires you to place the
    database in an internal network zone, segregated from the DMZ

    Hi,
    Would you please tell us which ports did you open for Edge server?
     It seems you open the wrong port from Edge server, please open the right ports for both Edge internal and external interface with the help of the link below:
    http://technet.microsoft.com/en-us/library/gg425891.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Putting apps database in Read-Only mode

    Hi,
    I want to put the apps database in read-only mode to that user will be able to login into the applications and see data but will not be able to update it.
    What is the best way to do this?
    Thanks

    I am still looking at how to do this because if users
    update the UAT/test database, when the prod upgrade
    is completed, they will think that their updates will
    be available and this will cause some issues.This is a training/expectation-setting issue, not a technical one. You need to make sure that your users understand the difference between a test system and production, and that changes made in testing will not be present in production. They also need to understand that this situation is actually to their benefit: it enables them to really work with the test system to uncover potential problems and learn new features, without fear of making changes that could negatively impact their day-to-day work in production.
    Please note that I'm not trying to be a jerk here. I very respectfully submit that attempting to make an instance read-only for training purposes, even if possible, will involve a great deal of technical work for very little (and perhaps even negative) overall benefit to the users.
    Regards,
    John P.

Maybe you are looking for