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: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.
Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK statement. See your documentation for Oracle security-related products for more information about creating database links using the ROM: link type.
Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error.
Action: Drop the database link and re-create it using valid syntax. See the Oracle9i SQL Reference for more information about the connect string portion of the CREATE DATABASE LINK statement.
Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username/password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password).
Action: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database.
Cause: You are attempting to mount a secondary database that has already been mounted by your instance.
Action: The database is already mounted, so you need not take additional action to mount it. To establish access, use the ALTER DATABASE linkname OPEN statement to open the database.
Cause: You are attempting to open a secondary database that is already open.
Action: The database is open and you need not take additional action to establish access.
Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.
Action: Manually mount and open the secondary database using ALTER DATABASE linkname with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE.
Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.
Action: Follow the steps outlined in the accompanying error messages to resolve the problem.
Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.
Action: Follow the steps outlined in the accompanying error messages to resolve the problem.
Cause: You can only specify the ROM: link type on a public, not a private, database link.
Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command.
Cause: The database you attempted to access is closing, so your operation has been terminated.
Action: Wait until the database has been reopened, or contact the database administrator.
Cause: The database you attempted to access is closed, so your operation has been terminated.
Action: Wait until the database is reopened, or contact the database administrator.
Cause: An attempt was made to open a database that has not been mounted.
Action: Mount the database with the ALTER DATABASE linkname MOUNT statement, then re-attempt to open the database.
Cause: An attempt was made to dismount a database that is still open.
Action: Close the database with the ALTER DATABASE linkname CLOSE statement, then re-attempt to dismount the database.
Cause: An attempt was made to close a database that is not open.
Action: The database is closed; you can proceed with dismounting it.
Cause: An attempt was made to login while another user is mounting or dismounting the same database.
Action: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible.
Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).
Action: Change the value of this parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255.
Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.
Action: Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.
Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege.
Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database.
Cause: An attempt was made to drop a ROM: database link that was still mounted and/or opened.
Action: Close and dismount the database and then re-issue the drop statement.
Cause: An attempt was made to create a view which references a remote object which, in turn, references an object on another database. Since the view that would have been created references a remote object, that object cannot reference an object on another database.
Action: Choose a different object to reference in your view or change the remote object so that it does not reference another database.
Cause: An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database.
Action: Manually recompile the invalid object in the secondary database.
Cause: An attempt was made to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.
Action: Choose a different object to reference or change the remote view or procedure so that it does not reference another database.
Cause: An attempt was made to access an object (for example, a table or view) on a secondary database that was in the process of being dropped.
Action: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle Support Services.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
