Solution : https://service.sap.com/sap/support/notes/817253 (SAP Service marketplace login required)
Summary :
Opening an Oracle database in read-only mode prevents SCN increase, supporting recovery without further data alteration. Technical actions such as querying during recovery and using flashback for investigating past events are viable. Such mode requires stable and synced datafiles, with consistent control files; discrepancies preclude read-only access. Use commands ‘startup mount’ and ‘alter database open read only’. Validate structure operations are feasible in this mode. However, operating SAP systems like R/3 or BW in read-only mode isn't possible due to internal change mechanisms such as user logon updates and statistical data storage.
Key words :
analyze table/index validate structure, startup mountalter database open read, 'validate index' filling index_stats, validate structure actions, supported oracle releases, lets oracle ignore, db abap loads, db opened read, database read, opened read
Related Notes :
| 659946 | FAQ: Temporary tablespaces |
| 592393 | FAQ: Oracle |
| 105047 | Support for Oracle functions in the SAP environment |
| 23345 | Consistency check of ORACLE database |