Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: An operation has completed normally, having met no exceptions.
Action: No action required.
Cause: The server's configuration data has a problem of some sort which prevents the server from starting.
Action: Previous error messages in the log file will specify the exact problems leading to the shutdown. The problem most frequently occurs when the network is broken up into multiple administrative regions and the delegation points are incorrect. Read the Oracle Names documentation sections on region delegation and ensure that their directions are being followed correctly.
Cause: The server's configuration contains more domains than the server can support. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains an invalid domain description list. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains duplicate domain descriptions in the domain description list. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a domain description with an invalid name. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a domain description with an invalid minimum TTL. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a domain description with an invalid minimum TTL. This error is not fatal; the server will automatically set the TTL to a default value which is suitable for most uses. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message written to the log file during normal server startup.
Action: No action required.
Cause: An error was encountered while trying to load the server's topology data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: An informational message written to the log file when the server has been forced to load from its most recent topology checkpoint file, by setting the NAMES.NO_REGION_DATABASE parameter to TRUE.
Action: No action required.
Cause: An informational message written to the log file during normal server startup.
Action: No action required.
Cause: An error was encountered while trying to load the server's domain data from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: An informational message written to the log file when the server has been forced to load from its most recent domain checkpoint file, by setting the NAMES.NO_REGION_DATABASE parameter to TRUE.
Action: No action required.
Cause: An informational message written to the log file during normal server startup.
Action: No action required.
Cause: An informational message written to the log file whenever the Net8 Assistant or the Oracle Names control program send a reload request to the server.
Action: No action required.
Cause: An informational message written to the log file whenever the Oracle Names control program halts a reload request previously sent to the server
Action: No action required.
Cause: This warning is issued whenever the server fails to connect to the configuration database to see if any configuration data has changed. The server will automatically begin reissuing reload checks more frequently, and will eventually give up if connections fail continuously for three days.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database.
Cause: A warning issued whenever the server has continuously failed for three days in its attempts to connect to the configuration database. The server disables reload checking. Reload checking can later be re-enabled from the Net8 Assistant or the Oracle Names control program.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: An informational message written to the log file whenever the server's configuration has changed, and the server is reloading the new configuration from the configuration database.
Action: No action required.
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: This is an internal error, not normally visible to the user.
Action: Enable tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: An informational message written to the log file during normal server startup.
Action: No action required.
Cause: An informational message written to the log file during normal server startup.
Action: No action required.
Cause: An internal delegation error has occurred. Delegation is controlled by the Oracle Network Manager, which enforces correct delegation rules. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An internal configuration error has occurred. The Oracle Network Manager is responsible for configuring Oracle Names servers correctly. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a syntax error its domain data. This message will also appear if the server's internal checkpoint files become corrupted. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found an invalid global name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found an invalid TTL in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message which appears during server startup when the server detects out-of-date cached data in its cache checkpoint file. The message is part of normal server startup.
Action: No action required.
Cause: The server found an invalid TTL value in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found an invalid data type name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found an unknown data type in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found an invalid data type syntax in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a duplicate record in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a alias and non-alias data with the same global name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a alias and non-alias data with the same global name in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found more than one record with the same name and type, when the type allows only a single record with a particular name. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a record with an invalid data type in its domain data.
Action: No action required; adjustments to data will eliminate the warning.
Cause: The server found a record with a missing data type in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a record whose length exceeds an internal limit. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found a global name in its domain data for which it is not authoritative. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server found an invalid record in its domain data. The record in question is not loaded, but the server continues to load data. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: the server found an invalid record in its domain data. The record in question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Oracle Support Services.
Cause: the server found an invalid global name in its domain data. The record in question is not loaded, but the server continues to load data.
Action: Contact Oracle Support Services.
Cause: an object in the domain data is apparently not in the domains which the server is authoritative for. The record in question is not loaded, but the server continues to load data.
Action: Check for inconsistencies in the data and correct any errors in topology definition or domain data outside of authoritative domains.
Cause: The server's configuration contains an invalid hint description list. The server will continue to run, but will not load any hints. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contained a hint for a domain in the server's administrative region. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: There are too many hints in the server's hint list. The server will load a specified maximum number of hints, ignore the rest, and continue running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a hint domain with an invalid name. The domain is ignored and the server continues to run. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a hint with an invalid server name. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a hint with no server address. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a hint whose address length exceeds an internal limit. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a hint with an invalid address. The hint is ignored and the server continues to run. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's hint domain list is too long. The server will load a specified maximum number of hint domains, ignore the rest, and continue running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's hint domain list contains a duplicate domain. The duplicate is ignored and the server continues running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's hint server list contains a duplicate server. The duplicate is ignored and the server continues running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server encountered an invalid administrative region description during startup. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.ADMIN_REGION parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: The server's administrative region description is missing a required parameter. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.ADMIN_REGION parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: The server encountered an invalid administrative region parameter. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.ADMIN_REGION parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: The server encountered an administrative region parameter whose length exceeds an internal limit. This error will prevent the server from starting. The administrative region description is stored in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.ADMIN_REGION parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: The server encountered an administrative region parameter with an invalid value. The value is set to a default suitable for most applications, and the server continues running. The administrative region description is stored in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.ADMIN_REGION parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: The server was unable to initialize ROS during startup. The error prevents the server from running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message which appears during server startup, and notes the name of the administrative region for future diagnostic use by administrators. The message is part of normal server startup.
Action: No action required.
Cause: The server encountered an error while trying to get the configuration database's serial number. The error occurs almost always because the server is unable to access the configuration database. If the error occurs during server startup, the server will shut down. If the error occurs during server operation (the server checks the serial number periodically to see if it should reload itself), then the server assumes a transient failure has occurred and repeats the operation a short while later. If the repetitions continue to fail for three days, the server will log another error and stop issuing the serial number load operation.
Action: First make sure that the NETADMIN program has exported a server configuration for this name server. Next, make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. If the error occurs during server startup, you can force startup anyway, with checkpoint data, by starting the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: An error was encountered while trying to load the server's configuration from the configuration database. If more information is available, it will appear under this error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: The configuration database has not been properly installed.
Action: Make sure the Oracle Network Manager and its database have been properly installed
Cause: An informational message written to the log file when the server has been forced to load from its most recent configuration checkpoint file, by setting the NAMES.NO_REGION_DATABASE parameter to TRUE.
Action: No action required.
Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: The server was unable to write the named checkpoint file. This problem is typically due to the file system's protection settings. The error is not fatal; it means the server will not create any checkpoint data. Note, however, that if the configuration database is ever unavailable during a future server startup, the lack of checkpoint data means you will be unable to force a startup from checkpoint data with the NAMES.NO_REGION_DATABASE parameter.
Action: Check to see that the server has permission to write the file named in the error message.
Cause: The server encountered an error while accessing the configuration database. The error can occur when the database is unavailable, or SQL*Net connectivity to the database is interrupted.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: The server attempted to fetch data from the configuration database and no data was found.
Action: The error generally appears underneath a more specific error which will tell you the exact nature of the problem.
Cause: The server was started using checkpoint data, and was unable to read that data. The remaining errors below this one on the error stack provide more specific information about the problem.
Action: Check to see that the named file exists and that the server has permission to read it.
Cause: The server encountered an error while trying to get its configuration ID from the configuration database. The error can occur any time the server is unable to access the configuration database. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: The server successfully contacted the configuration database, but was unable to find any configuration information associated with the server's name. The name is specified in the server's NAMES.ORA configuration file. The error occurs almost always because the server configuration has not been exported from the NETADMIN program.
Action: Make sure that the NETADMIN program has exported a server configuration for this name server.
Cause: An informational message indicating that the server has been started with the NAMES.NO_REGION_DATABASE parameter set to TRUE, and that it will use checkpoint data rather than attempting to contact the configuration database.
Action: No action required.
Cause: The server cannot use the specified configuration database because it is of an incorrect version.
Action: Run the document conversion utility supplied with the Network Manager and re-export your network. The conversion utility will upgrade old documents to a version which can be understood by the name server.
Cause: An ORACLE error was encountered while accessing the configuration database. The error can occur when the database is unavailable, or SQL*Net connectivity to the database is interrupted.
Action: Make sure that the database is running, that its name and password as specified in the Oracle Network Manager are accurate, and that there is SQL*Net connectivity between the Oracle Names server and the database. To force the server to start up anyway, using its checkpoint data, start the server with the NAMES.NO_REGION_DATABASE parameter set to TRUE. If no checkpoint data is available, the server will shut down.
Cause: The region description in NAMES.ORA is out of synch with the network definition.
Action: No action is required unless the name server cannot run with the network definition. To be safe NAMES.ORA should be updated with one which is consistent with the network definition.
Cause: There is a syntax error in the DIT/DN provided in the region description.
Action: Correct the error and restart the server.
Cause: The server's configuration is missing addresses on which to listen. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message written to the log file when the server receives a shutdown request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server shuts down.
Action: No action required.
Cause: An informational message written to the log file when the server successfully starts up.
Action: No action required.
Cause: The length of one of the server's listen addresses exceeds an internal limit. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message written to the log file when the server changes its trace level in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file whenever the Oracle Names control program halts a shutdown request previously sent to the server
Action: No action required.
Cause: The server's name is invalid. The name is specified in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.SERVER_NAME parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: An informational message written to the log file when the server receives a restart request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server restarts.
Action: No action required.
Cause: An informational message written to the log file whenever the Oracle Names control program halts a restart request previously sent to the server
Action: No action required.
Cause: The server's configuration contains an invalid listen address list. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains an invalid listen address. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's password length exceeds an internal limit. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server encountered an error while changing its trace level in response to a request from the Oracle Names control program. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: An informational message written to the log file during server startup.
Action: No action required.
Cause: An informational message written to the log file when the server disables statistic counter resetting in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server changes its statistic counter reset interval in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server resets its statistic counters in response to a request from the Oracle Names control program.
Action: No action required.
Cause: The server could not find a NAMES.SERVER_NAME parameter. The name is specified in the server's NAMES.ORA configuration file.
Action: Make sure that the NAMES.SERVER_NAME parameter in NAMES.ORA is correct. The NAMES.ORA file is automatically generated by the Oracle Network Manager, but administrators can edit the file at any time, introducing errors. If the file was never changed, contact Oracle Support Services.
Cause: An informational message written to the log file when the server disables statistics dumping in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server changes its statistic dump interval in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server dumps its statistic counters in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file at the beginning of a statistic dump. The message is followed by a set of server statistics, and ends with another informational message indicating the dump has finished.
Action: No action required.
Cause: An informational message written to the log file at the end of a statistic dump. The message is preceded by a set of server statistics.
Action: No action required.
Cause: An informational message written to the log file when the server resets its statistic counters to zero in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server saves the configuration to the configuration file in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server saves the configuration to a configuration file in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the a set operation is performed and the change cannot be saved in the save configuration table, but should be.
Action: No action required.
Cause: An informational message written to the log file when the server finds the region database has it's serial number set lower than it was when the server previously loaded the region data. This is an unnatural condition--every update to the region should increment the serial number so a reduction of the serial number might reflect tampering or accidental manual alteration this and possibly other region tables.
Action: Administrators should find out how and why the serial number decreased.
Cause: the value set in names.admin_region is an obsolete ROS type.
Action: No action is necessary; administrators should set the value to the correct type (SQL, LDAP, or LDIF).
Cause: the value set in names.admin_region is an obsolete ROS type.
Action: No action is necessary; administrators should set the value to the correct type (SQL, LDAP, or LDIF).
Cause: The server's configuration contains too many default forwarders. The server loads a specified maximum number of forwarders, ignores the rest, and continues running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration enables DEFAULT-FORWARDERS-ONLY mode but the configuration contains no default forwarders. The server ignores the request and continues running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: One of the forwarders in the default forwarder list has an invalid address. The forwarder definition is ignored and the server continues running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message written to the log file when the server enables request processing in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server disables request processing in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server enables modification-request processing in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server disables modification-request processing in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server's configuration enables DEFAULT-FORWARDERS-ONLY mode.
Action: No action required.
Cause: The server received a corrupted request. The request is ignored.
Action: corrupted requests are usually caused by transient network problems. If many corrupted messages are received, turn on tracing for further information. If the errors persist, contact Oracle Support Services.
Cause: The server's configuration contains a forwarder address whose length exceeds an internal limit. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server detected an alias loop involving the specified name. An alias loop occurs when an alias "X" points to another alias "Y", which points back to "X" rather than to an address or other name server data. The loop can contain more hops but the basic idea remains the same. Loops occur when administrators incorrectly enter network data, particularly when an alias in one administrative region points to data in another administrative region.
Action: Use the Oracle Names control program to query for the specified name. The control program will describe the alias path, and you can use that information to find which names are incorrect and what administrative regions the incorrect data belongs to.
Cause: An informational message written to the log file when the server disables request forwarding in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server enables request forwarding in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server disables the FORWARDING-DESIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server enables the FORWARDING-DESIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server disables DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server enables DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server enables the AUTHORITY-REQUIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server disables the AUTHORITY-REQUIRED attribute on queries that it generates. The message comes in response to a request from the Oracle Names control program.
Action: No action required.
Cause: If an auto-refresh query is issued and continuously returns an error for three days, the query is removed from the auto-refresh queue and a warning logged. The query can be restarted from the Oracle Names control program.
Action: this message will be preceded by numerous warnings that the query in question is failing. Use the Oracle Names control program to describe the failing query. Make sure the server being queried is running and that there is network connectivity between the querying server and the server being queried.
Cause: An informational message written to the log file when the server changes its auto-refresh retry interval in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server changes its auto-refresh expiration period in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server changes the time when an auto-refresh query is next issued. The message comes in response to a request from the Oracle Names control program.
Action: No action required.
Cause: The Oracle Names control program issued a request to enable DEFAULT-FORWARDERS-ONLY mode, and the request was ignored because the server has no default forwarders.
Action: No action required.
Cause: An informational message written to the log file when the server removes a query from the auto-refresh queue in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server changes its maximum-reforward count in response to a request from the Oracle Names control program.
Action: No action required.
Cause: The server's configuration contains an invalid forwarder description list. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: An informational message written to the log file when the server sets an artificial request-processing delay in response to a request from the Oracle Names control program.
Action: No action required.
Cause: The server's configuration contains a forwarder description with an invalid server name. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server's configuration contains a forwarder description with a missing address. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server detected a fatal delegation loop while forwarding a request. A loop occurs when the server's topology data indicates that it should forward a request to itself. The server immediately shuts down in response to this error. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: A server "X" received authoritative data from another server "Y" when server "X" is also authoritative for the data. Such situations should never arise because if server "X" is authoritative for the requested data, it should never forward the request to another server. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: The server's default forwarder list contains a duplicate server. The duplicate is ignored and the server continues running. This is an internal error, not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The server was unable to perform its normal periodic cache checkpointing, typically because the cache checkpoint file could not be written. The cache checkpoint file name appears as an informational message during server startup.
Action: Check to see that the server has permission to write the cache checkpoint file, and that there is sufficient disk space for the file to be written.
Cause: The server could not construct a system-dependent file name. This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and restart the server. If the error persists, contact Oracle Support Services.
Cause: An informational message written to the log file when the server disables cache checkpointing in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server changes its cache checkpoint interval in response to a request from the Oracle Names control program.
Action: No action required.
Cause: The server was unable to open the named checkpoint file for writing. This problem is typically due to the file system's protection settings. The error is not fatal; it means the server will not checkpoint its cache.
Action: Check to see that the server has permission to write the file named in the error message.
Cause: An informational message written to the log file when the server checkpoints its cache in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file when the server flushes its cache in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file whenever the Oracle Names control program halts a cache flush request previously sent to the server
Action: No action required.
Cause: The server attempted to flush its cache, which also deletes the cache checkpoint file. The file deletion failed, although the rest of the cache flush succeeded. Accompanying errors describe the reason for the deletion failure.
Action: This error typically occurs when two cache-flush operations are issued in succession without an intervening cache checkpoint operation (which would re-create the file). The first deletes the cache file, the second attempts to do so, but fails since the file has already been deleted. In such cases, the message is harmless and can be ignored. If, however, the error occurs because the server lacks permission to delete the file, then you must change the file system permissions so the server is allowed to delete the file.
Cause: An informational message written to the log file when the server dumps its cache to the trace file in response to a request from the Oracle Names control program.
Action: No action required.
Cause: An informational message written to the log file whenever the Oracle Names control program halts a cache dump request previously sent to the server
Action: No action required.
Cause: The server was unable to perform its normal periodic cache checkpointing, typically because the cache checkpoint file could not be written. The cache checkpoint file name appears as an informational message during server startup.
Action: Check to see that the server has permission to write the cache checkpoint file, and that there is sufficient disk space for the file to be written.
Cause: The query for the region database version failed. The database may be shut down, or the tables may not exist in the schema specified in NAMES.ORA.
Action: Correct any access problems accordingly.
Cause: Diagnostic information was returned from OCI during region database access.
Action: No action required.
Cause: The server did not provide sufficient data to the OCI interface while accessing the region database. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The server called OCI with an invalid handle whilc accessing the region database. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An OCI operation between the server and the database is still in progress.
Action: No action required.
Cause: An OCI occurred while accessing the region database. More specific details will be written to the log file.
Action: Find the appropriate entry in the log file and correct the cause of the failure if possible. Otherwise contact Oracle Support Services.
Cause: All rows have been returned from the region table.
Action: No action required.
Cause: The LDAP API returned an error. More specific details will be written to the log file.
Action: Find the appropriate entry in the log file and correct the cause of the failure if possible. Otherwise contact Oracle Support Services.
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error and correct it and restart the server.
Cause: the server could not retrieve query entries from the LDAP API.
Action: Find the cause of the error and correct it and restart the server.
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error and correct it and restart the server.
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error, correct it, and restart the server.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
