|
Index >
ORACLE Server Parameters >
instance_name
instance_name
Oracle 11.1.0:
| Parameter Name: | instance_name
| | Description: | instance name supported by the instance
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 10.2.0:
| Parameter Name: | instance_name
| | Description: | instance name supported by the instance
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 10.1.0:
| Parameter Name: | instance_name
| | Description: | instance name supported by the instance
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 9.2.0:
| Parameter Name: | instance_name
| | Description: | instance name supported by the instance
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 8.1.7:
| Parameter Name: | instance_name
| | Description: | instance name supported by the instance
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 8.0.6:
No such parmeter in Oracle 8.0.6.
Oracle 7.3.4:
No such parmeter in Oracle 7.3.4.
Related Error Messages:
ORA-12521: TNS:listener does not currently know of instance requested in connect descriptorCause: The listener received a request to establish a connection to adatabase or other service. The connect descriptor received by the listenerspecified in addition to the service name an instance name for an instance(usually a database instance) that either has not yet dynamically registeredwith the listener or has not been statically configured for the listener.This may be a temporary condition such as after the listener has started,but before the database instance has registered with the listener.Action: - Wait a moment and try to connect a second time. - Check which instances are currently known by the listener by executing: lsnrctl services - Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener. - Check for an event in the listener.log file.
ORA-16626: failed to enable specified object Cause: The broker failed to enable management of an object (most likely a standby database). You can expect to see this status when attempting to enable broker management of a standby database that: - cannot locate itself in the broker configuration file. - fails to distinguish itself from two or more databases in the configuration file. - determines it was not part of a change of primary database due to failover.Action: To correct the problem, try one of these actions: - confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE. - confirm that you have not created two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not indicate the same physical database. - if you had performed a failover and have re-created your old primary database (or a standby database that had to be re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files that are in use by the new primary database.
This parameter is documented in the
Oracle Server Reference Guide.
Search for more info about
[ instance_name ]
on the Oracle FAQ.
| 
