75 ORA-12315 to ORA-12354
- ORA-12315: database link type is invalid for the ALTER DATABASE statement
-
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.
- ORA-12316: syntax error in database link's connect string
-
Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error.
- ORA-12317: logon to database (link name string) denied
-
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).
- ORA-12318: database (link name string) is already mounted
-
Cause: You are attempting to mount a secondary database that has already been mounted by your instance.
- ORA-12319: database (link name string) is already open
-
Cause: You are attempting to open a secondary database that is already open.
- ORA-12321: database (link name string) is not open and AUTO_MOUNTING=FALSE
-
Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.
- ORA-12322: unable to mount database (link name string)
-
Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.
- ORA-12323: unable to open database (link name string)
-
Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.
- ORA-12324: cannot use the ROM: link type on a private database link
-
Cause: You can only specify the ROM: link type on a public, not a private, database link.
- ORA-12326: database string is closing immediately; no operations are permitted
-
Cause: The database you attempted to access is closing, so your operation has been terminated.
- ORA-12329: database string is closed; no operations are permitted
-
Cause: The database you attempted to access is closed, so your operation has been terminated.
- ORA-12333: database (link name string) is not mounted
-
Cause: You attempted to open a database that has not been mounted.
- ORA-12334: database (link name string) is still open
-
Cause: You attempted to dismount a database that is still open.
- ORA-12335: database (link name string) is not open
-
Cause: You attempted to close a database that is not open.
- ORA-12336: cannot login to database (link name string)
-
Cause: You are tyring to login while another user is mounting or dismounting the same database.
- ORA-12341: maximum number of open mounts exceeded
-
Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).
- ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter
-
Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.
- ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string)
-
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.
- ORA-12350: database link being dropped is still mounted
-
Cause: An attempt was made to drop a ROM: database link that was still mounted and/or opened.
- ORA-12351: cannot create view using a remote object which has a remote object reference
-
Cause: You tried to create a view which references a remote object which, in turn, references an object on another database. Since the view that you tried to create references a remote object, that object cannot reference an object on another database.
- ORA-12352: object string.string@string is invalid
-
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.
- ORA-12353: secondary stored object cannot reference remote object
-
Cause: You tried 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.
- ORA-12354: secondary object being dropped
-
Cause: You tried to access a object (for example, a table or view) on a secondary database that was in the process of being dropped.