• About Me

    Maxwell Miranda
    Oracle DBA Consultant.
  • Category

  • Archives

  • My Blog Calendar

    October 2010
    M T W T F S S
    « Aug   Nov »
  • RSS Oracle Feeds

    • Can't access database after power outage
      I could access the database before the power outage. From what I've read, it is a problem with the environment variables, but they are correct. Not sure what else to add. C:\Documents and Settings\konoca>sqlplus / as sysdba SQL*Plus: Release - Production on Wed Feb 21 09:17:08 2018 Copyright (c) 1982, 2005, Oracle. All rights reserved. ERR […]
    • Problems with RESET DATABASE
      Recently I wanted to do RESET DATABASE. Oracle documentation suggests the following commands connect target / startup force nomount reset database to incarnation 2 run { set until time "date time" restore controlfile from autobackup alter database mount restore database recover database } alter database open resetlogs In this view my db has given e […]
  • Advertisements

Automatic Diagnostic Repository (ADR) : 11g

ADR is a single directory location for all error and trace data in the database. It replaces the traditional diagnostic directories such as bdump, cdump, and udump. ADR location is controlled by the new initialization parameter DIAGNOSTIC_DEST. Oracle recommends you choose the same ADR base for all Oracle products.


SAP : The OPS$ Mechanism Under UNIX

For the database, the SAP System is a single user, SAPR3 / SAP, whose password is stored in the table SAPUSER.
Therefore, to access the database, the SAP System uses a mechanism called the OPS$ mechanism, which works as follows:

1. When the system accesses the database, it first logs on to the database as the user OPS$, for example, OPS$adm. (The OPS$ user that corresponds to the operating system user must be defined in the database and identified as externally.)

2. It retrieves the password for SAPR3from the SAPUSER table.

3. It then logs on to the database as the user SAPR3.