• About Me

    Maxwell Miranda
    Oracle DBA Consultant.
  • Category

  • Archives

  • My Blog Calendar

    September 2015
    M T W T F S S
    « Jan    
     123456
    78910111213
    14151617181920
    21222324252627
    282930  
  • 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 10.2.0.1.0 - 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

Primary Database Changes That Require Manual Intervention at a Physical Standby

Primary Database Changes That Require Manual Intervention at a Physical Standby

Most structural changes made to a primary database are automatically propagated through redo data to a physical standby database. lists primary database structural and configuration changes which require manual intervention at a physical standby database.

Table 9-1 Primary Database Changes That Require Manual Intervention at a Physical Standby

Primary Database Change Action Required on Physical Standby Database
Add a datafile or create a tablespace No action is required if the STANDBY_FILE_MANAGEMENT database initialization parameter is set to AUTO. If this parameter is set to MANUAL, the new datafile must be copied to the physical standby database.
Drop or delete a tablespace or datafile Delete datafile from primary and physical standby database after the redo data containing the DROP or DELETE command is applied to the physical standby.
Use transportable tablespaces Move tablespace between the primary and the physical standby database.
Rename a datafile Rename the datafile on the physical standby database.
Add or drop a redo log file group Evaluate the configuration of the redo log and standby redo log on the physical standby database and adjust as necessary.
Perform a DML or DDL operation using the NOLOGGING or UNRECOVERABLE clause Copy the datafile containing the unlogged changes to the physical standby database.
Grant or revoke administrative privileges or change the password of a user who has administrative privileges If the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE, replace the password file on the physical standby database with a fresh copy of the password file from the primary database.
Reset the TDE master encryption key Replace the database encryption wallet on the physical standby database with a fresh copy of the database encryption wallet from the primary database.
Change initialization parameters Evaluate whether a corresponding change must be made to the initialization parameters on the physical standby database.
Advertisements

unix CPU and Core information

# Count the number of “physical processor(s)”

grep “physical id” /proc/cpuinfo | sort -u | wc -l

# Count the number of “physical cores per CPU”

grep “cpu cores” /proc/cpuinfo |sort -u |cut -d”:” -f2

# Count the number of “logical cores ” (including multi-threading cores)

grep -c “processor” /proc/cpuinfo