asebosm.blogg.se

Sg300 cli show interface errors
Sg300 cli show interface errors












Thus, if the database is shut down and restarted outside of Oracle Enterprise Manager and DGMGRL (such as from the SQL*Plus interface), the database uses the new parameter values from the updated server parameter file when it starts. If broker management of the database is enabled, setting a database property value causes the underlying parameter value to be changed in the corresponding database, and the value for the changed parameter is reflected in the server parameter file. LocalListenerAddress = '(ADDRESS=(PROTOCOL=TCP)(HOST=dr.foo.com)(PORT=1514))' The following example shows the properties for the DR_Sales database.ĭGMGRL> SHOW DATABASE VERBOSE 'DR_Sales' Use the SHOW DATABASE VERBOSE command to view all properties and their values for a database. Property "StandbyArchiveLocation" updated. For example, the following statements set the LogArchiveFormat and StandbyArchiveLocation properties for the DR_Sales standby database:ĭGMGRL> EDIT DATABASE 'DR_Sales' SET PROPERTY 'LogArchiveFormat'='log_%t_%s_%r_%d.arc' ĭGMGRL> EDIT DATABASE 'DR_Sales' SET PROPERTY 'StandbyArchiveLocation'='/archfs/arch/' Use the SHOW CONFIGURATION command to verify that the DR_Sales database was added to the DRSolution configuration:ħ.3 Scenario 2: Setting Database PropertiesĪfter you create the configuration with DGMGRL, you can set database properties at any time. The name DR_Sales is the value of the database's DB_UNIQUE_NAME initialization parameter. The following command defines DR_Sales as a standby database, which is the standby database associated with the primary database called North_Sales: To add a standby database to the DRSolution configuration, use the ADD DATABASE command to create a broker configuration profile for the standby database. Step 5 Add a standby database to the configuration. Use the SHOW CONFIGURATION command to display a brief summary of the configuration: Step 4 Show the configuration information. The name North_Sales is the value of this database's DB_UNIQUE_NAME initialization parameter. > CONNECT IDENTIFIER IS North_ ĭGMGRL returns the following information:Ĭonfiguration "DRSolution" created with primary database "North_Sales" Use the CREATE CONFIGURATION command to create the DRSolution configuration and define the primary database, North_Sales:ĭGMGRL> CREATE CONFIGURATION 'DRSolution' AS Fetch these from their DB_UNIQUE_NAME initialization parameter as follows: The names for the primary and standby databases must match their database unique names. The next time you start the Oracle instance, the broker is started automatically, and you do not need to issue the SQL ALTER SYSTEM statement again. The parameter value will be saved in the server parameter file. If an instance was not started with a server parameter file, then you must shut down the instance and restart it using the server parameter file.Īfter starting the Oracle instance, set the DG_BROKER_START=TRUE initialization parameter using the SQL ALTER SYSTEM statement. You must use a server parameter file with the broker (see Section 2.1 and Section 8.1.3).Ĭonvert the initialization parameter files (PFILE) on both primary and standby databases into server parameter files (SPFILE), if necessary. The DG_BROKER_START initialization parameter must be set to TRUE for all databases in the configuration. One of the prerequisites for using DGMGRL is that a primary database and any standby databases must already exist.














Sg300 cli show interface errors